You might check the user ID used to log onto the ADSM server to make
sure that volume labels are visible to ADSM. ADSM on NT uses volume
labels to define filespaces. We are an NT environment, and whenever our
scheduled backups failed to back up a drive, it was either due to lack
of a volume label, or the need for the logon used at the server to have
the  NT permissions changed.

Moir,Elizabeth wrote:
>
> To: OAS     --LMS1
>
> FROM: Betsy Moir (TTCEDM) Ext 85020
>       VM Tech Services
>       email:  betsy.moir AT abbott DOT com
> Subject: Re: NT Service and Logical Drives
>
> F: and G: do have volume labels, but certain user id's can't see the labels.
> They can see the drives, but not the labels.
>
> Betsy
> *** Forwarding note from OWNERAD1--INTERNET 97/10/21 13:32 ***
>
> TO:         NOREPLY  INTERNET  ADSM-L AT VM.MARIST DOT EDU
> FROM:       OWNERAD1 INTERNET  owner-adsm-l AT VM.MARIST DOT EDU
> DATE:       10/21/97 13:32
> SUBJECT:    Re: NT Service and Logical Drives
> Do drives F: and G: have volume labels?
>
> Moir,Elizabeth wrote:
> >
> > To: OAS     --LMS1
> >
> > FROM: Betsy Moir (TTCEDM) Ext 85020
> >       VM Tech Services
> >       email:  betsy.moir AT abbott DOT com
> > Subject: NT Service and Logical Drives
> >
> > I have a client with a problem that my lack of NT server experience can't
> > help them with.
> >
> > They installed ADSM on their NT server as userid ADSMTEST.  ADSMTEST was a
> > member of the administrator group and the Backup group.  The options file
> > contains the command DOMAIN D: F: G:  When the scheduler runs it recognizes
> > drive D: and backs it up, but returns the error ANS4147E Drive F: is an
> > invalid drive specification.  The same for G:
> >
> > The questions are:
> >
> > 1.  How do we get the ADSM scheduled service to recognize these logical
> >     drives?
> >
> > 2.  When the product is installed under a user account, does it retain the
> > rights of that account even if the account isn't logged on to the server at
> > the time of scheduler runs?
> >
> > 3.  Is it possible to get ADSM to recognize the F: and G: drives without
> > having to grant ADSMTEST access at the directory level.
> >
> > If anyone has any experience with this or can help out with a solution it
> > would be greatly appreciated.  Thanks.
> >
> > Betsy