Why would you run the delete obsolete command?

Why would you run the delete obsolete command? (Choose all that apply.)

Why would you run the delete obsolete command? (Choose all that apply.)

A.
To remove missing backup set pieces physically from disk

B.
To remove metadata related to backup set pieces in the control file and the recovery catalog

C.
To mark as deleted records in the control file and the recovery catalog associated with obsolete
backup sets

D.
To delete backup set pieces associated with backups that are no longer needed due to
retention criteria

E.
To remove old versions of RMAN backups



Leave a Reply 1

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


Helcio

Helcio

Deleting Obsolete RMAN Backups Based on Retention Policies

The RMAN DELETE command supports an OBSOLETE option, which deletes backups that are obsolete, that is, no longer needed to satisfy specified recoverability requirements. You can delete files obsolete according to the configured default retention policy, or another retention policy that you specify as an option to the DELETE OBSOLETE command. As with other forms of the DELETE command, the files deleted are removed from backup media, deleted from the recovery catalog, and marked as DELETED in the control file.

If you specify the DELETE OBSOLETE command with no arguments, then RMAN deletes all obsolete backups defined by the currently configured retention policy For example:

DELETE OBSOLETE;

You can also use the REDUNDANCY or RECOVERY WINDOW clauses with DELETE to delete backups obsolete under a specific retention policy instead of the configured default:

DELETE OBSOLETE REDUNDANCY = 3;
DELETE OBSOLETE RECOVERY WINDOW OF 7 DAYS;