the backup. This option is not generally recommended as there are very
few programs that use st\_atime, and the backup overhead is increased
because of the additional system call necessary to reset the times.
+ However, for some files, such as mailboxes, when Bacula backs up the
+ file, the user will notice that someone (Bacula) has accessed the
+ file. In this, case keepatime can be useful.
(I'm not sure this works on Win32).
+ Note, if you use this feature, when Bacula resets the access time, the
+ change time (st_ctime) will automatically be modified by the system,
+ so on the next incremental job, the file will be backed up even if
+ it has not changed. As a consequence, you will probably also want
+ to use {\bf mtimeonly = yes} as well as keepatime (thanks to
+ Rudolf Cejka for this tip).
+
\item [wild=\lt{}string\gt{}]
\index[dir]{wild }
Specifies a wild-card string to be applied to the filenames and
import bacula
+The following are the read-only attributes provided by the bacula object.
+\begin{description}
+\item [Name]
+\item [ConfigFile]
+\item [WorkingDir]
+\item [Version] string consisting of "Version Build-date"
+\end{description}
+
+
A simple definition of the Bacula Events Class might be the following:
\footnotesize
for the {\bf job} object.
\begin{description}
-\item [DirName] The name of the Director daemon.
\item [Level]
\item [Type]
\item [JobId]
\item [MediaType]
\item [JobName]
\item [JobStatus]
-\item [ConfigFile]
-\item [WorkingDir]
-\item [Version] tuple consisting of (Version, Build-date)
\item [CatalogRes] tuple consisting of (DBName, Address, User,
Password, Socket, Port, Database Vendor) taken from the Catalog resource
for the Job with the exception of Database Vendor, which is