Poohmanchoo
Active Newcomer
I hope someone can help me with this because I have been banging my head against the desk for the past couple of hours and can't figure it out.
I was turning my old server back on and connecting everything to get backups back up and running, after a failed upgrade attempt to a new server, as I have done once in the past few weeks with no issues, and low and behold the library driver failed to load on startup. I used the wizard that popped up and it appeared to load the driver without issue.
I was attempting to perform some replication after restarting the old server and noticed that the drives were not loading tapes. I did the usual
q drive
q library
etc......and everything appeared to be fine, up, online, and defined. After further investigation I noticed that the TSM name was not as it was supposed to be lb2.1.0.2 vs lb1.1.0.2, mt2.0.0.2 vs mt1.0.0.2, mt3.0.0.2 vs mt2.0.0.2, etc...
mt2.0.0.2 2 0 0 2 F09E8ED000 500308C09E8ED001 LTO IBM ULT3580-TD4 A239
lb2.1.0.2 2 1 0 2 000001313693_LLA 500308C09E8ED001 LIBRARY IBM 3576-MTL 587G
mt3.0.0.2 3 0 0 2 F09E8ED090 500308C09E8ED091 LTO IBM ULT3580-TD4 A239
mt2.0.0.3 2 0 0 3 F09E8ED004 500308C09E8ED005 LTO IBM ULT3580-TD4 A239
At this point I figured I needed to delete and redefine the library and drives.
Simple process 1,2,3, right! Apparently not on my watch.
I am learning as I go, more or less, with this system but the following is what I did and the results are the reasons why I am writing this now.
First I deleted the library and drives. No Problem there.
I then attempted to redefine the library (first error)
tsm: LSTIVOLI>define path LSTIVOLI TS3310 srctype=server desttype=library device=lb1.1.0.2
ANR8418E DEFINE PATH: An I/O error occurred while accessing library TS3310.
ANS8001I Return code 15.
discovered work around for that while reading other forums
tsm: LSTIVOLI>define path LSTIVOLI TS3310 srctype=server desttype=library device=lb1.1.0.2 online=no
ANR1720I A path from LSTIVOLI to TS3310 has been defined.
tsm: LSTIVOLI>upd path LSTIVOLI TS3310 srctype=server desttype=library online=yes
ANR1722I A path from LSTIVOLI to TS3310 has been updated.
At this point I thought I was in the clear due to my results from Q path
tsm: LSTIVOLI>q path
Source Name Source Type Destination Destination On-Line
Name Type
----------- ----------- ----------- ----------- -------
LSTIVOLI SERVER TS3310 LIBRARY Yes
Success..........Then this happened at the next step
tsm: LSTIVOLI>define drive TS3310 LTO4-1
ANR8444E DEFINE DRIVE: Library TS3310 is currently unavailable.
ANS8001I Return code 14.
And now I have no idea where to go next. I have exhausted what little know-how I have and everything else (the documentation out there) make it out to be just 1,2,3, and you're done.
If anybody has any ideas, I am willing to give them a shot.
Details of server and Library are as follows;
Windows 2003 x64 Server
TSM 5.5.3
Total Storage 3576 modular tape library, with 2 extension units,
with 3 drives.
Updated driver for tape library to 6.2.1.7, even though it was showing the correct revision, after the issues started.
FYI. Everything worked a week ago without a single issue and multiple restarts for well over a year.
I was turning my old server back on and connecting everything to get backups back up and running, after a failed upgrade attempt to a new server, as I have done once in the past few weeks with no issues, and low and behold the library driver failed to load on startup. I used the wizard that popped up and it appeared to load the driver without issue.
I was attempting to perform some replication after restarting the old server and noticed that the drives were not loading tapes. I did the usual
q drive
q library
etc......and everything appeared to be fine, up, online, and defined. After further investigation I noticed that the TSM name was not as it was supposed to be lb2.1.0.2 vs lb1.1.0.2, mt2.0.0.2 vs mt1.0.0.2, mt3.0.0.2 vs mt2.0.0.2, etc...
mt2.0.0.2 2 0 0 2 F09E8ED000 500308C09E8ED001 LTO IBM ULT3580-TD4 A239
lb2.1.0.2 2 1 0 2 000001313693_LLA 500308C09E8ED001 LIBRARY IBM 3576-MTL 587G
mt3.0.0.2 3 0 0 2 F09E8ED090 500308C09E8ED091 LTO IBM ULT3580-TD4 A239
mt2.0.0.3 2 0 0 3 F09E8ED004 500308C09E8ED005 LTO IBM ULT3580-TD4 A239
At this point I figured I needed to delete and redefine the library and drives.
Simple process 1,2,3, right! Apparently not on my watch.
I am learning as I go, more or less, with this system but the following is what I did and the results are the reasons why I am writing this now.
First I deleted the library and drives. No Problem there.
I then attempted to redefine the library (first error)
tsm: LSTIVOLI>define path LSTIVOLI TS3310 srctype=server desttype=library device=lb1.1.0.2
ANR8418E DEFINE PATH: An I/O error occurred while accessing library TS3310.
ANS8001I Return code 15.
discovered work around for that while reading other forums
tsm: LSTIVOLI>define path LSTIVOLI TS3310 srctype=server desttype=library device=lb1.1.0.2 online=no
ANR1720I A path from LSTIVOLI to TS3310 has been defined.
tsm: LSTIVOLI>upd path LSTIVOLI TS3310 srctype=server desttype=library online=yes
ANR1722I A path from LSTIVOLI to TS3310 has been updated.
At this point I thought I was in the clear due to my results from Q path
tsm: LSTIVOLI>q path
Source Name Source Type Destination Destination On-Line
Name Type
----------- ----------- ----------- ----------- -------
LSTIVOLI SERVER TS3310 LIBRARY Yes
Success..........Then this happened at the next step
tsm: LSTIVOLI>define drive TS3310 LTO4-1
ANR8444E DEFINE DRIVE: Library TS3310 is currently unavailable.
ANS8001I Return code 14.
And now I have no idea where to go next. I have exhausted what little know-how I have and everything else (the documentation out there) make it out to be just 1,2,3, and you're done.
If anybody has any ideas, I am willing to give them a shot.
Details of server and Library are as follows;
Windows 2003 x64 Server
TSM 5.5.3
Total Storage 3576 modular tape library, with 2 extension units,
with 3 drives.
Updated driver for tape library to 6.2.1.7, even though it was showing the correct revision, after the issues started.
FYI. Everything worked a week ago without a single issue and multiple restarts for well over a year.