Configure a Standby Database for Disaster Recovery Using Oracle Exadata Database Service on Cloud@Customer
In the event of a disaster, your Oracle Exadata Database Service on Cloud@Customer primary database could become unavailable. A standby database is a copy of the production database that becomes available in the event of a production database outage. This playbook describes how to configure a standby database for Oracle Exadata Database Service on Cloud@Customer using the OCI interface.
Oracle Data Guard ensures high availability, data protection, and disaster recovery for enterprise data in an Oracle Database. Oracle Data Guard provides a comprehensive set of services that create, maintain, manage, and monitor one or more standby databases to enable production Oracle databases to survive disasters and data corruptions.
Oracle Data Guard maintains these standby databases as copies of the production database. If the production database becomes unavailable because of a planned or an unplanned outage, Oracle Data Guard can switch any standby database to production, minimizing the downtime associated with the outage.Architecture
This architecture shows an Oracle Exadata Database Service on Cloud@Customer primary database that transmits data to a standby database using Oracle Data Guard. The standby database is remotely located from the primary database for disaster recovery.
Before You Begin
Before you begin, ensure you are familiar with the following resources:
- "Use Oracle Data Guard with Exadata Database Service on Cloud@Customer" in Exadata Database Service on Cloud@Customer Administrator's Guide.
- Enabling Data Guard on Oracle Exadata Cloud@Customer Video.
This playbook is tested on the following software and hardware versions of Oracle Exadata Database Service on Cloud@Customer:
- Oracle Exadata Database Service on Cloud@Customer X8M-2
- Exaimage 21.2.13
- DBaaS Tools 22.2.1.1.0_220713.1149
- Oracle Database 19.16
Considerations for Configuration
Before you begin to configure your standby database, review these assumptions and considerations.
- The primary and standby Oracle Exadata Database Service on Cloud@Customer Infrastructures should be physically located in different regions to ensure high availability in the event of a disaster. The primary and standby must be managed in the same OCI tenancy and region in the OCI interface.
- The standby database is a physical standby.
- The primary and standby databases can be in different compartments.
- Oracle Database Home Software, DBaaS Tools, and Dbcs Agent versions must be identical between primary and standby VM Clusters.
- You are limited to configure one standby database for each primary database using the OCI interface. If more than one standby database is required, Oracle Data Guard configuration must be done manually.
- Your Oracle Data Guard configuration can be Active Data Guard or Data Guard. If Active Data Guard is configured, automatic backups cannot be configured on the standby database using the OCI interface.
- You cannot configure Oracle Data Guard if your primary database is encrypted with Transparent Data Encryption (TDE) Keys managed by Oracle Key Vault. As a workaround, you must create a primary database, enable Data Guard, then manually configure Oracle Key Vault for the primary and standby databases using the OCI command line interface.
- Intermediate storage is not required. Standby database instantiation will happen over the network.
About Required Services and Roles
This solution requires the following service:
-
Oracle Exadata Database Service on Cloud@Customer
These are the roles needed for each service.
| Service Name: Role | Required to... |
|---|---|
Oracle Exadata Database Service
on Cloud@Customer: sys |
|
See Learn how to get Oracle Cloud services for Oracle Solutions to get the cloud services you need.