--- title: "Configurando a recuperação de desastres com o Metro (EN)" description: "Implementing Metro for a Disaster Recovery Plan" url: https://docs.ovhcloud.com/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/metro-availability lang: pt lastUpdated: 2024-05-13 --- # Configurando a recuperação de desastres com o Metro (EN) ## Objective **This guide introduces Metro Availability, which provides an automated disaster recovery plan.** :::warning OVHcloud provides services for which you are responsible, with regard to their configuration and management. It is therefore your responsibility to ensure that they work properly. This guide is designed to assist you as much as possible with common tasks. Nevertheless, we recommend contacting a specialist provider if you experience any difficulties or doubts when it comes to managing, using or setting up a service on a server. ::: ## Requirements - Access to the OVHcloud Control Panel - Access to your clusters via Prism Central - You need to have 3 Nutanix clusters within the OVHcloud infrastructure with **Pro** or **Ultimate** packs if you have a Nutanix on OVHcloud packaged service on both clusters in the P.R.A. These 3 clusters will need to be at remote sites for maximum security. - You must have less than 5 ms of latency between the two replicated clusters. Please note that latency is not covered by SLAs. ## Introduction We will set up a two-way disaster recovery plan between two clusters with this hardware: - A Nutanix cluster in Roubaix, France, with virtual machines replicated in Gravelines. - A Nutanix cluster in Gravelines, France, with virtual machines replicated in Roubaix. - A Nutanix cluster in Erith, England with Prism Central to serve as a witness in the disaster recovery plan. We will only use one vRack, which will contain: - The three Nutanix clusters. - Load balancers. - Additional IP addresses on the **rtvRack**. Below is the diagram showing the three sites: ![00 - Metro Availability Diagram 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/00-metro-availability-diagram01.png) ## Instructions - [Step 1 Configuration](#configuration) - [Step 1.1 Interconnection of the three clusters](#connectcl) - [Step 1.2 Delete the Prism Central records for the Roubaix and Gravelines clusters](#delpc) - [Step 1.3 Register both clusters on Prism Central in Erith](#regpc) - [Step 1.4 Adding IP Addresses for iSCSI Connections on All Three Clusters](#configiscsi) - [Step 1.5 Creating two Storage Containers](#addsc) - [Step 1.6 Move virtual machines to the Storage Container](#movevm) - [Step 1.7 Creation of a category to be used when implementing the P.R.A.](#creacat) - [Step 1.8 Add virtual machines in categories](#addvmcat) - [Step 1.9 Setting up synchronous replications between Roubaix and Gravelines](#confreplsync) - [Step 1.10 Create Subnets for Disaster Recovery Plan](#addsublan) - [Step 1.11 Implementation of disaster recovery plans](#adddr) - [Step 2 - Validate Disaster Recovery Plan](#validation) - [Step 2.1 Monitoring the Disaster Recovery Plan](#ctrldr) - [Step 2.2 Live migration of virtual machines from Roubaix to Gravelines](#livemigration) - [Step 2.3 Operations after a migration](#aftermigration) - [Step 2.4 Execute the Disaster Recovery Plan in Real Condition](#epmcr) We will implement this disaster recovery plan step by step. The cluster configuration information used in our guide is as follows: - Roubaix cluster: - Server 1: VM address **CVM** `192.168.0.21`, hypervisor IP address **AHV** `192.168.0.1`. - Server 2: VM address **CVM** `192.168.0.22`, hypervisor IP address **AHV** `192.168.0.2`. - Server 3: VM address **CVM** `192.168.0.23`, hypervisor IP address **AHV** `192.168.0.3`. - Prism Element virtual address: `192.168.0.100`. - Prism Element iSCSI address: `192.168.0.102`. - Prism Central IP address: `192.168.0.101`. - Gateway: `192.168.3.254`. - Mask: `255.255.252.0` - Cluster version: `6.5` - Gravelines cluster: - Server 1: VM address **CVM** `192.168.1.21`, hypervisor IP address **AHV** `192.168.1.1`. - Server 2: VM address **CVM** `192.168.1.22`, hypervisor IP address **AHV** `192.168.1.2`. - Server 3: VM address **CVM** `192.168.1.23`, hypervisor IP address **AHV** `192.168.1.3`. - Prism Element virtual address: `192.168.1.100`. - Prism Element iSCSI address: `192.168.1.102`. - Prism Central IP address: `192.168.1.101`. - Gateway: `192.168.3.254`. - Mask: `255.255.252.0` - Cluster version: `6.5`. - Erith Cluster: - Server 1: VM address **CVM** `192.168.2.21`, hypervisor IP address **AHV** `192.168.2.1`. - Server 2: VM address **CVM** `192.168.2.22`, hypervisor IP address **AHV** `192.168.2.2`. - Server 3: VM address **CVM** `192.168.2.23`, hypervisor IP address **AHV** `192.168.2.3`. - Prism Element virtual address: `192.168.2.101`. - Prism Element iSCSI address: `192.168.2.102`. - Prism Central IP address: `192.168.2.100`. - Gateway: `192.168.3.254`. - Mask: `255.255.252.0` - Cluster version: `6.5`. In addition to this guide, you can use these documents: - [Nutanix hyperconvergence](/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/nutanix-hci.md) - [advanced tools](/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/advanced-tools.md) [](#) ### Step 1 - Configuration [](#) #### Step 1.1 - Interconnection of the three clusters The first step is to interconnect the three clusters on the same OVHcloud vRack. Use this guide to connect your clusters: [Interconnect clusters through the vRack](/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/vrack-interconnection.md). To connect the three clusters, use the instructions provided in the guide: - Roubaix clusters in the vRack dedicated to Gravelines. - Erith clusters in the vRack dedicated to Gravelines. When you have finished configuring your vRack, you will have these elements in your vRack: - 9 dedicated servers (3 per cluster) - 3 public IP addresses - 3 Load Balancers ![01 - vRack Configuration 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/01-vrack-configuration01.png) The three clusters are currently accessible from the Prism Central URL of each cluster. [](#) #### Step 1.2 - Delete the Prism Central records for the Roubaix and Gravelines clusters To implement a disaster recovery plan solution with **Metro Availability**, a cluster witness is required to automate tasks in the event of one of the clusters becoming unavailable. The cluster witness is located on a Prism Central virtual machine. The Erith cluster will host the Prism Central virtual machine for the three clusters, and serve as a cluster witness for the disaster recovery plan between Roubaix and Gravelines. ##### **Disabling Prism Central on the Roubaix cluster** Connect via SSH to the Prism Element cluster in Roubaix: ```bash ssh nutanix@private_ip_address_prism_element_Roubaix Enter Prism Element password ``` Run this command to remove Prism Element from the Prism Central configuration: ```bash ncli multicluster remove-from-multicluster external-ip-address-or-svm-ips=private_ip_address_central_roubaix\ username=admin password=pwd_pe_Roubaix force=true ``` This message appears when disconnecting from Prism Central. ```console Cluster unregistration is currently in progress. This operation may take a while. ``` Enter this command: ```bash ncli cluster info ``` Note the value of the **Cluster UUID** that must have this form **xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx**. Disconnect from Prism Element and connect via SSH on the Prism Central virtual machine in Roubaix. ```bash ssh nutanix@private_ip_address_prism_central_roubaix Enter Prism Central password ``` Enter this command: ```bash python /home/nutanix/bin/unregistration_cleanup.py cluster_uuid_prism_element_Roubaix ``` ##### **Disabling Prism Central on the Gravelines cluster** Log in to the Prism Element cluster in Gravelines via SSH. ```bash ssh nutanix@private_ip_address_prism_element_Gravelines Enter Prism Element password ``` Enter this command: ```bash ncli multicluster remove-from-multicluster external-ip-address-or-svm-ips=private_ip_address_prism_central_Gravelines\ username=admin password=pwd_pe_Gravelines force=true ``` This message appears when disconnecting from Prism Central. ```console Cluster unregistration is currently in progress. This operation may take a while. ``` Enter this command: ```bash ncli cluster info ``` Note the value of **Cluster UID** that should be in this form **xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx** Disconnect from Prism Element and connect via SSH on the Prism Central virtual machine in Gravelines. ```bash ssh nutanix@private_ip_address_prism_central_Gravelines enter Prism Central password python /home/nutanix/bin/unregistration_cleanup.py cluster_uuid_prism_element_Gravelines ``` [](#) #### Step 1.3 - Registration of the two clusters on the Prism Central in Erith Log in to the Prism Element in Roubaix via SSH: ```bash ssh nutanix@private_ip_address_prism_element_Roubaix enter Prism Element password ``` Run this command: ```bash ncli multicluster register-to-prism-central username=admin password=passwod_admin\ external-ip-address-or-svm-ips=private_ip_address_prism_central_Erith ``` This message appears: ```console Cluster registration is currently in progress. This operation may take a while. ``` Wait and enter this command: ```bash ncli multicluster get-cluster-state ``` If the cluster is connected to Prism Central in Erith, you will see this information: ```console Registered Cluster Count: 1 Cluster Id : xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx Cluster Name : Prism-Central-Erith-FQDN Is Multicluster : true Controller VM IP Addre... : [private_ip_address_prism_central_Erith] External or Masqueradi... : Cluster FQDN : Controller VM NAT IP A... : Marked for Removal : false Remote Connection Exists : true ``` Log in to Prism Element in Gravelines via SSH: ```bash ssh nutanix@adresse_ip_prism_element_Gravelines Enter Prism Element password from Gravelines ``` Run this command: ```bash ncli multicluster register-to-prism-central username=admin password=passwod_admin_Erith external-ip-address-or-svm-ips=private_ip_address_central_Erith ``` This message appears: ```console Cluster registration is currently in progress. This operation may take a while. ``` Wait and enter this command: ```bash ncli multicluster get-cluster-state ``` If the cluster is connected to the Prism Central in Erith, you will see this information: ```console Registered Cluster Count: 1 Cluster Id : xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx Cluster Name : Prism-Central-Erith-FQDN Is Multicluster : true Controller VM IP Addre... : [private_ip_address_prism_central_Erith] External or Masqueradi... : Cluster FQDN : Controller VM NAT IP A... : Marked for Removal : false Remote Connection Exists : true ``` From a web browser, log in to the URL from Prism-Central to Erith, you will see the three clusters. ![02 - Prism Central Dashboard 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/02-show-prismcentral01.png) The Prism Central virtual machines in Gravelines and Roubaix are no longer being used. You can stop them. In the main menu, click `Vms ` in the **Compute & Storage** submenu. ![02b - Shutdow Prism Central Gravelines Roubaix 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/02-shutdown-prism-central01.png) Select the Prism Central virtual machines in Gravelines and Roubaix and click `Guest Shutdown ` from the `Actions ` menu. ![02b - Shutdow Prism Central Gravelines Roubaix 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/02-shutdown-prism-central02.png) [](#) #### Step 1.4 - Adding IP Addresses for iSCSI Connections on All Three Clusters From the Prism Central dashboard, click the link to the `Erith cluster ` . ![03 - Add iscsi address Erith 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-erith01.png) On the Prism Element dashboard, click the `cluster name ` in the top left-hand corner. ![03 - Add iscsi address Erith 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-erith02.png) Scroll down the window and check the IP address in `ISCSI Data Services IP`. ![03 - Add iscsi address Erith 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-erith03.png) From the Prism Central dashboard, click the link to the "Gravelines cluster". ![03 - Add iscsi address Gravelines 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-gravelines01.png) On the Prism Element dashboard, click "the cluster name" in the top left-hand corner. ![03 - Add iscsi address Gravelines 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-gravelines02.png) Scroll down the window and check the IP address in `ISCSI Data Services IP`. ![03 - Add iscsi address graveline 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-gravelines03.png) From the Prism Central dashboard, click on the link to the "Roubaix cluster". ![03 - Add iscsi address Roubaix 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-roubaix01.png) On the Prism Element dashboard, click the "cluster name" in the top left-hand corner. ![03 - Add iscsi address Roubaix 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-roubaix02.png) Scroll down the window and check the IP address in `ISCSI Data Services IP`. ![03 - Add iscsi address Roubaix 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/03-add-iscsi-address-roubaix03.png) [](#) #### Step 1.5 - Creating Two Storage Containers We will create two Storage Containers with the same name, one in Roubaix and the other in Gravelines. From the Prism Element main menu, click `Storage Containers ` in the `Compute & Storage ` submenu. ![05 - Add-storage-container 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/05-add-storage-container01.png) Click `Create Storage Container `. ![05 - Add-storage-container 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/05-add-storage-container02.png) Type `UsedForDR` in **Name** , choose the Roubaix `cluster` in **Cluster** , and click `Create `. ![05 - Add-storage-container 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/05-add-storage-container03.png) Click `Create Storage Container `. ![05 - Add-storage-container 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/05-add-storage-container04.png) Type `UsedForDR` in **Name** , choose the **Gravelines cluster** in `Cluster` , and click `Create `. ![05 - Add-storage-container 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/05-add-storage-container05.png) In the list of `Storage Containers`, you will see two Storage Containers with the same name. One on the Roubaix cluster and the other on the Gravelines cluster. ![05 - Add-storage-container 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/05-add-storage-container06.png) [](#) #### Step 1.6 - Moving virtual machines to the Storage Container We will move the virtual machine storage to the `Storage Container` we have created. Connect via SSH on the Prism Element of the Roubaix cluster: ```bash ssh nutanix@private_ip_address_Prism_element_Roubaix Enter the Nutanix account password of Prism Element ``` Run this command for each VM we will move to the `Storage Container`, replacing **vmname** with the name of the virtual machine (in our disaster recovery plan, we have two virtual machines in Roubaix, one on Windows and one on Linux). ```bash acli vm.update_container vmname container=UsedForDR Enter the Nutanix account password of Prism Element ``` Log in to the Prism Element of the Gravelines cluster via SSH: ```bash ssh nutanix@private_ip_address_Prism_element_Gravelines Enter the Nutanix account password of Prism Element ``` Execute this command for each VM that we will move to the `Storage Container`, replacing **vmname** with the name of the virtual machine (in our disaster recovery plan, we have three virtual machines in Gravelines, one on Windows, another on Linux and the gateway that gives access to the Internet). ```bash acli vm.update_container vmname container=UsedForDR Enter the Nutanix account password of Prism Element ``` [](#) #### Step 1.7 - Creation of a category to be used when implementing the P.R.A We will create a category with two values in Prism Central to assign the virtual machines involved in replication. Scroll through the main menu, click `Categories ` on the `Administration ` submenu. ![06 - Add Categorie 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/06-add-categories01.png) Click `New Category `. ![06- Add Categorie 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/06-add-categories02.png) Type `Protected VM` in **Name** , add the `Roubaix` and `Gravelines` values in **Values** and click on the next button `Save `. ![06 - Add Categorie 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/06-add-categories03.png) The category appears in the list and is ready to use. ![06 - Add Categorie 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/06-add-categories04.png) [](#) #### Step 1.8 - Adding virtual machines in categories We will assign two virtual machines on the Roubaix cluster in one category and three virtual machines on the Gravelines cluster in another category. From the Prism Central main menu, click `Vms ` in the `Compute & Storage ` submenu. ![07 - Add Categorie to VM Roubaix 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/07-add-categorie-to-vm-roubaix01.png) **Select the two virtual machines** in Roubaix on the left, then on the `Actions ` menu, click `Manage Categories `. ![07 - Add Categorie to VM Roubaix 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/07-add-categorie-to-vm-roubaix02.png) Add the category `ProtectedVM: Roubaix` , then click `Save `. ![07 - Add Categorie to VM Roubaix 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/07-add-categorie-to-vm-roubaix03.png) Select `the three virtual machines ` in Gravelines on the left, and on the `Actions ` menu, click `Manage Categories `. ![08 - Add Categorie to VM Gravelines 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/08-add-categorie-to-vm-gravelines01.png) Add the category `ProtectedVM: Gravelines` , then click `Save `. ![08 - Add Categorie to VM Gravelines 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/08-add-categorie-to-vm-gravelines02.png) [](#) #### Step 1.9 - Setting up synchronous replications between Roubaix and Gravelines Synchronous replication allows permanent replication with 0 seconds of data loss. ##### **Replication setup between Roubaix and Gravelines** On the Prism Central main menu, click `Protection Policies ` in the `Data Protection ` submenu. ![09 - Create Protection Policy Roubaix 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix01.png) Click `Create Protection Policy `. ![09 - Create Protection Policy Roubaix 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix02.png) Type `ROUBAIX-TO-GRAVELINES` in **Policy name** , keep `Local AZ` , and click `Select Cluster ` in **Primary Location** . ![09 - Create Protection Policy Roubaix 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix03.png) Choose the Roubaix cluster and click `Save `. ![09 - Create Protection Policy Roubaix 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix04.png) In the top left-hand corner next to **Disaster Recovery** , click `Enable `. ![09 - Create Protection Policy Roubaix 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix05.png) The system checks that everything is correct before enabling **Disaster Recovery**. ![09 - Create Protection Policy Roubaix 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix06.png) Click `Enable ` to enable the **Disaster Recovery** option. ![09 - Create Protection Policy Roubaix 07](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix07.png) Click `Enable ` again. ![09 - Create Protection Policy Roubaix 07](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix08.png) Your **Disaster Recovery** option is being activated. Keep `Local AZ` , select the cluster in **Recovery Location** and click `Save `. ![09 - Create Protection Policy Roubaix 08](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix09.png) Click `\+ Add Schedule `. ![09 - Create Protection Policy Roubaix 10](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix10.png) Choose `Synchronous ` for **Protection Type** and `Automatic ` for **Failure Detection Mode** . Then click `Save Schedule `. ![09 - Create Protection Policy Roubaix 11](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix11.png) Click `Next `. ![09 - Create Protection Policy Roubaix 12](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix12.png) Select the category `ProtectedVM : Roubaix ` and click `Add `. ![09 - Create Protection Policy Roubaix 13](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix13.png) Click `Create `. ![09 - Create Protection Policy Roubaix 14](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix14.png) Virtual machines in Roubaix are now replicated to Gravelines. You must wait for a first full replication to have permanent replication. ![09 - Create Protection Policy Roubaix 15](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/09-create-data-protection-roubaix15.png) ##### **Replication setup between Gravelines and Roubaix** Replication can be two-way. We will now create replication from Gravelines to Roubaix. Click `Create Protection Policy `. ![10 - Create Protection Policy Gravelines 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines01.png) Choose as name `GRAVELINES-TO-ROUBAIX` in **Policy Name** , keep `Local AZ` and choose Gravelines cluster in **Primary Location** . Then click `Save `. ![10 - Create Protection Policy Gravelines 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines02.png) Keep **Local AZ** , select the Roubaix cluster and click `Save `. ![10 - Create Protection Policy Gravelines 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines03.png) Click `\+ Add Schedule `. ![10 - Create Protection Policy Gravelines 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines04.png) Choose `Synchronous ` for **Protection Type** and `Automatic ` for **Failure Detection Mode** . Then click `Save Schedule `. ![10 - Create Protection Policy Gravelines 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines05.png) Click `Next `. ![10 - Create Protection Policy Gravelines 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines06.png) Select the category `ProtectedVM: Gravelines ` and click `Add `. ![10 - Create Protection Policy Gravelines 07](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines07.png) Click `Create `. ![10 - Create Protection Policy Gravelines 08](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines08.png) A second protection strategy is in place. ![10 - Create Protection Policy Gravelines 09](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/10-create-data-protection-gravelines09.png) [](#) #### Step 1.10 - Create Subnets for Disaster Recovery Plan We will create subnets that will be used to test disaster recovery plans. For each existing subnet, a test network is required. On the two clusters of the Disaster Recovery Plan, we have three production subnets. - **based** on VLAN 0. - **infrastructure** on VLAN 1. - **production** on VLAN 2. We will therefore create 3 additional subnets on the Gravelines and Roubaix clusters with these names: - **testing** on VLAN 100. - **testinfra** on VLAN 101. - **production** on VLAN 102. Use this guide to create VLANs on your Nutanix clusters: [isolate production management machines](/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/isolate-management-vm.md). In the Prism Central `Subnets` dashboard, you will see six new subnets. ![11 - Create Test Subnet 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/11-create-testsubnet01.png) [](#) #### Step 1.11 - Implementation of disaster recovery plans Now that the replications and subnets are in place, we will implement automated or manual disaster recovery plans on demand to: - migrate virtual machines on the fly between the two clusters - Test that replication is working properly - Automatically restart the VMs that are members of the P.R.A in the event of a failure of one of two clusters. ##### **Creation of a disaster recovery plan for the Roubaix cluster** In the main menu of Prism Central, click `Recovery Plans ` in the `Data Protection ` submenu. ![12 - Create Recovery Plan Roubaix 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan01.png) Click on `Enable Disaster Recovery ` on the left. ![12 - Create Recovery Plan Roubaix 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan02.png) Normally, the recovery plan must be activated as indicated with the message **Disaster Recovery enabled** . Click on the **right to close this window. ![12 - Create Recovery Plan Roubaix 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan03.png) Click `Create New Recovery Plan `. ![12 - Create Recovery Plan Roubaix 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan04.png) Choose this information: - **Recovery Plan Name**: `Recovery VM from ROUBAIX to GRAVELINES`. - **Primary Location**: `Local AZ`. - **Primary Cluster**: `cluster in Roubaix`. - **Recovery Location**: `Local AZ`. - **Recovery Cluster**: `cluster in Gravelines`. - **Failure Execution Mode**: `Automatic`. - **Execute failover after disconnectivity of**: `30 seconds`. Then click `Next `. ![12 - Create Recovery Plan Roubaix 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan05.png) Click `\+ Add VM(s) `. ![12 - Create Recovery Plan Roubaix 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan06.png) Select both virtual machines and click `Add `. ![12 - Create Recovery Plan Roubaix 07](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan07.png) Click `Next `. ![12 - Create Recovery Plan Roubaix 08](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan08.png) Click `OK. Got it `. ![12 - Create Recovery Plan Roubaix 09](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan09.png) Click `Stretch networks `. ![12 - Create Recovery Plan Roubaix 10](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan10.png) Click `Proceed `. ![12 - Create Recovery Plan Roubaix 11](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan11.png) Choose the VLANs that will be used during the IP like this: - **Primary** - **Production** : `production` - **Test Failback** : `testproduction` - **Recovery** - **Production** : `production` - **Test Failback** : `testproduction` Then click `Done `. ![12 - Create Recovery Plan Roubaix 12](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan12.png) ##### **Creation of a disaster recovery plan for the Roubaix cluster** The Disaster Recovery Plan has been created for the Roubaix site. Click `Create Recovery Plan ` to create the Gravelines Disaster Recovery Plan. ![12 - Create Recovery Plan Roubaix 13](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/12-create-roubaix-recovery-plan13.png) Choose this information: - **Recovery Plan Name**: `Recovery VM from Gravelines to Roubaix`. - **Primary Location**: `Local AZ`. - **Primary Cluster**: `cluster in Gravelines`. - **Recovery Location**: `Local AZ`. - **Recovery Cluster**: `cluster in Roubaix`. - **Failure Execution Mode**: `Automatic`. - **Execute failover after disconnectivity of**: `30 seconds`. Then click `Next `. ![13 - Create Recovery Plan Gravelines 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan01.png) Click `\+ Add VM(s) `. ![13 - Create Recovery Plan Gravelines 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan02.png) Select the three virtual machines and click `Add `. ![13 - Create Recovery Plan Gravelines 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan03.png) Click `Next `. ![13 - Create Recovery Plan Gravelines 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan04.png) Click `Stretch networks `. ![13 - Create Recovery Plan Gravelines 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan05.png) Click `Proceed `. ![13 - Create Recovery Plan Gravelines 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan06.png) Choose this information: - **Primary** - **Production**: `basis` - **Failback** test: `test` - **Recovery** - **Production**: `basis` - **Failback** test: `test` Then click `\+ Add Network Mapping `. ![13 - Create Recovery Plan Gravelines 07](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan07.png) Choose this information: - **Primary** - **Production** : `infra` - **Test Failback** : `testinfra` - **Recovery** - **Production** : `infra` - **Test Failback** : `testinfra` Then click `\+ Add Network Mapping `. ![13 - Create Recovery Plan Gravelines 08](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan08.png) Choose this information: - **Primary** - **Production** : `production` - **Test Failback** : `testproduction` - **Recovery** - **Production** : `production` - **Test Failback** : `testproduction` Then click `Done `. ![13 - Create Recovery Plan Gravelines 09](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan09.png) :::info 3 networks have been added to this disaster recovery plan because the Gateway virtual machine uses these three networks. ::: Both disaster recovery plans are in production. ![13 - Create Recovery Plan Gravelines 10](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/13-create-gravelines-recovery-plan10.png) [](#) ### Step 2 - Validate Disaster Recovery Plan [](#) #### Step 2.1 - Monitoring the Disaster Recovery Plan ##### **Using the Commit to Disaster Recovery Plan Option** You can validate the disaster recovery plan via Prism Central. Click on the `Recovery VM from Roubaix ` to validate and test. ![14 - Validate test recovery plan 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan01.png) Click `Validate ` ![14 - Validate test recovery plan 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan02.png) Select the Roubaix cluster for **Entity Failing Over From** and the Gravelines cluster for **Entity Failing Over To** . Then click `Proceed ` ![14 - Validate test recovery plan 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan03.png) The recovery plan has been validated. Click `Close ` ![14 - Validate test recovery plan 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan04.png) ##### **Test Disaster Recovery Plan** We can test the disaster recovery plan without impacting production. The test creates virtual machines with different names on the destination cluster in the VLANs created earlier. Click `Test `. ![14 - Validate test recovery plan 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan05.png) Select the Roubaix cluster for **Entity Failing Over From** and the Gravelines cluster for **Entity Failing Over To** . Then click `Test `. ![14 - Validate test recovery plan 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan06.png) :::info Make sure you have the right licences if you have chosen the Nutanix on OVHcloud packaged service. You need to have signed up to the **Pro** or **Ultimate** packs for the Roubaix and Gravelines clusters.. ::: Click `Execute Anyway `. ![14 - Validate test recovery plan 07](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan07.png) Go to the VM dashboard in Prism Central and you will see the test virtual machines that are created with the replicated data. ![14 - Validate test recovery plan 08](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan08.png) Return to your recovery plan and click `Clean-up test entities ` to remove the test virtual machines. ![14 - Validate test recovery plan 09](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan09.png) Click `Clean Up ` ![14 - Validate test recovery plan 10](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/14-validate-test-recovery-plan10.png) [](#) #### Step 2.2 - Live migration of Roubaix virtual machines in Gravelines On a fully operational infrastructure, it is possible to move virtual machines from one cluster to another without any service downtime. Go to a virtual machine in Roubaix that is part of the recovery plan. We will ping the OVHcloud DNS server **213.186.33.99**. ![15 - Roubaix to Gravelines 00 delivery](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/15-livemigration-roubaix-to-gravelines00.png) Return to your recovery plan and click `Failover ` on the `More ` menu. ![15 - Roubaix to Gravelines 01 delivery](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/15-livemigration-roubaix-to-gravelines01.png) Choisissez `Planned Failover `, cochez `Live Migrate Entities `. Take the Roubaix cluster for **Entity Failing Over From** and the Gravelines cluster for **Entity Failing Over To**. Then click `Failover `. ![15 - Roubaix to Gravelines 02 delivery](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/15-livemigration-roubaix-to-gravelines02.png) Type `Failover` and click `Failover `. ![15 - delivery Roubaix to Gravelines 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/15-livemigration-roubaix-to-gravelines03.png) Hot migration is in progress. ![15 - Roubaix to Gravelines 04 delivery](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/15-livemigration-roubaix-to-gravelines04.png) The migration was completed successfully without any service downtime. ![15 - Roubaix to Gravelines 05 delivery](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/15-livemigration-roubaix-to-gravelines05.png) You can go back to the virtual machine and see that the ping continues to work even if the virtual machine has been moved from one cluster to another. ![15 - delivery Roubaix to Gravelines 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/15-livemigration-roubaix-to-gravelines06.png) [](#) #### Step 2.3 - Operations after a hot migration After a migration, it is necessary to reverse the replication and operation of the disaster recovery plan. ##### **Reverse Replication** On the Prism Central main menu, click `Protections Policies ` in the `Data Protection ` submenu. ![16 - invert replication after failover 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover01.png) Click on the protection plan named `ROUBAIX TO GRAVELINES `. ![16 - invert replication aftr failover 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover02.png) Click `Update `. ![16 - invert replication after failover 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover03.png) Position the mouse below the Roubaix cluster name in **Primary Location** and click `Edit `. ![16 - invert replication after failover 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover04.png) Check the `Gravelines ` cluster instead of the Roubaix cluster. ![16 - invert replication after failover 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover05.png) Click `Save `. ![16 - invert replication after failover 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover06.png) Click `Update Location `. ![16 - invert replication after failover 07](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover07.png) Position the mouse below the Gravelines cluster name in **Recovery Location** and click `Edit `. ![16 - invert replication after failover 08](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover08.png) Select the `Roubaix ` cluster instead of the Gravelines cluster. ![16 - invert replication after failover 09](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover09.png) Click `Save `. ![16 - invert replication after failover 10](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover10.png) Click `Update Location `. ![16 - invert replication after failover 11](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover11.png) Click `Next `. ![16 - invert replication after failover 12](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover12.png) Click `Update `. ![16 - invert replication after failover 12](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/16-invert-replication-after-failover13.png) Replication is reversed, click the button **to close the protection plan. ##### **Disaster Recovery Plan Reverse** In the main menu of Prism Central, click `Recovery Plans ` in the `Data Protection ` submenu. ![17 - invert recovery plan after failover 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/17-invert-recovery-plan-after-failover01.png) Click `Recovery VM from Roubaix to Gravelines `. ![17 - invert recovery plan after failover 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/17-invert-recovery-plan-after-failover02.png) On the `More ` menu, click `Update `. ![17 - invert recovery plan after failover 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/17-invert-recovery-plan-after-failover03.png) In **locations** , put the Gravelines cluster in **Primary CLusters** and the Roubaix cluster in **Recovery Clusters** and then click `Next `. ![17 - invert recovery plan after failover 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/17-invert-recovery-plan-after-failover04.png) Click `Proceed `. ![17 - invert recovery plan after failover 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/17-invert-recovery-plan-after-failover05.png) Click `Next `. ![17 - invert recovery plan after failover 06](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/17-invert-recovery-plan-after-failover06.png) Choose this information: - **Primary** - **Production** : `production` - **Test Failback** : `testproduction` - **Recovery** - **Production** : `production` - **Test Failback** : `testproduction` Click `Done `. ![17 - invert recovery plan after failover 07](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/17-invert-recovery-plan-after-failover07.png) :::info Replication and recovery plans were reversed following a migration of virtual machines from Roubaix to Gravelines. To return to the original state, you need to perform a hot migration again and reverse replication and the disaster recovery plan. You can use this part of the guide if your disaster recovery plan is triggered because a cluster is unavailable. ::: [](#) #### Step 2.4 - Execute the Disaster Recovery Plan in Real Condition We will simulate a total loss of connection to Gravelines where three virtual machines are located in the disaster recovery plan (the Internet gateway and two other virtual machines). Log in to the command line and ping the public address of the gateway. ```bash ## Ping from a remote linux console ping xx.xx.xx.xx Reply from xx.xx.xx.xx: bytes=32 time=21ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=21ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=23ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=20ms TTL=58 ``` Leave the ping command to run continuously and return to Prism Central. In the main menu, click `VMs ` in the `Compute & Storage ` submenu. ![18 - fail on Gravelines 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/18-fail-on-gravelines01.png) The three virtual machines in the disaster recovery plan are functional. ![18 - fail on Gravelines 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/18-fail-on-gravelines02.png) All three nodes in the Gravelines cluster will be disconnected. :::info The disconnection is done by deleting the 3 nodes of the Gravelines cluster from the vRack. ::: Return to the console that is pinging to the gateway, and you will see a connection loss. ```bash Reply from xx.xx.xx.xx: bytes=32 time=20ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=21ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=20ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=20ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=20ms TTL=58 Request timed out. Request timed out. Request timed out. Request timed out. ``` In Prism Central, click the top right on the `tasks ` to display the task launch, including **Recovery plan execute** . ![18 - fail on Gravelines 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/18-fail-on-gravelines03.png) :::warning In the event of an incident on an entire cluster (there are not enough nodes to function, or a network outage), the virtual machines that are part of the IP and that are on this cluster will be started on the other cluster. The RPO (Recovery Point Objective) is 0 seconds, which means that no data loss will be reported. However, it will take a while for the virtual machines to reboot on the other cluster. In this guide, 3 virtual machines are restarted on the remote cluster. It will take you 4 minutes to start the virtual machines. This time can be measured by regularly running tests on disaster recovery plans. ::: Go back to the text console and you will see that the ping works again. ```bash Request timed out. Reply from xx.xx.xx.xx: bytes=32 time=20ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=19ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=18ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=18ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=19ms TTL=58 Reply from xx.xx.xx.xx: bytes=32 time=19ms TTL=58 ``` Go to Prism Central in the virtual machine management, you will see the three virtual machines of the recovery plan in duplicate. They are marked as started, but in reality, only the ones restarted in Roubaix are working. ![18 - fail on Gravelines 04](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/18-fail-on-gravelines04.png) We will reconnect the three nodes in the vRack to return to normal mode. After the recovery, the virtual machines on the original cluster are still visible but are turned off. You can delete or keep them if problems occur on the VMs that are being rebooted. ![18 - fail on Gravelines 05](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/18-fail-on-gravelines05.png) You can view the history of **Disaster Recovery** actions in Prism Central. Click the button in the ** top right-hand corner to go to the Prism Central configuration. ![19 - show Witness information 01](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/19-show-witness-information01.png) Left-click `Witness ` and click `View Usage History `. ![19 - show Witness information 02](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/19-show-witness-information02.png) The list of events appears, click `Close ` to close. ![19 - show Witness information 03](/images/hosted-private-cloud/nutanix-on-ovhcloud/48-metro-availability/19-show-witness-information03.png) [](#) ## Go further [Interconnect clusters through the vRack](/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/vrack-interconnection.md) [Disaster Recovery Plan for Nutanix](/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/disaster-recovery-plan-overview.md) [Asynchronous or NearSync replication through Prism Element](/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/prism-element-replication.md) [Advanced replication with Leap](/pt/guides/hosted-private-cloud/nutanix-on-ovhcloud/nutanix-leap.md) [Introduction to vRacks](https://www.ovhcloud.com/pt/network/vrack/) [Documentation Nutanix AHV Metro - Witness Option](https://portal.nutanix.com/page/documents/details?targetId=Leap-Xi-Leap-Admin-Guide-v2022_6:ecd-ecdr-witness-syncrep-pc-c.html) If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pt/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. Join our community of users on [https://community.ovh.com/en/](https://community.ovh.com/en/).