Update

diff --git a/docs/manuals/en/concepts/concepts.kilepr b/docs/manuals/en/concepts/concepts.kilepr
index f3181fac64f56d93a58353738b7104ebf66a93cd..193159a8ed84800c8b664985ef9364e1e306ca9f 100644 (file)
--- 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=58
+column=41
 encoding=UTF-8
 highlight=LaTeX
-line=938
+line=460
 open=true
 order=0
 

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index b52830f24fb56331a20bf4573006ecee3e518337..901c715ae02fc0d14573611c4a2be9fe1e94d8a9 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -442,22 +442,23 @@ By using different command lines to {\bf bpipe},
 you can backup any kind of data (ASCII or binary) depending
 on the program called.
 
-\section{Microsoft Exchange Server 2003/2007 plugin}
+\section{Microsoft Exchange Server 2003/2007 Plugin}
 
 \subsection{Concepts}
 
 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
-inside it, 'Mailbox Store (SERVER NAME)' and 'Public Folder Store
-(SERVER NAME)', which hold user email and public folders respectively.
+inside it, "Mailbox Store (SERVER NAME)" and 
+"Public Folder Store (SERVER NAME)", 
+which hold user email and public folders respectively.
 
 In the default configuration, Exchange logs everything that happens to
 log files, such that if you have a backup, and all the log files since,
 you can restore to the present time. Each Storage Group has its own set
 of log files and operates independently of any other Storage Groups. At
 the Storage Group level, the logging can be turned off by enabling a
-function called 'Enable circular logging'. At this time the Exchange
+function called "Enable circular logging". At this time the Exchange
 plugin will not function if this option is enabled.
 
 The plugin allows backing up of entire storage groups, and the restoring
@@ -467,16 +468,16 @@ can be simulate by use of the Recovery Storage Group (see below).
 
 \subsection{Installing}
 
-Once the bacula-fd is installed on your Windows server, the Exchange API
-DLL must be copied to the bin directory in the Bacula installation
-directory (eg C:\\Program Files\\Bacula\\bin). The Exchange API DLL is
-named esebcli2.dll and is found in C:\\Program Files\\Exchsrvr\\bin on a
-default Exchange installation.
-
-We plan to make the plugin a bit smarter about finding the
-esebcli2.dll file, so the step here will ultimately only be as a last
-resort, but for now it is required.
+The Exchange plugin requires a DLL that is shipped with Microsoft
+Exchanger Server called {\bf esebcli2.dll}. Assuming Exchange is installed
+correctly the Exchange plugin should find this automatically and run
+without any additional installation.
 
+If the DLL can not be found automatically it will need to be copied into
+the Bacula installation
+directory (eg C:\verb+\+Program Files\verb+\+Bacula\verb+\+bin). The Exchange API DLL is
+named esebcli2.dll and is found in C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+bin on a
+default Exchange installation.
 
 \subsection{Backup up}
 
@@ -521,7 +522,7 @@ the following provisos:
     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:\\Program Files\\Exchsrvr\\mdbdata\\*)
+   database files from the server (eg C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+ mdbdata\verb+\+*)
    as Exchange can get confused by stray log files lying around.
 \end{itemize}
 
@@ -538,21 +539,21 @@ Small Business Server versions of Exchange can not ordinarily have more
 than one Storage Group.
 
 To create the Recovery Storage Group, drill down to the Server in
-Exchange System Manager, right click, and select 'New -> Recovery
-Storage Group...'. Accept or change the file locations and click OK. On
-the Recovery Storage Group, right click and select 'Add Database to
-Recover...' and select the database you will be restoring.
+Exchange System Manager, right click, and select 
+{\bf "New -> Recovery Storage Group..."}. Accept or change the file locations and click OK. On
+the Recovery Storage Group, right click and select 
+{\bf "Add Database to Recover..."} and select the database you will be restoring.
 
 In Bacula, select the Database and the log files, making sure to mark
 the Storage Group directory itself too. Once you have selected the files
 to back up, use the RegexWhere clause to remove the prefix of
-'/@EXCHANGE/Microsoft Information Store/<storage group name>/' and
-replace it with '/@EXCHANGE/Microsoft Information Store/Recovery Storage
-Group/'. Then run the restore.
+"/@EXCHANGE/Microsoft Information Store/\lt{}storage group name\gt{}/" and
+replace it with "/@EXCHANGE/Microsoft Information Store/Recovery Storage Group/". 
+Then run the restore.
 
-\subsection{}Caveats
+\subsection{Caveats}
 
-The 'Enable Circular Logging' option cannot be enabled or the plugin
+The "Enable Circular Logging" option cannot be enabled or the plugin
 will fail.
 
 Exchange insists that a successful Full backup must have taken place if
@@ -567,8 +568,9 @@ other backup application is truncating the log files.
 
 
 
-\section{libdbi framework}
+\section{libdbi Framework}
 As a general guideline, Bacula has support for a few catalog database drivers
+(MySQL, PostgreSQL, SQLite)
 coded natively by the Bacula team.  With the libdbi implementation, which is a
 Bacula driver that uses libdbi to access the catalog, we have an open field to
 use many different kinds database engines following the needs of users.