%%
%%

\section*{Critical Items to Implement Before Going Production}
\label{_ChapterStart32}
\index[general]{Production!Critical Items to Implement Before Going }
\index[general]{Critical Items to Implement Before Going Production }
\addcontentsline{toc}{section}{Critical Items to Implement Before Going
Production}

\subsection*{General}
\index[general]{General }
\addcontentsline{toc}{subsection}{General}

We recommend you take your time before implementing a Bacula backup system
since Bacula is a rather complex program, and if you make a mistake, you may
suddenly find that you cannot restore your files in case of a disaster.
This is especially true if you have not previously used a major backup
product. 

If you follow the instructions in this chapter, you will have covered most of
the major problems that can occur. It goes without saying that if you ever
find that we have left out an important point, please inform us, so
that we can document it to the benefit of everyone. 

\label{Critical}
\subsection*{Critical Items}
\index[general]{Critical Items }
\index[general]{Items!Critical }
\addcontentsline{toc}{subsection}{Critical Items}

The following assumes that you have installed Bacula, you more or less
understand it, you have at least worked through the tutorial or have
equivalent experience, and that you have set up a basic production
configuration. If you haven't done the above, please do so and then come back
here. The following is a sort of checklist that points with perhaps a brief
explanation of why you should do it. You will find the details elsewhere in the
manual. The order is more or less the order you would use in setting up a
production system (if you already are in production, use the checklist anyway). 

\begin{itemize}
\item Test your tape drive for compatibility with Bacula by using the  test
   command in the \ilink{btape}{btape} program. 
\item Better than doing the above is to walk through the nine steps in the  
   \ilink{Tape Testing}{_ChapterStart27} chapter of the manual. It 
   may take you a bit of time, but it will eliminate surprises. 
\item Test your the end of tape handling of your tape drive by using the
   fill command in the \ilink{btape}{btape} program.
\item If you are using a 2.4 kernel, make sure that /lib/tls is disabled. Bacula
   does not work with this library. See the second point under 
   \ilink{ Supported Operating Systems.}{SupportedOSes} 
\item Do at least one restore of files. If you backup both Unix and Win32
   systems,  restore files from each system type. The 
   \ilink{Restoring Files}{_ChapterStart13} chapter shows you how. 
\item Write a bootstrap file to a separate system for each backup job.  The
   Write Bootstrap directive is described in the  
   \ilink{Director Configuration}{writebootstrap}  chapter of the
   manual, and more details are available in the  
   \ilink{Bootstrap File}{_ChapterStart43} chapter. Also, the default
   bacula-dir.conf comes with a Write Bootstrap directive defined. This  allows
   you to recover the state of your system as of the last backup.  
\item Backup your catalog. An example of this is found in the default 
   bacula-dir.conf file. The backup script is installed by default and  should
   handle any database, though you may want to make your own  local
   modifications.  
\item Write a bootstrap file for the catalog. An example of this is found in
   the default bacula-dir.conf file. This will allow you to quickly restore your
   catalog in the event it is wiped out -- otherwise it  is many excruciating
   hours of work.  
\item Make a Bacula Rescue CDROM! See the 
   \ilink{Disaster Recovery Using a Bacula Rescue
   CDROM}{_ChapterStart38} chapter. It is trivial to  make such a CDROM,
   and it can make system recovery in the event of  a lost hard disk infinitely
   easier. 
\item After doing your first backup restore some or all the data.  Do this for
   at least one client on each different OS (e.g. Linux, FreeBSD, Solaris, Win32).
\end{itemize}

\subsection*{Recommended Items}
\index[general]{Items!Recommended }
\index[general]{Recommended Items }
\addcontentsline{toc}{subsection}{Recommended Items}

Although these items may not be critical, they are recommended and will help
you avoid problems. 

\begin{itemize}
\item Read the \ilink{Quick Start Guide to Bacula}{_ChapterStart37} 
\item After installing and experimenting with Bacula, read and work carefully 
   through the examples in the 
   \ilink{Tutorial}{_ChapterStart1} chapter  of this manual. 
\item Learn what each of the \ilink{Bacula Utility Programs}{_ChapterStart9} 
does. 
\item Set up reasonable retention periods so that your catalog does not  grow
   to be too big. See the following three chapters:\\
   \ilink{Recycling your Volumes}{_ChapterStart22},\\
   \ilink{Basic Volume Management}{_ChapterStart39},\\
   \ilink{Using Pools to Manage Volumes}{_ChapterStart11}. 
\item Perform a bare metal recovery using the Bacula Rescue CDROM.  See the 
   \ilink{Disaster Recovery Using a Bacula Rescue CDROM}{_ChapterStart38}
    chapter. 
\end{itemize}

If you absolutely must implement a system where you write a different 
tape each night and take it offsite in the morning. We recommend that you do 
several things:
\begin{itemize}
\item Write a bootstrap file of your backed up data and a bootstrap file
   of your catalog backup to a floppy disk or a CDROM, and take that with
   the tape.  If this is not possible, try to write those files to another 
   computer or offsite computer, or send them as email to a friend. If none
   of that is possible, at least print the bootstrap files and take that
   offsite with the tape.  Having the bootstrap files will make recovery
   much easier.
\item It is better not to force Bacula to load a particular tape each day.
   Instead, let Bacula choose the tape.  If you need to know what tape to
   mount, you can print a list of recycled and appendable tapes daily, and
   select any tape from that list.  Bacula may propose a particular tape
   for use that it considers optimal, but it will accept any valid tape
   from the correct pool.
\end{itemize}
