Hi
We currently have a single Windows vCenter server, running v6.0.0.17802, with an embedded PSC, and a local SQL instance. We have two sites.
I want to get to either of these configurations:
I do not wish to use a load balancer.
Is there a migration path supported for these transitions?
Thanks
I will recommend you to use the configuration #1, and to achieve that you will need to deploy a new external PSC, move your current vCenter to that external PSC. After that, deploy a new PSC and your second site and join that PSC to the SSO domain of your PSC at your first site, and then deploy your second vCenter at the secondary site and point that vCenter to your PSC at site 2.
Here is the list of supported vCenter 6 deployment topologies: vCenter Server 6 Deployment Topologies and High Availability - VMware vSphere Blog
In this configuration each site is independent with PSC replication between sites. The vCenter Server is aware of the site topologies and use the local PSC under normal circumstances. Customers are able to seamlessly move the vCenter Servers between PSCs when necessary. This topology allows for Enhanced Linked Mode (ELM) which is facilitated by the PSC. Enhanced Linked Mode provides for a single point of management for all vCenter Servers in the same vSphere domain. In vSphere 6 the Windows-based and Virtual Appliance-based vCenter Servers have the same operational maximums and can belong to the same linked mode configuration. The configuration replicates all license, global permissions, tags and roles across all sites.
I will recommend you to use the configuration #1, and to achieve that you will need to deploy a new external PSC, move your current vCenter to that external PSC. After that, deploy a new PSC and your second site and join that PSC to the SSO domain of your PSC at your first site, and then deploy your second vCenter at the secondary site and point that vCenter to your PSC at site 2.
Here is the list of supported vCenter 6 deployment topologies: vCenter Server 6 Deployment Topologies and High Availability - VMware vSphere Blog
In this configuration each site is independent with PSC replication between sites. The vCenter Server is aware of the site topologies and use the local PSC under normal circumstances. Customers are able to seamlessly move the vCenter Servers between PSCs when necessary. This topology allows for Enhanced Linked Mode (ELM) which is facilitated by the PSC. Enhanced Linked Mode provides for a single point of management for all vCenter Servers in the same vSphere domain. In vSphere 6 the Windows-based and Virtual Appliance-based vCenter Servers have the same operational maximums and can belong to the same linked mode configuration. The configuration replicates all license, global permissions, tags and roles across all sites.
Thanks.
In this setup, with 2 of each, I assume we have two options for the vCenter SQL DBs...
a) Install SQL locally on both vCenter servers
or
b) Install SQL externally in a HA config - one DB per vCenter
Is this correct?
a) Install SQL locally on both vCenter servers
If you have SQL license, it is ok.
b) Install SQL externally in a HA config - one DB per vCenter
It depends... I will recommend at least on SQL per site, so if you can configure the SQL cluster with a node per site it is ok.
Anyway, did you considered move to vCenter Server 6.5 appliance? I will really encourage you do that.
I am considering it, yes. How would this change my migration strategy?
Should I upgrade vCenter Windows to 6.5 first, then run this migration? https://esxsi.com/2016/11/17/vcsa65m/
At what stage should I separate out the PSCs?