We will be doing this later this year. We have a complicating problem - several disk pools using migration delay. We do this for several applications that use TSM to archive data (deleting it from within the application). We hold this data in a disk pool for fast restores, migrating it to tape after about a year. We accomplish this by using a 1 yr migration delay to make the disk pool into a queue fifo queue.
Any thoughts on how to migrate this kind of disk pool to a new system? If we follow the cook book, we delete the pool.... but this also deletes the queued data and I know of no way to repopulate the new disk pool that will retain with the most recent data sent to TSM from these applications. I'm thinking of something like this . . . ( . . . . they are on raw volumes right now . . . ) 1) migrate these disk pools to disk pool that is on a filesystem. 2) just copy the files to the new server Thanks Rick anton walde <[EMAIL PROTECTED] DE> To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: New TSM Server, DB and STG POOL question 03/15/2006 10:44 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Hallo. We changed our Hardware a year ago. We asked support to help us and got a good hand-out with all the steps to make. Here is the 'cook book': 1. you must have the samt TSM-Version on the old and new server. 2. migrate all diskpools to tape 3. backup the TSM-DB on the old server maybe to a file-devclass ( better for restore ) 4. stop the old server 5. save all the config-files from the old server ( dsmserv.opt,dsmserv.dsk,devconfig.out,volhist.out,nodelock ) 6. connect the libraryies to the new server 7. install the tsm device driver on the new server all the following steps are on the new server 8. copy the config-files from step 5. to the new server, over the existing! 9. create log-files and db-files with dsmserv format 10. check the config-files! for example the devconfig.out for devclass,devices,pathes,etc. 11. restore the db from step 3. 12. change dsm.opt: nomigrrecl expinterval = disablescheds yes 13. start the tsm-server in foreground ( dsmserv ) 14. disable sessions 15. delete all paths, drives and libraries 16. define all paths, libraries and drives again you must do step 15. and 16. because of possible changed scsi-id's 17. checkin libv <library> search=yes status=scratch checklabel=barcode 18. checkin libv <library> search=yes status=private checklabel=barcode 19. create the diskpools. If you have another directory-name for the volumes, you must delete the old ones and define new ones. 20. If everything runs fine, stop the server ( halt server ), remove the options you defined in step 12 from dsm.opt and start the tsm-server as a service like you did on the old hardware THAT'S IT! Hope that helps you. Kind regards Robert Fijan -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.