KVM backups failing

[ERS]

Well, backing up my kvm machines seems to be failing.

This is a standard instalation (straight from the iso onto a HW RAID 5 array), as can be confirmed by:

 vgdisplay
  --- Volume group ---
  VG Name               pve
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  1297
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               1.82 TB
  PE Size               4.00 MB
  Total PE              476703
  Alloc PE / Size       475680 / 1.81 TB
  Free  PE / Size       1023 / 4.00 GB
  VG UUID               TdsR7c-9Bps-Qh73-godO-W0Ta-Yjb3-FU2Tt4

I have a simple setup for the backups (full backups everyday at 4am, then I just incude those files in the main backup policy), ans the error that it started outputing is:

201: Jul 13 03:18:58 INFO: Starting Backup of VM 201 (qemu)
201: Jul 13 03:18:58 INFO: status = running
201: Jul 13 03:18:58 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap')
201: Jul 13 03:18:59 INFO:   Logical volume "vzsnap" created
201: Jul 13 03:18:59 INFO: mounting lvm snapshot
201: Jul 13 03:18:59 INFO: creating archive '/cronus-backup/vzdump-201.dat' (/mnt/vzsnap/images/201)
201: Jul 13 03:18:59 INFO: qemu-server.conf
201: Jul 13 03:18:59 INFO: vm-201-disk.qcow2
201: Jul 13 04:46:42 INFO: 45794361344 B 42.6 GB 5263.2 s (1:27 h) 8700865 B/s 8.30 MB/s
201: Jul 13 04:46:42 INFO: write: No space left on device
201: Jul 13 04:46:44 INFO:   Logical volume "vzsnap" successfully removed
201: [COLOR=red]Jul 13 04:47:41 ERROR: Backup of VM 201 failed - command '(tar cvzpf - -C '/mnt/vzsnap/images/201' --totals --sparse --numeric-owner --ignore-failed-read qemu-server.conf vm-201-disk.qcow2|cstream -t 10485760 >/cronus-backup/vzdump-201.dat)' failed with exit code 2
[/COLOR]

Thanks in advance for any help you may provide me.

 

[dietmar]

201: Jul 13 04:46:42 INFO: write: No space left on device

Seem you do not have enough spave on /var/tmp? You can use the --tmpdir option of vzdump to setup another directory to store temporary files.

- Dietmar

 

[ERS]

Isn't vzdump used only for OpenVZ machines? From the log, it appears the backup is just a tarball of the kvm/qemu image...

 df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/pve/root          95G   52G   38G  58% /
tmpfs                 3.9G     0  3.9G   0% /lib/init/rw
udev                   10M   48K   10M   1% /dev
tmpfs                 3.9G     0  3.9G   0% /dev/shm
/dev/mapper/pve-data  1.7T  127G  1.6T   8% /var/lib/vz
/dev/sda1             496M   84M  387M  18% /boot

# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
/dev/sda1 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

Still, while I was compoosing this post, I noticed I'm backing everything up to /cronus-backups/, which is mounted on /dev/pve/root, and doesn't have enough space. Might be it... if so, sorry for not noticing and wasting your time, and thank you for your help. Will post update for this later.

 

[tom]

Isn't vzdump used only for OpenVZ machines? From the log, it appears the backup is just a tarball of the kvm/qemu image...

vzdump is used for KVM and OpenVZ,
see http://pve.proxmox.com/wiki/Backup_-_Restore_-_Live_Migration

 

[ERS]

Thanks for the info, you learn something new everyday

The problem I had was that I was using pve-root as backup location, so of course the backups stopped due to lack of space. Should have noticed it before, really. Sorry for the trouble and thanks.