From: Kern Sibbald Date: Tue, 14 Oct 2008 11:14:25 +0000 (+0000) Subject: Update X-Git-Tag: Release-3.0.0~813 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=200928ae6c17fad4c8b3ccd27190f558ed3759d0;p=bacula%2Fdocs Update --- diff --git a/docs/home-page/en/pages/maillists.php b/docs/home-page/en/pages/maillists.php index 9dbb07c7..71b1fca7 100644 --- a/docs/home-page/en/pages/maillists.php +++ b/docs/home-page/en/pages/maillists.php @@ -70,6 +70,25 @@ The previous address was modified to prevent easy use by spammers. To use it, you must replace the at with an @ symbol.

+

bacula-users-fr

+The bacula-users-fr list is the general French language forum to +ask questions about Bacula or respond to questions +from other users. The volume on this list is generally +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 French Users List Subscription/Unsubscription/Modification. +

+To send an email to the Bacula French Users List, use the following +address: bacula-users-fr at lists.sourceforge.net. +The previous address was modified to prevent easy use by spammers. To use it, +you must replace the at with an @ symbol. +

+ +

bacula-devel

The bacula-devel list is for those users who wish to communicate directly with the developers. The email volume diff --git a/docs/manuals/en/concepts/concepts.kilepr b/docs/manuals/en/concepts/concepts.kilepr index 1c58c86b..1a0cc57f 100644 --- a/docs/manuals/en/concepts/concepts.kilepr +++ b/docs/manuals/en/concepts/concepts.kilepr @@ -161,10 +161,10 @@ order=-1 [item:newfeatures.tex] archive=true -column=12 +column=0 encoding=UTF-8 highlight=LaTeX -line=1697 +line=544 open=true order=0 diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex index c8535c71..c3b26710 100644 --- a/docs/manuals/en/concepts/newfeatures.tex +++ b/docs/manuals/en/concepts/newfeatures.tex @@ -449,6 +449,12 @@ on the program called. \subsection{Concepts} +Although it is possible to backup Exchange using Bacula VSS the Exchange +plugin adds a good deal of functionality, because while Bacula VSS +completes a full backup (snapshot) of Exchange, it does +not support Incremental or Differential backups, restoring is more +complicated, and a single database restore is not possible. + Microsoft Exchange organises its storage into Storage Groups with Databases inside them. A default installation of Exchange will have a single Storage Group called 'First Storage Group', with two Databases @@ -467,7 +473,7 @@ plugin will not function if this option is enabled. The plugin allows backing up of entire storage groups, and the restoring of entire storage groups or individual databases. Backing up and restoring at the individual mailbox or email item is not supported but -can be simulated by use of the Recovery Storage Group (see below). +can be simulated by use of the "Recovery" Storage Group (see below). \subsection{Installing} @@ -507,13 +513,44 @@ Incremental or Differential backup too. This adds 5MB to each Incremental or Differential backup size but otherwise does not cause any problems. +By default, a normal VSS fileset containing all the drive letters will +also back up the Exchange databases using VSS. This will interfere with +the plugin and Exchange's shared ideas of when the last full backup was +done, and may also truncate log files incorrectly. It is important, +therefore, that the Exchange database files be excluded from the backup, +although the folders the files are in should be included, or they will +have to be recreated manually if a baremetal restore is done. + +\begin{verbatim} +FileSet { + Include { + File = C:/Program Files/Exchsrvr/mdbdata + Plugin = "exchange:..." + } + Exclude { + File = C:/Program Files/Exchsrvr/mdbdata/E00.chk + File = C:/Program Files/Exchsrvr/mdbdata/E00.log + File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log + File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log + File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log + File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log + File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb + } +} +\end{verbatim} + +The advantage of excluding the above files is that you can significantly +reduce the size of your backup since all the important Exchange files +will be properly saved by the Plugin. + + \subsection{Restoring} The restore operation is much the same as a normal Bacula restore, with the following provisos: \begin{itemize} -\item The 'Where' restore option must not be specified +\item The {\bf Where} restore option must not be specified \item Each Database directory must be marked as a whole. You cannot just select (say) the .edb file and not the others. \item If a Storage Group is restored, the directory of the Storage Group @@ -521,8 +558,8 @@ the following provisos: \item It is possible to restore only a subset of the available log files, but they {\bf must} be contiguous. Exchange will fail to restore correctly if a log file is missing from the sequence of log files -\item Each database to be restored must be dismounted and marked as 'Can be - overwritten by restore' +\item Each database to be restored must be dismounted and marked as "Can be + overwritten by restore" \item If an entire Storage Group is to be restored (eg all databases and logs in the Storage Group), then it is best to manually delete the database files from the server (eg C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+mdbdata\verb+\+*) @@ -534,11 +571,11 @@ the following provisos: The concept of the Recovery Storage Group is well documented by Microsoft \elink{http://support.microsoft.com/kb/824126}{http://support.microsoft.com/kb/824126}, -but to briefly summarise... +but to briefly summarize... Microsoft Exchange allows the creation of an additional Storage Group called the Recovery Storage Group, which is used to restore an older -copy of a database (eg before a mailbox was deleted) into without +copy of a database (e.g. before a mailbox was deleted) into without messing with the current live data. This is required as the Standard and Small Business Server versions of Exchange can not ordinarily have more than one Storage Group.