Installing the Zerto Solution : The Zerto Solution DR Architecture
  
The Zerto Solution DR Architecture
The following diagram shows how the main Zerto components are deployed across sites to provide disaster recovery across these sites.
Note: For details of the architecture and ports used in a cloud-based architecture environment, see Zerto Cloud Manager Installation Guide.
vSphere Architecture
The following architecture diagram shows the ports that must be opened in the firewalls on all sites.
Hyper-V Architecture
The following architecture diagram shows the ports that must be opened in the firewalls on all sites.
Zerto Virtual Replication can be installed at multiple sites and each of these sites can be paired to any of the other sites.
Zerto supports both the protected and recovery sites being managed by a single vCenter Server or System Center Virtual Machine Manager. For example, in the following scenario:
■ From a branch office, to the main office, both managed by the same System Center Virtual Machine Manager.
■ From one host to a second host, both managed by the same System Center Virtual Machine Manager.
■ To the same host but using different storage for recovery.
It is recommended to install Zerto Virtual Replication in the main office site where protected machines will be recovered.
The following table provides basic information about the ports shown in the above diagram by Zerto Virtual Replication.
Note: UDP ports in the 444xx range for DHCP are not required and can therefore be blocked.
 
Port
Purpose
22
(vSphere only) Required between an ESXi host and the ZVM during installation of a VRA.
443
(vSphere only) Required between the ZVM and the vCenter Server.
443
(vSphere only) Required between an ESXi host and the ZVM during installation of a VRA.
8100
(Hyper-V only) Communication between the ZVM and the SCVMM (System Center Virtual Machine Manager).
4005
Log collection between the ZVM and site VRAs.
4006
Communication between the ZVM and local site VRAs and the site VBA.
4007
Control communication between protecting and peer VRAs.
4008
Communication between VRAs to pass data from protected virtual machines to a VRA on a recovery site.
4009
Communication between the ZVM and local site VRAs to handle checkpoints.
5672
(vSphere only) TCP communication between the ZVM and vCloud Director for access to AMQP messaging.
9779
Communication between ZVM and ZSSP (Zerto Self Service Portal).
9989
Communication between ZCM, and ZCM GUI and ZCM REST APIs.
9080*
Communication between the ZVM, Zerto Powershell Cmdlets, and Zerto Diagnostic tool.
9081*
Communication between paired ZVMs**
Note:  
■ When a single vCenter Server or SCVMM is used for both protection and recovery, only one ZVM is installed and port 9081 is not used.
■ Recovery to a different vCenter Server or SCVMM uses port 9081 between the ZVMs in each site.
9180*
Communication between the ZVM and the VBA.
9669*
Communication between ZVM and ZVM GUI and ZVM REST APIs, and the ZCM.
(Hyper-V only) Communication between every Hyper-V host and the Zerto Virtual Manager.
*The default port provided during the ZVR installation which can be changed during the installation.
 
 
See also:
■ Zerto Interoperability Matrix
■ Requirements
■ Considerations
■ The Zerto User Interface in a vSphere Client
■ Database Requirements
■ vSphere Privileges Required by Zerto Virtual Replication
■ (Hyper-V Only) Privileges Required by Zerto Virtual Replication
■ Installing Zerto Virtual Replication in On-Premise Environments
■ Performing a Silent Installation
■ Installing Zerto Cmdlets
■ Repairing the Current Installation
■ Uninstalling Zerto Virtual Replication
■ Upgrading Zerto Virtual Replication