High Availability

Explore approaches to High Availability to ensure minimal OCI GoldenGate service disruptions.

About High Availability in OCI GoldenGate

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).

If you're also using Autonomous Database as your source or target, consider selecting the same standby regions as your Autonomous Database instances. For example, if your Autonomous Database standby is in Frankfurt, select Frankfurt for your OCI GoldenGate deployment standby as well.

Note:

Peer deployments are billed at the same rate as your primary deployment. Learn more about OCPU management and billing.

Concepts

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.
  • Recovery point objective (RPO): The maximum amount of data that could be lost before OCI GoldenGate is restored in the standby AD. For OCI GoldenGate, the RPO is zero.
  • Recovery time objective (RTO): The maximum amount of time to restore OGG in a standby AD.