Backup LXC to PBS error 11

yandaxx

New Member
Feb 9, 2021
2
0
1
49
Hello. When backing up a container to PBS about 300Gb in size, error 11 appears. When copying a smaller container, there is no error. The backup to another NFS storage is done normally. Tell me how to fix it?

Code:
INFO: starting new backup job: vzdump 110 --remove 0 --storage PBS-Backup-1 --node pve6-4 --mode suspend
INFO: Starting Backup of VM 110 (lxc)
INFO: Backup started at 2021-02-09 11:36:29
INFO: status = running
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: FSNC-law
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/37162/root/ to /var/tmp/vzdumptmp16624_110
ERROR: Backup of VM 110 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/37162/root//./ /var/tmp/vzdumptmp16624_110' failed: exit code 11
INFO: Failed at 2021-02-09 11:56:06
INFO: Backup job finished with errors
TASK ERROR: job errors

Config LXC

Code:
root@pve6-4:/var/lib/lxc/110# cat ./config
lxc.cgroup.relative = 0
lxc.cgroup.dir.monitor = lxc.monitor/110
lxc.cgroup.dir.container = lxc/110
lxc.cgroup.dir.container.inner = ns
lxc.arch = amd64
lxc.include = /usr/share/lxc/config/debian.common.conf
lxc.include = /usr/share/lxc/config/debian.userns.conf
lxc.seccomp.profile = /usr/share/lxc/config/pve-userns.seccomp
lxc.apparmor.profile = generated
lxc.apparmor.raw = deny mount -> /proc/,
lxc.apparmor.raw = deny mount -> /sys/,
lxc.mount.auto = sys:mixed
lxc.monitor.unshare = 1
lxc.idmap = u 0 100000 65536
lxc.idmap = g 0 100000 65536
lxc.tty.max = 2
lxc.environment = TERM=linux
lxc.uts.name = FSNC-law
lxc.cgroup.memory.limit_in_bytes = 2147483648
lxc.cgroup.memory.memsw.limit_in_bytes = 4294967296
lxc.cgroup.cpu.shares = 1024
lxc.rootfs.path = /var/lib/lxc/110/rootfs
lxc.net.0.type = veth
lxc.net.0.veth.pair = veth110i0
lxc.net.0.hwaddr = 42:D9:6F:B1:8D:E3
lxc.net.0.name = eth0
lxc.net.0.script.up = /usr/share/lxc/lxcnetaddbr
lxc.cgroup.cpuset.cpus = 3,24

Code:
root@pve6-4:~# pct config 110
arch: amd64
cores: 2
description: LAW Container
hostname: FSNC-law
lock: backup
memory: 2048
nameserver: 192.168.100.77
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=42:D9:6F:B1:8D:E3,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: NFS-Datastore:110/vm-110-disk-1.raw,size=500G
searchdomain: 192.168.100.146
swap: 2048
unprivileged: 1
 
Last edited:
Hi,

INFO: starting first sync /proc/37162/root/ to /var/tmp/vzdumptmp16624_110
ERROR: Backup of VM 110 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/37162/root//./ /var/tmp/vzdumptmp16624_110' failed: exit code 11


exit code 11 from rsync normally means that there's no space left on the device to make the temporary copy for your suspend mode backup. As the Container disk is relatively big with its 500 GiB, the suspend mode may not work out here.

You can try setting the tmpdir to a filesystem with more space or try out another backup mode which does not require an intermediated copy
https://pve.proxmox.com/pve-docs/chapter-vzdump.html#_backup_modes
 
Fine. Thank. I have a local storage local-lvm which can be quite used for tmpdir, but how to determine its path to write it into /etc/vzdump.conf
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!