For most enterprises, Oracle is the database that never got to modernize. The rest of the cloud estate moved to policy-driven, managed protection, while the mission-critical Oracle instance stayed on a hand-written runbook that a small team maintains and nobody wants to touch.
That runbook is more involved than it looks. A representative Oracle backup sequence enables backup mode, runs a sync, creates incremental disk snapshots, ends backup mode, then polls snapshot status in a sleep-and-check loop, switches and archives redo logs, copies those logs to a dedicated log disk, snapshots that disk, and finally purges archive logs on a short retention window. Full backups run daily and archived-log backups run hourly, with a separate scheduled job to enforce retention and still more scripts for logging, alerting, and missing-backup reports. Oracle's own RMAN carries the same weight, since it expects ongoing maintenance of backups and repository records rather than a one-time setup.
Moving Oracle to Amazon RDS removes some of that toil, but the native tooling has real ceilings. Automated RDS backups retain for 0 to 35 days, and you cannot push frequency or retention past the available options. Every restore builds a brand-new DB instance with a new endpoint, so recovery forces application reconfiguration. Backups are instance-level only: AWS Backup captures the whole DB instance and does not restore individual databases inside it. Schema or table recovery falls back to Oracle Data Pump, whose logical exports are not incremental. You can run RMAN backups on RDS, but you cannot use RMAN to restore an RDS for Oracle instance. Point-in-time recovery is bounded too, since RDS uploads transaction logs to S3 roughly every five minutes.
Oracle joins the estate
Eon, the cloud-native data backup company, brings mission-critical Oracle on Amazon RDS under the same model as the rest of your estate with Eon Backup and Recovery for Oracle, covering the modern releases RDS supports, Oracle Database 19c and 21c. Oracle in the cloud is a live enterprise priority, underscored by the general availability of Oracle Database@AWS in July 2025. The underlying Oracle hot-backup process stays exactly as your DBAs know it, with the Eon CLI acting as a drop-in replacement in the snapshot step and everything else unchanged.
One inventory, one policy model, one vault, and one restore experience now include Oracle alongside everything else you protect.
How Oracle fits the model
Oracle slots into the lifecycle every other Eon-managed resource already follows.
- Discovery into one inventory. After a one-time CloudFormation permission grant, Eon runs discovery across the account and populates a single inventory with resources and their metadata such as names, tags, and existing snapshots. Discovery reads only metadata, never the data itself.
- One policy model. Eon policies come in three types, Standard, High frequency, and Point-in-time recovery, and PITR covers RDS and Aurora through cloud-native point-in-time capabilities. For RDS, Eon supports standard snapshots held in Eon-managed vaults as well as orchestrated AWS-native continuous backups.
- Policy-driven compliance. Eon evaluates backup posture using discovery metadata and classification data, so policy and classification together drive control-violation reporting rather than manual audits.
- One restore experience. For RDS resources, Eon restores full instances and also restores the records matching a SQL query, without rebuilding the entire resource.
Data classification is part of the same model. Every newly supported resource inherits Eon's classification, mapping, discovery, and indexing, which then feeds posture controls and targets granular restores.
Recovery and resilience
Eon changes Oracle recovery on two fronts: granular, record-level restore and an isolated, logically air-gapped vault. Legacy and native Oracle protection forces all-or-nothing, full-instance restores, caps how precisely you can rewind, and leaves backups reachable from the same production boundary they are meant to protect.
First, granularity: restore a full instance when the incident calls for it, or restore only the records matching a SQL query when a bad write, a bad migration, or a corrupted table is the real problem. Native tooling rebuilds the whole resource to a timestamp and drags every legitimate write since the incident back with it, and restoring only the affected records avoids that.
Second, isolation. Eon backups live in a vault inside a dedicated vault account in your Eon tenant, logically air-gapped from your other environments, including production. That separation matters because attackers now go after backups directly: 96% of ransomware attacks target backup repositories, and only 14% of victims recover without paying. A 2025 study of 1,300 ransomware victims found 89% had their backup repositories targeted. The same risk profile applies to automated jobs and coding agents that can write bad data at machine speed with valid credentials, which is exactly what an isolated vault plus record-level restore is built to survive.
Oracle closes the last coverage gap
Oracle was the last major enterprise holdout, and bringing it under a single policy-driven model closes a real coverage gap. Support for Oracle on Amazon RDS continues Eon's recent coverage expansions, which include BigQuery backup and AWS-native point-in-time recovery for Amazon RDS and Aurora.
If you run mission-critical Oracle on RDS, see it under one inventory and one policy. Book a demo or explore the launch-week hub to walk through discovery, policy, and a granular restore on your own estate.
FAQ
Q: How long can Amazon RDS for Oracle retain automated backups?
Amazon RDS for Oracle automated backups retain for 0 to 35 days, and you cannot adjust frequency or retention beyond the available options. Eon holds Oracle backups longer in a logically air-gapped vault kept outside your production environment.
Q: Can you restore individual records in an Oracle database on Amazon RDS?
Native Amazon RDS restores always build a brand-new DB instance and cannot recover individual databases inside an instance. Eon adds granular Oracle restore for RDS, recovering the records that match a SQL query without rebuilding the entire resource.
Q: Which Oracle Database versions does Amazon RDS support?
Amazon RDS for Oracle supports Oracle Database 19c and 21c, in both Enterprise Edition and Standard Edition 2, with 21c available only in the multitenant architecture. Eon Backup and Recovery for Oracle on Amazon RDS covers these modern releases.
Q: Does moving Oracle backups to Eon change the Oracle backup process?
No. The Oracle hot-backup process stays exactly the same, and the Eon CLI is a drop-in replacement in the snapshot step, with no client software to install on the database. The DB-side sequence your DBAs already run does not change:
ALTER DATABASE BEGIN BACKUP;
-- snapshot the volume (the Eon CLI is a drop-in replacement in this step)
ALTER DATABASE END BACKUP;
ALTER SYSTEM ARCHIVE LOG CURRENT;
