by jllotz1 » Wed Jun 29, 2016 10:03 pm people like this post
I have about 225 VM's that I need to migrate from older hardware/SAN managed by a 5.1 vCenter, to new hardware/SAN managed by a version 6 vCenter. The two environments are in the same physical location and have basic network connectivity between them, but otherwise are totally separate. I have looked into different options to move the VM's, but I can't seem to come up with a good method for moving that many VM's relatively efficiently. What are my options here? We own Veeam Backup and Replication - could that be utilized?
by ashman70 » Wed Jun 29, 2016 11:12 pm people like this post
I just used veeam quick migration to move two vm's from an old host to a new one, it was easy peasy. Now while you are moving far more vm's I don't see why you couldn't also utilize quick migration, you should look into it.
by jllotz1 » Thu Jun 30, 2016 4:58 pm people like this post
Thanks for the great info. I'm not familiar with quick migration. Can you briefly explain how it is different from veeam replication? Also, is it a separate product, or is it a feature in version 9? Thanks.
by larry » Thu Jun 30, 2016 9:19 pm people like this post
When I moved from ESX 5 to 6 I also switch ESX hardware and SAN. I connected my old SAN to my ESX6 setup while leaving it connected to the ESX 5 setup. Had the VMs running on the old setup and then just import into the new 6 Vcenter. During the week, I moved the vm from the old san to the new san. I used Veeam to replicate live then during off hours just down live VM, replicate again (takes seconds as only change from minutes ago) bring up replica. Some VMs I just vmotion over live. The hardest part is that the vms get a new ID on the new virtual center so Veeams jobs need to be recreated or the size of backups will be double. I took the time to move VMs to data stores that had set RTO/RPO which makes other planning much easier. I also backup by datastore now so my new Veeam jobs just backup a whole datastore. My new SANs also replicated off site so this setup allowed a move controlled move. You need to pull your esx 5 host into your new vcenter to vmonition live but I did one host at a time over a weeks time. The other issue I ran into was licensing as Veeam and ESX is per CPU. Veeam will send you a temp lic if your nice to them VMware allows you to use the trial license for 30 days that has no CPU limit during your migration. I also needed extra space and tapes for backups for that week. Every move requires a full backups as the VM id changed, new SAN all new change blocks. It all went good with no down time during production time, a lot of waiting.