Multisite vCenter Server deployment

The multisite deployment is a common use case and network deployment pattern. This topology is highly scalable and easier to manage and expand. The multisite deployment pattern is based on the vCenter Server multisite deployment option.

The following diagram shows an example of a customer deployment by using this topology. You can add more hosts or new clusters to scale the solution.

1. The vCenter Server automation deploys an initial vSphere cluster on the primary instance, which includes a vCenter, three NSX managers, and an Active Directory deployment. They run either on a single IBM Cloud Classic Virtual Server Instance or two VMware VMs in an HA deployment. This instance includes a vCenter, three NSX managers, an Active Directory deployment with either running on a single IBM Cloud Classic Virtual Server Instance or two VMware VMs in an HA deployment and two NSX edge clusters, one for services and one for workloads.
2. The initial VCF for Classic - Automated instance can include several vSphere clusters (refer to single site deployment). They are typically deployed in the initial IBM Cloud data center location.
3. You can provision a secondary VCF for Classic - Automated instance after the primary that is deployed. This option deploys automatically a secondary VCF for Classic - Automated instance in the new IBM Cloud data center location. This instance is then linked to the initial primary vCenter Server single site deployed on step 1. You can create multiple secondary instances. As the primary, this instance includes a vCenter, three NSX managers, an Active Directory deployment with either running on a single IBM Cloud Classic Virtual Server Instance or two VMware VMs in an HA deployment and two NSX edge clusters, one for services and one for workloads. The second site is under the same SSO and root domain as the primary.
4. As the primary, also the secondary VCF for Classic - Automated instance can include several vSphere clusters. They are typically deployed in the same IBM Cloud data center location as the secondary.
5. You can add NFS based IBM Cloud File Storage for Classic to your clusters. You can add one or more file shares and configure them individually by selecting the performance (IOPS) and size (GB) for each. Each data center and each instance uses its own storage.
6. You can also use vSAN with your vSphere clusters. When you use vSAN, due to the nature of dedicated local storage, you must select the vSAN option when you order the cluster. Each instance uses its own storage.
7. Both the primary and secondary instances have their own NSX managers and their own NSX topologies. Each instance has a workload edge cluster, which consists of two edge transport nodes for your usage.
8. The hosts and NSX Tier-0 Gateways in the specific data center or POD are attached to VLANs and subnets that are local to that IBM Cloud data center or POD. These VLANs and subnets cannot be extended or moved to other IBM Cloud data centers. However, these subnets can communicate with subnets that are provisioned to another IBM Cloud data center over IBM Cloud private network.
9. If you select an optional gateway cluster, the vCenter Server automates two ESXi hosts by using IBM Cloud bare metal servers and forms a new vSphere cluster in your deployment. This can be done on each instance separately.

Dual-site vCenter Server deployment

The dual-site deployment is typically suitable for the production and disaster recovery use cases. This deployment pattern is based on two vCenter Server as a single site instance, where each instance is deployed separately and they do not have any common management. This pattern is highly scalable and each instance is managed and expand separately. Integration between these environments is typically at network level and in disaster recovery use cases, third-party products are typically used to replicate data and VMs.

The following diagram shows an example of a customer deployment by using this topology.

1. The vCenter Server automation deploys instance A and its management or converged cluster, which includes a vCenter, three NSX managers, and an Active Directory deployment. They run either on a single IBM Cloud Classic Virtual Server Instance or two VMware VMs in an HA deployment. This instance includes a vCenter, three NSX managers, an Active Directory deployment with either running on a single IBM Cloud Classic Virtual Server Instance or two VMware VMs in an HA deployment and two NSX edge clusters, one for services and one for workloads.
2. You can provision another VCF for Classic - Automated instance, instance B, at the same time or later than the instance A. By using this option, the automation deploys a new VCF for Classic - Automated instance in the new IBM Cloud data center location. As the instance A, this instance includes a vCenter, three NSX managers, an Active Directory deployment with either running on a single IBM Cloud Classic Virtual Server Instance or two VMware VMs in an HA deployment and two NSX edge clusters, one for services and one for workloads.
3. Both VCF for Classic - Automated instances can include several vSphere clusters (refer to single site deployment).
4. If you select an optional gateway cluster, the vCenter Server automates two ESXi hosts by using IBM Cloud bare metal servers and forms a new vSphere cluster in your deployment. This can be done on each instance separately.
5. Each instance has its own storage, which can be NFS-based IBM Cloud File Storage for Classic or vSAN. You can add one or more NFS file shares and configure them individually by selecting the performance (IOPS) and size (GB) for each. When you use vSAN, due to the nature of dedicated local storage, you must select the vSAN option when you order the cluster.
6. Both instances have their own NSX managers and their own NSX topologies. Each instance has a workload edge cluster, which consists of two edge transport nodes for your usage.
7. The hosts and NSX Tier-0 Gateways in the specific data center or POD are attached to VLANs and subnets that are local to that IBM Cloud data center or POD. These VLANs and subnets cannot be extended or moved to other IBM Cloud data centers. However, these subnets can communicate with subnets that are provisioned to another IBM Cloud data center over IBM Cloud private network.

Considerations for multisite vCenter Server deployment topologies

When you design or deploy this architecture pattern, consider the following steps:

• You have several options to expand the capacity for the deployment, for example by provisioning new hosts on the initial cluster or by adding new clusters.
• This pattern provides a few examples of how to expand and customize the initial deployment for a few use cases to fit your needs, but note that these are just examples.
• You must note VMware limitations.

To customize the NSX overlay topologies, see the architecture pattern for multisite NSX topologies.

Related links

• vCenter Server overview
• Architecture pattern for multisite NSX topologies
• Multisite configuration for VCF for Classic - Automated instances