Stefan, While I prefer to use the rman design as depicted in the Oracle/TSM doco, here is how I have done this in the past.
Tasks are script based, executed by cron, and use rman so the repository and catalogs are maintained. Logs are archived to TSM every 5-30 minutes depending on the system disk availability. Database backups are sent to local disk daily using rman. Each process creates a dummy, or lock file that is checked before execution to assure that the processes do not run simultaneously. On the TSM server the flat-files obviously create a retention issue so I made a management class for the flat-file directories with the following backup settings (even though Oracle cuts log files they are not archived, Oracle log files are always stored as backup items): Versions Data Exists: 1 Retain Extra Versions: 0 Versions Data Deleted: 1 Retain Only Version: 14 A cron job maintains the latest 3 versions of the DB flat file backups on disk, purging those that are older. Rman retention is set to 14 days. Flat file DB backups: when the object is deleted from the disk by the cron task TSM's next file backup will set them as inactive and expire them once the "Retain Only Version" setting, in my case 14 days, is met. The final piece is to make sure you still create and schedule a rman task to purge, crosscheck, and sync the repository/catalog and expire the old log files that are backed up to the TSM server. The "versions exist and retain extra" are kind of irrelevant as all the flat-files have a unique file-name and remain active versions until they are removed from the file-system. The RMAN retention setting and "Retain Only" can be adjusted to meet your retention needs. -Rick Adamson -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Stefan Folkerts Sent: Thursday, September 12, 2013 9:26 AM To: [email protected] Subject: [ADSM-L] Oracle v9 backup and restore without TDP Hi guy's, A customer of ours is investigating cutting out the Oracle TDP for Oracle v9 and replacing it with rman backups to disk that get picked up by the TSM B/A client. I am wondering if people here are doing this already. I'm no Oracle or rman man but I wonder if you can create a workable environment with scripting and procedures, I understand we need disk space for the 'dumps' to disk and some space to stage the restore from TSM before it goes back to Oracle. But how about archive log backups and how to go about telling rman a backup is back on another disk ready to restore to Oracle. Can you script the name of the backups with rman and is this usually done with the B/A archive function or the backup function. I can image that the Oracle naming might be an issue. If anybody here could give me some pointers that would be great, it's a fairly large Oracle environment with full backups of more than 40TB's and single database or multiple TB's. Regards, Stefan
