Re: V5.1 3494 manual library gotcha

[Scott Behrens]

Steve,
I sure don't have Tom's TSM expertise, so 'grain of salt' this -- but my TSM admin 
had to do a db restore on a 3494 (due to an auditdb gone bad) at version 5.1.x.x.  He 
did have to define the 3494 as a manual library to access the db tape.   I'm thinking 
your desttype='library' is the problem.  In our devconfig, it was 'drive'.  Here is 
the devconfig file he used:

/* Device Configuration */
DEFINE DEVCLASS 3590CLASS DEVTYPE=3590 FORMAT=DRIVE MOUNTLIMIT=DRIVES MOUNTWAIT=60 
MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=3494LIB
SET SERVERNAME BLAHBLAH01
DEFINE LIBRARY 3494LIB LIBTYPE=manual
DEFINE DRIVE 3494LIB DRIVE1
DEFINE PATH BLAHBLAH01 DRIVE1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=3494LIB 
DEVICE=/dev/rmt1 ONLINE=yes

Scott Behrens

 [EMAIL PROTECTED] 12/2/02 9:09:56 AM 
Steve --

Manual libraries are just that - Manual - and do not have a path to the
library.

You need to use the local library management system (I'm not familiar with
3494 as such) to mount tapes by hand for the restore.

Tom Kauffman
NIBCO, Inc

 -Original Message-
 From: Steve Harris [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 28, 2002 1:54 AM
 To: [EMAIL PROTECTED]
 Subject: V5.1 3494 manual library gotcha


 Hi All,

 I'm trying to move datacentres by restoring a 4.2.2 database
 to 5.1.5.3 at the new site - anyone tried an upgrade at the
 same time as a restore? - I'd like to hear your war stories.

 Anyway, I've defined my server and I'm running scripts
 modified from the DRM plan scripts. When I come to do the
 restore, obviously the devconfig file has to have the new
 V5.1 path statements in it.  The restore fails but I see that
 I'm using a 3494 and there's an old bug about having to
 define a manual library for  restoring a 3494.
 So, I go to my test instance and try to define a manual
 library so I can see what the devconfig file looks like, and
 here's the gotcha.

 I can define the manual library, and the drive in the
 library, and the path to the drive, but when I try to define
 the path to the library I get

 tsm: TSMDCTdefine path tsmdct fred srctype=server
 destt=library device=/dev/rmt1
 define path tsmdct fred srctype=server destt=library device=/dev/rmt1
 ANR8416E DEFINE PATH: The DEVICE parameter is invalid for
 library type MANUAL.
 ANS8001I Return code 15.

 tsm: TSMDCTDEFINE PATH TSMDCT FRED SRCTYPE=SERVER
 DESTTYPE=LIBRARY ONLINE=YES
 DEFINE PATH TSMDCT FRED SRCTYPE=SERVER DESTTYPE=LIBRARY ONLINE=YES
 ANR2022E DEFINE PATH: One or more parameters are missing.
 ANS8001I Return code 3.

 Have I missed something  here or found a bug?

 Regards

 Steve Harris
 Unix, Backup and Storage Admin
 Queensland Health, Brisbane Australia

WinNT Client Upgrade - Overwrite or Uninstall/Reinstall

[Scott Behrens]

Please excuse if this is obvious - several archive searches turned up
nothing, and I didn't see a reference in Richard Sims' Quick Facts.

Relevant Installation Info:
  TSM Server 4.1.1.0 on AIX 4.3.3
   WinNT Clients:  TSM Client 4.1.1.0  on Intel NT 4.0 SP5 or SP6

Goal:  Upgrade of WinNT TSM Clients from 4.1.1.0 to 4.1.2.12
  to handle DST problem before April 1 (avoiding 4.1.1.16  because
  of potential memory-leak problem (IC28969))

If I install the 4.1.2.12 client over the top of the existing 4.1.1.0 client,
then I end up with two 'Tivoli Storage Manager Client' entries in the
'Control Panel--Add/Remove Programs' (and duplicate entries for the
two installed products in the Registry as might be expected).

The 'Installing the Clients' manual, Version 4.1, Chapter 4. has a
section, 'Reinstalling the Client' , which implies that if you are installing
to the same location, you can just install over the top of the previous
version with no uninstall required.  I want to provide our NT sysadmins
a straight-forward procedure for doing this upgrade, and don't know
whether to suggest an uninstall-reinstall (ensuring that they have
a backup of the dsm.opt and dsmsched.log), or just have them
do an install over the top of the existing client (and put the footnote
about the duplicate registry entries in the 'Book of Who Cares'.)
Any thoughts on best practices?  Thanks,  Scott Behrens