Part-5: Test Failover

In the previous posts we went through deploying Prism Central in Main site and DR site, Enable Leap, Configure Availability Zones and creating Protection Policies, Create, Configuring and Validating Recovery Plans

Part-1: Prism Central One-Click Deployment (Click Here)
Part-2: Enabling Leap and Configure Availability Zones (Click Here)
Part-3: Create and Configure Protection Policies (Click Here)
Part-4: Create and Configure Recovery Plans (Click Here)

In this post we will go through Test the Recovery Plans by conducting Test Failover,

After Validation completed, lets do a Test Failover to make sure all are good, same like Validation, select your recovery plan, click on Actions and then click on "Test"

Part-4: Create and Configure Recovery Plans

In the previous posts we went through deploying Prism Central in Main site and DR site, Enable Leap, Configure Availability Zones and creating Protection Policies,

Part-1: Prism Central One-Click Deployment (Click Here)
Part-2: Enabling Leap and Configure Availability Zones (Click Here)
Part-3: Create and Configure Protection Policies (Click Here)

In this post we will go through Creating, Configuring and Validating Recovery Plans,

From Prism Central on the Main Site, on the left corner, click on Entities menu > Policies > Recovery Plans

Click on Create New Recovery Plan

Part-3: Create Protection Policies

In the previous posts we went through deploying Prism Central in Main site and DR site, Enable Leap and Configure Availability Zones,

Part-1: Prism Central One-Click Deployment (Click Here)
Part-2: Enabling Leap and Configure Availability Zones (Click Here)

In this post we will go through Creating and configuring Protection Policies,

From Prism Central on the Main Site, on the left corner, click on Entities menu > Policies > Protection Policies

Part-2: Enabling Leap and Configure Availability Zones

In the previous post we deployed Prism Central in Main site and DR site:

Part-1: Prism Central One-Click Deployment (Click Here)

Before you start you need to make sure that your network connectivity between both sites is healthy and both sites are reachable from the other site,

Now Let's start our journey with Nutanix Leap ...
From Prism Central "PC" in Main site and the same steps from DR Site,  From Settings menu, under Setup, Click on "Leap"

Part-1: Prism Central One-Click Deployment

In this post we will cover the required steps to deploy Prism Central,

From Prism Element main page on the upper left side look for Prism Central, click on "Register or Create new"

If you are joining your cluster to Prism Central already deployed locally or even on another Cluster then you will click on Connect, in our scenario here we need to deploy new one then we will click on Deploy

DR Orchestration (On-Prem Leap)

Nutanix Leap will help you setup, configure, orchestrate and automate all the DR services from centralized location from Nutanix Prism Central, From AOS 5.11 onward, Nutanix adds protection policies and recovery plans to Prism Central for AHV and ESXi, offering an easy way to orchestrate operations around migrations and unplanned failures, Now you can apply orchestration policies from a central location, ensuring consistency across all your sites and clusters, To help manage these new protection policies and recovery plans, Nutanix uses a construct called Availability Zones managed by one Prism Central. An availability zone can also represent a region in Nutanix Xi Cloud Services

Before you start you need to make sure that your network connectivity between both sites is healthy and both sites are reachable from the other site,

My Lab consist of two Nutanix Clusters (Main Site) and (DR Site), on each site we will deploy Prism Central which will be integrated together to provide single logical management layer for our Leap DR services,

Why Disaster Recovery matter!

First, let's go through the definition of the term "Disaster Recovery" or in short as its commonly used by IT professionals "DR."

From an IT point of view, a disaster is anything that stops the operability of IT services in any organization. IT services, such as Infrastructure failure or cyber attack ... etc.,

The goal of the Disaster Recovery solution is to recover your organization IT services operation to normal situation.

What is "RTO and RPO" and why it is matter?

Recovery Time Objective or "RTO" is the time needed to recover your IT Services operations after a disaster has occurred, You’ll want your RTO to be as short as possible,

Recovery Point Objective or "RPO" is the number of data changes you lose that your company or organization can sustain or how much data changes you can afford to lose if a disaster happened,

For example: if a disaster happened at 11:00 AM and your DR solution can recover your Data with change updated until 10:45 AM then your "RPO" is equal "15 Minutes RPO", if your DR solution can recover your data with changes updated until 11:00 AM then your RPO is equal to "0".