The Challenge

You need to minimize downtime and maintain continuous application availability, while reducing costs and operational inefficiencies associated with disaster recovery. Eliminating data loss is key to achieving this. Asynchronous replication always results in data loss during a disaster; synchronous replication costs too much and does not guarantee zero data loss.

When using asynchronous replication, there is an inherent lag between the data in the primary site and the data in the disaster recovery site. If this lag is not protected, your organization risks losing transaction data during a disaster. Disaster recovery in this scenario slows down the recovery process and the return to normal operation because it requires time-consuming identification of what data has been lost and reconciliation of lots of transactions and data. The longer recovery takes—that is, the longer the downtime—the greater the potential loss of revenue, customers, productivity, and reputation. In a survey of more than 800 enterprises, 81 percent of respondents reported downtime costs of more than $300,000 per hour; 33 percent reported hourly costs of $1 million or more.[1]

These losses don’t even include the loss of the transaction data itself. Although some organizations resign themselves to some data loss (and the resulting downtime) during asynchronous replication, your organization does not have to tolerate any amount of data loss during a disaster. Nor should you tolerate anything but the absolute minimum downtime.

The Solution

Phoenix for Oracle achieves continuous application availability and saves money by constantly protecting yet-to-be-replicated data and rapidly restoring production across the Oracle environment.

By combining Oracle® multiplexing capabilities with Phoenix’s disaster-proof Black Box and its operating system’s rich-featured recovery process, Phoenix for Oracle provides continuous application availability without the complexity, cost, performance issues, and distance limitations associated with synchronous replication. In the event of failure at the primary site, Phoenix for Oracle recovers all applications and databases together, with full consistency across them.

Your organization can leverage any type of storage (including Exadata and flash arrays), any type of server connectivity (e.g., storage area network [SAN], InfiniBand, or IP-based), and any type of replication (e.g., storage-based or Data Guard). In addition, Phoenix operates over existing communication lines and has no impact on bandwidth requirements, freeing you from one of the most costly line items in disaster recovery budgets.

[1] Information Technology Intelligence Consulting (ITIC). Hourly Downtime Tops 300K for 81% of Firms; 33% of Enterprises Say Downtime Costs > $1M. May 2017. https://itic-corp.com/blog/2017/05/hourly-downtime-tops-300k-for-81-of-firms-33-of-enterprises-say-downtime-costs-1m/

Minimum Downtime

Continuous application availability is achieved by maintaining zero data loss and full consistency across applications, thereby reducing the risk of lost revenue, productivity, or customers.

Cross-App Consistency

Phoenix synchronizes all applications and databases in the Oracle environment to one consistent point in time, allowing the fastest possible recovery.

Unmatched Cost Reduction

No three-data-center topology. No bandwidth upgrades. Less human intervention. Continuous application availability. Phoenix reduces capital, operational, and risk-related costs.

No Distance Barrier

Locate your DR site at any distance from the primary site. Phoenix augments your asynchronous replication and protects the entire data lag right at the primary site.

No Costly Communication Lines

The disaster-proof Black Box protects and transfers the data lag from its location at the primary site, eliminating bandwidth costs related to synchronous replication.

Continuous Application Availability at Flash Speeds

Phoenix protects the most recent not-yet-replicated snapshot and is the only technology that enables continuous availability of flash-based storage arrays.

The Phoenix Black Box resides at the primary data center. It uses Oracle multiplexing to receive and protect a copy of the Oracle Redo log and Archive log files. These files constitute the lag between data at the primary site and replicated data at the remote site. In a disaster, the Black Box transfers these files to the remote site, where the Phoenix Recoverer works with the remote Oracle host to recreate an exact, consistent copy of what was in the primary data center at the time of the disaster.

Larry Carpenter – Oracle Presents Axxana’s ZDL solution

see more videos