Can not take live backup and snapshot's

[withouck.vincent]

Hello,

I'am using
Virtual Environment 7.2-4


I want to take backup's from my lxc container on a nfs storage.
I do not want to change the tmpdir.




My config file of the container





If I disable the fuse feature then i can take a backup. Do not want to disabla this too. I need this because on my container I have installed proxmox .


Taking snapshot's is not possible also.



How can I make this working.

Thx

 

[withouck.vincent]

When i stop the container then I can take a backup.

 

[fiona]

Hi,
you could try to configure a local tmpdir in /etc/vzdump.conf to see if that works. Please also see this thread (TL;DR try to replace fuse mounts with bind mounts).

Regarding not being able to take snapshots, that's because of a missing mechanism to snapshot the bind mounts, so the container can't be snapshot as a whole.

P.S. if you post the output in [CODE]your log here[/CODE] tags it will show as

your log here

be much more readable, searchable and not cut off

 

[withouck.vincent]

Hi,
you could try to configure a local tmpdir in /etc/vzdump.conf to see if that works. Please also see this thread (TL;DR try to replace fuse mounts with bind mounts).

Regarding not being able to take snapshots, that's because of a missing mechanism to snapshot the bind mounts, so the container can't be snapshot as a whole.

P.S. if you post the output in [CODE]your log here[/CODE] tags it will show as

Sep 14 15:55:21 demo01 pvedaemon[1220]: <root@pam> end task UPID:demo01:00002962:0001EA8D:6321D9A3:vzdump:108:root@pam: unexpected status
Sep 14 15:55:21 demo01 pvedaemon[19641]: INFO: starting new backup job: vzdump 113 --node demo01 --storage hcb-storage --notes-template Testje --compress zstd --remove 0 --mode snapshot
Sep 14 15:55:22 demo01 pvedaemon[19641]: INFO: Starting Backup of VM 113 (lxc)
Sep 14 15:55:22 demo01 ntpd[936]: 162.159.200.1 local addr 10.45.78.53 -> <null>
Sep 14 15:55:56 demo01 ntpd[936]: 81.21.65.168 local addr 10.45.78.53 -> <null>
Sep 14 15:56:09 demo01 pvedaemon[1219]: worker exit
Sep 14 15:56:10 demo01 pvedaemon[1217]: worker 1219 finished
Sep 14 15:56:10 demo01 pvedaemon[1217]: starting 1 worker(s)
Sep 14 15:56:10 demo01 pvedaemon[1217]: worker 20471 started
Sep 14 15:56:27 demo01 corosync[1171]: [KNET ] link: host: 1 link: 0 is down
Sep 14 15:56:27 demo01 corosync[1171]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 14 15:56:27 demo01 corosync[1171]: [KNET ] host: host: 1 has no active links
Sep 14 15:56:30 demo01 corosync[1171]: [KNET ] rx: host: 1 link: 0 is up
Sep 14 15:56:30 demo01 corosync[1171]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 14 15:57:15 demo01 pvedaemon[1218]: worker exit
Sep 14 15:57:15 demo01 pvedaemon[1217]: worker 1218 finished
Sep 14 15:57:15 demo01 pvedaemon[1217]: starting 1 worker(s)
Sep 14 15:57:15 demo01 pvedaemon[1217]: worker 21089 started
Sep 14 15:57:51 demo01 corosync[1171]: [KNET ] link: host: 3 link: 0 is down
Sep 14 15:57:51 demo01 corosync[1171]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Sep 14 15:57:51 demo01 corosync[1171]: [KNET ] host: host: 3 has no active links
Sep 14 15:57:54 demo01 corosync[1171]: [KNET ] rx: host: 3 link: 0 is up
Sep 14 15:57:54 demo01 corosync[1171]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Sep 14 15:59:25 demo01 corosync[1171]: [KNET ] link: host: 3 link: 0 is down
Sep 14 15:59:25 demo01 corosync[1171]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Sep 14 15:59:25 demo01 corosync[1171]: [KNET ] host: host: 3 has no active links
Sep 14 15:59:28 demo01 corosync[1171]: [KNET ] rx: host: 3 link: 0 is up
Sep 14 15:59:28 demo01 corosync[1171]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Sep 14 15:59:35 demo01 corosync[1171]: [KNET ] link: host: 1 link: 0 is down
Sep 14 15:59:35 demo01 corosync[1171]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 14 15:59:35 demo01 corosync[1171]: [KNET ] host: host: 1 has no active links
Sep 14 15:59:38 demo01 corosync[1171]: [KNET ] rx: host: 1 link: 0 is up
Sep 14 15:59:38 demo01 corosync[1171]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 14 16:00:38 demo01 corosync[1171]: [KNET ] link: host: 1 link: 0 is down
Sep 14 16:00:38 demo01 corosync[1171]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 14 16:00:38 demo01 corosync[1171]: [KNET ] host: host: 1 has no active links
Sep 14 16:00:41 demo01 corosync[1171]: [KNET ] rx: host: 1 link: 0 is up
Sep 14 16:00:41 demo01 corosync[1171]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 14 16:01:34 demo01 ntpd[936]: 178.32.55.184 local addr 10.45.78.53 -> <null>
Sep 14 16:02:19 demo01 pvedaemon[19641]: ERROR: Backup of VM 113 failed - command 'rsync --stats -h --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' '--exclude=/mnt/pve/iso-library' '--exclude=/mnt/pve/iso-hcb' /proc/18184/root//./ /mnt/pve/hcb-storage/dump/vzdump-lxc-113-2022_09_14-15_55_21.tmp' failed: exit code 23
Sep 14 16:02:19 demo01 pvedaemon[19641]: INFO: Backup job finished with errors
Sep 14 16:02:19 demo01 pvedaemon[19641]: job errors
Sep 14 16:03:05 demo01 corosync[1171]: [KNET ] link: host: 3 link: 0 is down

be much more readable, searchable and not cut off

I have said "I do not want to change the tmpdir into /tmp local directory". And than it works if I so. The reason I do not want to change is because my local disk is to small to make large backup's. Question : where is the backup made when I change it to /tmp ? I think it is the /tmp directory. Can you confirm this also. If not then I can change the tmpdir in the config file.

 

[fiona]

I have said "I do not want to change the tmpdir into /tmp local directory".

Sorry, I missed that part. But it might be necessary for your use case with NFS target and fuse mounts.

And than it works if I so. The reason I do not want to change is because my local disk is to small to make large backup's. Question : where is the backup made when I change it to /tmp ? I think it is the /tmp directory. Can you confirm this also. If not then I can change the tmpdir in the config file.

You can configure any directory with tmpdir: /some/path, it doesn't have to be /tmp. But if you don't have enough space locally, you should have a look at the other thread and try to replace the fuse mounts.