This image shows a customer environment and two cloud regions: US-East1 and US-West1.

The customer environment includes a set of users who are using various devices to connect to the cloud regions. A traffic steering policy sets the correct DNS depending on which region is active.

The US-East1 region is the primary region, and contains: an active traffic steering policy, a public facing VCN, a private VCN, and Object Storage.

The public facing VCN includes a Service Gateway and an application tier container, which includes the Oracle Flex virtual machines (VMs) and corresponding block storage for each VM.

The private VCN contains Database Cluster Services (DBCS), an RMAN backup process, and a block storage network. The block storage network is composed of:

The Object Storage includes a database backup bucket, an app backup bucket, a logging/event bucket, and a collection of bucket policies.

The US-West1 region is the standby or failover region. This region replicates the contents of the primary region and uses a failover traffic steering policy.

In normal circumstances, data flows between the customer environment and the US-East1 region as users access FLEXCUBE. FLEXCUBE writes data to the local block storage, and also writes data to the private VCN, where DBCS manages the storage of data.

DBCS uses ASM Volume management to route data to the file system folders and to block storage.

The RMAN backup process then clones data from DBCS to Object Storage outside of the private VCN.

Data is replicated from US-East1 to US-West1 in two ways:
  1. The block storage in the public facing VCN is copied to the standby region using Volume Backup Replication.
  2. The Object Storage in the primary region is copied to the standby region using Object Storage replication.

This ensures data is actively copied to the standby region. On failover, the standby region uses the RMAN backup process to rehydrate the application from the data that was copied to block storage.