how can a snapshot backup become unusable?

[m.ardito]

Hi,
i run a 1.5 2.6.18 pve install. (pveversion -v appended later)

today i tried restoring the "last night" backu to another test pve server (running 1.7 2.6.18, identical hardware as the 1.5)

well, the vm did not start, because... pve saw no disk! even booting from a livecd appeared the 8 gb disk was "not allocated" to gparted...

then i stopped the (running) vm and restarted: all ok, vm running.
so i stopped the vm, backed it up on 1.5 and restored that file to 1.7: all ok, vm running...

so, it should have been the night backup that failed somehow... but what could have caused this? i restored other vm, from the same backup job and pve server, and restoring those other files went ok. just this one vm failed, and had "not allocated" disk...

what could have happened? how can one test automatically if "last night" backup is not good?

Marco

proxmox1:~# pveversion -v
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5

 

[tom]

any log from the failed backup?

btw, you run an outdated system, upgrade to 1.7 (you can keep the 2.6.18er Kernel branch)

 

[m.ardito]

i am just verifying vms compatibility on the newer server, then i will reate a cluster (both on 1.7)

here the "failed" log:

Jan 15 04:12:07 INFO: Starting Backup of VM 104 (qemu)
Jan 15 04:12:07 INFO: running
Jan 15 04:12:07 INFO: status = running
Jan 15 04:12:07 INFO: backup mode: snapshot
Jan 15 04:12:07 INFO: bandwidth limit: 10240 KB/s
Jan 15 04:12:07 INFO: Logical volume "vzsnap-proxmox1-0" created
Jan 15 04:12:07 INFO: creating archive '/mnt/pve/vm_backup/vzdump-qemu-104-2011_01_15-04_12_07.tgz'
Jan 15 04:12:07 INFO: adding '/mnt/pve/vm_backup/vzdump-qemu-104-2011_01_15-04_12_07.tmp/qemu-server.conf' to archive ('qemu-server.conf')
Jan 15 04:12:07 INFO: adding '/dev/pve_vm_disks/vzsnap-proxmox1-0' to archive ('vm-disk-ide0.raw')
Jan 15 04:20:43 INFO: Total bytes written: 5011621888 (9.26 MiB/s)
Jan 15 04:20:43 INFO: archive file size: 2.18GB
Jan 15 04:20:43 INFO: delete old backup '/mnt/pve/vm_backup/vzdump-qemu-104-2011_01_14-04_12_10.tgz'
Jan 15 04:20:50 INFO: Logical volume "vzsnap-proxmox1-0" successfully removed
Jan 15 04:20:50 INFO: Finished Backup of VM 104 (00:08:43)

and here the "working" backup (this timerun backup manually and stopped the vm, the usual night backup use snapshot mode for all vms)

Jan 17 15:14:43 INFO: Starting Backup of VM 104 (qemu)
Jan 17 15:14:43 INFO: stopped
Jan 17 15:14:43 INFO: status = stopped
Jan 17 15:14:44 INFO: backup mode: stop
Jan 17 15:14:44 INFO: bandwidth limit: 10240 KB/s
Jan 17 15:14:44 INFO: creating archive '/mnt/pve/vm_backup/vzdump-qemu-104-2011_01_17-15_14_43.tgz'
Jan 17 15:14:44 INFO: adding '/mnt/pve/vm_backup/vzdump-qemu-104-2011_01_17-15_14_43.tmp/qemu-server.conf' to archive ('qemu-server.conf')
Jan 17 15:14:44 INFO: adding '/dev/pve_vm_disks/vm-104-disk-1' to archive ('vm-disk-ide0.raw')
Jan 17 15:23:27 INFO: Total bytes written: 5013050880 (9.14 MiB/s)
Jan 17 15:23:28 INFO: archive file size: 2.18GB
Jan 17 15:23:28 INFO: Finished Backup of VM 104 (00:08:45)