Zero Data Loss and Fast Recovery: The New Normal
A business continuity plan is an essential part of risk management. It documents the steps required to ensure that an organization continues to function (or quickly resumes function) in the event of a natural or human-made disaster. A disaster recovery plan is a subset of business continuity planning. It focuses on the tasks required to protect and recover IT infrastructure and data before, during, and after a disaster. The goal for business continuity planning (and by extension, disaster recovery planning) is to minimize data loss and downtime so that an organization can reduce risk and return to normal operations as quickly as possible after an event.
A well-conceived business continuity plan analyzes the business impact / risk of disruptions to applications and business processes, includes a disaster recovery plan to protect data and ensure rapid recovery, and identifies workarounds so that business operations can continue as normally as possible until disaster recovery is complete.
Business Continuity Plan Targets: Zero Data Loss, Near-Zero Recovery Time
A business continuity plan starts with risk management questions such as, “What happens if we lose transactional data?” “What are the consequences if this application becomes unavailable for a minute, hour, day, or…?” Once organizations determine the potential risks and the cost of mitigating those risks, they can go about creating a business continuity plan that balances risk and cost.
In crafting a business continuity plan, organizations typically set a for the amount of data loss and downtime, respectively, they are willing to tolerate in the event of a disaster. Ideally, every application or business process would have an RPO of zero and an RTO of near zero; however, these targets are not always physically or financially attainable with either asynchronous or synchronous database replication alone.
Data loss. With asynchronous database replication, an inherent lag exists between the data in the primary site and the data in the disaster recovery site. Without Axxana Phoenix, this lag is usually unprotected, leading to the loss of transaction data if disaster strikes. Synchronous replication topologies are also vulnerable. Because synchronous replication requires the primary site and disaster recovery site to be geographically close to one another, regional disasters or rolling outages can interrupt synchronous replication, resulting in the loss of valuable data.
Recovery time. When transaction data is lost, data consistency across databases and applications may also be lost. In this case, disaster recovery entails a laborious, time-consuming process of determining what data has been lost and reconstructing application consistency. The longer that recovery and the return to normal operations is delayed—that is, the longer the downtime—the greater the risk.
Given these challenges in both synchronous and asynchronous replication environments, many organizations accept some amount of data loss (and consequent slower recovery times) as inevitable during a disaster.
Achieving Business Continuity Plan Targets – Regardless of Topology or Budget
With Axxana’s Phoenix, organizations no longer have to tolerate a single byte of data loss when they set data loss and recovery time objectives for their business continuity plans and disaster recovery plans. Axxana Phoenix uses the disaster-proof Black Box and an intelligent operating system to protect the data lag (not-yet-replicated data) during a disaster and safely transfer the data during recovery. It enables organizations to achieve zero data loss (RPO = 0) and near-zero RTO, regardless of size, complexity, budget, replication topology, or infrastructure (including flash arrays, cloud-based applications, and more.)
Click here for use cases illustrating how you can use Axxana’s Phoenix to meet business continuity plan requirements within your own organization.