Hello, On Thursday 08 February 2007 20:21, Andrea Conti wrote: > Hello, > > I have been using bacula for more than a year to back up a small number > of machines. I am perfectly happy with the software, despite a certain > initial difficulty in setting up a working configuration.
Yes, the Director conf file is by far the most difficult to setup. The only good point is that I heard a number of times that it is easier than most other software. > > When I recently upgraded to 2.0 I found out the hard way that the > RunClientAfterJob directive semantics changed quite a bit with the new > version: while in 1.38 the script was run after all activities requiring > a connection with the client were over (including data and attribute > despooling), in 2.0 the script is run as soon as data spooling is > complete. I did not find any mention of this fact in the release notes, > but from a couple of posts on the devel list I got the impression that > this was a deliberate design decision made in order to allow restarting > applications on the client as soon as possible. > > However, this causes nasty effects when ClientRunAfterJob is used to > remotely switch off the client (think backing up powered off > workstations in an office at night, with a RunBefore script to switch > them on via wake-on-lan), because after despooling is complete the > director complains it cannot connect to the fd and simply reschedules > the job. As you have probably seen, I consider this change a bug. Though Eric and I might have talked about this, I never grasped the significance of the change. IMO, the ClientRunAfterJob should always be run at the very end of the job only after all the data has transferred to the SD and the SD has "released" the FD. As Eric mentioned, in 2.1.2 the exact time in the evolution of the whole job when this release occurs has changed, but from what you describe here, that should cause no problem for you since from the standpoint of both the Director and the SD, the FD will have completed its work and can be shutdown providing a small delay is left for the final cleanup (the same as with prior versions). > > After a big headache and lots of wasted space I ended up reverting to > 1.38 FDs - which work as expected - , but this is hardly a solution. > > Is this a bug or a feature? > If it's here to stay, is it possible to have the old behavior back > (possibly via a flag in the RunScript directive)? I'm hoping Eric will provide a patch that puts the old behavior back, and you can either apply it or wait for 2.0.3. > > Plus, I think there should definitely be a mention of the change > somewhere in the documentation. > > Thanks, > Andrea > > > > > > > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
