Before you deploy the DRaaS Connector, review these system and network requirements.

vSphere and VMware Cloud on AWS Compatibility

For the most current information on vSphere and VMware Cloud on AWS compatibility with the service, see the VMware product interopability matrix.

For configuration limits of the service, see VMware Cloud DR configuration limits.

DRaaS Connector System Requirements

To deploy the DRaaS Connector VM, make sure that the vSphere host where you deploy it has the following available resources for the VM.
Site Resources Value
VMware vCenter Version 6.5 U2 or later
CPU 8 GHz (reserved)
RAM 12 GiB (reserved)
Disk 100 GiB virtual disk
Network connectivity

If you deploy more than one DRaaS Connector, deploy only one connector VM per-host.

Note: VMware Cloud DR does not support an internet proxy server between the DRaaS Connector and the cloud.
Note: If the DRaaS Connector becomes unregistered, delete the VM and re-deploy the connector VM as an OVF. Do not use the the vCenter datastore browser to register the connector.

DRaaS Connector Deployment Considerations

Consider the following strategies when deploying the DRaaS Connector on a protected site:

  • Deploy a minimum of two DRaaS Connectors per-protected site.
  • Deploy one DRaaS Connector per-host.
  • For sites with more 10,000 VMs, you might experience some responsiveness issues with the VMware Cloud DR UI, such as slow loading of pages or windows when previewing protection group VM membership, creating and editing DR Plans, and during plan compliance checking.

DRaaS Connector Networking Requirements

The DRaaS Connector requires the following open outbund ports listed below in your network to allow connector traffic. See Service Public IP Addresses for how to find the public IP addresses of the Orchestrator and the cloud file system. Network flow diagram showing outbound ports that need to be open in your network to allow DRaaS Connector communication.
Note: The DRaaS Connector no longer uses port 22 to communicate with the Orchestrator. Staring in November 2021, the connector can now use outbound port 1759 for communicating with the Orchestrator. We recommend that you first open outbound port 1759 to the Orchestrator. Once that connection is working, you can close outbound port 22 for the connector.
Table 1. Open Ports Required for the DRaaS Connector
Port Protocol Source Destination Service Description Classification
80 TCP DRaaS Connector (on-premises deployment only) vCenter Server vCenter web service Outbound
1759 TCP DRaaS Connector

Cloud file system

Encrypted tunnel for data transfers and metadata operations Outbound
1759 TCP DRaaS Connector Orchestrator Management service Outbound
443 TCP DRaaS Connector vCenter Server vCenter web service Outbound
443 TCP DRaaS Connector Orchestrator Management service Outbound
443 TCP DRaaS Connector VMware auto-support server Support service Outbound
902 TCP DRaaS Connector(on-premises deployment only)

ESXi Management IP address

Reading/writing vdisks Outbound