Muthu,
As the other guys have pointed out, there should be a single management class with the well-known set-in-stone backup copygroup retention policies as a destination for DP for Oracle backups. Take a look in the IBM Redbook "Backing Up Oracle using Tivoli Storage Management" >>> http://www.redbooks.ibm.com/redbooks/pdfs/sg246249.pdf around page 42.
There are various methods one can use to keep Oracle backups for longer periods - the method suggested below of performing an 'export' dump of the data into a self-describing format from Oracle before TSM archiving it off for a set period of time is very valid, especially for longer retention periods: if for regulatory purposes one must keep data for, say 7 years, 10 years or even longer, this is particularly recommended as the SDF file should be readable by whichever generation of Oracle one happens to be using in the far-flung future, or even by another third-party application altogether.
However, within Oracle/RMAN, there is a way of achieving this requirement using 'format' to modify the object name at the point of backup - for example, one might format one's monthly backups to have 'monthly' in their name. Your RMAN backuppiece expiration routine can then generate lists of 'expiration candidates' based upon the name of the backup object, ensuring that any backuppieces with 'monthly' in their title are expired on a different basis to those with, for example, 'daily' or 'weekly' in their name. This setup does require a little bit of logic and working out, but can work very well.
Hope that helps,
| David McClelland
Storage and Systems Management Specialist IBM Tivoli Certified Deployment Professional (ITSM 5.2) SSO UK Service Delivery – Storage Services IBM Global Services – IBM United Kingdom |  |
| Kurt Beyers <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 16/12/2005 06:12
|
|
Hi Muthu,
The retention time of Oracle backups is completely controlled by Oracle. Any Oracle backup always receive a unique name in TSM and will thus never expire.
The backupsets must be deleted with RMAN scripts and RMAN will delete then the corresponding entries in the TSM database too.
If you want to keep certain backups like 1YEAR and 5YEAR, I just would take a full export of the database and include it then in the FS backup of TSM. There you can store it to the corresponding management class.
best regards,
Kurt
________________________________
From: ADSM: Dist Stor Manager on behalf of Muthukumar Kannaiyan
Sent: Thu 12/15/2005 23:46
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDPO and different Management Class
Hi All,
Our Oracle DBAs want to backup their database under different management
class. Do we need to take case anything special while creating management class
such as ONEYEAR and FIVEYEAR.
Separately, how do we specify management class while backing up from RMAN?
Regards
Muthu
202-458-8340 - Work
