Production deployments of vCloud Availability for vCloud Director have specific sizing and component configurations.

A production deployment uses multiple components to support many protected virtual machines, and to provide a fault-tolerance within the DRaaS environments.

Production Architecture

Production deployments must meet certain requirements.

  • At each tenant site, there is one or more single-tenant environments to be protected.

  • In the service provider disaster recovery site, one or more vCloud Director is configured with a specific number of components designed to handle the required number of VMs from each tenant.

  • A single vCloud Director environment in a data center hosts up to 500 individual tenants.

Using this information as a base, you must install and configure a new vCloud Availability for vCloud Director service pod for every 100 tenants that use the service.

In a single vCloud Director deployment, there is a limit to the number of VMs that can be replicated as part of the DR solution. The exact combination depends on the number of VMs that must be supported combined with the system limits for each component.

Component Sizing

Individual components have a minimum installation count required for a base installation.

Table 1. Relative Component Sizing

Component

Related Component

vCloud Director

2 vCenter Server Appliances

vSphere Replication Manager

4 vSphere Replication Server

Component Limits

Individual components have limits for the maximum number of supported services, instances, or connections required.

Table 2. Component Counts and Limits per Pod

Component

Limit

Cloud Proxy

2000 Connections

vSphere Replication Server

500 active replications

Tenants

500 per vCloud Director

vCloud Director

10 vCenter Server Instances

vCloud Availability for vCloud Director Portal

800 concurrent sessions

Sample Deployment Scaling

Using the information on sizing and configurations, for a single pod, supporting up to the maximum of 100 tenants.

Table 3. Component Counts for Production Deployments

Protected VMs

500

1000

2000

3000

5000

10000

vSphere Replication Server

12

24

48

60

120

240

vSphere Replication Cloud Service

2

2

3

3

3

3

Cloud Proxy

2

2

2

2

3

5

Sample Deployment Configuration

Production deployment depends on the number of supported VMs and Tenants. An example configuration of a production deployment is provided in the table.

Table 4. Component Deployment for Production Deployments

Component

Host 1

Host 2

Host 3

Host 4

Quantity

Cassandra

Yes

Yes

Yes

Yes

4

Cloud Proxy

Yes

Yes

2

Microsoft SQL Server

Yes

Yes

Yes

3

NFS

Yes

1

NSX Manager

Yes

1

RabbitMQ

Yes

Yes

Yes

3

vCenter Server Appliance

Yes

1

vCloud Director

Yes

Yes

2

vSphere Replication Cloud Service

Yes

1

vSphere Replication Manager

Yes

1

vSphere Replication Server

Yes

Yes

Yes

Yes

4

vCloud Availability for vCloud Director Portal

Yes

1

Within a production deployment, the underlying network architecture is important. The following describes a best practice network configuration.

  • Each underlying physical ESXi installation is configured with a VMXNET3 high-speed network adapter, connected to two separate 10Gbe switches using NIC teaming.

  • The two switches are connected to each other using two 40gbe QSFP cables.

  • The switches are configured to present a VLAN that is configured as a port group on the ESXi hosts.

  • The virtual machines that make up the environment are all configured in this flat broadcast domain.