- Release Notes for Bacula 5.2.0
+ Release Notes for Bacula 5.2.0 Beta 1
- Bacula code: Total files = 1,088 Total lines = 219,172 (Using SLOCCount)
+ Bacula code: Total files = 1,110 Total lines = 231,439 (Using SLOCCount)
General:
--------
This 5.2.0 version is a major release since the last version 5.0.3.
-It includes well over 50,000 lines of changes and a number of important
-new features:
+It includes well over 50,000 lines of changes made by 19 contributors
+and a number of important new features:
Compatibility:
--------------
Director and Storage daemons. There should be no need to upgrade older File
Daemons.
-Changes and New Features:
+================== Warning !!!!!! ==========================
+
+ The new pruning algorithm will not allow to prune jobs that are essential to
+ restore since the last Full backup. Pruning of volumes are not affected.
+
+New Catalog format in version 5.2.0
+-----------------------------------
+This release of Bacula uses a new catalog format. We provide a set of
+scripts that permit to convert a 5.0.x (version 12) catalog to 5.2.0 (version
+14). The Bacula project rpms distributed on Source Forge will automatically
+detect the database change and do the upgrade for you. We strongly
+recommend that you save a copy of your existing database before upgrading
+using rpms.
+
+The simplest way to upgrade the database assuming you are building from
+source:
+1. Stop any current version of Bacula from running.
+2. Save a copy of your existing database.
+3. Configure, build, and install the 5.2.0 version of Bacula
+ Note the new ./configure options in the manuals see the link
+ at the bottom of this file.
+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.
+
+If you start from scratch, you don't need to run the update_bacula_tables
+script because the create_bacula_tables script automatically creates the new
+table format. However, if you are using a version of Bacula older than 5.0.0
+(e.g. 3.0.3) 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.
+
+================================================================
+
+Changes:
+
+Speed and Memory Usage Enhancements:
+- Implement LZO compression algorithm (need lzo2 headers to activate this option)
+- New Pruning algoritm -- safer and faster
- Use of PostgreSQL cursor when doing large queries, should reduce the
memory usage during restore and accurate backups.
-- Includes better handling for Windows repares points, mount points, and
- junction points.
-- A few path name length limits in Windows have been removed.
-- New SQL backend and ./configure that permits building multiple catalog
- backends in one build, and has the main Bacula core code totally independent
- of the SQL backend, which should simplify packaging (only the libbacsql.so/dll
- needs to be changed.
-- New database format
-- Director selection option in bconsole
-- restorejob command in bconsole
-- Checkpoint of jobs so that in many cases they can be restarted
-- Maximum Bandwidth Per Job in several places
-- Disable batch insert config item
-- setbandwith command
-- limit command
+- limit command in some list commands
- Bacula Virtual File System for fast catalog access
-- New Pruning algoritm -- safer and faster
+- Faster crc32 algorithm
+
+Security Enhancements:
- Additional security against injection of illegal characters
-- New block delta backup/restore
-- Indent lsmark during restore
-- Additional script variable editing
+- Fix possible fnmatch problem
+
+Features Enhancements:
- Improvements in ACL and xattr handling on additional platforms:
AIX, Darwind, FreeBSD, HPUX, IRIX, Solaris, Tru64
+- Tray monitor for Windows
+- New SQL backend and ./configure that permits building multiple catalog
+ backends in one build, and has the main Bacula core code totally independent
+ of the SQL backend, which should simplify packaging (only the
+ libbacsql.so/dll needs to be changed.
+- Indent lsmark during restore
+- Disable batch insert config item
+- Director selection option in bconsole
+- restorejob command in bconsole
+- Many additional features for bat such as "brestore" panel
+- Improved hash table for hard links
+- Additional script variable editing such as %b (JobBytes), %F (JobFiles)
+ and %h (Client Address)
+
+Other Enhancements:
+- Includes better handling for Windows repares points, mount points, and
+ junction points.
+- New database format
- Many new plugin API features
-- Faster crc32 algorithm
- Improved memory handling for restores
-- Improved hash table for hard links
- Significant stability enhancements to bat
-- Many additional features for bat
-- Tray monitor for Windows
-- New FTP device handler for Storage daemon
-
-Bug fixes
+- A few path name length limits in Windows have been removed.
===========================================================================
-This 5.0.3 version is significant bug fix update to version 5.0.2.
+The 5.0.3 version is significant bug fix update to version 5.0.2.
It includes new code and some new features.
There is no database change since prior versions of 5.0.