AWS Recovery Best Practices and Strategies

AWS Recovery Best Practices and Strategies

Before initiating a complete infrastructure Disaster Recovery (DR) process with Appranix, consider the following best practice guidelines:

Method of Protection

  1. For small-sized AWS infrastructures, consider protecting them under a single Appranix Cloud Assembly for easy and simplified recovery.
  1. For large infrastructures with multiple applications, consider splitting substantial resources into smaller assemblies. This will reduce assembly backup replication time, which enhances the Recovery Point Objective (RPO) of the application. Furthermore, segregating resources into multiple assemblies based on applications enhances application-level recovery capabilities.

Structured Cloud Assembly Creation
  1. Organize your cloud resources based on applications when creating a cloud assembly under Appranix. ( For example, categorize them as Domain Servers and Active Directory, Web Servers, Application Servers, Database Servers, or based on your services.)
Note: Utilize application tags to facilitate easy grouping when creating a cloud assembly.


Recovery Process
  1. During recovery, start by recovering the High critical resource and Domain servers.
  1. After recovering the domain server and other high-critical applications, proceed with the recovery of all the other application resources one by one.
  1. After recovering all the critical instances and load balancers, proceed with recovering all the rest of the application resources.
Note: All your Route 53 private records will be recovered during their associated resource recovery. Your public records can be recovered using custom webhook scripts integrated with any assembly.

Reset Process

  1. After successful recovery and testing, initiate the reset process. Start resetting the application in reverse order, beginning with the last recovered assembly and concluding with the domain servers.
  1. All the Hosted and DNS records created during the recovery process will be rolled back once the reset is complete.



    • Related Articles

    • AWS Cross-Tenant Configuration

      Cloud Connection For doing a Cross-tenant recovery the user should have two Cloud Connections, one pointing to the primary AWS account and another one pointing to the recovery AWS account. To add a new AWS Cloud Connection in Appranix, follow the ...

    • AWS Cloud Connections FAQ

      When we add an AWS account to Appranix does it take into account the default resources of the AWS account as well? - No, only the dependent resources of the selected resource(EC2, RDS Instance) While discovering assemblies, Appranix does show the VPC ...

    • AWS Environment Onboarding

      Subscribe from AWS Marketplace Search for "Appranix" in the AWS Marketplace Subscribe for "Appranix Cloud Application Resilience" from the search result Subscribe to the service Register your account with Appranix AWS Onboarding Prerequisites For ...

    • Appranix Route 53 Recovery Guide for AWS Shared VPC Environments

      Appranix has expanded its support for Route 53 recovery in AWS-shared VPC environments. This document provides valuable insights into the various types of shared VPC setups that Appranix can recover. Explore the configuration details and step-by-step ...

    • How does Appranix handle cross regions with multiple availability zones during recovery?

      Appranix maps the Availability Zones of the primary region to the recovery region’stwoAvailability Zones during the recovery process.  Protected resources in the cloud assembly that are spread across multiple zones in the primary region are mapped ...