Upgrade Considerations with Zerto Virtual Replication

Zerto Virtual Replication release regular updates. In addition, VMware also release new versions of their
products which can impact on Zerto Virtual Replication. This document describes the different options for
different upgrade scenarios.
The document includes the following topics:
Upgrading Zerto Virtual Replication to the next version
Upgrading Zerto Virtual Replication to a version at least two versions higher than the current version
Upgrading VRAs
Upgrading VMware products (vSphere and ESX/ESXi hosts)

Upgrading Zerto Virtual Replication to the Next Version

You can upgrade Zerto Virtual Replication to the new version, either by installing the new version as an
upgrade over the existing version, or by uninstalling the existing version and then installing the new version
Zerto Best practice: Before upgrading Zerto Virtual Replication, it is recommended to clear the Microsoft
Internet Explorer cache of temporary internet files. Not clearing the cache of temporary files can result in
problems when accessing the Zerto Virtual Manager via the vSphere Client console.

Zerto Virtual Replication can be used with versions on other sites, either one version higher or lower than
the version installed on this site. Thus, for example, version 2.0U2 of Zerto Virtual Replication can only be
used with Zerto Virtual Replication versions 2.0U1, 2.0U2 and 2.0U3.
If a newer version of the installed Virtual Replication Appliances (VRAs) exists, you can continue to use
these VRAs with the new version or upgrade these VRAs from within the Zerto Virtual Replication UI in
vSphere Client console as described below.
Zerto Best practice: Zerto recommends upgrading the VRAs.

When upgrading, the protection of the virtual machines continues, but during the upgrade no new
checkpoints are written to the journal, resulting in alerts after the upgrade, even if only one of the sites was
upgraded. After the upgrade Zerto alerts might be issued stating that the journal history and RPO do not
meet the specified targets.
The installation checks for an existing installation and provides options to upgrade or reinstall Zerto Virtual
Replication if an existing installation is identified. If the version is newer than the installed version, you can
upgrade the existing version of the Zerto Virtual Manager without disrupting the protection. The defined
Virtual Replication Appliances and protected virtual machines, along with all other information, such as
checkpoints, journals, masking, site and pairing information, are kept.
You can only upgrade to the next version.
When the upgrade installation has completed, the VPG definitions are upgraded to the new version. Also,
any customization of Zerto Virtual Replication alarms is maintained during an upgrade except for the Send
a notification email action which is removed. Email notifications for alarms configured in the Zerto
GUI, in the Advanced Settings dialog, are also maintained during an upgrade.
While upgrading Zerto Virtual Replication, the protection of the virtual machines continues, but during the
upgrade no new checkpoints are written to the journal, resulting in alerts after the upgrade, even if only one

2013 Zerto Ltd. All rights reserved.

1

of the sites was upgraded. After the upgrade, Zerto alerts might be issued stating that the journal history
and RPO do not meet the specified targets.
If the vSphere Client console was open during the upgrade, close it and reopen it to ensure the upgraded
Zerto Virtual Replication UI is loaded in the console.

Upgrading Zerto Virtual Replication to a Version at Least Two

Versions Higher Than the Current Version
If you need to upgrade more than one version, either upgrade to the next version, as described above, and
repeat this until you upgrade to the required version or use the procedure below.
Note: You can only protect or recover VPGs to a site running a different version, either one version higher or

lower than the version installed on this site.

Use the following procedure to save the VPGs that have been defined, before uninstalling the old version of
Zerto Virtual Replication and then, after the upgrade of Zerto Virtual Replication, to re-implement these
VPGs.
The following procedure also applies when upgrading Zerto Virtual Replication from any version from 1.0U4
to any newer version.
Zerto Best practice: It is recommended to make sure that all the VPGs are in Protecting state, and not

in a sync state or an error state, such as Missing Configuration.

If you need to upgrade more than one version higher, either upgrade to the next version and repeat this until
you upgrade to the required version or use the Zerto Diagnostics utility export and import options as
described in the following upgrade procedure:
Before upgrading do the following:
1. Click Start > Programs > Zerto Virtual Replication > Zerto Diagnostics.
The Zerto Virtual Replication Diagnostics menu dialog is displayed.

2013 Zerto Ltd. All rights reserved.

2

2. Select the Export Protection Group Settings option and click Next.

3. Select the destination for the file to contain exported settings and specify the Zerto Virtual Manager IP
address and port where the VPGs are protecting virtual machines.
4. Click Next.
The list of exported VPGs is displayed.
5. Click Done.
6. In the vSphere Client console delete the VPGs, keeping their target disks.
7. Uninstall the existing Zerto Virtual Replication version.
If you did not export the settings, Zerto Virtual Replication exports settings on a daily basis to the
Zerto_Installation_Folder\Zerto Virtual Replication\ExportedSettings folder. You can
use the last exported file as input to recreate the VPGs to this point in time. The default
Zerto_Installation_Folder is C:\Program Files\Zerto.
8. Install the new Zerto Virtual Replication version.
9. Click Start > Programs > Zerto Virtual Replication > Zerto Diagnostics.
The Zerto Virtual Replication Diagnostics menu dialog is displayed.
10. Select the Import Protection Group Settings option.

