I've never really used the backup functionality in Proxmox before, as I prefer to use rsync to copy all files to a backup machine. I still do this for Linux containers.
However after upgrading to 2.3 and after some server problems I've been backing up a Windows VM to NFS storage. (every night, keeping 2 backups).
I've already had to use one backup image because the backup process itself failed and completely messed up the Windows filesystem (but I'll leave that one for now).
Last night the backup failed part way through and the VM was stopped. This time, Windows did restart correctly. The VM has been running fine for 3 years and uses a .raw format file. I've now had to stop the automatic backup as it's less than useful.
Here's the backup log:
vzdump 103 --quiet 1 --mailto <me> --mode snapshot --compress lzo --storage arthur-backup --node ivmhost1
103: Mar 14 02:00:02 INFO: Starting Backup of VM 103 (qemu)
103: Mar 14 02:00:02 INFO: status = running
103: Mar 14 02:00:03 INFO: backup mode: snapshot
103: Mar 14 02:00:03 INFO: ionice priority: 7
103: Mar 14 02:00:03 INFO: creating archive '/mnt/pve/arthur-backup/dump/vzdump-qemu-103-2013_03_14-02_00_01.vma.lzo'
103: Mar 14 02:00:03 INFO: started backup task '9cd11bc4-85b9-411b-94a4-8242cae85e37'
103: Mar 14 02:00:06 INFO: status: 0% (157679616/21474836480), sparse 0% (806912), duration 3, 52/52 MB/s
103: Mar 14 02:00:09 INFO: status: 1% (284033024/21474836480), sparse 0% (1134592), duration 6, 42/42 MB/s
103: Mar 14 02:00:12 INFO: status: 2% (440926208/21474836480), sparse 0% (3878912), duration 9, 52/51 MB/s
103: Mar 14 02:00:16 INFO: status: 3% (663093248/21474836480), sparse 0% (5021696), duration 13, 55/55 MB/s
103: Mar 14 02:00:20 INFO: status: 4% (890503168/21474836480), sparse 0% (7729152), duration 17, 56/56 MB/s
103: Mar 14 02:00:25 INFO: status: 5% (1083703296/21474836480), sparse 0% (11583488), duration 22, 38/37 MB/s
103: Mar 14 02:01:19 ERROR: VM 103 not running
103: Mar 14 02:01:19 INFO: aborting backup job
103: Mar 14 02:01:19 ERROR: VM 103 not running
103: Mar 14 02:01:20 ERROR: Backup of VM 103 failed - VM 103 not running
However after upgrading to 2.3 and after some server problems I've been backing up a Windows VM to NFS storage. (every night, keeping 2 backups).
I've already had to use one backup image because the backup process itself failed and completely messed up the Windows filesystem (but I'll leave that one for now).
Last night the backup failed part way through and the VM was stopped. This time, Windows did restart correctly. The VM has been running fine for 3 years and uses a .raw format file. I've now had to stop the automatic backup as it's less than useful.
Here's the backup log:
vzdump 103 --quiet 1 --mailto <me> --mode snapshot --compress lzo --storage arthur-backup --node ivmhost1
103: Mar 14 02:00:02 INFO: Starting Backup of VM 103 (qemu)
103: Mar 14 02:00:02 INFO: status = running
103: Mar 14 02:00:03 INFO: backup mode: snapshot
103: Mar 14 02:00:03 INFO: ionice priority: 7
103: Mar 14 02:00:03 INFO: creating archive '/mnt/pve/arthur-backup/dump/vzdump-qemu-103-2013_03_14-02_00_01.vma.lzo'
103: Mar 14 02:00:03 INFO: started backup task '9cd11bc4-85b9-411b-94a4-8242cae85e37'
103: Mar 14 02:00:06 INFO: status: 0% (157679616/21474836480), sparse 0% (806912), duration 3, 52/52 MB/s
103: Mar 14 02:00:09 INFO: status: 1% (284033024/21474836480), sparse 0% (1134592), duration 6, 42/42 MB/s
103: Mar 14 02:00:12 INFO: status: 2% (440926208/21474836480), sparse 0% (3878912), duration 9, 52/51 MB/s
103: Mar 14 02:00:16 INFO: status: 3% (663093248/21474836480), sparse 0% (5021696), duration 13, 55/55 MB/s
103: Mar 14 02:00:20 INFO: status: 4% (890503168/21474836480), sparse 0% (7729152), duration 17, 56/56 MB/s
103: Mar 14 02:00:25 INFO: status: 5% (1083703296/21474836480), sparse 0% (11583488), duration 22, 38/37 MB/s
103: Mar 14 02:01:19 ERROR: VM 103 not running
103: Mar 14 02:01:19 INFO: aborting backup job
103: Mar 14 02:01:19 ERROR: VM 103 not running
103: Mar 14 02:01:20 ERROR: Backup of VM 103 failed - VM 103 not running