This is an old revision of the document!
In other words, what is and what is not currently implemented and functional.
o Network backup/restore with centralized Director.
o Internal scheduler for automatic Job execution. o Scheduling of multiple Jobs at the same time. o You may run one Job at a time or multiple simultaneous Jobs (sometimes called multiplexing). o Job sequencing using priorities. o Console interface to the Director allowing complete control. A shell, GNOME GUI and wxWidgets GUI versions of the Console program are available. Note, the GNOME GUI program currently offers very few additional features over the shell program. With version 2.2.0, a much more complete GUI interface has been written, which is called the Bacula Admistration Tool, or bat.
o Verification of files previously cataloged, permitting a Tripwire like capability (system break-in detection).
o CRAM-MD5 password authentication between each component (daemon). o Configurable TLS (SSL) communications encryption between each component. o Configurable Data (on Volume) encryption on a Client by Client basis. o Computation of MD5 or SHA1 signatures of the file data if requested.
o Restore of one or more files selected interactively either for the current backup or a backup prior to a specified time and date.
o Restore of a complete system starting from bare metal. This is mostly automated for Linux systems and partially automated for Solaris. See Disaster Recovery Using Bacula. This is also reported to work on Win2K/XP systems. o Listing and Restoration of files using stand-alone bls and bextract tool programs. Among other things, this permits extraction of files when Bacula and/or the catalog are not available. Note, the recommended way to restore files is using the restore command in the Console. These programs are designed for use as a last resort. o Ability to restore the catalog database rapidly by using bootstrap files (previously saved). o Ability to recreate the catalog database by scanning backup Volumes using the bscan program.
o Catalog database facility for remembering Volumes, Pools, Jobs, and Files backed up.
o Support for MySQL, PostgreSQL, and SQLite Catalog databases. o User extensible queries to the MySQL, PostgreSQL and SQLite databases.
o Labeled Volumes, preventing accidental overwriting (at least by Bacula).
o Any number of Jobs and Clients can be backed up to a single Volume. That is, you can backup and restore Linux, Unix, Sun, and Windows machines to the same Volume. o Multi-volume saves. When a Volume is full, Bacula automatically requests the next Volume and continues the backup. o Pool and Volume library management providing Volume flexibility (e.g. monthly, weekly, daily Volume sets, Volume sets segregated by Client, ...). o Machine independent Volume data format. Linux, Solaris, and Windows clients can all be backed up to the same Volume if desired. o The Volume data format is upwards compatible so that old Volumes can always be read. o A flexible message handler including routing of messages from any daemon back to the Director and automatic email reporting. o Data spooling to disk during backup with subsequent write to tape from the spooled disk files. This prevents tape "shoe shine" during Incremental/Differential backups.
o Autochanger support using a simple shell interface that can interface to virtually any autoloader program. A script for mtx is provided.
o Support for autochanger barcodes -- automatic tape labeling from barcodes. o Automatic support for multiple autochanger magazines either using barcodes or by reading the tapes. o Support for multiple drive autochangers. o Raw device backup/restore. Restore must be to the same device. o All Volume blocks (approximately 64K bytes) contain a data checksum. o Migration support -- move data from one Pool to another or one Volume to another. o Supports writing to DVD.
o Programmed to handle arbitrarily long filenames and messages.
o GZIP compression on a file by file basis done by the Client program if requested before network transit. o Saves and restores POSIX ACLs on most OSes if enabled. o Access control lists for Consoles that permit restricting user access to only their data. o Support for save/restore of files larger than 2GB. o Support for 64 bit machines, e.g. amd64, Sparc. o Support ANSI and IBM tape labels. o Support for Unicode filenames (e.g. Chinese) on Win32 machines on version 1.37.28 and greater. o Consistent backup of open files on Win32 systems (WinXP, Win2003, and Vista) but not Win2000, using Volume Shadow Copy (VSS). o Support for path/filename lengths of up to 64K on Win32 machines (unlimited on Unix/Linux machines).
o Multi-threaded implementation.
o A comprehensive and extensible configuration file for each daemon.
Advantages Over Other Backup Programs
o You build it on your own system from scratch with one simple command: make – well, then make burn.
o It uses your kernel o It captures your current disk parameters and builds scripts that allow you to automatically repartition a disk and format it to put it back to what you had before. o It has a script that will restart your networking (with the right IP address) o It has a script to automatically mount your hard disks. o It has a full Bacula FD statically linked o You can easily add additional data/programs, ... to the disk.
Current Implementation Restrictions
Design Limitations or Restrictions