1. Articles
  2. Hosted Private Cloud
  3. Nutanix
  4. Disaster Recovery

Articles in this section

How to Set Up Advanced Replication and Disaster Recovery with Nutanix

Avatar
Stephanie Richards
  • Updated
Follow

This guide details how to set up advanced replication and disaster recovery plans with Nutanix Disaster Recovery (formerly Leap) in Prism Central.

Introduction

Nutanix Disaster Recovery allows:

  • Asynchronous and synchronous replication based on the chosen license pack
  • Test replicas
  • Advanced disaster recovery plans with virtual machine startup and, in some cases, cluster-to-cluster failover automation (only with synchronous replication and a cluster witness)
  • a destination to the Nutanix cloud with Disaster Recovery (note that this solution is not available with licenses provided by OVHcloud)

Requirements

  • Two Nutanix clusters in your OVHcloud account
  • Access to the OVHcloud Control Panel
  • Access to your clusters via Prism Central
  • An interconnection between two clusters, for example using these technologies:
  • Prism Central needs more resources depending on the mode:
    • Single Mode: 4GB additional RAM.
    • Scale Mode with 3 Prism Central virtual machines: 8 GB additional RAM per virtual machine.

Instructions

Our Disaster Recovery Plan will be set up between two clusters, both of which are located in remote OVHcloud datacenters, one in Datacenter 1 and the other in Datacenter 2. The two clusters are connected by an IPSec VPN with this network configuration:

  • Cluster administration LAN in Datacenter 2: 192.168.0.0/24.

  • Cluster administration LAN in Datacenter 1: 192.168.10.0/24.

  • Production LAN for VMs, common to both clusters: 192.168.50.0/24 on VLAN 50.

  • Test LAN common to both clusters: 192.168.51.0/25 on VLAN 51.

Commissioning of Nutanix Disaster Recovery

Using Prism Central, connect to Prism Element on the cluster in Datacenter 2. You can use the Nutanix Hyperconvergence guide for more information.

In the top left-hand corner of the Prism Element dashboard, click the cluster name.

leap01.png

 

Verify the IP Address in the iSCSI Data Service IP field and click Save.

leap02.png

 

Also via Prism Central, now perform the same operation on the cluster in Datacenter 1.

In the top left-hand corner of the Prism Element dashboard, click the cluster name.

leap03.png

 

Verify the IP Address in the iSCSI Data Service IP field and click Save. 

leap04.png

 

Enabling Disaster Recovery

Go back to the Prism Central interface for the cluster in Datacenter 2.

From the main menu, click the Data Protection section and then Recovery Plans.

leap05.png

 

Click Enable Disaster Recovery.

leap06*.png

 

When you see Prechecks successful, click Enable.

leap07.png

 

Now go back to the Prism Central interface of the cluster in Datacenter 1 and do the same.

Under Data Protection click Recovery Plans.

leap08.png

 

Click Enable Disaster Recovery.

leap06*.png

 

Again, when Prechecks successful appears on the screen, click Enable.

leap07.png

Each cluster now has an Availability zone, which allows them to be interconnected.

 

Connecting both clusters.

Stay on Prism Central in the cluster in Datacenter 1.

From the main menu, click Availability Zones under Administration.

leap09.png

 

Then click Connect to Availability Zone.

leap10.png

 

Enter this information:

  • Availability Zone Type: Physical Location.
  • IP Address for Remote PC: IP address of the remote Prism Central.
  • Username: Remote Central Prism administrator account.
  • Password Remote Central Prism account password.

Then click Connect.

leap11.png

 

The remote cluster is named after the private IP address of the Prism Central in Datacenter 2, preceded by PC_.

leap12.png

 

Connect to the cluster in Datacenter 2 with Prism Central.

From the main menu, click Availability Zones on the Administration submenu.

leap09.png

 

You will see that the remote site in Datacenter 1 appears with the private IP address of the Prism Central in Datacenter 1 preceded by PC_.

leap13.png

 

