We just went through this....we considered the approach that you proposed below, it turned out to be more work than we needed to do. The following is what we ended up doing:
Stanza in dsm.sys: SErvername DP COMMmethod TCPip TCPPort port# TCPServeraddress server address nfstimeout 120 txnbytelimit 25600 tcpbuffsize 512 tcpwindowsize 64 resourceutilization 5 largecommbuffers yes commrestartduration 480 commrestartinterval 120 inclexcl /opt/tivoli/tsm/client/oracle/bin64/dsm_dp.inclexcl schedlogname /opt/tivoli/tsm/client/oracle/bin64/dsmsched_dp.log errorlogname /opt/tivoli/tsm/client/oracle/bin64/dsmerror_dp.log schedmode prompted passwordaccess prompt schedlogretention 10 d ERRORLOGRetention 10 d Dsm.opt in tdp directory: Servername dp Dsm_dp.inclexcl in tdp directory: INCLUDE /adsmorc/.../DB* DBTAPE_TDPNC (or RMAN_TAPE_POOL) INCLUDE /adsmorc/.../LOG* DBDISK_TDPNC (or RMAN_DISK_POOL) You will need the dba to specify a naming convention so all database files start with DB and all log files start with LOG. Hope this helps......we struggled with the right strategy for a while. Let me know if you have any questions. Ingrid -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jurjen Oskam Sent: Wednesday, November 24, 2004 9:16 AM To: [EMAIL PROTECTED] Subject: Different stgpool for RMAN archivelogs and datafile backups? Hi there, For several Oracle 9i databases, we use RMAN and TSM for Databases to store the backups in TSM. This works fine. However, both database backups and archivelog backups go to the same storagepool. The database is about 400 GB large, and this goes straight to tape. Archivelog backups are much smaller, perhaps 1 GB each time. Archivelog backups occur several times each day. These also go directly to tape. What this means is that one drive is occupied most of the time by the archivelog backups. This is inconvenient; the drive could be put to better use. How I think this problem could be solved: * create a disk stgpool, say RMAN_DISK_POOL * create a tape stgpool, say RMAN_TAPE_POOL * define the MAXSIZE parameter for RMAN_DISK_POOL * define the NEXTSTGPOOL paramater for RMAN_DISK_POOL to point to RMAN_TAPE_POOL * point RMAN to RMAN_DISK_POOL Will this work? Is there perhaps a better way of solving this problem? (Is it even a problem at all?) A possible problem with this setup might be that the TSM server doesn't know the size of an RMAN-backup ahead of time, so everything goes to RMAN_DISK_POOL and things break when too large 'files' end up in RMAN_DISK_POOL. (In our setup, the backup piece size is quite large, much larger than the typical archivelog backup. Choosing a correct value for MAXSIZE wouldn't be too difficult.) Thanks, -- Jurjen Oskam
