![]() The KEEP UNTIL clause never causes RMAN to consider a backup obsolete, if the backup is still required to satisfy the retention policy. 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:ĭELETE OBSOLETE RECOVERY WINDOW OF 7 DAYS Ĩ.3.4.1 DELETE OBSOLETE Behavior When KEEP UNTIL Time ExpiresĭELETE OBSOLETE does not delete backups required to satisfy the specified retention policy, even if some backups have KEEP UNTIL times set which have passed to override the retention policy. 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: 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. 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. The RMAN DELETE command supports an OBSOLETE option, which deletes backups that are obsolete, that is, no longer needed to satisfy specified recoverability requirements. ![]() For example:ĭELETE FORCE NOPROMPT BACKUPSET TAG 'weekly_bkup' Ĩ.3.4 Deleting Obsolete RMAN Backups Based on Retention Policies ![]() It then updates the RMAN repository to reflect the fact that the backup is deleted, regardless of whether RMAN was able to delete the file or whether the file was already missing. If you use the DELETE command with the optional FORCE keyword, RMAN deletes the specified backups, but ignores any I/O errors, including those that occur when a backup is missing from disk or tape. RMAN-06207: WARNING: 1 objects could not be deleted for DISK channel(s) due If you attempt to delete the object, then you receive a warning such as the following: For example, the RMAN repository says that a backup set is AVAILABLE when it is in fact no longer present on disk or tape (or missing from the media manager's catalog of the contents of tapes or other backup media). It is possible for the RMAN repository to indicate that an object has one status while the actual status of the object on the media is different. You can suppress these confirmations by using the NOPROMPT keyword with any form of the BACKUP command:Ĩ.3.3 Using DELETE FORCE With RMAN Backups If you run RMAN interactively, then RMAN asks for confirmation before deleting any files. The following examples show many of the common ways to specify backups and archived logs to delete using the DELETE command:ĭeleting backups using primary keys from LIST output:ĭELETE CONTROLFILECOPY '/tmp/control01.ctl' ĭELETE NOPROMPT ARCHIVELOG UNTIL SEQUENCE = 300 ĭelete backups based on the objects backed up and the media or disk location where the backup is stored:ĭELETE BACKUP OF TABLESPACE users DEVICE TYPE sbt # delete only from tapeĭELETE COPY OF CONTROLFILE LIKE '/tmp/%' #ĭelete all backups for this database recorded in the RMAN repository:ĭelete backups and archived redo logs from disk based on whether they are backed up on tape: For complete information about these options, see Oracle Database Backup and Recovery Reference. The DELETE command supports a wide range of options to identify backups to delete. The DELETE command supports deleting several types of backups, including:ĭELETE BACKUP (which deletes backup sets, proxy copies, and image copies), DELETE COPY (which deletes only image copies), or DELETE ARCHIVELOG as in these examples: DELETE removes the physical files from the backup media, deletes the record of the backup from the recovery catalog (if RMAN is connected to a recovery catalog), and updates the records of these backups in the control file to status DELETED. In general, use the DELETE command to remove backups that you do not want to retain. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |