From: Kern Sibbald Date: Sun, 12 Nov 2006 12:47:33 +0000 (+0000) Subject: Update docs X-Git-Tag: Release-2.0.0~307 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=37b03271945476efae844a074bb12541e8ddc845;p=bacula%2Fdocs Update docs --- diff --git a/docs/developers/version.tex b/docs/developers/version.tex index 24522f04..a2bc60d6 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -1.39.26 (14 October 2006) +1.39.28 (12 November 2006) diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index 24522f04..a2bc60d6 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -1.39.26 (14 October 2006) +1.39.28 (12 November 2006) diff --git a/docs/manual/configure.tex b/docs/manual/configure.tex index d4bd15d1..c633a6d3 100644 --- a/docs/manual/configure.tex +++ b/docs/manual/configure.tex @@ -105,7 +105,7 @@ blackslashes and double quotes ("). Please note, however, that Bacula resource names as well as certain other names (e.g. Volume names) must contain only letters (including ISO accented letters), numbers, and a few special characters (space, underscore, ...). -All other characters and punctuation are illegal. +All other characters and punctuation are invalid. \label{Includes} \subsubsection*{Including other Configuration Files} diff --git a/docs/manual/console.tex b/docs/manual/console.tex index 8a405072..2be74df0 100644 --- a/docs/manual/console.tex +++ b/docs/manual/console.tex @@ -494,7 +494,7 @@ label storage=\lt{}storage-name\gt{} volume=\lt{}volume-name\gt{} The Volume name is restricted to letters, numbers, and the special characters hyphen ({\bf -}), underscore ({\bf \_}), colon ({\bf :}), and - period ({\bf .}). All other characters including a space are illegal. + period ({\bf .}). All other characters including a space are invalid. This restriction is to ensure good readability of Volume names to reduce operator errors. diff --git a/docs/manual/faq.tex b/docs/manual/faq.tex index e27eb16c..2a21e723 100644 --- a/docs/manual/faq.tex +++ b/docs/manual/faq.tex @@ -534,24 +534,26 @@ specify. Please see: \index[general]{Compression} There are two kinds of compression. One is tape compression. This is done by the tape drive hardware, and you either enable or disable it with system - tools such as {\bf mt}. This compression works independently of Bacula. + tools such as {\bf mt}. This compression works independently of Bacula, + and when it is enabled, you should not use the Bacula software + compression. - Bacula also has compression code, which is normally used only when - backing up to file Volumes. There are two conditions for this - "software" to become enabled. + Bacula also has software compression code in the File daemons, which you + normally need to enable only when backing up to file Volumes. There are + two conditions necessary to enable the Bacula software compression. \begin{enumerate} -\item You must have the zip development libraries loaded on your system when - building Bacula and Bacula must find this library, normally {\bf - /usr/lib/libz.a}. On RedHat systems, this library is provided by the {\bf - zlib-devel} rpm. +\item You must have the zip development libraries loaded on your system + when building Bacula and Bacula must find this library, normally {\bf + /usr/lib/libz.a}. On RedHat systems, this library is provided by the + {\bf zlib-devel} rpm. - If the library is found by Bacula during the {\bf ./configure} it will be - mentioned in the {\bf config.out} line by: + If the library is found by Bacula during the {\bf ./configure} it will + be mentioned in the {\bf config.out} line by: \footnotesize \begin{verbatim} - ZLIB support: yes + ZLIB support: yes \end{verbatim} \normalsize @@ -569,14 +571,13 @@ There are several reasons why Bacula will request a new tape. \begin{itemize} \item There is an I/O error on the tape. Bacula prints an error message and requests a new tape. Bacula does not attempt to continue writing after an -I/O - error. + I/O error. \item Bacula encounters and end of medium on the tape. This is not always distinguishable from an I/O error. \item You have specifically set some size limitation on the tape. For example the {\bf Maximum Volume Bytes} or {\bf Maximum Volume Files} in the Director's Pool resource, or {\bf Maximum Volume Size} in the Storage - daemon's Device resource. + daemon's Device resource. \end{itemize} \label{LevelChanging} diff --git a/docs/manual/restore.tex b/docs/manual/restore.tex index 1f5ff084..a807f010 100644 --- a/docs/manual/restore.tex +++ b/docs/manual/restore.tex @@ -617,7 +617,6 @@ encounter, and for same machine restores, how to avoid them. \end{itemize} \label{Windows} - \subsection*{Restoring on Windows} \index[general]{Restoring on Windows } \index[general]{Windows!Restoring on } diff --git a/docs/manual/version.tex b/docs/manual/version.tex index 24522f04..a2bc60d6 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.39.26 (14 October 2006) +1.39.28 (12 November 2006) diff --git a/docs/manual/win32.tex b/docs/manual/win32.tex index 5358b632..9c98136b 100644 --- a/docs/manual/win32.tex +++ b/docs/manual/win32.tex @@ -286,16 +286,17 @@ use the ACPI power management timer as a high-resolution counter on Windows \index[general]{Considerations!Windows Compatibility} \addcontentsline{toc}{subsection}{Windows Compatibility Considerations} -If any applications are running during the backup and they have files -opened exclusively, Bacula will not be able to backup those files, so be -sure you close your applications (or tell your users to close their -applications) before the backup. Fortunately, -most Microsoft applications do not open -files exclusively so that they can be backed up. However, you will need to -experiment. In any case, if Bacula cannot open the file, it will print an -error message, so you will always know which files were not backed up. -For version 1.37.25 and greater, see the section below on -Volume Shadow Copy Service. +If you are not using the VSS (Volume Shadow Copy) option described in the +next section of this chapter, and if any applications are running during +the backup and they have files opened exclusively, Bacula will not be able +to backup those files, so be sure you close your applications (or tell your +users to close their applications) before the backup. Fortunately, most +Microsoft applications do not open files exclusively so that they can be +backed up. However, you will need to experiment. In any case, if Bacula +cannot open the file, it will print an error message, so you will always +know which files were not backed up. For version 1.37.25 and greater, see +the section below on Volume Shadow Copy Service that permits backing up any +file. During backup, Bacula doesn't know about the system registry, so you will either need to write it out to an ASCII file using {\bf regedit~~/e} or use a @@ -308,10 +309,9 @@ gives some distinct advantages and some disadvantages. First, the advantages are that on WinNT/2K/XP systems, the security and ownership information is now backed up. In addition, with the exception of -files in exclusive use by another program (a major disaster for backup -programs on Windows), Bacula can now access all system files. This means -that when you restore files, the security and ownership information will be -restored on WinNT/2K/XP along with the data. +files in exclusive use by another program, Bacula can now access all system +files. This means that when you restore files, the security and ownership +information will be restored on WinNT/2K/XP along with the data. The disadvantage of the Windows backup API calls is that it produces non-portable backups. That is files and their data that are backed up on @@ -321,8 +321,15 @@ WinNT can be restored on WinXP, but this remains to be seen in practice (not yet tested). In addition, the stand-alone tools such as {\bf bls} and {\bf bextract} cannot be used to retrieve the data for those files because those tools are not available on Windows. All restores must use the Bacula -{\bf restore} command. This restriction is mentioned for completeness, but -in practice should not create any problems. +{\bf restore} command. As of Bacula 1.39.x, thanks to Thorsten Engel, this +restriction is removed, and Bacula should be able to read non-portable +backups on any system and restore the data appropriately. However, +on a system that does not have the BackupRead/BackupWrite calls (older +Windows versions and all Unix/Linux machines), though the file data +can be restored, the Windows security and access control data will not be restored. +This means that a standard set of access permissions will be set for +such restored files. + As a default, Bacula backs up Windows systems using the Windows API calls. If you want to backup data on a WinNT/2K/XP system and restore it on a @@ -351,8 +358,6 @@ WinNT/2K/XP specific security and ownership information will be lost. The following matrix will give you an idea of what you can expect. Thanks to Marc Brueckner for doing the tests: -+ - \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status} \begin{longtable}{|l|l|p{2.8in}|} \hline @@ -383,9 +388,12 @@ message) } \\ \hline {Linux} & {WinMe} & {Works } \\ \hline {Linux} & {WinXP} & {Works (SYSTEM permissions)} \\ \hline - \end{longtable} +Note: with Bacula versions 1.39.x and later, non-portable Windows data can +be restore to any machine. + + \label{VSS} \subsection*{Volume Shadow Copy Service} \index[general]{Volume Shadow Copy Service} @@ -567,6 +575,43 @@ Please see the \ilink{Restore Chapter}{Windows} of this manual for problems that you might encounter doing a restore. +subsection*{Windows Backup Problems} +\index[general]{Problems!Windows Backup} +\index[general]{Windows Backup Problems} +\addcontentsline{toc}{subsection}{Windows Backup Problems} +If during a Backup, you get the message: +{\bf ERR=Access is denied} and you are using the portable option, +you should try both adding both the non-portable (backup API) and +the Volume Shadow Copy options to your Director's conf file. + +In the Options resource: +\footnotesize +\begin{verbatim} +portable = no +\end{verbatim} +\normalsize + +In the FileSet resource: +\footnotesize +\begin{verbatim} +enablevss = yes +\end{verbatim} +\normalsize + +In general, specifying these two options should allow you to backup +any file on a Windows system. However, in some cases, if users +have allowed to have full control of their folders, even system programs +such a Bacula can be locked out. In this case, you must identify +which folders or files are creating the problem and do the following: + +\begin{enumerate} +\item Grant ownership of the file/folder to the Administrators group, +with the option to replace the owner on all child objects. +\item Grant full control permissions to the Administrators group, +and change the user's group to only have Modify permission to +the file/folder and all child objects. + +Thanks to Georger Araujo for the above information. \subsection*{Windows Ownership and Permissions Problems} \index[general]{Problems!Windows Ownership and Permissions}