From: Thomas Glatthor Date: Mon, 18 Aug 2008 08:14:07 +0000 (+0000) Subject: Kile X-Git-Tag: Release-3.0.0~1079 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=5020cc17e739624a94c9fa61f56d8e922e627941;p=bacula%2Fdocs Kile --- diff --git a/docs/manuals/de/concepts/autochangerres.tex b/docs/manuals/de/concepts/autochangerres.tex index 4a322d4e..6080891c 100644 --- a/docs/manuals/de/concepts/autochangerres.tex +++ b/docs/manuals/de/concepts/autochangerres.tex @@ -6,7 +6,7 @@ In der Autochanger-Konfiguration k\"{o}nnen Autochanger mit einzelnen oder mehreren Laufwerken angelegt werden, indem eine oder mehrere Ger\"{a}tekonfigurationen zu einer Einheit, die Bacula Autochanger nennt, -gruppiert werden. (Autochangerherrsteller nennen so etwas auch "Tape Library") +gruppiert werden. (Autochangerherrsteller nennen so etwas auch "`Tape Library"') Damit Ihr Autochanger korrekt funktioniert, {\bf m\"{u}ssen} Sie eine Autochanger-Konfiguration in der Konfigurationsdatei diff --git a/docs/manuals/de/concepts/autochangers.tex b/docs/manuals/de/concepts/autochangers.tex index b458035b..e36ab588 100644 --- a/docs/manuals/de/concepts/autochangers.tex +++ b/docs/manuals/de/concepts/autochangers.tex @@ -48,7 +48,7 @@ dass Bacula {\bf chio} benutzen l\"{a}sst. Bacula unterst\"{u}tzt Autochanger mir Barcode-Lesern, dieses beinhaltet zwei Consolen-Kommandos: {\bf label barcodes} und {\bf update slots}. -Im Abschnitt "Barcode Unterst\"{u}tzung" (siehe unten) erfolgt eine detaillierte Beschreibung dieser Kommandos. +Im Abschnitt "`Barcode Unterst\"{u}tzung"' (siehe unten) erfolgt eine detaillierte Beschreibung dieser Kommandos. Momentan beinhaltet die Autochanger-Unterst\"{u}tzung keine Stacker und Silos, und auch keine Laufwerks-Reinigung (Cleaning). Stacker und Silos werden nicht unterst\"{u}tzt, diff --git a/docs/manuals/de/concepts/bugs.tex b/docs/manuals/de/concepts/bugs.tex index 6f4b9b6a..f9764203 100644 --- a/docs/manuals/de/concepts/bugs.tex +++ b/docs/manuals/de/concepts/bugs.tex @@ -15,5 +15,5 @@ ver\"{o}ffentlicht. Das Verzeichnis {\bf patches} im aktuellen SVN enth\"{a}lt eine Liste aller Programmkorrekturen die f\"{u}r \"{a}ltere Bacula-Versionen ver\"{o}ffentlicht wurden. -Eine "grobe" \"{U}bersicht der momentanen Arbeit und bekannter Probleme befindet sich +Eine "`grobe"' \"{U}bersicht der momentanen Arbeit und bekannter Probleme befindet sich auch in der Datei {\bf kernstodo} im Hauptverzeichnis der Bacula-Programmquellen. diff --git a/docs/manuals/de/concepts/concepts.tex b/docs/manuals/de/concepts/concepts.tex index b383be02..8119bff3 100644 --- a/docs/manuals/de/concepts/concepts.tex +++ b/docs/manuals/de/concepts/concepts.tex @@ -36,7 +36,7 @@ \parskip 10pt \parindent 0pt -\title{\includegraphics{./bacula-logo.eps} \\ \bigskip +\title{\includegraphics{\idir bacula-logo.eps} \\ \bigskip \Huge{Bacula Konzepte und \"{U}berblick} \begin{center} \large{Es kommt bei Nacht und saugt die lebenswichtigen Daten aus Ihren Computern.} diff --git a/docs/manuals/de/concepts/general.tex b/docs/manuals/de/concepts/general.tex index e17c017f..26d2900b 100644 --- a/docs/manuals/de/concepts/general.tex +++ b/docs/manuals/de/concepts/general.tex @@ -63,7 +63,7 @@ dabei aber als freie Software unter der GNU Software Lizenz Version 2 verf\"{u}g Bacula besteht aus den folgenden f\"{u}nf Hauptkomponenten bzw. Diensten: \addcontentsline{lof}{figure}{Bacula Applications} -\includegraphics{./bacula-applications.eps} +\includegraphics{\idir bacula-applications.eps} (Dank an Aristedes Maniatis f\"{u}r diese und die folgende Grafik) \subsection*{Bacula Director} @@ -178,7 +178,7 @@ erstellt werden, die bestimmte Eintr\"{a}ge (bzw. Ressourcen) enthalten. Die folgende Abbildung gibt hierzu eine \"{U}bersicht: \addcontentsline{lof}{figure}{Bacula Objects} -\includegraphics{./bacula-objects.eps} +\includegraphics{\idir bacula-objects.eps} \section{Die in diesem Dokument verwendeten Konventionen} \index[general]{Die in diesem Dokument verwendeten Konventionen } @@ -536,4 +536,4 @@ Director den \"{U}berblick \"{u}ber die Aktionen und pflegt die Katalog-Datenbank. \addcontentsline{lof}{figure}{Interaktionen zwischen den Bacula-Diensten} -\includegraphics{./flow.eps} +\includegraphics{\idir flow.eps} diff --git a/docs/manuals/de/concepts/lesser.tex b/docs/manuals/de/concepts/lesser.tex index 6fcc81ed..b20dc7f8 100644 --- a/docs/manuals/de/concepts/lesser.tex +++ b/docs/manuals/de/concepts/lesser.tex @@ -144,7 +144,7 @@ therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. -We call this license the "Lesser" General Public License because it does +We call this license the "`Lesser"' General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the @@ -171,8 +171,8 @@ Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification -follow. Pay close attention to the difference between a "work based on the -library" and a "work that uses the library". The former contains code +follow. Pay close attention to the difference between a "`work based on the +library"' and a "`work that uses the library"'. The former contains code derived from the library, whereas the latter must be combined with the library in order to run. @@ -186,22 +186,22 @@ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION {\bf 0.} This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser -General Public License (also called "this License"). Each licensee is -addressed as "you". +General Public License (also called "`this License"'). Each licensee is +addressed as "`you"'. A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. -The "Library", below, refers to any such software library or work which has -been distributed under these terms. A "work based on the Library" means +The "`Library"', below, refers to any such software library or work which has +been distributed under these terms. A "`work based on the Library"' means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term -"modification".) +"`modification"'.) -"Source code" for a work means the preferred form of the work for making +"`Source code"' for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the @@ -299,17 +299,17 @@ object code. {\bf 5.} A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, -is called a "work that uses the Library". Such a work, in isolation, is not +is called a "`work that uses the Library"'. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. -However, linking a "work that uses the Library" with the Library creates an +However, linking a "`work that uses the Library"' with the Library creates an executable that is a derivative of the Library (because it contains portions -of the Library), rather than a "work that uses the library". The executable +of the Library), rather than a "`work that uses the library"'. The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. -When a "work that uses the Library" uses material from a header file that is +When a "`work that uses the Library"' uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if @@ -328,7 +328,7 @@ containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. {\bf 6.} As an exception to the Sections above, you may also combine or link a -"work that uses the Library" with the Library to produce a work containing +"`work that uses the Library"' with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. @@ -345,7 +345,7 @@ Also, you must do one of these things: machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete -machine-readable "work that uses the Library", as object code and/or source +machine-readable "`work that uses the Library"', as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will @@ -368,7 +368,7 @@ made with. materials or that you have already sent this user a copy. \end{itemize} -For an executable, the required form of the "work that uses the Library" +For an executable, the required form of the "`work that uses the Library"' must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either @@ -462,8 +462,8 @@ be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library -specifies a version number of this License which applies to it and "any later -version", you have the option of following the terms and conditions either of +specifies a version number of this License which applies to it and "`any later +version"', you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation. @@ -481,7 +481,7 @@ promoting the sharing and reuse of software generally. {\bf 15.} BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE -THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR +THE LIBRARY "`AS IS"' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY diff --git a/docs/manuals/de/concepts/license.tex b/docs/manuals/de/concepts/license.tex index e6d37e19..63927176 100644 --- a/docs/manuals/de/concepts/license.tex +++ b/docs/manuals/de/concepts/license.tex @@ -99,7 +99,7 @@ NO WARRANTY BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE -PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, +PROGRAM "`AS IS"' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, diff --git a/docs/manuals/de/concepts/python.tex b/docs/manuals/de/concepts/python.tex index 40e1b2e0..41e10c27 100644 --- a/docs/manuals/de/concepts/python.tex +++ b/docs/manuals/de/concepts/python.tex @@ -151,7 +151,7 @@ The following are the read-only attributes provided by the bacula object. \item [Name] \item [ConfigFile] \item [WorkingDir] -\item [Version] string consisting of "Version Build-date" +\item [Version] string consisting of "`Version Build-date"' \end{description} diff --git a/docs/manuals/de/concepts/recycling.tex b/docs/manuals/de/concepts/recycling.tex index a1eb3c54..2218af03 100644 --- a/docs/manuals/de/concepts/recycling.tex +++ b/docs/manuals/de/concepts/recycling.tex @@ -126,7 +126,7 @@ details of the Files backed up. In addition, without the File records, you cannot use the Console restore command to restore the files. When a Job record is pruned, the Volume (Media record) for that Job can still -remain in the database, and if you do a "list volumes", you will see the +remain in the database, and if you do a "`list volumes"', you will see the volume information, but the Job records (and its File records) will no longer be available. @@ -135,7 +135,7 @@ also prevents the catalog from growing to be too large. You choose the retention periods in function of how many files you are backing up and the time periods you want to keep those records online, and the size of the database. You can always re-insert the records (with 98\% of the original data) -by using "bscan" to scan in a whole Volume or any part of the volume that +by using "`bscan"' to scan in a whole Volume or any part of the volume that you want. By setting {\bf AutoPrune} to {\bf yes} you will permit {\bf Bacula} to @@ -327,7 +327,7 @@ A few points from Alan Brown to keep in mind: \item If the Job, File, and Volume retention periods are different, then it's common to see a tape with no files or jobs listed in the database, - but which is still not marked as "purged". + but which is still not marked as "`purged"'. \end{enumerate} diff --git a/docs/manuals/de/concepts/restore.tex b/docs/manuals/de/concepts/restore.tex index 05e23fd6..48fb2c33 100644 --- a/docs/manuals/de/concepts/restore.tex +++ b/docs/manuals/de/concepts/restore.tex @@ -269,7 +269,7 @@ $ \normalsize Depending on the number of {\bf JobFiles} for each JobId, the {\bf Building -directory tree ..."} can take a bit of time. If you notice ath all the +directory tree ...} can take a bit of time. If you notice ath all the JobFiles are zero, your Files have probably been pruned and you will not be able to select any individual files -- it will be restore everything or nothing. @@ -669,7 +669,7 @@ The format is very close to that used by sed or Perl (\texttt{s/replace this/by Each field is delimited by a separator specified by the user as the first character of the expression. The separator can be one of the following: \begin{verbatim} - = / ! ; % : , ~ # = & + = / !�; % : , ~ # = & \end{verbatim} You can use several expressions separated by a commas. diff --git a/docs/manuals/de/concepts/spooling.tex b/docs/manuals/de/concepts/spooling.tex index 9d1e4a9a..c55eeaa7 100644 --- a/docs/manuals/de/concepts/spooling.tex +++ b/docs/manuals/de/concepts/spooling.tex @@ -29,8 +29,8 @@ important purposes. File daemon, you may actually slow down the overall backup. \end{itemize} -Data spooling is exactly that "spooling". It is not a way to first write a -"backup" to a disk file and then to a tape. When the backup has only been +Data spooling is exactly that "`spooling"'. It is not a way to first write a +"`backup"' to a disk file and then to a tape. When the backup has only been spooled to disk, it is not complete yet and cannot be restored until it is written to tape. diff --git a/docs/manuals/de/concepts/tutorial.tex b/docs/manuals/de/concepts/tutorial.tex index 84517880..9cee52b3 100644 --- a/docs/manuals/de/concepts/tutorial.tex +++ b/docs/manuals/de/concepts/tutorial.tex @@ -702,7 +702,7 @@ Wenn Sie jetzt {\bf yes} eingeben, werden die Datein unterhalb von {\bf /tmp/bacula-restores} wiederhergestellt. Dies ist der Standard f\"{u}r die Wiederherstellung und l\"{a}sst sich \"{u}ber {\bf mod} und {\bf Where} anpassen. Um die Dateien an ihrem originalen Ort widerherzustellen, -m\"{u}ssen Sie {\nf Where} entweder leer lassen oder auf {\bf /} setzen. +m\"{u}ssen Sie {\bf Where} entweder leer lassen oder auf {\bf /} setzen. In diesem Beispiel antworten Sie bitte einfach mit {\bf yes} um die Wiederherstellung zu starten. Warten Sie inene kurzen Moment und geben Sie {\bf messages} ein. Wenn der Wiederherstellungs-Job beendet ist, sehen Sie @@ -937,7 +937,7 @@ Anschlie{\ss}end benutzen Sie das {\bf label}-Kommando um das neue Volume zu lab Das label-Kommando veranla{\ss}t den Storage-Dienst eine Software-Markierung auf das Volume zu schreiben. Wenn das erfolgreich war, wird das neue Volume dem entsprechendem Pool zugeordnet und das Volume in das Laufwerk geladen. Weiter oben -in diesem Kapitel finden Sie weitere Information bez\"{u\}glich des label-Kommandos. +in diesem Kapitel finden Sie weitere Information bez\"{u}glich des label-Kommandos. Das Ergebnis ist, dass Bacula den Backup-Job mit dem neuen Volume fortsetzen kann. @@ -976,7 +976,7 @@ folgen Sie bitte diesen zus\"{a}tzlichen Schritten: {\bf mt \ -f \ /dev/st0 \ rewind} und {\bf mt \ -f \ /dev/st0 \ weof}, wobei Sie nat\"{u}rlich den korrekten Device-Namen f\"{u}r Ihr System benutzen m\"{u}ssen -\item Dann k\"{o\nnen Sie, wie gewohnt, in dem Console-Programm das +\item Dann k\"{o}nnen Sie, wie gewohnt, in dem Console-Programm das {\bf label}-Kommando benutzen um das neue Volume-Label zu erstellen. \item Falls das Volume danach nicht automatischin das Laufwerk geladen wird, benutzen Sie daf\"{u}r das {\bf mount}-Kommando. diff --git a/docs/manuals/de/concepts/update_version b/docs/manuals/de/concepts/update_version deleted file mode 100755 index 5c2e0092..00000000 --- a/docs/manuals/de/concepts/update_version +++ /dev/null @@ -1,10 +0,0 @@ -#!/bin/sh -# -# Script file to update the Bacula version -# -out=/tmp/$$ -VERSION=`sed -n -e 's/^.*VERSION.*"\(.*\)"$/\1/p' /home/kern/bacula/k/src/version.h` -DATE=`sed -n -e 's/^.*[ \t]*BDATE.*"\(.*\)"$/\1/p' /home/kern/bacula/k/src/version.h` -. ./do_echo -sed -f ${out} version.tex.in >version.tex -rm -f ${out} diff --git a/docs/manuals/de/concepts/vars.tex b/docs/manuals/de/concepts/vars.tex index f28f714b..8aee9c81 100644 --- a/docs/manuals/de/concepts/vars.tex +++ b/docs/manuals/de/concepts/vars.tex @@ -28,7 +28,7 @@ controlled loop, support of arithmetic expressions in the loop start, step and end conditions, and recursive expansion. When using variable expansion characters in a Volume Label Format record, the -format should always be enclosed in double quotes ({\bf "}). +format should always be enclosed in double quotes. For example, {\bf \$\{HOME\}} will be replaced by your home directory as defined in the environment. If you have defined the variable {\bf xxx} to be @@ -89,7 +89,7 @@ prior to executing Bacula. Environment variables may be either scalar or an array, where the elements of the array are referenced by subscripting the variable name (e.g. {\bf \$\{Months[3]\}}). Environment variable arrays are defined by separating the elements with a vertical bar ({\bf |}), thus {\bf -set Months="Jan|Feb|Mar|Apr|..."} defines an environment variable named +set Months="`Jan|Feb|Mar|Apr|..."'} defines an environment variable named {\bf Month} that will be treated as an array, and the reference {\bf \$\{Months[3]\}} will yield {\bf Mar}. The elements of the array can have differing lengths. diff --git a/docs/manuals/de/concepts/verify.tex b/docs/manuals/de/concepts/verify.tex index 17261587..3a2130fd 100644 --- a/docs/manuals/de/concepts/verify.tex +++ b/docs/manuals/de/concepts/verify.tex @@ -42,7 +42,7 @@ the files on the Client to the last {\bf InitCatalog} that is stored in the catalog and to report any differences. See the example below for the format of the output. -You decide what files you want to form your "snapshot" by specifying them in +You decide what files you want to form your "`snapshot"' by specifying them in a {\bf FileSet} resource, and normally, they will be system files that do not change, or that only certain features change. diff --git a/docs/manuals/de/concepts/win32.tex b/docs/manuals/de/concepts/win32.tex index dbcf9254..3b1a02e8 100644 --- a/docs/manuals/de/concepts/win32.tex +++ b/docs/manuals/de/concepts/win32.tex @@ -81,18 +81,18 @@ Bacula, so we don't recommend that option. icon. The actual name of the icon will vary from one release version to another. -\includegraphics{./win32-nsis.eps} winbacula-1.xx.0.exe +\includegraphics{\idir win32-nsis.eps} winbacula-1.xx.0.exe \item Once launched, the installer wizard will ask you if you want to install Bacula. \addcontentsline{lof}{figure}{Win32 Client Setup Wizard} -\includegraphics{./win32-welcome.eps} +\includegraphics{\idir win32-welcome.eps} \item Next you will be asked to select the installation type. \addcontentsline{lof}{figure}{Win32 Installation Type} -\includegraphics{./win32-installation-type.eps} +\includegraphics{\idir win32-installation-type.eps} \item If you proceed, you will be asked to select the components to be @@ -102,7 +102,7 @@ Bacula, so we don't recommend that option. following: \addcontentsline{lof}{figure}{Win32 Component Selection Dialog} -\includegraphics{./win32-pkg.eps} +\includegraphics{\idir win32-pkg.eps} \index[general]{Upgrading} \item If you are installing for the first time, you will be asked to @@ -117,35 +117,35 @@ Bacula, so we don't recommend that option. \addcontentsline{lof}{figure}{Win32 Configure} -\includegraphics{./win32-config.eps} +\includegraphics{\idir win32-config.eps} \item While the various files are being loaded, you will see the following dialog: \addcontentsline{lof}{figure}{Win32 Install Progress} - \includegraphics{./win32-installing.eps} + \includegraphics{\idir win32-installing.eps} \item Finally, the finish dialog will appear: \addcontentsline{lof}{figure}{Win32 Client Setup Completed} - \includegraphics{./win32-finish.eps} + \includegraphics{\idir win32-finish.eps} \ \end{itemize} That should complete the installation process. When the Bacula File Server is -ready to serve files, an icon \includegraphics{./idle.eps} representing a +ready to serve files, an icon \includegraphics{\idir idle.eps} representing a cassette (or tape) will appear in the system tray -\includegraphics{./tray-icon.eps}; right click on it and a menu will appear.\\ -\includegraphics{./menu.eps}\\ +\includegraphics{\idir tray-icon.eps}; right click on it and a menu will appear.\\ +\includegraphics{\idir menu.eps}\\ The {\bf Events} item is currently unimplemented, by selecting the {\bf Status} item, you can verify whether any jobs are running or not. When the Bacula File Server begins saving files, the color of the holes in the -cassette icon will change from white to green \includegraphics{./running.eps}, +cassette icon will change from white to green \includegraphics{\idir running.eps}, and if there is an error, the holes in the cassette icon will change to red -\includegraphics{./error.eps}. +\includegraphics{\idir error.eps}. If you are using remote desktop connections between your Windows boxes, be warned that that tray icon does not always appear. It will always be visible @@ -459,8 +459,8 @@ RDBMS to produce consistent file copies. VSS aware applications are called VSS Writers, they register with the OS so that when Bacula wants to do a Snapshot, the OS will notify the register Writer programs, which may then create a consistent state in their application, which will be backed up. -Examples for these writers are "MSDE" (Microsoft database -engine), "Event Log Writer", "Registry Writer" plus 3rd +Examples for these writers are "`MSDE"' (Microsoft database +engine), "`Event Log Writer"', "`Registry Writer"' plus 3rd party-writers. If you have a non-vss aware application (e.g. SQL Anywhere or probably MySQL), a shadow copy is still generated and the open files can be backed up, but there is no guarantee @@ -508,9 +508,9 @@ JobId 1 Job NightlySave.2005-07-23_13.25.45 is running. SDReadSeqNo=5 fd=352 \end{verbatim} \normalsize -Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..." +Here, you see under Running Jobs that JobId 1 is "`VSS Backup Job started ..."' This means that VSS is enabled for that job. If VSS is not enabled, it will -simply show "Backup Job started ..." without the letters VSS. +simply show "`Backup Job started ..."' without the letters VSS. The second way to know that the job was backed up with VSS is to look at the Job Report, which will look something like the following: @@ -527,7 +527,7 @@ Job Report, which will look something like the following: \end{verbatim} \normalsize In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if -other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the +other drives are backed up, they will be listed on the {\bf Drive(s)="`C"'} You also see the reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means that you will get a consistent snapshot of the data handled by that writer. @@ -546,7 +546,7 @@ The FD hang problems were reported with {\bf MSDEwriter} when: \begin{itemize} \item a local firewall locked local access to the MSDE TCP port (MSDEwriter seems to use TCP/IP and not Named Pipes). -\item msdtcs was installed to run under "localsystem": try running msdtcs +\item msdtcs was installed to run under "`localsystem"': try running msdtcs under networking account (instead of local system) (com+ seems to work better with this configuration). \end{itemize} @@ -705,7 +705,7 @@ The problem appears as a directory which cannot be browsed with Windows Explorer. The symptoms include the following message when you try to click on that directory: -\includegraphics{./access-is-denied.eps} +\includegraphics{\idir access-is-denied.eps} If you encounter this message, the following steps will change the permissions to allow full access. @@ -717,26 +717,26 @@ to allow full access. \item If the following message appears, you can ignore it, and click on {\bf OK}. -\includegraphics{./view-only.eps} +\includegraphics{\idir view-only.eps} You should see something like this: -\includegraphics{./properties-security.eps} +\includegraphics{\idir properties-security.eps} \item click on Advanced \item click on the Owner tab \item Change the owner to something other than the current owner (which is {\bf SYSTEM} in this example as shown below). -\includegraphics{./properties-security-advanced-owner.eps} -\item ensure the "Replace owner on subcontainers and objects" box is +\includegraphics{\idir properties-security-advanced-owner.eps} +\item ensure the "`Replace owner on subcontainers and objects"' box is checked \item click on OK -\item When the message "You do not have permission to read the contents of +\item When the message "`You do not have permission to read the contents of directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace - the directory permissions with permissions granting you Full Control?", click + the directory permissions with permissions granting you Full Control?"', click on Yes. -\includegraphics{./confirm.eps} +\includegraphics{\idir confirm.eps} \item Click on OK to close the Properties tab \end{enumerate}