Zero Data Loss for Oracle’s Flagship Database Machine
Oracle® Exadata Database Storage is a pre-configured platform of compute, storage, network, and server functions for running database workloads on premises and in the cloud. It’s optimized to prevent network bottlenecks, making it ideal for online transaction processing (OLTP), data warehousing, virtual desktop infrastructures, flash-based storage, and other operations that require high input/output (I/O) rates (i.e., fast throughput) and minimal data access times (i.e., low latency). Axxana’s Phoenix for Oracle enables organizations to take full advantage of Exadata by ensuring zero data loss without compromising the performance gains that Exadata offers—or requiring costly fiber or cabling.
Getting to Zero Data Loss with Exadata
In an ambitious disaster recovery model, an organization running Oracle databases would strive to use synchronous replication (via Oracle Data Guard and/or Far Sync) to ensure that essential data is not lost. However, synchronous replication may not be feasible for the following reasons:
High data transmission costs. Synchronous replication must be executed across costly fiber optics or other dedicated cabling that supports minimum latency in order to ensure zero data loss in case of a disaster. Exadata (e.g., when used for flash-based storage) imposes such high I/O rates that it is almost impossible to find bandwidth that matches its extremely low latency requirements.
Additional latency. With synchronous replication, each write operation must be propagated to a remote site. This propagation delay imposes additional latency on write performance, and it robs organizations of the performance gains that cause them to seek Exadata in the first place.
Axxana’s Phoenix for Oracle: Zero Data Loss Without the Performance Overhead
Axxana’s Phoenix for Oracle, when used with Oracle Data Guard, addresses these challenges by allowing Exadata to replicate asynchronously at any distance, while still protecting data that has not yet been written to the remote disaster recovery site. In this scenario, organizations can ensure zero data loss for all their business-critical applications. That is, they can achieve recovery point objective (RPO) = 0 while meeting the following goals:
Reduced data transmission costs. Organizations can maintain unreplicated data (i.e., lag) at the primary Exadata site. This lag is protected inside the disaster-proof Phoenix Black Box, so in case of a disaster, it is not lost or damaged. During recovery, the intelligent PhoenixOS™ transfers the lag to the disaster recovery site (standby database).
Minimal latency. By avoiding synchronous replication—and the associated propagation delays—to the remote disaster recovery site, organizations can significantly reduce the latency overhead on write operations. Although synchronous writes occur to the Phoenix system, overall latency is minimal because Axxana’s Phoenix is located in the same data center as the primary Exadata platform.