Use RMAN to Manage BackupSet -RETENTION POLICY

With Oracle 9iR2, We have a new way to let RMAN to manage backupset better.
That is CONFIGURE RETENTION POLICY command .

If we have enough backups to meet a specific recovery window.
We can also tell RMAN to keep a specific number of copies of datafiles and controlfiles.

For example:
If I have enough backupset to recover the database to seven days ago, we can issue:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;

Moreover, to insure that we have at least two copies of each datafile and controlfile backup, we can issue:

CONFIGURE RETENTION POLICY TO REDUNDANCY 2;

RMAN will keeps all archived redo logs and incremental backups necessary to insure the retention policies can be met.
When a backup piece is no longer needed, RMAN marks it as obsolete.

If we want to clear out all obsolete backup files, we can simply issue DELETE OBSOLETE;
RMAN command and RMAN handles the deletion of the corresponding physical files.

So,Under Oracle9iR2,We can use RMAN to manage all of us backupset. It's very easy and convenience.

Some testing is following:

1.Use CONFIGURE to change the setting

 

2.You may Need CROSSCHECK

If you have delete your backupset manual ,you may need to CROSSCHECK first.

With this step ,Rman will check does these file is exists on your disk.

If a backup piece is unreadable or absent, then RMAN marks the backup piece EXPIRED in the output of the list command
and the recovery catalog views.
If it was marked EXPIRED but is now available, RMAN marks the backup piece as AVAILABLE in the output of the list
command and the recovery catalog views.

3.DELETE OBSOLETE

Now you can use rman to list and delete obsolete file from disk.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/13165828/viewspace-610836/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/13165828/viewspace-610836/