2 Release Notes for Bacula 5.0.1
4 Bacula code: Total files = 1,081 Total lines = 217,272 (Using SLOCCount)
8 -----------------------------------------------------------
9 You might be wondering why this release jumps from 3.0.x to
10 5.0.0 thus skipping version 4.0.0. We have done this for
11 several reasons: first, we wanted a way of distinguishing
12 the numbering system for the Bacula System Enterprise version
13 and the Bacula Project version. So, to do so, we have decided
14 that the first number of the Bacula Project version will always
15 be odd, and the first number of the Enterprise version will always
16 be even. Thus the Bacula Project now moves from 3.0.x to 5.0.x.
17 In addition, we want to keep the Bacula Project version larger
18 than the Enterprise version to indicate that the Bacula Project
19 version is more advanced or has more features than the
20 Enterprise version. For memory, the current Enterprise version
21 is 2.6.1, and the next release (in a few months -- before June 2010)
22 will be version 4.0.0.
25 --------------------------------------------------------------
26 Please note the three Warnings below before doing any install or
34 1466 1467 1468 1481 1486 1488
36 - Fix bug #1488 -- create delivery_error() subroutine to avoid recursion and
37 race conditions in messages.c
38 - Upgrade cats library also to 5.0.0
39 - Fix missing console page in bat
40 - Add bat help files to Win64 installer
41 - Win -- add help files to installer + stop any running bacula-fd before
43 - Fix bug #1481 -- bat consumes all console file descriptors
44 - Backport truncate on purge from 5.1.x
45 - Fix bug #1486 -- bat doesn't show any errors on command-line
46 - Update the bsock error url
47 - Correct .my.cnf umask in make_catalog_backup.pl
48 - Apply Philipp's fix for dbcheck use by make_catalog_backup.pl
49 - Fix seg fault in bscan from new comment field
50 - Patch from checks multple CNs when using TLS
51 - Fix seg fault in SQlite driver
52 - Make versions of shared libs inline with the software version.
53 - Remove file_index sequential check -- reported by Graham
54 - Fix #1466 about Bogus pruning message
57 Changes since 3.0.3a (the last Bacula Project release):
58 -------------------------------------------------------
61 1337 1351 1352 1354 1357 1361 1367 1369 1370 1373
62 1376 1391 1403 1409 1420 1422 1427 1428 1431 1450
66 - Problem that locks the Director when the SMTP server wasn't
67 responding to the bsmtp program
68 - Restore's dir command shows incorrect file sizes
69 - Fix various problems with the reload command
70 - Fix problems with conio
71 - Eliminate several deadlocks or potential race conditions from SD
74 - Project 5: Truncate volume after purge
75 - Project 6: File Deduplication using Base Jobs
76 - Project 10: Restore from Multiple Storage Daemons
77 - Project 11: AllowCompression per Device
78 - Project 23: Add Maximum Concurent Jobs for Devices to balance load
80 - Add Accurate Fileset Options to configure accurate detection. Can use
81 checksum verification for example.
82 - Allow FD to keep root read but drop write permission (CAP)
83 - Secure handling of passwords for catalog backup
84 - Add Tab-completion for Bconsole when using Readline
85 - Add Bvfs API to query the catalog without building a memory tree
86 - Add new speed test to btape program
87 - Add new Bat screens (Autochanger content, Job view, Media view, ...)
88 - Windows version of Bat
89 - Added Spanish Bacula translation
90 - New bconsole -u nnn option to have timeout on commands
91 - Allow Migrate, Copy, and Virtual Full to read and write
93 - show disabled -- shows disabled Jobs
94 - Add Pool File and Job retention periods (take precedence over Client)
95 - Many ACL improvements
96 - Level added to FD status Job entry
97 - Allow turning on/off Block Checksum per device
98 - Set Device Poll interval to 5 minutes -- previously did not poll
99 - Implement lock manager with bad order protection
102 As always, both the Director and Storage daemon must be upgraded at
103 the same time, and on any given machine, you must run only one version
104 of Bacula. This means that on the Director and Storage daemon machines,
105 you *must* upgrade your File daemon as well.
107 Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 5.0.0
108 Director and Storage daemons. There should be no need to upgrade older File
109 Daemons immediately. However, we recommend that you do so as soon
110 as is reasonable for your situation.
112 ================== Warning !!!!!! ==========================
114 New Catalog format in version 5.0.0 (3.1.9 or later)
115 -----------------------------------------------------
117 This release of Bacula uses a new catalog format. We provide a set of
118 scripts that permit to convert a 3.0.x (version 11) catalog to 5.0.0 (version
119 12). The Bacula project rpms distributed on Source Forge will automatically
120 detect the database change and do the upgrade for you. We strongly
121 recommend that you save a copy of your existing database before upgrading
124 The simplest way to upgrade the database assuming you are building from
126 1. Stop any current version of Bacula from running.
127 2. Save a copy of your existing database.
128 3. Configure, build, and install the 5.0.0 version of Bacula
129 Note the new ./configure options in the manuals see the link
130 at the bottom of this file.
131 4. cd <your-scripts-installation-directory>
132 5. ./update_bacula_tables
133 6. If you have multiple catalogs, edit the update_bacula_tables
134 script and put the name of another database, and then
135 execute the script again. Repeat this until all Bacula
136 catalogs have been updated.
137 7. Start the new Bacula. If everything worked, it should
138 not print any error messages.
140 If you start from scratch, you don't need to run the update_bacula_tables
141 script because the create_bacula_tables script automatically creates the new
142 table format. However, if you are using a version of Bacula older than 3.1.9
143 (e.g. 3.0.3) then you need to run the update_bacula_tables script that will
144 be found in the <bacula>/src/cats directory after you run the ./configure
145 command. As mentioned above, before running this script, please backup your
146 catalog database, and when you do running it, be sure shutdown Bacula and be
147 aware that running the script can take some time depending on your database
149 ================================================================
152 ================== Warning !!!!!! ==========================
153 If you upgrade a previous Win32 client installation, you must
154 first stop the File daemon, then uninstall it before attempting
155 the upgrade. If you do not do so, the upgrade will probably
156 fail and you will need to manually find and run the
157 Uninstall.exe file, before you can upgrade to the new version.
158 This is because the file locations are different. If you want
159 to save your previous bacula-fd.conf file, please do so before
161 ================================================================
163 ================== Warning !!!!!! ==========================
164 Due to permissions problems on Windows Vista and later systems,
165 we no longer require SYSTEM or Administrator permissions to
166 access the binaries and configuation files. If you wish
167 to restrict access to these files, please see the New Features
168 section of the manual for how to set access control lists.
169 ================================================================
171 Note, the Win32 Installer no longer installs the Bacula Servers
172 (Director and Storage daemon). See the New Features section of
173 the manual for more details.
175 ============ Documentation improvements needed ==================
177 Note!!!!! The 5.0.0+ documentation has a number of known problems:
179 1. We have reduced the number of manuals, which has fixed many
180 of the broken links found in the old 3.0.x version, but there
181 are still some that need fixing.
183 2. Integration of the 3.0.x features into the main manuals has
186 The documentation will not be completed in the near future due to lack
187 manpower. If you are unhappy with this situation as we are, we suggest
188 you help by submitting patches to the documentation. Thanks.
192 This release includes large number of new features and changes.
193 It should be more or less compatible with previous xx.conf files
194 and File daemons providing that you are not using any of the new
197 Please see the New Features chapter of the new manual, which documents
198 some but not all the new features (we are still working on it):
200 http://www.bacula.org/5.0.x-manuals/en/main/main/New_Features_in_5_0_0.html
202 The ChangeLog has more details.