We've also experienced something similar.  In our case, the GUI backup
client works fine, the scheduler when started via the command line or by
the Startup folder also works fine.  The problem occurred only when the
scheduler started via the NT service.  To fix our problem, we went into the
NT services, double-click on the ADSM scheduler and click on the button to
run the service as the local System Account.  Previously, we chose the
Logon As and assigned it an ADMIN ID with all the necessary privilges that
we can think of and that did not work!!!!

   Cookie.





Paul Zarnowski <vkm AT CORNELLC.CIT.CORNELL DOT EDU> on 11/03/98 12:36:36 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Cookie Nguyen/US2/CORP/ARCO)
Subject:  Re: Problem backing up E drive in Schedule




At 02:32 PM 11/2/98 -0700, Kelly J. Lipp wrote:
>Hey gang,
>
>Weird one.  We've got three drives in this NT 4.0 system, c, d and e.
With a
> domain statement
>
>domain c: d: e:
>
>or
>
>domain all-local
>
>The scheduled job backs up C and D without problem, but then fails on E.

We have seen something close to this.  We have a Windows NT Workstation
client who has a C: and D: drive.  They can back up both drives manually
just fine.  However, the ADSM Scheduler completely ignores the D: drive.
No error messages, it just won't touch it.  The DOMAIN statement is set to
ALL-LOCAL.  C: and D: are both partitions on the same physical hard disk.
The C: drive is a FAT filesystem and the D: drive is an NTFS filesystem.
If anyone has seen this or has ideas, I'd love to hear about them.  We
haven't had a chance to call this one in yet.

..Paul