Purity ActiveDR™, available with Purity //FA6.0+, delivers continuous, near real-time, replication between two FlashArrays™ within or across disparate data centers thus enabling data protection solutions with near-zero RPO (Recovery Time Objective) and a very short RTO (Recovery Time Objective). This results in global data protection with minimal data loss and fast failover to the Disaster Recovery (DR) site.
In this article, we will learn how to set up Oracle disaster recovery (DR) between two sites using Purity ActiveDR™.
The unit of replication, failover, and consistency with ActiveDR is a pod. Think of a pod as a logical container. Each pod is a separate namespace and can contain a mix of volumes, protection groups with member volumes, and volume snapshot history. A pod, when created, is in the promoted state, meaning it’s available to the host with read/write access. A demoted pod allows only read-only access to the host. A remote pod must be in a demoted state when a replica link is created. Local and remote pods/FlashArrays are also interchangeably referred to as the source and target pods/FlashArrays.
Here are the high-level steps that need to be performed to set up DR for an Oracle database: