[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bacula-commits
Subject:    [Bacula-commits] git: Bacula Documentation branch, master,
From:       "Kern Sibbald" <kerns () users ! sourceforge ! net>
Date:       2009-09-27 14:01:06
Message-ID: E1MruJH-0003q9-BH () cxgxhf1 ! ch3 ! sourceforge ! com
[Download RAW message or body]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Bacula Documentation".

The branch, master has been updated
       via  b6384c10fa1a855d00dfc43d8ff580ac7e2d1bb7 (commit)
       via  a36cc323fdf814171cc2e04fa9bff56e5920a882 (commit)
      from  9a1529cb61c8e9e31b6ff154678766e4875c659a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit b6384c10fa1a855d00dfc43d8ff580ac7e2d1bb7
Merge: a36cc323fdf814171cc2e04fa9bff56e5920a882 9a1529cb61c8e9e31b6ff154678766e4875c659a
Author: Kern Sibbald <kern@sibbald.com>
Date:   Sun Sep 27 16:01:17 2009 +0200

    Merge branch 'master' of ssh://bacula.git.sourceforge.net/gitroot/bacula/docs

commit a36cc323fdf814171cc2e04fa9bff56e5920a882
Author: Kern Sibbald <kern@sibbald.com>
Date:   Sun Sep 27 16:00:19 2009 +0200

    Add update warnings

-----------------------------------------------------------------------

Summary of changes:
diff --git a/docs/manuals/en/developers/Makefile.in b/docs/manuals/en/developers/Makefile.in
index b565d79..852e7e2 100644
--- a/docs/manuals/en/developers/Makefile.in
+++ b/docs/manuals/en/developers/Makefile.in
@@ -73,7 +73,7 @@ web:
 	latex2html -split 4 -local_icons -t "Developer's Guide" -long_titles 4 \
 		-contents_in_nav -toc_stars -white -notransparent ${DOC} >tex.out 2>&1
 	./translate_images.pl --to_meaningful_names ${DOC}/Developer*Guide.html
-	@cp -f ${DOC}/Developers_Guide.html ${DOC}/index.html
+	@cp -f ${DOC}/Developer_s_Guide.html ${DOC}/index.html
 	@rm -f *.eps *.gif *.jpg ${DOC}/*.eps  *.old 
 	@rm -f ${DOC}/idle.png
 	@rm -f ${DOC}/win32-*.png ${DOC}/wx-console*.png ${DOC}/xp-*.png
diff --git a/docs/manuals/en/install/installation.tex b/docs/manuals/en/install/installation.tex
index 2a47cd6..66c8a5c 100644
--- a/docs/manuals/en/install/installation.tex
+++ b/docs/manuals/en/install/installation.tex
@@ -80,7 +80,25 @@ them.
 
 If you are upgrading from one Bacula version to another, you should first
 carefully read the ReleaseNotes of all major versions between your current
-version and the version to which you are upgrading.  If the Bacula catalog
+version and the version to which you are upgrading.  In many upgrades,
+especially for minor patch upgrades (e.g. between 3.0.0 and 3.0.1) there
+will be no database upgrade, and hence the process is rather simple.
+
+With version 3.0.0 and later, you {\bf must} ensure that on any one
+machine that all components of Bacula are running on exactly the
+same version.  Prior to version 3.0.0, it was possible to run a 
+lower level FD with a newer Director and SD.  This is no longer the
+case.  
+
+As always, we attempt to support older File daemons. This avoids the
+need to do a simultaneous upgrade of many machines. For exactly what
+older versions of the FD are supported, please see the ReleaseNotes 
+for the new version.  In any case, you must always upgrade both the
+Director and the Storage daemon at the same time, and you must also
+upgrade any File daemon that is running on the same machine as a Director
+or a Storage daemon (see the prior paragraph).
+
+If the Bacula catalog
 database has been upgraded (as it is almost every major release), you will
 either need to reinitialize your database starting from scratch (not
 normally a good idea), or save an ASCII copy of your database, then proceed


hooks/post-receive
-- 
Bacula Documentation

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-commits mailing list
Bacula-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-commits
[prev in list] [next in list] [prev in thread] [next in thread]