[SOLVED] localtmpdir for PBS backups?

N

nakaori

New Member
Aug 6, 2020
17
1
3
37
Hi,

I am testing PBS for a week now and am very satisfied with it. I am currently backing up 2 PVEs to one PBS. One of them is very low powered and has only so much disk space. When I try to back up a larger machine it fails after filling up local storage. Can I somehow set up a localtmpdir for backups using the new backup-client as it seems that vzdump.conf doesn't affect this.


Thanks!
 
I assume you are talking about container backups? which mode? can you post a full log of such a failing backup job?
 
hi fabian,

thanks for your quick response. You're right. It's a container. Here's the output of one of them:

Code: 
()
INFO: starting new backup job: vzdump 110 --node haruka --storage <redacted> --remove 0 --mode snapshot
INFO: Starting Backup of VM 110 (lxc)
INFO: Backup started at 2020-08-06 05:55:37
INFO: status = running
INFO: CT Name: docker
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: docker
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/2209/root// to /var/tmp/vzdumptmp31383
INFO: rsync: write failed on "/var/tmp/vzdumptmp31383/var/lib/docker/vfs/dir/ca3c87ae5efb1dca280f5e7002d95b168e0c2acf3d3d7527a4a023da36a793bd/tmp/cps.vWkaD2": No space left on device (28)
INFO: rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]
ERROR: Backup of VM 110 failed - command 'rsync --stats -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/2209/root///./ /var/tmp/vzdumptmp31383' failed: exit code 11
INFO: Failed at 2020-08-06 06:52:30
INFO: Backup job finished with errors
TASK ERROR: job errors
 
yes, suspend mode backup needs to copy all the files to a tmp dir on the PVE host. either configure your container to support snapshot mode, or use stop mode, or set 'tmpdir' in /etc/vzdump.conf to somewhere with more space.
 
fabian said:
yes, suspend mode backup needs to copy all the files to a tmp dir on the PVE host. either configure your container to support snapshot mode, or use stop mode, or set 'tmpdir' in /etc/vzdump.conf to somewhere with more space.
Click to expand...


Hi Fabian,


i used snapshot mode in this example.

INFO: starting new backup job: vzdump 110 --node haruka --storage <redacted> --remove 0 --mode snapshot


Also the tmpdir actually IS my issue. The backup process seems to ignore the tmpdir option.
 
Same issue here: ERROR: Backup of VM 105 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/4181/root//./ /var/tmp/vzdumptmp48360' failed: exit code 11

client version: 0.8.13

Backup Server 0.8-13
 
please post the full backup log and pveversion -v output
 
Code: 
proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-5
pve-kernel-helper: 6.2-5
pve-kernel-5.4.55-1-pve: 5.4.55-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.4.134-1-pve: 4.4.134-112
pve-kernel-4.4.98-5-pve: 4.4.98-105
pve-kernel-4.4.49-1-pve: 4.4.49-86
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.8-1-pve: 4.4.8-52
ceph-fuse: 12.2.13-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.1-2
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
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-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-11
pve-cluster: 6.1-8
pve-container: 3.1-12
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-2
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-12
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-11
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1



Code: 
[...]

INFO: Starting Backup of VM 202 (lxc)
INFO: Backup started at 2020-08-31 06:20:05
INFO: status = running
INFO: CT Name: xxxxxxxx-03
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: xxxxxxxx-03
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/14122/root/ to /var/tmp/vzdumptmp37161
ERROR: Backup of VM 202 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/14122/root//./ /var/tmp/vzdumptmp37161' failed: exit code 11
INFO: Failed at 2020-08-31 06:21:07
INFO: Starting Backup of VM 240 (lxc)
INFO: Backup started at 2020-08-31 06:21:07
INFO: status = running
INFO: CT Name: xxxxxxxxx-b2c
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: xxxxxxxxxxxx-b2c
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/14444/root/ to /var/tmp/vzdumptmp37161
ERROR: Backup of VM 240 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/14444/root//./ /var/tmp/vzdumptmp37161' failed: exit code 11
INFO: Failed at 2020-08-31 06:22:28
INFO: Starting Backup of VM 301 (qemu)
INFO: Backup started at 2020-08-31 06:22:28
INFO: status = running
INFO: VM Name: chr-01
INFO: include disk 'virtio0' 'vms:301/vm-301-disk-1.qcow2' 128M
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/301/2020-08-31T04:22:28Z'
INFO: enabling encryption
INFO: started backup task '22ec8f1f-185f-4c69-a412-ff80ef366cb3'
INFO: resuming VM again
INFO: using fast incremental mode (dirty-bitmap), 56.0 MiB dirty of 128.0 MiB total
INFO: status: 100% (56.0 MiB of 56.0 MiB), duration 2, read: 28.0 MiB/s, write: 28.0 MiB/s
INFO: backup was done incrementally, reused 72.00 MiB (56%)
INFO: transferred 56.00 MiB in 2 seconds (28.0 MiB/s)
INFO: Finished Backup of VM 301 (00:00:03)
INFO: Backup finished at 2020-08-31 06:22:31
INFO: Backup job finished with errors

TASK ERROR: job errors
 
pve-manager has not been bumped yes with the fix included.. pve-manager >= 6.2-12 should contain the fix once it hits the repositories.
 
bumped, should move to the public repos in the next few days..
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom