Backup job of VM/CT fails

G

Gilgamesh

New Member
Jan 11, 2024
10
1
3
When I try to make a backup of that CT it fails. Other backup work normal just not that one. I'm not professional enough make sense out of that ERROR. Does someone has an idea?

INFO: starting new backup job: vzdump 122 --notification-mode auto --compress zstd --notes-template 'Audibookshelf April 2024' --remove 0 --storage Backup2 --node pve --mode snapshot
INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp281683_122 for temporary files
INFO: Starting Backup of VM 122 (lxc)
INFO: Backup started at 2024-04-25 12:59:27
INFO: status = running
INFO: CT Name: audiobookshelf
INFO: including mount point rootfs ('/') in backup
INFO: mode failure - some volumes do not support snapshots
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: audiobookshelf
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/3857244/root/ to /var/tmp/vzdumptmp281683_122
ERROR: Backup of VM 122 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/3857244/root//./ /var/tmp/vzdumptmp281683_122' failed: exit code 11
INFO: Failed at 2024-04-25 13:16:37
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors

Proxmox version 8.1.10
 
could you also post the container config? anything particular about that container?
 
Why is "/var/tmp" a CIFS mount?

> INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp281683_122 for temporary files

I would try to use a unix filesystem there (xfs, ext4, zfxs, nfs).
 
It's on a TrueNAS drive. There is no issue with 15 other LXC backup files on that Cifs mount. It's just that single container.
dietmar said:
Why is "/var/tmp" a CIFS mount?

> INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp281683_122 for temporary files

I would try to use a unix filesystem there (xfs, ext4, zfxs, nfs).
Click to expand...
 
fabian said:
"pct config <ID>"
Click to expand...
root@pve:~# pct config 122
arch: amd64
cores: 2
description: <div align='center'><a href='https%3A//Helper-Scripts.com' target='_blank' rel='noopener noreferrer'><img src='https%3A//raw.githubusercontent.com/tteck/Proxmox/main/misc/images/logo-81x112.png'/></a>%0A%0A # audiobookshelf LXC%0A%0A <a href='https%3A//ko-fi.com/D1D7EP4GF'><img src='https%3A//img.shields.io/badge/&#x2615;-Buy me a coffee-blue' /></a>%0A </div>%0A
features: keyctl=1,nesting=1
hostname: audiobookshelf
memory: 2048
net1: name=eth1,bridge=vmbr2,firewall=1,hwaddr=BC:24:11:E2:AF:94,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: Paperless:122/vm-122-disk-0.raw,size=140G
swap: 512
tags: proxmox-helper-scripts
unprivileged: 1
 
I have no idea what that script does inside the container, but you can try running rsync manually (you might need to replace the PID if you've rebooted/migrated the container in the meantime (pct status 122 --verbose gives you the current PID, in the example below it was 3857244):

Code: 
mkdir /var/tmp/test
rsync -vv --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/3857244/root//./ /var/tmp/test
rm -rf /var/tmp/test
 
You must log in or register to reply here.
Top Bottom