VM not starting after backup failed- Start and then stop

[Yan Gilchenok]

I have been battling a new problem. After setting up a backup and scheduling it, After I shut down a VM (2008 server), I cannot start it.

Part of the symptom is that I cannot modify VM config.
Attemting to change settings (from gui) gives me the:
Error: unable to apply VM settings, command failed: /usr/bin/ssh -n -o BatchMode=yes ...IP..../usr/sbin/qm set 200 -- name Server4 - description ...

It seems as though after backup failed, the MV locked up. Here is the backup error as well. Note VMID 200.

200 VM 200 FAILED 00:00:00 command 'qm set 200 --lock backup' failed with exit code 255

Suggestions welcome!!!

Thanks,
Yan

 

[Yan Gilchenok]

Found the answer. I should have looked more closely first..
qm unlock 101

How backup locked the vm is another question...
I have a cluster of two 1.9s. Master is configured with a backup to VZdump.. Node lists the directory, but is read only...

Now, I delete the master backup and recreated a different backup directory.. Strange... Both storage locations show not empty through https and the old directory still there. SSH to folder confirms that there are no snapshots listed.

Is there a tutorial on setting up backups so they do not lock VMs? Obviously I am missing something..

Pardon, but I have to start somewhere,
Signed:Newbie

 

[dietmar]

Is there a tutorial on setting up backups so they do not lock VMs? Obviously I am missing something..

Backups always lock the VM, but normally unlocks when finished - maybe a backup was aborted somehow?