We backup many logical drives without problems, as long as we have them
labeled, so you probably need to look at NT access rights. Did you see
the post from Michael Bartl

"The user you created has to be in the group "backup operators". Given
the user has this access right, ADSM can backup any drive (with
volumelabel...) without having any rights on the directory structure.
Additionally ADSM needs to get access to the root entry of the drive."

Also from Michael, but I'm not sure it pertains to NT is the following:

"Make sure, you put at least an entry "ADSMTEST (CI)R" (browse dir) into
the acl of only the root entry (not for the whole structure)."

When we first setup ADSM, we backed up one server with a RAID array
divided into 24 logical drives, c: through Z:, and on our first backup,
two drives were not seen by ADSM, Neither myself or our network
administrator remember exactly what we did, but it had to with NT
security on the root, which fits in with Michaels note. If you are
backing up any othr logical drives, you might compare the security
settings on those with the two that are currently causing you grief.
Sorry I can't be more specific.


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: have labels, but they are logical partitions on one physical disk.
>
> 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