From: Kern Sibbald Date: Sun, 30 Jul 2006 10:39:32 +0000 (+0000) Subject: Updates X-Git-Tag: Release-2.0.0~703 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=ca07ae9b240c6a70c80a092420539c0ef5c5d9b5;p=bacula%2Fdocs Updates --- diff --git a/docs/developers/version.tex b/docs/developers/version.tex index 0bcfb8d8..facc6b24 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -1.38.11 (24 July 2006) +1.39.18 (30 July 2006) diff --git a/docs/home-page/fr/inc/header.php b/docs/home-page/fr/inc/header.php index d9c18877..976911bc 100644 --- a/docs/home-page/fr/inc/header.php +++ b/docs/home-page/fr/inc/header.php @@ -45,11 +45,11 @@ + restauration par le réseau"> - - + + @@ -59,15 +59,15 @@ diff --git a/docs/home-page/pages/feature-request.php b/docs/home-page/pages/feature-request.php index 770a524f..0cbf2278 100644 --- a/docs/home-page/pages/feature-request.php +++ b/docs/home-page/pages/feature-request.php @@ -9,16 +9,37 @@ In the past, users informally submitted feature requests by email, and I 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, I would like to formalize -the process a bit more. The main change will be to require users +

+Now that Bacula has become a bigger project, this process has been +formalized a bit more. The main change is for users to carefully think about their feature, and submit it on a feature request form. A mostly empty form is shown below along with an -example of an actual filled in form. - -Once I receive and approve the Feature Request, possibly requesting -some modifications, I'll add it to the projects file, which contains -a list of all open Feature Requests. +example of an actual filled in form. A text copy of the form can +be found in the projects file in the main source directory +of the Bacula release. That file also contains a list of all the +currently approved projects and their status. +

+The best time to submit a Feature Request is just after a release when +I officially request feature requests for the next version. The worst +time to submit a feature request is just prior to a new release (we are +very busy at that time). To actually submit the Feature request, +fill out the form, and submit it to both the bacula-users and +the bacula-devel email lists. It will then be openly discussed. +

+Once the Feature Request has beeen adequately discussed, I will +either reject it, approve it, or possibly request some +modifications. If you plan to implement the feature or donate +funds to have it implemented, this is important to note, +otherwise, the feature, even if approved, may wait a long time +for someone to implement it. +

+Once the Feature request is approved, I'll add it to the projects +file, which contains a list of all open Feature Requests. The projects +file is updated from time to time +

+The current (though possibly somewhat old) list of projects can also +be found on the Web site by clicking on the Projects menu item. +

Feature Request Form

diff --git a/docs/home-page/pages/projects.php b/docs/home-page/pages/projects.php
index a1b400b2..765d1645 100644
--- a/docs/home-page/pages/projects.php
+++ b/docs/home-page/pages/projects.php
@@ -6,10 +6,11 @@
 
 
                 
+                
 Projects:
                      Bacula Projects Roadmap 
-                       07 December 2005
-                    (prioritized by user vote)
+                Prioritized by user vote 07 December 2005
+                    Status updated 30 July 2006
 
 Summary:
 Item  1:  Implement data encryption (as opposed to comm encryption)
@@ -44,7 +45,7 @@ Below, you will find more information on future projects:
 Item  1:  Implement data encryption (as opposed to comm encryption)
   Date:   28 October 2005
   Origin: Sponsored by Landon and 13 contributors to EFF.
-  Status: Landon Fuller has implemented this in 1.39.x.
+  Status: Done: Landon Fuller has implemented this in 1.39.x.
                   
   What:   Currently the data that is stored on the Volume is not
           encrypted. For confidentiality, encryption of data at
@@ -58,7 +59,7 @@ Item 2:   Implement Migration that moves Jobs from one Pool to another.
   Origin: Sponsored by Riege Software International GmbH. Contact:
           Daniel Holtkamp 
   Date:   28 October 2005
-  Status: Partially working in 1.39, more to do. Assigned to
+  Status: 90% complete: Working in 1.39, more to do. Assigned to
           Kern.
 
   What:   The ability to copy, move, or archive data that is on a
@@ -396,7 +397,8 @@ Item  9:  Implement new {Client}Run{Before|After}Job feature.
 Item 10:  Merge multiple backups (Synthetic Backup or Consolidation).
   Origin: Marc Cousin and Eric Bollengier 
   Date:   15 November 2005
