The usual cause of that is NT permissions. The scheduler (usually) runs under the system account; it requires access to the root of the D: drive.
It works when you do a manual backup because you are running under the current logon id, which has probably has different access rights from the system account. -----Original Message----- From: Joni Moyer [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 10:08 AM To: [EMAIL PROTECTED] Subject: Drive not backing up on NT client through scheduled backup Hello everyone! I have been trying to figure this one out, but there doesn't seem to be anything missed here. I have TSM server on the mainframe 5.1.6.2. The client is an NT client at 5.1.6.0. When the client does it's nightly backups it is continuing to skip over the D drive. We have looked at the include/exclude list in the options file and cannot find any parameter that would exclude the whole D drive. We started a manual backup from the backup/archive client and it successfully backed up the D drive, but it still will not do it when the TSM server schedules the incremental backup. All of the folders within this drive are shared, but I didn't think that would effect the outcome of a backup. Does anyone have any suggestions on what may be causing this drive to be missed during it's backup? Thank you! Joni Moyer Systems Programmer [EMAIL PROTECTED] (717)975-8338
