Before initiating a complete infrastructure Disaster Recovery (DR) process with Cloud Rewind, consider the following best practice guidelines:
Method of Protection
For small-sized AWS infrastructures, consider protecting them under a single Cloud Rewind Cloud Assembly for easy and simplified recovery. 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
Organize your cloud resources based on applications when creating a cloud assembly under Cloud Rewind. 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
During recovery, start by recovering the High critical resource and Domain servers. After recovering the domain server and other high-critical applications, proceed with the recovery of all the other application resources one by one. 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
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. All the Hosted and DNS records created during the recovery process will be rolled back once the reset is complete.