Article number
000004374
Affected Versions
All
Source Hypervisor
All
How to Work Around Some Third-party Solutions Simultaneously with Zerto
Viewed 398 times
Summary
The use of third-party data replication products such as EMC RecoverPoint will interfere with the proper functionality of Zerto Virtual Replication by locking the virtual disks or VMDK files of protected virtual machines.
This will cause them to not be available to Zerto to be protected through replication if the other replication product is replicating their data at the same time.
Customers therefore must only use Zerto for replication in the same environment.
Products that do not use a replication framework but rather a snapshot-based mechanism such as Veeam will not interfere.
However, Veeam backup jobs running at certain times may cause RPO spikes with Zerto due to increased network bandwidth usage.
This will cause them to not be available to Zerto to be protected through replication if the other replication product is replicating their data at the same time.
Customers therefore must only use Zerto for replication in the same environment.
Products that do not use a replication framework but rather a snapshot-based mechanism such as Veeam will not interfere.
However, Veeam backup jobs running at certain times may cause RPO spikes with Zerto due to increased network bandwidth usage.
Target Audience
Customers/Internal
Notice
The use of third-party data replication products such as EMC RecoverPoint will interfere with the proper functionality of Zerto Virtual Replication by locking the virtual disks or VMDK files of protected virtual machines.
This will cause them to not be available to Zerto to be protected through replication if the other replication product is replicating their data at the same time.
Customers therefore must only use Zerto for replication in the same environment.
Products that do not use a replication framework but rather a snapshot-based mechanism such as Veeam will not interfere.
However, Veeam backup jobs running at certain times may cause RPO spikes with Zerto due to increased network bandwidth usage then.
This will cause them to not be available to Zerto to be protected through replication if the other replication product is replicating their data at the same time.
Customers therefore must only use Zerto for replication in the same environment.
Products that do not use a replication framework but rather a snapshot-based mechanism such as Veeam will not interfere.
However, Veeam backup jobs running at certain times may cause RPO spikes with Zerto due to increased network bandwidth usage then.
Steps
If a third party solution is installed and trying to lock up virtual disks or VMDKs of VMs to be protected, disable or dissociate the third party solution allowing only Zerto to use for replication.
In a scenario where another product was used, please see the following KB on how to dissociate VMs as an example: How to Dissociate VMs from Previously Used Replication Products
NOTE: The above is just an example and other vendor products may have a different process. Please refer to the third party vendor support to assist as needed.
In a scenario where another product was used, please see the following KB on how to dissociate VMs as an example: How to Dissociate VMs from Previously Used Replication Products
NOTE: The above is just an example and other vendor products may have a different process. Please refer to the third party vendor support to assist as needed.