For Managed Service Provider Sites
Notes:
|
•
|
For all known issues or limitations, see the Release Notes > Known Issues section. |
Zerto Virtual Manager Requirements
|
•
|
The Zerto Virtual Manager must have access to the vCenter Server via a user with administrator level privileges to the vCenter Server. |
|
•
|
On the machines were Zerto Virtual Replication is installed: |
|
•
|
64-bit Operating System |
|
•
|
The Operating system version number must be 6.1 or higher |
|
•
|
The Windows operating system must be Server Edition |
|
•
|
Microsoft .NET Framework 4.7.2. or higher
|
|
•
|
The 4.7.2 installation executable is included as part of the Zerto Virtual Replication installation kit and needs an additional 4.5 GB of free disk space |
|
•
|
If you install .NET Framework 4.7.2 as part of the Zerto Virtual Replication installation, you will be prompted to restart. |
|
•
|
Make sure that you have the latest .NET and Windows updates, unless Zerto support warns against a specific update. |
|
•
|
Reserve at least 2 CPUs and 4GB RAM for the machine. |
|
•
|
The clocks on the machines where Zerto Virtual Replication is installed must be synchronized with UTC and with each other (the timezones can be different). Zerto recommends synchronizing the clocks using NTP. |
|
•
|
At least 4GB of free disk space. |
|
•
|
Advanced Message Queuing Protocol (AMQP) Server. |
|
•
|
IP address of the vCloud Director. |
|
•
|
vCloud Director system administrator username and password. You can create a dedicated user for Zerto Virtual Replication but it must have system administration privileges. |
Make sure that the Managed Service Provider vDC has enough resources in order to replicate all the protected virtual machines into the Org vDC. Zerto Virtual Replication does not support replicating vApp networks and fence mode must not be enabled when performing a failover, test failover or move.
Note: To ensure that vCD is correctly installed, you must be able to define and power on a vApp with at least one virtual machine for each organization vDC. After verifying the vCD installation, the vApp can be removed. After the installation, there is no need to create a vApp network in vCloud Director on the cloud site. Zerto Virtual Replication creates the vApp network when performing a failover or migration into the provider vDC.
|
•
|
You must exclude the following folders from antivirus scanning: |
|
•
|
%ProgramData%\Zerto\Data\zvm_db.mdf |
|
•
|
C:\Program Files\Zerto\Zerto Virtual Replication\Zerto.Zvm.Service.exe |
|
•
|
C:\Program Files\Zerto\Zerto Virtual Replication\Zerto.Vba.VbaService.exe |
|
•
|
C:\Program Files\Zerto\Zerto Virtual Replication\Zerto Online Services Connector\Zerto.Online.Services.Connector.exe |
|
•
|
C:\Program Files\Zerto\Zerto Virtual Replication\Embedded DB Manager Service\Zerto.LocalDbInstanceManagerService.exe |
Important: Failure to do so may lead to the Zerto folder being incorrectly identified as a threat and in some circumstances corrupt the Zerto Virtual Replication folder.
Virtual Replication Appliances Requirements
To install a VRA you require the following:
|
•
|
12.5GB datastore space. |
|
•
|
At least 1GB of reserved memory. |
You must also know the following information to install a VRA:
|
•
|
If the ESXi version is 5.5 or higher and the VRA should connect to the host with user credentials, or if the ESXi version is lower than 5.5 (4.x or 5.x), the password to access the host root account. |
Note: For ESXi versions 5.5 or higher, by default the VRA connects to the host with a vSphere Installation Bundle, VIB. Therefore, it is not necessary to enter the password used to access the host root account.
|
•
|
The storage the VRA will use and the local network used by the host. |
|
•
|
The network settings to access the peer site; either the default gateway or the IP address, subnet mask, and gateway. |
Note: When the gateway is not required, you can specify 0.0.0.0 as the gateway, for example when performing self replication.
|
•
|
If a static IP is used, which is the Zerto recommendation, instead of DHCP, the IP address, subnet mask, and default gateway to be used by the VRA. |
Note: In a non-production environment it is often convenient to use DHCP to allocate an IP to the VRA. In a production environment this is not recommended. For example, if the DHCP server changes the IP allocation on a reboot, the VRA does not handle the change.
Note: For the duration of the installation of the VRA, the Zerto Virtual Manager enables SSH in the vCenter Server.
Zerto Cloud Manager Requirements
Zerto Cloud Manager is installed on a machine running a Windows operating system with the following requirements:
|
•
|
Windows Server 2008, 2008R2, 2012, 2012R2 or 2016 with at least 1 CPU and 2GB RAM reserved. |
|
•
|
At least 4GB of free disk space. |
|
•
|
Microsoft .NET Framework 4.7.2 or higher. |
Zerto User Interface Requirements
|
•
|
Adobe Flash Player 11.9 ActiveX or higher for the Zerto Cloud Manager user interface. If a valid version of the Flash Player is not installed, you are prompted to install it when first accessing the user interface. |
Note: Adobe Flash Player is only necessary for Zerto Cloud Manager. It is not necessary for Zerto Virtual Manager.
|
•
|
The minimum recommended screen resolution is 1024*768. |
Zerto Cloud Connectors (DRaaS) Requirements
|
•
|
Zerto Cloud Connectors can only be installed on ESX/ESXi hosts version 4.1 and higher with 2GB datastore space. |
|
•
|
You must know the following information to install a Zerto Cloud Connector: |
|
•
|
The organization network to access the Zerto Cloud Connector. |
|
•
|
The cloud network settings to access the Zerto Cloud Connector. |