This content has been marked as final. Show 16 replies
you can do it using obsolete backup by using TAG or giving backup location.... ..... expired backups are not available so you can't use them.......
my backup retention period is 7 days, i want to use those obsolete backups for restore/recover a database.
could you share the steps
provide OS and oracle version... and also tell me why you want to restore...is there anything goes wrong....
Edited by: Niket Kumar on Jan 25, 2013 12:13 PM
OS version is : AIX Version 7.1
DB version is : 126.96.36.199.0
Actually in our environment we are taking cold backup only, so we planned to go for RMAN. Testing scenario is in process!!
this will help you...
you can check rman logs for obsolete backup locations.......
As long as the obsolete backup is still there where RMAN thinks it is, the restore will just use it if needed according to your desired point-in-time-recovery.
No further action from your side (except the restore command) needed.
If the backup is expired, you need to catalog it to inform RMAN that it is (again) accessible.
"Don't believe it, test it!"
First i've to go through this document and then catch u
so as per your point, no need to catalog obsolete backups when we restore/recover
no...as they are just became obsolete due to time policy but they are remain catalogged already in RMAN....
Thanks Hesse.. I got some idea about this. Your conversations very helpful to me.
Once again thanks..
Excellent support from my seniors...
maja wrote:This is already marked as answered but reading through it seems that the OP might benefit from a summary and clarification of what it means for a backup to 'expired' or 'obsolete'.
Could any one share, how to recover a database using obsolete/expired backup using RMAN
thanks in advance
"Expired" means the backup has been physically removed from where the rman repository thinks it is. If you move or delete a backup by use of any means other than an rman 'delete' command, rman has no knowledge of that fact and will continue to believe the backup is available. An rman 'crosscheck' command will 'crosscheck' the list of known backups against reality. If a backup is found to have 'gone missing', that backup's record in the repository will be marked 'expired'. An rman 'delete expired' command will remove all repository records that are marked 'expired'.
"Obosolete" means the backup is no longer needed to enforce the recovery policy. Several things to note about this:
- A backup that is older than "retention policy days" will not be considered obsolete if it is still needed to enforce the retention policy. All recovery has to begin with a full backup before any incremental backups and redo records are applied. So the newest full (incremental level 0) backup (as well as all incremental 1 and archivelog backups subsequent to that full backup) will never be obsolete, regardless of its age.
- backups are not 'marked' as obsolete. The are evaluated for obsolescence when processing an rman command that cares about it - 'delete obsolete' or 'report obsolete'. A backup that is reported as obsolete can be made "un-obsolete" by simply modifying the retention policy.
- even obsolete backups are not deleted until such time as you issue 'delete obsolete'. I've not demonstrated it for myself, but it is my understanding that if the backups are maintained in the FRA and there is space pressure on the FRA, obsolete backups can be 'automatically' deleted to make room for newer backups.
- even if a backup is considered obsolete, until such time as it is actually deleted it is still available for recovery.
- if a backup has been deleted (from rman's perspective) but is still physically available, it can be 'undeleted' from rman by use of the rman 'catalog' command.
Details for all of the above referenced commands are available in the Backup and Recovery manual at tahiti.oracle.com