Here's the deal...

The physical device tape0, as seen by the library manager, has the
devicename mt1.0.0.3. The same tape drive on the client, however, sees
the tape drive as devicename mt3.0.0.5. (We can tell this by the tape
drive serial numbers being reported.)

We've deleted all but one library manager-defined path from the library
client to the tape drive, and we've tried both mt definitions in the
library manager's path statements--the one from the library manager and
the one from the library client. In both cases, the manager changes
ownership of the library volume, mounts the volume in the drive, and
then the client waits and waits, and finally times out with the ANR8779E
error message.

We're stumped. The only thing that I can think is that the library
client is at 5.4.2 and the library server is at 5.4.1.

 
--
Mark Stapleton (mark.stapleton AT cdw DOT com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Fred Johanson
> Sent: Thursday, October 02, 2008 12:22 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Library manager/library conundrum
> 
> If you're SAN connected, Q SAN on the client supplies the device name
> for each path.
> 
> Fred Johanson
> TSM Administrator
> University of Chicago
> 
> 773-702-8464
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Remco Post
> Sent: Thursday, October 02, 2008 12:04 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Library manager/library conundrum
> 
> On Oct 2, 2008, at 18:33 , Mark Stapleton wrote:
> 
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf
> > Of Paul Zarnowski
> >> Double check your element numbers and paths to the drives.  Make
> sure
> > you
> >> have a path defined for each drive to each library-client server.
> >
> > There are no drive definitions for the "remote" library in the
> library
> > client, and therefore no element numbers or paths to check. There is
> a
> > path in the library manager that connects each of the tape drives to
> > the
> > library client, and as I mentioned there is obviously some
> > communication
> > going on.
> 
> > Here's another question that has been asked...
> >
> > When a library client sends migrated data from disk to a tape drive
> > managed by a library manager, does the data flow on fiber from the
> > client to the tape drive directly, or does it flow across the LAN
> from
> > the client to the manager, and then on fiber from the manager to the
> > tape drive?
> >
> 
> This may be a clue, the drive is accessed directly by the library
> client. All the library server does is verify the label. After that,
> the device is opened by the client. This is the reason the paths
> (defined on the library server) must be correct for the library
> client. So if a drive called drive4 is \\.\tape4 on the server and \\.
> \tape1 on the client, there must be a path, defined on the server,
> from your client to drive4 via device \\.\tape1
> 
> > --
> > Mark Stapleton (mark.stapleton AT cdw DOT com)
> > CDW Berbee
> > System engineer
> > 7145 Boone Avenue North, Suite 140
> > Brooklyn Park MN 55428-1511
> > 763-592-5963
> > www.berbee.com
> >
> 
> --
> Met vriendelijke groeten,
> 
> Remco Post
> remco AT pipsworld DOT nl