- Release Notes for Bacula 1.29
-
- Bacula code: Total files = 228 Total lines = 62,662 (*.h *.c *.in)
-
-Major Changes this Release:
-- This release is primarily a bug fix release. I spent a great
- deal of time searching for any possible buffer overflow, stress
- testing the memory allocator, and eliminating places where bad
- input or strange characters could cause a crash.
-- All known 1.28 bugs have been fixed.
-- Allow dynamic input of files into Include statements via a
- program or reading a file. E.g.
- Include = {
- "|program input"
- "<file_input"
-- Allow backup of raw partitions.
-- Allow input of data for backup via a fifo -- good for doing a
- "hot" backup of a database.
-- Fixed a major bug that caused Bacula to crash if there were error
- messages in the catalog interface code and you started two jobs
- at the same time.
-- Fixed a buffer overrun bug found by James MacLean in filename quoting
- if you had very long filenames with many single quotes in it.
-- Fixed a number of "recursive" calls to the print routines that would
- eventually cause a crash -- pointed out by James MacLean.
-
-
-Other Changes this Release:
-- Bigendian is detected in configure making porting easier.
-- Added beginning of Gentoo platform files
-- Improved mtx-changer for handling subtle differences between differen
- versions of mtx. Also beginning of handling Bar Code reading.
-- Quite a number of updates to the manual, with more examples ...
-- Documented tape drive modes expected by Bacula.
-- Enhanced the dbcheck program with a few more options and better
- user control as well as better display.
-- Fixed a bug in VolumeUseDuration reported by George Motter.
-- Implemented thread timer routines, currently used to time out FIFO's,
- but ultimately will monitor connections.
-- Improved error reporting. Initial errors no longer changed by later errors.
- Both FD and SD exit status reported in Backup output report.
-- Cancel now work within the File daemon (previously it always traversed all
- files).
-- New Volume Files option for "update" that allows correcting incorrect volume
- file count entries in catalog due to a program crash.
-- Removed virtually all sm_check()s -- should run a bit faster.
-
-
-Items to note:
-- Version 1.28 File daemons can be used with version 1.29, but it
- is preferable to upgrade.
+
+ Release Notes for Bacula 2.5.28
+
+ 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
+use some of the new features that affect the FD. In other words, you should
+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 !!!!!! ==========================
+
+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
+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
+libtool on the configure command line with:
+
+ ./configure --disable-libtool
+==============================================================
+
+This release includes large number of new features and changes.
+It should be more or less compatible with previous xx.conf files
+and File daemons providing that you are not using any of the new
+features.
+
+Please see the New Features chapter of the new manual, which documents
+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.
+
+
projects / bacula / bacula / blobdiff