Requirements
Zerto Virtual Manager is installed on each site managed by a vCenter Server. The installation must be on a machine running a Windows operating system with the following requirements:
■ Windows Server 2008 R2 SP1 with KB3033929 and KB2864202, Windows Server 2012 base, or Windows Server 2012 R2.
Reserve at least 2 CPUs and 4GB RAM for the machine. The following CPU and RAM are recommended by Zerto for the machine running Zerto Virtual Replication, dependent on the size of the site:
Sites protecting up to 750 virtual machines and up to 5 peer sites: 2 CPUs and 4GB RAM.
Sites protecting 751-2000 virtual machines and up to 15 peer sites: 4 CPUs or 2 Dual Core CPUs and 4GB RAM.
Sites protecting over 2000 virtual machines and over 15 peer sites: 8 CPUs or 4 Dual Core CPUs and 8GB RAM.
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.
Note: The following restriction applies to recovering individual files and folders and not to recovering the whole virtual machine: The operating system of the machine on which the recovery site Zerto Virtual Manager is installed determines the types of file systems from which individual files and folders can be recovered. When the recovery site Zerto Virtual Manager virtual machine operating system supports a file system, files and folders can be recovered from this file system in virtual machines that this Zerto Virtual Manager will manage the recovery of. For example, if a protected virtual machine running Windows 2012 has files using the ReFS file system and requires one or more of these files to be recovered and the recovery site Zerto Virtual Manager is on a machine with Windows 2008, which does not support ReFS, the protected virtual machine files and folders cannot be recovered, but the whole virtual machine can be recovered.
■ At least 4GB of free disk space.
■ Microsoft .NET Framework 4.5.2. The 4.5.2 installation executable is included as part of the Zerto Virtual Replication installation kit and it needs an additional 1.8GB of free disk space. Note that recent Windows operating systems include .NET as part of the operating system. Make sure that you have the latest Windows updates, unless Zerto support warns against a specific update.
Note: If the required version of Microsoft .NET Framework is not installed, you are prompted to install the required version of .NET Framework as part of the Zerto Virtual Replication installation procedure.
You must have VMware vCenter Server version 4.0U1 or higher with at least one ESX/ESXi host installed on each site where Zerto Virtual Manager is to be used. The Zerto Virtual Manager must have access to the vCenter Server via a user with administrator level privileges to the vCenter Server. When recovery is managed by the same vCenter Server as the protection, Zerto Virtual Manager is required to be installed once only. When the protected and recovery sites are managed by different vCenter Servers Zerto Virtual Manager is installed once per vCenter Server. If Zerto Cloud Manager is used, vSphere Standard edition cannot be used. For details about Zerto Cloud Manager, see Zerto Cloud Manager Administration Guide.
Note: When the vCenter Server is installed on a Linux machine via the vCenter Server Linux Virtual Appliance (vCSA), the Zerto Virtual Manager must still be installed on a Windows machine.
Zerto recommends installing the Zerto Virtual Manager with the following profile:
■ On a dedicated virtual machine.
■ With a dedicated administrator account.
■ No other applications installed on this machine. If additional applications are installed, the Zerto Virtual Manager service must receive enough resources and HA remain enabled.
■ With VMware vSphere High Availability (HA) enabled.
■ With the VM Restart Policy set to High.
Note: If a proxy server is used at the site, specify the IP address of the Zerto Virtual Manager in the exception list in the Proxy Server settings.
You cannot take snapshots of the Zerto Virtual Manager as snapshots cause operational problems for the Zerto Virtual Manager, such as creating inconsistencies with peer site Zerto Virtual Managers.