[Bacula-users] Feature Request: non-disruptive full backups

[(private) H. <hks...@gm...>]

Would anybody else find this useful?

To solve the below problem, I created separate jobs for each of my
clients. What would have made this task much simpler is a level of
backup that is functionally full, but doesn't disrupt the chain of
incrementals/differential. That way, instead of doubling the number of
jobs in my config file, I could have just modified my schedule to
this:

Schedule {
  Name = "WeeklyCycle"
  Run = Full 1st sun at 2:05
  Run = Differential 2nd-5th sun at 2:05
  Run = Incremental mon-sat at 2:05
  Run = Level=NDFull Storage=Tape Pool="Tape Pool" sat at 10:05
}

Just an idea.

-HKS

On Mon, Apr 6, 2009 at 5:19 PM, (private) HKS <hks...@gm...> wrote:
> Bacula 2.2.8 on OpenBSD 4.4 in a mixed OS environment.
>
> I'm introducing tape backups into a disk-only backup scheme, and
> trying to figure out what the best way to do so is. Right now, I think
> the best option is to modify my schedules from this:
>
> Schedule {
>  Name = "WeeklyCycle"
>  Run = Full 1st sun at 2:05
>  Run = Differential 2nd-5th sun at 2:05
>  Run = Incremental mon-sat at 2:05
> }
>
> To something like this:
>
> Schedule {
>  Name = "WeeklyCycle"
>  Run = Full 1st sun at 2:05
>  Run = Differential 2nd-5th sun at 2:05
>  Run = Incremental mon-sat at 2:05
>  Run = Level=Full Storage=Tape Pool="Tape Pool" mon at 10:05
> }
>
> The obvious problem is that the weekly tape backup will disrupt my
> incremental/differential scheme. Is there any way to avoid this? I'm
> probably just not thinking this through right, but it seems wrong to
> me that a full backup to a given storage device would disrupt
> incrementals on a different storage device.
>
> Alternatively, does anyone have an elegant solution for getting
> regular tape backups of all their clients without messing with
> existing ful/diff/incr schemes and without duplicating jobs for all of
> them?
>
> -HKS
>