4 \section*{The Current State of Bacula}
6 \index[general]{Current State of Bacula }
7 \addcontentsline{toc}{section}{Current State of Bacula}
9 In other words, what is and what is not currently implemented and functional.
11 \subsection*{What is Implemented}
12 \index[general]{Implemented!What}
13 \index[general]{What is Implemented}
14 \addcontentsline{toc}{subsection}{What is Implemented}
17 \item Network backup/restore with centralized Director.
18 \item Internal scheduler for automatic
19 \ilink{Job}{JobDef} execution.
20 \item Scheduling of multiple Jobs at the same time.
21 \item You may run one Job at a time or multiple simultaneous Jobs.
22 \item Job sequencing using priorities.
23 \item Restore of one or more files selected interactively either for the
24 current backup or a backup prior to a specified time and date.
25 \item Restore of a complete system starting from bare metal. This is mostly
26 automated for Linux systems and partially automated for Solaris. See
27 \ilink{Disaster Recovery Using Bacula}{_ChapterStart38}. This is also
28 reported to work on Win2K/XP systems.
29 \item Listing and Restoration of files using stand-alone {\bf bls} and {\bf
30 bextract} tool programs. Among other things, this permits extraction of files
31 when Bacula and/or the catalog are not available. Note, the recommended way
32 to restore files is using the restore command in the Console. These programs
33 are designed for use as a last resort.
34 \item Ability to recreate the catalog database by scanning backup Volumes
35 using the {\bf bscan} program.
37 \ilink{Console}{UADef} interface to the Director allowing complete
38 control. A shell, GNOME GUI and wxWidgets GUI versions of the Console program
39 are available. Note, the GNOME GUI program currently offers very few
40 additional features over the shell program.
41 \item Verification of files previously cataloged, permitting a Tripwire like
42 capability (system break-in detection).
43 \item CRAM-MD5 password authentication between each component (daemon).
45 \ilink{TLS (ssl) encryption}{_ChapterStart61} between each component.
46 \item A comprehensive and extensible
47 \ilink{configuration file}{_ChapterStart40} for each daemon.
48 \item Catalog database facility for remembering Volumes, Pools, Jobs, and
50 \item Support for SQLite, PostgreSQL, and MySQL Catalog databases.
51 \item User extensible queries to the SQLite, PostgreSQL and MySQL databases.
52 \item Labeled Volumes, preventing accidental overwriting (at least by
54 \item Any number of Jobs and Clients can be backed up to a single Volume.
55 That is, you can backup and restore Linux, Unix, Sun, and Windows machines to
57 \item Multi-volume saves. When a Volume is full, {\bf Bacula} automatically
58 requests the next Volume and continues the backup.
60 \ilink{Pool and Volume}{PoolResource} library management
61 providing Volume flexibility (e.g. monthly, weekly, daily Volume sets, Volume
62 sets segregated by Client, ...).
63 \item Machine independent Volume data format. Linux, Solaris, and Windows
64 clients can all be backed up to the same Volume if desired.
66 \ilink{ message}{MessageResource} handler including routing
67 of messages from any daemon back to the Director and automatic email
69 \item Multi-threaded implementation.
70 \item Programmed to handle arbitrarily long filenames and messages.
71 \item GZIP compression on a file by file basis done by the Client program if
72 requested before network transit.
73 \item Computation of MD5 or SHA1 signatures of the file data if requested.
74 \item Saves and restores POSIX ACLs on most OSes if enabled.
75 \item Autochanger support using a simple shell interface that can interface
76 to virtually any autoloader program. A script for {\bf mtx} is provided.
77 \item Support for autochanger barcodes -- automatic tape labeling from
79 \item Automatic support for multiple autochanger magazines either using
80 barcodes or by reading the tapes.
81 \item Support for multiple drive autochangers.
82 \item Raw device backup/restore. Restore must be to the same device.
83 \item All Volume blocks (approx 64K bytes) contain a data checksum.
84 \item Access control lists for Consoles that permit restricting user access
86 \item Data spooling to disk during backup with subsequent write to tape from
87 the spooled disk files. This prevents tape "shoe shine" during
88 Incremental/Differential backups.
89 \item Support for save/restore of files larger than 2GB.
90 \item Support for 64 bit machines, e.g. amd64.
91 \item Ability to encrypt communications between daemons using stunnel.
92 \item Support ANSI and IBM tape labels.
93 \item Support for Unicode filenames (e.g. Chinese) on Win32 machines on
94 version 1.37.28 and greater.
95 \item Consistent backup of open files on Win32 systems (WinXP, Win2003),
96 but not Win2000, using Volume Shadow Copy (VSS).
99 \subsection*{Advantages of Bacula Over Other Backup Programs}
100 \index[general]{Advantages of Bacula Over Other Backup Programs }
101 \index[general]{Programs!Advantages of Bacula Over Other Backup }
102 \addcontentsline{toc}{subsection}{Advantages of Bacula Over Other Backup
106 \item Since there is a client for each machine, you can backup
107 and restore clients of any type ensuring that all attributes
108 of files are properly saved and restored.
109 \item It is also possible to backup clients without any client
110 software by using NFS or Samba. However, if possible, we
111 recommend running a Client File daemon on each machine to be
113 \item Bacula handles multi-volume backups.
114 \item A full comprehensive SQL standard database of all files backed up. This
115 permits online viewing of files saved on any particular Volume.
116 \item Automatic pruning of the database (removal of old records) thus
117 simplifying database administration.
118 \item Any SQL database engine can be used making Bacula very flexible.
119 \item The modular but integrated design makes Bacula very scalable.
120 \item Since Bacula uses client file servers, any database or
121 other application can be properly shutdown by Bacula using the
122 native tools of the system, backed up, then restarted (all
123 within a Bacula Job).
124 \item Bacula has a built-in Job scheduler.
125 \item The Volume format is documented and there are simple C programs to
127 \item Bacula uses well defined (IANA registered) TCP/IP ports -- no rpcs, no
129 \item Bacula installation and configuration is relatively simple compared to
130 other comparable products.
131 \item According to one user Bacula is as fast as the big major commercial
133 \item According to another user Bacula is four times as fast as another
134 commercial application, probably because that application stores its catalog
135 information in a large number of individual files rather than an SQL database
137 \item Aside from a GUI administrative interface, Bacula has a
138 comprehensive shell administrative interface, which allows the
139 administrator to use tools such as ssh to administrate any part of
140 Bacula from anywhere (even from home).
142 \item Bacula has a Rescue CD for Linux systems with the following features:
144 \item You build it on your own system from scratch with one simple command:
145 make -- well, then make burn.
146 \item It uses your kernel
147 \item It captures your current disk parameters and builds scripts that allow
148 you to automatically repartition a disk and format it to put it back to what
150 \item It has a script that will restart your networking (with the right IP
152 \item It has a script to automatically mount your hard disks.
153 \item It has a full Bacula FD statically linked
154 \item You can easily add additional data/programs, ... to the disk.
159 \subsection*{Current Implementation Restrictions}
160 \index[general]{Current Implementation Restrictions }
161 \index[general]{Restrictions!Current Implementation }
162 \addcontentsline{toc}{subsection}{Current Implementation Restrictions}
165 \item Path and filenames longer than 260 characters on Win32 systems are
166 not supported. They will be backed up, but they cannot be restored. By
167 using the {\bf Portable=yes} directive in your FileSet, files with
168 long names can be restored to Unix and Linux systems.
170 Long filenames for Win32 will be implemented in a later version.
171 \item If you have over 4 billion file entries stored in your database, the
172 database FileId is likely to overflow. This is a monster database, but still
173 possible. At some point, Bacula's FileId fields will be upgraded from 32 bits
174 to 64 bits and this problem will go away. In the mean time, a good workaround
175 is to use multiple databases.
176 \item Files deleted after a Full save will be included in a restoration.
177 \item File System Modules (configurable routines for saving/restoring special
178 files) are not yet implemented.
179 \item Data encryption of the Volume contents.
180 \item Bacula cannot automatically restore files for a single Job
181 from two or more different storage devices or different media types.
182 That is, if you use more than one storage device or media type to
183 backup a single job, the restore process will require some manual
187 \subsection*{Design Limitations or Restrictions}
188 \index[general]{Restrictions!Design Limitations or }
189 \index[general]{Design Limitations or Restrictions }
190 \addcontentsline{toc}{subsection}{Design Limitations or Restrictions}
193 \item Names (resource names, Volume names, and such) defined in Bacula
194 configuration files are limited to a fixed number of characters. Currently
195 the limit is defined as 127 characters. Note, this does not apply to
196 filenames, which may be arbitrarily long.
197 \item On Win32 machines filenames are limited by the non-Unicode Windows
198 API that we use to 260 characters. This is planned to be corrected in
199 a future version by switching to the Unicode API.