Karin,

Not sure if you got if figured out already, but I just went though the
same exact thing, find my posts from before: "tsm tape path ...".

Because I had already blown away all the "old" tape paths, my final
solution was to create new devices/paths. But if your old paths are still
there try something like this:

UPDATE PATH TSM_SERVER1 LBx.0.0.x SRCTYPE=SERVER DESTTYPE=LIBRARY
DEVICE=lbx.0.0.x ONLINE=YES

UPDATE PATH TSM_SERVER1 MT1.0.0.3 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=LB6.0.0.3 DEVICE=mt1.0.0.5 ONLINE=YES

etc. for each drive you have

If you've already blown away the "old" tape paths, then you need to blow
away all the "old" devices, then recreate new devices (library + drives),
make sure your server points to the new library, then recreate the paths
for those new devices. THEN, you must checkin all the tapes from the
databse into the "new" library. Checkin scrtach tapes first:

checkin libvol lb6.0.0.5 status=scratch search=yes, checkin libvol
lb6.0.0.5 status=private search=yes.

Then do a similar checkin for private volumes.

My understanding now is that I NEVER reboot the host without the
library/drives attached. Doing so always makes windows/TSM think that the
old devices are gone, and thus I have to update paths again.

Hope this helps,

Alex


On Tue, 12 Jul 2005, Karin Dambacher wrote:

Hi all,

we have a 3570 Magstar and TSM 5.2.3.4 on Windows 2000. After changing the
drives (physically) at the magstar, the library could not be initialized
anymore. Error is
ANR8840E Unable to open device lb8.1.0.2 with error
                         2818368.
ANR8441E Initialization failed for SCSI library LB8.1.0.2.

We have taken the newest drivers IBMMagxxx from ftp.boulder.ibm.com, in
Windows everything ok, with tsmdlst we get the addresses we have in the
pathes.
Before changing the drives everthing was ok.

Can anyone help? Do we have to delete TSM definitions (library) and
redefine it?

Thanks a lot, Karin
please immediately delete its contents and notify us. This e-mail was
checked for virus contamination
before being sent. Nevertheless, it is advisable to check for any
contamination occurring during transmission.
We cannot accept any liability for virus contamination.