Migration of VMs from Proxmox A to Proxmox B in same cluster: Target Storage does not show up

[Scampicfx]

Hey there,

- Proxmox Server A is connected to a dedicated NFS storage A which is only available for Proxmox Server A
- Proxmox Server B is connected to a dedicated NFS storage B which is only available for Proxmox Server B

I created a cluster so that both Server A and Server B can get managed from the same web interface.

My goal is to migrate VMs from A to B.

The problem is: When right-clicking on a VM and selecting "Migrate", I do not have any option to select Target Storage. The drop down menu simply isn't there.
I tried to do a migration from A to B with following VMs:
- A VM on Server A, which is stored on local disk
- A VM on Server A, which is stored on NFS storage

Both VMs have the same problem: I can't migrate them to Server B because the Target Storage Dropdown Menu is missing.

As mentioned, both Server have their unique NFS storage which isn't shared between the hosts.

I am happy to use other methods of migrating the VMs as well. I thought doing it with "right click -> migrate" might be easy. But it looks like it is more complicated.

Any help would be appreciated! Thank you so much!

Cheers,
Chris

 

[UdoB]

The problem is: When right-clicking on a VM and selecting "Migrate", I do not have any option to select Target Storage.

Is the VM up and running? The offer of a "Target storage" in the "Migrate VM" dialog is only given for running VMs.

 

[Scampicfx]

Hey,
I tried both: VMs up and VMs offline.
Since I couldn't solve this issue until now I will try to do backup/restore method.

 

[Scampicfx]

If anybody else comes here: My solution was to do Backup -> Restore.

 

[waltar]

Why not just allow export on nfs storage A to host B and on storage B host A also ?!?

 

[Scampicfx]

Hey waltar, could you quickly describe what you mean by "allow export"?

 

[waltar]

Proxmox Server A is connected to a dedicated NFS storage A

So inside your dedicated storage there is an nfs export defined (mostly written into /etc/exports in linux based os) but I think was done by gui of it which allows access of server A. That should be extended to allow server B also.
Same for dedicated storage B is configured for access of server B which shoud be extended for server A also.

 

[fba]

Shouldn't this work on CLI withqm migrate <vmId> <destHost> -targetstorage <targetStorage> anyway? If vm is running then add -online
like asked and described here: https://forum.proxmox.com/threads/move-vm-to-another-node-with-different-storage-name.55798/

 

[garigon]

Same issue. We are running Proxomx 8.3.5 on 6 nodes with Ceph, and each one has a local storage (local-lvm). We isolate the issue as follow.
If and only if the vm's disk is allocated on local storage (e.g.: local-lvm or local-zfs) when you select Migrate the Target storage option does show up.

But... if the vm's disk is allocated on a distributed storage (like Ceph) when we select Migrate, Target storage option does not show up.

Of course, in both cases vm's are up and running due Target storage option is defined for Online Migration.

Somebody has an explanation. Don't think this issue is a bug in the GUI. May be there is a border condition or some scenario that we can't figure up for this behavior on the GUI (on Cli with qm migrate always target storage is available).


Thanks in advance.

P.D: For Scampicfx. You also can use this. In VM's Hardware ----> select hard disk and then use Disk Action option and then Move Storage. This method can be used with vm's up and running. It isn't easy as Migrate with target storage option available, but it works.