Just because your database sits in your own data center doesn't mean you can't leverage OCI's immutable vault. There are two primary architectural paths to send backups to OCI, both capable of utilizing Retention Locked policies.
Option A: The "Premium" Path (Autonomous Recovery Service)
You can connect your on-premise database directly to the OCI Autonomous Recovery Service (ARS).
The Pros: This brings the "Cloud Native" advantages to on-premise: Real-time data protection (Zero Data Loss) and Incremental Forever backup strategies.
The Requirements: This route requires a robust Site-to-Site VPN or FastConnect (no public internet). It is strictly limited to Linux x86 infrastructure and requires a recent 19c patch set.
Option B: The "Universal" Path (Database Backup Cloud Service)
For environments where ARS isn't a fit (e.g., non-Linux OS or no VPN), we utilize the Database Cloud Backup Module.
The Pros: Flexible and runs over the secure public internet (HTTPS). Even allows for encrypted and compressed backups without buying the corresponding database options.
The Cons: You lose the "Real-time" redo transport (potential data loss between backup intervals) and must manage standard Full/Incremental backup cycles.
The Critical "Gotcha": The Wallet
Whether you use Option A or B, there is one single point of failure that renders an immutable backup useless: The Encryption Wallet (TDE). If you lose your on-premise data center to ransomware and haven't backed up the local TDE wallet to a separate, secure location (or Vault), your immutable backups in OCI are cryptographically locked forever. Always backup the wallet separately.