From the course: Oracle Database 12c: Backup and Recovery

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Managing expired RMAN backups

Managing expired RMAN backups - Oracle Database Tutorial

From the course: Oracle Database 12c: Backup and Recovery

Start my 1-month free trial

Managing expired RMAN backups

“

- [Instructor] Expired backups in RMAN are different compared to obsolete backups. A status of expired means that the backup piece or backup set is not found in the directory where RMAN is looking for it. For example, if we manually deleted one of our RMAN backup files. By default, RMAN stores the status and location of database backups in the database control file. If the database control file indicates that a backup should exist under a specific directory, but maybe someone deleted that file using the Linux RMAN command, RMAN will tag this backup as expired. In order for RMAN to detect if backup files are missing or not, we need to run a crosscheck command manually. This command instructs RMAN to validate that all of the backups of a database it thinks that exists do indeed exist in our file system. Let's see this in action. So, going back to our RMAN prompt, let's type the crosscheck backup command. This will cause RMAN to scan the directories it knows backups were stored in and…

Contents