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 20 files) is
-copyrighted under the GPL by other people (FSF, Sun, ...).
+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:
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 libaries are not
+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
and may contain Microsoft intellectual property (examples:
Microsoft VC++, the source to the VSS libraries, the Microsoft C
runtime libraries). As such we cannot and do not distribute that
-software. We are permitted however to distribut Bacula with the
+software. We are permitted however to distribute Bacula with the
necessary Microsoft libraries in binary form.
You may obtain the parts that we cannot distribute as follows. The
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.
+
+ 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
Other Licenses:
Certain parts of the Bacula software are licensed by their
-copyright holder(s) under the GPL. These software files are
-clearly marked as such.
+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
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+=====================================
+
+
============== Text of GPL version 2 license ========
GNU GENERAL PUBLIC LICENSE
+Kern;;;2007/9/9;;;14:30
+I regret to announce that there is a rather serious bug in Bacula.
+
+Bacula bug #935 reports that during a restore, a large number of files are
+missing and thus not restored. This is really quite surprising because we
+have a fairly extensive regression test suite that explicitly tests for this
+kind of problem many times.
+
+Despite our testing, there is indeed a bug in Bacula that has the following
+characteristics:
+
+1. It happens only when multiple simultaneous Jobs are run (regardless of
+whether or not data spooling is enabled).
+
+2. It has only been observed on disk based backup, but not on tape.
+
+3. Under the right circumstances (timing), it could and probably does happen
+on tape backups.
+
+4. It seems to be timing dependent, and requires multiple clients to
+reproduce.
+
+5. Analysis indicates that it happens most often when the clients are slow
+(e.g. doing Incremental backups).
+
+6. It has been verified to exist in versions 2.0.x and 2.2.x.
+
+7. It should also be in version 1.38, but could not be reproduced in testing,
+perhaps due to timing considerations or the fact that the test FD daemons
+were version 2.2.2.
+
+8. The data is correctly stored on the Volume, but incorrect index (JobMedia)
+records are stored in the database. (the JobMedia record generated during
+the Volume change contains the index of the new Volume rather than the
+previous Volume).
+
+9. You can prevent the problem from occurring by either turning off multiple
+simultaneous Jobs or by ensuring that while running multiple simultaneous
+Jobs that those Jobs do not span Volumes. E.g. you could manually mark
+Volumes as full when they are sufficiently large.
+
+10. If you are not running multiple simultaneous Jobs, you will not be
+affected by this bug.
+
+11. If you are running multiple simultaneous Jobs to tapes, I believe there is
+a reasonable probability that this problem could show up when Jobs are split
+across tapes.
+
+12. If you are running multiple simultaneous Jobs to disks, I believe there is
+a high probability that this problem will show up when Jobs are split across
+disks Volumes.
+
+I have uploaded patches to bug #935 (bugs.bacula.org) that will correct
+version 2.2.0, 2.2.1, and 2.2.2. The patch has been tested only on version
+2.2.2 and passes all regression tests as well as the specific test that
+reproduced the problem. This patch is still in the testing phase because it
+has not yet been confirmed by any user other than myself. The only daemon
+that is affected by the bug and the patch is the Storage daemon, so there is
+no need to upgrade any clients.
+
+After a little more testing, I plan to release version 2.2.3 probably on
+Monday the 10th or Tuesday.
+
+At this time, I do not have a patch for 2.0.x versions, and unless there is
+some really compelling reason to create one, I would prefer not -- it would
+not be a huge effort to back port the patch, but it would require rather
+extensive testing. Though it is hard to make a specific recommendation, I
+believe that it probably will be the wisest and simplest to either patch
+version 2.2.x if that is what you are currently running, or upgrade to
+version 2.2.3 when it is released.
+
+It *could* be possible to manually correct the bad JobMedia records in the
+catalog, but it is not something that I would personally recommend. If you
+*really* need data off an old tape, I recommend first trying a restore.
+Sometime tomorrow, I will provide more detailed instructions on several ways
+how to correct the problem if necessary -- all of them are somewhat painful.
+
+;;;
+
Kern;;;2007/8/11;;;14:30
Bacula Version 2.2.0 has been released to Source Forge.
projects / bacula / docs / commitdiff