Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

hiddentrue

Abiquo 5.2 introduces the DRaaS feature with an initial integration of Zerto into the multi-cloud platform to provide self-service disaster recovery on demand for your users

...

.

...


Abiquo 5.2 introduces the DRaaS feature with an initial integration of Zerto into the multi-cloud platform to provide self-service disaster recovery on demand for your users. This will complement the existing Backup as a Service feature and enable you to provide a more complete Managed Services platform. 

Table of Contents

...

Introduction to DRaaS - Disaster recovery as a service

...

The Abiquo dashboard displays the number of VMs the tenant has protected with disaster recovery.

As usual administrators can set limits for the DRaaS feature.
In this case they can set limits at the tenant, tenant in datacenter, and VDC levels on the number of VMs that users can protect with disaster recovery as a service.

...

To start working with the DRaaS feature, in the Infrastructure view, you can define the Protection managers. For  
For each protection manager, you will also need a recovery protection manager.

...

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.
The platform will use the NARS remote service from an available datacenter to manage Zerto.

...

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.
An administrator must configure the base name of the network in abiquo.properties.
The Cloud administrator should then edit 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.

...

In this version, the administrator must perform failover tests and failovers directly in Zerto.
After a failover, the administrator may capture the VM into Abiquo in the recovery datacenter.
In order to do this, the administrator must configure the use of duplicate VM names in the abiquo.properties file.
Before the administrator captures a recovered VM, they may also wish to create an external network in Abiquo to represent the tenant's recovery network.

...