| 1 |
\chapter{ANSI and IBM Tape Labels} |
| 2 |
\label{blb:AnsiLabelsChapter} |
| 3 |
\index[general]{ANSI and IBM Tape Labels} |
| 4 |
\index[general]{Labels!Tape} |
| 5 |
|
| 6 |
\bacula{} supports \acs{ANSI} or IBM tape labels as long as you |
| 7 |
enable it. In fact, with the proper configuration, you can |
| 8 |
force \bacula{} to require \acs{ANSI} or IBM labels. |
| 9 |
|
| 10 |
\bacula{} can create an \acs{ANSI} or IBM label, but if Check Labels is |
| 11 |
enabled (see below), \bacula{} will look for an existing label, and |
| 12 |
if it is found, it will keep the label. Consequently, you |
| 13 |
can label the tapes with programs other than \bacula{}, and \bacula{} |
| 14 |
will recognize and support them. |
| 15 |
|
| 16 |
Even though \bacula{} will recognize and write \acs{ANSI} and IBM labels, |
| 17 |
it always writes its own tape labels as well. |
| 18 |
|
| 19 |
When using \acs{ANSI} or IBM tape labeling, you must restrict your Volume |
| 20 |
names to a maximum of six characters. |
| 21 |
|
| 22 |
If you have labeled your Volumes outside of \bacula{}, then the |
| 23 |
ANSI/IBM label will be recognized by \bacula{} only if you have created |
| 24 |
the HDR1 label with {\bf BACULA.DATA} in the Filename field (starting |
| 25 |
with character 5). If \bacula{} writes the labels, it will use |
| 26 |
this information to recognize the tape as a \bacula{} tape. This allows |
| 27 |
ANSI/IBM labeled tapes to be used at sites with multiple machines |
| 28 |
and multiple backup programs. |
| 29 |
|
| 30 |
|
| 31 |
\section{Director Pool Directive} |
| 32 |
|
| 33 |
\begin{bdescription} |
| 34 |
\item [ Label Type = \acs{ANSI} | IBM | Bacula] |
| 35 |
This directive is implemented in the Director Pool resource and in the SD Device |
| 36 |
resource. If it is specified in the SD Device resource, it will take |
| 37 |
precedence over the value passed from the Director to the SD. The default |
| 38 |
is \bdefaultvalue{Label Type = Bacula}. |
| 39 |
\end{bdescription} |
| 40 |
|
| 41 |
\section{Storage Daemon Device Directives} |
| 42 |
|
| 43 |
\begin{bdescription} |
| 44 |
\item [ Label Type = \acs{ANSI} | IBM | Bacula] |
| 45 |
This directive is implemented in the Director Pool resource and in the SD Device |
| 46 |
resource. If it is specified in the the SD Device resource, it will take |
| 47 |
precedence over the value passed from the Director to the SD. |
| 48 |
|
| 49 |
\item [Check Labels = \byesorno{}] |
| 50 |
This directive is implemented in the the SD Device resource. If you intend |
| 51 |
to read \acs{ANSI} or IBM labels, this \textbf{must} be set. Even if the volume is |
| 52 |
not \acs{ANSI} labeled, you can set this to yes, and \bacula{} will check the |
| 53 |
label type. Without this directive set to yes, \bacula{} will assume that |
| 54 |
labels are of \bacula{} type and will not check for \acs{ANSI} or IBM labels. |
| 55 |
In other words, if there is a possibility of \bacula{} encountering an |
| 56 |
ANSI/IBM label, you must set this to yes. |
| 57 |
\end{bdescription} |