From: Kern Sibbald Date: Thu, 9 Apr 2009 20:41:51 +0000 (+0000) Subject: Update home page X-Git-Tag: Release-3.0.1~59 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=3d45ed1c65e9678e665b9f0bb0964b32ccb7fb59;p=bacula%2Fdocs Update home page --- diff --git a/docs/home-page/de/LICENSE b/docs/home-page/de/LICENSE index 8f08f61d..c1ec1a38 100644 --- a/docs/home-page/de/LICENSE +++ b/docs/home-page/de/LICENSE @@ -1,3 +1,4 @@ + History: The original Bacula code was Copyright Kern Sibbald and John Walker. After November 2004, it became Copyright Kern Sibbald, and finally, @@ -5,52 +6,69 @@ the copyright was transferred to the Free Software Foundation Europe on 15 November 2006. Trademark: -The name Bacula is a registered trademark. +The name Bacula is a registered trademark of Kern Sibbald. =================================== License: -For the most part, Bacula is licensed under the GPL version 2 -this code is listed under Copyright Free Software Foundation -Europe e.V. A small part of the code (less than 10 files) is -copyrighted under the GPL by FSF, or under BSD licenses by various -authors (see below). - -What follows is information from the authors of the code: +For the most part, Bacula is licensed under the GPL version 2 this +code is listed under Copyright Free Software Foundation Europe e.V. +What follows is the addition(s) to the GPL version 2 license, that +applies to code that is copyrighted by the Free Software Foundation +Europe e.V. Linking: -Bacula may be linked with any libraries permitted under the GPL. -However, if configured with encryption Bacula does use the -OpenSSL libraries which are, unfortunately, not compatible with -GPL v2. To the best of our knowledge these libraries are not -distributed with Bacula code because they are shared objects, and -as such there is no conflict with the GPL according what I (Kern) -understand in talking to FSFE, and in any case, for the code that -I have written, I have no problems linking in OpenSSL (of course -this does not speak for the few files in Bacula that are -copyrighted by others). If you take a more severe stance on this -issue, and you are going to distribute Bacula, then simply do not -use the --with-openssl when building your package, and no use of -OpenSSL even through dynamic linking will be included. +As a special exception to the GPLv2, the Bacula Project gives +permission to link the code of its release of Bacula with the OpenSSL +project's "OpenSSL" library (or with modified versions of it that use +the same license as the "OpenSSL" library), and distribute the linked +executables. You must obey the GNU General Public License in all +respects for all of the code used other than "OpenSSL". + +As a special exception to the GPLv2, the Bacula Project gives +permission to link the code of its release of the Bacula Win32 File +daemon with the Microsoft supplied Volume Shadow Copy (VSS) libraries +and distribute the linked executables. You must obey the GNU General +Public License in all respects for all of the code used other than for +the Microsoft VSS code, where you must obey their license terms. + +The Bacula Project gives permission for plugins with GPLv2 compatible +licenses to be loaded and distributed with the Bacula executables as +long as the combined work is distributed under the terms listed in the +Bacula LICENSE file. A full list of GPLv2 compatible licenses can be +found at: http://www.fsf.org/licensing/licenses/. If you wish to load +or distribute plugins with different licensing terms please contact +the Bacula Project at: license@bacula.org +=================================== -IP rights: -Recipient understands that although each Contributor grants the -licenses to its Contributions set forth herein, no assurances are -provided by any Contributor that the Program does not infringe -the patent or other intellectual property rights of any other -entity. Each Contributor disclaims any liability to Recipient -for claims brought by any other entity based on infringement of -intellectual property rights or otherwise. As a condition to -exercising the rights and licenses granted hereunder, each -Recipient hereby assumes sole responsibility to secure any other -intellectual property rights needed, if any. For example, if a -third party patent license is required to allow Recipient to -distribute the Program, it is Recipient's responsibility to -acquire that license before distributing the Program. + +What follows is information from the authors of the code: + +License: +To the best of our knowledge, all code used in Bacula, which is +copyrighted by a third party, has licenses that are compatible +with the OpenSSL license, and so given the exception that we have +made to the GPLv2 above, Bacula can be freely linked and distributed +with the OpenSSL libraries. + +Intellectual Property rights: +Recipient understands that although each Contributor to Bacula grants +the licenses to its Contributions set forth herein, no assurances are +provided by any Contributor that the Program does not infringe the +patent or other intellectual property rights of any other entity. +Each Contributor disclaims any liability to Recipient for claims +brought by any other entity based on infringement of intellectual +property rights or otherwise. As a condition to exercising the rights +and licenses granted hereunder, each Recipient hereby assumes sole +responsibility to secure any other intellectual property rights +needed, if any. For example, if a third party patent license is +required to allow Recipient to distribute the Program, it is +Recipient's responsibility to acquire that license before distributing +the Program. Copyrights: -Each Contributor represents that to its knowledge it has +Each Contributor to Bacula represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. @@ -58,14 +76,14 @@ Code falling under the above conditions will be marked as follows: Bacula® - The Network Backup Solution - Copyright (C) 2000-2006 Free Software Foundation Europe e.V. + Copyright (C) 2000-2009 Free Software Foundation Europe e.V. The main author of Bacula is Kern Sibbald, with contributions from many others, a complete list can be found in the file AUTHORS. This program is Free Software; you can redistribute it and/or modify it under the terms of version two of the GNU General Public - License as published by the Free Software Foundation, a copy of which - is in the LICENSE file + License as published by the Free Software Foundation plus additions + that are listed in the file LICENSE. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of @@ -102,67 +120,43 @@ so themselves. Our intention is to respect as closely as possible Open Source practices while maintaining full respect for proprietary and copyrighted code. -BSD code used in the Windows version only: -Code falling under the BSD license has the following license: - - Copyright (c)2002-2003 Mark K. Kim - All rights reserved. +GPLv2 or later license: + src/tools/bsmtp.c + Copyright (C) 1997 Ralf S. Engelschall, All Rights Reserved. + (note, bsmtp.c does not use OpenSSL, nor is it used with the code + of any other part of Bacula) + +3 clause BSD License notice for inclusion with the binary: + src/lib/fnmatch.c + * Copyright (c) 1989, 1993, 1994 + * The Regents of the University of California. All rights reserved. + src/lib/fnmatch.h + * Copyright (c) 1992, 1993 + * The Regents of the University of California. All rights reserved. + +Permissive licenses: + src/lib/var.c/h + ** OSSP var - Variable Expansion + ** Copyright (c) 2001-2002 Ralf S. Engelschall + ** Copyright (c) 2001-2002 The OSSP Project (http://www.ossp.org/) + ** Copyright (c) 2001-2002 Cable & Wireless Deutschland (http://www.cw.com/de/) + + src/lib/bsnprintf.c + * Copyright Patrick Powell 1995 + + src/bregex.c/h + * Copyright (c) 1991 Tatu Ylonen, Espoo, Finland + + src/lib/sha1.c/h + Copyright (C) The Internet Society (2001). All Rights Reserved. + + src/win32/compat/getopt.c + "... licensed under IBM copyrights to use the IBM-provided source code + in any way he or she deems fit ..." + + src/win32/compat/sys/mtio.h (LGPL) + Copyright (C) 1996, 1997 Free Software Foundation, Inc. - Redistribution and use in source and binary forms, with or without - modification, are permitted provided that the following conditions - are met: - - * Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. - - * Redistributions in binary form must reproduce the above copyright - notice, this list of conditions and the following disclaimer in - the documentation and/or other materials provided with the - distribution. - - * Neither the original author of this software nor the names of its - contributors may be used to endorse or promote products derived - from this software without specific prior written permission. - - THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS - "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT - LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS - FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE - COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, - INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, - BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS - OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED - AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, - OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF - THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH - DAMAGE. - - -===================================== - -The entire GPL is reproduced below, in the manuals distributed with the -Bacula documentation and can also be found online on the GNU web site -as well as at www.bacula.org. You may also obtain a copy of the -GPL (or LGPL) by writing to: Free Software Foundation, Inc., -51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA - -The Four Freedoms Guaranteed by the GPL: -Freedom zero is the freedom to run the program as you wish for any purpose. - -Freedom one is the freedom to study the source code and change it -to do what you wish. - -Freedom two is the freedom to help your neighbour, that's the -freedom to make copies and distribute them to others when you -wish. - -Freedom three is the freedom to help your community, that's the -freedom to publish or distribute modified versions when you wish. - -Other Licenses: -Certain parts of the Bacula software are licensed by their -copyright holder(s) under the GPL or under the BSD license. -These software files are clearly marked as such. Bacula can be enabled with data encryption and/or communications encryption. If this is the case, you will be including OpenSSL code that @@ -171,7 +165,7 @@ that contains cryptographic software written by Eric Young (tjh@cryptsoft.com). There are parts of Bacula that are licensed under the LGPL so -that they may be used in proprietary code to interface with +that those files may be used in proprietary code to interface with Bacula. Finally there are parts of Bacula that are in the public domain. @@ -191,6 +185,12 @@ SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ===================================== +The entire GPL is reproduced below, in the manuals distributed with the +Bacula documentation and can also be found online on the GNU web site +as well as at www.bacula.org. You may also obtain a copy of the +GPL (or LGPL) by writing to: Free Software Foundation, Inc., +51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + ============== Text of GPL version 2 license ======== GNU GENERAL PUBLIC LICENSE diff --git a/docs/home-page/de/news.txt b/docs/home-page/de/news.txt index 4c95c1df..57211f87 100644 --- a/docs/home-page/de/news.txt +++ b/docs/home-page/de/news.txt @@ -1,3 +1,291 @@ +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 +Uniinet 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 +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 /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= + +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= + +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= + +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= + +============================================================== + +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 diff --git a/docs/home-page/en/LICENSE b/docs/home-page/en/LICENSE index 8f08f61d..c1ec1a38 100644 --- a/docs/home-page/en/LICENSE +++ b/docs/home-page/en/LICENSE @@ -1,3 +1,4 @@ + History: The original Bacula code was Copyright Kern Sibbald and John Walker. After November 2004, it became Copyright Kern Sibbald, and finally, @@ -5,52 +6,69 @@ the copyright was transferred to the Free Software Foundation Europe on 15 November 2006. Trademark: -The name Bacula is a registered trademark. +The name Bacula is a registered trademark of Kern Sibbald. =================================== License: -For the most part, Bacula is licensed under the GPL version 2 -this code is listed under Copyright Free Software Foundation -Europe e.V. A small part of the code (less than 10 files) is -copyrighted under the GPL by FSF, or under BSD licenses by various -authors (see below). - -What follows is information from the authors of the code: +For the most part, Bacula is licensed under the GPL version 2 this +code is listed under Copyright Free Software Foundation Europe e.V. +What follows is the addition(s) to the GPL version 2 license, that +applies to code that is copyrighted by the Free Software Foundation +Europe e.V. Linking: -Bacula may be linked with any libraries permitted under the GPL. -However, if configured with encryption Bacula does use the -OpenSSL libraries which are, unfortunately, not compatible with -GPL v2. To the best of our knowledge these libraries are not -distributed with Bacula code because they are shared objects, and -as such there is no conflict with the GPL according what I (Kern) -understand in talking to FSFE, and in any case, for the code that -I have written, I have no problems linking in OpenSSL (of course -this does not speak for the few files in Bacula that are -copyrighted by others). If you take a more severe stance on this -issue, and you are going to distribute Bacula, then simply do not -use the --with-openssl when building your package, and no use of -OpenSSL even through dynamic linking will be included. +As a special exception to the GPLv2, the Bacula Project gives +permission to link the code of its release of Bacula with the OpenSSL +project's "OpenSSL" library (or with modified versions of it that use +the same license as the "OpenSSL" library), and distribute the linked +executables. You must obey the GNU General Public License in all +respects for all of the code used other than "OpenSSL". + +As a special exception to the GPLv2, the Bacula Project gives +permission to link the code of its release of the Bacula Win32 File +daemon with the Microsoft supplied Volume Shadow Copy (VSS) libraries +and distribute the linked executables. You must obey the GNU General +Public License in all respects for all of the code used other than for +the Microsoft VSS code, where you must obey their license terms. + +The Bacula Project gives permission for plugins with GPLv2 compatible +licenses to be loaded and distributed with the Bacula executables as +long as the combined work is distributed under the terms listed in the +Bacula LICENSE file. A full list of GPLv2 compatible licenses can be +found at: http://www.fsf.org/licensing/licenses/. If you wish to load +or distribute plugins with different licensing terms please contact +the Bacula Project at: license@bacula.org +=================================== -IP rights: -Recipient understands that although each Contributor grants the -licenses to its Contributions set forth herein, no assurances are -provided by any Contributor that the Program does not infringe -the patent or other intellectual property rights of any other -entity. Each Contributor disclaims any liability to Recipient -for claims brought by any other entity based on infringement of -intellectual property rights or otherwise. As a condition to -exercising the rights and licenses granted hereunder, each -Recipient hereby assumes sole responsibility to secure any other -intellectual property rights needed, if any. For example, if a -third party patent license is required to allow Recipient to -distribute the Program, it is Recipient's responsibility to -acquire that license before distributing the Program. + +What follows is information from the authors of the code: + +License: +To the best of our knowledge, all code used in Bacula, which is +copyrighted by a third party, has licenses that are compatible +with the OpenSSL license, and so given the exception that we have +made to the GPLv2 above, Bacula can be freely linked and distributed +with the OpenSSL libraries. + +Intellectual Property rights: +Recipient understands that although each Contributor to Bacula grants +the licenses to its Contributions set forth herein, no assurances are +provided by any Contributor that the Program does not infringe the +patent or other intellectual property rights of any other entity. +Each Contributor disclaims any liability to Recipient for claims +brought by any other entity based on infringement of intellectual +property rights or otherwise. As a condition to exercising the rights +and licenses granted hereunder, each Recipient hereby assumes sole +responsibility to secure any other intellectual property rights +needed, if any. For example, if a third party patent license is +required to allow Recipient to distribute the Program, it is +Recipient's responsibility to acquire that license before distributing +the Program. Copyrights: -Each Contributor represents that to its knowledge it has +Each Contributor to Bacula represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. @@ -58,14 +76,14 @@ Code falling under the above conditions will be marked as follows: Bacula® - The Network Backup Solution - Copyright (C) 2000-2006 Free Software Foundation Europe e.V. + Copyright (C) 2000-2009 Free Software Foundation Europe e.V. The main author of Bacula is Kern Sibbald, with contributions from many others, a complete list can be found in the file AUTHORS. This program is Free Software; you can redistribute it and/or modify it under the terms of version two of the GNU General Public - License as published by the Free Software Foundation, a copy of which - is in the LICENSE file + License as published by the Free Software Foundation plus additions + that are listed in the file LICENSE. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of @@ -102,67 +120,43 @@ so themselves. Our intention is to respect as closely as possible Open Source practices while maintaining full respect for proprietary and copyrighted code. -BSD code used in the Windows version only: -Code falling under the BSD license has the following license: - - Copyright (c)2002-2003 Mark K. Kim - All rights reserved. +GPLv2 or later license: + src/tools/bsmtp.c + Copyright (C) 1997 Ralf S. Engelschall, All Rights Reserved. + (note, bsmtp.c does not use OpenSSL, nor is it used with the code + of any other part of Bacula) + +3 clause BSD License notice for inclusion with the binary: + src/lib/fnmatch.c + * Copyright (c) 1989, 1993, 1994 + * The Regents of the University of California. All rights reserved. + src/lib/fnmatch.h + * Copyright (c) 1992, 1993 + * The Regents of the University of California. All rights reserved. + +Permissive licenses: + src/lib/var.c/h + ** OSSP var - Variable Expansion + ** Copyright (c) 2001-2002 Ralf S. Engelschall + ** Copyright (c) 2001-2002 The OSSP Project (http://www.ossp.org/) + ** Copyright (c) 2001-2002 Cable & Wireless Deutschland (http://www.cw.com/de/) + + src/lib/bsnprintf.c + * Copyright Patrick Powell 1995 + + src/bregex.c/h + * Copyright (c) 1991 Tatu Ylonen, Espoo, Finland + + src/lib/sha1.c/h + Copyright (C) The Internet Society (2001). All Rights Reserved. + + src/win32/compat/getopt.c + "... licensed under IBM copyrights to use the IBM-provided source code + in any way he or she deems fit ..." + + src/win32/compat/sys/mtio.h (LGPL) + Copyright (C) 1996, 1997 Free Software Foundation, Inc. - Redistribution and use in source and binary forms, with or without - modification, are permitted provided that the following conditions - are met: - - * Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. - - * Redistributions in binary form must reproduce the above copyright - notice, this list of conditions and the following disclaimer in - the documentation and/or other materials provided with the - distribution. - - * Neither the original author of this software nor the names of its - contributors may be used to endorse or promote products derived - from this software without specific prior written permission. - - THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS - "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT - LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS - FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE - COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, - INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, - BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS - OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED - AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, - OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF - THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH - DAMAGE. - - -===================================== - -The entire GPL is reproduced below, in the manuals distributed with the -Bacula documentation and can also be found online on the GNU web site -as well as at www.bacula.org. You may also obtain a copy of the -GPL (or LGPL) by writing to: Free Software Foundation, Inc., -51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA - -The Four Freedoms Guaranteed by the GPL: -Freedom zero is the freedom to run the program as you wish for any purpose. - -Freedom one is the freedom to study the source code and change it -to do what you wish. - -Freedom two is the freedom to help your neighbour, that's the -freedom to make copies and distribute them to others when you -wish. - -Freedom three is the freedom to help your community, that's the -freedom to publish or distribute modified versions when you wish. - -Other Licenses: -Certain parts of the Bacula software are licensed by their -copyright holder(s) under the GPL or under the BSD license. -These software files are clearly marked as such. Bacula can be enabled with data encryption and/or communications encryption. If this is the case, you will be including OpenSSL code that @@ -171,7 +165,7 @@ that contains cryptographic software written by Eric Young (tjh@cryptsoft.com). There are parts of Bacula that are licensed under the LGPL so -that they may be used in proprietary code to interface with +that those files may be used in proprietary code to interface with Bacula. Finally there are parts of Bacula that are in the public domain. @@ -191,6 +185,12 @@ SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ===================================== +The entire GPL is reproduced below, in the manuals distributed with the +Bacula documentation and can also be found online on the GNU web site +as well as at www.bacula.org. You may also obtain a copy of the +GPL (or LGPL) by writing to: Free Software Foundation, Inc., +51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + ============== Text of GPL version 2 license ======== GNU GENERAL PUBLIC LICENSE diff --git a/docs/home-page/en/news.txt b/docs/home-page/en/news.txt index 4c95c1df..57211f87 100644 --- a/docs/home-page/en/news.txt +++ b/docs/home-page/en/news.txt @@ -1,3 +1,291 @@ +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 +Uniinet 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 +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 /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= + +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= + +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= + +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= + +============================================================== + +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 diff --git a/docs/home-page/en/pages/home.php b/docs/home-page/en/pages/home.php index d26b0345..3662036e 100644 --- a/docs/home-page/en/pages/home.php +++ b/docs/home-page/en/pages/home.php @@ -18,9 +18,8 @@ ready, network based backup program.

