I am trying to do a live migration of Virtual machines running on vSphere cluster 5.1U1 to standalone ESXi 6.7. I tried using vmware converter however stuck with SSL error
SSL exception: error:140000DB:SSL routines:SSL routines:short read
Has anyone experienced this situation and would please suggest an alternate way to bypass this error.
Cheers
There will be no live migration possible (if you mean vMotion) between those two versions. Also, VMware Converter isn't probably the best tool for this job. You can simply move that VM on some form of storage from source to destination, or use a third party tool (depending on your license level) to do this.
By moving VM on some form of storage, you mean by powering off? .. What is the name of the third party tool you are referring to??
Thanks,
Yes, you will have to power off regardless. There are tools such as Veeam which can do a quick migration.
Our management has just decided to replace existing backups system with Veeam. Will try that once procured and setup.. With Quick migration, it would be live though?
Cheers..
No, as I said, going from such an old version you cannot do a live migration. You must take an outage.
Hello,
I prefer to use replication (and i prefer to use veeam backup & replication). And replicate VMs from old to new and then do a Planned Failover.
Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.
Cheers,
VCIX6-NV|VCP-NV|VCP-DC|
Thanks Hassan. Please share any article which explain steps on doing this.
Do make sure the Guest OS is compatible with ESXi 6.7:
Hello,
Kindly start with the following: https://www.veeam.com/blog/starting-with-vmware-vm-replication-using-veeam-availability-suite.html
How to start with VMware VM replication using Veeam
Please consider marking this answer "CORRECT" or "Helpful" if you think your question have been answered correctly.
Cheers,
VCIX6-NV|VCP-NV|VCP-DC|
Thanks Hasan. I found doing migration using Veeam migration tool easier. It's easier than doing replication as both source and destination are within same datacenter but on new hardware. Comments please?