Skip to main content

How can we help you?

Druva Documentation

Automated Disaster Recovery Workflow

Provides information on the Automated Disaster Recovery workflow for AWS resources.

Overview

With Automated Disaster Recovery, (ADR), Druva CloudRanger offers an enhanced disaster recovery model to keep your AWS data secure and recoverable from any region-specific or account-specific outages. With disaster recovery, you can validate RTO and RPO objectives to ensure business continuity with significant cost savings.

The disaster recovery testing functionality allows you to test the failover of the Amazon Machine Interface (AMIs) and snapshots defined in the backup policy. Based on the test results, you can expand your resource capacity or select a different target environment to reduce RTO or you may increase backup frequency to minimize the RPO. Testing can be run on-demand or automated based on a defined schedule.

Key advantages

  • Improved flexibility with Sync Schedules tschedule the cloning of your source AWS environments. Define the frequency and schedule criteria when your source environments are cloned and synchronized with the target environments, as per a user-defined schedule (similar to schedules in a backup policy).
  • Resource Rules to identify resources that you wish to recover from the source environment.
  • Intelligent real-time feedback confirming or otherwise, your backup strategy meets your Recovery Point Objective (RPO).
  • AWS cross-account disaster recovery plans.
  • Enhanced testing options and flexibility in choosing instance sizes for disaster recovery.
  • Support for Amazon RDS resources as part of DR plans.

 DR Plans currently do not support automated recovery of full RDS clusters.

Automated Disaster Recovery Workflow

The Automated Disaster Recovery workflow in Druva CloudRanger is shown below:

Steps Description
Step 1: Create an Environment Identify and group the resources that need to be protected.
Step 2: Clone the Environment Create a replica of the source environment in the target region.
Step 3: Set up a Sync Schedule (Optional) Create a Sync Schedule to periodically sync the Target environment with the Source.
Step 4: Setup a Backup Policy (Optional) Create backup copies using the backup plan. The backup copies will be used to restore the resources in the target region.
Step 5: Create a Disaster Recovery Plan Define the RTO and RPO - the downtime your organization can manage and the amount of data loss that your organization can absorb.
Step 6: Testing the Disaster Recovery Plan Test the disaster recovery plan before implementing it.
You may also create a schedule to test the disaster recovery plan. 
Step 7: Executing the Disaster Recovery Plan If required, perform the failover with the click of a button.

Before you begin

Before you begin with Automated Disaster Recovery, ensure that you have the following:

  • At least one AWS resource in your account that you want to protect.
  • Access to the accounts if you plan to perform cross-account disaster recovery.

Step 1: Create an Environment

This is the first step in setting up Disaster Recovery. In Druva CloudRanger, an environment refers to a logical grouping of your AWS resources that you want to protect in case of a disaster. With Automated Disaster Recovery, you can failover these resources with the click of a button.

Note: Creating a source environment does not create or update existing resources or configurations in your AWS account.

To create an environment:

  1. Log into your Druva CloudRanger console and navigate to Disaster Recovery > Environments.

    DR Env Main.png
     
  2. Click Create Environment.

    Field

    Description

    Name

    The name of the environment.

    Description

    (Optional) The description of the environment.

    Region

    The storage region where you want to create your source environment.
    Select the required region from the list. Based on the region selected, the associated VPCs are displayed.

    Add Resources

    VPC

    Select the VPC, which has the resource that you want to protect.
    All the associated Subnets and Security Groups are selected by default.

    Note: If the VPC contains an RDS instance, you will have the option to select the DB Subnet Groups.
  3. Click Save Environment.
     

Step 2: Clone the Environment

The next step is to clone the source environment to a region where you want to failover in case of a disaster. Druva CloudRanger clones the source environment to the region or account that you have selected. Cloning essentially replicates the source infrastructure in the target region, which allows the resources to be failed over quickly and seamlessly.

To clone an environment:

  1. Log into your Druva CloudRanger console and navigate to Disaster Recovery > Environments.

    1_Env.png
     
  2. Select the environment that you wish to clone, and then click Clone.
    2_Clone.png
  3. On the Clone Environment page, specify the following:

  • Select the Account where you want to clone the source environment so you can perform cloning across accounts.

