8.3 qm remote-migrate

K

kellogs

Active Member
Proxmox Subscriber
May 14, 2024
233
35
28
Hello

Source VM in a stopped state but config locked (migrate) even tho it has completed successfully.

In this case do we do qm unlock vmid? and is this by design for it to be locked after successful remote migration?

Thanks!
 
Hi,
kellogs said:
Source VM in a stopped state but config locked (migrate) even tho it has completed successfully.
In this case do we do qm unlock vmid? and is this by design for it to be locked after successful remote migration?
Click to expand...
yes, that is the usual behavior if you don't specify the --delete 1 option (EDIT: this will automatically delete the original VM after successful migration!). Yes, you need to unlock the VM before doing something else.
 
Last edited:
fiona said:
yes, that is the usual behavior if you don't specify the --delete 1 option.
Click to expand...
Just to clarify (so the OP does not misunderstand): The --delete 1 option will delete the original VM and related data after successful migration.

AFAIK there is no way todo a qm remote-copy (which is probably what the OP wanted). I know this is something that users could find useful. Doing a qm remote-migrate & then unlocking the original - amounts to the same.
 
  • Like
Reactions: fiona
Thank you @fiona and @gfngfn256 information. I am totally in love with this remote-migrate feature and essentially could build a DR solution of some sort.

I wonder if there is any way have near time async using this tool to a remote cluster.
 
You must log in or register to reply here.
Top Bottom