ADSM-L

Re: [ADSM-L] Library manager/library conundrum

2008-10-02 13:10:20
Subject: Re: [ADSM-L] Library manager/library conundrum
From: Remco Post <remco AT PIPSWORLD DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 2 Oct 2008 19:04:08 +0200
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

<Prev in Thread] Current Thread [Next in Thread>