Serial numbers on Win2003
-----Oorspronkelijk bericht-----
Van: Bill Boyer [mailto:bill.boyer AT VERIZON DOT NET]
Verzonden: donderdag 1 april 2004 17:08
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: Re: Library sharing
Serial numbers or the WWN of the device? Several responses showed you how to
get the serial number, but the WWN can be gotten with 'lsattr -El rmtx'
command.
Bill Boyer
DSS, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Zoltan Forray/AC/VCU
Sent: Thursday, April 01, 2004 8:58 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Library sharing
Thanks for all the help in this area. I think I finally got it working !
Now then, how do I get this (WWN) or similar information from a Windows
TSM server, since it too will be sharing the 3494ATL and/or LTO2 library ?
I can see the serial numbers on the 2K3 server. How can I get the
serial-numbers from AIX ?
Sorry to be so dense......I am not an AIX person......still learning !
Bill Boyer <bill.boyer AT VERIZON DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/31/2004 12:08 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Re: Library sharing
Then substitute storage agent client for library client. You define the
paths on the library manager server. The PATHS reference the library
client
servername, the library name (which I believe must be the same name) and
the
drive names as defined on the library manager server. You then use the
DEVICE= to point to the /dev/rmtx device on the library client server that
matches the same device on the library manager server. Let's say on the
TSM
library manager server:
Library: 3584
Drive: LTO1 /dev/rmt1
Drive: LTO2 /dev/rmt2
Your library client server name is LIBCLIENT (or whatever) and you have
the
following drives:
/dev/rmt3 Which is the same device as /dev/rmt1 on the library
manager
server
/dev/rmt4 Which is the same device as /dev/rmt2 on the library manager
server
If these are fibre, you'll have to get the WWN names (lsattr -El rmtx) on
both/all server and create a matrix that shows which is which on each
server.
Then on the library manager server:
define path libclient lto1 srctype=server desttype=drive library=3584
device=/dev/rmt3
define path libclient lto2 srctype=server desttype=drive library=3584
device=/dev/rmt4
Clear as mud, right?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Zoltan Forray/AC/VCU
Sent: Wednesday, March 31, 2004 11:27 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Library sharing
Well, in this case, it isn't, sortof.......
I don't have *ANY* path statements on the client, that refer to these
drives. All that is defined on the client is the SHARED LIBRARY. This is
another TSM server, not just a storage agent.
The path statements on the library manager are duplicated for the client,
pointing to the client as the SOURCE server....and yes, both sets of
definitions point to the same /dev/rmtx.
I am beginning to wonder if it has to do with the different levels of
ATAPE. The client is much newer (8.4.1.0) while the library manager is
8.3.x.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/31/2004
11:07:04 AM:
> When you define the PATHs on the TSM server for the storage agent on
> the client node, the device= is the name of the tape drive on the
> client, not on the server. You need to match the drive name on the
> TSM server to the correct device name on the client node, then use
> that in the DEFINE PATH. So on your TSM server:
>
> If library 3584 drive LTO1 points to the /dev/rmt1 device and on the
> storage agent client SA1 that same physical drive is the /dev/rmt3
> device you would use:
>
> define path SA1 LTO1 srctype=server desttype=drive library=3584
> device=/dev/rmt3
>
> Bill Boyer
> DSS, Inc.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Karel Bos
> Sent: Wednesday, March 31, 2004 10:54 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Library sharing
>
>
> Hi,
>
> Can be, but don't have to be the same... In the past I saw some machines
> with different device names for the same devices and it worked well with
> ITSM (on Windows).
>
> Regards,
>
> Karel
>
> -----Oorspronkelijk bericht-----
> Van: Amos Hagay [mailto:amos AT CCC.CO DOT IL]
> Verzonden: woensdag 31 maart 2004 17:46
> Aan: ADSM-L AT VM.MARIST DOT EDU
> Onderwerp: Re: Library sharing
>
>
> Hi,
>
> From my experience with 3584 Library, the rmt devices should be
> The same on both machines e.g. server_1 /dev/rmt1 /dev/rmt2 etc...
> And also on the library client /dev/rmt1 ...
>
> AH
>
> -----Original Message-----
> From: Zoltan Forray/AC/VCU [mailto:zforray AT VCU DOT EDU]
> Sent: Wednesday, March 31, 2004 5:46 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Library sharing
>
> Trying to get ATL library sharing working between two TSM AIX servers.
>
> I think I finally got the definitions correct......at least they seem to
> function.........
>
> However, I can't get the library client (capella) to use the drives.
Every
> time it does, I get these errors in the activity log:
>
> 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error
> number=46.
> (SESSION: 2663, PROCESS: 11)
>
> The "library manager" says the tape is mounted and ready.....
>
> 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive
> ATL-DRIVE2 (/dev/rmt1).
> 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership
> is changing from TSM-AGENA to TSM-CAPELLA.
>
> Any suggestions on what might be wrong ?
>
> AIX messages says the "-46" is "Drive Not Ready".
>
> These are FC / SAN attached 3590E1A drives.
|
