Proxmox Backup Server po

M

Michal6040

Member
May 6, 2022
20
0
6
Hello, when backing up, LXC displays this error after a while.
The deposit is in the form of snapschot. this does not happen with other VM/LXCs.

Thanks for help


Task viewer: VM/CT 149 - Backup


OutputStatus

Stop
INFO: starting new backup job: vzdump 149 --mode snapshot --notes-template '{{guestname}}' --node PROX01-HP --storage Proxmox-Backup-Server --remove 0
INFO: Starting Backup of VM 149 (lxc)
INFO: Backup started at 2022-10-20 07:10:15
INFO: status = running
INFO: CT Name: WebMVSR-Live
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: WebMVSR-Live
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/21139/root/ to /var/tmp/vzdumptmp1124907_149
ERROR: Backup of VM 149 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/21139/root//./ /var/tmp/vzdumptmp1124907_149' failed: exit code 10
INFO: Failed at 2022-10-20 07:21:42
INFO: Backup job finished with errors
TASK ERROR: job errors
Click to expand...
 
Hello,

Can you please post the config of 149 CT; pct config 149 and the output of cat /etc/pve/storage.cfg?
 
hi,
could you also print the output of systemctl list-unit-files |grep rsync and dmesg | grep rsync
 
Moayad said:
Hello,

Can you please post the config of 149 CT; pct config 149 and the output of cat /etc/pve/storage.cfg?
Click to expand...
Here you go
root@PROX01-HP:~# pct config 149
arch: amd64
cores: 4
features: nesting=1
hostname: WebMVSR-Live
memory: 4096
nameserver: 1.1.1.1
net0: name=eth0,bridge=vmbr1,firewall=1,gw=192.168.159.254,hwaddr=2A:D7:70:4C:E9:60,ip=192.168.159.199/24,type=veth
onboot: 1
ostype: ubuntu
protection: 1
rootfs: HDD2:vm-149-disk-0,size=150G
searchdomain: 192.168.159.254
swap: 512
unprivileged: 1
Click to expand...
root@PROX01-HP:~# cat /etc/pve/storage.cfg
lvm: HDD1
vgname hdd1
content images,rootdir
shared 0

lvm: HDD2
vgname pve
content images,rootdir
shared 0

dir: local
path /var/lib/vz
content iso,vztmpl
prune-backups keep-all=1
shared 0

nfs: QNAP-Backup-NAS
export /Proxmox-Backup-NAS
path /mnt/pve/QNAP-Backup-NAS
server 192.168.158.43
content backup
prune-backups keep-all=1

pbs: Proxmox-Backup-Server
datastore Proxmox-Backup-Server
server 192.168.158.55
content backup
fingerprint 19:cc:17:92:83:a7:ca:01:46:27:d8:37:03:bf:10:98:a2:97:24:56:ac:63:24:93:26:9c:a9:97:ac:d4:fe:cf
prune-backups keep-all=1
username proxmox-backup-server@pbs
Click to expand...
 
Last edited:
Just to clarify, when I choose the stop backup type, the backup goes through without a problem The problem is only a snapshot backup.
 
Here you go :)

root@PROX01-HP:~# df -h /var/tmp
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-root 94G 42G 48G 47% /
 
Hi,

Thank you for the output, can you try to change the "tmpdir:" path in the /etc/vzdump.conf config file? You can set the "tmpdir" to another disk storage, i.e, not the root storage and test the backup with snapshot again.
 
this is what my configuration file/etc/vzdump.conf looks like, what path should I change it to?

GNU nano 5.4 /etc/vzdump.conf
# vzdump default settings

#tmpdir: DIR
#dumpdir: DIR
#storage: STORAGE_ID
#mode: snapshot|suspend|stop
#bwlimit: KBPS
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
#stdexcludes: BOOLEAN
#mailto: ADDRESSLIST
#prune-backups: keep-INTERVAL=N[,...]
#script: FILENAME
#exclude-path: PATHLIST
#pigz: N
#notes-template: {{guestname}}
 
I already know where the local storage problem was, it doesn't have LXC capacity, it takes over 150Gb
think I can delete the contents of /var/tmp there is some data there
 
Last edited:
You must log in or register to reply here.
Top Bottom