- Release Notes for Bacula 1.31
-
- Bacula code: Total files = 243 Total lines = 70,151 (*.h *.c *.in)
-
-Major Changes this Release:
-- Support to save and restore all files on WinNT/2K/XP systems
- including the permissions. Unfortunately files that are in use by another
- program cannot be saved.
-- Support for Win95 systems (untested since I don't have Win95).
-- Heartbeat every 20 minutes between daemons to prevent network
- timeouts. The heartbeat interval can be set.
-- Volume names may now only contain letters, numbers, colon, period, dash,
- and underscore.
-
-
-Other Changes this Release:
-- Preliminary support for BSDi.
-- Use smtp instead of mail to send the traceback message.
-- Fixed a race condition in the "list" command while a backup is
- in progress.
-- Beginning of support for SSL encryption.
-- Beggining of support for Base level backups.
-- Improvements to gnome-console.
-- Prune certain orphaned jobs (no files saved, no Volume used).
-- Added non-fatal errors to Job reports.
-- Eliminate need for SubsysDirectory in each daemon.
-- Add a lot more "command line" options to console commands.
-- More info in traceback (database type, ...).
-- Better handling of errors with autochangers during restore.
-- Better cancellation of jobs in Storage daemon (doesn't try
- to cleanup twice).
-- SD error messages such as autochanger errors are now properly
- directed back to Console -- previously some were lost.
-
-
-
-Items to note: !!!!!
-- For MySQL users, you must have the thread safe client libraries
- available. If you build MySQL yourself, add the --enable-thread-safe-client
- option on the ./configure.
-- Version 1.31 and 1.30 daemons/Director are not compatible. You must
- upgrade all or nothing.
+ 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