From 761ba9d4bae5d7bbc11d5acfe768f3542c9a4598 Mon Sep 17 00:00:00 2001 From: Eric Bollengier Date: Fri, 4 Dec 2009 11:43:42 +0100 Subject: [PATCH] Report newfeatures to the manual --- docs/manuals/en/main/dirdconf.tex | 15 +++++++++ docs/manuals/en/main/newfeatures.tex | 8 ++--- docs/manuals/en/main/storedconf.tex | 24 ++++++++++++++ docs/manuals/en/utility/progs.tex | 49 ++++++++++++++++++++++++++++ 4 files changed, 92 insertions(+), 4 deletions(-) diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex index c448d311..e7b61546 100644 --- a/docs/manuals/en/main/dirdconf.tex +++ b/docs/manuals/en/main/dirdconf.tex @@ -2799,6 +2799,21 @@ The Pool Resource defined in the Director's configuration file what is stored for the Volume. To change the value for an existing Volume you must use the {\bf update} command in the Console. +\item [Action On Purge = \lt{Truncate}] +\index[dir]{actiononpurge} + +This directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate +the volume when it is purged. It is useful to prevent disk based volumes from +consuming too much space. + +\begin{verbatim} +Pool { + Name = Default + Action On Purge = Truncate + ... +} +\end{verbatim} + \label{PoolScratchPool} \item [ScratchPool = \lt{}pool-resource-name\gt{}] \index[dir]{ScrachPool} diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex index 5dc7919d..7a7d94d8 100644 --- a/docs/manuals/en/main/newfeatures.tex +++ b/docs/manuals/en/main/newfeatures.tex @@ -117,10 +117,10 @@ This project was funded by Bacula Systems. \section{Accurate Fileset Options} \label{sec:accuratefileset} -In previous versions, the accurate code used the file creation and -modification times to determine if a file was modified or not. Now you can specify -which attributes to use (time, size, checksum, permission, owner, group, -\dots), similar to the Verify options. +In previous versions, the accurate code used the file creation and modification +times to determine if a file was modified or not. Now you can specify which +attributes to use (time, size, checksum, permission, owner, group, \dots), +similar to the Verify options. \begin{verbatim} FileSet { diff --git a/docs/manuals/en/main/storedconf.tex b/docs/manuals/en/main/storedconf.tex index b5d54196..5c9e28da 100644 --- a/docs/manuals/en/main/storedconf.tex +++ b/docs/manuals/en/main/storedconf.tex @@ -529,6 +529,16 @@ bacula-sd Alert: TapeAlert[32]: Interface: Problem with SCSI interface for reserving a drive for something special such as a high priority backup or restore operations. +\item[Maximum Concurent Jobs = {\it num}] +\index[sd]{MaximumConcurentJobs} + +{\bf Maximum Concurrent Jobs} is a directive that permits setting the maximum +number of Jobs that can run concurrently on a specified Device. Using this +directive, it is possible to have different Jobs using multiple drives, because +when the Maximum Concurrent Jobs limit is reached, the Storage Daemon will +start new Jobs on any other available compatible drive. This facilitates +writing to multiple drives with multiple Jobs that all use the same Pool. + \item [Maximum Changer Wait = {\it time}] \index[sd]{Maximum Changer Wait} \index[sd]{Directive!Maximum Changer Wait} @@ -739,6 +749,20 @@ the editing codes that can be used in this directive. If you need to specify multiple commands, create a shell script. +\item[Block Checksum = {\it yes/no}] + + You may turn off the Block Checksum (CRC32) code that Bacula uses when + writing blocks to a Volume. Doing so can reduce the Storage daemon CPU usage + slightly. It will also permit Bacula to read a Volume that has corrupted + data. + + The default is {\bf yes} -- i.e. the checksum is computed on write and + checked on read. + + \textbf{We do not recommend to turn this off} particularly on older tape + drives or for disk Volumes where doing so may allow corrupted data to go + undetected. + \item [Minimum block size = {\it size-in-bytes}] \index[sd]{Minimum block size} \index[sd]{Directive!Minimum block size} diff --git a/docs/manuals/en/utility/progs.tex b/docs/manuals/en/utility/progs.tex index 440fd4b7..d818bc3d 100644 --- a/docs/manuals/en/utility/progs.tex +++ b/docs/manuals/en/utility/progs.tex @@ -910,6 +910,7 @@ The full list of commands are: rewind rewind the tape scan read() tape block by block to EOT and report scanblocks Bacula read block by block to EOT and report + speed report drive speed status print tape status test General test Bacula tape functions weof write an EOF on the tape @@ -942,6 +943,54 @@ In the event that you want to relabel a {\bf Bacula}, you can simply use the note for labeling tapes, we recommend that you use the {\bf label} command in the {\bf Console} program since it will never overwrite a valid Bacula tape. +\subsubsection*{Testing your Tape Drive} +\label{sec:btapespeed} + +To determine the best configuration of your tape drive, you can run the new +\texttt{speed} command available in the \texttt{btape} program. + +This command can have the following arguments: +\begin{itemize} +\item[\texttt{file\_size=n}] Specify the Maximum File Size for this test + (between 1 and 5GB). This counter is in GB. +\item[\texttt{nb\_file=n}] Specify the number of file to be written. The amount + of data should be greater than your memory ($file\_size*nb\_file$). +\item[\texttt{skip\_zero}] This flag permits to skip tests with constant + data. +\item[\texttt{skip\_random}] This flag permits to skip tests with random + data. +\item[\texttt{skip\_raw}] This flag permits to skip tests with raw access. +\item[\texttt{skip\_block}] This flag permits to skip tests with Bacula block + access. +\end{itemize} + +\begin{verbatim} +*speed file_size=3 skip_raw +btape.c:1078 Test with zero data and bacula block structure. +btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes. +++++++++++++++++++++++++++++++++++++++++++ +btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0) +btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 MB/s +... +btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 MB/s + +btape.c:1090 Test with random data, should give the minimum throughput. +btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes. ++++++++++++++++++++++++++++++++++++++++++++ +btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0) +btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 MB/s ++++++++++++++++++++++++++++++++++++++++++++ +... +btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s + +\end{verbatim} + +When using compression, the random test will give your the minimum throughput +of your drive . The test using constant string will give you the maximum speed +of your hardware chain. (cpu, memory, scsi card, cable, drive, tape). + +You can change the block size in the Storage Daemon configuration file. + \section{Other Programs} \index[general]{Programs!Other} \index[general]{Other Programs} -- 2.39.5