VMware Cloud Community
Kahonu84
Hot Shot
Hot Shot
Jump to solution

Vcenter consolidation during 5.5 to 6.5.2 upgrade

Aloha,

Currently we have 3 sites on island with a very reliable fiber link connecting them. Each site as its own vcenter and we use Zerto to move VMs between sites and for DR.

We are thinking now that we have VCHA available to us, would it be appropriate design to merge all 3 vcenters into one. Each current 5.5 vcenter would then become an individual datacenter under the new 6.5.2 singular vcenter. We would then use VCHA to replicate the new vcenter to the other 2 sites. We would then have vmotion options we never had before.

Are there any fallacies I am missing?

Bill

Reply
0 Kudos
1 Solution

Accepted Solutions
daphnissov
Immortal
Immortal
Jump to solution

Hi, Bill. I think you might be under a little bit of a false impression about vCHA. It isn't used as a DR mechanism and it wouldn't "replicate" vCenter across your three sites. It's really not meant to be used across sites (there is a specific latency requirement of no more than 10ms). Plus, using or not using it wouldn't give you any further abilities when it comes to vMotion across the islands. However, you could upgrade each of those sites to vSphere 6.5 (or 6.7 if you wanted to go there) and join them all in Enhanced Linked Mode with the appliance. This would give you the "single pane of glass" experience allowing you to migrate workloads across from within the vSphere Client. Note that you'd still have to meet all the vMotion requirements in order to do so, but shared storage is *not* one of those requirements (nor is stretched L2 on the vMotion network, BTW), so you still have a great deal of flexibility in what you can do with your infrastructure.

View solution in original post

Reply
0 Kudos
1 Reply
daphnissov
Immortal
Immortal
Jump to solution

Hi, Bill. I think you might be under a little bit of a false impression about vCHA. It isn't used as a DR mechanism and it wouldn't "replicate" vCenter across your three sites. It's really not meant to be used across sites (there is a specific latency requirement of no more than 10ms). Plus, using or not using it wouldn't give you any further abilities when it comes to vMotion across the islands. However, you could upgrade each of those sites to vSphere 6.5 (or 6.7 if you wanted to go there) and join them all in Enhanced Linked Mode with the appliance. This would give you the "single pane of glass" experience allowing you to migrate workloads across from within the vSphere Client. Note that you'd still have to meet all the vMotion requirements in order to do so, but shared storage is *not* one of those requirements (nor is stretched L2 on the vMotion network, BTW), so you still have a great deal of flexibility in what you can do with your infrastructure.

Reply
0 Kudos