I've never tried stgpool volumes to a network drive.  But I have done DB
backups to a networked drive under NT, a while ago.
I remember there were permissions issues I had to deal with.  

First check to see if YOU can write something to that network drive - if
your id can do it, then it's probably just a permission thing.  By default,
everybody who mounts a network drive has READ access, but not WRITE access.

The ADSM Server is a service.  If you look at Start/settings/control
panel/Services, and select the ADSM service, click STARTUP. You will see
that the ADSM service is running under the SYSTEM id.  By default that ID
does not have permission to write on a network-attached drive.

You have to create an ID with permission to write on that drive.  Then
change the ADSM service to run under that account instead of SYSTEM so that
it will have permission to write on that drive.

That's a general description of what I did, it's been a long time and I
don't remember any more than that!  ANd this was just two WinNT machines on
the same wire; might be different still if you are in a NOvell network, I
don't know.  

But maybe that will give you a starting point.

************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************





> -----Original Message-----
> From: Andreas Huber [SMTP:ahub AT CSCSERVODATA DOT COM]
> Sent: Friday, January 14, 2000 7:19 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Storage pool volumes on a network drive?
> 
> Hi,
> 
> I'm in the process of setting up an ADSM server 3.1.2.50 for backup
> purposes on NT4. I tried to setup storage pools (DISK) and volumes
> (FILE) on a network drive (don't ask) with no success. ADSM doesn't seem
> to understand UNC pathnames like "\\server\\share\adsmdata\disk.001". If
> I'm using a network drive instead as in "v:\adsmdata\disk.001" I'm
> getting an error message saying that the volume cannot be mounted (w/ an
> error code of 108 meaning "ERROR_DRIVE_LOCKED").
> 
> Is this something that is supposed to work?
> 
> TIA,
> Andreas
> 
> -- 
> Andreas Huber - mailto:ahub AT cscservodata DOT com
> CSC SERVODATA GmbH - http://www.cscservodata.com
> A-1020 Wien, Nordbahnstraße 36 / Stiege 2 / 5. Stock
> Tel: +43 / 1 / 216 65 65-373 Fax: DW 13