Implementation of replication from Datacenter 1 to Datacenter 2

NOTE: Virtual machines that will be protected with Nutanix Disaster Recovery should not be members of a Domain Protection created from Prism Element. There is a procedure on the Nutanix website to perform this migration: Migrating from a Domain Protection.

Creating a category containing the virtual machines to replicate

From the main menu, click Categories in the Administration submenu.

leap14.png

 

Click New Category.

leap15.png

 

Enter this information:

  • Name: replicated-vm
  • values: from-Datacenter1

Then click Save.

leap16.png

 

Go back to the main menu and select VMs under Compute and Storage.

leap17.png

 

Select the virtual machine by using the check box to its left, then click the Actions button.

leap18.png

 

In this menu, click Manage Categories.

leap19.png

 

Select the category you created and click the blue + button.

leap20.png

 

Click Save.

leap21.png

 

Creating the protection policy

A protection policy creates a scheduled replication between two Availability zones. You can choose this type of schedule depending on your license:

  • asynchronous every hour
  • nearsync between 1 and 15 minutes
  • synchronous with a delay of 0 seconds (this mode requires a network latency of less than 5ms between the two clusters)

From the main menu, click Protection Policies under Data Protection.

leap22.png

 

Click Create Protection Policy.

leap23.png

 

Enter a name in the Policy name field.

In the Primary location box, choose these options:

  • Location: Local AZ to choose the zone containing the local cluster.
  • Cluster: Cluster containing the virtual machines to be replicated.

Click Save.

leap24.png

 

In the Recovery location frame, choose these options:

  • Location: Remote cluster zone.
  • Cluster: Destination cluster.

Click Save.

leap25.png

 

Then click + Add schedule.

leap26.png

 

Choose Asynchronous as Protection Type.

Change the Take Snapshot Every option to Minutes: 15 to do nearsync replication.

Select the Take App-Consistent Snapshots checkbox and click Save Schedule.

leap27.png

 

Click Next.

leap28.png

 

Select the category where the virtual machine was added and click Add.

leap29.png

 

Click Create.

leap30.png

 

The protection policy is enabled and appears in the Protection Policies dashboard.

leap31.png

 

Disaster Recovery Plan Management

Introduction

Disaster recovery plans can be created with various options:

  • Manually launch the disaster recovery plan if there is no cluster witness.
  • Synchronous replication disaster recovery plan automation with a cluster witness.
  • Choose how virtual machines start when the disaster recovery plan is activated with the ability to run a script.

In our example, this will be a manual disaster recovery plan that includes automatic startup of virtual machines.

Creating Disaster Recovery Plan

From the main menu, choose Recovery Plans under Data Protection.

leap32.png

 

Click Create New Recovery Plan.

leap33.png

 

Enter these values:

  • Recovery Plan Name: the name of the disaster recovery plan.
  • Primary Location: Local AZ to choose the zone containing the local cluster.
  • Recovery Location: Name of the Remote Area that will be used for the disaster recovery plan.

Click Next.

leap34.png

 

Click Add Entities.

leap35.png

 

Select the checkbox next to the virtual machine that is part of the disaster recovery plan, then click Add.

leap36.png

 

Select the checkbox next to the virtual machine that should start automatically when the disaster recovery plan is enabled.

Then click Next.

leap37.png

 

After reviewing the Disaster Recovery Plan presentation, click OK, Got it.

leap38.png

 

On the primary site, choose these options:

  • Production: Production VLAN
  • Test Failback: Test VLAN

On the recovery site, choose these options:

  • Production: Production VLAN
  • Test Failback: Test VLAN

Then click Done.

leap39.png

 

The disaster recovery plan appears in the list.

leap40.png

 

Scheduled migration

Migrating a site from Datacenter 1 to Datacenter 2

Connect with Prism Central on the cluster in Datacenter 2 to switch the virtual machine from Datacenter 1 to Datacenter 2.

From the main menu, choose Recovery Plans in the Data Protection section.

