Home  >  Oracle Database Administration (DBA)  >  Backup & Recovery  >  RMAN Configuration

1. Which is the default RMAN configuration ?

show all;

RMAN configuration parameters 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 ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/10gOHome/dbs/snapcf_db10.f'; # default

NOTES: 

• The parameters which are currently modified are in bold.  

• The changes in the RMAN configuration are saved automatically in the control file/ RMAN catalog.

2. How could I restore the actual configuration to the default value ?

CONFIGURE RETENTION POLICY CLEAR; 

CONFIGURE BACKUP OPTIMIZATION CLEAR; 

CONFIGURE DEFAULT DEVICE TYPE CLEAR; 

CONFIGURE CONTROLFILE AUTOBACKUP CLEAR;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR; 

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT CLEAR; 

CONFIGURE DEVICE TYPE DISK CLEAR; 

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK CLEAR; 

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT CLEAR; 

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK CLEAR; 

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT CLEAR; 

CONFIGURE CHANNEL DEVICE TYPE DISK CLEAR; 

CONFIGURE CHANNEL DEVICE TYPE SBT CLEAR; 

CONFIGURE MAXSETSIZE CLEAR; 

CONFIGURE SNAPSHOT CONTROLFILE NAME CLEAR;

3. Using substitution variables

RMAN can make use of substitution variables in creating format strings to generate UNIQUE file names. If the file names are not unique the files will be overwritten and the data will be lost.

4. Configure RETENTION POLICY

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;

>> After 30 days the backup will become OBSOLETE. 

CONFIGURE RETENTION POLICY TO REDUNDANCY 3;

>> The latest 3 backups will NOT be OBSOLETE. The others will be. 

When configuring a retention policy, RMAN will NOT cause backups to be automatically deleted.

REPORT OBSOLETE; -> List the backups (on disk) that have become obsolete with the current retention policy.

DELETE OBSOLETE; -> Delete the obsolete backup files.

delete noprompt obsolete;

NOTES:

• crosscheck backup;  -> check if the backup files exist physically on the disk

• crosscheck copy;  -> check if the files of a copy operation exist physically on the disk

• list backup;    -> To list all backup sets, backup pieces

• list expired backup;  -> To identify those backups that were not found during a crosscheck

• DELETE EXPIRED BACKUP; -> To delete the information about the expired backups in the RMAN repository

• DELETE EXPIRED COPY; -> To delete the information about the expired copies in the RMAN repository

More information about  this subject ( RMAN Configuration ) you can get from  www.in-oracle.com