_
From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] On Behalf Of Shawn Drew
[shawn.d...@americas.bnpparibas.com]
Sent: Thursday, January 19, 2012 10:53
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Drive and Path Definition
The only other option to restarting the library ma
Shawn Drew
Internet
rrho...@firstenergycorp.com
Sent by: ADSM-L@VM.MARIST.EDU
01/19/2012 09:57 AM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
Re: [ADSM-L] Drive and Path Definition
"ADSM: Dist Stor Manager" wrot
"ADSM: Dist Stor Manager" wrote on 01/19/2012
08:42:26 AM:
> > ...
> > Our libraries are 3584 scsi libraries, which are different animals
from
> > 3494 libraries. Sorry, I should have said that.
> >
> > Any time we have changed the physical library it has required us to
bounce
> > TSM so the new
would suspect).
See Ya'
Howard Coles Jr.
John 3:16!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Allen
S. Rout
Sent: Thursday, January 19, 2012 8:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Re: Drive and Path Definition
On 01/19/2012 01:37 AM, Roger Deschner wrote:
Pay attention to the fact that typically rmtN, mtN, and TSM driveN
device numbers will be different. Make sure the serial numbers in TSM Q
DRIVE F=D are correct.
... This, a whole bunch.I'll drop a few scripts here I use to
automate the proces
On 01/18/2012 06:28 PM, David Bronder wrote:
Richard Rhodes wrote:
In the past we've never had to restart TSM to add a new drive. As
long as the drive was discovered and available at the AIX layer, we
could define the new drive. Has this changed with v6.2.x?
Seriously? Is this behavior du
On Jan 19, 2012, at 8:19 AM, Richard Rhodes wrote:
> ...
> Our libraries are 3584 scsi libraries, which are different animals from
> 3494 libraries. Sorry, I should have said that.
>
> Any time we have changed the physical library it has required us to bounce
> TSM so the new slots EA and/or dri
"ADSM: Dist Stor Manager" wrote on 01/18/2012
06:28:41 PM:
> > > In the past we've never had to restart TSM to add a new drive. As
> > > long as the drive was discovered and available at the AIX layer, we
> > > could define the new drive. Has this changed with v6.2.x?
> >
> > It's my experience
rs, depending on the
context and the situation.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger
Deschner
Sent: Thursday, January 19, 2012 1:38 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Drive and Path Definition
I used to believe
I used to believe in all sorts of hokus-pokus in this regard, but I have
found that if you do things in an organized way in the correct order,
everything just works, without restarting dsmserv, on both TSM 5.5 and
6.2. See the TSM for AIX Administrator's Guide.
I recently moved a library from a si
Richard Rhodes wrote:
>
> > In the past we've never had to restart TSM to add a new drive. As
> > long as the drive was discovered and available at the AIX layer, we
> > could define the new drive. Has this changed with v6.2.x?
>
> It's my experience that any change to the library (adding slots o
>
> In the past we've never had to restart TSM to add a new drive. As
> long as the drive was discovered and available at the AIX layer, we
> could define the new drive. Has this changed with v6.2.x?
It's my experience that any change to the library (adding slots or drives)
requires cycling TSM
recognized newly
defined devices.
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Tailor, Mahesh C.
Sent: Wednesday, January 18, 2012 9:41 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Drive and Path Definition
Hello.
I have a PMR on this, but
Dist Stor Manager [ADSM-L@VM.MARIST.EDU] On Behalf Of Shawn Drew
[shawn.d...@americas.bnpparibas.com]
Sent: Wednesday, January 18, 2012 10:43
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Drive and Path Definition
You did the itdt against rmt0, but you are defining the path to rmt11. I'm
ass
inic.org
Sent by: ADSM-L@VM.MARIST.EDU
01/18/2012 09:41 AM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
[ADSM-L] Drive and Path Definition
Hello.
I have a PMR on this, but not making much progress on it so thought I
would send this out on the User List to see if anyone else encoun
Hello.
I have a PMR on this, but not making much progress on it so thought I would
send this out on the User List to see if anyone else encountered this issue and
can suggest a fix.
Here's what I have:
TSM 6.2.3.100
AIX 7.1 (oslevel: 7100-00-04-1140)
IBM FC 5729 8-Gbps FC adapters
SAN Switch:
ECTED] cc:
Sent by: "ADSM: Subject: Path definition
Dist Stor
On Wednesday 01 October 2003 22:49, Sylvia Nergard wrote:
> My environment is TSM 5.2 on Windows 2000, tapelibrary is 3583 lto on the
> SAN.
>
> II wonder.when defining path for tapelibrary and drives, should the
> device parameter be \\.\Tape0 and Changer0 (which is how Windows sees the
> devi
h defs for you.
-Original Message-
From: Sylvia Nergard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 4:49 PM
To: [EMAIL PROTECTED]
Subject: Path definition
Hi folks!
My environment is TSM 5.2 on Windows 2000, tapelibrary is 3583 lto on the
SAN.
II wonder.when defining path f
[EMAIL PROTECTED]
cc:
Subject:Path definition
Hi folks!
My environment is TSM 5.2 on Windows 2000, tapelibrary is 3583 lto on the
SAN.
II wonder.when defining path for tapelibrary and drives, should the
device parameter be \\.\Tape0 and Changer0 (which is how Windows sees t
Hi folks!
My environment is TSM 5.2 on Windows 2000, tapelibrary is 3583 lto on the
SAN.
II wonder.when defining path for tapelibrary and drives, should the
device parameter be \\.\Tape0 and Changer0 (which is how Windows sees the
devices?)etc, or mt0.0.0.1 an lb1.0.0.1(which is how TSM sees
21 matches
Mail list logo
