In my previous article I described some best practices in architecting database systems High Availability Levels (HA) 2 and 3 describing some technical solutions based on Data Guard, Standby database and Oracle Real Application Cluster (RAC). This time I’ll continue till Availability level 4 describing cluster database solutions based on Oracle Extended RAC and Oracle Maximum Availability Architecture (MAA) principles with combinations of Oracle RAC and Standby databases. I suggest reviewing a few of my previous articles on database High Availability including the Availability Continuum graph that illustrates and depicts the increases in availability that can be gained with the progression between levels of availability:
High Availability and SLA requirements for Oracle database
Oracle High Availability – ASM, Clusterware, Cold Failover
Oracle database High Availability – Data Guard, Standby, RAC
Availability Level 3b: Recovery via Redundant Components – Extended RAC
Oracle Database with Oracle RAC architecture is designed primarily as a scalability and availability solution that resides in a single data center. It is possible however, under certain circumstances, to build and deploy an Oracle RAC system where the nodes in the cluster are separated by up to 100 kilometers, to share the same RAC database with multiple RAC instances spread across two sites. This architecture is referred to as an Extended RAC or Metro cluster. We can consider this database architecture as an extension of Availability level 3.
The advantages of using Oracle RAC on extended clusters include: Read more »