Thems the breaks... this feature, as documented, specifically creates the
problem you have.  You've got to make the choice, of trade-offs, between the
old-reliable exclude (not .DIR) to define the tree of files you want
excluded, OR you've got to be more precise on the EXCLUDE.DIR --- which is
the choice I'd make to save ADSM time (to traverse directories, as in v2).
BTW, you should be using "DOMAIN ALL-LOCAL" (the default), which
automatically excludes network drives and cluster resources.

See the Version 3 Technical Guide for the following (and more details)...

If a directory structure is excluded through EXCLUDE.DIR, subdirectories in
the
excluded directory tree are not eligible for backup. Any INCLUDE statement
that
includes part of an excluded directory structure is ignored at backup time:

exclude.dir /home/dir1
include /home/dir1/subdir1

In the above example the include statement for the /home/dir1/subdir1
directory is
ignored when an incremental backup is performed because the subdirectory has
been excluded through an EXCLUDE.DIR statement.
exclude.dir /home/dir1
include /home/dir1/subdir1




When a directory structure is excluded from backup in Version 2, the
directory
objects of the excluded directory structure are backed up. Only the files in
an
excluded directory structure are excluded from backup. Directories excluded
through an EXCLUDE statement are nevertheless traversed by the ADSM
backup-archive client during an incremental backup. Processing large
directory
structures can be time and resource consuming and can cause timeout problems
on the clients.
The Version 3 backup-archive client supports excluding directory structures
from
backup.
2.2.2.1 New EXCLUDE.DIR Statements
A new include-exclude statement, EXCLUDE.DIR, is introduced in Version 3.
The
EXCLUDE.DIR statement excludes a directory structure from the internal
traverse tree that the ADSM backup-archive client builds internally before
performing the backup and prevents directories and directory attributes from
being backed up.
The exclude statement goes in the client user options file (dsm.opt) on
single-user clients like OS/2 and Windows NT, and in the include/exclude
file
referred to by the client system options file (dsm.sys) on multiuser
operating
systems like UNIX.
The new EXCLUDE.DIR statement coexists with the existing EXCLUDE
statement:
EXCLUDE.DIR Excludes a directory structure from backup and from being
traversed during incremental backup

> -----Original Message-----
> From: John Johnson [mailto:jjohns AT US.IBM DOT COM]
> Sent: Tuesday, January 18, 2000 8:01 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: NT client backup storing complete directory structureb
>
>
> I like the new exclude.dir option, it saves alot of
> processing time (up to
> 30 min).  I only wish it would not override the include
> statements, so our
> exclude.dir list could consist of one line not 20+.
>
> John Johnson
> IBM Global Services - WMI
> Enterprise Architecture Design
>
>
> <<  At a minimum, I basically have an Exclude.dir list that
> resembles the
> alphabet.  There
> has got to be a better way to implement this.  Something
> resembling the
> Include/Exclude
> statements for files ???  Why not have the include exclude
> statments for
> the
> files also
> determine the directories needed for backup ???  Or, drive
> letter with a
> wildcard
> (Exclude.dir C:\*)  or a keyword like,
> DONTEVENLOOKATNETWORKCONNECTIONS ???
> ...  something...
>
> Anyone else have this problem?  >>
>