In today’s fast-paced digital world, where every second of downtime can translate to significant financial and reputational losses, disaster recovery has become a cornerstone of business continuity planning. From natural disasters to cyberattacks, the risks to IT infrastructure are numerous and ever-evolving. As organizations increasingly rely on complex systems to manage their operations and data, the need for robust, reliable disaster recovery solutions is more critical than ever.

But disaster recovery isn’t a one-size-fits-all proposition. With a myriad of options ranging from traditional on-premises backups to advanced cloud-native solutions, choosing the right approach can be daunting. The stakes are high, and the wrong decision could mean the difference between a seamless recovery and a catastrophic failure.

In this post, I’ll explore the question of how to select the most suitable disaster recovery strategy for a given organization. Using a recent real-world case study from my own work—designing a disaster recovery solution to migrate a client’s on-premises environment to AWS—I’ll unpack the factors that influence this critical decision and share insights into crafting a solution that aligns with both current needs and future goals.

Stay tuned as I delve into the nuances of disaster recovery and the lessons learned from tackling this challenge head-on.

Case Study: Crafting a Disaster Recovery Solution on AWS

The Client’s Existing Environment
The client was looking to run a Proof of Concept (PoC) a disaster recovery solution on AWS for three of their critical on-premises systems:

• ERP Application: Hosted in a virtualized environment, this was the client’s most critical system.

• Information System: Running on a physical server.

• Library System: Also running on a physical server.

Currently, the client relied on native backup software to perform daily full backups of these systems. However, these backups were retained for only 24 hours, after which they were discarded. Additionally, the client had encountered several issues with the restore process, including incomplete backups and unsuccessful recovery attempts.

Challenges with the Existing Solution

The primary challenges faced by the client included:

• Limited Backup Retention: With backups retained for only 24 hours, the risk of losing critical data in case of delayed issue detection was high.

• Inefficient Recovery Process: The manual restore process was cumbersome and prone to failure, compromising their ability to recover systems effectively.

• Critical ERP System Requirements: For their ERP application, the client needed a solution with a stringent Recovery Time Objective (RTO) of 1-2 hours to ensure minimal disruption to business operations.

Requirements for the New Solution

The client sought a comprehensive backup and restore solution on AWS that addressed these challenges:

• Comprehensive Backups: A solution capable of ensuring data integrity and addressing the shortcomings of their current incomplete backups.

• Enhanced Recovery Capabilities: A system that enabled efficient and reliable recovery processes, reducing the risks of failed restores.

• ERP-Specific Recovery Objectives: A tailored approach for the ERP system with:

  ~ An RTO of 1-2 hours.

  ~ Recovery options that included both on-premises restoration and the possibility of running the ERP in the cloud.

• Flexible RTO and RPO for Other Systems: While the ERP required stringent recovery metrics, the information and library systems had more flexible Recovery Time and Recovery Point Objectives (RTO/RPO).

Key Considerations for Crafting the Solution

So, let’s start by identifying the core considerations/factors that influence the choice of a Backup/DR solution. We’ll then dive into each of these factors to understand how they each impact the final solution.

1. Backup vs DR: Determining whether a system needs just data preservation or rapid operational recovery can significantly influence service selection and configuration.

2. AWS-Native vs Third-Party Solutions: Balancing native integration, cost-effectiveness, and feature richness is essential for crafting a tailored solution.

3. Scheduling and Automation: The right tools and schedules can simplify operations, reduce manual intervention, and ensure reliability during critical recovery scenarios.

4. Physical vs Virtual Servers: Selecting a solution that accommodates both server types ensures comprehensive coverage and seamless recovery.

5. RPO and RTO Requirements: Solutions must be tailored to meet the client’s specific RPO and RTO needs

6. On-Premises vs Cloud Restores: The location of data recovery is influenced by several factors e.g. compliance, application dependencies, enhanced resiliency, etc.

Designing the right disaster recovery solution is no small task, especially when balancing the complexities of modern IT environments with an organization’s unique needs. Each factor requires careful evaluation to ensure that the chosen approach is not only robust but also aligned with both operational goals and budgetary constraints.

In the next installment of this series, we’ll take a deep dive into each of these considerations, unpacking how they influence the decision-making process and exploring practical strategies for addressing them. Whether it’s the choice between AWS-native tools and third-party solutions, or tailoring RPO and RTO requirements for different systems, we’ll walk through the details to provide actionable insights for crafting effective disaster recovery plans.

Stay tuned for Part 2, where the journey continues! If you’ve faced similar challenges or have thoughts on disaster recovery strategies, I’d love to hear from you in the comments below. Let’s keep the conversation going—because when it comes to disaster recovery, every insight counts.