- Kern Sibbald announces the creation of Bacula Systems SA to provide - professional services to Bacula users. See: - + Bacula 3.0.0 is released. + See: News

@@ -43,7 +42,7 @@ presents important information for users who want to contribute to the Bacula project.
-
Bacula is Hosted on +
Bacula is released on SourceForge at http://sourceforge.net/projects/bacula where you can download the software.

You may also use diff --git a/docs/home-page/fr/LICENSE b/docs/home-page/fr/LICENSE index 8f08f61d..c1ec1a38 100644 --- a/docs/home-page/fr/LICENSE +++ b/docs/home-page/fr/LICENSE @@ -1,3 +1,4 @@ + History: The original Bacula code was Copyright Kern Sibbald and John Walker. After November 2004, it became Copyright Kern Sibbald, and finally, @@ -5,52 +6,69 @@ the copyright was transferred to the Free Software Foundation Europe on 15 November 2006. Trademark: -The name Bacula is a registered trademark. +The name Bacula is a registered trademark of Kern Sibbald. =================================== License: -For the most part, Bacula is licensed under the GPL version 2 -this code is listed under Copyright Free Software Foundation -Europe e.V. A small part of the code (less than 10 files) is -copyrighted under the GPL by FSF, or under BSD licenses by various -authors (see below). - -What follows is information from the authors of the code: +For the most part, Bacula is licensed under the GPL version 2 this +code is listed under Copyright Free Software Foundation Europe e.V. +What follows is the addition(s) to the GPL version 2 license, that +applies to code that is copyrighted by the Free Software Foundation +Europe e.V. Linking: -Bacula may be linked with any libraries permitted under the GPL. -However, if configured with encryption Bacula does use the -OpenSSL libraries which are, unfortunately, not compatible with -GPL v2. To the best of our knowledge these libraries are not -distributed with Bacula code because they are shared objects, and -as such there is no conflict with the GPL according what I (Kern) -understand in talking to FSFE, and in any case, for the code that -I have written, I have no problems linking in OpenSSL (of course -this does not speak for the few files in Bacula that are -copyrighted by others). If you take a more severe stance on this -issue, and you are going to distribute Bacula, then simply do not -use the --with-openssl when building your package, and no use of -OpenSSL even through dynamic linking will be included. +As a special exception to the GPLv2, the Bacula Project gives +permission to link the code of its release of Bacula with the OpenSSL +project's "OpenSSL" library (or with modified versions of it that use +the same license as the "OpenSSL" library), and distribute the linked +executables. You must obey the GNU General Public License in all +respects for all of the code used other than "OpenSSL". + +As a special exception to the GPLv2, the Bacula Project gives +permission to link the code of its release of the Bacula Win32 File +daemon with the Microsoft supplied Volume Shadow Copy (VSS) libraries +and distribute the linked executables. You must obey the GNU General +Public License in all respects for all of the code used other than for +the Microsoft VSS code, where you must obey their license terms. + +The Bacula Project gives permission for plugins with GPLv2 compatible +licenses to be loaded and distributed with the Bacula executables as +long as the combined work is distributed under the terms listed in the +Bacula LICENSE file. A full list of GPLv2 compatible licenses can be +found at: http://www.fsf.org/licensing/licenses/. If you wish to load +or distribute plugins with different licensing terms please contact +the Bacula Project at: license@bacula.org +=================================== -IP rights: -Recipient understands that although each Contributor grants the -licenses to its Contributions set forth herein, no assurances are -provided by any Contributor that the Program does not infringe -the patent or other intellectual property rights of any other -entity. Each Contributor disclaims any liability to Recipient -for claims brought by any other entity based on infringement of -intellectual property rights or otherwise. As a condition to -exercising the rights and licenses granted hereunder, each -Recipient hereby assumes sole responsibility to secure any other -intellectual property rights needed, if any. For example, if a -third party patent license is required to allow Recipient to -distribute the Program, it is Recipient's responsibility to -acquire that license before distributing the Program. + +What follows is information from the authors of the code: + +License: +To the best of our knowledge, all code used in Bacula, which is +copyrighted by a third party, has licenses that are compatible +with the OpenSSL license, and so given the exception that we have +made to the GPLv2 above, Bacula can be freely linked and distributed +with the OpenSSL libraries. + +Intellectual Property rights: +Recipient understands that although each Contributor to Bacula grants +the licenses to its Contributions set forth herein, no assurances are +provided by any Contributor that the Program does not infringe the +patent or other intellectual property rights of any other entity. +Each Contributor disclaims any liability to Recipient for claims +brought by any other entity based on infringement of intellectual +property rights or otherwise. As a condition to exercising the rights +and licenses granted hereunder, each Recipient hereby assumes sole +responsibility to secure any other intellectual property rights +needed, if any. For example, if a third party patent license is +required to allow Recipient to distribute the Program, it is +Recipient's responsibility to acquire that license before distributing +the Program. Copyrights: -Each Contributor represents that to its knowledge it has +Each Contributor to Bacula represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. @@ -58,14 +76,14 @@ Code falling under the above conditions will be marked as follows: Bacula® - The Network Backup Solution - Copyright (C) 2000-2006 Free Software Foundation Europe e.V. + Copyright (C) 2000-2009 Free Software Foundation Europe e.V. The main author of Bacula is Kern Sibbald, with contributions from many others, a complete list can be found in the file AUTHORS. This program is Free Software; you can redistribute it and/or modify it under the terms of version two of the GNU General Public - License as published by the Free Software Foundation, a copy of which - is in the LICENSE file + License as published by the Free Software Foundation plus additions + that are listed in the file LICENSE. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of @@ -102,67 +120,43 @@ so themselves. Our intention is to respect as closely as possible Open Source practices while maintaining full respect for proprietary and copyrighted code. -BSD code used in the Windows version only: -Code falling under the BSD license has the following license: - - Copyright (c)2002-2003 Mark K. Kim - All rights reserved. +GPLv2 or later license: + src/tools/bsmtp.c + Copyright (C) 1997 Ralf S. Engelschall, All Rights Reserved. + (note, bsmtp.c does not use OpenSSL, nor is it used with the code + of any other part of Bacula) + +3 clause BSD License notice for inclusion with the binary: + src/lib/fnmatch.c + * Copyright (c) 1989, 1993, 1994 + * The Regents of the University of California. All rights reserved. + src/lib/fnmatch.h + * Copyright (c) 1992, 1993 + * The Regents of the University of California. All rights reserved. + +Permissive licenses: + src/lib/var.c/h + ** OSSP var - Variable Expansion + ** Copyright (c) 2001-2002 Ralf S. Engelschall + ** Copyright (c) 2001-2002 The OSSP Project (http://www.ossp.org/) + ** Copyright (c) 2001-2002 Cable & Wireless Deutschland (http://www.cw.com/de/) + + src/lib/bsnprintf.c + * Copyright Patrick Powell 1995 + + src/bregex.c/h + * Copyright (c) 1991 Tatu Ylonen, Espoo, Finland + + src/lib/sha1.c/h + Copyright (C) The Internet Society (2001). All Rights Reserved. + + src/win32/compat/getopt.c + "... licensed under IBM copyrights to use the IBM-provided source code + in any way he or she deems fit ..." + + src/win32/compat/sys/mtio.h (LGPL) + Copyright (C) 1996, 1997 Free Software Foundation, Inc. - Redistribution and use in source and binary forms, with or without - modification, are permitted provided that the following conditions - are met: - - * Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. - - * Redistributions in binary form must reproduce the above copyright - notice, this list of conditions and the following disclaimer in - the documentation and/or other materials provided with the - distribution. - - * Neither the original author of this software nor the names of its - contributors may be used to endorse or promote products derived - from this software without specific prior written permission. - - THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS - "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT - LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS - FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE - COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, - INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, - BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS - OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED - AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, - OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF - THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH - DAMAGE. - - -===================================== - -The entire GPL is reproduced below, in the manuals distributed with the -Bacula documentation and can also be found online on the GNU web site -as well as at www.bacula.org. You may also obtain a copy of the -GPL (or LGPL) by writing to: Free Software Foundation, Inc., -51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA - -The Four Freedoms Guaranteed by the GPL: -Freedom zero is the freedom to run the program as you wish for any purpose. - -Freedom one is the freedom to study the source code and change it -to do what you wish. - -Freedom two is the freedom to help your neighbour, that's the -freedom to make copies and distribute them to others when you -wish. - -Freedom three is the freedom to help your community, that's the -freedom to publish or distribute modified versions when you wish. - -Other Licenses: -Certain parts of the Bacula software are licensed by their -copyright holder(s) under the GPL or under the BSD license. -These software files are clearly marked as such. Bacula can be enabled with data encryption and/or communications encryption. If this is the case, you will be including OpenSSL code that @@ -171,7 +165,7 @@ that contains cryptographic software written by Eric Young (tjh@cryptsoft.com). There are parts of Bacula that are licensed under the LGPL so -that they may be used in proprietary code to interface with +that those files may be used in proprietary code to interface with Bacula. Finally there are parts of Bacula that are in the public domain. @@ -191,6 +185,12 @@ SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ===================================== +The entire GPL is reproduced below, in the manuals distributed with the +Bacula documentation and can also be found online on the GNU web site +as well as at www.bacula.org. You may also obtain a copy of the +GPL (or LGPL) by writing to: Free Software Foundation, Inc., +51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + ============== Text of GPL version 2 license ======== GNU GENERAL PUBLIC LICENSE diff --git a/docs/home-page/fr/news.txt b/docs/home-page/fr/news.txt index 4c95c1df..57211f87 100644 --- a/docs/home-page/fr/news.txt +++ b/docs/home-page/fr/news.txt @@ -1,3 +1,291 @@ +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 +Uniinet 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 +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 /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= + +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= + +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= + +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= + +============================================================== + +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