- This topic has 3 replies, 3 voices, and was last updated September 11, 2019 by Matthew W.
We’d like to update our Zerto Software which is currently running at 5.5 build 7. Can you please advise what version we can upgrade to and if we need to perform step upgrades to get to final version?
We currently use VMWare vSphere 6.5, ESXi Host 6.0 U3e and ESXi Host 6.5 U1g. We have VMs running SUSE Linux 12, do the VMs version have an impact to Zerto version?Matthew WSeptember 10, 2019 07:30:15 PM
Please see the document Upgrading Zerto Virtual Replication for specific information on upgrading your installation of Zerto. The article ZVM Upgrade Best Practices can also provide some insight for you. I have added some general details from them for you below.
Zerto recommends upgrading to the latest version of Zerto that supports the environment you are using. See the Zerto Interoperability Matrix for the list of environments supported by this version of Zerto.
• The order you upgrade the sites, protected or recovery, is not relevant as long as paired sites remain only one version apart, that is, only one version higher or lower.
• You may only upgrade one major release at a time, meaning you can go from 5.5 to 6.0, but not directly to 6.5 or 7.0 as an in place upgrade.
• If you would like to go directly from 5.5 to a version after 6.0, you may uninstall the old version of Zerto Virtual Replication and install the new version. Please be sure to use the Zerto Diagnostics utility’s export option to export the existing VPG definitions before uninstalling.
• When upgrading from versions prior to Zerto Virtual Replication 6.0U2, changing the Journal Size Hard Limit requires restarting the VRAs.
The following two notes apply if you are using Zerto’s Offsite Backup functionality in addition to VM Replication. This feature was replaced by Long Term Recovery.
• During an upgrade from v6.0x to v6.5, all back up and repositories configurations are deleted.
• During an upgrade from v6.5 to v7.0, Repositories that were created in 6.5 and all the retentions sets they contain, will be available for Restores only.
I hope this information helps!Jeremy YSeptember 11, 2019 02:05:38 PM
Thanks for the reply.
Also wondering about the Database side. I’m pretty sure we’re using the Zerto Virtual Manager internal database, is there a need to move to External SQL server with these upgrades? Or can we continue using our current Database? Our environment isn’t too big, we have 2 vCenters with 2 ZVM. About 15 hosts per site and approximately 120 VMs.
Is there a way to tell how big our current DB is? I’ve read that the ZVM internal database is 4gb limit.
ThanksMatthew WSeptember 11, 2019 09:24:44 PM
Using the internal DB option should not disrupt the normal Zerto upgrade process.
The internal DB is located at C:\ProgramData\Zerto\Data\zvm_db.mdf. You should be able to see the size of the file here.
Does this help?