just a question of adapting the {\bf mtx-changer} script (or selecting one
already adapted) for proper interfacing. You can find a list of autochangers
supported by {\bf mtx} at the following link:
-\elink{http://mtx.badtux.net/compatibility.php}
-{http://mtx.badtux.net/compatibility.php}.
+\elink{http://mtx.opensource-sw.net/compatibility.php}
+{http://mtx.opensource-sw.net/compatibility.php}.
The home page for the {\bf mtx} project can be found at:
-\elink{http://mtx.badtux.net/}{http://mtx.badtux.net/}.
+\elink{http://mtx.opensource-sw.net/}{http://mtx.opensource-sw.net/}.
If you are having troubles, please use the {\bf auto} command in the {\bf
btape} program to test the functioning of your autochanger with Bacula. When
after recycling. This value is checked and the {\bf Used} status set
while the job is writing to the particular volume.
+ This directive is particularly useful for restricting the size
+ of disk volumes, and will work correctly even in the case of
+ multiple simultaneous jobs writing to the volume.
+
The value defined by this directive in the bacula-dir.conf file is the
default value used when a Volume is created. Once the volume is
created, changing the value in the bacula-dir.conf file will not change
The use duration is checked and the {\bf Used} status is set only at the
end of a job that writes to the particular volume, which means that even
though the use duration may have expired, the catalog entry will not be
- updated until the next job that uses this volume is run.
-
+ updated until the next job that uses this volume is run. This
+ directive is not intended to be used to limit volume sizes
+ and will not work correctly (i.e. will fail jobs) if the use
+ duration expires while multiple simultaneous jobs are writing
+ to the volume.
+
Please note that the value defined by this directive in the bacula-dir.conf
file is the default value used when a Volume is created. Once the volume is
created, changing the value in the bacula-dir.conf file will not change what
\index[dir]{Volume Retention}
\index[dir]{Directive!Volume Retention}
The Volume Retention directive defines the length of time that {\bf
- Bacula} will keep Job and Files records associated with the Volume in
+ Bacula} will keep records associated with the Volume in
the Catalog database after the End time of each Job written to the
Volume. When this time period expires, and if {\bf AutoPrune} is set to
{\bf yes} Bacula may prune (remove) Job records that are older than the
specified Volume Retention period if it is necessary to free up a
Volume. Recycling will not occur until it is absolutely necessary to
- free up a volume. All File records associated with pruned Jobs are also
+ free up a volume (i.e. no other writable volume exists).
+ All File records associated with pruned Jobs are also
pruned. The time may be specified as seconds, minutes, hours, days,
weeks, months, quarters, or years. The {\bf Volume Retention} is
applied independently of the {\bf Job Retention} and the {\bf File
Bacula does not automatically recycle a Volume. It attempts to keep the
Volume data intact as long as possible before over writing the Volume.
- The default Volume retention period is 365 days. Note, this directive
- sets the default value for each Volume entry in the Catalog when the
- Volume is created. The value in the catalog may be later individually
- changed for each Volume using the Console program.
By defining multiple Pools with different Volume Retention periods, you
may effectively have a set of tapes that is recycled weekly, another
This means that if you do a Full backup once a month, the minimum Volume
retention period should be two months.
- Please note that the value defined by this directive in the bacula-dir.conf
- file is the default value used when a Volume is created. Once the volume is
- created, changing the value in the bacula-dir.conf file will not change what
- is stored for the Volume. To change the value for an existing Volume you
- must use the {\bf update} command in the Console.
+ The default Volume retention period is 365 days, and either the default
+ or the value defined by this directive in the bacula-dir.conf file is
+ the default value used when a Volume is created. Once the volume is
+ created, changing the value in the bacula-dir.conf file will not change
+ what is stored for the Volume. To change the value for an existing
+ Volume you must use the {\bf update} command in the Console.
\label{PoolRecyclePool}
\item [RecyclePool = \lt{}pool-resource-name\gt{}]
{\bf /dev/dvd} depending on your system. It will not be a name such
as {\bf /mnt/cdrom}.
+Finally, for {\bf growisofs} to work, it must be able to lock
+a certain amount of memory in RAM. If you have restrictions on
+this function, you may have failures. Under {\bf bash}, you can
+set this with the following command:
+
+\footnotesize
+\begin{verbatim}
+ulimit -l unlimited
+\end{verbatim}
+\normalsize
+
\section{Edit Codes for DVD Directives}
\index[general]{Directives!DVD Edit Codes}
\index[general]{Edit Codes for DVD Directives }
\index[sd]{Directive!Heartbeat Interval}
\index[general]{Heartbeat Interval}
\index[general]{Broken pipe}
- This directive defines an interval of time. When the Storage daemon is
- waiting for the operator to mount a tape, each time interval, it will
- send a heartbeat signal to the File daemon. The default interval is
- zero which disables the heartbeat. This feature is particularly useful
- if you have a router such as 3Com that does not follow Internet
- standards and times out an valid connection after a short duration
- despite the fact that keepalive is set. This usually results
- in a broken pipe error message.
+ This directive defines an interval of time in seconds. When
+ the Storage daemon is waiting for the operator to mount a
+ tape, each time interval, it will send a heartbeat signal to
+ the File daemon. The default interval is zero which disables
+ the heartbeat. This feature is particularly useful if you
+ have a router such as 3Com that does not follow Internet
+ standards and times out an valid connection after a short
+ duration despite the fact that keepalive is set. This usually
+ results in a broken pipe error message.
+
+\item [Client Connect Wait = \lt{}time-interval\gt{}]
+ \index[sd]{Connect Wait}
+ \index[sd]{Directive!Connect Wait}
+ \index[general]{Client Connect Wait}
+ This directive defines an interval of time in seconds that
+ the Storage daemon will wait for a Client (the File daemon)
+ to connect. The default is 30 seconds. Be aware that the
+ longer the Storage daemon waits for a Client, the more
+ resources will be tied up.
\item [Maximum Concurrent Jobs = \lt{}number\gt{}]
\index[sd]{Maximum Concurrent Jobs}
Capacity/Slot column below, I quote the Compressed capacity per tape (or
Slot).
+Since on most systems (other than FreeBSD), Bacula uses {\bf mtx}
+through the {\bf mtx-changer} script, in principle, if {\bf mtx}
+will operate your changer correctly, then it is just a question
+of adapting the {\bf mtx-changer} script (or selecting one
+already adapted) for proper interfacing. You can find a list of
+autochangers supported by {\bf mtx} at the following link:
+\elink{http://mtx.opensource-sw.net/compatibility.php}
+{http://mtx.opensource-sw.net/compatibility.php}.
+The home page for the {\bf mtx} project can be found at:
+\elink{http://mtx.opensource-sw.net/}{http://mtx.opensource-sw.net/}.
+
\addcontentsline{lot}{table}{Autochangers Known to Work with Bacula}
\begin{longtable}{|p{0.6in}|p{0.8in}|p{1.9in}|p{0.8in}|p{0.5in}|p{0.75in}|}
\index[general]{Win32!Dealing with Problems}
\index[general]{Dealing with Win32 Problems}
+Sometimes Win32 machines the File daemon may have very slow
+backup transfer rates compared to other machines. To you might
+try setting the Maximum Network Buffer Size to 32,768 in both the
+File daemon and in the Storage daemon.
+
If you are not using the portable option, and you have VSS
(Volume Shadow Copy) enabled in the Director, and you experience
problems with Bacula not being able to open files, it is most
projects / bacula / docs / commitdiff