On Tue, Jul 29, 2014 at 12:15:06 +0700, Olivier Nicole wrote: > If I may... I think the solution suggested by Nathan does not lean > toward the excludes.
Yes, that's correct. The thread only mentions excludes as a workaround for situations where program=GNUTAR dumptypes are still being using, since those dumptypes don't allow message handling to be configured on the fly. When one is using the amgtar application (as Gene is), the "direct" way to adjust to tar's new behavior is to add the property "NORMAL" ": directory is on a different filesystem; not dumped" line to the amgtar configuration block (or perhaps an IGNORE line instead). That approach changes Amanda's handling of this specific warning message, without changing anything else about the operation of the dump. (And this is the default configuration in Amanda 3.3.6 and later.) (Gene, if you still decide to use excludes, you'll need to be sure that the exclude lines you use allow tar to back up the mount-point directory themselves -- otherwise if you have to do a bare-metal restore you'll probably have to manually go back and create those directories before the Ubuntu startup scripts will be able to work properly.... [This "directory v.s. contents" topic is touched on in http://wiki.zmanda.com/index.php/Exclude_and_include_lists ... but I won't be more specific since you shouldn't be doing it that way :) .]) Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
