You need to minimize downtime, prevent data loss, and reduce costs and operational inefficiencies associated with disaster recovery. Asynchronous replication isn’t enough, and synchronous costs too much.
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. When you lose transaction data, you also risk losing data consistency across business-critical databases and applications.
Disaster recovery in this scenario requires time-consuming identification of what data has been lost and reconstruction of application consistency, which slows down the recovery process and the return to normal operations. The longer recovery takes—that is, the longer the downtime—the greater the potential loss of revenue, customers, productivity, and reputation. Gartner Research “typically cites the cost of network downtime as $5600 per minute, which extrapolates to well over $300K per hour.
These losses don’t even include the loss of the transaction data itself. Although some organizations resign themselves to some data loss during asynchronous replication, your organization doesn’t have to tolerate any amount of data loss during a disaster. Nor should you tolerate anything but the absolute minimum downtime.
Phoenix for Oracle ensures zero data loss, maximizes availability, and saves money by continuously protecting yet-to-be-replicated data and rapidly restoring application consistency 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 zero data loss and rapid recovery 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 expensive line items in disaster recovery budgets.
Zero data loss and full consistency across applications means you can return to normal operations faster, reducing the risk of lost revenue, productivity, or customers.
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 data loss. No three-data-center topology. No bandwidth upgrades. Less human intervention. 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.
RPO = 0 at Flash Speeds
Phoenix protects the most recent not-yet-replicated snapshot and is the only technology that ensures synchronous replication 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.