Bacula-users

[Bacula-users] Antw.: Re: question about schedules and retentions

2008-11-11 16:25:17
Subject: [Bacula-users] Antw.: Re: question about schedules and retentions
From: Carlo Maesen <c.maesen AT aca-it DOT be>
To: Arno Lehmann <al AT its-lehmann DOT de>
Date: Tue, 11 Nov 2008 22:22:14 +0100 (CET)
----- Oorspronkelijk bericht -----
Van: "Arno Lehmann" <al AT its-lehmann DOT de>
Aan: "bacula-users" <bacula-users AT lists.sourceforge DOT net>
Verzonden: Dinsdag 11 november 2008 20:45:45 GMT +01:00 Amsterdam / Berlijn / 
Bern / Rome / Stockholm / Wenen
Onderwerp: Re: [Bacula-users] question about schedules and retentions

Hi,

11.11.2008 18:18, Carlo Maesen wrote:
> I did read the bacula manual but, I have some questions about schedules.
> I creat the following schedule:
> Schedule {
>   Name = aca-cycle
>   Run = Level=Incremental Pool=aca mon-thu at 22:00
>   Run = Level=Full Pool=aca 1st-4th sat at 22:00
> }
> 
> I backup one client according this schedule, but each different run has also 
> a different file and job retention. (Incr = 4 weeks, Full = 1 year)
> Do I have to create 2 different clients and jobs, one for the incemental 
> backup and one for the full ?
> Because the file and job retenion is defined in the client-directive.

If you actually need the job-specific retention times you are in 
trouble...

An incremental can only be based on the latest full backup for the 
same job, and a job is defined by the unique combination of client and 
fileset.

The better approach is to use distinct pools for full, differential, 
and incremental backups, where each pool has its own retention settings.

When a job is purged from a pool volume, the accompanying file and job 
data is also removed.

Typically, you'll keep the full backup longest, so in essence, the job 
  and file retentions apply to full backups only, if they are longer 
than the retention times of the partial backup pools retention times.

This, typically, is exactly what is needed - complete control when 
restoring from recent backups, and less control but also less database 
use for the long-term storage.

Arno

Hi Arno,

After I create the 3 pools (with different retentions), I only have to create 1 
client with a file/job retention of 1 year.
When the volume retention of the incremental-pool expires (4weeks), the 
corresponding files/jobs will be pruned from the catalog. Because the shortest 
retention takes precendence. Is this correct ?





-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>