2 Release Notes for Bacula 5.0.0
4 Bacula code: Total files = 1,081 Total lines = 217,272 (Using SLOCCount)
6 This release includes large number of new features and changes.
8 Important changes since 3.0.3a:
9 -------------------------------
12 1337 1351 1352 1354 1357 1361 1367 1369 1370 1373
13 1376 1391 1403 1409 1420 1422 1427 1428 1431 1450
17 - Problem that locks the Director when the SMTP server wasn't responding
19 - Restore's dir command shows incorrect file sizes
20 - Fix various problems with reload command
21 - Fix problems with conio
22 - Eliminate several deadlocks or potential race conditions from SD
25 - Project 5: Truncate volume after purge
26 - Project 6: File Deduplication using Base Jobs
27 - Project 10: Restore from Multiple Storage Daemons
28 - Project 11: AllowCompression per Device
29 - Project 23: Add Maximum Concurent Jobs for Devices to balance load
31 - Add Accurate Fileset Options to configure accurate detection. Can use
32 checksum verification for example.
33 - Allow FD to keep root read but drop write permission (CAP)
34 - Secure handling of passwords for catalog backup
35 - Add Tab-completion for Bconsole when using Readline
36 - Add Bvfs API to query the catalog without building a memory tree
37 - Add new speed test to btape program
38 - Add new Bat screens (Autochanger content, Job view, Media view, ...)
39 - Windows version of Bat
40 - Added Spanish Bacula translation
41 - New bconsole -u nnn option to have timeout on commands
42 - Allow Migrate, Copy, and Virtual Full to read and write
44 - show disabled -- shows disabled Jobs
45 - Add Pool File and Job retention periods (take precedence over Client)
46 - Many ACL improvements
47 - Level added to FD status Job entry
48 - Allow to turn off/on Block Checksum per device
49 - Set Device Poll interval to 5 minutes -- previously did not poll
50 - Implement lock manager with bad order protection
53 Like always, both the Director and Storage daemon must be upgraded at
56 Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 5.0.0
57 Director and Storage daemons. It should be no need to upgrade older File
60 ============ Documentation improvements needed ==================
62 Note!!!!! The 5.0.0+ documentation needs rather extensive modifications in the
65 1. Missing documentation.
66 2. Correction of links within various manuals -- most fail.
67 3. Integration of the new features into the main documents.
70 The documentation will not be completed in the near future due to lack
71 manpower. If you are unhappy with this situation as we are, we suggest
72 you help by submitting patches to the documentation. Thanks.
75 ================== Warning !!!!!! ==========================
77 New Catalog format in version 5.0.0 (3.1.9 or later)
78 -----------------------------------------------------
80 This release of Bacula uses a new catalog format. We provide a set of
81 scripts that permit to convert a 3.0.x (version 11) catalog to 5.0.0 (version
82 12). The Bacula project rpms distributed on Source Forge will automatically
83 detect the database change and do the upgrade for you. We strongly
84 recommend that you save a copy of your existing database before upgrading
87 The simplest way to upgrade the database assuming you are building from
89 1. Stop any current version of Bacula from running.
90 2. Save a copy of your existing database.
91 3. Configure, build, and install the 5.0.0 version of Bacula
92 Note the new ./configure options in the manuals see the link
93 at the bottom of this file.
94 4. cd <your-scripts-installation-directory>
95 5. ./update_bacula_tables
96 6. If you have multiple catalogs, edit the update_bacula_tables
97 script and put the name of another database, and then
98 execute the script again. Repeat this until all Bacula
99 catalogs have been updated.
100 7. Start the new Bacula. If everything worked, it should
101 not print any error messages.
103 If you start from scratch, you don't need to run the update_bacula_tables
104 script because the create_bacula_tables script automatically creates the new
105 table format. However, if you are using a version of Bacula older than 3.1.9
106 (e.g. 3.0.3) then you need to run the update_bacula_tables script that will
107 be found in the <bacula>/src/cats directory after you run the ./configure
108 command. As mentioned above, before running this script, please backup your
109 catalog database, and when you do running it, be sure shutdown Bacula and be
110 aware that running the script can take some time depending on your database
113 ================================================================
115 This release includes large number of new features and changes.
116 It should be more or less compatible with previous xx.conf files
117 and File daemons providing that you are not using any of the new
120 Please see the New Features chapter of the new manual, which documents
121 some but not all the new features (we are still working on it):
123 http://www.bacula.org/5.0.x-manuals/en/main/main/New_Features_in_5_0_0.html
125 The ChangeLog has more details.