Skip to content
DBAExperts
Oracle Backups & recovery

How to back up an Oracle database with RMAN

RMAN is Oracle's native tool for consistent, recoverable backups. A poorly made backup is worthless the day you actually need it.

  1. 1

    Check the archiving mode

    For hot backups and point-in-time recovery you need ARCHIVELOG. Verify the status before backing up.

    SQL> SELECT log_mode FROM v$database;
  2. 2

    Connect to RMAN

    Open RMAN against the instance. Use the recovery catalog if you have one; otherwise the control file works.

    $ rman target /
  3. 3

    Run a full backup with archivelogs

    Back up the database and the archived redo logs in the same command to get a consistent set.

    RMAN> BACKUP DATABASE PLUS ARCHIVELOG;
  4. 4

    Consider an incremental for day-to-day use

    Level 0 is the baseline; level 1 backs up only changed blocks. It cuts both time and space.

    RMAN> BACKUP INCREMENTAL LEVEL 1 DATABASE PLUS ARCHIVELOG;
  5. 5

    Validate the backup

    List what was backed up and confirm it is restorable. An untested backup is just an assumption.

    RMAN> LIST BACKUP SUMMARY;
RMAN> RESTORE DATABASE VALIDATE;

// common mistake

Backing up without ARCHIVELOG only lets you recover to the last cold backup. You will lose every transaction that came after it.

// when it's worth an expert

If the backup takes too long, fills the disk, or you have never tested a real restore, it is worth reviewing before an incident hits. At dba.mx we design and test backup strategies at a fixed price.

Book an assessment — from USD $550

This guide is for reference and uses example commands. In production, adapt to your version and test in a safe environment first.