Meeting RPO and RTO Requirements for CRM Application on Oracle Cloud Infrastructure (OCI) DB Systems
Question
An automobile company wants to deploy their CRM application for Oracle Database on Oracle Cloud Infrastructure (OCI) DB Systems for one of its major clients.
In compliance with the business continuity program of the client, they need to provide a Recovery Point Objective (RPO) of 24 hours and a Recovery Time Objective (RTO) of 1 hour.
The CRM application should be available even in the event that an entire OCI Region is down.
Which approach meets these requirements in the most cost effective manner? (Choose the best answer.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.B.
The question is asking for the most cost-effective approach to deploy a CRM application on Oracle Database on OCI DB Systems for a major client, with a Recovery Point Objective (RPO) of 24 hours and a Recovery Time Objective (RTO) of 1 hour. The application must also be available even in the event that an entire OCI Region is down.
Option A: This option involves deploying a single-node VM Oracle database in one region and manually configuring an RMAN database backup schedule to take hourly database backups. The backups are then asynchronously copied to object storage in another OCI region. If the primary OCI region is unavailable, a new single-node VM Database is launched in the other OCI region, and the production database is restored from the backup.
This approach meets the RPO requirement since backups are taken hourly, but it does not meet the RTO requirement since it may take several hours to launch a new VM and restore the database from the backup. Additionally, this approach does not provide high availability since it only uses a single VM database.
Option B: This option involves deploying a single-node VM Oracle database in one region and replicating the database to another single-node VM Oracle database in another region using a manual setup and configuration of Oracle Data Guard.
This approach meets the RTO requirement since the standby database can be activated within an hour in the event of a failover. However, it may not meet the RPO requirement since the standby database may lag behind the primary database by several minutes or hours depending on the configuration. Additionally, this approach does not provide high availability since it only uses a single VM database.
Option C: This option involves deploying an Autonomous Transaction Processing (ATP) database in one region and replicating it to another ATP database in another region using Oracle GoldenGate.
This approach provides high availability since ATP databases are designed to be highly available and scalable, and Oracle GoldenGate ensures that data is replicated in near-real-time. It also meets the RTO requirement since failovers can be completed within a few minutes. However, it may not meet the RPO requirement since there may be some data loss in the event of a failover.
Option D: This option involves deploying a two-node VM Oracle RAC database in one region and replicating the database to another two-node VM Oracle RAC database in another region using a manual setup and configuration of Oracle Data Guard.
This approach provides high availability since Oracle RAC databases are designed to be highly available and scalable, and Oracle Data Guard ensures that data is replicated in near-real-time. It also meets the RTO requirement since failovers can be completed within a few minutes. It also meets the RPO requirement since Data Guard replication can be configured with zero data loss.
Therefore, Option D is the most cost-effective approach to meet the requirements since it provides high availability, meets the RPO and RTO requirements, and uses a two-node VM Oracle RAC database, which is likely to be more cost-effective than an ATP database.
