Hi everyone,
We actually face a problem for scheduling backups of lxc containers with a second raw disk as a mountpoint (mp0).
vzdump seems to ignore this and only backup the raw rootfs. Even with options like backup=1 or backup=yes specified.
Here is the container conf:
root@pmx1:~# cat /etc/pve/lxc/100.conf
arch: amd64
cpulimit: 4
cpuunits: 1024
hostname: nginx-master
memory: 8192
mp0: local:100/vm-100-disk-2.raw,mp=/elq,size=100G,backup=1
net0: bridge=vmbr0,gw=10.101.240.254,hwaddr=36:65:36:63:34:63,ip=10.101.240.11/24,name=eth0,type=veth
onboot: 1
ostype: debian
rootfs: local:100/vm-100-disk-1.raw,size=8G
swap: 2048
Is there an option to force this somewhere, could'nt find a precise answer on the forum. I'm pretty sure this only works when mount point is not raw but on the host filesystem.
We're on a fresh 4.2 install
Thanks in advance.
We actually face a problem for scheduling backups of lxc containers with a second raw disk as a mountpoint (mp0).
vzdump seems to ignore this and only backup the raw rootfs. Even with options like backup=1 or backup=yes specified.
Here is the container conf:
root@pmx1:~# cat /etc/pve/lxc/100.conf
arch: amd64
cpulimit: 4
cpuunits: 1024
hostname: nginx-master
memory: 8192
mp0: local:100/vm-100-disk-2.raw,mp=/elq,size=100G,backup=1
net0: bridge=vmbr0,gw=10.101.240.254,hwaddr=36:65:36:63:34:63,ip=10.101.240.11/24,name=eth0,type=veth
onboot: 1
ostype: debian
rootfs: local:100/vm-100-disk-1.raw,size=8G
swap: 2048
Is there an option to force this somewhere, could'nt find a precise answer on the forum. I'm pretty sure this only works when mount point is not raw but on the host filesystem.
We're on a fresh 4.2 install
Thanks in advance.