The Challenge – Maintaining Application Availability through Rolling and Regional Disasters
You want to move to a two-data-center topology in order to improve performance, simplify operations, and reduce costs—but you still need to ensure rapid recovery and continuous application availability in any disaster scenario. Zero data loss is key to achieving this.
With Oracle’s Active Data Guard Far Sync solution, the active database at the primary site synchronously replicates to a Far Sync instance at a nearby site, which then replicates asynchronously to a distant site. Although this lightweight model provides a less costly alternative to a full three-data-center topology, it still has the other disadvantages of traditional synchronous replication solutions: Organizations need to invest in a nearby facility from which to run the Far Sync instance; the high-bandwidth communication lines between the production and nearby site are costly; and latency still impacts performance.
More important, the solution is not immune to regional or rolling disasters, in which power and communication outages can cause synchronous replication to fail. In fact, without Axxana’s Phoenix, no DR solution is immune to these types of disaster. Until now, this has been an industry-wide challenge.
The Solution – Continuous Application Availability
Oracle customers can make disaster recovery simpler, more reliable, and more affordable by combining Axxana’s Phoenix with Oracle Active Data Guard Far Sync technology. This best-of-breed solution lets you avoid the major shortcomings of three-data-center topologies by maintaining only two sites (the primary and DR site), while ensuring rapid recovery and enabling continuous application availability in any disaster scenario, including regional and rolling disasters. It’s the only industry solution that can do so.
Axxana’s Phoenix for Oracle Far Sync, supported by Oracle, is a self-contained, physically indestructible solution that houses, protects, and supports the Oracle Far Sync instance from within the primary (production) data center. Because a nearby data center is not needed, the risk of a nearby synchronous site failing (e.g., due to a power outage or downed communication lines) no longer exists. Zero data loss is guaranteed, which is essential to maintaining continuous application availability. In addition, because the instance can reside at the primary site, communication lines are a matter of feet instead of miles and network latency is negligible.
Given that it easily and cost-effectively resolves the challenges associated with standalone versions of Far Sync, there is simply no good reason to use the Far Sync software on any other platform—or for that matter, to use three data centers. IT leaders owe it to their company and their customers to take advantage of the risk reduction, cost savings, and other opportunities that Phoenix for Oracle Far Sync offers.
Axxana’s Phoenix fulfills the functions of a nearby synchronous Far Sync instance right at the primary site, continuously protecting yet-to-be-replicated data without the need for a synchronous data center. Because a nearby data center is not needed, the risk of a nearby synchronous site failing (e.g., due to a power outage or downed communication lines) no longer exists—even in regional or rolling disasters. Zero data loss is guaranteed in any disaster, significantly increasing the probability of successful failover and continuous application availability.
Reduces Operational and Recovery Costs
The Phoenix-based architecture does not require a third, nearby data center, so it costs a lot less to implement. Savings span across multiple cost centers, including head count, real estate, utilities, equipment, and communications. In addition, because Axxana’s Phoenix for Oracle Far Sync ensures zero data loss recovery, there are no missing transactions or data to reconcile. Labor associated with data reconciliation becomes a line item of the past.
Eliminates High-Bandwidth Lines
Because there is no need for a nearby synchronous data center, there is no need for costly fiber-optic replication lines. Your organization can use low-cost IP lines for asynchronous replication across the large distance between the primary and remote DR data center.
Axxana’s Phoenix for Oracle Far Sync solution trades a complex three-data-center topology for a simple two-data-center deployment. That means one less physical plant, one less HR staffing headache, and one less communications infrastructure to manage. And when disaster strikes, it also means you can skip reconciliation (because data is never lost) and move straight to failover.
Protected storage unit with DR capabilities
Installed at the production site, the Black Box is designed to withstand a wide variety of extreme conditions that may occur during a disaster.
Redundant communication systems
Once a disaster has occurred, the Black Box has several methods of sending the transaction data to the remote site:
- Over an existing WAN (if the disaster is local and the WAN still operates)
- Downloading the transaction data over Wi-Fi to a laptop and transferring it over a secured alternative WAN connection
- Transferring the encrypted and authenticated transaction data via a VPN over a 4G network using multiple LTE modems.
For More Information
To learn more about how Axxana’s Phoenix and Oracle Far Sync complement one another, read Axxana’s paper, Phoenix for Oracle Far Sync – 100% Zero Transaction Loss DR Solution for Oracle® Data Guard 12c Far Sync.
For technical details of Axxana’s Phoenix for Oracle Far Sync, read here.
To learn more about how Axxana’s Phoenix eliminates the need for a three-data-center solution and ensures that Oracle databases meet Tier 0 and Tier 1 SLAs, read here.