Flexible recovery topologies

ControlShift supports a variety of on-premises and cloud topologies. Individual DR plans are configured with topologies best suited for the type of DR protection needed for your protected sites. RPO/RTO selection depends on several criteria, including application availability requirements and available DR budgets.

DVX (protected) to DVX (failover)

In a simple 2-site topology, a single DVX System serves as both a backup and failover site. The protected site sends snapshot replicas to the failover site. ControlShift orchestrates instant failover to backup/failover site with no additional data transfer at recovery time.

DVX (protected) to DVX (backup) to DVX (failover)

In a common 3-site topology, the protected site sends snapshot replicas to both the failover site and a backup site (replication schedules and retention policies need not be the same).

When the failover occurs, replication data from the backup site is used to move data to the failover site.

This topology is useful for extra protection, for longer archiving, or as a method of recovering from ransomware attacks that require ‘going back in time’, which a failover site alone might not be able to accommodate.

When executing failover, ControlShift can either use snapshots available on the failover site (zero RTO) or to fetch them from a backup site (with potentially longer RTO).

DVX (protected) to Cloud DVX (backup) to DVX (failover) 1

This is an example of a 3-site topology with a backup site being Cloud DVX (hosted on the public cloud) instead of an on-premises DVX.

When the failover occurs, replication data from the backup site is used to move data to the failover site.

DVX (protected) to Cloud DVX to DVX (backup)

A cost-effective cloud backup and archiving solution that uses a single cloud backup site. It can be used for operational recovery or for disaster recovery in cases where the on-premises hardware remains operational (e.g. disasters due to user errors or ransomware attacks). ControlShift failover will use either the local snapshots available on the failover site (zero RTO) or snapshots stored in Cloud DVX (with longer RTO).

DVX (protected) to Cloud DVX (backup) to DVX (failover)

This example enables recovery from cloud backups even when a disaster destroys the protected on-premises site. A new on-premises system is procured followed by ControlShift failover using snapshots stored on Cloud DVX.

When the failover occurs, replication data from the backup site is used to move data to the failover site.

While the RTO is longer (the snapshots need to be retrieved into the new system), this is a very cost efficient solution that makes recovery possible without maintaining a secondary on-premises DR site.

Datrium DRaaS: DVX (protected) to Cloud DVX (backup) to VMC (failover)

The DRaaS topology combines the economic benefits of eliminating a secondary DR site with the low RTO recovery to the public cloud.

 

Cloud DVX serves as a cloud backup site. Following a disaster event, a failover site is deployed in the public cloud - VMware Cloud on AWS (VMC). A ControlShift plan will perform failover to this newly created cloud failover site.

Individual DR plans can employ different DR topologies tailored to specific use cases. The ControlShift service can maintain a multitude of DR plans employing different topologies with many plans executing concurrently.

In one example, ControlShift manages several different DR plans with multiple on-premises protected sites replicating to cloud backup site Cloud DVX as well as to other on-premises backup and failover sites. Cloud DVX, the second cloud backup site, is bound to Cloud-DR, a cloud failover site deployed on VMware Cloud on AWS. This enables protected on-premises sites such as “HQ” to instantly failover to the public cloud.