...
Abiquo with Zerto Disaster Recovery enables lets you to configure DRaaS in your multi-cloud platform so users can easily protect their VMs in private cloud datacenters with VMware vCenter.
| Warning |
|---|
Abiquo 6.1.x supports Zerto 9.7 U2 on Linux only |
Introduction to DRaaS
The Abiquo DRaaS feature uses Zerto to enable let you to offer self-service disaster recovery as a service and on demand.
This will enable let users to supplement their snapshots and on-demand backups, as part of a fully protected multi-cloud platform.
When users protect VMs, Abiquo creates virtual protection groups (per virtual appliance) and manages VM protection.
| Info |
|---|
Contact Abiquo Customer Service to obtain your separate license for the DRaaS feature with the Zerto plugin. |
In Abiquo 5.2, you You can configure DRaaS for private cloud environments with Zerto and VMware vCenter.
Abiquo supports a Zerto environment where you can protect a datacenter and fail over to a recovery datacenter. See Abiquo and Zerto test environment 
This document is not updated for Zerto 9.7 U2.
To work with Zerto failover in Abiquo, you must configure configure the Zerto plugin in the Abiquo platform using Abiquo configuration properties and - search for zerto in the properties.
To Then to register your Zerto system in Abiquo, create Protection managers .
To control access to this feature, there are two new privileges, and by default only the Cloud cloud administrator role has these privileges.
| Panel |
|---|
Privileges: View and manage protection managers, Manage VM disaster recovery protection |
...
Dashboards
The Abiquo dashboard displays can display the number of VMs the tenant has protected with disaster recovery.
...
To start working with the DRaaS feature, in the Infrastructure view, you can define the a Protection managersmanager. For each protection manager, you will also need a recovery protection manager.
...
It is easy to configure Abiquo to use a standard DRaaS configuration of Zerto Protection Managers for vCenter. See Protection managers
...
When a VM fails over, Zerto should replicate it should be replicated from the production vCenter to the recovery vCenter in the recovery datacenter.
...
In the recovery vCenter, the administrator should create a network for each tenant to use for recovery and failover testing.
When the user protects a VM, the platform will search for the tenant's recovery network by name to add it to the Zerto virtual protection group.
To define the recovery networks for multiple tenants, the administrator should create a base name and register it in the abiquo.properties file. Then, for each tenant the administrator should define a DR-code.
For example, the default network base name is " Draasnet".
And if you had three enterprises called "Enterprise1", "Enterprise2", "Enterprise 3", you could use the DR-codes of "Ent1", "Ent2", and "Ent3".
The network administrator should create networks with the same base name plus the DR-code tenant suffix for each tenant.
So in our example, we would create three networks called: "DraasnetEnt1", "DraasnetEnt2", and "DraasnetEnt3".
The administrator should then edit each Abiquo enterprise and add an enterprise property with the key "DR-code" and the value of the tenant's network suffix.
In this case, for "Enterprise1" it would be "Ent1", and so on for the other enterprises.
See Manage enterprise credentials and properties
...
In order to onboard recovered VMs, you can define the recovery networks in the recovery datacenter in Abiquo.
To capture a VM, you will need to know the network tag of the network that it is in. The easiest networking option is to create an external network as the recovery network for each enterprise.
When you create the external network in the platform, enter the same network tag that you assigned in the infrastructure.
...
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.
If a protection group already exists, the administrator may need to delete it directly in Zerto to enable the user to protect the VM.
...