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.
However, the chapter was originally written to explain backing up to disk, so
-you will see it is slanted in that direction, but that all the directives
+you will see it is slanted in that direction, but all the directives
presented here apply equally well whether your volume is disk or tape.
If you have a lot of hard disk storage or you absolutely must have your
label, and the internal label must agree with the system filename before
Bacula will use it.
-Although this is quite simple, there are a number of problems, the first is
+Although this is quite simple, there are a number of problems. The first is
that unless you specify otherwise, Bacula will always write to the same volume
until you run out of disk space. This problem is addressed below.
For example, the above directives can allow you to ensure that you rotate
through a set of daily Volumes if you wish.
-As mentioned above, each of those directives are specified in the Pool or
+As mentioned above, each of those directives is specified in the Pool or
Pools that you use for your Volumes. In the case of {\bf Maximum Volume Job},
{\bf Maximum Volume Bytes}, and {\bf Volume Use Duration}, you can actually
specify the desired value on a Volume by Volume basis. The value specified in
\normalsize
then if you run a backup once a day (every 24 hours), Bacula will use a new
-Volume each backup because each Volume it writes can only be used for 23 hours
+Volume for each backup, because each Volume it writes can only be used for 23 hours
after the first write. Note, setting the use duration to 23 hours is not a very
good solution for tapes unless you have someone on-site during the weekends,
because Bacula will want a new Volume and no one will be present to mount it,
various different Volumes to meet their needs.
The rest of this chapter will give an example involving backup to disk
-Volumes, but most of the information applies equally well for tape Volumes.
+Volumes, but most of the information applies equally well to tape Volumes.
\label{TheProblem}
\subsection*{The Problem}
They want to maintain 6 months of backup data, and be able to access the old
files on a daily basis for a week, a weekly basis for a month, then monthly
-for 6 months. In addition, and offsite capability was not needed (well perhaps
+for 6 months. In addition, offsite capability was not needed (well perhaps
it really is, but it was never used). Their daily changes amount to about
300MB on the average, or about 2GB per week.
\normalsize
As you can see, the Differential Pool can grow to a maximum of six volumes,
-and the Volumes are retained 40 days and there after can be recycled. Finally
+and the Volumes are retained 40 days and thereafter they can be recycled. Finally
there is one job per volume. This, of course, could be tightened up a lot, but
the expense here is a few GB which is not too serious.
\label{IncPool}
projects / bacula / docs / commitdiff