Library unavailable after database recovery

rico

ADSM.ORG Member
Joined
Jun 8, 2005
Messages
12
Reaction score
0
Points
0
Website
Visit site
Hi,



It's me again. One step further in the disaster recovery procedure.



I recovered the TSM database on a server that uses different hardware than the original backup server. This means that I have to update the TSM database (drives and paths) to use the new device names.



My strategy was to simply delete the existing paths and drives and define new ones based on the disaster recovery device configuration file which I modified earlier to reflect the new device names.



Deleting elements worked fine, but defining new drives always results in:



ANR8444E DEFINE DRIVE: Library LIB.TAPE is currently unavailable.



I checked the library, it is online. I recognized that the library was still using the old library's serial number, so I deleted the library definition as well. I could even define a new library, but this time, the serial number stays empty.



Any ideas what I'm missing?



Thanks in advance,

Rico.



---



tsm: INTERNAL>DEFINE LIBRARY LIB.TAPE LIBTYPE=SCSI SERIAL=AUTODETECT

ANR8400I Library LIB.TAPE defined.



tsm: INTERNAL>q library f=d



Library Name: LIB.TAPE

Library Type: SCSI

ACS Id:

Private Category:

Scratch Category:

WORM Scratch Category:

External Manager:

RSM Media Type:

Shared: No

LanFree:

ObeyMountRetention:

Primary Library Manager:

WWN:

Serial Number:

AutoLabel:

Reset Drives: No

Last Update by (administrator): ADMIN

Last Update Date/Time: 11/06/2006 21:10:06





tsm: INTERNAL>DEFINE DRIVE LIB.TAPE DR.TAPE.480 ELEMENT=480 ONLINE=Yes

ANR8444E DEFINE DRIVE: Library LIB.TAPE is currently unavailable.

ANS8001I Return code 14.
 
Hi,



you have to define the devices and paths in this order



library -> library path -> drives -> drives paths



When defining a drive in SCSI library, TSM tries to communicate with the library .....



So again - try to define library paths before drives



Hope it helps



Harry
 
Thanks a lot, this did the trick.



The device configuration file has the commands listed in the order: define library, define drive, define paths, which misled me to the assumption that this is the correct order for the command line.



Anyway, thanks again.

-Rico
 
Back
Top