>> 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".
Right. I will try upgrading sometime soon. Is it an easy matter to upgrade my existing installation from v1.38.2 to v2.0? I presume that I need to download, compile and install the new bacula binaries. Do I need to do anything to upgrade the database / config files? Will I need to delete my existing backup files? Any pointers or a link to some instructions would be great! Many thanks, Chris. ------------------------------------------------------------------------- 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
