This was indeed the problem.  The D: drive did not give SYSTEM access to the
drive, so we saw no errors, no comment on success or failure to  backup D:,
etc.  As soon as we added SYSTEM to the permissions for the drive,
everything worked fine.

Thanks everyone...

Paul

----- Original Message -----
From: "William Jean" <wjean AT GLASSHOUSE DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, June 29, 2005 10:58 AM
Subject: Re: [ADSM-L] 5.1.7 on NT skipping drives

Does the service run as the system account?  If so make sure that it has
access to the drive at the root.  If the service account running the TSM
scheduler service does not have access to the root of the drive it will
not be added to the domain list and you will not get any errors.

________________________________

From: ADSM: Dist Stor Manager on behalf of Paul Fielding
Sent: Wed 6/29/2005 12:52 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] 5.1.7 on NT skipping drives



Hi everyone,
After doing a few searches and not finding an answer to this I figured I'd
see if anyone else has encountered this.

Running Windows 5.1.7client (the last supported client for NT) on NT 4
(sp6 I think).

Two drives, C: and D:

During a scheduled incremental, the C: drive gets backed up, system
objects get backed up, but D: drive doesn't get touched.

No error messages, nuttin.  It's as if the drive isn't there.

There's no Domain line in the dsm.opt file, no excludes.

I can go into the GUI and see the drive, and manually backup the drive.

Same client on other similarly configured NT systems at same site seem to
work just fine.

any thoughts?

Paul

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________