> FreeBSD, however, has 'nodump' flag support (being a 4.4BSD derivative),
> and as of 4.3-RELEASE, nodump on a directory is now recursive on the
> subtree (although there is a performance penalty). AMANDA was built from
> the ports, which by default adds the honor-nodump option.
>
> So I am thinking that I might be able to get away with marking the
> hold directory with the 'nodump' flag so that dump will skip it and then
> taking away the 'no-hold' directive from the disklist entry. Has anyone
> tried this (or a similar) configuration?
I've used the nodump flag to avoid backing up parts of a filesystem on
FreeBSD (/usr/ports, for example). It works quite nicely with amanda.
I would expect that some creative use of a dump wrapper and chflags could
help avoid the need to use gnutar to split up large filesystems. I haven't
tried that -- setting the nodump flag on hierarchies of data that is easily
re-obtainable has kept the dumps smaller than the tapes.
-Ben
--
Benjamin Lewis Thank goodness modern convenience is a
Database Analyst/Programmer thing of the remote future.
Purdue University Computing Center -- Pogo, by Walt Kelly
[EMAIL PROTECTED]
