ADSM-L

Re: [ADSM-L] Library error

2009-08-05 08:44:24
Subject: Re: [ADSM-L] Library error
From: Mario Behring <mariobehring AT YAHOO DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 5 Aug 2009 05:43:21 -0700
There are several errors on the OS indeed...

Did not match serial number "1110072935" provided by "IBM 3582 LTO Library 
(Changer0)" among the list of drives.

Did not match serial number "9111059298" provided by "IBM 3582 LTO Library 
(Changer0)" among the list of drives.

The device 'IBM ULT3580-TD2 SCSI Sequential Device' 
(SCSI\Sequential&Ven_IBM&Prod_ULT3580-TD2&Rev_73V1\7&75e84cd&0&030) disappeared 
from the system without first being prepared for removal.

The device 'IBM 3582 LTO Library' 
(SCSI\Changer&Ven_IBM&Prod_ULT3582-TL&Rev_310B\7&75e84cd&0&031) disappeared 
from the system without first being prepared for removal.

The device 'IBM ULT3580-TD2 SCSI Sequential Device' 
(SCSI\Sequential&Ven_IBM&Prod_ULT3580-TD2&Rev_73V1\7&75e84cd&0&020) disappeared 
from the system without first being prepared for removal

The device 'IBM ULT3580-TD2 SCSI Sequential Device' 
(SCSI\Sequential&Ven_IBM&Prod_ULT3580-TD2&Rev_73V1\7&380a70d7&0&010) 
disappeared from the system without first being prepared for removal.

...and so on...



I´ve just found out what happened and probably caused the problem...some 
Einsteins changed the Brocade switch where everything was connected to another 
one for some reason (same switch model)...TSM Server, Libraries (there are 2) 
and Storage...without the proper preparation and not involving TSM 
professionals....


Any way to fix this? I believe this is to be solved at OS level, but, maybe a 
dumb question but...is there any risk to loose the data on the tapes? TSM 
Database is intact...


Thanks

Mario





________________________________
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Sent: Wednesday, August 5, 2009 8:41:10 AM
Subject: Re: Library error

You didn't provide context on the error...  If this is s new library,
review that you have implemented the right driver.  If a prevailing
library, look back in the TSM Activity Log and Windows Event Log for
perspective on the start of the problem.  Check the library physical
status from its panels or web pages.  Use OS environment commands to
test the ability to use the library from that level.

   Richard Sims





<Prev in Thread] Current Thread [Next in Thread>