with BaseJobs. The options letters are the same than in the \textbf{verify=}
option below.
-\item[accurate=\lt{}options\gt{}]
-\index[dir]{accurate}
-\index[dir]{Directive!accurate}
- The options letters specified are used when running a {\bf Backup
- Level=Incremental/Differential} in Accurate mode. The options
- letters are the same than in the \textbf{verify=} option below.
+\item[accurate=\lt{}options\gt{}] \index[dir]{accurate}
+ \index[dir]{Directive!accurate} The options letters specified are used when
+ running a {\bf Backup Level=Incremental/Differential} in Accurate mode. The
+ options letters are the same than in the \textbf{verify=} option below.
\item [verify=\lt{}options\gt{}]
\index[dir]{verify}
\item {\bf 1}
compare the SHA1 signature
+
+ \item {\bf A}
+ Only for Accurate option, it allows to always backup the file
+
\end{description}
A useful set of general options on the {\bf Level=Catalog} or {\bf
ndbm. The default is {\bf no}, so no checks are made for sparse files.
You may specify {\bf sparse=yes} even on files that are not sparse file.
No harm will be done, but there will be a small additional overhead to
- check for buffers of all zero, and a small additional amount of space on
- the output archive will be used to save the seek address of each
- non-zero record read.
+ check for buffers of all zero, and if there is a 32K block of all zeros
+ (see below), that block will become a hole in the file, which
+ may not be desirable if the original file was not a sparse file.
{\bf Restrictions:} Bacula reads files in 32K buffers. If the whole
buffer is zero, it will be treated as a sparse block and not written to
benchmark the difference or set sparse for only those files that are
really sparse.
+ You probably should not use this option on files or raw disk devices
+ that are not really sparse files (i.e. have holes in them).
+
\label{readfifo}
\item [readfifo=yes\vb{}no]
\index[dir]{readfifo}
filesystem type. The permitted filesystem-type names are:
ext2, jfs, ntfs, proc, reiserfs, xfs, usbdevfs, sysfs, smbfs,
- iso9660. For ext3 systems, use ext2.
+ iso9660.
You may have multiple Fstype directives, and thus permit matching
of multiple filesystem types within a single Options resource. If