Zero Data Loss Autonomous Recovery Service

This image describes real-time data protection enabled with a single click which configures Recovery Service as an alternative log destination for the protected database. As redo changes are generated in database memory, they’re automatically sent to and validated on Recovery Service as received. When a database log switch occurs, Recovery Service automatically creates a compressed archived log backup and registers it the recovery catalog.

Recovery Service preserves recoverability up to the last committed transaction even if connectivity with protected databases is interrupted in-between typical log switch occurrences. If the redo stream terminates unexpectedly, Recovery Service closes the incoming redo stream and creates a partial archived redo log file backup. When Recovery Service detects the redo stream has restarted, all missing archive redo log files are automatically retrieved from the protected database, thereby keeping your recovery window intact.

Recovery validation throughout the backup lifecycle

Enhance your resilience posture with validation extending well beyond backup integrity checks to what’s needed for successful point-in-time database recovery.

This image entitled “Continuous Database-Aware Anomaly Detection and Recovery Validation” describes how Oracle Database Zero Data Loss Autonomous Recovery Service delivers unique recovery readiness:

1. Incoming redo and RMAN backup streams validated prior to storing on disk. Corrupted data, not readable by RMAN, is rejected
2. Periodic validation of backups at rest and that all database transactions (SCNs) needed for RMAN point-in-time-recovery are available
3. Outgoing restores, backup copies and replicated backups are validated prior to sending over the network

Autonomous Recovery Service delivers unique recovery readiness capabilities with multi-factor, database recovery-aware validation at every touch point, which includes periodic recovery validation for backups at rest—automatically and without overhead on production database servers.

Policy-based access controls and backup immutability

Safeguard backups using a defense-in-depth foundation with separation of production and data protection infrastructure, role-based separation of duties, and retention lock policies for backup immutability.

This image entitled, “Multi-layered Guardrails Protect Backup Integrity and Access”, describes key security best practices built into Recovery Service including:

• Recovery Service is designed to be fault-isolated from the production databases it protects. It operates within an Oracle-managed tenancy, utilizing private endpoint connectivity to the customer's tenancy.
• All backups must be encrypted, and customers may enable retention-lock in a Recovery Service protection policy to make the backup immutable; deletion or shortening the retention period is prohibited.
• Separation of duty access controls between Database Administrators (DBAs) and Recovery Service Administrators

Backups managed by Recovery Service cannot be arbitrarily modified or deleted by any administrator or user, thereby guarding against both malicious and accidental deletion. Database administrators (DBAs) interact with Recovery Service exclusively through Recovery Manager (RMAN), which orchestrates all backup and restore operations. Logically and physically separated from the customer tenancy, another layer of security depth is added; if DBA or systems administrator credentials were compromised, they couldn’t be used to attack backups residing on the service.

Built-in retention defaults and user-defined policies help you consistently meet service level agreements and compliance requirements for backup retention, including a 14-day minimum recovery window safeguarding retention from human error or malicious bad actors. If a protected database is terminated (deleted), Recovery Service automatically retains its backups for a minimum of 72 hours providing a safety net for accidental database deletion scenarios.

All protected databases are associated with a protection policy defining how the backup is managed throughout its lifecycle, including replication, retention (point-in-time recovery window), and retention lock settings for backup immutability.