On 08/20/2013 04:49 PM, Phil Stracchino wrote: > Dmitri, if you look at the approach I proposed, it would back up the > entire tree and only exclude specific files, which entirely sidesteps > the parent-directory-metadata problem you mentioned. Excluding only > the files you don't want is a simpler solution altogether. Are you > arguing that it won't work? Your point is unclear.
My points are
1. Excluding files based on size alone sounds icky. You need to consider
your false positives & negatives carefully.
2. OP didn't say what his fileset normally looks like. Without that
- if he's backing up everything and excluding specific files, then
another exclude should probably work.
- If he's excluding everything and backing up specific files, then
dynamic fileset comes with the parent metadata problem.
3. Most importantly, the only way to do it right is if OP can get his
users to cooperate. Then (e.g.) 'exclude { wild = "*__nobak__*" }' is
all there's to it.
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
