| 1 |
\chapter{The Current State of \bacula{}} |
| 2 |
\label{blb:StateChapter} |
| 3 |
\index[general]{Current state of \bacula{}} |
| 4 |
|
| 5 |
In other words, what is and what is not currently implemented and functional. |
| 6 |
|
| 7 |
\section{What is Implemented} |
| 8 |
\index[general]{Implemented!What} |
| 9 |
\index[general]{What is Implemented} |
| 10 |
|
| 11 |
\begin{bitemize} |
| 12 |
\item Job Control |
| 13 |
\begin{bitemize} |
| 14 |
\item Network backup/restore with centralized Director. |
| 15 |
\item Internal scheduler for automatic |
| 16 |
\bilink{Job}{blb:JobDef} execution. |
| 17 |
\item Scheduling of multiple Jobs at the same time. |
| 18 |
\item You may run one Job at a time or multiple simultaneous Jobs |
| 19 |
(sometimes called multiplexing). |
| 20 |
\item Job sequencing using priorities. |
| 21 |
\item \bilink{Console}{blb:UADef} interface to the Director allowing complete |
| 22 |
control. A shell, Qt5 \acs{GUI}, and Web versions of |
| 23 |
the Console program are available. Note, the Qt5 \acs{GUI} program called |
| 24 |
the \bat{}, offers many additional features over the shell program. |
| 25 |
\end{bitemize} |
| 26 |
|
| 27 |
\item Security |
| 28 |
\begin{bitemize} |
| 29 |
\item Verification of files previously cataloged, permitting a Tripwire like |
| 30 |
capability (system break-in detection). |
| 31 |
\item \acs{CRAM}-\acs{MD}5 password authentication between each component (daemon). |
| 32 |
\item Configurable |
| 33 |
\bilink{\acs{TLS} (\acs{SSL}) communications encryption}{blb:CommEncryption} between each |
| 34 |
component. |
| 35 |
\item Configurable |
| 36 |
\bilink{Data (on Volume) encryption}{blb:DataEncryption} |
| 37 |
on a Client by Client basis. |
| 38 |
\item Computation of \acs{MD}5, \acs{SHA}1 signatures of the file data if requested. |
| 39 |
\end{bitemize} |
| 40 |
|
| 41 |
|
| 42 |
\item Restore Features |
| 43 |
\begin{bitemize} |
| 44 |
\item Restore of one or more files selected interactively either for the |
| 45 |
current backup or a backup prior to a specified time and date. |
| 46 |
\item Restore of a complete system starting from bare metal. This is mostly |
| 47 |
automated for Linux systems and partially automated for Solaris. See |
| 48 |
\bilink{Disaster Recovery Using \bacula{}}{blb:RescueChapter}. This is also |
| 49 |
reported to work on Win2K/XP systems. |
| 50 |
\item Listing and Restoration of files using stand-alone \btool{bls} and \btool{bextract} |
| 51 |
tool programs. Among other things, this permits extraction of |
| 52 |
files when \bacula{} and/or the catalog are not available. Note, the |
| 53 |
recommended way to restore files is using the \bcommandname{restore} command in the |
| 54 |
Console. These programs are designed for use as a last resort. |
| 55 |
\item Ability to restore the catalog database rapidly by using bootstrap |
| 56 |
files (previously saved). |
| 57 |
\item Ability to recreate the catalog database by scanning backup Volumes |
| 58 |
using the \btool{bscan} program. |
| 59 |
\end{bitemize} |
| 60 |
|
| 61 |
\item SQL Catalog |
| 62 |
\begin{bitemize} |
| 63 |
\item Catalog database facility for remembering Volumes, Pools, Jobs, and |
| 64 |
Files backed up. |
| 65 |
\item Support for \mysql{} and \postgresql{} Catalog databases. \sqlite{} is |
| 66 |
deprecated and will ultimately be removed. We strongly recommend that you |
| 67 |
not use \sqlite{}. |
| 68 |
\item User extensible queries to the \mysql{} and \postgresql{} databases. |
| 69 |
\end{bitemize} |
| 70 |
|
| 71 |
\item Advanced Volume and Pool Management |
| 72 |
\begin{bitemize} |
| 73 |
\item Labeled Volumes, preventing accidental overwriting (at least by |
| 74 |
\bacula{}). |
| 75 |
\item Any number of Jobs and Clients can be backed up to a single Volume. |
| 76 |
That is, you can backup and restore Linux, Unix, Sun, and Windows machines to |
| 77 |
the same Volume. |
| 78 |
\item Multi-volume saves. When a Volume is full, \textbf{\bacula{}} automatically |
| 79 |
requests the next Volume and continues the backup. |
| 80 |
\item |
| 81 |
\bilink{Pool and Volume}{blb:PoolResource} library management |
| 82 |
providing Volume flexibility (e.g. monthly, weekly, daily Volume sets, Volume |
| 83 |
sets segregated by Client, \ldots{}). |
| 84 |
\item Machine independent Volume data format. Linux, Solaris, and Windows |
| 85 |
clients can all be backed up to the same Volume if desired. |
| 86 |
\item The Volume data format is upwards compatible so that old Volumes |
| 87 |
can always be read. |
| 88 |
\item A flexible |
| 89 |
\bilink{message}{blb:MessagesChapter} handler including routing |
| 90 |
of messages from any daemon back to the Director and automatic email |
| 91 |
reporting. |
| 92 |
\item Data spooling to disk during backup with subsequent write to tape from |
| 93 |
the spooled disk files. This prevents tape ``shoe shine'' during |
| 94 |
Incremental/Differential backups. |
| 95 |
\end{bitemize} |
| 96 |
|
| 97 |
\item Advanced Support for most Storage Devices |
| 98 |
\begin{bitemize} |
| 99 |
\item Autochanger support using a simple shell interface that can interface |
| 100 |
to virtually any autoloader program. A script for \mtx{} is provided. |
| 101 |
\item Support for autochanger barcodes -- automatic tape labeling from |
| 102 |
barcodes. |
| 103 |
\item Automatic support for multiple autochanger magazines either using |
| 104 |
barcodes or by reading the tapes. |
| 105 |
\item Support for multiple drive autochangers. |
| 106 |
\item Raw device backup/restore. Restore must be to the same device. |
| 107 |
\item All Volume blocks (approximately 64K bytes) contain a data checksum. |
| 108 |
\item Migration support -- move data from one Pool to another or |
| 109 |
one Volume to another. |
| 110 |
\item Supports writing to \acs{DVD}. |
| 111 |
\end{bitemize} |
| 112 |
|
| 113 |
\item Multi-Operating System Support |
| 114 |
\begin{bitemize} |
| 115 |
\item Programmed to handle arbitrarily long filenames and messages. |
| 116 |
\item \acs{GZIP} compression on a file by file basis done by the Client program if |
| 117 |
requested before network transit. |
| 118 |
\item Saves and restores \acs{POSIX} \acsp{ACL} and Extended Attributes on most \acs{OS}es if |
| 119 |
enabled. |
| 120 |
\item Access control lists for Consoles that permit restricting user access |
| 121 |
to only their data. |
| 122 |
\item Support for save/restore of files larger than 2GB. |
| 123 |
\item Support for 64 bit machines, e.g. amd64, Sparc. |
| 124 |
\item Support ANSI and IBM tape labels. |
| 125 |
\item Support for Unicode filenames (e.g. Chinese) on Win32 machines |
| 126 |
\item Consistent backup of open files on Win32 systems (WinXP, Win2003, |
| 127 |
and Vista) |
| 128 |
but not Win2000, using Volume Shadow Copy (\acs{VSS}). |
| 129 |
\item Support for path/filename lengths of up to 64K on Win32 machines |
| 130 |
(unlimited on Unix/Linux machines). |
| 131 |
\end{bitemize} |
| 132 |
|
| 133 |
\item Miscellaneous |
| 134 |
\begin{bitemize} |
| 135 |
\item Multi-threaded implementation. |
| 136 |
\item A comprehensive and extensible |
| 137 |
\bilink{configuration file}{blb:DirectorChapter} for each daemon. |
| 138 |
\end{bitemize} |
| 139 |
\end{bitemize} |
| 140 |
|
| 141 |
\section{Advantages Over Other Backup Programs} |
| 142 |
\index[general]{Advantages of \bacula{} Over Other Backup Programs } |
| 143 |
\index[general]{Programs!Advantages of \bacula{} Over Other Backup } |
| 144 |
|
| 145 |
\begin{bitemize} |
| 146 |
\item Since there is a client for each machine, you can backup |
| 147 |
and restore clients of any type ensuring that all attributes |
| 148 |
of files are properly saved and restored. |
| 149 |
\item It is also possible to backup clients without any client |
| 150 |
software by using \acs{NFS} or Samba. However, if possible, we |
| 151 |
recommend running a Client File daemon on each machine to be |
| 152 |
backed up. |
| 153 |
\item \bacula{} handles multi-volume backups. |
| 154 |
\item A full comprehensive \acs{SQL} standard database of all files backed up. This |
| 155 |
permits online viewing of files saved on any particular Volume. |
| 156 |
\item Automatic pruning of the database (removal of old records) thus |
| 157 |
simplifying database administration. |
| 158 |
\item Any \acs{SQL} database engine can be used making \bacula{} very flexible. |
| 159 |
Drivers currently exist for \mysql{}, \postgresql{}, and \sqlite{}. |
| 160 |
Note: SQLite is deprecated; it is strongly recommended not to use it. |
| 161 |
\item The modular but integrated design makes \bacula{} very scalable. |
| 162 |
\item Since \bacula{} uses client file servers, any database or |
| 163 |
other application can be properly shutdown by \bacula{} using the |
| 164 |
native tools of the system, backed up, then restarted (all |
| 165 |
within a \bacula{} Job). |
| 166 |
\item \bacula{} has a built-in Job scheduler. |
| 167 |
\item The Volume format is documented and there are simple \texttt{C} programs to |
| 168 |
read/write it. |
| 169 |
\item \bacula{} uses well defined (\acs{IANA} registered) \acs{TCP}/\acs{IP} ports -- no rpcs, no |
| 170 |
shared memory. |
| 171 |
\item \bacula{} installation and configuration is relatively simple compared to |
| 172 |
other comparable products. |
| 173 |
\item According to one user \bacula{} is as fast as the big major commercial |
| 174 |
applications. |
| 175 |
\item According to another user \bacula{} is four times as fast as another |
| 176 |
commercial application, probably because that application stores its catalog |
| 177 |
information in a large number of individual files rather than an \acs{SQL} database |
| 178 |
as \bacula{} does. |
| 179 |
\item Aside from several \acs{GUI} administrative interfaces, \bacula{} has a |
| 180 |
comprehensive shell administrative interface, which allows the |
| 181 |
administrator to use tools such as \btool{ssh} to administrate any part of |
| 182 |
\bacula{} from anywhere (even from home). |
| 183 |
\item \bacula{} has a Rescue \acs{CD} for Linux systems with the following features: |
| 184 |
\begin{bitemize} |
| 185 |
\item You build it on your own system from scratch with one simple command: |
| 186 |
\btool{make} -- well, then make burn. |
| 187 |
\item It uses your kernel |
| 188 |
\item It captures your current disk parameters and builds scripts that allow |
| 189 |
you to automatically repartition a disk and format it to put it back to what |
| 190 |
you had before. |
| 191 |
\item It has a script that will restart your networking (with the right \acs{IP} |
| 192 |
address) |
| 193 |
\item It has a script to automatically mount your hard disks. |
| 194 |
\item It has a full \bacula{} \acs{FD} statically linked |
| 195 |
\item You can easily add additional data/programs, \ldots{} to the disk. |
| 196 |
\end{bitemize} |
| 197 |
|
| 198 |
\end{bitemize} |
| 199 |
|
| 200 |
\section{Current Implementation Restrictions} |
| 201 |
\index[general]{Current Implementation Restrictions } |
| 202 |
\index[general]{Restrictions!Current Implementation } |
| 203 |
|
| 204 |
\begin{bitemize} |
| 205 |
\item It is very unusual to attempt to restore two Jobs |
| 206 |
that ran simultaneously in a single restore, but if |
| 207 |
you do, please be aware that unless you had |
| 208 |
data spooling turned on and the spool file held the full |
| 209 |
contents of both Jobs during the backup, the restore will not |
| 210 |
work correctly. In other terms, \bacula{} cannot restore |
| 211 |
two jobs in the same restore if the Jobs' data blocks were |
| 212 |
intermixed on the backup medium. The problem is resolved by |
| 213 |
simply doing two restores, one for each Job. |
| 214 |
Normally this can happen only if you manually enter specific |
| 215 |
JobIds to be restored in a single restore Job. |
| 216 |
\item \bacula{} can generally restore any backup made from one client |
| 217 |
to any other client. However, if the architecture is significantly |
| 218 |
different (i.e. 32 bit architecture to 64 bit or Win32 to Unix), |
| 219 |
some restrictions may apply (e.g. Solaris door files do not exist |
| 220 |
on other Unix/Linux machines; there are reports that Zlib compression |
| 221 |
written with 64 bit machines does not always read correctly on a 32 bit |
| 222 |
machine). |
| 223 |
\end{bitemize} |
| 224 |
|
| 225 |
\section{Design Limitations or Restrictions} |
| 226 |
\index[general]{Restrictions!Design Limitations or } |
| 227 |
\index[general]{Design Limitations or Restrictions } |
| 228 |
|
| 229 |
\begin{bitemize} |
| 230 |
\item Names (resource names, Volume names, and such) defined in \bacula{} |
| 231 |
configuration files are limited to a fixed number of |
| 232 |
characters. Currently the limit is defined as 127 characters. Note, |
| 233 |
this does not apply to filenames, which may be arbitrarily long. |
| 234 |
\item Command line input to some of the stand alone tools -- e.g. \btool{btape}, |
| 235 |
\btool{bconsole} is restricted to several hundred characters maximum. |
| 236 |
Normally, this is not a restriction, except in the case of listing |
| 237 |
multiple Volume names for programs such as \btool{bscan}. To avoid |
| 238 |
this command line length restriction, please use a \bfilename{.bsr} |
| 239 |
file to specify the Volume names. |
| 240 |
\item \bacula{} configuration files for each of the components can be |
| 241 |
any length. However, the length of an individual line is limited |
| 242 |
to 500 characters after which it is truncated. If you need lines |
| 243 |
longer than 500 characters for directives such as \acsp{ACL} where |
| 244 |
they permit a list of names are character strings simply |
| 245 |
specify multiple short lines repeating the directive on |
| 246 |
each line but with different list values. |
| 247 |
|
| 248 |
\end{bitemize} |
| 249 |
|
| 250 |
\section{Items to Note} |
| 251 |
\index[general]{Items to Note} |
| 252 |
\begin{bitemize} |
| 253 |
\item \bacula{}'s Differential and Incremental \emph{normal} backups are based |
| 254 |
on time stamps. Consequently, if you move files into an existing directory |
| 255 |
or move a whole directory into the backup fileset after a Full backup, those |
| 256 |
files will probably not be backed up by an Incremental save because they will |
| 257 |
have old dates. This problem is corrected by using Accurate mode backups |
| 258 |
or by explicitly updating the date/time stamp on all moved files. |
| 259 |
\item In older versions of \bacula{} ($\leq{}$ 3.0.x), if you have over 4 billion file |
| 260 |
entries stored in your database, the database FileId is likely to overflow. |
| 261 |
This limitation does not apply to current \bacula{} versions. |
| 262 |
\item In non \emph{Accurate} mode, files deleted after a Full save will be |
| 263 |
included in a restoration. This is typical for most similar backup programs. |
| 264 |
To avoid this, use Accurate mode backup. |
| 265 |
\end{bitemize} |