Alan is correct, you don't want the catalog backup occurring when other client jobs are running. You can setup the job (as Alan noted) to run after all other jobs have completed -- the stock configuration is set up this way out of the oven. I get this same message if there are still jobs running or waiting to time out (this happens with a client that is off line) but it eventually fires and we get a good backup of the catalog.
Setting the Heartbeat option keeps the FD <--> SD communication link 'open' (this is my rudimentary understanding) to cope with congestion on the network. It won't solve your network problems but will allow bacula to get the job done if there are issues with the data link between the FD and SD. For a number of client machines we backup over the 'net, this configuration setting is a life saver. We have our client jobs running concurrently and storing to disk. There is a significant risk (apparently) if attempting to do this to tape - if I recall, you're setup was going to disk. Check your Max Concurrent Job settings in the Dir and SD configurations. Unless I've missed something here, there isn't a bug to track down, just an appropriate configuration needs to be made. On Jan 4, 2007, at 12:23 PM, Alan Brown wrote: > On Thu, 4 Jan 2007, Chris Rodgers wrote: > >>> You need to add a RunBeforeJob which will exit with an error if >>> ngorongoro is not online. Ther ewas some discussion on this in >>> the past >>> relating to laptops and there may already be a script for it >>> somewhere. >> >> This sounds like a bacula bug to me. Surely bacula should be able to >> cope if one of the client machines is unavailable for some reason. > > Bacula will give up and continue on other machines.... eventually. > > However for a machine which is known to not always be there, it is > better > to test in the first place or shorten the "giveup" timeout from > default > settings. > >> If it cannot, it makes it very easy to perfom a denial of service >> attack. It could also mean that in a larger office / etc. where >> machines >> are occasionally unavailable for some reason that the machines >> last in >> the backup list are rather likely not to be backed up. That seems >> quite >> a significant flaw to me. > > If you have concurrency set high enough and the max start delays > set long > enough, the backups will run... :-) > >>> Possibly, but more importantly these jobs should never had shown as >>> finished on the Director status until the Storage daemon said >>> they were >>> finished - the fact that they're wedged means that the >>> BackupCatalog job >>> should never have started in the first place.... >> >> To my mind, the correct behaviour would be for the director to >> terminate >> the job after FDConnectTimeout has elapsed and then to inform the >> storage daemon that the job has been cancelled / had an error. At the >> moment, it looks like the director cancels the job but leaves the >> storage daemon in an inconsistent state. > > "This should not be happening" and if it is occuring with 2.0 then > it's > definitely worthy of a bug report. > > As for older versions, "Your Milage May Vary". > > AB > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
