| 1 |
\chapter{Critical Items to Implement Before Production} |
| 2 |
\label{blb:CriticalChapter} |
| 3 |
\index[general]{Production!Critical Items to Implement Before} |
| 4 |
\index[general]{Critical Items to Implement Before Production} |
| 5 |
|
| 6 |
We recommend you take your time before implementing a production a \bacula{} |
| 7 |
backup system since \bacula{} is a rather complex program, and if you make a |
| 8 |
mistake, you may suddenly find that you cannot restore your files in case |
| 9 |
of a disaster. This is especially true if you have not previously used a |
| 10 |
major backup product. |
| 11 |
|
| 12 |
If you follow the instructions in this chapter, you will have covered most of |
| 13 |
the major problems that can occur. It goes without saying that if you ever |
| 14 |
find that we have left out an important point, please inform us, so |
| 15 |
that we can document it to the benefit of everyone. |
| 16 |
|
| 17 |
|
| 18 |
\section{Critical Items} |
| 19 |
\label{blb:Critical} |
| 20 |
\index[general]{Critical Items} |
| 21 |
\index[general]{Items!Critical} |
| 22 |
|
| 23 |
The following assumes that you have installed \bacula{}, you more or less |
| 24 |
understand it, you have at least worked through the tutorial or have |
| 25 |
equivalent experience, and that you have set up a basic production |
| 26 |
configuration. If you haven't done the above, please do so and then come back |
| 27 |
here. The following is a sort of checklist that points with perhaps a brief |
| 28 |
explanation of why you should do it. In most cases, you will find the |
| 29 |
details elsewhere in the manual. The order is more or less the order you |
| 30 |
would use in setting up a production system (if you already are in |
| 31 |
production, use the checklist anyway). |
| 32 |
|
| 33 |
\begin{bitemize} |
| 34 |
\item Test your tape drive for compatibility with \bacula{} by using the \bcommandname{test} |
| 35 |
command in the See the \bxlink{btape}{blb:btape}{utility}{section} of the \butilityman{}. |
| 36 |
\item Better than doing the above is to walk through the nine steps in the |
| 37 |
\bxlink{Tape Testing}{blb:TapeTestingChapter}{problems}{chapter} of the \bproblemman{}. It |
| 38 |
may take you a bit of time, but it will eliminate surprises. |
| 39 |
\item Test the end of tape handling of your tape drive by using the |
| 40 |
\bcommandname{fill} command in the \bxlink{btape program}{blb:btape}{utility}{section} (Part of the \butilityman{}) |
| 41 |
\item If you are using a Linux 2.4 kernel, make sure that \btool{/lib/tls} is disabled. \bacula{} |
| 42 |
does not work with this library. See the second point under |
| 43 |
\bilink{Supported Operating Systems.}{blb:SupportedOSes} |
| 44 |
\item Do at least one restore of files. If you backup multiple \acs{OS} types |
| 45 |
(Linux, Solaris, HP, MacOS, FreeBSD, Win32, \ldots{}), |
| 46 |
restore files from each system type. The |
| 47 |
\bilink{Restoring Files}{blb:RestoreChapter} chapter shows you how. |
| 48 |
\item Write a bootstrap file to a separate system for each backup job. The |
| 49 |
\bdirectivename{Write Bootstrap} directive is described in the |
| 50 |
\bilink{Director Configuration}{blb:writebootstrap} chapter of the |
| 51 |
manual, and more details are available in the |
| 52 |
\bilink{Bootstrap File}{blb:BootstrapChapter} chapter. Also, the default |
| 53 |
\bfilename{bacula-dir.conf} comes with a \bdirectivename{Write Bootstrap} directive defined. This allows |
| 54 |
you to recover the state of your system as of the last backup. |
| 55 |
\item Backup your catalog. An example of this is found in the default |
| 56 |
\bfilename{bacula-dir.conf} file. The backup script is installed by default and |
| 57 |
should handle any database, though you may want to make your own local |
| 58 |
modifications. See also \bilink{Backing Up Your \bacula{} Database --- Security Considerations}{blb:BackingUpBaculaSecurityConsiderations} for more |
| 59 |
information. |
| 60 |
\item Write a bootstrap file for the catalog. An example of this is found in |
| 61 |
the default \bfilename{bacula-dir.conf} file. This will allow you to quickly restore your |
| 62 |
catalog in the event it is wiped out -- otherwise it is many excruciating |
| 63 |
hours of work. |
| 64 |
\item Make a copy of the \bfilename{bacula-dir.conf}, \bfilename{bacula-sd.conf}, and |
| 65 |
\bfilename{bacula-fd.conf} files that you are using on your server. Put it in a safe |
| 66 |
place (on another machine) as these files can be difficult to |
| 67 |
reconstruct if your server dies. |
| 68 |
\item Make a \bacula{} Rescue CDROM! See the |
| 69 |
\bilink{Disaster Recovery Using a \bacula{} Rescue CDROM}{blb:RescueChapter} chapter. |
| 70 |
It is trivial to make such a CDROM, and it can make system recovery in the event of |
| 71 |
a lost hard disk infinitely easier. |
| 72 |
\item \bacula{} assumes all filenames are in \acs{UTF}-8 format. This is important |
| 73 |
when saving the filenames to the catalog. For Win32 machine, \bacula{} will |
| 74 |
automatically convert from Unicode to UTF-8, but on Unix, Linux, *BSD, |
| 75 |
and MacOS X machines, you must explicitly ensure that your locale is set |
| 76 |
properly. Typically this means that the \textbf{LANG} environment variable |
| 77 |
must end in \textbf{.UTF-8}. A full example is \textbf{en\_US.UTF-8}. The |
| 78 |
exact syntax may vary a bit from OS to OS, and exactly how you define it |
| 79 |
will also vary. |
| 80 |
|
| 81 |
On most modern Win32 machines, you can edit the configuration files with \textbf{notepad} |
| 82 |
and choose output encoding UTF-8. |
| 83 |
\end{bitemize} |
| 84 |
|
| 85 |
\section{Recommended Items} |
| 86 |
\index[general]{Items!Recommended} |
| 87 |
\index[general]{Recommended Items} |
| 88 |
|
| 89 |
Although these items may not be critical, they are recommended and will help |
| 90 |
you avoid problems. |
| 91 |
|
| 92 |
\begin{bitemize} |
| 93 |
\item Read the \bilink{Quick Start Guide to \bacula{}}{blb:QuickStartChapter} |
| 94 |
\item After installing and experimenting with \bacula{}, read and work carefully |
| 95 |
through the examples in the |
| 96 |
\bilink{Tutorial}{blb:TutorialChapter} chapter of this manual. |
| 97 |
\item Learn what each of the \bxdlink{\bacula{} Utility Programs}{blb:TheUtilityChapter}{utility}{chapter} |
| 98 |
does. |
| 99 |
\item Set up reasonable retention periods so that your catalog does not grow |
| 100 |
to be too big. See the following three chapters: |
| 101 |
\begin{bitemize} |
| 102 |
\item \bilink{Recycling your Volumes}{blb:RecyclingChapter}, |
| 103 |
\item \bilink{Basic Volume Management}{blb:DiskChapter}, |
| 104 |
\item \bilink{Using Pools to Manage Volumes}{blb:PoolsChapter}. |
| 105 |
\end{bitemize} |
| 106 |
\item Perform a bare metal recovery using the \bacula{} Rescue CDROM. See the |
| 107 |
\bilink{Disaster Recovery Using a \bacula{} Rescue CDROM}{blb:RescueChapter} |
| 108 |
chapter. |
| 109 |
\end{bitemize} |
| 110 |
|
| 111 |
If you absolutely must implement a system where you write a different |
| 112 |
tape each night and take it offsite in the morning. We recommend that you do |
| 113 |
several things: |
| 114 |
\begin{bitemize} |
| 115 |
\item Write a bootstrap file of your backed up data and a bootstrap file |
| 116 |
of your catalog backup to a usb disk or a \acs{CDROM} and take that with |
| 117 |
the tape. If this is not possible, try to write those files to another |
| 118 |
computer or offsite computer, or send them as email to a friend. If none |
| 119 |
of that is possible, at least print the bootstrap files and take that |
| 120 |
offsite with the tape. Having the bootstrap files will make recovery |
| 121 |
much easier. |
| 122 |
\item It is better not to force \bacula{} to load a particular tape each day. |
| 123 |
Instead, let \bacula{} choose the tape. If you need to know what tape to |
| 124 |
mount, you can print a list of recycled and appendable tapes daily, and |
| 125 |
select any tape from that list. \bacula{} may propose a particular tape |
| 126 |
for use that it considers optimal, but it will accept any valid tape |
| 127 |
from the correct pool. |
| 128 |
\end{bitemize} |