+Kern;;;18 October 2 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
projects / bacula / docs / blobdiff