John Drescher wrote:
> On Fri, Apr 3, 2009 at 8:02 PM, Maria McKinley <maria AT shadlen DOT org> 
> wrote:
>> Greetings,
>>
>> I posted this a bit ago, but didn't receive a response, so thought I
>> would try again...
>>
>> I would like to have most of the jobs I run to be compressed and put on
>> disk, but I want the daily incremental to be put on tape, which means
>> letting the hardware do compression. It looks like the only way to do
>> this is to define a separate FileSet for the jobs done nightly than for
>> the jobs done weekly. However, I'm pretty sure that this will mean that
>> the daily is truly a separate job, and will not recognize the weekly
>> full backup as the same job, even though they are the same files, and
>> will thus not 'reset' every week to the current weekly backup, and will
>> continue to indefinitely do incremental to the full set it will want to
>> do when I start the bacula daemon. Is there any way around this, or
>> should I just move entirely to disk?
>>
> 
> If you are just talking about incrementals I would just let the
> compression run. You are correct that this new fileset will make it
> look like a different job and it will promote the first to a full.
> 
> John

I guess that means you can't over-ride it in the Storage resource? Now 
that I think about it, it seems a little strange to me that this is 
configured in the FileSet resource instead of the Storage resource.

thanks,
maria

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users