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


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
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