From: Kern Sibbald Date: Sat, 30 Dec 2006 16:14:39 +0000 (+0000) Subject: Update X-Git-Tag: Release-2.0.0~51 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=2116957ca9753f53c6f267de31657e79bfb898af;p=bacula%2Fdocs Update --- diff --git a/docs/developers/version.tex b/docs/developers/version.tex index a7e70623..9bcc38ba 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -1.39.33 (28 December 2006) +1.39.35 (28 December 2006) diff --git a/docs/home-page/fr/pages/professional.php b/docs/home-page/fr/pages/professional.php index 57110a20..5913b3de 100644 --- a/docs/home-page/fr/pages/professional.php +++ b/docs/home-page/fr/pages/professional.php @@ -129,10 +129,10 @@ Arno Lehmann
- Wittekamp 2
- 30177 Hannover
+ Sandstr. 6
+ 49080 Osnabrück
Germany
- +49 (0) 511 69099508
+ +49 (0) 541 5803396
+49 (0) 160 92008971 (mobile)

Storage, Communication, Backup and Monitoring using diff --git a/docs/home-page/pages/professional.php b/docs/home-page/pages/professional.php index dd4d8209..4b6a1442 100644 --- a/docs/home-page/pages/professional.php +++ b/docs/home-page/pages/professional.php @@ -172,10 +172,10 @@ Arno Lehmann
- Wittekamp 2
- 30177 Hannover
+ Sandstr. 6
+ 49080 Osnabrück
Germany
- +49 (0) 511 69099508
+ +49 (0) 541 5803396
+49 (0) 160 92008971 (mobile)

