>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 - Here are my notes, from http://people.bu.edu/rbs/ADSM.QuickFacts
       which may cover your issue.
Remember also to look beyond your options file Incl/Excl: always consider
that there may be server-side Cloptset values, so do 'dsmc q inclexcl'.

    D: drive not backed up
        The simplest cause would be that the backup was attempted via the
        scheduler and it was not restarted after a change to either the drives
        complement or client options file, to know to back up that drive.
        Do 'dsmc query inclexcl' to see if the drive is being inadvertently
        excluded from Backup.
        This normally is a permissions problem.  Check the scheduler service via
        control panel / services.  See what account the service logs in as.  If
        it is the SYSTEM account, make sure that the drive has permissions for
        the SYSTEM account.  A lot of NT Administrators remove EVERYONE from the
        permissions, which also prevents the SYSTEM account from being able to
        do backups.  Note that running the backup manually causes it to run
        under your own account, so that may succeed whereas the scheduled backup
        may fail.
        Another reason could be that disks involved are part of the Microsoft
        clustering environment. Have you included CLUSTERnode Yes in the
        cluster.opt file for each logical node on the cluster?
        And, the volume should really have a label.
        See also: Backup skips some PC disks

 Richard Sims, BU