- This topic has 6 replies, 1 voice, and was last updated June 6, 2022 by .
vCenter vMotion
You must be logged in to create new topics.
Click here to login
How does Zerto handle vMotion between vCenter instances?
Hey Travis,
The logical boundary of protection in Zerto is anything within a vCenter, as one ZVM is required per vCenter. If you vMotion a VM to another vCenter then it will break the protection group and the VM will no longer be protected.
You can however vMotion/Storage vMotion a VM between any datacenter, cluster or host within a vCenter without any interruption to the replication as long as a VRA is installed and running on the target host.
Your 2 options are therefore:
Which of the above would work best for you? Please can you share a bit more about your use case for vMotion between vCenters? Many thanks,
Joshua
Hey Travis,
In this configuration I’d recommend having having each remote office registered to a central vCenter as a separate datacenter object.
You should then deploy VRAs to the hosts in each remote office in a separate VRA group, to indicate they are in a separate physical location.
With this configuration you can then create protection groups within the vCenter (enabled in advanced settings) replicating from the remote sites into the main DC for disaster recovery. You can then also leverage vMotion and Storage vMotion between the hosts in the remote site or from the remote site to the central DC without without breaking protection.
Any questions let me know. Thanks,
Joshua
Travis – how about keeping the 3 “major site” VCs and just reducing the remote sites to a single VC? Or is that the plan and I’m just reading into it too much?
I don’t think we need to get into the design decisions of the vSphere environment as a whole since there are too many variables involved to hash it out via a forum.
From a Zerto standpoint it looks like a centralized vCenter is the way to go. Especially with vm’s that have to ability to move across datacenters.
Thanks for your responses!