vCD Used by the Cloud Service Provider
The following diagram shows an example of an organization protecting virtual machines to the cloud service provider vCD:
Note: vCloud Networking and Security (vCNS) can be used instead of VPN. In this case the VPN component between the External Network and Org vCD Network is replaced by vCNS. Even though vCNS supports NAT, Zerto Virtual Replication does not support NAT.
You can set up the cloud site infrastructure such that the cloud and organization networks are on different subnets or on the same subnet.
Cloud and Organization Networks on Different Subnets – If the cloud service provider dedicated network IP addresses and the organization dedicated Org vDC Network IP addresses are on different IP subnets, make two IP addresses available for the Zero Cloud Connector component (IPs 10.4.141.32 and 192.168.2.42 in the above diagram), one IP address available for each network.
Cloud and Organization Networks on the Same Subnet – If the cloud service provider dedicated network IP addresses and the organization dedicated Org vDC Network IP addresses are on the same IP subnet, there is no need for the Zerto Cloud Connector.
When creating the organization dedicated Org vDC Network, make sure it is connected to the External Network either directly or via a routed connection. The organization dedicated network must enable a connection between the Org vDC Network and the External Network, so that VPN can be used to connect to the outside world. Connect the VPN to the organization dedicated Org vDC network in order to create a connection between the organization site and its own internal Organization vDC in the cloud vCD.
Make sure that the VC Network and the External Network inside vCD on the cloud site have a connection to the internet or to a wider network that will enable a connection between the cloud site and the organization sites.
