![]() ![]() It depends on whether a full-backup is available within the last 4 days. ![]() Please keep in mind that sometimes it might not be just 4 days. In our example above, any backup that we have in our system (both on RMAN catalog, and as physical RMAN backup files at the filesystem level) that is older than 4 days is considered obsolete. There is a big difference between Obsolte and Expired RMAN backup. $ rman target /ĬONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS So, any backup that is older than 4 days is considered obsolete and old. In the following example, retention policy is 4 days. To identify your retention policy, connect using RMAN and and execute “show all” and look for the following line. The main parameter that decides what to delete is the retention policy. This tutorial explains how to identify the backups that are obsolete and expired, and how to properly delete them from RMAN. If you don’t properly delete obsolete and expired Oracle DB backup from the catalog, it will cause some unnecessary throw error message during backup and also it will take-up space at the filesystem level.Īlso, it is not recommended to directly remove the RMAN backup files from the filesystem using Linux rm command. If you are sysadmin, sometimes you might find yourself dealing with Oracle backups.Īpart from taking oracle RMAN backup, you should also understand how to Delete the old backups from the RMAN catalog and from physical filesystem.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |