Bacula-users

[Bacula-users] Retention period definitions clashing with scheduling definitions?

2009-01-22 12:39:34
Subject: [Bacula-users] Retention period definitions clashing with scheduling definitions?
From: Foo <bfoo33 AT yahoo.co DOT uk>
To: "bacula-users AT lists.sourceforge DOT net" <bacula-users AT lists.sourceforge DOT net>
Date: Thu, 22 Jan 2009 18:36:22 +0100
Hi,

Just to make sure I've got this correct: Bacula does a simple calculation  
when parsing retention config options such as month=30 days*24 hours*60  
minutes*60 seconds everywhere.

An example:

maximum volumes=3 (per pool)
volume use duration=1 month
volume retention=5 weeks
file retention=2 months
job retention=2 months

Which translates to (llist volumes):

      VolRetention: 3,024,000
    VolUseDuration: 2,592,000

So, Vol A is used for 2,592,000 seconds (day 1-30 day), on day 65 its  
status is changed from Append to Used (volume retention=5 weeks) and  
associated files/jobs are purged from the database on day 91. (I may have  
the status names confused)
Vol B is used from day 31-60, its status changes on day 95, file/jobs  
purge on day 121.
Vol C is used from day 61-90, its status changes on day 125. file/jobs  
purge on day 151.
On day 91, Bacula sees Vol A is the only one from the pool which can be  
recycled (status Used) and it has also just purged file/job info from the  
db so the cycle is complete, everything's fine.

Except, in the schedule section, if you use something like: Run = Full 1st  
sun at 00:30, the actual backup date can be up to 6 days later (i.e. month  
starts on a Monday, so 1st Sun is 7th day). For 2009, 1st Sun in  
Jan/Feb/Mar/Apr is 2009-01-04, 2009-02-01, 2009-03-01 and 2009-04-05.

Vol A is used from 2009-01-04 - 2009-02-02, status changed on 2009-03-09,  
files/jobs purged on 2009-04-03.
Vol B from 2009-02-03 - 2009-03-04, status 2009-04-08, purge 2009-05-03.
Vol C from 2009-03-05 - 2009-04-03, status 2009-05-08, purge 2009-06-02.

So, Vol A has a full backup on 2009-01-04 and 2009-02-01, Vol B has a  
backup on 2009-03-01 and Vol C has no backups at all. After the cycle  
rotates around and Vol B is purged, if something goes wrong you are  
basically missing a month.

Also, if you make the mistake with file/job retentions using 3 months for  
example you will also end up with warnings (and no backups) while Bacula  
is waiting to purge file/job info.

Is there any way to have Bacula keep dynamic track of weeks/months and  
interpret 'month' as 28 days for February for example?


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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>
  • [Bacula-users] Retention period definitions clashing with scheduling definitions?, Foo <=