I'm not an NT person myself, but we recently had a big go 'round here with
this same kind of problem and it basically all came down to NT permissions.

This the concluding revelations of the NT administrator here that finally got
the problem solved.  Doesn't make a whole lot of sense to me, but maybe it
will to you.

 "I know you were wondering about the solution to our ADSM problem.
 Basically we were able to determine the account to grant file system
 permissions to.  The account is the local administrators account.  Once
 we gave this accout permissions to the drives to be backed up, it worked.

 As I said before, we can't run the service under any user account.  We have
 tried several different ones.  I thought this was interesting in your
message.  It
 could be why it doesn't work.


  As I mentioned in my previous note, there is a known problem with being
  able to access system acl security descriptors (auditing information) when
  running as a service."

You might also want to look through the archives of the listserv, because
there was a lot of good information and suggestions sent here when we were
trying to figure out the problem.  Good luck and don't give up.  It IS a
solvable problem.




ADSM-L AT VM.MARIST DOT EDU on 11/14/97 01:36:35 PM
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: ADSM Problems

        I am trying to backup a NT server with ADSM.  The problem I am
having is that I can't backup the F: drive.  This drive is a RAID disk
drive.  The lettering sequence is a little different also, we have
drives C:, D:, then D: is mirrored where E: would be, then we have the
F: drive.  We run the scheduling service as a system account and it
backs up the C and D drives fine, however, it says that F is an invalid
drive specification.  All of the drives are labeled in the same manor:
Servername-driveletter.  If we run the Scheduler service under the
administrators ID, which is God to the machine, it sees the F: drive and
tries to back it up, however, we get access denied errors.  Not only do
we get this error on F: when we do this, but we get the same errors on
C: and D: which work fine the other way.  If we run a manual backup
through the backup client we can back it up fine also.

Thanks,
Rick Smith
Maritz, Inc.
Storage & Security Administration
smithrr AT maritz DOT com
(314) 827-1584