backup problem with vzdump on proxmox 1.9

[projan]

Hello All,

I'm experiencing some problems with creating a backup of a OPenVZ container on Proxmox VE 1.9 (in order to restore it in VE 3.3)

I'm trying to make a backup from the command line with the following command:

 vzdump 300 --compress --dumpdir /backup/

This is the output I get

INFO: starting new backup job: vzdump 300 --compress --dumpdir /backup/
INFO: Starting Backup of VM 300 (openvz)
INFO: CTID 300 exist unmounted down
INFO: status = CTID 300 exist unmounted down
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: creating archive '/backup/vzdump-openvz-300-2014_12_31-10_40_52.tgz'
INFO: Total bytes written: 10240 (10KiB, 145MiB/s)
INFO: archive file size: 0KB
INFO: Finished Backup of VM 300 (01:21:28)
INFO: Backup job finished successfuly

Even though it says successfull, the archive size is 0KB.
The actual size of the VM is ~850GB. Another VM that was on there with a size of about 200GB succeeded.

First I tried to back it up on a network share, when that didn't worked, I tried to the local disk (output is above). Both should have enough disk space to hold the backup

Does anyone has any idea what causes this or how it can be solved?

 

[m.ardito]

sorry to see nobody has answered...

if you still have the trouble, try posting details about the vm. like, its .conf and its disk/backup storages (storage.conf, fstab, df -h etc), maybe also about the node (pveperf, pveversion -v).

if anything fails, you can manually try to backup all content in the /var/lib/vz/private/<vmid> fodler (IIRC) and then try to restore it back somehow.

also, openvz help forums, may help you to find a way...

Marco

 

[Stewge]

Have you tried dropping the --dumpdir option? The resulting backup should go into /var/lib/vz/dump by default.

I believe you may also require the --tmpdir option for --dumpdir to actually work when using a different storage location (don't quote me on that, since I haven't used the old vzdump in a long time). --tmpdir is the sync directory which is then compressed afterwards. If not optioned it usually ends up being something like ./vzdump-openvz-300-date-time.tar.dat/. You should be able to see this folder get created.

As mentioned above, some more info on the VM would be useful as well.

I've done this very same thing recently with some old VMs from PVE1.8 -> PVE3.3 without issue. However none of mine were anywhere near that big (50-60GB each).