RMAN 1.4 RMAN Architecture
You can start performing backups with RMAN executable from the $ORACLE_HOME/bin directory.
- The target database control file will always store the RMAN repository, which is the set of RMAN related backup and recovery information —> RMAN METADATA.
- It’s smarter to use a dedicated database to store the RAMN repository then create a special schema called the recovery catalog.
- Thus avoiding the risk of the critical metadata being overwritten when the control files runs out of space.
- Flash Recovery Area :
- This is a location on disk where the database will store the backup and recovery related files.
- MML -Media Management Layer
- RMAN can directly interact only with disk drives.
- if you want to use tape drives to store your backups, you’ll need a MML in addition to RMAN.
- RMAN can’t directly inteact with the tape drives.
- Oracle also provides Oracle Secure backup , most well integrated media management layer for RMAN backup.
Benefits of using RMAN
- The powerful Data Recovery Advisor Feature which enables you to easily diagonse and repair data failures and corruption.
- It automatically manages the backup files without DBA intervention.
- It automatically deletes unnecessary backup datafiles and archived redo log files both from disk and tape.
- Reporting of backup actions.
- Duplicating a database or creating a standby database.
- Verify available backups are useable for recovery
- Incremental backup
- I lets you perform database duplication without backups by using the network enabled database duplication feature also known as active duplication.
- It automatically detects corrupt data blocks during backups V$DATABASE_BLOCK_CORRUPTION view.
- when only a few data blocks are corrupted, you can recover at the data block level.
- Unused block complession feature, wherein RMAN skips unused data blocks during a backup.
- RMAN provides the ability to perform encrypted backups.
- You can use a powerful scrpting language which lets you write custom backup and recovery scripts quickly.