08:31
When it is necessary to move an existing
TSM server from one Windows machine to another, there are two methods available
to do so. In preparation for both methods, the following needs to be done first
on the old machine first :
1) quiesce all activity on TSM server
disable sessions all
stop all processes
2) empty the disk storage pools
move data of disk pool volumes or use migration to tape pool
3) perform full database backup
Do database backup to TAPE or FILE devclass.
4) stop TSM server
Once the above steps have been completed, you can proceed with either method below.
Method A
This method will use database backup to do the move.
i) Using database backup from step 3, perform a database restore on the new server.
Notes:
- In order to do the database restore on the new machine, it will require that a similar tape device be accessible on the new machine if the database backup was done to TAPE.
- If the same library is to be used on the new machine, then disconnect the library from old machine and connect it to the new server and then configure the device configuration file with the correct device names. It is possible to use the setup wizards on the new machine to setup the server instance and configure the library so that the device configuration file is automatically written instead of having to manually edit it in preparation for the database restore
- If the database backup was done to a FILE devclass, then ftp the FILE volumes (in binary) to the new machine and do the restore using the FILE volumes.
ii) Once the database is restored and started on the new machine, recreate new DISK storage pool volumes in appropriate location and also delete the existing drives and their paths and the library and its path. Once this is done, redefine the library and drives and their paths(*) using the device names on the new machine.
iii) Checkin the scratch, private and cleaning (if appropriate) tapes in the library. For example :
checkin libv <libname> search=yes status=cleaner cleanings=xx volrange=xxxxxx,yyyyyyy....optional
checkin libv <libname> search=yes checklabel=barcode status=scratch
checkin libv <libname> search=yes checklabel=barcode status=private
Method B
This method will copy the necessary files instead of using db backup. For this method, the TSM server must be stopped. This is imperative. Do not proceed further until TSM server is stopped.
i) Copy the following files from the old server to the new server :
dsmserv.dsk
dsmserv.opt
volume history file
device configuration file
Assuming the new server instance is also server1, those files would be copied to the following path : \program files\tivoli\tsm\server1.
ii) Move all database volumes and recovery log volumes listed in the dsmserv.dsk file on old server. These database and log volumes may be moved using "binary" ftp.
Note :
The exact same paths and names for the database and recovery log volumes must be kept on the new server. For example, if the dsmserv.dsk file on old server contains :
D:\TSMDATA\SERVER1\LOG1.DSM
D:\TSMDATA\SERVER1\DB1.DSM
D:\TSMDATA\SERVER1\DB2.DSM
then, those files must be copied to the new server on the same drive letter, at the same path and using the exact same name. Failure to do so will result in the server not starting on the new machine.
iii) Once the database and recovery log volumes have been moved to the new server, the server may be started on the new server. Once this is done, recreate new DISK storage pool volumes in appropriate location and also delete the existing drives and their paths and the library and its path. Once this is done, redefine the library and drives and their paths(*) using the device names on the new machine.
iv) Checkin the scratch, private and cleaning (if appropriate) tapes in the library. For example :
checkin libv <libname> search=yes status=cleaner cleanings=xx volrange=xxxxxx,yyyyyyy....optional
checkin libv <libname> search=yes checklabel=barcode status=scratch
checkin libv <libname> search=yes checklabel=barcode status=private
(*) The tape device names may not be the same on the new machine. For more information on redefining tape devices on the new machine, refer to the following document for tape device naming convention :
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmcw.doc/anrwgd53112.htm
It is also possible to install the tsm device driver on the new machine, although it may not be needed for certain libraries. When installed, the TSM device driver comes with a tool named "tsmdlst.exe", which is located in the \program files\tivoli\tsm\console directory. Running the tsmdlst.exe tool provides a list of the tape device names which may then be used in the define path commands when redefining the library and drives to TSM.
No comments
Post a Comment