High Availability

High Availability is a system's ability to remain operational and accessible at a high percentage of time. To achieve High Availability with OCI GoldenGate, you can create a peer deployment in the same region as your primary deployment (local standby) or a different region (cross-region standby). This set up ensures that the recovery point objective (RPO), which is the maximum amount of data lost before OCI GoldenGate is restored in the standby Availability Domain (AD), is zero. The recovery time objective (RTO), which is the maximum amount of time to restore OCI GoldenGate in a standby AD, depends on the amount of data stored on the deployment. The higher the storage utilization is, the longer the RTO will be.

Consider selecting the same standby regions as your source and target instances. For example, if your Autonomous AI Database standby is in Frankfurt, select Frankfurt for your OCI GoldenGate deployment standby as well.

The following concepts are essential for working on OCI GoldenGate High Availability:

• Primary deployment: The main data replication deployment that you first create.
• Peer deployment: A standby deployment that you can switch to in the event of a disaster or service disruption.
• Local peer: A peer deployment that resides in the same region as the primary deployment, but in a different Availability or Fault domain.
• Remote peer: A peer deployment that resides in a different region.
• Recovery point objective (RPO): The maximum amount of data that could be lost before OCI GoldenGate is restored. For OCI GoldenGate, the RPO is zero.
• Recovery time objective (RTO): The maximum amount of time to restore GoldenGate. The RTO depends on the amount of data stored on the deployment. The higher the storage utilization, the longer the RTO.