Hi
I think I have this one figured out - please advise if you could fix this in vzdump.
The situation:
VM 72002 is a KVM-VE and is set to not boot anyways, but just sit there until an admin manually kicks it to boot manually.
the vzdump backup runs and everything is fine:
but when vzdump runs again the next day it fails like this:
it seems the "qm unlock 72002" is not done after vzdump finishes, manually unlocking works for the next backup.
But this seems only to happen with this (relatively big) VE that isn't even running during backup.
Please advise,
hk
I think I have this one figured out - please advise if you could fix this in vzdump.
The situation:
VM 72002 is a KVM-VE and is set to not boot anyways, but just sit there until an admin manually kicks it to boot manually.
the vzdump backup runs and everything is fine:
| 72002 | ag-sbs-2008 | OK | 05:34:01 | 46.19GB | /mnt/pve/store02_kXX_backup/vzdump-qemu-72002-2011_11_11-21_45_01.tgz |
but when vzdump runs again the next day it fails like this:
| 72002 | VM 72002 | FAILED | 00:00:01 | command 'qm set 72002 --lock backup' failed with exit code 2 |
it seems the "qm unlock 72002" is not done after vzdump finishes, manually unlocking works for the next backup.
But this seems only to happen with this (relatively big) VE that isn't even running during backup.
Please advise,
hk