Moving TSM to another server

[DominicLapalme]

I want to move my whole TSM server from one server to another.

First, here is a preview of my hardware.

Server 1 (the one with TSM working on it)
IBM X-Series 330 1 CPU
512 Mb RAM
Windows 2000 Advanced Server
2x18.2 Gb U160 SCSI Drives Mirrored (I know it's not a lot, that's why I want to move it)
Adaptec 2940 SCSI Card

Server 2 (my target)
IBM X-Series 335 2 CPU
Windows 2000 Server
1024 Mb Ram
2x72.4 Gb U320 SCSI Drives Mirrored (I already have these, so it's better to use it)
Adaptec 29320 SCSI Card (this server only has 2 PCI-X slots and the 2940 is a PCI card)

Backup Library
IBM ULT-3583
1 Drive LTO1
18 tapes

On the first server, TSM detects the loader as ID lb6.0.0.2 and the drive as ID mt0.0.0.2. But when I connect the library to the second server, TSM detects them as lb6.0.0.3 and mt0.0.0.3. So if I try to move my whole database, TSM can't talk to the library. Also, if I try to label the tapes, it doesn't find any. Is it possible that the tapes have been tagged to the first TSM server?

Here's what's left for me to do at this point :
- Use the 29320 in the other PCI-X slot
- Install the 29320 in the first server and rescan the library
- Clone the first server's drives and plug them in the second one


If anyone ever done this with a Windows server, your help would be most appreciated.

Thanks

 

[andyman1070]

My experience tells me that you need to completely blow away the devcfg files in order for the target server to communicate to the library in a windows environment. This means you need to recreate definitions for the library, drives, and paths.

You can do this quickly by keeping a copy of the devffg in a WordPad file, then issuing the correct DELETE or DEFINE in front of the sequentially copy/pasted line.

Alternately, I believe TSM has a migrate command sequence as well. You would need to contact Tivoli support fot those steps.