I am running a single director which controls 2 locations, one local (eg lan speed) to the director, the other remote (eg wan speed - 512kbits). The reason for doing this is that the director runs in a colo facility which is going to be far less likely to have problems like fire and theft than the remote location which is just an office, which makes restoring much easier (catalog already exists). Each location has one sd and multiple fd's.
This works fine, except for one MySQL problem recently which turned out to be disk space related. I was just browsing the documentation and noticed the following in the FAQ section (http://bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION 0037130000000000000000): " All my Jobs are scheduled for the same time. Will this cause problems? [All my Jobs are scheduled for the same time. Will this cause problems? ] No, not at all. Bacula will schedule all the Jobs at the same time, but will run them one after another unless you have increased the number of simultaneous jobs in the configuration files for the Director, the File daemon, and the Storage daemon. The appropriate configuration record is Maximum Concurrent Jobs = nn. At the current time, we recommend that you leave this set to 1 for the Director. " The last sentence gave me cause for concern... I have this set to 2 so that both sites can run their jobs at the same time. Is "Maximum Concurrent Jobs = 1" still the recommendation or is that just a throwback to older versions of Bacula? If it is still the recommendation, why? Thanks James ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
