RMAN -- Differences Between obsolete and expired

If you can understand the sources of the two States, You can naturally understand the differences;

Expired status:

This status is related to the crosscheck command. The crosscheck BACKUP command performs a cross-check on the backup to check whether the backup set is valid. When the crosscheck command checks that a backup has been deleted at the system level, that is, it does not exist physically, it sets the available status to expired, however, at this time, the backup is not deleted. Therefore, you cannot delete the backup at the system level. Instead, you should delete the backup in RMAN and use Delete backup ];

For example:

RMAN> List backup tag = 'Con _ Bak '; 
List of backup Sets
==============================
BS key Type LV Size Device Type elapsed time completion time
-------------------------------------------------------------
34 full 9.64 M Disk 00:00:02 23--14 14
BP key: 34 Status: available compressed: No tag: con_bak
Piece name:/bak/control19plo5s3_1_1
Control file included: ckp scn: 10309054 CKP time: 23--14 14

[[Email protected] ~] $ RM/bak/control19plo5s3_1_1
-- Delete the backup from the system
RMAN> crosscheck backup;
-- Cross-check whether the backup set is valid
RMAN> List backup tag = 'Con _ Bak ';
List of backup Sets
==============================
BS key Type LV Size Device Type elapsed time completion time
-------------------------------------------------------------
34 full 9.64 M Disk 00:00:02 23--14 14
BP key: 34 Status: expired compressed: No tag: con_bak
Piece name:/bak/control19plo5s3_1_1
Control file included: ckp scn: 10309054 CKP time: 23--14 14

RMAN> List backup summary;
List of backups
====================
Key ty LV s device type completion time # pieces # copies compressed tag
-----------------------------------------------------------------
34 B f x disk 23--14 14 1 1 No con_bak

RMAN> Delete noprompt expired backup;

-- Delete expired backup is used to delete invalid backup information.

Obsolete status:

The obsolete status is determined based on the RMAN backup retention policy. When the backup exceeds the retention policy, it will be marked as the obsolete status. Run the report obsolete command to view the status, delete noprompt obselete to delete the backup;

For example:

RMAN> run {
2> Configure retention policy to redundancy 1;
3> Backup current controlfile format '/bak/con_test _ % U' tag = 'bakcontest ';
4>}

-- Configure retention policy to redundancy 1; set the retention policy of the RMAN backup set to 1. If more than one copy is retained, it is marked as obsolete [obsolete] State. Use the preceding run code block to back up twice;

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type key completion time filename/handle
----------------------------------------------------------------
Backup set 35 23--14 14
Backup piece 35 23--14 14/bak/con_test_1aplo6pd_1_1

-- Report obsolete will display discarded backup Sets

RMAN> Delete noprompt obsolete;

-- Delete Obsolete backup

Summary:

The obsolete occurs mainly because it violates the backup retention policy [obsolete]. Delete Obsolete is required for deletion, and expired checks whether the backup set is valid at crosscheck, the main manifestation is that the backup is deleted at the system level, but the backup information is not deleted. The [invalid status] is required to delete the backup;

This article is from the "dbguy" blog, please be sure to keep this source http://dbguy.blog.51cto.com/8921728/1569360

RMAN -- Differences Between obsolete and expired