Tutorial: Scale clusters in a private cloud
To get the most out of your Azure VMware Solution private cloud experience, scale the clusters and hosts to reflect what you need for planned workloads. You can scale the clusters and hosts in a private cloud as required for your application workload. You should address performance and availability limitations for specific services on a case-by-case basis.
The following table describes the maximum limits for Azure VMware Solution.
Resource | Limit |
---|---|
vSphere clusters per private cloud | 12 |
Minimum number of ESXi hosts per cluster | 3 (hard-limit) |
Maximum number of ESXi hosts per cluster | 16 (hard-limit) |
Maximum number of ESXi hosts per private cloud | 96 |
Maximum number of vCenter Servers per private cloud | 1 (hard-limit) |
Maximum number of HCX site pairings | 25 (any edition) |
Maximum number of HCX service meshes | 10 (any edition) |
Maximum number of Azure VMware Solution ExpressRoute linked private clouds from a single location to a single Virtual Network Gateway | 4 The virtual network gateway used determines the actual max linked private clouds. For more details, see About ExpressRoute virtual network gateways If you exceed this threshold use Azure VMware Solution Interconnect to aggregate private cloud connectivity within the Azure region. |
Maximum Azure VMware Solution ExpressRoute port speed | 10 Gbps (use Ultra Performance Gateway SKU with FastPath enabled) The virtual network gateway used determines the actual bandwidth. For more details, see About ExpressRoute virtual network gateways |
Maximum number of Azure Public IPv4 addresses assigned to NSX-T Data Center | 2,000 |
Maximum number of Azure VMware Solution Interconnects per private cloud | 10 |
vSAN capacity limits | 75% of total usable (keep 25% available for SLA) |
VMware Site Recovery Manager - Maximum number of protected Virtual Machines | 3,000 |
VMware Site Recovery Manager - Maximum number of Virtual Machines per recovery plan | 2,000 |
VMware Site Recovery Manager - Maximum number of protection groups per recovery plan | 250 |
VMware Site Recovery Manager - RPO Values | 5 min or higher * (hard-limit) |
VMware Site Recovery Manager - Maximum number of virtual machines per protection group | 500 |
VMware Site Recovery Manager - Maximum number of recovery plans | 250 |
* For information about Recovery Point Objective (RPO) lower than 15 minutes, see How the 5 Minute Recovery Point Objective Works in the vSphere Replication Administration guide.
For other VMware-specific limits, use the VMware configuration maximum tool.
In this tutorial, you'll use the Azure portal to:
- Add a cluster to an existing private cloud
- Add hosts to an existing cluster
Prerequisites
You'll need an existing private cloud to complete this tutorial. If you haven't created a private cloud, follow the create a private cloud tutorial to create one.
Add a new cluster
In your Azure VMware Solution private cloud, under Manage, select Clusters > Add a cluster.
Use the slider to select the number of hosts and then select Save.
The deployment of the new cluster begins.
Scale a cluster
In your Azure VMware Solution private cloud, under Manage, select Clusters.
Select the cluster you want to scale, select More (...), then select Edit.
Click Add Host to add a host to the cluster. Repeat that to reach the desired number of hosts, and then select Save.
The addition of hosts to the cluster begins.
Note
The hosts will be added to the cluster in parallel.
Next steps
If you require another Azure VMware Solution private cloud, create another private cloud following the same networking prerequisites, cluster, and host limits.
Feedback
Submit and view feedback for