How to Restore and Clone an OCI DB System from an Automatic Backup

Kumaran Murugan — Thu, 24 Sep 2026 07:31:57 +0000

If you're running Oracle databases on OCI's Base Database Service, one of the most useful recovery skills to have is knowing how to spin up a completely new DB system from an existing automatic backup — whether you're recreating a test environment, recovering from an accidental termination, or just validating that your backups actually work.

In this walkthrough, I'll take you through the full process: terminating an existing DB system, and rebuilding it from scratch using nothing but an automatic backup.

Why this matters

OCI decouples compute and storage lifecycle from your actual data. That means even if a DB system is gone, your data isn't — as long as a backup exists, you can rebuild the entire compute/storage/networking stack around it. This is a pattern worth practicing before you need it in a real incident.

Step-by-step walkthrough

1. Locate your source backup
Navigate to your DB system's Backups tab and review the available automatic incremental backups, each with its own start/end timestamp.

2. Start the restore
Select the backup you want and choose "Create database" from its action menu — this launches the Create Database from Backup wizard.

3. Choose what to restore
Decide whether to include all PDBs from the backup, or select specific ones.

4. Pick your target compartment
The new DB system doesn't have to go back into the same compartment — useful if you're rebuilding into a test/dev compartment instead of production.

5. Configure compute shape
Choose your shape series (AMD, Intel, or Ampere) and OCPU count.

6. Configure storage
Pick your storage management software (Oracle Grid Infrastructure or Logical Volume Manager) and performance tier.

7. Add SSH access and licensing
Paste or upload your SSH key, and choose License Included or Bring Your Own License.

8. Set up networking
Select your VCN, subnet, and hostname prefix.

9. Set the database name and credentials
Name your database, then provide the SYS password — plus the source database's TDE wallet/RMAN password, since that's required to unlock the backup.

10. Submit and monitor
The whole operation runs as a single Work Request, so you can track provisioning, networking setup, and the actual database restore in one place, right through to "Available."

What I learned

A few things stood out to me doing this hands-on:

The TDE wallet/RMAN password is non-negotiable — without the source database's original password, the backup can't be unlocked, so document it defensively.
Recovery area storage is read-only and auto-derived from the backup — you don't configure it directly.
You get real flexibility on where the new system lands — different compartment, VCN, even subnet — which makes this a genuinely practical way to spin up isolated test/dev copies of production data without touching the original.

If you're studying for the OCI Architect certifications or just want to build confidence in your OCI story, I'd recommend running through this exact exercise once in a sandbox — it's the kind of thing that's much better to have already practiced before you need it under pressure.

Kumaran Murugan is an Oracle Apps DBA and OCI Cloud Administrator with 5+ years of experience in Oracle E-Business Suite, Database migrations, and OCI infrastructure. Connect on www.linkedin.com/in/kumaranmurugan.

DEV Community: Kumaran Murugan

How to Restore and Clone an OCI DB System from an Automatic Backup

Why this matters

Step-by-step walkthrough

What I learned