%%
%%
-\section*{Basic Volume Management}
-\label{_ChapterStart39}
+\chapter{Basic Volume Management}
+\label{DiskChapter}
\index[general]{Basic Volume Management}
\index[general]{Management!Basic Volume}
\index[general]{Disk Volumes}
-\addcontentsline{toc}{section}{Basic Volume Management}
This chapter presents most all the features needed to do Volume management.
Most of the concepts apply equally well to both tape and disk Volumes.
either disk or tape volumes.
\label{Concepts}
-\subsection*{Key Concepts and Resource Records}
+\section{Key Concepts and Resource Records}
\index[general]{Key Concepts and Resource Records }
\index[general]{Records!Key Concepts and Resource }
-\addcontentsline{toc}{subsection}{Key Concepts and Resource Records}
Getting Bacula to write to disk rather than tape in the simplest case is
rather easy. In the Storage daemon's configuration file, you simply define an
at the end of this chapter under \ilink{Concurrent Disk
Jobs}{ConcurrentDiskJobs}.
-\subsubsection*{Pool Options to Limit the Volume Usage}
+\subsection{Pool Options to Limit the Volume Usage}
\index[general]{Usage!Pool Options to Limit the Volume }
\index[general]{Pool Options to Limit the Volume Usage }
-\addcontentsline{toc}{subsubsection}{Pool Options to Limit the Volume Usage}
Some of the options you have, all of which are specified in the Pool record,
are:
case), use:
{\bf UseVolumeOnce = yes}.
+
\item To write nnn Jobs to each Volume, use:
{\bf Maximum Volume Jobs = nnn}.
+
\item To limit the maximum size of each Volume, use:
{\bf Maximum Volume Bytes = mmmm}.
-\item To limit the use time (i.e. write the Volume for a maximum of 5 days),
+
+ Note, if you use disk volumes, with all versions up to and including
+ 1.39.28, you should probably limit the Volume size to some reasonable
+ value such as say 5GB. This is because during a restore, Bacula is
+ currently unable to seek to the proper place in a disk volume to restore
+ a file, which means that it must read all records up to where the
+ restore begins. If your Volumes are 50GB, reading half or more of the
+ volume could take quite a bit of time. Also, if you ever have a partial
+ hard disk failure, you are more likely to be able to recover more data
+ if they are in smaller Volumes.
+
+\item To limit the use time (i.e. write the Volume for a maximum of five days),
use:
{\bf Volume Use Duration = ttt}.
so no weekend backups will be done until Monday morning.
\label{AutomaticLabeling}
-\subsubsection*{Automatic Volume Labeling}
+\subsection{Automatic Volume Labeling}
\index[general]{Automatic Volume Labeling }
\index[general]{Labeling!Automatic Volume }
-\addcontentsline{toc}{subsubsection}{Automatic Volume Labeling}
Use of the above records brings up another problem -- that of labeling your
Volumes. For automated disk backup, you can either manually label each of your
In version 1.37 and later, it is probably much better to use Python scripting
and the NewVolume event since generating Volume labels in a Python script is
much easier than trying to figure out Counter variables. See the
-\ilink{Python Scripting}{_ChapterStart60} chapter of this manual for more
+\ilink{Python Scripting}{PythonChapter} chapter of this manual for more
details.
Please note that automatic Volume labeling can also be used with tapes, but
work with autochangers since Bacula will not access unknown slots. There
are several methods of labeling all volumes in an autochanger magazine.
For more information on this, please see the \ilink{
-Autochanger}{_ChapterStart18} chapter of this manual.
+Autochanger}{AutochangersChapter} chapter of this manual.
Automatic Volume labeling is enabled by making a change to both the Pool
resource (Director) and to the Device resource (Storage daemon) shown above.
Bacula will create Volume names Vol0001, Vol0002, and so on when new Volumes
are needed. Much more complex and elaborate labels can be created using
variable expansion defined in the
-\ilink{Variable Expansion}{_ChapterStart50} chapter of this manual.
+\ilink{Variable Expansion}{VarsChapter} chapter of this manual.
The second change that is necessary to make automatic labeling work is to give
the Storage daemon permission to automatically label Volumes. Do so by adding
records.
\label{Recycling1}
-\subsubsection*{Restricting the Number of Volumes and Recycling}
-\index[general]{Recycling!Restricting the Number of Volumes and }
-\index[general]{Restricting the Number of Volumes and Recycling }
-\addcontentsline{toc}{subsubsection}{Restricting the Number of Volumes and
-Recycling}
+\subsection{Restricting the Number of Volumes and Recycling}
+\index[general]{Recycling!Restricting the Number of Volumes and Recycling}
+\index[general]{Restricting the Number of Volumes and Recycling}
Automatic labeling discussed above brings up the problem of Volume management.
With the above scheme, a new Volume will be created every day. If you have not
The first three records (File Retention, Job Retention, and AutoPrune)
determine the amount of time that Job and File records will remain in your
Catalog, and they are discussed in detail in the
-\ilink{Automatic Volume Recycling}{_ChapterStart22} chapter of
+\ilink{Automatic Volume Recycling}{RecyclingChapter} chapter of
this manual.
Volume Retention, AutoPrune, and Recycle determine how long Bacula will keep
your Volumes before reusing them, and they are also discussed in detail in the
-\ilink{Automatic Volume Recycling}{_ChapterStart22} chapter of
+\ilink{Automatic Volume Recycling}{RecyclingChapter} chapter of
this manual.
The Maximum Volumes record can also be used in conjunction with the Volume
prune the specified volume.
\label{ConcurrentDiskJobs}
-\subsection*{Concurrent Disk Jobs}
+\section{Concurrent Disk Jobs}
\index[general]{Concurrent Disk Jobs}
-\addcontentsline{toc}{subsection}{Concurrent Disk Jobs}
Above, we discussed how you could have a single device named {\bf
FileBackup} that writes to volumes in {\bf /home/bacula/backups}.
You can, in fact, run multiple concurrent jobs using the
\label{Example2}
-\subsection*{An Example}
+\section{An Example}
\index[general]{Example }
-\addcontentsline{toc}{subsection}{Example}
The following example is not very practical, but can be used to demonstrate
the proof of concept in a relatively short period of time. The example
monthly cycle (take care about the amount of archive disk space used).
\label{MultipleDisks}
-\subsection*{Backing up to Multiple Disks}
+\section{Backing up to Multiple Disks}
\index[general]{Disks!Backing up to Multiple }
\index[general]{Backing up to Multiple Disks }
-\addcontentsline{toc}{subsection}{Backing up to Multiple Disks}
Bacula can, of course, use multiple disks, but in general, each disk must be a
separate Device specification in the Storage daemon's conf file, and you must
Storage resource in the Director when doing a restore.
\label{MultipleClients}
-\subsection*{Considerations for Multiple Clients}
+\section{Considerations for Multiple Clients}
\index[general]{Clients!Considerations for Multiple }
\index[general]{Multiple Clients}
-\addcontentsline{toc}{subsection}{Considerations for Multiple Clients}
If we take the above example and add a second Client, here are a few
considerations: