2 Release Notes for Bacula 5.2.2
4 Bacula code: Total files = 1,110 Total lines = 231,439 (Using SLOCCount)
8 The 5.2.2 version is an important bug fix release. It contains also some
9 additions and performance improvements.
11 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
12 If you are upgrading directly from 5.0.3 to this version, please see the
13 important notices below for version 5.2.1, particularly
14 the database upgrade and the difference in packaging the
16 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
20 As always, both the Director and Storage daemon must be upgraded at
23 Older 5.0.x and 3.0.x File Daemons are compatible with the 5.2.2
24 Director and Storage daemons. There should be no need to upgrade older File
29 - Add Systemd configure options
30 - Split messages line by line before sending it to syslog() fix #3325
31 - Fix bvfs_restore on MySQL
32 - Fix #3308 where a SMTP problem can block the director
33 - Change locking scheme of the mountpoint cache.
34 - Enhance mountcache with rescan option after interval.
35 - Add %D option to edit_job_code, simplify callbacks on director side
36 - Move Zdeflate and Zinflate to seperate file.
37 - Put libraries in the correct order for non shared libs.
38 - Remove last traces of @SQL_BINDIR@ and @DB_TYPE@
40 - Move batch insert detection into db.m4
41 - bat: try to fix offset button problem when clicking too much on previous
42 - bvfs: Use single transaction for each job during update
43 - Add missing bwild & bregex man8 pages
44 - Fix compilation issue of wx-console #1778
45 - bvfs: fix filter for pattern= bvfs parameter
46 - Improve speed of BVFS with SQLite, Thanks to J.Starek
47 - bvfs: add clear_cache function
48 - bvfs: Handle windows drive when building path hierarchy
50 Closed Bugs Since 5.2.1
51 -----------------------
55 ================================================================
59 The 5.2.1 version is a major release since the last version 5.0.3.
60 It includes well over 299,387 lines of changes made by 20 contributors,
61 lots of bug fixes (see below), 1,851 software commits,and a
62 number of important new features:
64 Version 5.2.0 was short lived, because Marco (thanks) found
65 a number of last minute bugs. So the first official release of 5.2
70 As always, both the Director and Storage daemon must be upgraded at
73 Older 5.0.x and 3.0.x File Daemons are compatible with the 5.2.1
74 Director and Storage daemons. There should be no need to upgrade older File
82 - Changes in Bvfs (Bacula Virtual FileSystem)
83 - Changes in the Pruning Algorithm
84 - Ability to Verify any specified Job
85 - Additions to RunScript variables
86 - Additions to the Plugin API
89 - Class Based Database Backend Drivers
90 - Hash List Enhancements
92 Some of the above are described below; all the above are
93 described in more detail in the New Features chapter of the
96 Closed Bugs since 5.0.3:
98 1389 1444 1448 1466 1467 1468 1476 1481 1486 1488 1493 1494 1497 1499 1501
99 1502 1504 1509 1511 1513 1516 1524 1526 1527 1532 1536 1538 1541 1542 1549
100 1551 1553 1554 1558 1559 1560 1564 1567 1568 1569 1571 1574 1577 1581 1582
101 1584 1587 1594 1595 1600 1601 1602 1603 1604 1606 1608 1610 1612 1623 1624
102 1633 1643 1648 1655 1661 1664 1666 1669 1672 1675 1684 1685 1695 1696 1699
103 1700 1703 1735 1741 1749 1751 1761 1762 1764 1768 1770 1771 2710
105 Note on bug 1612 where Bacula does not save a checksum for hard links during
106 full backup, but expects one during accurate differential backups. You need
107 a Full backup with the 5.2.x code to have these checksums in the Catalog.
108 Doing Incr/Diff over a 5.0.x Full backup will still display lot of errors.
112 ================== Warning !!!!!! ==========================
114 The new pruning algorithm will not allow pruning of jobs that are essential to
115 restore since the last Full backup. This is, of course, correct and desirable,
116 but it is different from older Bacula versions that could inappropriately
117 prune jobs. Pruning of volumes is not affected.
121 To build Bat, you need Qt4 version 4.6.2. If you build with any other
122 version it is likely not to work. If you do not have version 4.6.2, on
123 your system, you can download the Bacula depkgs_qt version 16Dec10.
125 Packaging the SQL backend:
126 --------------------------
127 The main Bacula Director code is independent of the SQL backend
128 in this version. This means that the Bacula Director can be packaged
129 by itself, then each of the different SQL backends supported can
130 be packaged separately. It is possible to build all the DB backends
133 - configure can be run with multiple database configure options.
138 Order of testing for database is
143 Each configured backend generates a libbaccats-<backend_name>-<version>.so
144 A dummy catalog library is created named libbaccats-version.so
146 At configure time the first detected backend is used as the so called default
147 backend and at install time the dummy libbaccats-<version>.so is replaced with
148 the default backend type.
150 If you configure all 3 backends you get 3 backend libraries and the postgresql
151 gets installed as the default. When you want to switch the default you can
152 copy one of the 3 backend libraries over the libbaccats-<version>.so e.g.
154 cp libbaccats-postgresql-<version>.so libbaccats-<version>.so
156 And update the default backend in the following files:
158 create_bacula_database
161 grant_bacula_privileges
166 New Catalog format in version 5.2.0 and greater
167 -----------------------------------------------
168 This release of Bacula uses a new catalog format. We provide a set of
169 scripts that permit to convert a 5.0.x (version 12) catalog to 5.2.1 (version
170 14). The Bacula project rpm spec files have been modified to
171 detect the database change and do the upgrade for you. We strongly
172 recommend that you save a copy of your existing database before upgrading
175 The simplest way to upgrade the database assuming you are building from
176 source (i.e. manually):
177 1. Stop any current version of Bacula from running.
178 2. Save a copy of your existing database.
179 3. Configure, build, and install the 5.2.1 version of Bacula
180 Note the new ./configure options in the manuals see the link
181 at the bottom of this file.
182 4. cd <your-scripts-installation-directory>
183 5. ./update_bacula_tables
184 6. If you have multiple catalogs, edit the update_bacula_tables
185 script and put the name of another database, and then
186 execute the script again. Repeat this until all Bacula
187 catalogs have been updated.
188 7. Start the new Bacula. If everything worked, it should
189 not print any error messages.
191 If you start from scratch, you don't need to run the update_bacula_tables
192 script because the create_bacula_tables script automatically creates the new
193 table format. However, if you are using a version of Bacula older than 5.0.0
194 (e.g. 3.0.3) then you need to run the update_bacula_tables script that will
195 be found in the <bacula>/src/cats directory after you run the ./configure
196 command. As mentioned above, before running this script, please backup your
197 catalog database, and when you do running it, be sure shutdown Bacula and be
198 aware that running the script can take some time depending on your database
201 ================================================================
205 Speed and Memory Usage Enhancements:
206 - Implement LZO compression algorithm (need lzo2 headers to activate this option)
207 - New Pruning algoritm -- safer and faster
208 - Use of PostgreSQL cursor when doing large queries, should reduce the
209 memory usage during restore and accurate backups.
210 - limit command in some list commands
211 - Bacula Virtual File System for fast catalog access
212 - Faster crc32 algorithm
214 Security Enhancements:
215 - Additional security against injection of illegal characters
216 - Fix possible fnmatch problem
218 Features Enhancements:
219 - Improvements in ACL and xattr handling on additional platforms:
220 AIX, Darwind, FreeBSD, HPUX, IRIX, Solaris, Tru64
221 - Tray monitor for Windows
222 - New SQL backend and ./configure that permits building multiple catalog
223 backends in one build, and has the main Bacula core code totally independent
224 of the SQL backend, which should simplify packaging (only the
225 libbacsql.so/dll needs to be changed to switch from one database backend
226 to another (e.g. MySQL to PostgreSQL).
227 - Indent lsmark during restore
228 - Disable batch insert config item
229 - Director selection option in bconsole
230 - restorejob command in bconsole
231 - Many additional features for bat such as "brestore" panel
232 - The old bat version browser has been turned off since it does not
233 work correctly and the brestore panel provides the same functionality
234 - Improved hash table for hard links
235 - Additional script variable editing such as %b (JobBytes), %F (JobFiles)
236 and %h (Client Address)
239 - Includes better handling for Windows repares points, mount points, and
241 - New database format
242 - Many new plugin API features
243 - Improved memory handling for restores
244 - Significant stability enhancements to bat
245 - xattr/ACL restore failure are now printed as Warning
246 - A few path name length limits in Windows have been removed.
249 ===========================================================================
251 The 5.0.3 version is significant bug fix update to version 5.0.2.
252 It includes new code and some new features.
253 There is no database change since prior versions of 5.0.
255 Note, if you are running 5.0.0, read the 5.0.1 and 5.0.2 release notes below in
256 the 5.0.1 release section.
261 As always, both the Director and Storage daemon must be upgraded at
264 Older 5.0.x and 3.0.x File Daemons are compatible with the 5.0.3
265 Director and Storage daemons. There should be no need to upgrade older File
268 Changes and New Features:
269 - If a VSS (Windows) snapshot fails, the whole Job is failed, previously
270 it printed a warning message and continued.
271 - New editing codes %b = Job Bytes and %f = Job Files for runscripts
272 - Any non-Bacula project plugins (i.e. third party plugins)
273 must be upgraded to specify AGPLv3 in place of the GPLv2 used previously
274 for the PLUGIN_LICENSE.
275 - The bat Media page text columns can be sorted by clicking on the column.
276 - If possible, the SD will automatically update the catalog Volume size if
277 it does not match the Volume size. The mismatch between the Volume sizes
278 typically occurs when the FD has a comm line drop or the FD crashes.
282 1538 1554 1564 1567 1568 1569 1571 1577 1581 1582 1587 1594 1595 1606 1610
284 - Change license from GPLv2 to AGPLv3
285 - Make Win32 no filesystem change more explicit
286 - Backport Branch-4.0 release to Branch-5.0
287 - Massive backport from Branch-5.1 to Branch-5.0
288 - Fix postgresql catalog creation when version is not on the first line
289 - Fix bug #1610 handle empty xattr values on Linux and xBSD.
290 - Garbage collect memory pool at end of job and before sm_dump
291 - Add xattr seg fault protection suggested by Marco for bug #1610
292 - Add archlinux to os.m4
293 - More fixes for 32/64 bit problems in smartall
294 - Fix 32/64 bit problem in smartalloc dump routine
295 - Fix bad copy/paste in commit c88dccb88 prably a seg fault
296 - Add .dump and .exit commands for daemons
297 - Make SD automatically fix the Volume size in the Catalog when out of sync
298 - Use Pmsg in smartall.c rather than printf for tracing Windows
299 - Up maximum block size to 20M
300 - Fix for TLS bugs #1568 and #1599
301 - Improve comm line error handling for TLS, may fix bug #1568 and #1599
302 - Fix problem when sending Cancel event to plugin
303 - Convert all Jmsg on the watchdog thread to Qmsg
304 - Fix SD crash due to mismatched lock/unlock in error condition
305 - Fix bug #1587 if you have clients with different catalogs configured, both
306 catalogs contains all clients after a reload or restart of the dir
307 - Fix bug #1577 During migration: ERROR in block.c:950 Failed ASSERT: dev->is_open()
308 by moving and commenting out the ASSERT()
309 - Skip HB kill in FD if HB thread terminated
310 - Fix crash from unequal volume_lock/unlock calls
311 - New prunning algorithm -- should be more accurate
312 - Save any dumps during regression to dumps directory
313 - Fix crash from rw_lock/unlock miss match
314 - Attempt to fix duplicate job kill seg fault
315 - Replace pthread_kill by my_thread_send_signal() in jcr.c
316 - fix #1595 about batch mode detection problem for postgresql with non standard
318 - Fix #1594 about prune copy jobs
319 - Apply literal string fix in printf submitted by Luca Berra
320 - Fix bug #1582 Restore from multiple storage daemons breaks subsequent backups
321 - Fix segfault on "cancel jobid=" command
322 - Fix bug #1554 Windows installer doesn't honor /S flag
323 - Remove pool zap code that breaks 2drive-concurrent-test
324 - Fix #1571 and install libraries with 755 perms
325 - Fix bug #1581 ASSERTs in src/dird/jobq.c can never trigger
326 - Fix problem with BaseJob and Accurate FileSet options on client side
327 - Fix for bug #1569 deadlock/crash in Dir
328 - Fix segfault when loading Plugins
329 - Fix #1567 about display of long volume names truncated during restore
330 - Added new bacula-libs package.
331 - Fix bug #1538 Start Scripts return incorrect value
332 - Fix bug #1564 init scripts not LSB compliant
334 See ChangeLog for more details.
336 =============================================================================
339 ============= Release 5.0.2 ========================
345 1502 1511 1517 1524 1527 1532 1536 1541 1549 1551 1553 1559 1560
347 - Probable fix for SD crash bug #1553
348 - Fix #1559 problem when restoring pruned jobs with a regexp
349 - Fix for bug #1560 bcopy cannot find Volume
350 - Fix cancel crash bug #1551
351 - Check if sql backend is thread-safe
352 - Correct Pool display in SD status. Fixes bug #1541
353 - Fix cancel crash reported by Stephen Thompson
354 - Rewind on close to fix #1549
355 - Remove closelog() in bpipe fixes bug #1536
356 - Fix #1517 about missing Base level in .level command
357 - Replace ASSERT in block.c with fail Job
358 - Fix database locking calling db_lock and returning from function without
360 - Add missing db_unlock to bvfs_update_cache.
361 - Fix #1532 about permission on binaries
362 - Fix #1527 about deadlock during migration
363 - Another fix for OpenSSLv1
364 - Add -lrt to Solaris links
365 - Fix tls.c for OpenSSLv1
366 - Fix #1511 when trying to insert more than 50.000 directories in bvfs
367 - Fix plugin load not to stop if one plugin bad -- pointed out by James
368 - Remove --without-qwt from configure statement.
369 - Second correct fix to bug #1524 verify fails after adding or removing files
370 - Fix bug #1524 verify fails after adding or removing files
371 - Apply fix suggested by Andreas in bug #1502 for mediaview column sort problem
372 - Fix OpenSSL 1.x problem in crypto.c on Fedora 12
373 - Display AllowCompress warning message only if compression used in FileSet
375 =============================================================================
378 ============= Release 5.0.1 ========================
380 !!!!!!!!!!!!!!! NOTE FOR 5.0.0 USERS !!!!!!!!!!!!!!!!!!!!
381 The Allow Duplicate Jobs directive has been significantly
382 reworked, and the default value has changed. See below.
384 Truncate On Purge has been totally rewritten. See the new
385 features section of the manual.
387 When Volume Poll Interval is set in the SD DEVICE configuration,
388 (default 5 mins), after a certain number of polling tries (approx
389 10) polling will stop and the operator will be asked to
390 resolve the problem. Previously there was no limit, and an
391 error message could be produced at each poll attempt.
392 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
396 - We believe that we have resolved most of the problems
397 concerning canceled or failed jobs being "stuck" in the
398 Director. There is one outstanding problem in the SD when
399 canceling jobs that we will fix in the next major release.
400 If you see jobs that seem to be stuck, in general issuing
401 a cancel command in bconsole should now make them go away.
404 - The default for "Allow Duplicate Jobs" has been changed from
405 no to yes. If you use this directive, please check your
406 conf file, and note the next two items !!!!!!!!!!!!!!!!!!!
407 - AllowHigherDuplicates disabled. It did not work as documented
409 - New directive "CancelLowerLevelDuplicates" See New Features
410 section in the manual.
411 - Truncate on Purge rewritten. See New Features section in the manual.
414 1448 1466 1467 1468 1476 1481 1486 1488 1494 1497
415 1499 1501 1505 1509 1513
417 - Ensure SD asks for help when looping even if poll set. Fixes bug #1513.
418 - Fix three-pool regress bug
419 - Modify bacula.spec fixes bug #1505
420 - This version fixes an issue where the console window would start out
421 docked. It is fixed by initiating the variables in the Pages class wi
423 - Fix make_catalog_backup.pl fails when catalog db is on other host
424 - Apply MacOSX installer patch from bug #1509
425 - Apply fix to previous fix of Copy problem. Fix proposed by reporter o
427 - Fix bug #1501 -t does not print errors
428 - Apply SQLite3 update fix from bug #1497
429 - Apply bashism fix for diskchanger.in script from bug #1499
430 - Apply rpm fix for Sci Linux from bug #1494
431 - Take most recent Ukranian po from bug #1448
432 - Probable fix for Copy/Migration bug #1476
433 - Fix bug #1488 -- avoid recursion and race conditions in messages.c
434 - Upgrade cats library also to 5.0.0
435 - Fix missing console page in bat
436 - Add bat help files to Window install
437 - Improve Windows upgrade to ensure old FD is shutdown
438 - Fix bug #1481 -- bat consumes all console file descriptors
439 - Backport truncate on purge from 5.1.x
440 - Fix bug #1486 -- bat doesn't show any errors on command-line
441 - Update the bsock error URL
442 - Correct .my.cnf umask in make_catalog_backup.pl
443 - Apply fix for dbcheck use by make_catalog_backup.pl
444 - Fix seg fault in bscan from new comment field
445 - Allow multiple CNs when using TLS
446 - Fix seg fault in SQlite driver
447 - Make shared libs version the same as the Bacula release version
448 - Remove file_index sequential check
449 - Fix #1466 about Bogus pruning message
452 1. The default query.sql file is now, except for some comments, empty.
453 The old file, which we no longer support (it is impossible or difficult to
454 make it work on every backend, and the queries are mostly contributed) can
455 be found in <bacula-source>/examples/sample-query.sql. The sample file is
456 not installed by the Makefiles
458 2. When you install the mtx-changer script, you must also install
459 mtx-changer.conf if it does not exist. This new file (mtx-changer.conf) is
460 required for mtx-changer to work, but it is a user configurable file, so on
461 any update, any existing file should not be overwritten.
463 3. Bat should be built on every platform that is capabable of running Qt.
464 However, the Qt code is changing rather quickly and is not always
465 compatible from version to version. We have built and verified bat on Qt
466 4.3.4. We strongly recommend that you do not build and distribute bat with
467 any other version of Qt unless you personally test it. To build against Qt
468 4.3.4, download the depkgs-qt package from the Bacula Source Forge download
469 location, read the README file and follow the instructions.
471 If you are building for Bacula version 5.0.0, please ensure that you do not
472 have qmake-qt4 loaded on your system. If you do, either remove it or
473 rename it before trying to build bat. If you do not, bat will probably be
474 built using the shared objects on your system. For Bacula 5.0.1 and later,
475 this problem (bug) does not exist.
477 depkgs-qt does not install Qt on your system, nor does it interfere with
478 you having any other version of Qt installed on your system. Once you
479 build bat with depkgs-qt, it should *not* use the Qt shared objects, but
480 rather they will be linked into the program. After fully installing bat
481 (make install), you can run "ldd bat" to see what shared objects it will
482 use. If any Qt shared objects are referenced, something has gone wrong.
484 4. Unless absolutely necessary, we recommend that you do not define any
485 special library environment variables that apply to the ./configure -- for
486 example: LIBDIR=/... ./configure <your-options> is strongly discouraged.
487 Doing so, could potentially cause Bacula to be linked against the wrong
490 5. The Bacula project strongly recommends that you install Bacula into a
491 single directory, with a few minor exceptions such as the MySQL or
492 PostgreSQL databases. Preferrably this should be /opt/bacula. The full
496 # Recommended configure script for Bacula
499 CFLAGS="-g -O2 -Wall" \
501 --sbindir=${prefix}/bin \
502 --sysconfdir=${prefix}/etc \
503 --docdir=${prefix}/html \
504 --htmldir=${prefix}/html \
505 --with-working-dir=${prefix}/working \
506 --with-pid-dir=${prefix}/working \
507 --with-subsys-dir=${prefix}/working \
508 --with-scriptdir=${prefix}/scripts \
509 --with-plugindir=${prefix}/plugins \
510 --libdir=${prefix}/lib \
511 --enable-smartalloc \
512 --enable-tray-monitor \
515 --with-dump-email=${email} \
516 --with-job-email=${email} \
517 --with-smtp-host=localhost \
520 Obviously, the email, and some of the minor options (mysql, postgresql,
521 ...) can be changed to suit your distribution, but the directory names
522 defined above are strongly recommended, and over time the default values in
523 the bacula-dir.conf and bacula-sd.conf will reflect these choices.
525 If you have any questions about this or would like a detailed document
526 describing our recommendations including packaging requirements, please
527 send an email to the bacula-devel list.
529 6. Starting with Bacula version 3.0.0 up to Bacula 5.0.0, the shared
530 libraries that Bacula uses by default are named xxx-1.0.0. Starting with
531 Bacula 5.0.1, we are going to name the libraries using the Bacula version.
532 So in Bacula 5.0.1, the libraries will be named xxx-5.0.1. With future
533 versions, the last digit may or may not change when we distribute patch
534 updates (i.e. the last digit of the version changes). This will depend on
535 whether or not we have changed something in the library. Hopefully this
536 new procedure will resolve some of the incompatibility problems between
537 different versions of the shared objects.
539 7. The default build option for bconsole is conio (my own little console
540 routines). I did this because some years ago, readline was very difficult
541 to maintain -- it and where it was found seemed to change on every release.
542 This generated at the time a number of support problems. It seems to me
543 that since then there have been very few problems with readline. As a
544 consequence, I have no problem if you want to make bconsole with readline
545 enabled. It will actually give some very nice new bconsole command
546 completion functionality that Eric has written. Bottom line: feel free to
547 use readline or not as you please.
549 ==========================================================
553 Release Notes for Bacula 5.0.0
556 -----------------------------------------------------------
557 You might be wondering why this release jumps from 3.0.x to
558 5.0.0 thus skipping version 4.0.0. We have done this for
559 several reasons: first, we wanted a way of distinguishing
560 the numbering system for the Bacula System Enterprise version
561 and the Bacula Project version. So, to do so, we have decided
562 that the first number of the Bacula Project version will always
563 be odd, and the first number of the Enterprise version will always
564 be even. Thus the Bacula Project now moves from 3.0.x to 5.0.x.
565 In addition, we want to keep the Bacula Project version larger
566 than the Enterprise version to indicate that the Bacula Project
567 version is more advanced or has more features than the
568 Enterprise version. For memory, the current Enterprise version
569 is 2.6.1, and the next release (in a few months -- before June 2010)
570 will be version 4.0.0.
573 --------------------------------------------------------------
574 Please note the three Warnings below before doing any install or
578 Changes since 3.0.3a (the last Bacula Project release):
579 -------------------------------------------------------
582 1337 1351 1352 1354 1357 1361 1367 1369 1370 1373
583 1376 1391 1403 1409 1420 1422 1427 1428 1431 1450
587 - Problem that locks the Director when the SMTP server wasn't
588 responding to the bsmtp program
589 - Restore's dir command shows incorrect file sizes
590 - Fix various problems with the reload command
591 - Fix problems with conio
592 - Eliminate several deadlocks or potential race conditions from SD
595 - Project 5: Truncate volume after purge
596 - Project 6: File Deduplication using Base Jobs
597 - Project 10: Restore from Multiple Storage Daemons
598 - Project 11: AllowCompression per Device
599 - Project 23: Add Maximum Concurent Jobs for Devices to balance load
601 - Add Accurate Fileset Options to configure accurate detection. Can use
602 checksum verification for example.
603 - Allow FD to keep root read but drop write permission (CAP)
604 - Secure handling of passwords for catalog backup
605 - Add Tab-completion for Bconsole when using Readline
606 - Add Bvfs API to query the catalog without building a memory tree
607 - Add new speed test to btape program
608 - Add new Bat screens (Autochanger content, Job view, Media view, ...)
609 - Windows version of Bat
610 - Added Spanish Bacula translation
611 - New bconsole -u nnn option to have timeout on commands
612 - Allow Migrate, Copy, and Virtual Full to read and write
614 - show disabled -- shows disabled Jobs
615 - Add Pool File and Job retention periods (take precedence over Client)
616 - Many ACL improvements
617 - Level added to FD status Job entry
618 - Allow turning on/off Block Checksum per device
619 - Set Device Poll interval to 5 minutes -- previously did not poll
620 - Implement lock manager with bad order protection
623 As always, both the Director and Storage daemon must be upgraded at
624 the same time, and on any given machine, you must run only one version
625 of Bacula. This means that on the Director and Storage daemon machines,
626 you *must* upgrade your File daemon as well.
628 Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 5.0.0
629 Director and Storage daemons. There should be no need to upgrade older File
630 Daemons immediately. However, we recommend that you do so as soon
631 as is reasonable for your situation.
633 ================== Warning !!!!!! ==========================
635 New Catalog format in version 5.0.0 (3.1.9 or later)
636 -----------------------------------------------------
638 This release of Bacula uses a new catalog format. We provide a set of
639 scripts that permit to convert a 3.0.x (version 11) catalog to 5.0.0 (version
640 12). The Bacula project rpms distributed on Source Forge will automatically
641 detect the database change and do the upgrade for you. We strongly
642 recommend that you save a copy of your existing database before upgrading
645 The simplest way to upgrade the database assuming you are building from
647 1. Stop any current version of Bacula from running.
648 2. Save a copy of your existing database.
649 3. Configure, build, and install the 5.0.0 version of Bacula
650 Note the new ./configure options in the manuals see the link
651 at the bottom of this file.
652 4. cd <your-scripts-installation-directory>
653 5. ./update_bacula_tables
654 6. If you have multiple catalogs, edit the update_bacula_tables
655 script and put the name of another database, and then
656 execute the script again. Repeat this until all Bacula
657 catalogs have been updated.
658 7. Start the new Bacula. If everything worked, it should
659 not print any error messages.
661 If you start from scratch, you don't need to run the update_bacula_tables
662 script because the create_bacula_tables script automatically creates the new
663 table format. However, if you are using a version of Bacula older than 3.1.9
664 (e.g. 3.0.3) then you need to run the update_bacula_tables script that will
665 be found in the <bacula>/src/cats directory after you run the ./configure
666 command. As mentioned above, before running this script, please backup your
667 catalog database, and when you do running it, be sure shutdown Bacula and be
668 aware that running the script can take some time depending on your database
670 ================================================================
673 ================== Warning !!!!!! ==========================
674 If you upgrade a previous Win32 client installation, you must
675 first stop the File daemon, then uninstall it before attempting
676 the upgrade. If you do not do so, the upgrade will probably
677 fail and you will need to manually find and run the
678 Uninstall.exe file, before you can upgrade to the new version.
679 This is because the file locations are different. If you want
680 to save your previous bacula-fd.conf file, please do so before
682 ================================================================
684 ================== Warning !!!!!! ==========================
685 Due to permissions problems on Windows Vista and later systems,
686 we no longer require SYSTEM or Administrator permissions to
687 access the binaries and configuation files. If you wish
688 to restrict access to these files, please see the New Features
689 section of the manual for how to set access control lists.
690 ================================================================
692 Note, the Win32 Installer no longer installs the Bacula Servers
693 (Director and Storage daemon). See the New Features section of
694 the manual for more details.
696 ============ Documentation improvements needed ==================
698 Note!!!!! The 5.0.0+ documentation has a number of known problems:
700 1. We have reduced the number of manuals, which has fixed many
701 of the broken links found in the old 3.0.x version, but there
702 are still some that need fixing.
704 2. Integration of the 3.0.x features into the main manuals has
707 The documentation will not be completed in the near future due to lack
708 manpower. If you are unhappy with this situation as we are, we suggest
709 you help by submitting patches to the documentation. Thanks.
713 This release includes large number of new features and changes.
714 It should be more or less compatible with previous xx.conf files
715 and File daemons providing that you are not using any of the new
718 Please see the New Features chapter of the new manual, which documents
719 some but not all the new features (we are still working on it):
721 http://www.bacula.org/5.0.x-manuals/en/main/main/New_Features_in_5_0_1.html
723 The ChangeLog has more details.