On 06/01/2011 17:48, Phil Stracchino wrote:
> On 01/06/11 12:16, Graham Keeling wrote:
>> With my configuration, a VirtualFull sometimes prevents an Incremental from
>> running, because the VirtualFull took too long (or vice versa). I have not 
>> been
>> able to solve this, because every idea that I've come up with either doesn't
>> work or makes something else happen that is worse.
> Suggestion:
>
> Schedule the day's Incremental, then schedule the VirtualFull, say, 30
> minutes later.
>
> Put a RunBeforeJob script on the incremental that creates a lockfile (in
> a properly race-safe manner, of course) for the client.
>
> Put a RunAfterJob script on the incremental that removes the lockfile.
>
> Put a RunBeforeJob script on the VirtualFull job that checks for
> presence of the client's lockfile, and, if it finds it still present,
> sleeps for five minutes before checking again, and does not return until
> the lockfile has been gone for two consecutive checks (thus making
> certain there is a minimum of five minutes for attribute metadata from
> the job to be flushed).
>
>
Brilliant - sounds workable, I just don't know if my bacula skills are 
up to it, I'm still very fresh to it, but the theory of your suggestion 
is the closest I guess we can come. I will look into in - Thank you 
bacula list :)

------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users