Home » RDBMS Server » Backup & Recovery » Archive log retention w/RMAN
Archive log retention w/RMAN [message #128809] Wed, 20 July 2005 14:57 Go to next message
ddummer
Messages: 1
Registered: July 2005
Location: Minnesota
Junior Member
All,
My company recently converted to using RMAN. Given current governmental guidelines we need to retain data for 7 years for financial data. It was decided that we would simply take a backup once a month ad set it to have a 2555 day retention. Where we have run into an issue is that rman will not mark any archive logs obsolete because it may need them to recover from the 7 year backup to current point in time, even though there are multiple backups since the 7 year backup. Since a requirement to retain data for multiple years is not a unique request, there must be a way to do this with rman without it trying to retain all the archive logs. Any ideas out there ?
Re: Archive log retention w/RMAN [message #128813 is a reply to message #128809] Wed, 20 July 2005 15:46 Go to previous message
Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
>>Where we have run into an issue is that rman will not mark any archive logs obsolete

Always backup the archivelogs along with the database datafiles backup.
Now for point of ease lets call this as full_backupset (datafiles + archived logfiles + controlfiles + spfile).

Once you are done, you can remove the old archived logs.
You can ask RMAN mark these backupsets ( backup of datafiles) as UNAVAILABLE.
Put this full_backupset in a tape. archive it.


Later, when you want restore , all you need to do is,
restore full_backupset from tape to its original location.
ask RMAN to mark those backupsets and backuppieces that it created (identfied by tag or date) before as AVAILABLE.
Proceed restoration.

This is what we do.
There is a backup everyday. Backupsets are retained locally in disks for 3-7 days ( depending on volume / need).
Every day the new Full_backupset is loaded into tape. Tapes are retained locally for 30 days and then archived to a remote place.
Every Month-End Backup is tagged Month_End_tape.
Further it goes with all kinds of naming conventions ( yearly, quaterly, weekly,HR_backuP_before_new_payrollSYTEM etc) depending on the group that needs the data to be archived.
Whenever you need, you get the tape which has all you want (archived log/datafiles/controlfile/spfiles and a exported dump of RMAN catalog itself, incase, we need to rebuild the catalog.).
Previous Topic: Please help
Next Topic: How can i restore the backupset on different host?
Goto Forum:
  


Current Time: Fri Apr 19 21:55:01 CDT 2024