Migrate VS backup lock

[mrmattyboy]

Hi,

I'm new to this forum,

I've installed proxmox 2.1 on a couple of servers and have implemented a backup script. During the script it checks to see if the VM is locked etc.

After doing checks on the VM, to make sure it's Ok to be backed up, it locks the VM. At the moment it locks it as "migrate" (`qm set 102 -lock migrate`)

I was wondering what the differences are between the locks, ie. does the migrate the lock mean that it stops it from being migrated, or does it mean that whilst this lock is in place, it's probably being migrated.

Or do both the locks do the same thing (just lock the VM) and the different names just for convenience?

During my backup, I won't want it either migrating, or, obviously, being backed up by proxmox.

Thanks
Matt

 

[dietmar]

During my backup, I won't want it either migrating, or, obviously, being backed up by proxmox.

I guess you should simply use a backup lock:

# qm set 102 -lock backup

That prevents any other actions.

 

[mrmattyboy]

But what is the difference between the two locks?

Thanks

 

[dietmar]

But what is the difference between the two locks?

One is used for backups, the other is used by migrate. For details, please check the source code yourself.