On Mon, Jan 24, 2011 at 2:54 PM, Phil Stracchino <ala...@metrocast.net> wrote: > On 01/24/11 14:46, Derek Wright wrote: >> Indeed the point was missed... Where I work we operate within a strict >> maintenance window. If our SA's want to take a server down from >> 12am-4am then thats their window, no guess work about it. I figured it >> might be useful to have Bacula be aware of this window and kick off >> the backup (or re-try in *user specified min* if client-fd doesn't >> respond on first attempt) so that I don't have to wake up at 4am just >> to re-enable/run the job. However from the sounds of most replies, >> most people don't operate within the confines of a maintenance window. > > Aaaaah. So is the problem perhaps not so much one of needing to > schedule predefined maintenance windows within Bacula, as of having > Bacula automatically retry a client that is unavailable due to > maintenance? Because the latter - retrying unavailable clients after a > defined interval - can already be done with existing Bacula functionality. >
No i fit that in as an after thought, figured it might help to have a little buffer to make sure the client comes back after a maintenance... ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
