TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 Hi all
Regarding Anton's check list below, I have a couple of questions. 1) Do I really need to delete and redefine the drives,libray,paths etc? I understand that I will need to update the /dev/rmt/??? entry for the drives to make sure they reflect how the drives are viewed on the new system. But apart from that things should in my mind be exactly the same as before. As far as the library is concerned, it's just an alias in the ibmatl.conf file anyway and I know that works as I can use the mtlib command to interrogate it. Am I missing something? and... 2) Do I really need to run the 'checkin libv' commands. Looking at the newly restored system I can see that TSM knows all the vols in the TAPEPOOL and also the qlibv command shows me the volumes I also see on the still live server. Again, am I missing something? Many thanks again for this list Anton, much appreciated. All the best Farren Minns |-----------------------------+-------------------------------------------| | anton walde | | | <[EMAIL PROTECTED]> | | | Sent by: "ADSM: Dist Stor | To| | Manager" | ADSM-L@VM.MARIST.EDU | | <ADSM-L@VM.MARIST.EDU> | cc| | | | | 15/03/2006 15:44 | Subject| | | Re: [ADSM-L] New TSM | | Please respond to | Server, DB and STG | | "ADSM: Dist Stor | POOL question | | Manager" | | | <ADSM-L@VM.MARIST.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 e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ######################################################################
