Arno Lehmann schrieb: > Hello, > > 19.11.2009 10:07, Christian Gaul wrote: > >> Amongst many other clients, i backup my workstation using bacula (in >> this case 3.0.3, but i've been seeing this since i started using bacula >> with version 2.2 something). >> >> I can see the job for my client in the director, it is in the status >> "Waiting for client XXX to connect to storage YYY", and it has been in >> that status since i turned it off (around 13 hours ago). I am unable to >> cancel the job, because it is not running or scheduled and none of the >> other jobs on the director were able to start, they are all "waiting for >> execution" and older jobs have been canceled (thanks for fixing the >> canceled email notification with 3.0.3 btw) which means that, on this >> director, i have not had nightly backups run on any of my clients, on >> any of my SDs because a single client got turned off inbetween the >> director initializing the job and the client making the connection to >> the SD. >> > > The way I do things: > - use concurrent jobs to make sure stalled ones don't stop all the > other jobs > - use a "Run Script" in the jobs where I back up machines that may be > offline or turned off, that basically just pings them and fails the > job if no success. > - set up those jobs to be retried a few times with reasonable > interval, so if a laptop comes in or a desktop is turned on, it will > be backed up automatically. > > Works quite well... > > Cheers, > > Arno > > > Thats exactly what i have too.. except for the concurrent jobs, which lead to "number of files mismatch" on my bacula 3.0.x director / SD combinations (several threads already in -user which didnt lead to anything much). But even if i had concurrent jobs i presume it wouldnt help because if it did i could run other jobs on other SDs (director has 100 jobs max, SDs it depends on media type.. i cant seem to get tapes to take more than 1 concurrent job without "number of files mismatch"-fail) which i can't currently do. One job on the director (100 jobs max concurrent) can stop me from scheduling a job on any of the connected SDs.
My script which does the same as yours ran at 18:00, scheduled the job, which is when i turned off the client to be backed up.. i dont see this problem often, because of this script, but it isnt failproof, it just makes the window for failure smaller. Thanks for your ideas though ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
