Here is a schedule I use. This is defined on a 5.1.5 TSM server on AIX O/S going to 5.1.5 W2k Client. I also have incorporated an exclude file to specify the exclusion of certain files. I wondered if the options portion of the schedule might help?
I just ran a test to a directory on the C: drive, I entered the schedule with the options=-subdir=yes" and objects="c:\testdir\*" - please note, the - on the sudir is important. The job ran perfectly, but I am running archive versus backup. Maybe there is some help info in the schedule definition below: Define schedule: nt_dom nt_weekly type=client description="W2K weekly backup C: and E: drives" action=archive options="-subdir=yes" objects="C:\* E:\*" startdate=today starttime=10:00 duration=1 durunits=Hours period=1 perunits=Days dayofweek=Sunday -----Original Message----- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 7:14 AM To: [EMAIL PROTECTED] Subject: Re: Windows 2000 scheduled backup problem >As directed from the ref guide, I changed my objects to '"C:\Research Folder\*"' > >Now the schedlog shows every file on the machine backing up, so I am back to >where I started. Are you certain that this is the only client schedule associated with the client...that there is no other server-defined schedule with a null Objects spec such that the Incremental Backup is following the dictates of your dsm.opt file (i.e., Domain specs, or absence thereof)? Do 'Query ASSOCiation' to verify what schedules are associated with the client. Do a full 'Query SCHedule Format=Detailed' to check for other schedules. The client's Backup log should indicate exactly what it was dispatched to do, so if you don't see "C:\Research Folder\*" reflected in it, something else is likely going on. Assure that there is no non-TSM time initiated backup execution occurring. Indirectly related: do 'dsmc query inclexcl' to verify that any client- or server-based Include-Exclude lists are as they should be. If you made any client options changes, assure that you restarted the client scheduler to absorb them. If necessary, post the output of 'Query SCHedule ... Format=Detailed' on the suspect client schedule, and the top 20 or so lines from the client log so that we may evaluate that data. Richard Sims, BU