Zerto Software Install Guide

Step 1. Deploy a VM

Deploy a new or multi-use VM in your environment that does not need protecting by SecondSite.

  • The server you are installing onto needs to be at least Windows Server 2016 or higher with at least 2 vCPU, 4GB RAM and 5GB free disk space.

  • You will also need to have .NET 4.72 or higher installed, which comes with the Zerto installation software. We recommend that you also use SQL Server if your environment has over 40 hosts and 400 VMs in need of protection.

Step 2. Getting Started - Software Installation

Upgrade Path

Customers on version 9.5 will need to upgrade to 9.7 (Recommended U4 P3). Version 10 U2 P1 migration is available from specifically 9.7 U4 P3.

Existing Version

Upgrade Path

Existing Version

Upgrade Path

9.5 (Legacy)

Upgrade to 9.7 U4 P3

9.7 (Supported)

Upgrade to 9.7 U4 P3, then migrate to 10.0 U2 P1

10.0 U2 P1

No upgrade required

Media Downloads







Zerto 10.0 U2 P1

Zerto 9.7 (Supported)

Zerto 9.7U4P3 for VMware

Zerto 9.7U4P3 for HyperV

Installing the Software

NOTE: If you are more than one major version away from the supported version you will need to perform a stepped upgrade to get to the latest version. Refer to “Upgrade Path” above.

Zerto Version 10:

Starting with Zerto v10, Windows based ZVM’s are no longer supported and you will need to perform a migration to the Zerto Linux appliance (ZVMA) which utilises integrated Keycloak authentication.


We recommend referencing Zerto’s documentation for the deployment and configuration of the Linux Appliance as well as running the migration tool. Please use the below documentation links we’ve collated:

ZVM Deployment: https://help.zerto.com/bundle/Linux.ZVM.HTML.10.0/page/ZVM_Linux_Deployment_Guide.htm
Appliance Menu and network configuration:https://help.zerto.com/bundle/Linux.ZVM.HTML.10.0/page/ZVM_Linux_Appliance_Menu.htm
Keyclock User Federation LDAP Provider:
Keyclock User Managment:
Migration Utility Prerequisites:
Migration Wizard Guide:
Post Migration Checks:


Zerto 9.7 (Windows ZVM)

Download the relevant media and run the installer. If you do not have Microsoft .Net or it needs to be updated then this will update it and also reboot the server.

Step 3. Install Directory

Choose an install directory. It?s generally best to avoid making this the OS drive, just in case it fills up one day.

Step 4. Installation Type

Choose a custom installation type.

Step 5. Security Credentials

Give it the appropriate credentials. Whether you run it as a local system account or a named account is up to you and what business rules you have governing application security and access.

Step 6. Database Type

Choose whether to use the embedded database or if you prefer to use an existing external database.

Step 7. vCentre Credentials

Put in your vCenter server and credentials.

Step 8. Cloud Director (Optional)

Enter in VMware Cloud Director information if you are using vCloud on premise. If you don?t know what this means then you most likely do not need to enable vCD BC/DR and should simply hit next.

Step 9. Communications Ports

This is an important step and you should not alter the below ports at all. If you alter any of these ports, you may have difficulties pairing to the Zettagrid SecondSite? instance in your Availability Zone.

Step 10. Installation Commences

Wait for the installation.

Step 11. Install Complete

Tick the box to open the Zerto interface.

Step 12. Pair with Zettagrid

Check the “Pair to a site with a license” option and then enter in the IP address that Zettagrid have used when deploying your own personal SecondSite appliance. It was the IP address you provided initially when you signed up.

If you have problems pairing at any stage during operation, make sure that you have the following ports open.






Communication between the ZVM and your hosts and between your ZVM and our Zerto Cloud Connector (ZCC) in your isolated VDC.


Communication between the ZVM and your hosts and locally between your ZVM and your vCenter Server or vCloud Director.


Log collection between your ZVM and VRAs in your same site.


TCP communication between the ZVM and VRAs and the VBA on the same site.


TCP control communication between your local VRAs to our VRAs through your dedicated ZCC.


TCP communication as above to pass data from your protected virtual machines to our VRAs through your ZCC.


TCP communication locally between your ZVM and VRAs to handle checkpoints.


HTTP communication between your ZVM and other local Zerto components.


TCP communication between your ZVM and our ZCC.


HTTPS communication between the Zerto Self-Service Portal for in-cloud (ICDR) customers and a ZVM.


If you have the following time out issue when trying to pair to the site, Please make sure your local firewall device has not issue of passing packets with MTU size 1500 through the IPsec VPN tunnel. You can verify that by pinging the ZCC IP with command “ping -M do -s 1472 xx.xx.xx.xx“ from your local ZVM.

”pairing to site failed, timed out after attempting to connect to peer for 20 seconds”

Step 13. Setup Replication

Click on the ?Setup? tab to start the installation process for the VRAs to enable replication.

Step 14. Create VRA

Click on the “New VRA” button to deploy your first VRA. You will need to deploy one VRA per ESXi host that is protecting VMs.

If you have any issues installing a VRA then please be sure that you have the following requirements per VRA;

  • Disk Space: 12.5 GB

  • RAM: 1 GB (reserved). It is minimum requirement

  • SSH Port:22 is enabled on ESXi host

  • Https Port: 443 is enabled on ESXi host

  • Static IP

Step 15. Deployment Completed

Success! You have now fully deployed Zerto and all its components. Part of the initial install process was to install the vSphere plugin as well.  If you do not wish to use the Zerto console, then you can also see it now from within vSphere as per below.

Step 16. Create VPGs

Now you need to start protecting VMs and creating Virtual Protection Groups (VPGs).

If you need assistance in getting started creating VPGs, please refer our guide on protecting VMs.