From: Kern Sibbald Date: Mon, 23 Jul 2007 10:15:52 +0000 (+0000) Subject: Update X-Git-Tag: Release-2.2.0~102 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=89ef27678591f32581e5522a03f95286577d4aa4;p=bacula%2Fdocs Update --- diff --git a/docs/developers/version.tex b/docs/developers/version.tex index 641fda3b..76a5117b 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -2.1.26 (12 July 2007) +2.1.29 (22 July 2007) diff --git a/docs/home-page/LICENSE b/docs/home-page/LICENSE index bd6fa9db..e105b738 100644 --- a/docs/home-page/LICENSE +++ b/docs/home-page/LICENSE @@ -10,17 +10,28 @@ The name Bacula is a registered trademark. =================================== License: -For the most part, Bacula is licensed under the GPL version 2 -with the additions listed below. Most this code is listed -under Copyright Free Software Foundation Europe e.V. What -follows are the additions to the GPL version 2 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, ...). + +What follows is information from the authors of the code: Linking: -Bacula may be linked with any libraries permitted under the GPL, -or with any non-GPLed libraries, including OpenSSL, that are -required for its proper functioning, providing the source code of -those non-GPLed libraries is non-proprietary and freely -available to the public. +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 +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. + IP rights: Recipient understands that although each Contributor grants the @@ -52,8 +63,8 @@ Code falling under the above conditions will be marked as follows: 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 plus additions - that are listed in the file LICENSE. + License as published by the Free Software Foundation, a copy of which + is in the LICENSE file This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of @@ -72,13 +83,13 @@ Code falling under the above conditions will be marked as follows: Windows: -Certain source code used to build the Windows version of the Bacula -File daemon is copyrighted and or trademarked by Microsoft 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 distribute Bacula in binary form with the necessary Microsoft -libraries linked in. +Certain source code used to build the Windows version of the +Bacula File daemon is copyrighted and or trademarked by Microsoft +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 +necessary Microsoft libraries in binary form. You may obtain the parts that we cannot distribute as follows. The Microsoft compiler available for purchase, and Microsoft provides a free @@ -113,8 +124,14 @@ 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 with no modifications. These -software files are clearly marked as such. +copyright holder(s) under the GPL. 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 +that contains cryptographic software written by Eric Young +(eay@cryptsoft.com) and also software written by Tim Hudson +(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 diff --git a/docs/home-page/donations.txt b/docs/home-page/donations.txt index 904f2f3c..2c038c87 100644 --- a/docs/home-page/donations.txt +++ b/docs/home-page/donations.txt @@ -6,7 +6,6 @@ donations or supplied finacial development support to the Bacula project and have specifically requested that their names appear here: -$50 TightPoker.com (Hans) Many thanks to the many Bacula listed and non-listed diff --git a/docs/home-page/news.txt b/docs/home-page/news.txt index 570258d2..6ba0184a 100644 --- a/docs/home-page/news.txt +++ b/docs/home-page/news.txt @@ -5,6 +5,10 @@ This is a bug fix release to version 2.0.2. If you are upgrading from a version older than 2.0.0, please be sure to read the important notes below. +Also, please check the patches directory in the current SVN or the +patches release section on Source Forge for important bug fixes to +this version. + 5Mar07 kes File migrate bug with Pool Occupancy using mediaid instead of jobids. Fixes bug #795. diff --git a/docs/home-page/pages/bugs.php b/docs/home-page/pages/bugs.php index 9f5c3875..57b6bd00 100644 --- a/docs/home-page/pages/bugs.php +++ b/docs/home-page/pages/bugs.php @@ -11,7 +11,7 @@ not a request for support (see the Support tab to the left).

- Bacula now has a bug reporting system + Bacula now has a Mantis bug reporting system implemented by Dan Langille and hosted on his computer. It is web based, easy to use, and we recommend you give it a try. You can submit a bug or review the list of open or closed bugs by visiting: @@ -23,14 +23,26 @@ To view the bug reports, you can login as user anonymous and password anonymous. -To submit bug reports, you must create an account. +To submit bug reports, you must create an account. You must also use +a browser running a US ASCII code page or UTF-8. Some users running +Win32 IE with Windows Eastern European code pages have experienced +problems interfacing with the system.

Most Bacula problems are questions of support, so if you are not sure if a problem you are having is a bug, see the support page on this site for links to the email lists. -

Information Needed

+You should expect two things to be slightly different in our +Bugs handling than many other Open Source projects. First, we unfortunately +cannot supply support via that bugs database, and second, we close +bugs very quickly to avoid being overwhelmed. Please don't take this +personally. If you want to add a note to the bug report after it +is closed, you can do so without reopening the bug. If after everything +considered, you are convinced there is a bug and you have new information, +you can always reopen the bug report. + +

Information Needed in a Bug Report

For us to respond to a bug report, we normally need the following as the minimum information, which you can enter into the appropriate fields of the bug reporting system: diff --git a/docs/home-page/pages/feature-request.php b/docs/home-page/pages/feature-request.php index 0cbf2278..b9f3e19d 100644 --- a/docs/home-page/pages/feature-request.php +++ b/docs/home-page/pages/feature-request.php @@ -7,7 +7,7 @@ In the past, users informally submitted feature requests by email, and -I collected them, then once a version was released, I would publish the +I (Kern) collected them, then once a version was released, I would publish the list for users to vote on.

Now that Bacula has become a bigger project, this process has been diff --git a/docs/home-page/pages/license.php b/docs/home-page/pages/license.php index 2dc6e2ed..9cb6e686 100644 --- a/docs/home-page/pages/license.php +++ b/docs/home-page/pages/license.php @@ -1,40 +1,40 @@ - + - +

We have done this to ensure that any variant of Bacula will + be exactly compatible with the program that we have released. + The use of the name Bacula is restricted to software systems + that agree exactly with the program presented here. +

+
- Bacula Copyright, Trademark, and Licenses - + Bacula Copyright, Trademark, and Licenses +
- There are a number of different licenses that are used in - Bacula. -

GPL

- The vast bulk of the code is released under the + 		+ There are a number of different licenses that are used in + Bacula. +

GPL

+ The vast bulk of the code is released under the - GNU General Public License version 2. - Most of this code is copyrighted: - Copyright (C) 2000-2005 Kern Sibbald and John Walker. -

Portions may be copyrighted by other people (ATT, the - Free Software Foundation, ...). -

LGPL

- Some of the Bacula library source code is released under the - GNU Lesser General Public License. - This permits third parties to use these parts of our code in - their proprietary programs to interface to Bacula. -

Public Domain

- Some of the Bacula code has been released to the public domain. - E.g. md5.c, SQLite. -

Trademark

- Bacula®is a registered trademark of Kern Sibbald and John - Walker. + GNU General Public License version 2. + Most of this code is copyrighted: + Copyright (C) 2000-2007 Free Software Foundation Europe, e.V. +

Portions may be copyrighted by other people (ATT, the + Free Software Foundation, ...). +

LGPL

+ Some of the Bacula library source code is released under the + GNU Lesser General Public License. + This permits third parties to use these parts of our code in + their proprietary programs to interface to Bacula. +

Public Domain

+ Some of the Bacula code has been released to the public domain. + E.g. md5.c, SQLite. +

Trademark

+ Bacula®is a registered trademark of John + Walker. -

We have done this to ensure that any variant of Bacula will - be exactly compatible with the program that we have released. - The use of the name Bacula is restricted to software systems - that agree exactly with the program presented here. -

-
diff --git a/docs/home-page/pages/listlic.php b/docs/home-page/pages/listlic.php index f85eb635..217dad07 100644 --- a/docs/home-page/pages/listlic.php +++ b/docs/home-page/pages/listlic.php @@ -6,27 +6,27 @@ - - The people listed are independent contractors.
- We can't take responsibility for their actions when you hire them, - but we would appreciate feedback positive or negative.
-
- Listing on the Bacula Professional page is offered as a - service, without any guarantees.
-
- We reserve the right to decide with reason who is - added/removed from the web page.
- To be listed, you must have some tangible connection with and - knowledge of Bacula (i.e. developer, contributed - code/patches, Bacula user and subscribed to bacula-users, or - bacula-devel, and preferably a Web site ...).
-
- People listed here agree to update their contact information - on a regular basis.
Anyone listed with incorrect - information is subject to removal.

If you want to be - listed on the page, please get in contact with Kern - Sibbald.
- + + The people listed are independent contractors.
+ We can't take responsibility for their actions when you hire them, + but we would appreciate feedback positive or negative.
+
+ Listing on the Bacula Professional page is offered as a + service, without any guarantees.
+
+ We reserve the right to decide with reason who is + added/removed from the web page.
+ To be listed, you must have some tangible connection with and + knowledge of Bacula (i.e. developer, contributed + code/patches, Bacula user and subscribed to bacula-users, or + bacula-devel, and preferably a Web site ...).
+
+ People listed here agree to update their contact information + on a regular basis.
Anyone listed with incorrect + information is subject to removal.

If you want to be + listed on the page, please get in contact with Kern + Sibbald.
+ diff --git a/docs/home-page/pages/maillists.php b/docs/home-page/pages/maillists.php index 129b9811..5bd0e3ee 100644 --- a/docs/home-page/pages/maillists.php +++ b/docs/home-page/pages/maillists.php @@ -39,6 +39,7 @@ moderate, but can vary. All users are encouraged to subscribe and to participate. Due to the increasing volume of spam, you must be subscribed before you can send email to this list. + To subscribe follow the instructions at: Bacula Users List Subscription/Unsubscription/Modification.

@@ -52,6 +53,9 @@ you must replace the at with an @ symbol. The bacula-devel list is for those users who wish to communicate directly with the developers. The email volume is currently quite low, but can vary. +Due to the increasing volume of spam, you must be subscribed +before you can send email to this list. + To subscribe, please follow this link: Bacula Developers List Subscription/Unsubscription/Modification. @@ -79,7 +83,10 @@ http://lists.sourceforge.net/lists/listinfo/bacula-bugs. The bacula-beta list is a read only list for those packagers or users who wish to be notified when a new release is in preparation or is ready. -Please do not send email to this list. +This list is also used for discussions on running regression +scripts. +Due to the increasing volume of spam, you must be subscribed +before you can send email to this list. To subscribe, follow follow the instructions at: diff --git a/docs/home-page/pages/projects.php b/docs/home-page/pages/projects.php index a8ca9077..dd818cdc 100644 --- a/docs/home-page/pages/projects.php +++ b/docs/home-page/pages/projects.php @@ -10,51 +10,65 @@ Projects: Bacula Projects Roadmap - Status updated 12 January 2007 + Status updated 7 July 2007 + After re-ordering in vote priority + +Items Completed: +Item: 2 Implement a Bacula GUI/management tool. +Item: 18 Quick release of FD-SD connection after backup. +Item: 23 Implement from-client and to-client on restore command line. +Item: 25 Implement huge exclude list support using dlist +Item: 41 Enable to relocate files and directories when restoring +Item: 42 Batch attribute inserts (ten times faster) +Item: 43 More concurrency in SD using micro-locking +Item: 44 Performance enhancements (POSIX/Win32 OS file access hints). +Item: 40 Include JobID in spool file name Summary: -Item 1: Accurate restoration of renamed/deleted files -Item 2: Implement a Bacula GUI/management tool. -Item 3: Implement Base jobs. -Item 4: Implement from-client and to-client on restore command line. -Item 5: Implement creation and maintenance of copy pools -Item 6: Merge multiple backups (Synthetic Backup or Consolidation). -Item 7: Deletion of Disk-Based Bacula Volumes -Item 8: Implement a Python interface to the Bacula catalog. -Item 9: Archival (removal) of User Files to Tape -Item 10: Add Plug-ins to the FileSet Include statements. -Item 11: Implement more Python events in Bacula. -Item 12: Quick release of FD-SD connection after backup. -Item 13: Implement huge exclude list support using hashing. -Item 14: Allow skipping execution of Jobs -Item 15: Tray monitor window cleanups -Item 16: Split documentation -Item 17: Automatic promotion of backup levels -Item 18: Add an override in Schedule for Pools based on backup types. -Item 10: An option to operate on all pools with update vol parameters -Item 20: Include JobID in spool file name -Item 21: Include timestamp of job launch in "stat clients" output -Item 22: Message mailing based on backup types -Item 23: Allow inclusion/exclusion of files in a fileset by creation/mod times -Item 24: Add a scheduling syntax that permits weekly rotations -Item 25: Improve Bacula's tape and drive usage and cleaning management. -Item 26: Implement support for stacking arbitrary stream filters, sinks. -Item 27: Allow FD to initiate a backup -Item 28: Directive/mode to backup only file changes, not entire file -Item 29: Automatic disabling of devices -Item 30: Incorporation of XACML2/SAML2 parsing -Item 31: Clustered file-daemons -Item 32: Commercial database support -Item 33: Archive data -Item 34: Filesystem watch triggered backup. -Item 35: Implement multiple numeric backup levels as supported by dump -Item 36: Implement a server-side compression feature -Item 37: Cause daemons to use a specific IP address to source communications -Item 38: Multiple threads in file daemon for the same job -Item 39: Restore only file attributes (permissions, ACL, owner, group...) -Item 40: Add an item to the restore option where you can select a pool - -Below, you will find more information on future projects: +Item: 1 Accurate restoration of renamed/deleted files +Item: 2* Implement a Bacula GUI/management tool. +Item: 3 Allow FD to initiate a backup +Item: 4 Merge multiple backups (Synthetic Backup or Consolidation). +Item: 5 Deletion of Disk-Based Bacula Volumes +Item: 6 Implement Base jobs. +Item: 7 Implement creation and maintenance of copy pools +Item: 8 Directive/mode to backup only file changes, not entire file +Item: 9 Implement a server-side compression feature +Item: 10 Improve Bacula's tape and drive usage and cleaning management. +Item: 11 Allow skipping execution of Jobs +Item: 12 Add a scheduling syntax that permits weekly rotations +Item: 13 Archival (removal) of User Files to Tape +Item: 14 Cause daemons to use a specific IP address to source communications +Item: 15 Multiple threads in file daemon for the same job +Item: 16 Add Plug-ins to the FileSet Include statements. +Item: 17 Restore only file attributes (permissions, ACL, owner, group...) +Item: 18* Quick release of FD-SD connection after backup. +Item: 19 Implement a Python interface to the Bacula catalog. +Item: 20 Archive data +Item: 21 Split documentation +Item: 22 Implement support for stacking arbitrary stream filters, sinks. +Item: 23* Implement from-client and to-client on restore command line. +Item: 24 Add an override in Schedule for Pools based on backup types. +Item: 25* Implement huge exclude list support using hashing. +Item: 26 Implement more Python events in Bacula. +Item: 27 Incorporation of XACML2/SAML2 parsing +Item: 28 Filesystem watch triggered backup. +Item: 29 Allow inclusion/exclusion of files in a fileset by creation/mod times +Item: 30 Tray monitor window cleanups +Item: 31 Implement multiple numeric backup levels as supported by dump +Item: 32 Automatic promotion of backup levels +Item: 33 Clustered file-daemons +Item: 34 Commercial database support +Item: 35 Automatic disabling of devices +Item: 36 An option to operate on all pools with update vol parameters +Item: 37 Add an item to the restore option where you can select a pool +Item: 38 Include timestamp of job launch in "stat clients" output +Item: 39 Message mailing based on backup types +Item: 40* Include JobID in spool file name +Item: 41* Enable to relocate files and directories when restoring +Item: 42* Batch attribute inserts (ten times faster) +Item: 43* More concurrency in SD using micro-locking +Item: 44* Performance enhancements (POSIX/Win32 OS file access hints). Item 1: Accurate restoration of renamed/deleted files Date: 28 November 2005 @@ -91,7 +105,7 @@ Item 1: Accurate restoration of renamed/deleted files Item 2: Implement a Bacula GUI/management tool. Origin: Kern Date: 28 October 2005 - Status: + Status: In progress What: Implement a Bacula console, and management tools probably using Qt3 and C++. @@ -111,8 +125,77 @@ Item 2: Implement a Bacula GUI/management tool. Lucas Di Pentima but it is no longer being developed. +Item 3: Allow FD to initiate a backup + Origin: Frank Volf (frank at deze dot org) + Date: 17 November 2005 + Status: + + What: Provide some means, possibly by a restricted console that + allows a FD to initiate a backup, and that uses the connection + established by the FD to the Director for the backup so that + a Director that is firewalled can do the backup. + + Why: Makes backup of laptops much easier. + + +Item 4: Merge multiple backups (Synthetic Backup or Consolidation). + Origin: Marc Cousin and Eric Bollengier + Date: 15 November 2005 + Status: Waiting implementation. Depends on first implementing + project Item 2 (Migration) which is now done. + + What: A merged backup is a backup made without connecting to the Client. + It would be a Merge of existing backups into a single backup. + In effect, it is like a restore but to the backup medium. + + For instance, say that last Sunday we made a full backup. Then + all week long, we created incremental backups, in order to do + them fast. Now comes Sunday again, and we need another full. + The merged backup makes it possible to do instead an incremental + backup (during the night for instance), and then create a merged + backup during the day, by using the full and incrementals from + the week. The merged backup will be exactly like a full made + Sunday night on the tape, but the production interruption on the + Client will be minimal, as the Client will only have to send + incrementals. + + In fact, if it's done correctly, you could merge all the + Incrementals into single Incremental, or all the Incrementals + and the last Differential into a new Differential, or the Full, + last differential and all the Incrementals into a new Full + backup. And there is no need to involve the Client. + + Why: The benefit is that : + - the Client just does an incremental ; + - the merged backup on tape is just as a single full backup, + and can be restored very fast. + + This is also a way of reducing the backup data since the old + data can then be pruned (or not) from the catalog, possibly + allowing older volumes to be recycled + +Item 5: Deletion of Disk-Based Bacula Volumes + Date: Nov 25, 2005 + Origin: Ross Boylan (edited + by Kern) + Status: + + What: Provide a way for Bacula to automatically remove Volumes + from the filesystem, or optionally to truncate them. + Obviously, the Volume must be pruned prior removal. + + Why: This would allow users more control over their Volumes and + prevent disk based volumes from consuming too much space. + + Notes: The following two directives might do the trick: + + Volume Data Retention =