Hello, the history of using 2.1.28 in a production system is that at that time we discovered the bug that is just now actual for everyone and while we were trying to find what and how to actually run Bacula that can be used for what it is supposed we ended with 2.1.28 and no concurrent jobs. I am watching the changelog and 2.1.28 is almost the same as 2.2.0 and later there are minor fixes that don't affect our systems and so we are still at 2.1.28 for our live system which is OK. I believe we will upgrade to 2.2.3 now.
Regards. Tuesday, September 11, 2007, 5:29:52 AM: RN> One point that I'm not sure was mentioned before: 2.1.28 was not a RN> production release. I assume you are just doing testing, or have gone to RN> that release because of problems with 2.0.x... but just checking. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
