You could disconnect the hosts from your old vCenter, connect them to the new vCenter and vMotion the VMs across to the new hosts and storage?
If you can afford to power off the VMs, you could use SCP to move the files to the new datastore and then register the VMs in the new vCenter. (VMware Knowledge Base , http://www.vmwarearena.com/how-to-copy-files-between-esxi-hosts-using-scp-command/ ). Veeam's FastSCP may be an even better option.
The upside is that SCP should alleviate using NFC(*) which can be a bottleneck in case of mass migrations. Both Converter and vMotion use NFC. Not sure about HCX (mentioned in another post), but its documentation reads "This service uses VMware vSphere Replication protocol to move virtual machines in parallel between HCX enabled sites". If, in addition to VR protocol, it uses also VR server, it uses NFC too at the final stage when it writes to the datastore.
Disclaimer: The above is more of a speculation, not empirically proven. I haven't actually done mass migration with scp. But you may want to consider it and do some experiments.
One more note: If you use Converter, you can do incremental cloning for Windows machines only, not for Linux.
(*) Network File Copy, VMware's internal protocol for writing to virtual disks.
if you cant connect the old storage to the new hosts - can you connect the new storage to the old hosts ? which storage protocol do you use in both cases ?
I can't do it because i have ESXi 5.0, and cannot be accepted by Vcenter 6.7. i need at least to upgrade it to 6.0
this is a good solution but i am looking for somthing to take it by one strick
I am presenting my storage from an SVC server ( IBM SAN Volume Controller ) and the ESXi are connected with HBA adapters to the SAN switch.
And yes this is a good solution that i will try tomorrow.
Thank you Plamen,
You have showed alot of stuf that i wasn't making a consider of, and your solution is perfect for VMs that are Down as you said. i already noted this solution to be my last escape.
Thank you again
if you can connect the new storage to old hosts (one LUN is enough) then you have an easy way:
- storage vmotion vm in old cluster to new storage
- shutdown vm
- unregister vm from old vcenter
- register to new vcenter
- startup vm (downtime < 5 min)
- proceed with next vm
You are welcome.
I am glad to have been useful.