ebl fix sql scripts and add new update stats query

[bacula/bacula] / bacula / ReleaseNotes

diff --git a/bacula/ReleaseNotes b/bacula/ReleaseNotes
index 11942fcb84e5bfeb7f383a959b9e7f02c146718f..4443960fa01664ddd11208d0bcc711f98819464b 100644 (file)
--- a/bacula/ReleaseNotes
+++ b/bacula/ReleaseNotes
@@ -1,7 +1,7 @@
 
-       Release Notes for Bacula 2.5.16
+       Release Notes for Bacula 2.5.28
 
-  Bacula code: Total files = 517 Total lines = 199,415 (*.h *.c *.in)
+  Bacula code: Total files = 522 Total lines = 203,305 (*.h *.c *.in)
 
 This Director and Storage daemon must be upgraded at the same time,
 but they should be compatible with all 2.4.x File daemons, unless you
@@ -10,27 +10,37 @@ not have to upgrade all your File daemons when you upgrade. There is
 no database upgrade needed from version 2.4.x.  However, the next
 BETA release will require a database upgrade.
 
-==================   Warning !!!!!! ==========================
+================== Warning !!!!!! ==========================
+
+New Catalog format :
+--------------------
+
+This BETA release of Bacula uses a new catalog format. We provide a set of
+script that permit to convert a 2.4.x (version 10) catalog to 2.5.x (version
+11). If you are using already a 2.5 version, you need to drop the JobHistory
+table before upgrading your catalog (if you are using the new "long term
+statistics" module, you can upgrade this table like with the Job table, see
+upgrade_<database>_table script).
+
+The upgrade operation will convert an essential field of the File table, and
+this operation will take TIME and will DOUBLE THE SIZE of your
+catalog temporarily. Depending on your catalog backend, you won't be able to run jobs
+during this period. For example, a 3 million files catalog will take 2mins to
+upgrade on a normal machine. Don't forget to backup it before executing the
+script.
+
+
+New configure option :
+----------------------
+
 This BETA release of Bacula 2.5.x development code uses libtool
 to generate the Bacula libraries as shared objects rather than
 being directly linked in as in prior versions.  This means that
 the Bacula shared objects, must either be in a shared object 
 directory known to the loader or they must be in the directory
-that may be specified on the ./configure line using the
---libdir option as:
-
-  ./configure --libdir=/full-path/dir
-
-the default /lib. If --libdir is specified, there should be
-no need to modify your loader configuration provided that
-the shared objects are installed in that directory (Bacula
-does this with the make install command). The shared objects 
-that Bacula references are:
-
-libbaccfg.so
-libbacfind.so
-libbacpy.so
-libbac.so
+where the Bacula binaries are installed.  It is also possible
+to explicitly specify the libraries directory on the ./configure
+line (--libdir=/full-path/dir), but this should not be necessary.
 
 If you have problems with libtool or you wish to use the old 
 way of building static libraries, you can do so by disabling 
@@ -50,3 +60,5 @@ some but not all the new features (we are still working on it):
 http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html
   
 The ChangeLog has more details.
+
+