Bacula-users

Re: [Bacula-users] Problem with huge backup - possible bug

2008-10-16 16:13:08
Subject: Re: [Bacula-users] Problem with huge backup - possible bug
From: Arno Lehmann <al AT its-lehmann DOT de>
To: bacula-users AT lists.sourceforge DOT net
Date: Thu, 16 Oct 2008 22:08:00 +0200
Hi,

16.10.2008 18:40, T. Horsnell wrote:
> Arno Lehmann wrote:
>> Hi,
>>
>> 16.10.2008 15:53, John Drescher wrote:
>>
>>>>> Does the first job take more than 1 day?
>>>> Yes, that is true in this case. But is this making any difference ?? With
>>>> running full backup there shouldn't be any next job upgraded to full prior 
>>>> to
>>>> finish of first one.
>>>>
>>> The reason I ask is when the next backup is scheduled to begin if the
>>> previous full is not completed the next backup will be upgraded to a
>>> full. There has been some discussion of this problem on the list. I am
>>> not sure of the solution to this but I will try to check the archives.
>>
>>  From my memory: One user implemented a small run before job script 
>> that checks if a corresponding full for the current job is running and 
>> returns 1 if that's the case, thus effectively canceling the newly 
>> scheduled job.
>>
>> In some future version, some directives will be available to prevent 
>> the outlined scenario. I forgot which directive names were discussed, 
>> though... and I don't think this is in the devel manual.
>>
>> Arno
> 
> I had this problem from the start. I ended up with a line in my 
> RunBefore script which disabled the backup job:
> 
>    echo "disable job=Job1" | /usr/local/bacula/bin/bconsole
> 
> This disables any further scheduling of Job1 but leaves the current one 
> running.
> 
> And in the RunAfter script I have
>    echo "run job=BackupCatalog yes" | /usr/local/bacula/bin/bconsole
>    echo "enable job=Job1" | /usr/local/bacula/bin/bconsole

Now this is a really slick way to solve that (works only with 2.erm... 
don't know now though, because job enabling/disabling wasn't always 
available).

Let me state that I always knew that Cambridge academia was among the 
cleverest in the world ;-)

Arno

> 
> The BackupCatalog job is set 'enabled=no' in bacula-dir.conf
> 
> I'm sure I saw some discussion on the devel list of upcoming facilities 
> which would disable a scheduled job if some other job was still running, 
> but I'm damned if I can find the relevant emails
> 
> Cheers,
> Terry
> 
> -------------------------------------------------------------------------
> 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
> 

-- 
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de

-------------------------------------------------------------------------
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