Note: For cross-account mapping, you will need to have access granted to the account where you wish to clone the source environment.

  • Select the Region where you want to clone the environment.
  • Optionally, you may choose to create a Sync Schedule to manage your environment cloning and periodically synchronize your target environment with the source. To create a Sync schedule, select Sync Schedule and then specify the cloning frequency and schedule.
    For more information, refer to Step 3: Set up a Sync Schedule.

4. Click Clone.
The CloudFormation process is initiated, which can take some time depending on the size. You can view the CloudFormation stack being created and the cloning status on your AWS console.

Note: Once the clone is ready, you can view the cloned environment in the list of environments. By default,  the suffix  ‘clone’ is appended at the end of the cloned environment name.
Verifying the status of the cloning process

Status in Druva CloudRanger

  • You can view the status of the job initiated for the cloning process on the Jobs page.
  • To access Jobs, navigate to Monitor > Jobs from the top bar, and then click the Disaster Recovery tab.

Status on AWS console

  • You can also view the status of the cloning process within your AWS console.
  • Navigate to CloudFormation and select the region where the environment is being cloned.
Download CloudFormation stack

Once you clone an environment, the CloudFormation stack is updated and the new cloning status will be updated on your AWS console. Once the process is complete, you can download the updated CloudFormation template.

  1. To download, select an environment clone and then click Download CloudFormation:

    1_CF download.png

  2. Select the appropriate version and click Download.

Note

  • The option to select the CloudFormation version will be available only when you select an environment clone. Druva CloudRanger will store the previous five versions of the CloudFormation for a target environment.

  • Selecting a source environment will automatically download the latest CloudFormation. 

Step 3: Set up a Sync Schedule

A Sync Schedule allows you to automate your environment cloning by periodically synchronizing a target environment with the source.

Note: You can define a Sync Schedule only for a cloned environment (the target environment on which the DR failover will be initiated).

To create a Sync Schedule:

  1. Log into your Druva CloudRanger console and navigate to Disaster Recovery > Environments.
  2. Select the target environment for which you want to define a sync schedule.

    Sync Schedule_1.png
     
  3. Select the Sync From checkbox and define the schedule to ensure that your target environment is periodically synchronized with the source.
    • Sync: Choose the sync frequency by day, week, or month.
      For example:
      Sync Weekly on Monday at 2:00 AM
      Sync Monthly on the 1st day of the month every 30 minutes
    • Timezone: Select the time zone that applies to the sync frequency specified.

You can choose to disable an active Sync Schedule, and then enable it based on your business requirements.

To view all active schedules, navigate to the Sync Schedule tab on your Environments listing page:

1_SyncSch.png

Note: The availability of this feature may be limited based on the license type, region, and other criteria. To access this feature, contact your Druva Account Manager or Support.

Step 4:  Set up a Backup Policy

You can create a new backup policy or use an existing backup policy to create backups in the cloned or target region. This enables Druva CloudRanger to restore instances using the backup copies. 

To create a backup policy, refer to Creating backup policies.

Executing the backup policy

Once you have created the backup policy, make sure that it has been executed at least once so that a backup copy is available at the target location.

To execute a backup policy:

  1. On the top navigation bar, click Policies and then select the policy you wish to execute.
  2. Click Execute Now to initiate the backup policy.

    BP_Exec.png

    The subsequent backups that are generated on policy execution may be reviewed under the relevant resource Backups page.
Note: The details of the policy execution can also be viewed on the Jobs page. Navigate to the Disaster Recovery tab to review the progress of the backup operation from the source region and copy to the target region.

Step 5: Create a Disaster Recovery Plan

A disaster recovery plan is a structured set of instructions designed to recover resources in the event of a failure or disaster. Disaster Recovery aims to get you back to the production-ready setup with minimal downtime.

Having a disaster recovery plan in place enables you to protect critical resources and to quickly restore resources to replicate a product-ready setup.

To create a disaster recovery plan:

  1. Log into your Druva CloudRanger console, and navigate to Disaster Recovery > DR Plans.

    DR1.png
     
  2. Click Create Disaster Recovery Plan.

    DR Plan 1A.png

Specify the following to create a DR plan.

Field Description
Name The name of the DR plan.
Description (Optional) The description of the DR plan.
Service Level Objective (SLO)

Recovery Point Objective (RPO)

