From fb027a54340bfd65137378ae6e6af13245cce7fc Mon Sep 17 00:00:00 2001 From: Jo Simoens Date: Tue, 17 May 2005 20:33:47 +0000 Subject: [PATCH] some typos fixed --- docs/manual/progs.tex | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/manual/progs.tex b/docs/manual/progs.tex index 97b7d833..8394705e 100644 --- a/docs/manual/progs.tex +++ b/docs/manual/progs.tex @@ -473,7 +473,7 @@ database name ({\bf -b} option), the user name ({\bf -u} option), and/or the password ({\bf -p}) options. As an example, let's suppose that you did a backup to Volume ``Vol001'' and -that sometime later all record of that Volume was pruned or purged from the +that sometime later all records of that Volume were pruned or purged from the database. By using {\bf bscan} you can recreate the catalog entries for that Volume and then use the {\bf restore} command in the Console to restore whatever you want. A command something like: @@ -484,7 +484,7 @@ bscan -c bacula-sd.conf -v -V Vol001 /dev/nst0 \end{verbatim} \normalsize -will give you a give you an idea of what is going to happen without changing +will give you an idea of what is going to happen without changing your catalog. Of course, you may need to change the path to the Storage daemon's conf file, the Volume name, and your tape (or disk) device name. This command must read the entire tape, so if it has a lot of data, it may take a @@ -665,7 +665,7 @@ against it and get valid results. \addcontentsline{toc}{subsubsection}{Using bscan to Correct the Volume File Count} -If the Storage daemon crashes during a backup Job, the catalog will no be +If the Storage daemon crashes during a backup Job, the catalog will not be properly updated for the Volume being used at the time of the crash. This means that the Storage daemon will have written say 20 files on the tape, but the catalog record for the Volume indicates only 19 files. @@ -682,7 +682,7 @@ update only the final Media record for the Volumes read. If you use {\bf bscan} to enter the contents of the Volume into an existing catalog, you should be aware that the records you entered may be immediately -pruned during the next job particularly if the Volume is very old or had been +pruned during the next job, particularly if the Volume is very old or had been previously purged. To avoid this, after running {\bf bscan}, you can manually set the volume status (VolStatus) to {\bf Read-Only} by using the {\bf update} command in the catalog. This will allow you to restore from the volume without @@ -757,7 +757,7 @@ file. As a default, it will look for {\bf bacula-sd.conf} in the current directory. If your configuration file is elsewhere, please use the {\bf -c} option to specify where. -The physical device name must be specified on the command line, and that this +The physical device name must be specified on the command line, and this same device name must be present in the Storage daemon's configuration file read by {\bf btape} @@ -1002,7 +1002,7 @@ The inconsistencies examined are the following: database. If this is the case, you will receive error messages during Jobs warning of duplicate database records. If you are not getting these error messages, there is no reason to run this check. -\item Repair bad Filename records. This checkes and corrects filenames that +\item Repair bad Filename records. This checks and corrects filenames that have a trailing slash. They should not. \item Repair bad Path records. This checks and corrects path names that do not have a trailing slash. They should. @@ -1159,7 +1159,7 @@ disk. It requires: \end{itemize} SQLite databases and DVD burning are not supported by {\bf bimagemgr} at this -time, but both planned for future releases. +time, but both are planned for future releases. \subsubsection*{bimagemgr installation} \index[general]{bimagemgr!Installation } @@ -1179,12 +1179,12 @@ http://localhost/cgi-bin/bimagemgr.pl} will produce a display as shown below in Figure 1. The program will query the bacula database and display all volume files with the date last written and the date last burned to disk. If a volume needs to be burned (last written is newer than last burn date) a ``Burn'' -button will be displayed in the right most column. +button will be displayed in the rightmost column. \addcontentsline{lof}{figure}{Bacula CD Image Manager} \includegraphics{./bimagemgr1.eps} \\Figure 1 -Place a blank CDR disk in your recorder and click a ``Burn'' button. This will +Place a blank CDR disk in your recorder and click the ``Burn'' button. This will cause a pop up window as shown in Figure 2 to display the burn progress. \addcontentsline{lof}{figure}{Bacula CD Image Burn Progress Window} @@ -1194,7 +1194,7 @@ When the burn finishes the pop up window will display the results of cdrecord as shown in Figure 3. Close the pop up window and refresh the main window. The last burn date will be updated and the ``Burn'' button for that volume will disappear. Should you have a failed burn you can reset the last burn date of -that volume by clicking it's ``Reset'' link. +that volume by clicking its ``Reset'' link. \addcontentsline{lof}{figure}{Bacula CD Image Burn Results} \includegraphics{./bimagemgr3.eps} \\Figure 3 @@ -1204,5 +1204,5 @@ In the bottom row of the main display window are two more buttons labeled your bacula catalog on a disk. If you use CDRW disks rather than CDR then ``Blank CDRW'' allows you to erase the disk before re-burning it. Regularly committing your backup volume files and your catalog to disk with {\bf -bimagemgr} insures that you can rebuild easily in the event of some disaster +bimagemgr} ensures that you can rebuild easily in the event of some disaster on the bacula server itself. -- 2.39.5