| 1 |
\chapter{What is Bacula?} |
| 2 |
\label{ch:whatisbacula} |
| 3 |
|
| 4 |
\bacula{} is a set of computer btools that permits the system |
| 5 |
administrator to manage backup, recovery, and verification of computer data |
| 6 |
across a network of computers of different kinds. Bacula can also run entirely |
| 7 |
upon a single computer and can backup to various types of media, including tape |
| 8 |
and disk. |
| 9 |
|
| 10 |
Bacula provides the following key features: |
| 11 |
|
| 12 |
\begin{description} |
| 13 |
%\setlength\labelsep{1.3em}% |
| 14 |
\item[Network Based] |
| 15 |
All backup and restores are done via the network. |
| 16 |
This permits Bacula to run on a single server and backup any |
| 17 |
computer in your data center. |
| 18 |
|
| 19 |
\item[Centralized Administration] |
| 20 |
Bacula administration is centralized in the Director. |
| 21 |
Centralizing the administration is essential when your network |
| 22 |
grows beyond a few computers. |
| 23 |
|
| 24 |
\item[Runs Automatically] |
| 25 |
Once setup, Bacula runs automatically. |
| 26 |
Normally a properly configured Bacula installation requires little |
| 27 |
maintenance or intervention except when adding new machines or |
| 28 |
when hardware errors occur. |
| 29 |
|
| 30 |
\item[Performs Bookkeeping] |
| 31 |
Bacula does the hard bookkeeping by maintaining |
| 32 |
a catalog of what is backed up and where. |
| 33 |
If you have hundreds or thousands of machines to be backed up, |
| 34 |
it is essential that the bookkeeping is automatically maintained |
| 35 |
by a btool rather than requiring human intervention. |
| 36 |
|
| 37 |
\item[Multi-platform] |
| 38 |
Bacula is compatible with a wide range of platforms: |
| 39 |
*BSD, Unix, Linux, MS~Windows, Mac~OS~X, and others as well as |
| 40 |
a large range of hardware. |
| 41 |
|
| 42 |
\item[Modular Design] |
| 43 |
means it scales well from small shops (one machine) to very large ones (tens of thousands of machines). |
| 44 |
|
| 45 |
\item[Multiple Backup Media] |
| 46 |
Bacula handles a variety of different media such as disk, tape, autochangers. |
| 47 |
There is no need for expensive Virtual Tape Libraries (VTL), |
| 48 |
Bacula knows how to write to disk out of the box. |
| 49 |
|
| 50 |
\item[Reliable] |
| 51 |
Bacula includes advance tools for memory and lock management, it is very |
| 52 |
common to run it without problems months at a time. |
| 53 |
|
| 54 |
\item[High Performance] |
| 55 |
Bacula's modern multi-threaded design allows running |
| 56 |
multiple simultaneous backups and can achieve speeds writing to |
| 57 |
tape at more than 200~Megabytes per second, or faster. |
| 58 |
|
| 59 |
\item[Customizable] |
| 60 |
Bacula can easily be customized to almost any backup\,/\,restore |
| 61 |
need. |
| 62 |
|
| 63 |
\item[Rapid Restores] |
| 64 |
Easy and rapid restores using Bacula's database and graphical user |
| 65 |
interface. |
| 66 |
|
| 67 |
\item[Advanced Reporting, Notification, Monitoring] |
| 68 |
Bacula has excellent reporting addons such as \bweb{}; those tools |
| 69 |
permit to get graphical and raw statistics for custom reports, |
| 70 |
billings, trends, optimizations and capacity planning. |
| 71 |
|
| 72 |
Bacula provides very good notifications and monitoring capabilities, and can |
| 73 |
also be extremely well integrated into monitoring tools |
| 74 |
such as Nagios\textregistered{}. |
| 75 |
|
| 76 |
%\item[Open Source] |
| 77 |
%Bacula is Open Source software, thus there are no license |
| 78 |
%fees. No lock-in. You can see and modify what the code does. |
| 79 |
|
| 80 |
\end{description} |
| 81 |
|
| 82 |
|
| 83 |
\section{Architecture} |
| 84 |
\label{ch:baculaarchitecture} |
| 85 |
\index{Bacula!Architecture} |
| 86 |
Bacula is made up of the following five major components or services: |
| 87 |
Director, Console, Client, Storage, and Catalog. |
| 88 |
|
| 89 |
\bimageH[1\linewidth]{architecture-master}{Bacula Components}{fig:components} |
| 90 |
%% \begin{figure}[htpb] |
| 91 |
%% \centering |
| 92 |
%% \includegraphics[width=\linewidth]{components} |
| 93 |
%% \caption{Bacula Components} |
| 94 |
%% \label{fig:components} |
| 95 |
%% \end{figure} |
| 96 |
|
| 97 |
|
| 98 |
\section{Bacula Director} |
| 99 |
\index{Director} |
| 100 |
\label{ch:defdir} |
| 101 |
The Bacula Director is the btool that supervises |
| 102 |
all the backup, restore and verify operations. The system |
| 103 |
administrator uses the Bacula Director to schedule backups and to |
| 104 |
recover files. The Director runs as a daemon (or service) in the background. |
| 105 |
If configured by the system administrator, users may access the Director |
| 106 |
to do backups or restores of their files through restricted consoles. |
| 107 |
|
| 108 |
|
| 109 |
\section{Bacula Console} |
| 110 |
\label{ch:defua} |
| 111 |
\index{Console} |
| 112 |
The Bacula Console is the btool that allows the |
| 113 |
administrator or user to communicate with the Bacula Director. |
| 114 |
Bacula Consoles are available with different user front ends: |
| 115 |
text-based console interface, graphical user interface, and web |
| 116 |
interface. |
| 117 |
The first and simplest is to run the \texttt{bconsole} btool in a shell |
| 118 |
window (i.\,e. TTY interface). Most system administrators will find this |
| 119 |
completely adequate. There are several graphical user interfaces, the |
| 120 |
most comprehensive being \textbf{bat} (Bacula Administration Tool) written using |
| 121 |
the Qt4 toolkit. There are also several web interfaces, the most complete |
| 122 |
being \textbf{BWeb Management Suite} available in the Bacula Enterprise version. |
| 123 |
|
| 124 |
\section{Bacula Client} |
| 125 |
\index{Client} |
| 126 |
\label{ch:deffd} |
| 127 |
The Bacula Client service (also known as the File Daemon) is the software |
| 128 |
btool that is installed on each machine to be backed up. |
| 129 |
It is specific to the operating system on which it runs and is responsible |
| 130 |
for providing the file attributes and data when requested by the Director. The Client |
| 131 |
services are also responsible for the file system dependent part of |
| 132 |
restoring the file attributes and data during a recovery operation. |
| 133 |
This btool runs as a daemon on the machine to be backed up.\par |
| 134 |
Bacula Enterprise clients, distributed as binary packages, are available for a wide variety of Operating Systems\footnote{Gnu/Linux flavors, Windows systems, Solaris, Mac OSX, AIX, HP-UX and more} |
| 135 |
|
| 136 |
\section{Bacula Storage} |
| 137 |
\index{Storage} |
| 138 |
\label{ch:defsd} |
| 139 |
The Bacula Storage service is the software btool that |
| 140 |
performs the storage and recovery of the file attributes and data to the |
| 141 |
physical backup media or volumes. In other words, the Storage Daemon is |
| 142 |
responsible for reading and writing your tapes (or other storage media, |
| 143 |
e.\,g. files). The Storage services runs as |
| 144 |
a daemon on the machine that has the backup device (for example a tape |
| 145 |
drive or a large disk). |
| 146 |
|
| 147 |
\section{Catalog} |
| 148 |
\index{Catalog} |
| 149 |
\label{ch:defcat} |
| 150 |
The Catalog services are comprised of the software btools |
| 151 |
responsible for maintaining the file indexes and volume databases for |
| 152 |
all files backed up. The Catalog services permit the system |
| 153 |
administrator or user to quickly locate and restore any desired file. |
| 154 |
The Catalog services sets Bacula apart from simple archiver btools like |
| 155 |
tar and dump, because the catalog maintains a record of all Volumes used, |
| 156 |
all Jobs run, and all Files saved, permitting efficient restoration and |
| 157 |
Volume management. \par\medskip |
| 158 |
|
| 159 |
Bacula can run with three SQL database backends: MySQL, PostgreSQL and SQLite. We strongly recommend using SQLite only for testing purposes.\footnote{Actually, \baculasystems{} does not even provide packages with SQLite as a Catalog database backend.}. The two others, MySQL and PostgreSQL, provide quite a number of features, including rapid indexing, arbitrary queries, and security. |
| 160 |
|
| 161 |
\section{Bootstrap File Concept} |
| 162 |
A \emph{bootstrap file} is an ASCII file containing just the information Bacula needs to find a specific set of data and it is really important in Bacula: |
| 163 |
\begin{bitemize} |
| 164 |
\item With a bootstrap file, you can restore without a Catalog; |
| 165 |
\item Bacula uses bootstrap files in Restore, Migrate or Copy Jobs, and more; |
| 166 |
\item The bootstrap files are created and updated automatically for each Job defined when they run. |
| 167 |
\end{bitemize} |