-  Status: Depends on first implementing project Item 1 (Migration).
+  Status: Waiting implementation. Depends on first implementing 
+          project Item 2 (Migration).
 
   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.
@@ -453,7 +455,7 @@ Item 12:  Directive/mode to backup only file changes, not entire file
   Date:   11 November 2005
   Origin: Joshua Kugler 
           Marek Bajon 
-  Status: RFC
+  Status: 
 
   What:   Currently when a file changes, the entire file will be backed up in
           the next incremental or full backup.  To save space on the tapes
@@ -762,6 +764,7 @@ Item n:   One line summary ...
 
 ===============================================
 Feature requests submitted after cutoff for December 2005 vote
+  and not yet discussed.
 ===============================================
 Item n:   Allow skipping execution of Jobs
   Date:   29 November 2005
@@ -805,7 +808,109 @@ Item n: archive data
           could do this bit ability to save data uncompresed so
           it can be read in any other system (future proof data)
           save the catalog with the disk as some kind of menu
-          system
+          system 
+
+Item :  Tray monitor window cleanups
+  Origin: Alan Brown ajb2 at mssl dot ucl dot ac dot uk
+  Date:   24 July 2006
+  Status:
+  What:   Resizeable and scrollable windows in the tray monitor.
+
+  Why:    With multiple clients, or with many jobs running, the displayed
+          window often ends up larger than the available screen, making
+          the trailing items difficult to read.
+
+   Notes:
+
+  Item :  Clustered file-daemons
+  Origin: Alan Brown ajb2 at mssl dot ucl dot ac dot uk
+  Date:   24 July 2006
+  Status:
+  What:   A "virtual" filedaemon, which is actually a cluster of real ones.
+
+  Why:    In the case of clustered filesystems (SAN setups, GFS, or OCFS2, etc)
+          multiple machines may have access to the same set of filesystems
+
+          For performance reasons, one may wish to initate backups from
+          several of these machines simultaneously, instead of just using
+          one backup source for the common clustered filesystem.
+
+          For obvious reasons, normally backups of $A-FD/$PATH and
+          B-FD/$PATH are treated as different backup sets. In this case
+          they are the same communal set.
+
+          Likewise when restoring, it would be easier to just specify
+          one of the cluster machines and let bacula decide which to use.
+
+          This can be faked to some extent using DNS round robin entries
+          and a virtual IP address, however it means "status client" will
+          always give bogus answers. Additionally there is no way of
+          spreading the load evenly among the servers.
+
+          What is required is something similar to the storage daemon
+          autochanger directives, so that Bacula can keep track of
+          operating backups/restores and direct new jobs to a "free"
+          client.
+
+   Notes:
+
+Item :  Tray monitor window cleanups
+  Origin: Alan Brown ajb2 at mssl dot ucl dot ac dot uk
+  Date:   24 July 2006
+  Status:
+  What:   Resizeable and scrollable windows in the tray monitor.
+
+  Why:    With multiple clients, or with many jobs running, the displayed
+          window often ends up larger than the available screen, making
+          the trailing items difficult to read.
+
+  Notes:
+
+Item:    Commercial database support
+  Origin: Russell Howe 
+  Date:   26 July 2006
+  Status:
+
+  What:   It would be nice for the database backend to support more 
+          databases. I'm thinking of SQL Server at the moment, but I guess Oracle, 
+          DB2, MaxDB, etc are all candidates. SQL Server would presumably be 
+          implemented using FreeTDS or maybe an ODBC library?
+
+  Why:    We only really have one database server, which is MS SQL Server 
+          2000. Maintaining a second one for the backup software (we grew out of 
+          SQLite, which I liked, but which didn't work so well with our database 
+          size). We don't really have a machine with the resources to run 
+          postgres, and would rather only maintain a single DBMS. We're stuck with 
+          SQL Server because pretty much all the company's custom applications 
+          (written by consultants) are locked into SQL Server 2000. I can imagine 
+          this scenario is fairly common, and it would be nice to use the existing 
+          properly specced database server for storing Bacula's catalog, rather 
+          than having to run a second DBMS.
+
+
+Item n:   Split documentation
+  Origin: Maxx 
+  Date:   27th July 2006
+  Status:
+
+  What:   Split documentation in several books
+
+  Why:    Bacula manual has now more than 600 pages, and looking for
+          implementation details is getting complicated.  I think
+          it would be good to split the single volume in two or
+          maybe three parts:
+
+          1) Introduction, requirements and tutorial, typically
+             are useful only until first installation time
+
+          2) Basic installation and configuration, with all the
+             gory details about the directives supported 3)
+             Advanced Bacula: testing, troubleshooting, GUI and
+             ancillary programs, security managements, scripting,
+             etc.
+
+  Notes:
+
 
 
diff --git a/docs/manual-de/update_version b/docs/manual-de/update_version index 78834ef7..5c2e0092 100755 --- a/docs/manual-de/update_version +++ b/docs/manual-de/update_version @@ -3,8 +3,8 @@ # Script file to update the Bacula version # out=/tmp/$$ -VERSION=`sed -n -e 's/^.*VERSION.*"\(.*\)"$/\1/p' /home/kern/bacula/branch-1.38/src/version.h` -DATE=`sed -n -e 's/^.*[ \t]*BDATE.*"\(.*\)"$/\1/p' /home/kern/bacula/branch-1.38/src/version.h` +VERSION=`sed -n -e 's/^.*VERSION.*"\(.*\)"$/\1/p' /home/kern/bacula/k/src/version.h` +DATE=`sed -n -e 's/^.*[ \t]*BDATE.*"\(.*\)"$/\1/p' /home/kern/bacula/k/src/version.h` . ./do_echo sed -f ${out} version.tex.in >version.tex rm -f ${out} diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index 0bcfb8d8..facc6b24 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -1.38.11 (24 July 2006) +1.39.18 (30 July 2006) diff --git a/docs/manual-fr/imagename_translations b/docs/manual-fr/imagename_translations index c1c0bead..028fdf2b 100644 --- a/docs/manual-fr/imagename_translations +++ b/docs/manual-fr/imagename_translations @@ -1,27 +1,27 @@ -img22.png./running.eps -img28.png./confirm.eps -img26.png./properties-security.eps +img16.png./win32-service-ok.eps +img6.png./Conf-Diagram.eps img2.png./bacula-applications.eps +img18.png./win32-finish.eps +img20.png./tray-icon.eps +img15.png./win32-service.eps +img27.png./properties-security-advanced-owner.eps +img5.png./Bacula-tray-monitor.eps img25.png./view-only.eps img21.png./menu.eps -img27.png./properties-security-advanced-owner.eps -img9.png./bimagemgr2.eps -img1.png./bacula-logo.eps -img10.png./bimagemgr3.eps -img19.png./idle.eps img3.png./bacula-objects.eps -img24.png./access-is-denied.eps -img6.png./Conf-Diagram.eps -img23.png./error.eps img12.png./win32-welcome.eps -img15.png./win32-service.eps +img23.png./error.eps +img4.png./flow.eps +img10.png./bimagemgr3.eps +img24.png./access-is-denied.eps +img13.png./win32-pkg.eps +img9.png./bimagemgr2.eps img11.png./win32-nsis.eps +img26.png./properties-security.eps img8.png./bimagemgr1.eps -img18.png./win32-finish.eps -img16.png./win32-service-ok.eps -img17.png./win32-start.eps img14.png./win32-location.eps -img20.png./tray-icon.eps -img13.png./win32-pkg.eps -img5.png./Bacula-tray-monitor.eps -img4.png./flow.eps +img1.png./bacula-logo.eps +img19.png./idle.eps +img28.png./confirm.eps +img17.png./win32-start.eps +img22.png./running.eps diff --git a/docs/manual/storedconf.tex b/docs/manual/storedconf.tex index 3c8fd697..9333a539 100644 --- a/docs/manual/storedconf.tex +++ b/docs/manual/storedconf.tex @@ -425,7 +425,7 @@ specified within the Device resource are specific to the Device. automatically change volumes as required by {\bf Bacula}. Normally, this directive will be specified only in the {\bf AutoChanger} resource, which is then used for all devices. However, you may also specify - the different {\bf Changer Command} in each resource Device. + the different {\bf Changer Command} in each Device resource. Most frequently, you will specify the Bacula supplied {\bf mtx-changer} script as follows: diff --git a/docs/manual/version.tex b/docs/manual/version.tex index 0bcfb8d8..facc6b24 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.38.11 (24 July 2006) +1.39.18 (30 July 2006)