From: Kern Sibbald Date: Sat, 27 May 2017 14:08:53 +0000 (+0200) Subject: Fix various typos that were reported X-Git-Tag: Release-7.9.1~1 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=6077758f403a3ce280069460a9cf99194d18879e;p=bacula%2Fdocs Fix various typos that were reported --- diff --git a/docs/manuals/en/main/basejob.tex b/docs/manuals/en/main/basejob.tex index 7429fa70..79ab79ae 100644 --- a/docs/manuals/en/main/basejob.tex +++ b/docs/manuals/en/main/basejob.tex @@ -2,25 +2,23 @@ \index[general]{Base Jobs} \index[general]{File Deduplication} \label{basejobs} -A base job is sort of like a Full save except that you will want the FileSet to -contain only files that are unlikely to change in the future (i.e. a snapshot -of most of your system after installing it). After the base job has been run, -when you are doing a Full save, you specify one or more Base jobs to be used. -All files that have been backed up in the Base job/jobs but not modified will -then be excluded from the backup. During a restore, the Base jobs will be -automatically pulled in where necessary. +A base job is sort of like a Full save except that you will want the +FileSet to contain only files that are unlikely to change in the future +(i.e. a snapshot of most of your system after installing it). After the +base job has been run, when you are doing a Full save, you specify one or +more Base jobs to be used. All files that have been backed up in the Base +job/jobs but not modified will then be excluded from the backup. During a +restore, the Base jobs will be automatically pulled in where necessary. -This is something none of the competition does, as far as we know (except -perhaps BackupPC, which is a Perl program that saves to disk only). It is big -win for the user, it makes Bacula stand out as offering a unique optimization -that immediately saves time and money. Basically, imagine that you have 100 -nearly identical Windows or Linux machine containing the OS and user files. -Now for the OS part, a Base job will be backed up once, and rather than making -100 copies of the OS, there will be only one. If one or more of the systems -have some files updated, no problem, they will be automatically restored. +This can be a very nice optimization for your backups. Basically, imagine +that you have 100 nearly identical Windows or Linux machines containing the +OS and user files. Now for the OS part, a Base job will be backed up once, +and rather than making 100 copies of the OS, there will be only one. If +one or more of the systems have some files updated, no problem, they will +be automatically saved and restored. -A new Job directive \texttt{Base=Jobx, Joby...} permits to specify the list of -files that will be used during Full backup as base. +A new Job directive \texttt{Base=Jobx, Joby...} permits you to specify the +list of jobs that will be used during a Full backup as base. \begin{verbatim} Job { @@ -62,12 +60,12 @@ FileSet { \end{verbatim} \textbf{Important note}: The current implementation doesn't permit to scan -volume with \textbf{bscan}. The result wouldn't permit to restore files +a Volume with \textbf{bscan}. The result wouldn't properly restore files easily. It is recommended to not prune File or Job records with Basejobs. \smallskip -Added in version 8.0.5, the new ``M'' option letter for the Accurate directive +Added the new ``M'' option letter for the Accurate directive in the FileSet Options block, which allows comparing the modification time and/or creation time against the last backup timestamp. This is in contrast to the existing options letters ``m'' and/or ``c'', mtime and ctime, which are checked diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex index 2293665c..a41c19cd 100644 --- a/docs/manuals/en/main/dirdconf.tex +++ b/docs/manuals/en/main/dirdconf.tex @@ -3251,7 +3251,7 @@ defined. \item [DB Port = \lt{}port\gt{}] \index[dir]{DB Port} - \index[dir]{Directive!DB Port} + \index[dir]{Directive!DBPort} This defines the port to be used in conjunction with {\bf DB Address} to access the database if it is on another machine. This directive is used only by MySQL and PostgreSQL and is ignored by SQLite if provided. This diff --git a/docs/manuals/en/main/install.tex b/docs/manuals/en/main/install.tex index babc4dcb..356a6ff9 100644 --- a/docs/manuals/en/main/install.tex +++ b/docs/manuals/en/main/install.tex @@ -1003,9 +1003,13 @@ $ nm /usr/local/lib/libpq.a | grep mutex simply use {\bf {-}{\-}with-postgresql}. Note, for Bacula to be configured properly, you must specify one - of the four database options supported. That is: - {-}{\-}with-sqlite, {-}{\-}with-sqlite3, {-}{\-}with-mysql, or + of the three database options supported. That is: + {-}{\-}with-sqlite3, {-}{\-}with-mysql, or {-}{\-}with-postgresql, otherwise the ./configure will fail. +\smallskip + Note: SQLite is no longer supported. The code remains in Bacula but + we no longer test it. + \item [ {-}{\-}with-openssl=\lt{}path\gt{}] This configuration option is necessary if you want to enable TLS (ssl),