Re: TSM 4.1.4.0 and tape drive solution (was TSM 4.2.1)

We got similar behavior. For testing we used a small server and
installation went as you pointed - install v4.1.0.0, define everything and
play with it, later installed v4.1.4.0 maintenance and v4.1.4.1 patch. On
the production machine we've installed maintenance and patch before to
start the server for first time and migration simply does not fire at all
:-((
So for today and tomorrow we will start from the beginning - remove,
install, define, patch.
When this finishes I will play around what if I define some device after
patch. Will devices only defined before that work or new one will as well?

Zlatko Krastev
IT Consultant





Jack McKinney <jackmc-adsm AT LORENTZ DOT COM> on 22.10.2001 17:55:39
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        TSM 4.1.4.0 and tape drive solution (was TSM 4.2.1)

Big Brother tells me that Gill, Geoffrey L. wrote:
> To all,
>
> For all those who are thinking of upgrading to 4.2.1, my opinion is
don't. I
> have been up on it for 10 days and have already experienced 3 crashes. I
> also have a tape problem that I'm told was supposed to have been fixed. I
> have 2 PMR's open, both at level 2. I'm on AIX 4.3.3 and not sure if
other
> platforms have had similar problems.

    I have had problems which I posted here that I recently solved.  Since
they have to do with upgrades, I thought I'd post it on this thread.

    I have an AIX 4.3.3 box with a 4mm tape drive.  I installed TSM 4.1.0.0
and added the drive in TSM with:

DEFINE LIBRARY MANUALLIB LIBTYPE=MANUAL
DEFINE DEVCLASS 4MM2GCLASS DEVTYPE=GENERICTAPE LIBRARY=MANUALLIB
MOUNTRETENTION=9999 MOUNTWAIT=2880
DEFINE DRIVE MANUALLIB RMT0 DEVICE=/dev/rmt0

    This box was a test machine for testing out TSM procedures before using
them on the production machine.  After a while, I decided to reinstall the
machine from scratch, so I installed AIX 4.3.3 and TSM 4.1.0.0.  The first
time through, I didn't bother to upgrade to 4.1.4.0.  This time I decided
to.  After installing TSM, I applied the patches.  Before I reinstalled the
machine, I exported all of my nodes to 4MM2GCLASS tapes.
    I used the same three commands above to tell TSM about the tape drive,
but the third command gave an error:

ANR8420E DEFINE DRIVE: An I/O error occurred while accessing drive RMT0.
ANS8001I Return code 3.

    I posted to the list, and was told that I was doing this wrong.  I
needed
to rmdev rmt0, and then rediscover the tape drive as a TSM drive with
smitty,
and then use mt0 instead.  This made no sense, in that every other machine
that I have a tape drive on (including this machine before the reinstall)
worked with rmt0.
    I tried this, and the DEFINE DRIVE worked.  However, the IMPORT NODE
failed when I tried to reload the data.  It complained that there were
not enough mount points available.
    I played with this for a while, and eventually I had an epiphany.  I
reinstalled 4.3.3 and TSM 4.1.0.0, and then defined the drive in TSM with
the commands above, _before_ applying the patch.  It worked.  I then
applied the patch and IMPORTed the nodes with no problem.
    On my production server, I had recently added a tape drive, and the
server was at 4.1.2.0.  I had no problem adding the drive.  Some time
later, I upgraded to 4.1.4.0.  Had I done this in reverse, I probably
would never have gotten the tape drive working.  It would appears that
a bug crept in somewhere between 4.1.2.0 and 4.1.4.0 wherein DEFINE DRIVE
for a GENERICTAPE drive fails.  One has to define the drive before
upgrading...