
\section*{ANSI and IBM Tape Labels}
\label{_ChapterStart62}
\index[general]{ANSI and IBM Tape Labels} 
\index[general]{Labels!Tape}
\addcontentsline{toc}{section}{ANSI and IBM Tape Labels}

Bacula can support ANSI or IBM tape labels as long as you
enable it.  In fact, with the proper configuration, you can
force Bacula to require ANSI or IBM labels.

Bacula can create an ANSI or IBM label, but if Check Labels is
enabled (see below), Bacula will look for an existing label, and
if it is found, it will keep the label. Consequently, you
can label the tapes with programs other than Bacula, and Bacula
will recognize and support them.

Even though Bacula will recognize and write ANSI and IBM labels, 
it always writes its own tape labels as well.

When using ANSI or IBM tape labeling, you must keep your Volume
names to a maximum of 6 characters.  


\subsection*{Director Pool Directive}
\addcontentsline{toc}{section}{Director Pool Directive}

\begin{description}
\item [ Label Type = ANSI | IBM | Bacula]  
  This directive is implemented in the Director Pool resource and in the SD Device
  resource.  If it is specified in the SD Device resource, it will take
  precedence over the value passed from the Director to the SD.
\end{description}

\subsection*{Storage Daemon Device Directives}
\addcontentsline{toc}{section}{Storage Daemon Device Directives}

\begin{description}
\item [ Label Type = ANSI | IBM | Bacula]  
  This directive is implemented in the Director Pool resource and in the SD Device
  resource.  If it is specified in the the SD Device resource, it will take
  precedence over the value passed from the Director to the SD.

\item [Check Labels = yes | no]
  This directive is implemented in the the SD Device resource.  If you intend
  to read ANSI or IBM labels, this *must* be set.  Even if the volume is
  not ANSI labeled, you can set this to yes, and Bacula will check the
  label type.
\end{description}

