Le jeudi 03 septembre 2009 à 11:24 -0700, Cedric Tefft a écrit :
> You might be able to accomplish this with a short script that identifies 
> the large files, run it before every backup, and use its output as an 
> include list for your large-files job and an exclude list for your 
> small-files job.

I didn't test it, but I've infered from the doc (2.4): 

        "Any change to the list of the included files will cause Bacula
        to
        automatically create a new FileSet (defined by the name and an
        MD5
        checksum of the Include/Exclude contents). Each time a new
        FileSet is created, Bacula will ensure that the next backup is
        always a Full save."

that your proposed solution shall trigger a full save, which may not be
what's wanted </understatement>

I'll be very happy to learn that I'm wrong because it's one of the
issues that nags me in Bacula.

Nicolas



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users