LXC unfinished backups

[RedBull]

Good morning, I ask if the same problem may have happened to anyone, when I perform a backup of a container (LXC) the process starts but does not end, while this does not happen with virtual machines. Can you help me please?

LCX ubuntu

 

[fiona]

Hi,
please post the output of pveversion -v, pct config <container ID> and the complete backup log. What kind of storage are the container volumes on, what kind of storage is the backup storage?

 

[RedBull]

2022-03-01 15:45:02 INFO: Starting Backup of VM 300 (lxc)
2022-03-01 15:45:02 INFO: status = running
2022-03-01 15:45:02 INFO: CT Name: web
2022-03-01 15:45:02 INFO: including mount point rootfs ('/') in backup
2022-03-01 15:45:02 INFO: mode failure - some volumes do not support snapshots
2022-03-01 15:45:02 INFO: trying 'suspend' mode instead
2022-03-01 15:45:02 INFO: backup mode: suspend
2022-03-01 15:45:02 INFO: ionice priority: 7
2022-03-01 15:45:02 INFO: CT Name: web
2022-03-01 15:45:02 INFO: including mount point rootfs ('/') in backup
2022-03-01 15:45:02 INFO: temporary directory is on NFS, disabling xattr and acl support, consider configuring a local tmpdir via /etc/vzdump.conf
2022-03-01 15:45:02 INFO: starting first sync /proc/1446/root/ to /mnt/pve/SRVnas/dump/vzdump-lxc-300-2022_03_01-15_45_02.tmp
2022-03-01 22:51:52 ERROR: Backup of VM 300 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' /proc/1446/root//./ /mnt/pve/SRVnas/dump/vzdump-lxc-300-2022_03_01-15_45_02.tmp' failed: interrupted by signal

 

[RedBull]

root@pve:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph: 15.2.15-pve1~bpo10
ceph-fuse: 15.2.15-pve1~bpo10
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-6
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1
root@pve:~#

 

[fiona]

2022-03-01 15:45:02 INFO: temporary directory is on NFS, disabling xattr and acl support, consider configuring a local tmpdir via /etc/vzdump.conf
2022-03-01 15:45:02 INFO: starting first sync /proc/1446/root/ to /mnt/pve/SRVnas/dump/vzdump-lxc-300-2022_03_01-15_45_02.tmp

If you have enough space, you might want to consider configuring a local temporary directory. How big is the container? Did you check the temporary directory if there is progress?

root@pve:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)

Proxmox VE 6.3 is rather old, I'd consider upgrading to at least 6.4. But no guarantees that it will improve this specific problem of course.

 

[RedBull]

If you have enough space, you might want to consider configuring a local temporary directory. How big is the container? Did you check the temporary directory if there is progress?


Proxmox VE 6.3 is rather old, I'd consider upgrading to at least 6.4. But no guarantees that it will improve this specific problem of course.

Thank you very much, how do I enable the folder?

 

[fiona]

You can set the tmpdir option in your /etc/vzdump.conf (by default the backup directory itself is used). If you have multiple nodes, you need to do it on each node.

 

[RedBull]

with LXC off the backup works

INFO: starting new backup job: vzdump 300 --remove 0 --storage SRVnas --mode snapshot --compress zstd --node pve
INFO: Starting Backup of VM 300 (lxc)
INFO: Backup started at 2022-03-12 19:57:22
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: web
INFO: including mount point rootfs ('/') in backup
INFO: creating vzdump archive '/mnt/pve/SRVnas/dump/vzdump-lxc-300-2022_03_12-19_57_22.tar.zst'
INFO: Total bytes written: 1640355840 (1.6GiB, 17MiB/s)
INFO: archive file size: 478MB
INFO: Finished Backup of VM 300 (00:01:42)
INFO: Backup finished at 2022-03-12 19:59:04
INFO: Backup job finished successfully
TASK OK

 

[fiona]

With stop mode backup the tmpdir is not used at all, because everything is backed-up in one go.