2 Release Notes for Bacula 5.0.1
4 Bacula code: Total files = 1,081 Total lines = 217,272 (Using SLOCCount)
10 - Truncate on Purge rewritten. See New Features section in the manual.
11 - AllowHigherDuplicates disabled. It did not work as documented
13 - New directive "CancelLowerLevelDuplicates" See New Features
14 section in the manual.
17 1466 1467 1468 1481 1486 1488 1497 1499 1494 1448 1476
19 - Fix bug #1488 -- avoid recursion and race conditions in messages.c
20 - Upgrade cats library also to 5.0.0
21 - Fix missing console page in bat
22 - Add bat help files to Window install
23 - Improve Windows upgrade to ensure old FD is shutdown
24 - Fix bug #1481 -- bat consumes all console file descriptors
25 - Backport truncate on purge from 5.1.x
26 - Fix bug #1486 -- bat doesn't show any errors on command-line
27 - Update the bsock error URL
28 - Correct .my.cnf umask in make_catalog_backup.pl
29 - Apply fix for dbcheck use by make_catalog_backup.pl
30 - Fix seg fault in bscan from new comment field
31 - Allow multiple CNs when using TLS
32 - Fix seg fault in SQlite driver
33 - Make shared libs version the same as the Bacula release version
34 - Remove file_index sequential check
35 - Fix #1466 about Bogus pruning message
38 1. The default query.sql file is now, except for some comments, empty.
39 The old file, which we no longer support (it is impossible or difficult to
40 make it work on every backend, and the queries are mostly contributed) can
41 be found in <bacula-source>/examples/sample-query.sql. The sample file is
42 not installed by the Makefiles
44 2. When you install the mtx-changer script, you must also install
45 mtx-changer.conf if it does not exist. This new file (mtx-changer.conf) is
46 required for mtx-changer to work, but it is a user configurable file, so on
47 any update, any existing file should not be overwritten.
49 3. Bat should be built on every platform that is capabable of running Qt.
50 However, the Qt code is changing rather quickly and is not always
51 compatible from version to version. We have built and verified bat on Qt
52 4.3.4. We strongly recommend that you do not build and distribute bat with
53 any other version of Qt unless you personally test it. To build against Qt
54 4.3.4, download the depkgs-qt package from the Bacula Source Forge download
55 location, read the README file and follow the instructions.
57 If you are building for Bacula version 5.0.0, please ensure that you do not
58 have qmake-qt4 loaded on your system. If you do, either remove it or
59 rename it before trying to build bat. If you do not, bat will probably be
60 built using the shared objects on your system. For Bacula 5.0.1 and later,
61 this problem (bug) does not exist.
63 depkgs-qt does not install Qt on your system, nor does it interfere with
64 you having any other version of Qt installed on your system. Once you
65 build bat with depkgs-qt, it should *not* use the Qt shared objects, but
66 rather they will be linked into the program. After fully installing bat
67 (make install), you can run "ldd bat" to see what shared objects it will
68 use. If any Qt shared objects are referenced, something has gone wrong.
70 4. Unless absolutely necessary, we recommend that you do not define any
71 special library environment variables that apply to the ./configure -- for
72 example: LIBDIR=/... ./configure <your-options> is strongly discouraged.
73 Doing so, could potentially cause Bacula to be linked against the wrong
76 5. The Bacula project strongly recommends that you install Bacula into a
77 single directory, with a few minor exceptions such as the MySQL or
78 PostgreSQL databases. Preferrably this should be /opt/bacula. The full
82 # Recommended configure script for Bacula
85 CFLAGS="-g -O2 -Wall" \
87 --sbindir=${prefix}/bin \
88 --sysconfdir=${prefix}/etc \
89 --docdir=${prefix}/html \
90 --htmldir=${prefix}/html \
91 --with-working-dir=${prefix}/working \
92 --with-pid-dir=${prefix}/working \
93 --with-subsys-dir=${prefix}/working \
94 --with-scriptdir=${prefix}/scripts \
95 --with-plugindir=${prefix}/plugins \
96 --libdir=${prefix}/lib \
98 --enable-tray-monitor \
101 --with-dump-email=${email} \
102 --with-job-email=${email} \
103 --with-smtp-host=localhost \
106 Obviously, the email, and some of the minor options (mysql, postgresql,
107 ...) can be changed to suit your distribution, but the directory names
108 defined above are strongly recommended, and over time the default values in
109 the bacula-dir.conf and bacula-sd.conf will reflect these choices.
111 If you have any questions about this or would like a detailed document
112 describing our recommendations including packaging requirements, please
113 send an email to the bacula-devel list.
115 6. Starting with Bacula version 3.0.0 up to Bacula 5.0.0, the shared
116 libraries that Bacula uses by default are named xxx-1.0.0. Starting with
117 Bacula 5.0.1, we are going to name the libraries using the Bacula version.
118 So in Bacula 5.0.1, the libraries will be named xxx-5.0.1. With future
119 versions, the last digit may or may not change when we distribute patch
120 updates (i.e. the last digit of the version changes). This will depend on
121 whether or not we have changed something in the library. Hopefully this
122 new procedure will resolve some of the incompatibility problems between
123 different versions of the shared objects.
125 7. The default build option for bconsole is conio (my own little console
126 routines). I did this because some years ago, readline was very difficult
127 to maintain -- it and where it was found seemed to change on every release.
128 This generated at the time a number of support problems. It seems to me
129 that since then there have been very few problems with readline. As a
130 consequence, I have no problem if you want to make bconsole with readline
131 enabled. It will actually give some very nice new bconsole command
132 completion functionality that Eric has written. Bottom line: feel free to
133 use readline or not as you please.
135 ==========================================================
139 Release Notes for Bacula 5.0.0
142 -----------------------------------------------------------
143 You might be wondering why this release jumps from 3.0.x to
144 5.0.0 thus skipping version 4.0.0. We have done this for
145 several reasons: first, we wanted a way of distinguishing
146 the numbering system for the Bacula System Enterprise version
147 and the Bacula Project version. So, to do so, we have decided
148 that the first number of the Bacula Project version will always
149 be odd, and the first number of the Enterprise version will always
150 be even. Thus the Bacula Project now moves from 3.0.x to 5.0.x.
151 In addition, we want to keep the Bacula Project version larger
152 than the Enterprise version to indicate that the Bacula Project
153 version is more advanced or has more features than the
154 Enterprise version. For memory, the current Enterprise version
155 is 2.6.1, and the next release (in a few months -- before June 2010)
156 will be version 4.0.0.
159 --------------------------------------------------------------
160 Please note the three Warnings below before doing any install or
166 Changes since 3.0.3a (the last Bacula Project release):
167 -------------------------------------------------------
170 1337 1351 1352 1354 1357 1361 1367 1369 1370 1373
171 1376 1391 1403 1409 1420 1422 1427 1428 1431 1450
175 - Problem that locks the Director when the SMTP server wasn't
176 responding to the bsmtp program
177 - Restore's dir command shows incorrect file sizes
178 - Fix various problems with the reload command
179 - Fix problems with conio
180 - Eliminate several deadlocks or potential race conditions from SD
183 - Project 5: Truncate volume after purge
184 - Project 6: File Deduplication using Base Jobs
185 - Project 10: Restore from Multiple Storage Daemons
186 - Project 11: AllowCompression per Device
187 - Project 23: Add Maximum Concurent Jobs for Devices to balance load
189 - Add Accurate Fileset Options to configure accurate detection. Can use
190 checksum verification for example.
191 - Allow FD to keep root read but drop write permission (CAP)
192 - Secure handling of passwords for catalog backup
193 - Add Tab-completion for Bconsole when using Readline
194 - Add Bvfs API to query the catalog without building a memory tree
195 - Add new speed test to btape program
196 - Add new Bat screens (Autochanger content, Job view, Media view, ...)
197 - Windows version of Bat
198 - Added Spanish Bacula translation
199 - New bconsole -u nnn option to have timeout on commands
200 - Allow Migrate, Copy, and Virtual Full to read and write
202 - show disabled -- shows disabled Jobs
203 - Add Pool File and Job retention periods (take precedence over Client)
204 - Many ACL improvements
205 - Level added to FD status Job entry
206 - Allow turning on/off Block Checksum per device
207 - Set Device Poll interval to 5 minutes -- previously did not poll
208 - Implement lock manager with bad order protection
211 As always, both the Director and Storage daemon must be upgraded at
212 the same time, and on any given machine, you must run only one version
213 of Bacula. This means that on the Director and Storage daemon machines,
214 you *must* upgrade your File daemon as well.
216 Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 5.0.0
217 Director and Storage daemons. There should be no need to upgrade older File
218 Daemons immediately. However, we recommend that you do so as soon
219 as is reasonable for your situation.
221 ================== Warning !!!!!! ==========================
223 New Catalog format in version 5.0.0 (3.1.9 or later)
224 -----------------------------------------------------
226 This release of Bacula uses a new catalog format. We provide a set of
227 scripts that permit to convert a 3.0.x (version 11) catalog to 5.0.0 (version
228 12). The Bacula project rpms distributed on Source Forge will automatically
229 detect the database change and do the upgrade for you. We strongly
230 recommend that you save a copy of your existing database before upgrading
233 The simplest way to upgrade the database assuming you are building from
235 1. Stop any current version of Bacula from running.
236 2. Save a copy of your existing database.
237 3. Configure, build, and install the 5.0.0 version of Bacula
238 Note the new ./configure options in the manuals see the link
239 at the bottom of this file.
240 4. cd <your-scripts-installation-directory>
241 5. ./update_bacula_tables
242 6. If you have multiple catalogs, edit the update_bacula_tables
243 script and put the name of another database, and then
244 execute the script again. Repeat this until all Bacula
245 catalogs have been updated.
246 7. Start the new Bacula. If everything worked, it should
247 not print any error messages.
249 If you start from scratch, you don't need to run the update_bacula_tables
250 script because the create_bacula_tables script automatically creates the new
251 table format. However, if you are using a version of Bacula older than 3.1.9
252 (e.g. 3.0.3) then you need to run the update_bacula_tables script that will
253 be found in the <bacula>/src/cats directory after you run the ./configure
254 command. As mentioned above, before running this script, please backup your
255 catalog database, and when you do running it, be sure shutdown Bacula and be
256 aware that running the script can take some time depending on your database
258 ================================================================
261 ================== Warning !!!!!! ==========================
262 If you upgrade a previous Win32 client installation, you must
263 first stop the File daemon, then uninstall it before attempting
264 the upgrade. If you do not do so, the upgrade will probably
265 fail and you will need to manually find and run the
266 Uninstall.exe file, before you can upgrade to the new version.
267 This is because the file locations are different. If you want
268 to save your previous bacula-fd.conf file, please do so before
270 ================================================================
272 ================== Warning !!!!!! ==========================
273 Due to permissions problems on Windows Vista and later systems,
274 we no longer require SYSTEM or Administrator permissions to
275 access the binaries and configuation files. If you wish
276 to restrict access to these files, please see the New Features
277 section of the manual for how to set access control lists.
278 ================================================================
280 Note, the Win32 Installer no longer installs the Bacula Servers
281 (Director and Storage daemon). See the New Features section of
282 the manual for more details.
284 ============ Documentation improvements needed ==================
286 Note!!!!! The 5.0.0+ documentation has a number of known problems:
288 1. We have reduced the number of manuals, which has fixed many
289 of the broken links found in the old 3.0.x version, but there
290 are still some that need fixing.
292 2. Integration of the 3.0.x features into the main manuals has
295 The documentation will not be completed in the near future due to lack
296 manpower. If you are unhappy with this situation as we are, we suggest
297 you help by submitting patches to the documentation. Thanks.
301 This release includes large number of new features and changes.
302 It should be more or less compatible with previous xx.conf files
303 and File daemons providing that you are not using any of the new
306 Please see the New Features chapter of the new manual, which documents
307 some but not all the new features (we are still working on it):
309 http://www.bacula.org/5.0.x-manuals/en/main/main/New_Features_in_5_0_0.html
311 The ChangeLog has more details.