2013 Zerto Ltd. All rights reserved.

3

11. Click Next.

12. Select the file previously exported and enter the Zerto Virtual Manager IP address and port specified
when exporting the VPGs.
13. Click Next.
The list of exported VPGs is displayed.

14. Select the VPGs to import. Only VPGs with names that are not already defined can be imported. VPGs in
the import files with the same name as an existing VPG are displayed in the list disabled.
15. Click Next.
The list of imported VPGs is displayed. If the VPG could not be imported the reason for the failure is
specified.
16. Click Done.

2013 Zerto Ltd. All rights reserved.

4

Upgrading VRAs
When upgrading Zerto Virtual Replication, the VRAs that were installed in the previous version are not
upgraded automatically and must be upgraded via the Manage VRAs dialog. Zerto Virtual Replication
enables VRAs installed with the previous version of Zerto Virtual Replication to work with VRAs installed
with the current version of Zerto Virtual Replication in any combination of VRAs (all from one version or a
mix of VRA versions) as long as the VRAs are only one update higher or lower than the version of Zerto
Virtual Replication installed on this site.
Zerto Best practice: It is recommended to upgrade the VRAs to be consistent with the latest version.

VRA Upgrade Considerations

After upgrading Zerto Virtual Replication, the VRAs might also require an upgrade. You can see if an
upgrade is available in the Manage VRAs dialog, in the Status column.

You can upgrade a VRA in one of the following ways:

VMotion the protected virtual machines and datastores managed by the VRA to another host with a VRA.
A Bitmap Sync is performed after the upgrade.
Upgrade the VRA without touching the virtual machines managed by the VRA. After the upgrade, the
protected and recovery sites need to be synchronized, using either a Delta Sync, potentially impacting
journal history times, or a Bitmap Sync.
Note: Upgrading a VRA to Zerto Virtual Replication version 2.0U4 (Zebra) causes all the VPGs with virtual

machines being recovered to the host where the upgraded VRA is installed, to enter a Delta Sync.
To upgrade a VRA protecting virtual machines:
1. VMotion protected machines from the host with the VRA to be upgraded to another host.
Note: Upgrading a VRA protecting virtual machines without first VMotioning these virtual machines to

another host with a VRA, can potentially result in a Delta Sync instead of a faster Bitmap Sync.
2. In the vSphere Client console, select the Zerto tab for the vCenter Server node.
3. Click the configuration (cog) button in the local, left, site panel.
The Site Configuration dialog for the site is displayed.
4. Click the Manage VRAs... button.
5. Select a VRA to be upgraded and click the Upgrade Selected button. After the upgrade, a Bitmap Sync is
performed on all the VPGs with virtual machines impacted by the upgrade.
2013 Zerto Ltd. All rights reserved.
5

To upgrade a VRA recovering virtual machines:

1. In the vSphere Client console, select the Zerto tab for the vCenter Server node.
2. Click the configuration (cog) button in the local, left, site panel.
The Site Configuration dialog for the site is displayed.
3. Click the Manage VRAs... button.
4. Select a VRA to be upgraded and click the Upgrade Selected button. After the upgrade, a Bitmap Sync is
performed on all the VPGs with virtual machines impacted by the upgrade.
You upgrade a VRA that is both protecting virtual machines as well as recovering virtual machines by
following the To upgrade a VRA protecting virtual machines: procedure, above.

Upgrading VMware Products

Zerto Virtual Replication is integrated with VMware vCenter Server, vSphere Client console, ESX/ESXi
hosts and vCloud Director.

Upgrading or Reinstalling a vCenter Server

When changing the version of the vCenter Server, you can either upgrade the vCenter Server or reinstall it.
Upgrading a vCenter Server
When you upgrade a vCenter Server, the Zerto Virtual Replication components are not affected and
protection continues without you needing to perform any additional procedures.
Zerto Best practice: Zerto recommends upgrading a vCenter Server in preference to reinstalling it.

Reinstalling a vCenter Server

If, for whatever reason, you need to reinstall the vCenter Server, contact Zerto for help throughout the
reinstallation.

2013 Zerto Ltd. All rights reserved.

6

Upgrading or Reinstalling a Host

When upgrading or reinstalling a host with an active VRA, the recommendation is to change the recovery
host of every VPG that is recovering to the host.
VRAs installed on ESXi 4.x and 5.x hosts require a password to access the host. This password is supplied as
part of the installation of each VRA. If the password for a host is changed, for example when he host is
upgraded, you can change the password stored by the VRA by editing the VRA.
To change the host password required by a VRA:
1. Select the VRA and click Edit Selected VRA.
The Edit VRA dialog is displayed.

2. Edit the host root password:

Host Root Password If the password for the host has changed, specify the new password.

3. Click Save.

There is also a procedure to change the passwords for more than one host at one time, described in the Zerto
Virtual Replication Administration Guide.

Feedback
Zerto is constantly looking for ways to improve all aspects of its business and your feedback is very
important to us. Please send any comments you have about this document, to help us to improve it, to
support@zerto.com.

2013 Zerto Ltd. All rights reserved.

7