General Support Timelines

Zerto typically certifies new VMware releases within approximately three months of their official release. DR2Cloud, which relies on Zerto, adheres to these same certification timelines. However, critical security updates may sometimes need to be deployed sooner.

Security Patches That Do Not Change the VMware Version

If the update only alters the VMware build number and does not introduce a new version (for instance, from ESXi 7.0U3r to 7.0U3s), DR2Cloud with Zerto remains fully supported. You can safely proceed with these updates in line with the Zerto Interoperability Matrix.

VMware Updates That Change the Version

If an update introduces a new VMware version not yet listed in the Zerto Interoperability Matrix, DR2Cloud cannot guarantee full vendor support until Zerto completes its certification. While addressing critical security concerns may necessitate applying the update promptly, please note:

1. Compatibility Risks: There is a chance of disruptions to replication or recovery processes.
2. Limited Support: Should issues arise, Zerto’s assistance may be restricted to “best efforts” until official certification is finalised.

Balancing Security and Compatibility

Organisations must consider the urgency of resolving critical security vulnerabilities against the potential risks of installing an unsupported update. If an early deployment is unavoidable, undertake thorough testing in a non-production environment and closely monitor the system afterwards. Engage Assurestor for additional guidance, and stay apprised of Zerto’s certification roadmap.

Key Recommendations:

• For patches that do not change the VMware version, proceed normally and consult the Zerto Interoperability Matrix as needed.
• For updates that introduce a new version not yet certified, carefully evaluate security requirements against possible service impacts and implement measures to minimise risk within your DR2Cloud environment.