-Kern;;;27 Jan 2008;;10:30
+Kern;;;01 August 2010 at 17:23 CET
+Welcome to our new bacula.org server
+
+This is our new bacula.org server, graciously provided
+by UKFast. Our previous server, also hosted by UKFast, was
+getting to be a bit old, so they furnished us a new one,
+and we are very pleased.
+
+;;;;
+Kern;;;28 April 2010 at 19:15 CET
+Eric has released Bacula Version 5.0.2 to Source Forge
+
+This 5.0.2 version is primarily a important bug fix update to version 5.0.1.
+
+Note, if you are running 5.0.0, read the 5.0.1 release notes below.
+ Important!!!
+
+Compatibility:
+--------------
+ As always, both the Director and Storage daemon must be upgraded at
+ the same time.
+
+ Older 5.0.x and 3.0.x File Daemons are compatible with the 5.0.2
+ Director and Storage daemons. There should be no need to upgrade older File
+ Daemons.
+
+Changes since 5.0.1
+-------------------
+
+Bug fixes
+1502 1511 1517 1524 1527 1532 1536 1541 1549 1551 1553 1559 1560
+
+- Probable fix for SD crash bug #1553
+- Fix #1559 problem when restoring pruned jobs with a regexp
+- Fix for bug #1560 bcopy cannot find Volume
+- Fix cancel crash bug #1551
+- Check if sql backend is thread-safe
+- Correct Pool display in SD status. Fixes bug #1541
+- Fix cancel crash reported by Stephen Thompson
+- Rewind on close to fix #1549
+- Remove closelog() in bpipe fixes bug #1536
+- Fix #1517 about missing Base level in .level command
+- Replace ASSERT in block.c with fail Job
+- Fix database locking calling db_lock and returning from function without
+ calling db_unlock.
+- Add missing db_unlock to bvfs_update_cache.
+- Fix #1532 about permission on binaries
+- Fix #1527 about deadlock during migration
+- Another fix for OpenSSLv1
+- Add -lrt to Solaris links
+- Fix tls.c for OpenSSLv1
+- Fix #1511 when trying to insert more than 50.000 directories in bvfs
+- Fix plugin load not to stop if one plugin bad -- pointed out by James
+- Remove --without-qwt from configure statement.
+- Second correct fix to bug #1524 verify fails after adding or removing files
+- Fix bug #1524 verify fails after adding or removing files
+- Apply fix suggested by Andreas in bug #1502 for mediaview column sort problem
+- Fix OpenSSL 1.x problem in crypto.c on Fedora 12
+- Display AllowCompress warning message only if compression used in FileSet
+
+;;;;
+
+Kern;;;25 February 2010 at 15:35
+Bacula Version 5.0.1 has been released to Source Forge
+
+Bacula version 5.0.1 source code and Windows (32/64 bit) binaries have been
+released to Source Forge (thanks Eric).
+
+This is a major bug fix release including a few directives that have been
+rewritten, one new directive, and some different directive behavior (see the
+release notes below). As is usual for a patch release (last digit changes by
+one), this version is compatible with the 5.0.0 database and with prior
+clients. However, you *must* upgrade all components that are on any one
+machine (that is you must upgrade your Director, Storage daemon, and File
+daemon at the same time, if they reside on the same machine).
+
+Note, Bacula does not normally uninstall previous versions, and we have
+changed the shared object naming convention, so you might want to first save
+your configuration files then uninstall the old Bacula using the old Bacula
+uninstall prior to installing the new one. If you do not, it should not be
+serious, but you may be left with some older Bacula shared objects that are
+not used and hence wasting a small amount of disk space.
+
+If you are upgrading from version 3.0.x or prior, please see the full release
+notes as you must do a database upgrade. When updating from 5.0.0 to this
+release there is no database upgrade needed.
+
+Scott has made a number of changes and improvements in the rpm packaging over
+the past few weeks since version 5.0.0 was released, so he will probably be
+releasing the 5.0.1 rpms quite soon.
+
+Thanks for using Bacula :-)
+
+Best regards,
+
+Kern
+
+============= Performance Note ==================
+
+Some of you have encountered performance problems with your
+database (mainly with MySQL) with Bacula version 5.0.0. This is
+mainly because we've changed the SQL query used for restore,
+accurate jobs and base jobs. We have extensively tested this
+change, and though it should be a little bit slower than the previous
+versions, on a well configured database it should run
+extremely well.
+
+We strongly recommend to avoid the temptation to add new indexes.
+In general, these will cause very significant performance
+problems in other areas. A better approch is to carefully check
+that all your MySQL memory configuation parameters are are
+suitable for the size of your installation. If you backup
+millions of files, you need to adapt the database memory
+configuration parameters concerning sorting, joining and global
+memory. By default, sort and join parameters are very small
+(sometimes 8Kb), and having sufficient memory specified by those
+parameters is extremely important to run fast.
+
+If adjusting your MySQL memory configuration values does not
+solve your problem, you can also consider switching to
+PostgreSQL, which performs much better with Bacula on big
+installations (many millions of files per Job). However for
+large installations, you will also need to adjust the default
+PostgreSQL memory configuration parameters.
+
+==========================================
+
+
+ Release Notes for Bacula 5.0.1
+
+ Bacula code: Total files = 1,081 Total lines = 217,272 (Using SLOCCount)
+
+!!!!!!!!!!!!!!!!!!!!! NOTE !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+The Allow Duplicate Jobs directive has been significantly
+reworked, and the default value has changed. See below.
+
+Truncate On Purge has been totally rewritten. See the new
+features section of the manual.
+
+When Volume Poll Interval is set in the SD DEVICE configuration,
+(default 5 mins), after a certain number of polling tries (approx
+10) polling will stop and the operator will be asked to
+resolve the problem. Previously there was no limit, and an
+error message could be produced at each poll attempt.
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+Changes since 5.0.0
+-------------------
+- We believe that we have resolved most of the problems
+ concerning canceled or failed jobs being "stuck" in the
+ Director. There is one outstanding problem in the SD when
+ canceling jobs that we will fix in the next major release.
+ If you see jobs that seem to be stuck, in general issuing
+ a cancel command in bconsole should now make them go away.
+
+Directives:
+- The default for "Allow Duplicate Jobs" has been changed from
+ no to yes. If you use this directive, please check your
+ conf file, and note the next two items !!!!!!!!!!!!!!!!!!!
+- AllowHigherDuplicates disabled. It did not work as documented
+ and was confusing.
+- New directive "CancelLowerLevelDuplicates" See New Features
+ section in the manual.
+- Truncate on Purge rewritten. See New Features section in the manual.
+
+Bug fixes:
+1448 1466 1467 1468 1476 1481 1486 1488 1494 1497
+1499 1501 1505 1509 1513
+
+- Ensure SD asks for help when looping even if poll set. Fixes bug #1513.
+- Fix three-pool regress bug
+- Modify bacula.spec fixes bug #1505
+- This version fixes an issue where the console window would start out
+ docked. It is fixed by initiating the variables in the Pages class wi
+ constructor.
+- Fix make_catalog_backup.pl fails when catalog db is on other host
+- Apply MacOSX installer patch from bug #1509
+- Apply fix to previous fix of Copy problem. Fix proposed by reporter o
+ #1476
+- Fix bug #1501 -t does not print errors
+- Apply SQLite3 update fix from bug #1497
+- Apply bashism fix for diskchanger.in script from bug #1499
+- Apply rpm fix for Sci Linux from bug #1494
+- Take most recent Ukranian po from bug #1448
+- Probable fix for Copy/Migration bug #1476
+- Fix bug #1488 -- avoid recursion and race conditions in messages.c
+- Upgrade cats library also to 5.0.0
+- Fix missing console page in bat
+- Add bat help files to Window install
+- Improve Windows upgrade to ensure old FD is shutdown
+- Fix bug #1481 -- bat consumes all console file descriptors
+- Backport truncate on purge from 5.1.x
+- Fix bug #1486 -- bat doesn't show any errors on command-line
+- Update the bsock error URL
+- Correct .my.cnf umask in make_catalog_backup.pl
+- Apply fix for dbcheck use by make_catalog_backup.pl
+- Fix seg fault in bscan from new comment field
+- Allow multiple CNs when using TLS
+- Fix seg fault in SQlite driver
+- Make shared libs version the same as the Bacula release version
+- Remove file_index sequential check
+- Fix #1466 about Bogus pruning message
+
+For Packagers:
+1. The default query.sql file is now, except for some comments, empty.
+The old file, which we no longer support (it is impossible or difficult to
+make it work on every backend, and the queries are mostly contributed) can
+be found in <bacula-source>/examples/sample-query.sql. The sample file is
+not installed by the Makefiles
+
+2. When you install the mtx-changer script, you must also install
+mtx-changer.conf if it does not exist. This new file (mtx-changer.conf) is
+required for mtx-changer to work, but it is a user configurable file, so on
+any update, any existing file should not be overwritten.
+
+3. Bat should be built on every platform that is capabable of running Qt.
+However, the Qt code is changing rather quickly and is not always
+compatible from version to version. We have built and verified bat on Qt
+4.3.4. We strongly recommend that you do not build and distribute bat with
+any other version of Qt unless you personally test it. To build against Qt
+4.3.4, download the depkgs-qt package from the Bacula Source Forge download
+location, read the README file and follow the instructions.
+
+If you are building for Bacula version 5.0.0, please ensure that you do not
+have qmake-qt4 loaded on your system. If you do, either remove it or
+rename it before trying to build bat. If you do not, bat will probably be
+built using the shared objects on your system. For Bacula 5.0.1 and later,
+this problem (bug) does not exist.
+
+depkgs-qt does not install Qt on your system, nor does it interfere with
+you having any other version of Qt installed on your system. Once you
+build bat with depkgs-qt, it should *not* use the Qt shared objects, but
+rather they will be linked into the program. After fully installing bat
+(make install), you can run "ldd bat" to see what shared objects it will
+use. If any Qt shared objects are referenced, something has gone wrong.
+
+4. Unless absolutely necessary, we recommend that you do not define any
+special library environment variables that apply to the ./configure -- for
+example: LIBDIR=/... ./configure <your-options> is strongly discouraged.
+Doing so, could potentially cause Bacula to be linked against the wrong
+shared objects.
+
+5. The Bacula project strongly recommends that you install Bacula into a
+single directory, with a few minor exceptions such as the MySQL or
+PostgreSQL databases. Preferrably this should be /opt/bacula. The full
+recommendation is:
+
+#!/bin/sh
+# Recommended configure script for Bacula
+prefix=/opt/bacula
+email=xxx@yyy.zz
+CFLAGS="-g -O2 -Wall" \
+ ./configure \
+ --sbindir=${prefix}/bin \
+ --sysconfdir=${prefix}/etc \
+ --docdir=${prefix}/html \
+ --htmldir=${prefix}/html \
+ --with-working-dir=${prefix}/working \
+ --with-pid-dir=${prefix}/working \
+ --with-subsys-dir=${prefix}/working \
+ --with-scriptdir=${prefix}/scripts \
+ --with-plugindir=${prefix}/plugins \
+ --libdir=${prefix}/lib \
+ --enable-smartalloc \
+ --enable-tray-monitor \
+ --enable-bat \
+ --with-mysql \
+ --with-dump-email=${email} \
+ --with-job-email=${email} \
+ --with-smtp-host=localhost \
+ --with-baseport=9101
+
+Obviously, the email, and some of the minor options (mysql, postgresql,
+...) can be changed to suit your distribution, but the directory names
+defined above are strongly recommended, and over time the default values in
+the bacula-dir.conf and bacula-sd.conf will reflect these choices.
+
+If you have any questions about this or would like a detailed document
+describing our recommendations including packaging requirements, please
+send an email to the bacula-devel list.
+
+6. Starting with Bacula version 3.0.0 up to Bacula 5.0.0, the shared
+libraries that Bacula uses by default are named xxx-1.0.0. Starting with
+Bacula 5.0.1, we are going to name the libraries using the Bacula version.
+So in Bacula 5.0.1, the libraries will be named xxx-5.0.1. With future
+versions, the last digit may or may not change when we distribute patch
+updates (i.e. the last digit of the version changes). This will depend on
+whether or not we have changed something in the library. Hopefully this
+new procedure will resolve some of the incompatibility problems between
+different versions of the shared objects.
+
+7. The default build option for bconsole is conio (my own little console
+routines). I did this because some years ago, readline was very difficult
+to maintain -- it and where it was found seemed to change on every release.
+This generated at the time a number of support problems. It seems to me
+that since then there have been very few problems with readline. As a
+consequence, I have no problem if you want to make bconsole with readline
+enabled. It will actually give some very nice new bconsole command
+completion functionality that Eric has written. Bottom line: feel free to
+use readline or not as you please.
+
+
+;;;;
+Eric;;;25 January 2010 at 10:00
+Bacula Version 5.0.0 has been released to Source Forge
+
+Release Numbering:
+-----------------------------------------------------------
+You might be wondering why this release jumps from 3.0.x to
+5.0.0 thus skipping version 4.0.0. We have done this for
+several reasons: first, we wanted a way of distinguishing
+the numbering system for the Bacula System Enterprise version
+and the Bacula Project version. So, to do so, we have decided
+that the first number of the Bacula Project version will always
+be odd, and the first number of the Enterprise version will always
+be even. Thus the Bacula Project now moves from 3.0.x to 5.0.x.
+In addition, we want to keep the Bacula Project version larger
+than the Enterprise version to indicate that the Bacula Project
+version is more advanced or has more features than the
+Enterprise version. For memory, the current Enterprise version
+is 2.6.1, and the next release (in a few months -- before June 2010)
+will be version 4.0.0.
+
+Warning:
+--------------------------------------------------------------
+Please note the three Warnings below before doing any install or
+upgrade.
+
+
+Changes since 3.0.3a (the last Bacula Project release):
+-------------------------------------------------------
+
+Bug fixes:
+1337 1351 1352 1354 1357 1361 1367 1369 1370 1373
+1376 1391 1403 1409 1420 1422 1427 1428 1431 1450
+1454 1455 1458 1456
+
+Fixed:
+ - Problem that locks the Director when the SMTP server wasn't
+ responding to the bsmtp program
+ - Restore's dir command shows incorrect file sizes
+ - Fix various problems with the reload command
+ - Fix problems with conio
+ - Eliminate several deadlocks or potential race conditions from SD
+
+Enhancements:
+ - Project 5: Truncate volume after purge
+ - Project 6: File Deduplication using Base Jobs
+ - Project 10: Restore from Multiple Storage Daemons
+ - Project 11: AllowCompression per Device
+ - Project 23: Add Maximum Concurent Jobs for Devices to balance load
+ between drives
+ - Add Accurate Fileset Options to configure accurate detection. Can use
+ checksum verification for example.
+ - Allow FD to keep root read but drop write permission (CAP)
+ - Secure handling of passwords for catalog backup
+ - Add Tab-completion for Bconsole when using Readline
+ - Add Bvfs API to query the catalog without building a memory tree
+ - Add new speed test to btape program
+ - Add new Bat screens (Autochanger content, Job view, Media view, ...)
+ - Windows version of Bat
+ - Added Spanish Bacula translation
+ - New bconsole -u nnn option to have timeout on commands
+ - Allow Migrate, Copy, and Virtual Full to read and write
+ to the same Pool
+ - show disabled -- shows disabled Jobs
+ - Add Pool File and Job retention periods (take precedence over Client)
+ - Many ACL improvements
+ - Level added to FD status Job entry
+ - Allow turning on/off Block Checksum per device
+ - Set Device Poll interval to 5 minutes -- previously did not poll
+ - Implement lock manager with bad order protection
+
+Compatibility:
+As always, both the Director and Storage daemon must be upgraded at
+the same time, and on any given machine, you must run only one version
+of Bacula. This means that on the Director and Storage daemon machines,
+you *must* upgrade your File daemon as well.
+
+Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 5.0.0
+Director and Storage daemons. There should be no need to upgrade older File
+Daemons immediately. However, we recommend that you do so as soon
+as is reasonable for your situation.
+
+================== Warning !!!!!! ==========================
+
+New Catalog format in version 5.0.0 (3.1.9 or later)
+-----------------------------------------------------
+
+This release of Bacula uses a new catalog format. We provide a set of
+scripts that permit to convert a 3.0.x (version 11) catalog to 5.0.0 (version
+12). 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.0.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 3.1.9
+(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.
+================================================================
+
+
+================== Warning !!!!!! ==========================
+If you upgrade a previous Win32 client installation, you must
+first stop the File daemon, then uninstall it before attempting
+the upgrade. If you do not do so, the upgrade will probably
+fail and you will need to manually find and run the
+Uninstall.exe file, before you can upgrade to the new version.
+This is because the file locations are different. If you want
+to save your previous bacula-fd.conf file, please do so before
+uninstalling it.
+================================================================
+
+================== Warning !!!!!! ==========================
+Due to permissions problems on Windows Vista and later systems,
+we no longer require SYSTEM or Administrator permissions to
+access the binaries and configuation files. If you wish
+to restrict access to these files, please see the New Features
+section of the manual for how to set access control lists.
+================================================================
+
+Note, the Win32 Installer no longer installs the Bacula Servers
+(Director and Storage daemon). See the New Features section of
+the manual for more details.
+
+============ Documentation improvements needed ==================
+
+Note!!!!! The 5.0.0+ documentation has a number of known problems:
+
+1. We have reduced the number of manuals, which has fixed many
+ of the broken links found in the old 3.0.x version, but there
+ are still some that need fixing.
+
+2. Integration of the 3.0.x features into the main manuals has
+ not yet been done.
+
+The documentation will not be completed in the near future due to lack
+manpower. If you are unhappy with this situation as we are, we suggest
+you help by submitting patches to the documentation. Thanks.
+=====
+
+
+This release includes large number of new features and changes.
+It should be more or less compatible with previous xx.conf files
+and File daemons providing that you are not using any of the new
+features.
+
+Please see the New Features chapter of the new manual, which documents
+some but not all the new features (we are still working on it):
+
+http://www.bacula.org/5.0.x-manuals/en/main/main/New_Features_in_5_0_0.html
+
+The ChangeLog has more details.
+
+;;;;
+
+
+Kern;;;18 October 2009 at 21:00
+Bacula Version 3.0.3 has been released to Source Forge
+
+Note, if you are not already running 3.0.x, read the 3.0.x release notes
+ below. Important!!!
+
+Version 3.0.3 is primarily a important bug fix update to version 3.0.2.
+
+Changes since 3.0.2:
+Bug fixes:
+ 1391, 1288, 1346, 1352, 1359, 1355, 1363, 1364, 1365, 1366, 1368,
+ 1369, 1370, 1371, 1382
+
+Fixes:
+ Apply James' fix for some Exchange plugin crashes
+ Integrate patch for building dmg on OSX from Lorenz Schori <lo@znerol.ch>
+ Fix bug #1391 Job status improperly set due to subtle variable overload problem
+ Fix #1352 about double free with regexp and big filenames on windows
+ Apply Graham's idea for recovering from disk full by recursing
+ when doing fixup_write_error ...
+ Make fix for VirtualFull changing device based on suggestion by
+ Nicolae Mihalache <mache@abcpages.com>
+ Fix concurrent Job recycle bug #1288
+ Backport part of one possible fix from bug #1346
+ Fix bug #1382 newly created disk volumes -> file not found warning
+ Fix Alpha ifdefing -- should fix bug #1359
+ Use old code for selecting file during restore.
+ Cherry-pick 3.1.x commits
+ tweak space on projects file
+ Fix seg fault in ignoredir code
+ Apply Frank's slash patch
+ Fix seg fault in SD bug #1371
+ 3.0.2-Fix-seg-fault-in-SD-bug-1371.patch
+ Add more info when SD connection refused
+ 3.0.2-Add-more-info-when-SD-connection-refused.patch
+ Fix bug #1355 Director crashes with double free in Accurate SQL query
+ 3.0.2-accurate.patch
+ Fixes bug #1368 ASSERT Failure on MacOS.
+ 3.0.2-mac-path-len.patch
+ Fix #1364 and #1363 about compression buffer error.
+ 3.0.2-zlib-buffer.patch
+ Fixes bug #1365 and #1366 about MacOSX resource forks.
+ 3.0.2-bug-1365.patch and 3.0.2-bug-1366.patch
+ Fix "Exclude Dir Containing" fileset option
+ 3.0.2-exclude-dir-containing-fd.patch
+ 3.0.2-exclude-dir-containing.patch
+ 3.0.2-exclude-dir-containing-top_level.patch
+
+Compatibility:
+ As always, both the Director and Storage daemon must be upgraded at
+ the same time.
+
+ Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 3.0.3
+ Director and Storage daemons. There should be no need to upgrade older File
+ Daemons.
+
+;;;;
+
+Kern;;;20 July 2009 at 14:49
+Bacula Version 3.0.2 has been released to Source Forge
+Note, if you are not already running 3.0.x, read the 3.0.x release notes
+below. Important!!!
+
+Version 3.0.2 is primarily a important bug fix update to version 3.0.1 with
+some enhancements (see below).
+
+Changes since 3.0.1:
+
+Bug fixes:
+ 1029, 1285, 1298, 1303, 1304, 1305, 1306, 1307, 1308, 1309, 1311, 1315
+ 1317, 1318, 1323, 1325, 1331, 1333, 1335
+
+Fixed:
+ - Fix problem with the Postgresql driver that sometime displays <NULL> values
+ - Cleanup old job records when starting the Director
+ - Fix bugs in xattr code
+ - Fix encoding problem with Postgresql
+ - Fix that prevents restore by file selection from using Copy job
+
+Enhancements:
+ - Security enhancement for the File Daemon
+ - New directive to specify source address for outgoing connexions
+ - Show volume availability in autochanger when doing restore.
+ This is project 31 in the projects file.
+ - Add accurate=yes/no option to estimate command
+ - Add --with-hostname, --with-bsrdir, --with-logdir to ./configure
+ - Add a restore menu that contructs a full restore when entering a JobId.
+ This is project 2 in the projects file.
+ - Add new Nagios plugin
+
+Compatibility:
+Like always, both the Director and Storage daemon must be upgraded at
+the same time.
+
+Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 3.0.2
+Director and Storage daemons. It should be no need to upgrade older File
+Daemon.
+;;;;
+
+Kern;;;30 April 2009 at 17:49
+Bacula Version 3.0.1 has been released to Source Forge.
+
+Note, if you are not already running 3.0.0, please read the 3.0.0 release notes. Important!!!
+
+Version 3.0.1 is primarily a minor bug fix update to version 3.0.0 with
+one enhancement (see below).
+
+Changes since 3.0.0:
+Bug fixes:
+ 1276, 1274, 1275, 1272 1246, 1268, 1281, 1282.
+
+Fixed:
+- Check for job_canceled() in fd_plugin code.
+- Update Win32 table creation to have new DB version 11 format
+- Remove illegal Options in Exclude of default Win32/64 bacula-dir.conf
+- Remove 'Reposition' messages when restoring
+- Updated projects file
+- Tweak version string to display versionid field at the end
+ and keep fields order.
+ - Add additional mysql connection debug code submitted by:
+ Chandranshu <chandranshu@gmail.com>
+
+Enhancement:
+- Modify insertion of read Volumes in SD to be done *before* the
+ drive reservation. This ensures that a Volume to be read will not
+ be reserved for writing. Significant improvement in eliminating
+ tape deadlock situations.
+
+Note, both the Director and Storage daemons must be upgraded at the
+same time. The 3.0.1 File daemons are compatible with 3.0.0 file
+daemons and as noted below in the 3.0.0 release notes the Director
+and Storage daemon should be compatible with 2.4.x File daemons.
+In general, we do not expect any of the 3.0.x File daemons to work with older
+Directors and Storage daemons (as has always been the case for Bacula
+releases).
+
+============ Documentation improvements needed ==================
+
+Note!!!!! The 3.0.0+ documentation needs rather extensive modifications in the
+following areas:
+
+1. Missing documentation.
+2. Correction of links within various manuals -- most fail.
+3. Integration of the new features into the main documents.
+4. Much more.
+
+The documentation will not be completed in the near future due to lack
+manpower. If you are unhappy with this situation as we are, we suggest
+you help by submitting patches to the documentation. Thanks.
+=====
+;;;
+
+Kern;;;09 April 2009 at 22:30
+Bacula Version 3.0.0 has been released to Source Forge.
+
+This is to inform you that we have uploaded the Bacula version 3.0.0 source
+tar files and the Win32/64 installer files to the Bacula Source Forge
+download location.
+
+There are quite a number of new features in this release, and upgrading to it
+requires a database upgrade, so please read the release notes carefully
+(included below) and the documentation for the new features at:
+
+http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html
+
+There is still a good deal of work to do to finish the release process (mainly
+reorganizing the web site manuals ...), but at least the source files are
+released. The rpms should follow shortly (probably this weekend).
+
+If you are currently using 2.4.4, please note that within a few months that
+version will no longer be supported, so please consider the possibility of
+upgrading.
+
+This release probably has the most new features that we have ever released,
+and it has taken a long time to produce it. The basic code is very well
+tested, and if you stick to 2.4.4 features, you are unlikely to experience
+problems. However, many of the new features have not been well tested, so
+your help will be appreciated.
+
+The following issues with 3.0.0 are known and we are working on them:
+
+1. The documentation is not 100% complete (there are so many new features that
+we missed documenting some).
+
+2. All the new documentation is in the New Features chapter, but not all of it
+has yet been integrated back into the appropriate chapters.
+
+3. James has reported that the Exchange plugin may crash if you cancel a job
+while it is running. He is working on this.
+
+4. The SD has many new features that will make it more stable. One in
+particular is that it knows what Volumes will be read during a migration,
+copy, or Virtual backup job, and will ensure that they are not selected for
+writing (something easy to do if you are using disk files and the same pool
+for reading an writing). However, the day after the release was cut, I found
+a problem with this code that prevents it from working properly during
+certain pre-allocations of the write tape.
+
+5. There is still an outstanding bug report on VSS failing (it seems to be a
+bit of a rare case).
+
+As I previously announced, we will now make 3.0.0 our main release source code
+stream, and we hope to release new version every six months and bug fix
+updates even sooner. To be able to do this, we will support version 2.4.4
+only for a few more months. There after the project will only support the
+most current release ...
+
+This release comprises a lot of work by a lot of different people and many
+contributions. Normally I hesitate to mention particular people or
+contributions because I always forget someone, but since this was such a big
+release, I would like to mention at least the big contributions:
+
+Sponsor Company(s) - Programmer - Project
+Bacula Systems - Eric Bollengier - Accurate Backup
+Bacula Systems - Eric Bollengier - Catalog format enhancements
+Bacula Systems - Eric Bollengier - bextract non-portable Win32 data
+Bacula Systems - Eric Bollengier - Win64 File daemon
+Bacula Systems - Eric Bollengier - SD deadlock detection + postmortum dump
+Bacula Systems - Eric Bollengier - Faster Attribute despooling if DIR & FD on
+ same machine
+Bacula Systems - Eric Bollengier - Virtual tape emulation
+Bacula Systems - Kern Sibbald - USB rescue key
+Equiinet funded development - James Harper - MS Exchange plugin
+
+Personal contributions:
+Kjetil Torgrim Homme - Regex expressions for restore in bootstrap file
+Marco van Wieringen - ACL code overhaul
+Marco van Wieringen - Solaris ZFS/NFSv4 ACL support
+Marco van Wieringen - Extended Attribute support
+Marco van Wieringen - Shared Objects
+Dirk Bartley - Bat speedup + stability improvement + many enhancements
+Joao Henrique Freitas - libdbi catalog driver
+Scott Barninger - rpm packaging
+Kern Sibbald - many big and little projects ...
+Many people -- see the AUTHORS file.
+
+Many thanks to everyone for making Bacula what it is today.
+
+=== List of new features ===
+- Accurate Backup
+- Copy Jobs
+- ACL code overhaul
+- Solaris ZFS/NFSv4 ACL support
+- Extended Attribute support
+ --disable-xattr (default=auto)
+- Shared Objects
+ --enable-libtool (default)
+ --disable-libtool
+- Virtual Backup
+- Catalog Format Enhancements
+ - Support for more than 4 Billion file entries
+ - New stats tables
+- Duplicate Job Control
+- TLS Authentication
+- bextract non-portable Win32 data
+- State File updated at Job Termination
+- Bacula Plugins
+ - FD bpipe plugin
+ - FD Exchange plugin
+- libdbi DB driver
+- Console Enhancements
+ - status slots
+ - list joblog
+ - command separator
+- Bootstrap regex
+- Restore seek optimization
+- Virtual Tape Emulation
+- Bat Enhancements
+- RunScript Enhancements
+- Status enhancements
+- FD connect timeout default to 3 minutes
+- ftruncate implemented for NFS Volumes
+- FD Version compatibily flag
+- Statistics Enhancements
+- Faster Attribute despooling
+- Document split into 6 manuals
+- GPLv2 license now compatible with OpenSSL
+- Win64 File daemon
+- Postmortum dump improvements in SD
+- Deadlock mutex detection in SD
+- Improved Volume management in SD to avoid deadlocks.
+- New configure install options
+ --docdir= (default=/usr/share/doc/bacula-VERSION)
+ --htmldir= (default=/usr/share/doc/bacula-VERSION/html -- bat help files)
+ --plugindir= (default=sysconfdir, where plugins will be installed)
+- New Bare Metal Recovery with USB key. See rescue/linux/usb
+ New Directives:
+- Max Full Interval
+- Max Diff Interval
+- Honor No Dump Flag
+- Exclude Dirs Containing
+- Recycle Pool
+- Max Run Sched Time
+- Max Wait Time
+- Full/Diff/Incr Max Run Time
+- Scratch Pool
+- Max Console Connections
+- Spool Size (in Job resource)
+- Allow Mixed Priorities
+- Allow Duplicate Jobs
+- Allow Higher Duplicates
+- Cancel Queued Duplicates
+- Cancel Running Duplicates
+- TLS Authenticate
+- Console (in RunScript)
+
+New features from Project Items Completed for version 3.0.0
+ also listed above:
+Item 1: Accurate restoration of renamed/deleted files
+Item 3: Merge multiple backups (Synthetic Backup or Consolidation)
+Item 4: Implement Catalog directive for Pool resource in Director
+Item 5: Add an item to the restore option where you can select a Pool
+Item 8: Implement Copy pools
+Item 12: Add Plug-ins to the FileSet Include statements.
+Item 13: Restore only file attributes (permissions, ACL, owner, group...)
+Item 18: Better control over Job execution
+Item 26: Store and restore extended attributes, especially selinux file
+contexts
+Item 27: make changing "spooldata=yes|no" possible for
+Item 28: Implement an option to modify the last written date for volumes
+Item n: Split documentation into several books
+================================
+
+
+ Release Notes for Bacula 3.0.0
+
+ Bacula code: Total files = 520 Total lines = 205,459 (*.h *.c *.in)
+
+The diff between 2.4.4 and 2.5.x is 208,340 lines, so this release
+represents an enormous effort.
+
+This Director and Storage daemon must be upgraded at the same time,
+but they should be compatible with all 2.4.x File daemons, unless you
+use some of the new features that affect the FD. In other words, you should
+not have to upgrade all your File daemons when you upgrade. However, any
+release of version 2.5.40 or greater requires a database upgrade.
+
+================== Warning !!!!!! ==========================
+
+New Catalog format in version 3.0.0 (2.5.40 or later)
+-----------------------------------------------------
+
+This release of Bacula uses a new catalog format. We provide a set of
+scripts that permit to convert a 2.4.x (version 10) catalog to 3.0.0 (version
+11). 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 upgrad 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 3.0.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.
+
+The upgrade operation will convert the FileId index field of the File table
+from 32 bits to 64 bits. This operation will take TIME and will *temporarily*
+DOUBLE THE SIZE of your catalog. Bacula must be shutdown during this update,
+so, won't be able to run jobs during this period. For example, a 3 million
+files
+catalog will take 2 mins to upgrade on a normal machine. Don't forget to
+backup it before executing the script.
+
+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 2.5.40
+(e.g. 2.4.4) 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.
+
+
+Important New configure options :
+----------------------
+
+This release of Bacula 3.0.0 uses libtool by default
+to generate the Bacula libraries as shared objects rather than
+being directly linked in as in prior versions. This means that
+the Bacula shared objects, must either be in a shared object
+directory known to the loader or they must be in the directory
+where the Bacula binaries are installed. It is also possible
+to explicitly specify the libraries directory on the ./configure
+line (--libdir=/full-path/dir), but this should not be necessary.
+
+ ./configure --libdir=<full-path>
+
+If you have problems with libtool or you wish to use the old
+way of building libraries and linking them into Bacula, you
+can do so by disabling libtool on the configure command line with:
+
+ ./configure --disable-libtool
+
+During the installation of Bacula 3.0.0, it will now install
+bat help files (if you have configured bat). These files
+are placed in /usr/share/doc/bacula/html by default. If you
+want to put them elsewhere use:
+
+ ./configure --htmldir=<full-path>
+
+During the installation of Bacula, it will now install the
+ReleaseNotes, License, technotes, ChangeLog, and similar
+files in /usr/share/doc/bacula by default. If you
+want to put them elsewhere use:
+
+ ./configure --docdir=<full-path>
+
+During the installation of Bacula, any plugins will be
+installed in the plugindir, which is by default the
+same as libdir (/usr/lib). You can specify an alternate
+location with:
+
+ ./configure --with-plugindir=<full-path>
+
+==============================================================
+
+This release includes large number of new features and changes.
+It should be more or less compatible with previous xx.conf files
+and File daemons providing that you are not using any of the new
+features.
+
+Please see the New Features chapter of the new manual, which documents
+some but not all the new features (we are still working on it):
+
+http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html
+
+The ChangeLog has more details.
+
+;;;
+Kern;;;03 Nobember 2008 at 17:35
+Critical 2.4.3-orphaned-jobs.patch released
+We recently found and corrected a serious bug in Bacula that causes jobs to be
+orphaned or "stuck" in the director during the pruning process. Depending on
+what jobs get stuck and how many there are, it could prevent additional jobs
+from running. As best we can tell, this problem occurs only during what could
+be called extreme pruning conditions -- i.e. there are insufficient Volumes
+available for normal operations.
+
+In any case, we recommend that everyone apply the 2.4.3-orphaned-jobs.patch,
+which you can find in the bacula-patches section of the Source Forge download
+area as well as in the directory patches of both the trunk and Branch-2.4 SVN.
+;;;
+
+Kern;;;12 October 2008 at 10:30am
+Creation of Bacula Systems SA
+Dear Members of the Bacula Community,
+
+I'm pleased to announce the creation of Bacula Systems S.A., a new company to
+provide professional support and service for Bacula. I believe you will be
+pleased to see how we have married a strong commitment to the ethos of honest
+open source software with the availability of services desired by a wide
+range of Bacula users.
+
+As many of you know, I began work on Bacula in 2000 and released the first
+public version in April 2002 to Source Forge. Although I have personally
+written a very substantial part of the code, I offer sincere thanks to the
+many members of the community who have provided ideas, fixes, testing, and
+contributions of code, without which Bacula would not be what it is today.
+It has been a labor of love and I am pleased that so many people have found
+Bacula useful.
+
+Before telling you more about Bacula Systems, let me reiterate my unfaltering,
+ongoing commitment to open source software and the Bacula open source
+project. The code for Bacula and all future releases will remain available as
+free open source software under the GPL license that I transferred to the
+protection of the Free Software Foundation of Europe. Unlike some other open
+source projects, there will be no separate "enterprise" or proprietary
+version of the Bacula source code. www.bacula.org will continue to be the
+home for Bacula project development.
+
+So, why create Bacula Systems? The company was created to respond to requests
+from users who want professional support with guaranteed levels of service
+and response times. To ensure continuity and the highest level of knowledge
+transfer, I will take the position of Chairman of the Board and Chief
+Technical Officer of Bacula Systems S.A..
+
+Several members of the Bacula community have joined me to start the company.
+The other team members are also strongly dedicated to the spirit of keeping
+Bacula open and free while simultaneously offering commercial services to
+those for whom it is essential in making the decision to deploy Bacula.
+Bacula Systems is self-financed -- the initial capital comes from the
+founders; no outside venture capital was sought or accepted. This means we
+have the power to establish the company's priorities and we can remain
+dedicated to "honest open source". Bacula Systems S.A. is a Swiss company
+with offices in Yverdon-les-Bains, and with branches in France and Germany
+initially. We will open additional branches as business requires.
+
+I will continue to support development of Bacula via bacula.org and the Bacula
+community. Future developments will be in the "community" code base which
+will remain free. Bacula Systems will offer "funded development" to
+customers who wish to accelerate the addition of certain features to Bacula.
+Code developed this way will be contributed to the free distribution and will
+be available to the entire community at no charge. Bacula Systems will
+provide additional fee-based services, including high quality consulting,
+training, documentation and certified binaries.
+
+Our goal in establishing Bacula Systems is to be inclusive of the community,
+and expand it by creating opportunities for members of the Bacula community
+through a well-defined Partner Program. If you provide IT services or
+consulting, the Bacula Systems Partner Program can provide you with the
+additional back-up (pardon the pun) support you need to serve your customers
+more effectively.
+
+Our plan is to develop an international network of partners who offer high
+value added services to Bacula users -- installing, configuring and optimizing
+Bacula for their customers, as well as Level 3 and 4 support, with guaranteed
+service levels. We will also provide training and tools to our partners.
+
+The Bacula project website, www.bacula.org, and Source Forge will be unchanged
+in the mission and ideals of being free sources of information, mail lists
+and forum-based support for and by the community. Both Bacula source code and
+Bacula binaries will continue to be available for free, as in the past, and
+new releases will also be available for free. The new commercial website,
+www.baculasystems.com will provide information on commercial subscriptions
+for those users who want guaranteed levels of service, support, documentation
+and certified binaries.
+
+All members of the Bacula community are encouraged to register for free at
+www.baculasystems.com, so that you will receive announcements and news about
+our commercial activities, and so that you can send feedback to our new
+company, Bacula Systems.
+
+Thank you for your interest and participation in the Bacula community.
+
+Sincerely,
+
+Kern Sibbald
+;;;
+
+Kern;;;11 October 2008 at 11:30am
+Bacula version 2.4.3 Released
+This is to let you know that the source tar files and the Win32 binaries for
+Bacula version 2.4.3 have been released to the Bacula Source Forge download
+area.
+
+Release 2.4.3
+ This is a bug fix to version 2.4.2. All daemons are compatible
+ with other 2.4.x versions.
+
+Bugs Fixed:
+ 1159, 1162. 1149, 1128, 1143, 1140, 1129
+
+Change Summary:
+- Apply 2.4.2-cancel-non-running-jobs.patch to be able to cancel
+ a non created job faster.
+- This should correct bug #1159 where Migration does not properly
+ respect the Migration Low Bytes directive.
+- Fix typo in configure.in that breaks --with-db-password option
+- This code should fix the race condition that leads to a Director
+ crash at job end time when the job list is updated. This was reported
+ in bug #1162.
+- Remove all double quotes from SQLite creating script and
+ replace by single quotes as suggested by John Huttley.
+- Fix SQL case problem that may cause the failure of DiskToCatalog
+ in bug #1149.
+- Copy missing storage name into edit buffer. As far as I can tell
+ this never caused a bug.
+- Remove catalog dependency for bcopy
+- Modify catalog scripts to have an easier packaging integration,
+ using default variables.
+ Make difference between SQLite3 and SQLite in db_get_type()
+- Attempt to fix bug #1128 InChanger flag cleared during Migration
+ job when reading from one autochanger and writing to another.
+- Add more information to SD acquire.c INFO messages.
+- Fix NULL Volume name error when reading and the drive must
+ be switched.
+- Fix a Verify InitCatalog problem where in certain cases
+ a garbage filename may be entered in the verification database. This
+ fixes bug #1143.
+- Add space after version before date in bat about dialog.
+- Fix seg fault in Dir during estimate command with no level value
+ given. This fixes bug #1140.
+- Add message to migration job when the target job is already migrated.
+ This closes bug #1129.
+
+Unless some really serious new bug shows up, this will be the last release
+until the next major version (3.0.0), which we hope will be ready around the
+end of the year.
+;;;
+
+Kern;;;26 July 2008 at 10:30am
+Bacula version 2.4.2 Released
+This is to inform you that we have released the source and Win32 binaries of
+Bacula version 2.4.2 to the Bacula Source Forge download area.
+
+ This is an important bug fix release since version 2.4.1.
+
+Bugs Fixed:
+ 1034, 1125, 1118, 1124, 1107, 1129, 1126
+
+Change Summary:
+26Jul08
+- When a migration job actually runs, re-check the Job record
+ and skip if the job is already migrated. This should
+ significantly reduce the problems with bug #1129.
+- Break the do_swapping into do_unload, do_swapping, and
+ do_load. It is much more logical that way.
+- Implement a set_dcr_from_vol subroutine in acquire.c for
+ reading volumes. This allows the dcr to be refreshed after being
+ zapped when the wrong volume is mounted. This should fix bug #1126 -
+- During multiple tape restore, bacula
+ does not ask for physical tape change, but rereads same tape
+- Apply patch submitted for bug #1107 with a small modification.
+ This fixes a bug where bcopy copied too many records.
+- Make some tweaks to bsmtp based on patch submitted in bug #1124.
+ This fixes bug #1124.
+- Make the default bat restore Pool be Any. This fixes bug #1118.
+- Fix bug #1125 which reports a SD crash at the end of a tape
+ during restore. It was a debug statement that should not be
+ in a release.
+- Fix #1034 by setting big timeout on mysql connections
+- Do partial integration of the Win32 bat build created by Eric.
+- Ensure that SD tried to mount a volume not in an autochanger
+ at least once before asking for operator intervention.
+- Fix a pthreads bug in the Win32 pthreads emulation code affects only
+ version 2.5.x and above.
+;;;
+
+Kern;;;7 July 2008 at 10:30am
+Bacula version 2.4.1 Released
+This is to inform you that we have released the source and Win32 binaries of
+Bacula version 2.4.1 to the Bacula Source Forge download area.
+
+Bugs Fixed:
+ 1103, 1100, 1105, 1094, 1109, 1106, 1101, 1102, 1112
+ 1117, 1116, 1097.
+
+Change summary:
+- Clear in-use bit on vol when unused while swapping.
+- Remove sleep at end of ./bacula
+- Clear hash packet for hardlinked files correctly. This corrects
+ a long standing bug where hardlinked files selected individually
+ would occasionally not be restored.
+- Apply Eric's patch to ensure that autoprune does not return
+ a Volume not in the autochanger unless requested to do so.
+- Correct bat restore display of multiple drives. This fixes
+ bug #1117.
+- Do find_a_volume() each time an unload is done. This
+ fixes the failure of maxvol2-test.
+- Use Qmsg() in job.c watchdog callback.
+- Release main control rwlock if ABORTing.
+- Make watchdog connect timeout queue messages rather than sending
+ directly to avoid lock conflicts with the real thread.
+- Remove const char that causes problems with Python, which has
+ older 'incorrect' headers.
+- Add const char in dbd.c to avoid compiler warnings.
+- Fix mtx-changer to detect both versions of Ubuntu (Debian)
+ mt. This fixes bug #1116.
+- Fix failure of 2drive-concurrent-test. Always read label;
+ clear_unload() only after drive is defined in acquire_for_read().
+- Generally clean up the manual tape loading code. The main
+ conceptial change is that when a volume is marked to be unloaded,
+ its volume name is retained, and it is only marked as unloaded
+ when either the autoloader says it is unloaded or another tape
+ is read on that drive.
+- Fix a recycling problem with two autochangers reported in bug
+ #1106. This may also (unlikely) fix a second recycling bug as
+ reported in #1103.
+- Fix a SD lock volumes deadlock problem reported in bug #1100.
+- Fix format problem in bscan output reported in bug #1105.
+- Copy more data when restarting a job so that run
+ overrides are kept. This should fix bug #1094.
+- Backport updates to jobq.c where possible.
+- Fix bug where SD did not ask operator if the device could not
+ be opened. Reported by Eric.
+- Add dbuser to DIR conf file (replaces user).
+- Add --with-db-password to ./configure
+- Fix regress to handle db_password.
+- Fix a couple of pedantic compiler warnings.
+- Fix bug when starting a restore on a storage that doesn't
+ have the requested MediaType.
+- More work on word alignments -- eliminate all ints from
+ the configuration routines.
+- Fix bug reported by Scott Barninger where the bacula script
+ refers to scripts in the wrong directory. Needed to meet the
+ requirements of recent FHS location changes.
+- Fix word alignment problem on non-Intel 64 bit machines
+ such as Solaris. This should fix bug #1097 -- bus error in SD.
+- Add missing win32/patches/wxWidgets.patch to 2.4 repository.
+;;;
+
+
+Kern;;;4 Jun 2008 at 10:30am
Bacula version 2.4.0 Released
This is to inform you that we have released the source and Win32 binaries of
Bacula version 2.4.0 to the Bacula Source Forge download area.
in job report.
;;;;
-Kern;;;27 Jan 2008;;10:30
+Kern;;;27 Jan 2008 at 10:30am
Bacula version 2.2.8 Released
Bacula version 2.2.8 source tar files as well as the Win32
binaries are available in the bacula and Win32 release areas
want to upgrade, but it is not urgent ...
;;;
-Kern;;;9 Jan 2008;;20:30
+
+Kern;;;9 Jan 2008 at 20:30
Bacula version BETA 2.2.8 Released
Bacula version 2.2.8 source tar files as well as the Win32
binaries are available in the bacula-beta and