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

I'm not completely sure, but I think that Bacula figures out what media
it is going to use before it calls RunBeforeJob. This would mean that if
you schedule your VirtualFull while your Incremental is running, the
VirtualFull will not include the Incremental backup, no matter how much
you wait inside the VirtualFull's RunBeforeJob script.

Does anyone know for sure?

James

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