[SOLVED] Backup: '/var/lib/vz/tmp_backup' full, how to use other mount point?

le_top

Renowned Member
Sep 6, 2013
42
0
71
PROXMOX VE5.0-33 does not succeed in backing up a virtual machine with a raw disk of 350GB.
That's because during the initial sync, the '/var/lib/vz/tmp_backup' space gets full.

The question is :
How to use a location in '/mnt/bigdisk' for that where the VM is located? Or another technique for efficient backup of this machine?.


The virtual machine is "hosted" in /mnt/bigdisk("big" hard drive), it is currently synced to /var/lib/vz ("small" SSD) for backup (how to change that) and the backup files go to /mnt/bigdisk.

So there are two kinds of spaces on the node: one "small" backed by SSD and one "big" backed by hard drives.

Here is an overview of the relevant mounting points:
Filesystem 1K-blocks Used Available Use% Mounted on
udev 131998344 0 131998344 0% /dev
tmpfs 26403580 141264 26262316 1% /run
/dev/sda1 20026236 2436096 16566192 13% /
tmpfs 132017896 64368 131953528 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 132017896 0 132017896 0% /sys/fs/cgroup
/dev/mapper/pve-data 10190136 37008 9628844 1% /var/lib/vz
vmpool 342241792 128 342241664 1% /vmpool
vmpool/subvol-102-disk-1 33554432 17059200 16495232 51% /vmpool/subvol-102-disk-1
/dev/sdb1 1921279812 581308404 1242322824 32% /mnt/bigdisk
/dev/fuse 30720 36 30684 1% /etc/pve

Here is the transcript (server name changed to example.com for privacy):
108: 2017-10-22 05:12:24 INFO: Starting Backup of VM 108 (lxc)
108: 2017-10-22 05:12:24 INFO: status = running
108: 2017-10-22 05:12:24 INFO: CT Name: example.com
108: 2017-10-22 05:12:24 INFO: mode failure - some volumes do not support snapshots
108: 2017-10-22 05:12:24 INFO: trying 'suspend' mode instead
108: 2017-10-22 05:12:24 INFO: backup mode: suspend
108: 2017-10-22 05:12:24 INFO: ionice priority: 7
108: 2017-10-22 05:12:24 INFO: CT Name: example.com
108: 2017-10-22 05:12:24 INFO: starting first sync /proc/21983/root// to
/var/lib/vz/tmp_backup/vzdumptmp7777
108: 2017-10-22 05:13:34 INFO: rsync: write failed on
"/var/lib/vz/tmp_backup/vzdumptmp7777/root/gcc-4.9.3/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu/bits/stdc++.h.gch/O2g.gch":
No space left on device (28)
108: 2017-10-22 05:13:34 INFO: rsync error: error in file IO (code 11) at
receiver.c(393) [receiver=3.1.2]
108: 2017-10-22 05:13:46 ERROR: Backup of VM 108 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/21983/root///./ /var/lib/vz/tmp_backup/vzdumptmp7777' failed: exit code 11



The VM disk is listed as: bigdisk_ct:108/vm-108-disk-1.raw,size=350G which is on /mnt/bigdisk
 
Last edited:

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!