Storage, Communication, Backup and Monitoring using diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index a7e70623..9bcc38ba 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -1.39.33 (28 December 2006) +1.39.35 (28 December 2006) diff --git a/docs/manual/Makefile.in b/docs/manual/Makefile.in index 6ce1115c..27d61220 100644 --- a/docs/manual/Makefile.in +++ b/docs/manual/Makefile.in @@ -34,14 +34,14 @@ tex: @cp -fp ${IMAGES}/hires/*.eps . @touch baculai-dir.tex baculai-fd.tex baculai-sd.tex \ baculai-console.tex baculai-general.tex - -latex -interaction=batchmode bacula.tex + latex -interaction=batchmode bacula.tex makeindex bacula.idx -o bacula.ind 2>/dev/null makeindex bacula.ddx -o bacula.dnd >/dev/null 2>/dev/null makeindex bacula.fdx -o bacula.fnd >/dev/null 2>/dev/null makeindex bacula.sdx -o bacula.snd >/dev/null 2>/dev/null makeindex bacula.cdx -o bacula.cnd >/dev/null 2>/dev/null - -latex -interaction=batchmode bacula.tex - -latex -interaction=batchmode bimagemgr.tex + latex -interaction=batchmode bacula.tex + latex -interaction=batchmode bimagemgr.tex pdf: @echo "Making pdfm" diff --git a/docs/manual/messagesres.tex b/docs/manual/messagesres.tex index ea011495..7dfb87c8 100644 --- a/docs/manual/messagesres.tex +++ b/docs/manual/messagesres.tex @@ -40,8 +40,8 @@ specification followed by a list of {\bf message-types} in the format: \begin{description} \item [destination = message-type1, message-type2, message-type3, ... ] - \index[dir]{destination} - \end{description} +\index[dir]{destination} +\end{description} or for those destinations that need and address specification (e.g. email): @@ -49,14 +49,14 @@ or for those destinations that need and address specification (e.g. email): \item [destination = address = message-type1, message-type2, message-type3, ... ] - \index[dir]{destination} - -Where {\bf destination} is one of a predefined set of keywords that define -where the message is to be sent ({\bf stdout}, {\bf file}, ...), {\bf -message-type} is one of a predefined set of keywords that define the type of -message generated by {\bf Bacula} ({\bf ERROR}, {\bf WARNING}, {\bf FATAL}, -...), and {\bf address} varies according to the {\bf destination} keyword, but -is typically an email address or a filename. +\index[dir]{destination} + + Where {\bf destination} is one of a predefined set of keywords that define + where the message is to be sent ({\bf stdout}, {\bf file}, ...), {\bf + message-type} is one of a predefined set of keywords that define the type of + message generated by {\bf Bacula} ({\bf ERROR}, {\bf WARNING}, {\bf FATAL}, + ...), and {\bf address} varies according to the {\bf destination} keyword, but + is typically an email address or a filename. \end{description} The following are the list of the possible record definitions that can be used @@ -65,19 +65,19 @@ in a message resource. \begin{description} \item [Messages] - \index[dir]{Messages} +\index[dir]{Messages} Start of the Messages records. \item [Name = \lt{}name\gt{}] - \index[dir]{Name} +\index[dir]{Name} The name of the Messages resource. The name you specify here will be used to -tie this Messages resource to a Job and/or to the daemon. -\label{mailcommand} + tie this Messages resource to a Job and/or to the daemon. +\label{mailcommand} \item [MailCommand = \lt{}command\gt{}] - \index[dir]{MailCommand} +\index[dir]{MailCommand} In the absence of this resource, Bacula will send all mail using the -following command: + following command: {\bf mail -s "Bacula Message" \lt{}recipients\gt{}} @@ -117,11 +117,11 @@ addressing form that you use. Certain programs such as Exim can be very selective as to what forms are permitted particularly in the from part. \item [OperatorCommand = \lt{}command\gt{}] - \index[fd]{OperatorCommand} +\index[fd]{OperatorCommand} This resource specification is similar to the {\bf MailCommand} except that -it is used for Operator messages. The substitutions performed for the {\bf -MailCommand} are also done for this command. Normally, you will set this -command to the same value as specified for the {\bf MailCommand}. + it is used for Operator messages. The substitutions performed for the {\bf + MailCommand} are also done for this command. Normally, you will set this + command to the same value as specified for the {\bf MailCommand}. \item [Debug = \lt{}debug-level\gt{}] \index[fd]{Debug} @@ -155,30 +155,34 @@ until the console program connects to the Director. \lt{}message-type1\gt{}, \lt{}message-type2\gt{}, ...} \index[console]{\lt{}destination\gt{}} -Where {\bf address} depends on the {\bf destination}, which may be one of the -following: +Where {\bf address} depends on the {\bf destination}. + +The {\bf destination} may be one of the following: \begin{description} \item [director] \index[dir]{director} + \index[general]{director} Send the message to the Director whose name is given in the {\bf address} -field. Note, in the current implementation, the Director Name is ignored, and -the message is sent to the Director that started the Job. + field. Note, in the current implementation, the Director Name is ignored, and + the message is sent to the Director that started the Job. \item [file] - \index[dir]{file} +\index[dir]{file} +\index[general]{file} Send the message to the filename given in the {\bf address} field. If the -file already exists, it will be overwritten. + file already exists, it will be overwritten. \item [append] - \index[dir]{append} +\index[dir]{append} +\index[general]{append} Append the message to the filename given in the {\bf address} field. If the file already exists, it will be appended to. If the file does not exist, it will be created. \item [syslog] - \index[fd]{syslog} +\index[general]{syslog} Send the message to the system log (syslog) using the facility specified in the {\bf address} field. Note, for the moment, the {\bf address} field is ignored and the message is always sent to the LOG\_DAEMON facility with @@ -188,7 +192,7 @@ file already exists, it will be overwritten. \end{verbatim} \item [mail] - \index[fd]{mail} + \index[general]{mail} Send the message to the email addresses that are given as a comma separated list in the {\bf address} field. Mail messages are grouped together during a job and then sent as a single email message when the @@ -200,7 +204,7 @@ file already exists, it will be overwritten. mailcommand}). \item [mail on error] - \index[fd]{mail on error} + \index[general]{mail on error} Send the message to the email addresses that are given as a comma separated list in the {\bf address} field if the Job terminates with an error condition. MailOnError messages are grouped together during a job @@ -212,7 +216,7 @@ file already exists, it will be overwritten. Job terminates normally, the output information is saved. \item [mail on success] - \index[fd]{mail on success} + \index[general]{mail on success} Send the message to the email addresses that are given as a comma separated list in the {\bf address} field if the Job terminates normally (no error condition). MailOnSuccess messages are grouped @@ -222,14 +226,38 @@ file already exists, it will be overwritten. totally discarded (for this destination). If the Job terminates in normally, it is emailed. - \item [operator] - \index[fd]{operator} + \index[general]{operator} Send the message to the email addresses that are specified as a comma separated list in the {\bf address} field. This is similar to {\bf mail} above, except that each message is sent as received. Thus there is one email per message. This is most useful for {\bf mount} messages - (see below). \end{description} + (see below). + +\item [console] + \index[general]{console} + Send the message to the Bacula console. + +\item [stdout] + \index[general]{stdout} + Send the message to the standard output (normally not used). + +\item [stderr] + \index[general]{stderr} + Send the message to the standard error output (normally not used). + +\item [catalog] + \index[general]{catalog} + Send the message to the Catalog database. The message will be + written to the table named {\bf Log} and a timestamp field will + also be added. This permits Job Reports and other messages to + be recorded in the Catalog so that they can be accessed by + reporting software. Bacula will prune the Log records associated + with a Job when the Job records are pruned. Otherwise, Bacula + never uses these records internally, so this destination is only + used for special purpose programs (e.g. {\bf bweb}). + +\end{description} For any destination, the {\bf message-type} field is a comma separated list of the following types or classes of messages: @@ -237,38 +265,41 @@ file already exists, it will be overwritten. \begin{description} \item [info] - \index[fd]{info} + \index[general]{info} General information messages. \item [warning] - \index[fd]{warning} + \index[general]{warning} Warning messages. Generally this is some unusual condition but not expected -to be serious. + to be serious. \item [error] - \index[fd]{error} + \index[general]{error} Non-fatal error messages. The job continues running. Any error message should -be investigated as it means that something went wrong. + be investigated as it means that something went wrong. \item [fatal] - \index[fd]{fatal} + \index[general]{fatal} Fatal error messages. Fatal errors cause the job to terminate. \item [terminate] - \index[fd]{terminate} + \index[general]{terminate} Message generated when the daemon shuts down. \item [saved] \index[fd]{saved} + \index[general]{saved} Files saved normally. \item [notsaved] \index[fd]{notsaved} + \index[general]{notsaved} Files not saved because of some error. Usually because the file cannot be -accessed (i.e. it does not exist or is not mounted). + accessed (i.e. it does not exist or is not mounted). \item [skipped] \index[fd]{skipped} + \index[general]{skipped} Files that were skipped because of a user supplied option such as an incremental backup or a file that matches an exclusion pattern. This is not considered an error condition such as the files listed for the {\bf @@ -279,23 +310,34 @@ accessed (i.e. it does not exist or is not mounted). \item [mount] \index[dir]{mount} + \index[general]{mount} Volume mount or intervention requests from the Storage daemon. These requests require a specific operator intervention for the job to continue. \item [restored] - \index[dir]{restored} + \index[fd]{restored} + \index[general]{restored} The {\bf ls} style listing generated for each file restored is sent to this message class. \item [all] - \index[fd]{all} + \index[general]{all} All message types. -\item [*security] - \index[fd]{*security} +\item [security] + \index[general]{security} Security info/warning messages principally from unauthorized connection attempts. + +\item [alert] + \index[general]{alert} + Alert messages. These are messages generated by tape alerts. + +\item [volmgmt] + \index[general]{volmgmt} + Volume management messages. Currently there are no volume mangement + messages generated. \end{description} \end{description} @@ -319,7 +361,7 @@ Messages { \normalsize With the exception of the email address (changed to avoid junk mail from -robot's), Kern's Director's Messages resource is as follows. Note, the {\bf +robot's), an example Director's Messages resource is as follows. Note, the {\bf mailcommand} and {\bf operatorcommand} are on a single line -- they had to be split for this manual: diff --git a/docs/manual/state.tex b/docs/manual/state.tex index 67ec18d3..1ada48d8 100644 --- a/docs/manual/state.tex +++ b/docs/manual/state.tex @@ -106,6 +106,7 @@ In other words, what is and what is not currently implemented and functional. \item All Volume blocks (approximately 64K bytes) contain a data checksum. \item Migration support -- move data from one Pool to another or one Volume to another. + \item Supports writing to DVD (beta code). \end{itemize} \item Multi-Operating System Support @@ -201,8 +202,8 @@ In other words, what is and what is not currently implemented and functional. \item If you have over 4 billion file entries stored in your database, the database FileId is likely to overflow. This is a monster database, but still possible. Bacula's FileId fields have been modified so that they can be - upgraded from 32 to 64 bits in version 1.39, but this has never been - tested. + upgraded from 32 to 64 bits in version 1.39 or later, but you must + manually do so. \item Files deleted after a Full save will be included in a restoration. This is typical for most similar backup programs (we have a project to correct this). diff --git a/docs/manual/version.tex b/docs/manual/version.tex index a7e70623..9bcc38ba 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.39.33 (28 December 2006) +1.39.35 (28 December 2006)