Bacula-users

Re: [Bacula-users] Running both full and inc backups

2011-02-11 11:53:15
Subject: Re: [Bacula-users] Running both full and inc backups
From: Phil Stracchino <alaric AT metrocast DOT net>
To: bacula-users AT lists.sourceforge DOT net
Date: Fri, 11 Feb 2011 11:50:45 -0500
On 02/11/11 11:35, J. Echter wrote:
> Am 11.02.2011 16:44, schrieb David Noriega:
>> I'd like to run incremental backups twice a week, but also need full
>> backups done every two/three(TBD) weeks. Is there a way to do this
>> without setting up a full and then an inc backup job? Because that
>> would lead to 'two' backup catalogs from which to pull a restore from?

Not only is there a better way, but in fact, doing it as two separate
Jobs simply will not work.

You DID read the quick start guide, right...?


> just an example:
> 
> Schedule {
>    Name = Backup
>    Run = Pool=File Level=Incremental mon-fri at 23:00
>    Run = Pool=File Level=Differential 2nd-5th sat at 23:00
>    Run = Pool=File Level=Full 1st sat at 23:00
> }

In this example, if you're using the same Pool every time, why even put
a Pool override in at all?  Additionally, Pool overrides in the Schedule
are deprecated in favor of Pool specification in the Job, because they
do not work correctly (and cannot be made to work correctly) in all cases.

So this should suffice:

Schedule {
   Name = Backup
   Run = Level=Incremental mon-fri at 23:00
   Run = Level=Differential 2nd-5th sat at 23:00
   Run = Level=Full 1st sat at 23:00
}


If you want to specify different Pools for different levels, it is
better to do so using Full Pool, Differential Pool, Incremental Pool in
the Job or JobDefs.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users