RMAN (Recovery Manager)

Introduction

rman stands for recovery manager .It is utility/tool to take backup and perform restore and recovery. it is also known as rman client. rman executable is located at $ORACLE_HOME/bin. when we type rman and hit enter it will internally call recover.bsq file.
Brain behind rman is recover.bsq which is located at $ORACLE_HOME/rdbms/admin.

Target Database:  The database which is going to backup(source)

Backup Set
It is a logical structure that contain one or more backup pieces.
Default one backup piece for one backup set.

Backup Piece
It is a physical file or operating system file which containing the backup of datafile, archive redolog file and control file.

No  Catalog
Default RMAN is configured in NO CATALOG Mode.
RMAN backup information will be stored in Controlfile.

Catalog
Backup information stored in CATALOG that is seperate from TARGET database in the form of tables and views.
bacup information also stored in controlfile.

Catalog Database
In which catalog object will store.

Catalog Owner
Who owns the catalog object.

Degree of Paralism
The number of channel that rman can open during backup or recovery.
Default is 1 Channel.

Backup Optimization rman doesnt perform a file backup if it has already backed up identical version of the file.

Image Copy
Image copies are similar to the copies of operating system files.
We can make image copies of datafile, controlfile and archive redolog file.
Rman image copies can be made only to disk.
they cant be made to tape.

Proxy Copy rman can alos perform a special kind of backup called the proxy backup.
proxy copies cant be used to disks.

CONFIGURING RMAN:-

By default the RMAN configuration is stored in the control file. You can see the default values for the configuration parameters by using RMAN to connect to the database and issuing the SHOW ALL command.

[oracle@rizwan ~]$ rman

Recovery Manager: Release 11.2.0.3.0 - Production on Mon May 18 00:04:19 2015

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target /;

connected to target database: PROD (DBID=246965557)
using target database control file instead of recovery catalog

RMAN> show all;

RMAN configuration parameters for database with db_unique_name PROD are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/d01/oracle/product/11.2.0/dbs/snapcf_prod.f'; # default

RMAN> show RETENTION POLICY;

RMAN configuration parameters for database with db_unique_name PROD2 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default


RMAN> show ARCHIVELOG DELETION POLICY;

RMAN configuration parameters for database with db_unique_name PROD2 are:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default


RMAN> show CONTROLFILE AUTOBACKUP FORMAT;

RMAN configuration parameters for database with db_unique_name PROD2 are:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default