Geoff Allen writes:
 > "Frank M. Ramaekers Jr." <frankr AT IBM DOT NET> writes:
 >
 > > See Include/Exclude
 >
 > A lot of other folks have said the same thing. Thanks to all the
 > responses.
 >
 > We are using include/exclude. The problem is that even if you exclude
 > files using the include/exclude file, ADSM still traverses (and backs
 > up, if I recall correctly) the entire directory structure.

Exclude.Fs avoids this. Exclude.Dir also avoids it, but when testing it
I had problems excluding the top level directory of a file space.

 >                                                            In the case
 > of some of the filesystems we don't want to back up, we *really* don't
 > want to do that. (One example is our Usenet news spool. Millions of
 > files in thousands of directories, and it adds hours to the nightly
 > backups to "exclude /var/news/spool/.../*". Since we'll never care
 > about restoring *anything* in that filesystem, we have a DOMAIN that
 > excludes it. I was just thinking it would be nice if the DOMAIN could
 > exclude the things I don't want, rather than including the things I do
 > want. Like I said, it's not a big deal, I just fear that one day I'm
 > going to add a new filesystem to the news server and forget to add it
 > to the DOMAIN.....

I had that situation, while on version 2. On version 3, I'm now happy to
be able to let the DOMAIN statement default to ALL-LOCAL and exclude the
file systems I do not want to backup via Exclude.Fs.

But I agree: the specification of file spaces to be backed up should not
be split to two different places. The DOMAIN statement should allow to
specify, which file spaces should NOT be backed up.

Reinhard

--
Reinhard Mersch                     Westfaelische Wilhelms-Universitaet
Reinhard Mersch                     Westfaelische Wilhelms-Universitaet
Universitaetsrechenzentrum, Roentgenstrasse 13, 48149 Muenster, Germany
E-Mail: mersch AT uni-muenster DOT de                  Phone: +49(251)83-31583