From: Eric Bollengier Date: Mon, 7 Sep 2009 13:58:48 +0000 (+0000) Subject: ebl space tweaks X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=ac736d5ca74a97e34d0d163df99fd2c1779e131e;p=bacula%2Fdocs ebl space tweaks --- diff --git a/docs/manuals/en/install/storedconf.tex b/docs/manuals/en/install/storedconf.tex index e5967921..fdc6713f 100644 --- a/docs/manuals/en/install/storedconf.tex +++ b/docs/manuals/en/install/storedconf.tex @@ -289,13 +289,13 @@ specified within the Device resource are specific to the Device. in the Solaris (Sun) archive specification {\bf /dev/rmt/0mbn} is what is needed in this case. Bacula does not support SysV tape drive behavior. - As noted above, normally the Archive Device is the name of a tape drive, but - you may also specify an absolute path to an existing directory. If the Device - is a directory Bacula will write to file storage in the specified directory, - and the filename used will be the Volume name as specified in the Catalog. - If you want to write into more than one directory (i.e. to spread the load to - different disk drives), you will need to define two Device resources, each - containing an Archive Device with a different directory. + As noted above, normally the Archive Device is the name of a tape drive, but + you may also specify an absolute path to an existing directory. If the + Device is a directory Bacula will write to file storage in the specified + directory, and the filename used will be the Volume name as specified in the + Catalog. If you want to write into more than one directory (i.e. to spread + the load to different disk drives), you will need to define two Device + resources, each containing an Archive Device with a different directory. \label{SetupFifo} In addition to a tape device name or a directory name, Bacula will accept the name of a FIFO. A FIFO is a special kind of file that connects two programs @@ -465,21 +465,21 @@ Changer Command = "/path/mtx-changer %c %o %S %a %d" \item [Alert Command = {\it name-string}] \index[sd]{Alert Command} - The {\bf name-string} specifies an external program to be called at the + The {\bf name-string} specifies an external program to be called at the completion of each Job after the device is released. The purpose of this - command is to check for Tape Alerts, which are present when something is - wrong with your tape drive (at least for most modern tape drives). The same - substitution characters that may be specified in the Changer Command may also - be used in this string. For more information, please see the - \ilink{Autochangers}{AutochangersChapter} chapter of this manual. + command is to check for Tape Alerts, which are present when something is + wrong with your tape drive (at least for most modern tape drives). The same + substitution characters that may be specified in the Changer Command may + also be used in this string. For more information, please see the + \ilink{Autochangers}{AutochangersChapter} chapter of this manual. - Note, it is not necessary to have an autochanger to use this command. The - example below uses the {\bf tapeinfo} program that comes with the {\bf mtx} - package, but it can be used on any tape drive. However, you will need to - specify a {\bf Changer Device} directive in your Device resource (see above) - so that the generic SCSI device name can be edited into the command (with the - \%c). + Note, it is not necessary to have an autochanger to use this command. The + example below uses the {\bf tapeinfo} program that comes with the {\bf mtx} + package, but it can be used on any tape drive. However, you will need to + specify a {\bf Changer Device} directive in your Device resource (see above) + so that the generic SCSI device name can be edited into the command (with + the \%c). An example of the use of this command to print Tape Alerts in the Job report is: @@ -570,10 +570,11 @@ bacula-sd Alert: TapeAlert[32]: Interface: Problem with SCSI interface Always Open = yes}. This also ensures that the drive is available when Bacula needs it. - If you have {\bf Always Open = yes} (recommended) and you want to use the - drive for something else, simply use the {\bf unmount} command in the Console - program to release the drive. However, don't forget to remount the drive with - {\bf mount} when the drive is available or the next Bacula job will block. + If you have {\bf Always Open = yes} (recommended) and you want to use the + drive for something else, simply use the {\bf unmount} command in the + Console program to release the drive. However, don't forget to remount the + drive with {\bf mount} when the drive is available or the next Bacula job + will block. For File storage, this directive is ignored. For a FIFO storage device, you must set this to {\bf No}. @@ -807,17 +808,18 @@ the editing codes that can be used in this directive. \item [Hardware End of Medium = {\it yes\vb{}no}] \index[sd]{Hardware End of Medium} \index[sd]{Directive!Hardware End of Medium} - If {\bf No}, the archive device is not required to support end of medium - ioctl request, and the storage daemon will use the forward space file - function to find the end of the recorded data. If {\bf Yes}, the archive - device must support the {\tt ioctl} {\tt MTEOM} call, which will position the - tape to the end of the recorded data. In addition, your SCSI driver must keep - track of the file number on the tape and report it back correctly by the - {\bf MTIOCGET} ioctl. Note, some SCSI drivers will correctly forward space to - the end of the recorded data, but they do not keep track of the file number. - On Linux machines, the SCSI driver has a {\bf fast-eod} option, which if set - will cause the driver to lose track of the file number. You should ensure - that this option is always turned off using the {\bf mt} program. + If {\bf No}, the archive device is not required to support end of medium + ioctl request, and the storage daemon will use the forward space file + function to find the end of the recorded data. If {\bf Yes}, the archive + device must support the {\tt ioctl} {\tt MTEOM} call, which will position + the tape to the end of the recorded data. In addition, your SCSI driver must + keep track of the file number on the tape and report it back correctly by + the {\bf MTIOCGET} ioctl. Note, some SCSI drivers will correctly forward + space to the end of the recorded data, but they do not keep track of the + file number. On Linux machines, the SCSI driver has a {\bf fast-eod} + option, which if set will cause the driver to lose track of the file + number. You should ensure that this option is always turned off using the + {\bf mt} program. Default setting for Hardware End of Medium is {\bf Yes}. This function is used before appending to a tape to ensure that no previously written data is @@ -855,35 +857,35 @@ the editing codes that can be used in this directive. \item [BSF at EOM = {\it yes\vb{}no}] \index[sd]{BSF at EOM} \index[sd]{Directive!BSF at EOM} - If {\bf No}, the default, no special action is taken by Bacula with the End - of Medium (end of tape) is reached because the tape will be positioned after - the last EOF tape mark, and Bacula can append to the tape as desired. - However, on some systems, such as FreeBSD, when Bacula reads the End of - Medium (end of tape), the tape will be positioned after the second EOF tape - mark (two successive EOF marks indicated End of Medium). If Bacula appends - from that point, all the appended data will be lost. The solution for such - systems is to specify {\bf BSF at EOM} which causes Bacula to backspace over - the second EOF mark. Determination of whether or not you need this directive - is done using the {\bf test} command in the {\bf btape} program. + If {\bf No}, the default, no special action is taken by Bacula with the End + of Medium (end of tape) is reached because the tape will be positioned after + the last EOF tape mark, and Bacula can append to the tape as desired. + However, on some systems, such as FreeBSD, when Bacula reads the End of + Medium (end of tape), the tape will be positioned after the second EOF tape + mark (two successive EOF marks indicated End of Medium). If Bacula appends + from that point, all the appended data will be lost. The solution for such + systems is to specify {\bf BSF at EOM} which causes Bacula to backspace over + the second EOF mark. Determination of whether or not you need this directive + is done using the {\bf test} command in the {\bf btape} program. \item [TWO EOF = {\it yes\vb{}no}] \index[sd]{TWO EOF} \index[sd]{Directive!TWO EOF} - If {\bf Yes}, Bacula will write two end of file marks when terminating a tape --- i.e. after the last job or at the end of the medium. If {\bf No}, the -default, Bacula will only write one end of file to terminate the tape. + If {\bf Yes}, Bacula will write two end of file marks when terminating a + tape -- i.e. after the last job or at the end of the medium. If {\bf No}, + the default, Bacula will only write one end of file to terminate the tape. \item [Backward Space Record = {\it yes\vb{}no}] \index[sd]{Backward Space Record} \index[sd]{Directive!Backward Space Record} - If {\it Yes}, the archive device supports the {\tt MTBSR ioctl} to backspace - records. If {\it No}, this call is not used and the device must be rewound - and advanced forward to the desired position. Default is {\bf Yes} for non - random-access devices. This function if enabled is used at the end of a - Volume after writing the end of file and any ANSI/IBM labels to determine whether - or not the last block was written correctly. If you turn this function off, - the test will not be done. This causes no harm as the re-read process is - precautionary rather than required. + If {\it Yes}, the archive device supports the {\tt MTBSR ioctl} to backspace + records. If {\it No}, this call is not used and the device must be rewound + and advanced forward to the desired position. Default is {\bf Yes} for non + random-access devices. This function if enabled is used at the end of a + Volume after writing the end of file and any ANSI/IBM labels to determine + whether or not the last block was written correctly. If you turn this + function off, the test will not be done. This causes no harm as the re-read + process is precautionary rather than required. \item [Backward Space File = {\it yes\vb{}no}] \index[sd]{Backward Space File} @@ -1008,8 +1010,8 @@ default, Bacula will only write one end of file to terminate the tape. \item [Maximum Spool Size = {\it bytes}] \index[sd]{Maximum Spool Size} \index[sd]{Directive!Maximum Spool Size} - where the bytes specify the maximum spool size for all jobs that are running. - The default is no limit. + where the bytes specify the maximum spool size for all jobs that are + running. The default is no limit. \item [Maximum Job Spool Size = {\it bytes}] \index[sd]{Maximum Job Spool Size}