That doesn't sound right to me. EXCLUDE.DIR should affect backup only.

What client level are you running? There is an older APAR, IC31329, that
describes your symptoms, but that was fixed somewhere in 4.2.2 and up.

Verify that you are using a current client level, then see if the problem
occurs again.

Re: using EXCLUDE instead of EXCLUDE.DIR:

Of the three EXCLUDE examples you tried, the second one (exclude
/bkp/.../*) is correct. It excludes files (but not dir entries) in /bkp
and its subdirectories; the directory structure is still backed up.
Assuming you don't care to have the dir entries backed up, this behavior
can range from "acceptable, not a problem" to "annoying" to "problematic",
with the latter being the case where the directory structure is so
large/deep, that the backup operation takes too long to complete. That is
where EXCLUDE.DIR comes into play, as it prevents traversal of the named
directory altogether during backup operations.

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2006-05-05
07:35:10:

> Good day all,
>
> I used an exclude.dir command in an effort to exclude a directory from
> my backups.  While I was successful in exluding the directory from my
> backup, the command also affected archive processing.
>
> The following command was run inside a larger script -
>
> dsmc archive -archmc=$ADSMMC -subdir=yes -desc="$ADSMDESC" -verbose
> "$BKPDIR/*"
>
> This command resulted in the following message -
>
> ANS1115W File '/bkp/vol18/*' excluded by Include/Exclude list
>
> I looked through some TSM manuals and I see different references to what
> exclude.dir will actually exclude.  It some places the terminology "all
> processing" is used and in others only "backup processing" is
> referenced.
>
> The reason I tried to use exclude.dir was because previous attempts to
> exclude this data from backup processing using the below, had failed.
>
> exclude /bkp/*
> exclude /bkp/.../*
> exclude /bkp/.../.../*
>
> Anyone have experience with using exclude.dir?  The exact command I had
> placed in my include-exclude statement was
>
> exclude.dir /bkp
>
> Once I removed the "exclude.dir /bkp" command, the archive jobs were
> re-run successfully.    The TSM server in question is running AIX 5.3 ML
> and TSM 5.2.7.
>
> Thanks
>
> Scott