Along with the permission issues discussed already, if you're on an older
client (3.1) there was a bug where if the drive didn't have a label, it was
skipped. The later 3.1 clients (3.1.0.5, I think) had this fixed.
Nick Cassimatis
[EMAIL PROTECTED]
>I have an NT client that is not backup up the D drive.
>From my notes at http://people.bu.edu/rbs/ADSM.QuickFacts :
D: drive not backed up
This normally is a permissions problem. Check the scheduler service via
control panel / services. See what account the service logs in
PROTECTED]
Subject: Not backing up drive
I have an NT client that is not backup up the D drive. We can manually do
the incremental but it will not do it when we start the scheduler. When
the client looks in the dsmsched.log it shows it backing up the C drive and
then skipping to the F drive. We
PROTECTED]
Subject: Not backing up drive
I have an NT client that is not backup up the D drive. We can manually do
the incremental but it will not do it when we start the scheduler. When
the client looks in the dsmsched.log it shows it backing up the C drive and
then skipping to the F drive. We
Jeff Rankin
[EMAIL PROTECTED]
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: May 22, 2001 4:51 PM
> To: [EMAIL PROTECTED]
> Subject: Not backing up drive
>
>
> I have an NT client that is not backup up the D drive. We
> can manu
ankin
[EMAIL PROTECTED]
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: May 22, 2001 4:51 PM
> To: [EMAIL PROTECTED]
> Subject: Not backing up drive
>
>
> I have an NT client that is not backup up the D drive. We
> can manually do
&
I have an NT client that is not backup up the D drive. We can manually do
the incremental but it will not do it when we start the scheduler. When
the client looks in the dsmsched.log it shows it backing up the C drive and
then skipping to the F drive. We have tried an INCLUDE...no luck. Any
i
