Bacula-users

Re: [Bacula-users] Issue with recycling after moving from 2.0 to 2.4

2009-02-13 10:16:42
Subject: Re: [Bacula-users] Issue with recycling after moving from 2.0 to 2.4
From: Kevin Keane <subscription AT kkeane DOT com>
Date: Fri, 13 Feb 2009 07:14:16 -0800
Yann Cézard wrote:
> Kevin Keane a écrit :
>> If my math is right, the 12th is the 13th day of the retention 
>> period. Since the previous job finished at 22:43, and your new job 
>> started at 22:38, the rentention period hadn't elapsed yet, by about 
>> five minutes. The reason it sometimes works and sometimes doesn't is 
>> simply the timing between the jobs.   
> Actually, I don't agree with your maths, sorry :)
> The 12th was the 14th day of the retention period.
> 29th 22:43:13 => start of retention, day/hour 0
> 30th 22:43:13 => 1st day
> 31th 22:43:13 => 2nd day
> 1st 22:43:13 => 3rd day
> 2nd 22:43:13 => 4th day
> ...
> 11th 22:43:13 => 13th day : job could be pruned, and then the volume
> 12th 22:38 => job is still there, volume is still not recycled ???
>
> So basically it looks more like a Job pruning problem ?
Oops. I think you are right. What are the volume, job and file retention 
times? I didn't see those two values in the tables you sent earlier; 
maybe I missed it. The only retention time I saw was the one for the 
pool - which really has no direct effect at all here. Maybe one of the 
files still had an unexpired retention time? In that case, the job won't 
get purged even if the job itself has passed its retention time. 
Similarly, if the job retention time is longer, the volume won't get 
purged even if its retention time has passed.
>> As you back up larger jobs, this problem is going to get worse. You 
>> really need more than 12 volumes for a 13 day retention period.
> I have 14 volumes : 2 full (1 day per week) + 12 incremental
> (6 days per week).
> So even if the job stopped one day after schedule (I limit
> the job to 20 hours by the way), when the "two week after"
> job should takes place (should it be Full or Incr), the volume
> should already have been recycled.
> That's why I choosed this 13 days Retention time, and not 14.
>
> Or perhaps I am wrong and don't understand some basic thing here ?
I think you  have to look at the incremental and full pools separately. 
You have 13 days, and you have effectively 13 incremental volumes to 
work with (one of them is virtual because you are not using up an 
incremental volume on the day you did the full backup). That means that 
on some days, you will run into this timing problem.
>> Personally, I would suggest you consider letting Bacula automatically 
>> label volumes as needed. Also, with bi-weekly backups, you may want 
>> to consider 15 days instead of 13 days as your retention period. 
>> Otherwise, bacula has to delete an older backup just before doing the 
>> next one, and you'd be left with just one backup on your disk. If 
>> that is somehow corrupted, you'd have a problem.
>>   
> I know that, but that's a choice that I have made, I should restrict
> the size of backups that I have (more than 6To actually, keeping one
> more Full Jobs would mean about 9To...).
Wow. That's pretty big. I didn't check in your original post, but is it 
possible that some of the full backups take more than 24 hours? That 
might throw off the schedule, too.

-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, please notify the sender immediately and 
permanently delete the e-mail and any copies, printouts or attachments thereof.


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users