Home » Oracle » Oracle Database » Recovery Manager (RMAN) :Benefits, media manager software

Recovery Manager (RMAN) :Benefits, media manager software

What is Recovery Manager (RMAN)

RMAN stands for recovery manager.it is a utility that can manage your entire Oracle backup and recovery activities. it is found in $ORACLE_HOME/bin. It comes with database installation

Usage
Without Catalog
rman target /
With Catalog
rman target / catalog <user>/<pass>@catdb

RMAN benefits over Manual Backups

Recovery Manager(RMAN)

(1)RMAN Backup Saves storage space because it only backs up blocks that have ever held data.
(2)Eliminates performance overhead during backups, because it doesn’t place oracle tablespace in backup mode.
(3) Helps maintain database integrity by detecting block corruption during backups.
(4)Decreases backup time by allowing parallelized and incremental backups.
(5)Maintains history of old backups and status of running backups.
(6)Has built-in reporting capabilities.
(7)Allows transition to 10g Automatic Storage Management which requires RMAN. We can use RMAN with oracle ASM storage based databases
(8) Decreases time for specific types of recoveries by allowing block and tablespace point in time options.
(9) Provides a GUI interface when used with OEM.

Media manager software

To store backups on tape, RMAN requires media manager software, a third-party software program that writes, reads, and manages sequential media such as tapes to backup and recover data. In the case of backup, RMAN starts the Oracle Server session which reads data and sends it to the media manager which writes the data to the tape device. In the case of restore, the media manager software reads the data from the tape and sends it to the Oracle Server session which restores data to the disk.
The SBT API is the interface through which RMAN interacts with the media manager. The API defines the functions that create backup files, write to/read from the backup media, and search for/remove backup files. Management of backup devices and media is handled by the media manager and is outside the scope of the SBT API.

See also  How to check Tablespace in Oracle -Size,Free space,datafiles ,growth

The core of the RMAN and media management software integration is the media management library, supplied by the backup vendor. This library contains an implementation of the SBT API functions and is linked in with the Oracle server binary. In Oracle 8.1.6 and below versions, the library must be explicitly linked in with the Oracle server binary before starting RMAN. In Oracle 8.1.7, the library is implicitly loaded by the OS at the start of the Oracle server session. In Oracle9i and 10g, the library is automatically loaded when RMAN channels are allocated. Oracle calls these SBT functions to back up and restore data files to and from media controlled by the media manager.

RMAN media management software

The common media manager software with RMAN are
Netbackup
Omniback
Tivoli
Legato Networker

RMAN base tables

  • RMAN is a powerful tool for taking backup .It maintains all the backup related information in RMAN base tables in RMAN catalog.We are listing all  tables and views are which  are generated in the catalog database.
  • Use the DESCRIBE command for each table or view to display column information.We have given some explanation for each table so that you can understand what data is residing in it

Tables

Views:

Also Reads
RMAN backup commands : Check out the RMAN Backup commands in this post. This is going to be very helpful for the person who is involved in backup and recovery
RMAN List backup commands : RMAN List backup commands are used to list the backup taken using RMAN , Date and Time, and many other details are included
Oracle RMAN interview questions: Oracle RMAN Interview Questions are a must for Oracle DBA’s looking for change. Oracle Backup and recovery is one of the essential duties of Oracle DBA
RMAN Recovery Catalog: Learn how to create an RMAN recovery catalog, how to register database in the catalog, how to catalog archived log files on the filesystem,
RMAN-06059: Check out how to resolve the RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
RMAN-20004 : RMAN-20004 happens when a Database has been cloned and a connection made from the clone to Catalog using rman without changing the DBID of the clone
https://docs.oracle.com/cd/B10501_01/server.920/a96566/rcmintro.htm

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top