Recovery time objective (RTO) is the targeted amount of time within which an organization wants to restore operations or business processes to normal after a disaster. Like , it is an important parameter of business continuity planning and disaster recovery, and often reflects on decisions about how much downtime and risk an organization is willing to accept.


Recovery Time Objective and Zero Data Loss

The longer the recovery time—that is, the longer the downtime—the greater is the potential loss of revenue, customers, productivity, and reputation. For this reason, the ideal RTO for business continuity planners is zero or near zero. One of the key requirements for short recovery times is zero data loss. Until the Axxana Phoenix, none of the traditional replication topologies has been able to guarantee this.


Although synchronous replication comes close to assuring zero data loss, it is very costly to deploy and maintain. In addition, it is not feasible in situations that require long-distance network communications or in flash-based storage environm ents. Because it requires primary and secondary replication sites to be in close geographic proximity, it is also prone to data loss in the event of regional disasters or rolling outages.


Asynchronous replication is more affordable and can be deployed in geographically distributed environments and with flash arrays. The downside is that an inherent lag between data at the primary site and data at the disaster recovery site means that yet-to-be-replicated data will be lost in the event of a disaster.


When data loss occurs in synchronous or asynchronous environments, consistency across inter-related applications can also be lost. In this case, the organization must engage in a time-consuming process of identifying what data is missing, and then reconstructing that data to a single point in time. The organization cannot resume normal business operations until consistency is re-established; system availability may be delayed for hours or days.

Near-Zero RTO and High Availability – With Any Topology

Many organizations mistakenly believe that fast recovery times are out of reach in their environment—whether because they can’t afford synchronous replication, their flash-based storage solution is incompatible with synchronous replication, their cloud-based disaster recovery service topology is vulnerable to regional disasters, or some other challenge puts them at risk for data loss and data inconsistency.


With the Axxana Phoenix, near-zero RTO is an achievable target for any organization’s disaster recovery and business continuity planning. Axxana’s Phoenix uses the disaster-proof Black Box and a built-in, intelligent operating system to protect data lag (not-yet-replicated data) during a disaster and safely transfer the data during recovery. This affordable, innovative technology complements an organization’s existing disaster recovery topology to ensure zero data loss and rapid recovery time.


Click here for examples of how you can use Axxana Phoenix to ensure zero data loss and achieve near-zero RTO within your own organization.


Recovery Time Objective

To contact an Axxana representative or learn more about Axxana’s ground-breaking technology, click here.