The current version (1.37.16) of Bacula does not coordinate between the two
drives, so you must make sure that Bacula doesn't attempt to mount the same
Volume on both drives at the same time. There are a number of ways to do this.
-One was is to use different pools for each drive.
+One is to use different pools for each drive.
\label{ConfigRecords}
\subsection*{Device Configuration Records}
where the keyword {\bf scan} can be appended or not. The n1,n2, ... represent
Slot numbers to be updated and the form n3-n4 represents a range of Slot
-numbers to be updates (e.g. 4-7 will update Slots 4,5,6, and 7).
+numbers to be updated (e.g. 4-7 will update Slots 4,5,6, and 7).
This form is particularly useful if you want to do a scan (time expensive) and
restrict the update to one or two slots.
\normalsize
If the above script runs, you probably have no timing problems. If it does not
-run, start by putting a {\bf sleep 30} or possibly a {\bf sleep 60} in the the
+run, start by putting a {\bf sleep 30} or possibly a {\bf sleep 60} in the
script just after the mtx-changer load command. If that works, then you should
move the sleep into the actual {\bf mtx-changer} script so that it will be
effective when Bacula runs.
The {\bf update slots} command will first obtain the list of cassettes and
their barcodes from {\bf mtx-changer}. Then it will find each volume in turn
-in the catalog database corresponding to to the barcodes and set its Slot to
+in the catalog database corresponding to the barcodes and set its Slot to
correspond to the value just read. If the Volume is not in the catalog, then
nothing will be done. This command is useful for synchronizing Bacula with the
current magazine in case you have changed magazines or in case you have moved
mount the tape and resume the backup. Otherwise, you simply {\bf mount} the
tape.
-Using this strategy, one typically does a Full backup once a week following by
+Using this strategy, one typically does a Full backup once a week followed by
daily Incremental backups. To minimize the amount of data written to the tape,
-once can do (as I do) a Full backup once a month on the first Sunday of the
+one can do (as I do) a Full backup once a month on the first Sunday of the
month, a Differential backup on the 2nd-5th Sunday of the month, and
incremental backups the rest of the week.
\label{Manual}
\addcontentsline{toc}{subsection}{Manually Changing Tapes}
If you use the strategy presented above, Bacula will ask you to change the
-tape, and you will {\bf unmount} it and the remount it when you have inserted
+tape, and you will {\bf unmount} it and then remount it when you have inserted
the new tape.
If you do not wish to interact with Bacula to change each tape, there are
command would tell Bacula to rewind the tape and on the next job assume the
tape has changed. This strategy may not work on some systems, or on
autochangers because Bacula will still keep the drive open.
-\item The final strategy is the similar to the previous case except that you
+\item The final strategy is similar to the previous case except that you
would use the unmount command to force Bacula to release the drive. Then you
would eject the tape, and remount it as follows:
projects / bacula / docs / commitdiff