Dear All What is the best method to handle a client disconnect?
I have had a few instances where the director has lost connection with the client while either spooling data to disc prior to writing to tape or when the data is being written to tape. The problem is that the cancel option in the console tries to attach to the client prior to canceling the job but the client cannot be connected. There seems to be no kill option like kill -9 PID in *nix. This has caused other jobs in the Running Jobs to wait "forever" - I have not waited long enough to see if the Max Start Delay is activated. My only fix is to restart the processes on the server that is bacula restart. Is there another way to kill the job and still maintain the existing jobs in the Running Jobs. The other problem I have noticed when writing to tape and the disconnection occurs is the volume and catalog are out by 2 - is this due to the update frequency of the catalog? Thanks to all Stephen Carr ------------------------------------------------------------------------- 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