Specify the RPO as per your business policy.
RPO is the point in time in the past to which you can recover data when a disaster occurs. In other words, RPO defines the amount of data the organization can afford to lose during a disaster.
Example:
For an organization with an RPO of 24 hours, where the backup is scheduled daily at 8 PM.
If a disaster occurs at 7.59 PM, you can recover data that was backed up on the previous day at 8 PM. However, you lose the data generated after the last backup.

Recovery Time Objective (RTO)

Specify the RTO as per your business policy.
RTO is the amount of time you set for your application to recover from the point-in-time the disaster occurs. In other words, RTO defines the maximum tolerable outage. The application must be restored within its defined RTO to ensure business continuity.
Example:
For an organization with an RTO of 30 hours. When a disaster occurs, the organization must recover all its critical IT services within 30 hours from the point in time the disaster occurs.

Environments  
Source Account The source account is by default the CloudRanger account in which you are currently creating the DR plan.
Source Environment Select the source environment, applicable within the Source Account.
Target Account Select the target account.
You can select the same source CloudRanger account as the target account.
Target Environment Select the target environment, applicable within the Target Account specified previously.
Component Mapping  
Source VPC Based on the Source Environment selection, the Source VPC and associated attributes are listed.
Target VPC Based on the Target Environment selection, the Target VPC and associated attributes are listed.
If you have cloned the environment, both Source and Target VPCs are populated.


3. Use Resource Rules to identify resources that you wish to recover from the source environment.

  • Click Add to identify resources that you wish to include or exclude as part of the DR plan.

 DR Plans currently do not support automated recovery of full RDS clusters.

1_DR_Res Rule1.png

  • On the Add Rules page, specify the filter criteria to identify specific resources to include or exclude.

    1_DR_Res Rules.png

 

Field Description

Rule Type

The option selected here will identify resources to include or exclude as part of the DR plan.

Find Resource types

Select the Resource Type, for example, EBS Volume, EC2, RDS or Redshift.
You may select All resource types to filter resources across resource types.

Match

Select the match criteria by Resource IDs, Tags, VPC IDs, Subnet IDs, or select All resources. Based on the match criteria selected, you will need to specify the appropriate values for that criteria. 
For example: VPC IDs: Select by VPC IDs or VPC Name
You can also include or exclude resources using resource Tags. Tags are standardized, case-sensitive key-value pairs that act as metadata to help identify and organize your AWS resources. Select Tags under Match and then specify the key and an associated value, as part of managing resources for disaster recovery.
For example: Key: Backup Type; Values: Daily

Note: When multiple tags are defined as part of include/exclude, this translates to an ‘AND’ condition. In other words, CloudRanger will select resources that satisfy all the specified tags. Use tags judiciously to ensure that you can narrow down to the appropriate subset of resources on which the DR plan will apply.

How Include/Exclude conditions apply on Druva CloudRanger:
  • You can create multiple include and exclude rules.
  • Include rules: When multiple include rules are defined, this translates to an ‘OR’ condition. In other words, resources are matched against each include rule, and do not have to meet all specified conditions concurrently.
  • Exclude rules: Exclude rules take precedence when the same resource is matched based on the include and exclude criteria selected.
  • When multiple tags are defined as part of include/exclude, this translates to an ‘AND’ condition.
     

The resources identified are then displayed under Include or Exclude Resources, based on your selection criteria. To eliminate a specific resource from the list of Resource Rules, select the checkbox against that rule and click Delete.
1_DR_Res Rule.png

Note: The Resource Status indicates the backup status for the list of resources selected as part of the Resource Rule.

  • Protected – Indicates that all the resources identified by a rule are protected by a valid backup policy
  • Partially Protected – Indicates that some of the resources identified are protected by a backup policy

  • Not Protected – Indicates that none of the resources identified by a rule are protected by a backup policy

    It is recommended that all resources identified as part of a DR plan are covered by a valid backup policy. For more information, see  Create Backup Policies.

5. Specify the encryption key mapping information and the Advanced options for your DR plan.

Field Description
SSH Key Mappings

Source SSH Key

Select the source SSH key.

To backup encrypted resources onto the Target Environment, you will need to define the encryption keys used in the source environment for the DR plan.
The SSH key applies only if the source environment has EC2 or RDS instances that are encrypted.

Target SSH Key

