capability (system break-in detection).
\item CRAM-MD5 password authentication between each component (daemon).
\item Configurable
- \ilink{TLS (ssl) encryption}{_ChapterStart61} between each component.
+ \ilink{TLS (ssl) communications encryption}{_ChapterStart61} between each component.
+ \item Data (on Volume) encryption on a Client by Client basis.
\item Computation of MD5 or SHA1 signatures of the file data if requested.
\end{itemize}
\item Support for multiple drive autochangers.
\item Raw device backup/restore. Restore must be to the same device.
\item All Volume blocks (approx 64K bytes) contain a data checksum.
- \end{itemize}
+ \item Migration support -- move data from one Pool to another or
+ one Volume to another.
+ \end{itemize}
\item Multi-Operating System Support
\begin{itemize}
version 1.37.28 and greater.
\item Consistent backup of open files on Win32 systems (WinXP, Win2003),
but not Win2000, using Volume Shadow Copy (VSS).
+ \item Support for path/filename lengths of up to 64K on Win32 machines
+ (unlimited on Unix/Linux machines).
\end{itemize}
\item Miscellaneous
\item Automatic pruning of the database (removal of old records) thus
simplifying database administration.
\item Any SQL database engine can be used making Bacula very flexible.
+ Drivers currently exist for MySQL, PostgreSQL, and SQLite.
\item The modular but integrated design makes Bacula very scalable.
\item Since Bacula uses client file servers, any database or
other application can be properly shutdown by Bacula using the
other comparable products.
\item According to one user Bacula is as fast as the big major commercial
applications.
-\item According to another user Bacula is four times as fast as another
+\item According to another user Bacula is four times as fast as another
commercial application, probably because that application stores its catalog
information in a large number of individual files rather than an SQL database
as Bacula does.
\addcontentsline{toc}{subsection}{Current Implementation Restrictions}
\begin{itemize}
-\item Path and filenames longer than 260 characters on Win32 systems are
- not supported. They will be backed up, but they cannot be restored. By
- using the {\bf Portable=yes} directive in your FileSet, files with
- long names can be restored to Unix and Linux systems.
- Long filenames for Win32 will be implemented in version 1.40.
\item If you have over 4 billion file entries stored in your database, the
database FileId is likely to overflow. This is a monster database, but still
- possible. At some point, Bacula's FileId fields will be upgraded from 32 bits
- to 64 bits and this problem will go away. In the mean time, a good workaround
- is to use multiple databases.
-\item Files deleted after a Full save will be included in a restoration.
+ possible. Bacula's FileId fields have been modified so that they can be
+ upgraded from 32 to 64 bits in version 1.39, but this has never been
+ tested.
+\item Files deleted after a Full save will be included in a restoration. This
+ is typical for most similar backup programs (we have a project to
+ correct this).
\item Bacula's Differential and Incremental backups are based on
time stamps. Consequently, if you move files into an existing directory or
move a whole directory into the backup fileset after a Full backup, those
files will probably not be backed up by an Incremental save because they
will have old dates. You must explicitly update the date/time stamp on all
- moved files. Correcting this is a future project.
+ moved files (we have a project to correct this).
\item File System Modules (configurable routines for saving/restoring special
files) are not yet implemented.
-\item Data encryption of the Volume contents. Bacula version 1.40
- will have this feature.
-\item Bacula cannot automatically restore files for a single Job
- from two or more different storage devices or different media types.
- That is, if you use more than one storage device or media type to
- backup a single job, the restore process will require some manual
- intervention.
-\item Bacula does not currently support removable disk Volumes.
- Some users seem to have it working, but you must take care to
- have the correct volume mounted, and restores spanning removable
- disk volumes are not likely to work. It is planned that Bacula
- 1.40 will have this feature.
\end{itemize}
\subsection*{Design Limitations or Restrictions}
\begin{itemize}
\item Names (resource names, Volume names, and such) defined in Bacula
- configuration files are limited to a fixed number of characters. Currently
- the limit is defined as 127 characters. Note, this does not apply to
- filenames, which may be arbitrarily long.
-\item On Win32 machines filenames are limited by the non-Unicode Windows
- API that we use to 260 characters. This is corrected in
- version 1.39 and later by switching to the Unicode API.
+ configuration files are limited to a fixed number of
+ characters. Currently the limit is defined as 127 characters. Note,
+ this does not apply to filenames, which may be arbitrarily long.
\end{itemize}
projects / bacula / docs / blobdiff