If you are upgrading library manager and clients you should be careful. The
upgrade process will define paths on all your servers, and it all looks and
works ok. Until you want to define a new drive (or delete/redefine a drive)
on a library client. Then you will discover that the 4.2 Admin Guide is
wrong (5.1 is correct). All drive and path definitions now need to be done
on the library manager. Only a library definition is done on the clients. If
you don't use library managers and clients the upgrade process should define
your paths and you should be OK. (My experience on AIX)
Paul.
-----Original Message-----
From: David Nicholson [mailto:David_R_Nicholson AT WHIRLPOOL DOT COM]
Sent: 11 September 2003 19:17
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 4.2.2.12 to 5.1.0.0 upgrade and PATHS
My recollection is that we simply had to define the paths. However, SOP
says be prepared for anything. I also recall that we were told to remove
the DRIVE def's from all TSM library clients. The DRIVE's only need to be
defined to the library manager/owner in a library sharing environment now.
The devices still need to be defined to the OS on the library client, but
TSM does not require the DRIVE to be defined to library clients. I am not
sure that it is required to delete the DRIVE def's from clients, but was
recommended.....
Dave Nicholson
Whirlpool Corporation
Farren Minns <fminns AT WILEY.CO DOT UK>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/11/2003 11:34 AM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: 4.2.2.12 to 5.1.0.0 upgrade and PATHS
I'm assuming that the Library and Device definitions will still be in
place, so then it'll just be the paths that need defining. Or do I need to
define new drives and lib too ?
Farren
|+--------------------------------+---------------------------------------|
|| Lawrence Clark | |
|| <Larry_Clark AT THRUWAY.STATE DOT NY| |
|| .US> | To: ADSM-L AT VM.MARIST DOT EDU |
|| Sent by: "ADSM: Dist Stor | cc: |
|| Manager" | Subject: Re:
4.2.2.12|
|| <ADSM-L AT VM.MARIST DOT EDU> | to 5.1.0.0 upgrade and PATHS |
|| | |
|| 09/11/2003 04:07 PM | |
|| Please respond to "ADSM: Dist| |
|| Stor Manager" | |
|| | |
|+--------------------------------+---------------------------------------|
On the other hand, we upgraded from 4.2 to 5.1, have two 3494 libraries,
and did not have to manually define the paths..............
>>> David_R_Nicholson AT WHIRLPOOL DOT COM 09/11/03 10:22AM >>>
We made the same upgrade 4.2 to 5.1 on our AIX server. We also have
3494
library. We deffinetly had to manually define the paths after the
upgrade.
Dave Nicholson
Whirlpool Corporation
Farren Minns <fminns AT WILEY.CO DOT UK>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/11/2003 07:53 AM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: 4.2.2.12 to 5.1.0.0 upgrade and PATHS
Hi TSMers
Ok, my questions about the 4.2 to 5.1 upgrade are prolly getting
boring,
but I always like to make sure I've asked every silly question I can so
as
not to get caught out.
So, next week I'm going from 4.2.2.12 to 5.1.6.2 on a Solaris 2.7
node.
I understand that PATHS are a new feature (or complication) of 5.1 but
want
to know if, after upgrade I HAVE to define these. I was speaking to an
IBM
rep the other day and he said yes, but I have heard others say they
didn't
have to do it (sorry to keep hastling you Gary). Our setup is one tcp
attached 3494 library with two scsi 3590 tape drives. I'm surprised
that
the upgrade would not see these devices already set up and create the
paths
accordingly.
Anyone got a definte answer here. Also, looking at the quick-start
guide
on
the 5.1.0.0 media, it doesn't mention paths. The Admin guide does, but
not
the quick start.
mm
Anyway, thanks for any pointers
Farren Minns - John Wiley & Sons Ltd
****************************************************************************
*
This email transmission is confidential and intended for the person or
organisation it is addressed to. If you are not the intended
recipient,
you
must not copy, distribute, or disseminate the information, open any
attachment, or take any action in reliance of it. If you have received
this
message in error please notify the sender.
Any views expressed in this message are those of the individual
sender,
except where the sender specifically states otherwise.
Although this email has been scanned for viruses you should rely on
your
own virus check, as the sender takes no responsibility for any damage
arising out of any bug or virus infection.
****************************************************************************
*
****************************************************************************
*
This email transmission is confidential and intended for the person or
organisation it is addressed to. If you are not the intended recipient,
you
must not copy, distribute, or disseminate the information, open any
attachment, or take any action in reliance of it. If you have received
this
message in error please notify the sender.
Any views expressed in this message are those of the individual sender,
except where the sender specifically states otherwise.
Although this email has been scanned for viruses you should rely on your
own virus check, as the sender takes no responsibility for any damage
arising out of any bug or virus infection.
****************************************************************************
*
Any e-mail message from the European Central Bank (ECB) is sent in good faith
but shall neither be binding nor construed as constituting a commitment by the
ECB except where provided for in a written agreement.
This e-mail is intended only for the use of the recipient(s) named above. Any
unauthorised disclosure, use or dissemination, either in whole or in part, is
prohibited.
If you have received this e-mail in error, please notify the sender immediately
via e-mail and delete this e-mail from your system.
|