leap41.png

 

Select the disaster recovery plan by using the checkbox to the left of it, then click the Actions button to open the menu.

leap42.png

 

Click Failover.

leap43.png

 

Select Planned Failover as the type of Failover and click the Failover button.

leap44.png

 

Type Failover in the confirmation field and click the Failover button.

leap45.png

 

The migration steps are described below:

  1. Stopping the virtual machine on the original cluster.
  2. Synchronizing the latest changes.
  3. Deleting the virtual machine on the original cluster.
  4. Adding the virtual machine on the destination cluster.
  5. Starting the virtual machine on the destination cluster.

The result of the migration appears in the Last Failover Status column with the status Succeeded if everything went well.

leap46.png

 

Reverse Replication

In the case of scheduled failover, you must reverse replication to continue to have redundancy between the two sites.

Using Prism Central, log in to the destination cluster in Datacenter 2.

From the main menu, choose Protection Policies from the Data Protection submenu.

leap47.png

 

Select the checkbox to the left of the protection policy and click the Actions button.

leap48.png

 

Click the Update button.

leap49.png

 

Move left under Primary Location until a menu appears. Click Edit.

leap50.png

 

Edit the following information in the Primary Location frame:

  • Location: Local AZ
  • Cluster: local area cluster

Then click Save.

leap51.png

 

Click Update Location.

leap52.png

 

Move to the right below the destination until a menu appears. Click Edit.

leap53.png

 

Then edit the following information as part of Recovery Location:

  • Location: destination area.
  • Cluster: cluster of the destination area.

Click Save.

leap54.png

 

Click Update Location.

leap55.png

 

Click Next.

leap56.png

 

Click Update to complete the inversion.

leap57.png

 

Modifying Disaster Recovery Plan

You must also change the disaster recovery plan by reversing the source and destination.

From the main menu, choose Recovery Plans from the Data Protection submenu.

leap58.png

 

Select the disaster recovery plan by using the checkbox to the left of the plan, then click the Actions button.

leap59.png

 

From the actions menu, click Update.

leap60.png

 

In the Primary Location drop-down menu on the left, replace the remote cluster with Local AZ.

leap61.png

 

Choose The remote area in Recovery Location on the right instead of Local AZ.

leap62.png

 

Now that the source and destination of the disaster recovery plan have changed, click Next.

leap63.png

 

 

Click Proceed.

leap64.png

 

Select the Virtual Machine that you want to start during the disaster recovery plan and click Next.

leap65.png

 

On the primary site, choose these options:

  • Production: Production VLAN
  • Test Failback: Test VLAN

At the destination site, choose these options:

  • Production: Production VLAN
  • Test Failover: Test VLAN

Then click Done.

leap66.png

 

The disaster recovery plan has been modified to allow the virtual machines in the cluster to be switched from the French to the Canadian virtual machines.

If you want to return to the original operation, you will need to failover, change replication, and change the disaster recovery plan.

leap67.png

 

Enabling a disaster recovery plan following an incident on the original cluster

The disaster recovery plan is also used in the event of a problem with the original cluster. In this case, the activation will be done without the data modified since the last synchronization.

If a synchronous replication solution is used, no data loss will occur.

In our case, replication is scheduled every 15 minutes, the risk of data loss can, in the worst case, corresponds to this duration.

From Prism Central, connect to the cluster that is receiving replicas.

From the main menu, choose Recovery Plan from the Data Protection submenu.

leap68.png

 

Select the Disaster Recovery Plan with the checkbox and click the Actions button.

leap69.png

 

Choose Failover from the menu.

leap70.png

 

Check Unplanned Failover and click Failover.

leap71.png

 

Type Failover in the confirmation field and click Failover.

leap72.png

The virtual machine that is a member of the disaster recovery plan will boot to the destination cluster with the contents of the last replication.

 

Go further

For more information and tutorials, please see our other Nutanix support guides or explore the guides for other OVHcloud products and services.

Related articles