Availability Service Level Objectives (SLOs)

This topic describes the Service Level Objectives (SLOs) for Oracle Autonomous Database on Shared Exadata Infrastructure.

Recovery Time Objective Service Level Objectives

Oracle Autonomous Database on Shared Exadata Infrastructure is engineered to return an application online following an unplanned outage or a planned maintenance activity within single-digit seconds. The following table outlines the target Recovery Time Objective (RTO) SLOs for different failure events.

Event	Recovery Time Objective (RTO) Service Level Objective	Recovery Point Objective (RPO) Service Level Objective, Maximum Possible Data Loss
Events requiring failover to a standby database when Autonomous Data Guard is enabled, such as: Data corruptions Full database failures Complete storage failures Availability Domain or Region failures	Local Standby Database two (2) minutes Cross-Region Standby Database fifteen (15) minutes See Autonomous Data Guard Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for more information.	The maximum possible data loss is 1 minute.
In the case of an Autonomous Database without a standby database, with events that require restoring from backup, such as: Data corruptions Full database failures Complete storage failures	Based on the size of the database: 1 hour + (1 hour per 5 TB) For example, a 5 TB database has a Recovery Time Objective (RTO) of up to 2 hours.	The maximum possible data loss is 1 minute.
In the case of an Autonomous Database without a standby database, with events that require restoring from backup, such as: Availability Domain failures, in regions with more than one Availability Domain See Regions and Availability Domains for information on Availability Domains.	48 hours	The maximum possible data loss is 1 minute.