...
When a VM fails over, it should be replicated from one the production vCenter (production) to another (the recovery )vCenter.
Each protection manager works with a single vCenter and each Abiquo virtual datacenter works with a single vCenter. This means that administrators do not need to link protection managers with virtual datacenters in Abiquo. Each protection manager can cover the group of Abiquo virtual datacenters with VMs in the same vCenter. For configuration reasons, the administrator should assign Available datacenters, which is where the users can access the protection managers. The platform will use the NARS remote service from an available datacenter to manage Zerto.
You can later edit the protection manager if you need to make changes.
...
Tenant networks
Within For the recovery vCenter, the administrator should create a network for each tenant to use for recovery and failover testing. To enable a multi-tenant Zerto environment, the administrator should create all the networks with the same base name and a tenant suffix for each tenant. They An administrator must configure the base name of the network in abiquo.properties. The Cloud administrator should then edit the each Abiquo enterprise and add an enterprise property with the key "DR-code" and a value of the tenant's network suffix.
...
Behind the scenes, the platform creates Zerto Protection Groups. The Zerto Protection Group are transparent to the Abiquo user and initially, Abiquo creates one Protection Group for the VMs in each Abiquo virtual appliance. Abiquo does not make changes to protection groups and the user cannot move a DR protected VM to another Virtual appliance.
On the VM icon, if the VM is protected, the DRaaS shield symbol is drawn with a darker line.
...