I'd also make sure there isn't another backup running with a different
opt file and verify if a cloptset is the culprit.
Another thing to check is q actlog for the last 48 hours and see how
many backups have run for this machine.

I have run into a few issues in the past that one person set up a backup
and another did as well. One scheduled at the TSM server and the other
was scheduled on the windows box.

My .02

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Tuesday, January 06, 2009 2:17 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Windows temp directory inadvertently excluded..sort of

Shawn -

As you say:  It's behaving as if there was a "exclude c:\temp\...\*"
somewhere.
That will cause a directory structure to be backed up, while omitting
its contained files.

Whereas a manual 'dsmc i' causes backup of the files, but the nightly
schedule excludes and expires them, it sure sounds to me like that
schedule has been running for some time, and is still using the local
exclude options that were in place when it was started back then, with
such an Exclude being part of them.  I would use the technique
summarized in "Scheduler process, see its options" in ADSM QuickFacts to
see what that scheduler process has stuck in its mind.  Or, just restart
the scheduler.

    Richard Sims