- Release Notes for Bacula 1.36.0
-
- Bacula code: Total files = 396 Total lines = 116,418 (*.h *.c *.in)
-
-
-Major Changes:
-- Tray monitor program (really cool)
-- Bacula Rescue CDROM (easy to make and essential for emergencies)
-- Bacula CD Image Manager
-- General bug fixes/stabilization
-- French translation of manual by Ludovic Strappazon well
- underway.
-- UTF-8 is supported in conio.
-- Improved conf scanning code allowing FileSet components to
- be put on a single line (previously everything had to be on
- a different line).
-- Win32 files restored to an alternate directory will have the
- colon following the drive letter turned into a / e.g. c:
- becomes c/. Previously the c: was stripped. This applies only
- to files written to an alternate directory (i.e. using a where=).
-- Certain open files (Word for example) can now be saved on
- Win32 systems.
-- Default for Wild-cards on Win32 systems is to fold case this
- should correct most of the problems users are having with
- exclusion on Win32.
-- Lots of improvements in the Rescue scripts -- better
- network detection, better mounting code, ...
-- The attributes spool file can now exceed 2GB.
-- Significant speed improvements when running PostgreSQL.
-- Significantly faster restore command with very large
- FileSets while building the in memory directory tree.
-- Patches directory in the source will have all patches
- that have not been applied and released (new releases are
- only generated when really critical bugs are found).
-- Bacula forces the tape drive into variable block mode
- on most systems (providing Bacula is running in variable
- block mode).
-- dbcheck updated to remove many more orphaned records.
-- Support for IPv6 (untested).
-- Modifications to the license to termination clause for
- more protection from SCO type predators. No change for
- normal users.
-- SIGHUP to Director causes it to reload conf file.
-
-- Many improvements in the documentation.
-
-New Directives:
-- Added "Rerun Failed levels = yes/no" in the Job resource
- of the Director. It will upgrade the current job to a
- higher level (Full or Differential) if a previous job
- of that level failed.
-- Added "Ignore FileSet Changes = yes/no" in the FileSet
- directive of the Director. It prevents the Director from
- immediately upgrading the job to a Full save if you modify
- the contents of the FileSet. Not recommended.
-- Added "Block positioning = yes/no" in Device resource in SD.
- If set to no, Bacula should (as yet untested) be able to
- recover data from tapes where the drive was set to fixed
- blocksize but Bacula is in variable block size.
-- Added "Multiple connections = yes/no" in Catalog record for
- allowing multiple simultaneous connections to the database.
- This is a major performance improvement for PostgreSQL and
- SQLite, but it is untested, so please test before putting
- it into production.
-- Alert Command in SD permits checking for tape drive
- alerts at the end of every job (or doing anything you want).
- An example of the command is in the default bacula-sd.conf
- file as well as in the Storage Configuration chapter of
- the manual.
-
-New Commands:
-- umount -- same as unmount.
-- delete job now permits multiple jobids and ranges, e.g.:
- delete job jobid=1,3,5,11-16
-- reload -- reloads bacula-dir.conf in Director.
-
-Items to note!!!
-- As of 1.35.5 you MUST do a database update.
-
- cd scripts-dir (or src/cats)
- ./update_bacula_tables
-
-- All daemons should be compatible with 1.34 with the exception
- of the new FileSet features such as regular expressions.
-- Regular expressions are not supported in the Win32 FD.
-
-Other Items:
-- Much better error messages from system errors particularly
- on Win32 and in running scripts.
-- Many improvements in the SD.
-- Full support for 64 bit machines.
-- btape improved test and fill commands.
-- See the ChangeLog for additional details.
+ Release Notes for Bacula 2.5.42
+
+ Bacula code: Total files = 521 Total lines = 204,881 (*.h *.c *.in)
+
+The diff between 2.4.4 and 2.5.x is 208,340 lines, so this release
+represents an enormous effort.
+
+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. However, any
+release of version 2.5.40 or greater requires a database upgrade.
+
+================== Warning !!!!!! ==========================
+
+New Catalog format in version 2.5.40
+------------------------------------
+
+This BETA release of Bacula uses a new catalog format. We provide a set of
+scripts 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 can drop the JobHistory
+table before upgrading your catalog (if you are using the new "long term
+statistics" module, you can upgrade this table the same way we do with
+the Job table, see the src/cats/update_bacula_tables script).
+
+The simplest way to:
+1. Stop any current version of Bacula from running.
+2. Save a copy of your existing database.
+3. Configure, build, and install the 2.5.42 version of Bacula
+4. cd <your-scripts-installation-directory>
+5. ./update_bacula_tables
+6. If you have multiple catalogs, edit the update_bacula_tables
+ script and put the name of another database, and then
+ execute the script again. Repeat this until all Bacula
+ catalogs have been updated.
+7. Start the new Bacula. If everything worked, it should
+ not print any error messages.
+
+The upgrade operation will convert the FileId index field of the File table
+from 32 bits to 64 bits. This operation will take TIME and will *temporarily*
+DOUBLE THE SIZE of your catalog. Bacula must be shutdown during this update,
+so, won't be able to run jobs during this period. For example, a 3 million files
+catalog will take 2 mins to upgrade on a normal machine. Don't forget to
+backup it before executing the script.
+If you start from scratch, you don't need to run the update_bacula_tables
+script. However, if you are using a version of Bacula older than 2.5.40,
+then you need to run the update_bacula_tables script that will be found
+in the <bacula>/src/cats directory after you run the ./configure command.
+As mentioned above, before running this script, please backup your
+catalog database, and when you do running it, be sure shutdown
+Bacula and be aware that running the script can take some time depending
+on your database size.
+
+
+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 libraries and linking them into Bacula, 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