Select the SSH key for the target environment with which you want to encrypt the instance after it is restored.

Instance Profile Mappings

Select the Instance Profile Mapping if the source instance has a specific IAM role attached to it, which governs access to that instance.
This applies only if the source environment has an instance managed by a policy that has an associated IAM role. In the case of cross-region or cross-account copy, the IAM role needs to be defined to initiate failover into the target environment.

Advanced

Target Instance Type

Select the target instance type that should be restored after the failover in the target region. In case, an instance type is not available in the target region, select an option to instruct Druva CloudRanger to:

  • Select an instance type that is large in size based on availability in the target region 
  • Select an instance type that is smaller than the current instance in size based on availability in the target region
  • Fail the creation of instance if the instance type of source region is not available in the target region

Test Plan Instance Type

Select an instance type that will be used during the testing of the disaster recovery plan. Choose an instance type carefully to avoid incurring costs.

Shutdown source servers after failover Select this option to shut down the servers in the source region after failover to the target region.6. 

6. Click Save Plan.

Step 6: Testing the Disaster Recovery Plan

Once you have defined your DR plan, it is time to test the DR plan so that you can initiate a failover of resources to the target region, when necessary. You can now easily try this on the resources in the cloned environment without touching your production environment.

To test execute a DR plan:

  1. Log into your Druva CloudRanger console and navigate to Disaster Recovery > DR Plans.

    Exec DR.png
     
  2. Select the DR plan you wish to test and then click Execute Test.

    DR Execute Test.png
  3. Select the backup criteria for the failover.
    Select point in time to define the exact date and time for the failover or select the standard RPO that you have defined in the DR plan.
  4. Specify the Test Retention Period for the instance in the target region, in hours, days, weeks, months, or years.
  5. RunBooks: Runbooks are standardized SOPs and can be used as part of your ADR testing strategy. Use Runbooks to automate server shutdown or restart of based on your DR failover plan testing parameters specified:
  • Server shutdown: To initiate a shutdown, upon failover, of all source servers defined within the DR Test Plan, enable Shutdown source resources while testing when failover occurs toggle.

Note: Enabling this runbook on test plans running within a Production environment will shut down all associated Production resources.

  • Server restart: To restart source instances post the failover retention period enable the Restart source resources automatically once test failover retention period has concluded toggle.

6. Click Confirm.

You can choose the frequency of the schedules where you would like to automatically test created backups by temporarily restoring them to an instance.

To create a test schedule:

  1. Log into your Druva CloudRanger console and navigate to Disaster Recovery > DR Plans.

    Test Sch1.png
     
  2. Select the DR plan for which to schedule testing and then select Create Test Schedule.

    DR Sch Test.png
     
  3. Set the Create Schedule Tests option to Enabled.
    • Select the Timezone that applies to the DR test schedule.
    • Specify the execution schedule.
      For example, Run Test Every weekday at 20:00.
    • Specify the retention time of the servers in hours, days, weeks, months, or years.
      For example, Delete Servers After 4 weeks.
    • RunBooks: Runbooks are standardized SOPs and can be used as part of your ADR testing strategy. Use Runbooks to automate server shutdown or restart of based on your DR failover plan testing parameters specified:
      • Server shutdown: To initiate a shutdown, upon failover, of all source servers defined within the DR Test Plan, enable Shutdown source resources while testing when failover occurs toggle.

Note: Enabling this runbook on test plans running within a Production environment will shut down all associated Production resources.

  • Server restart: To restart source instances post the failover retention period enable the Restart source resources automatically once test failover retention period has concluded toggle.
  1. Review the test schedule summary, and then click Save.
     

Step 7: Executing the Disaster Recovery Plan

Once you have tested the disaster recovery plan, you can execute your disaster recovery plan manually, if required. 
To execute the disaster recovery plan:

  1. Log into your Druva CloudRanger console and navigate to Disaster Recovery > DR Plans.

    Exec FLO.png
     
  2. Select the disaster recovery plan and click Execute Failover.
  3. Select the backup criteria for the failover.
    Select point in time to define the exact date and time for the failover or select the standard RPO that you have defined in the DR plan.

    Exec FLO2.png
     
  4. Click Confirm.
    Druva CloudRanger will then initiate the failover of the resources specified to the target environment as defined in the DR plan.
     
  • Was this article helpful?