In other words, what is and what is not currently implemented and functional.
\subsection*{What is Implemented}
-\index[general]{Implemented!What is }
-\index[general]{What is Implemented }
+\index[general]{Implemented!What}
+\index[general]{What is Implemented}
\addcontentsline{toc}{subsection}{What is Implemented}
\begin{itemize}
\item GZIP compression on a file by file basis done by the Client program if
requested before network transit.
\item Computation of MD5 or SHA1 signatures of the file data if requested.
-\item Saves and restores POSIX ACLs if enabled.
+\item Saves and restores POSIX ACLs on most OSes if enabled.
\item Autochanger support using a simple shell interface that can interface
to virtually any autoloader program. A script for {\bf mtx} is provided.
\item Support for autochanger barcodes -- automatic tape labeling from
barcodes.
\item Automatic support for multiple autochanger magazines either using
barcodes or by reading the tapes.
+\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.
\item Access control lists for Consoles that permit restricting user access
to only their data.
\item Data spooling to disk during backup with subsequent write to tape from
- the spooled disk files. This prevents tape ``shoe shine'' during
+ the spooled disk files. This prevents tape "shoe shine" during
Incremental/Differential backups.
\item Support for save/restore of files larger than 2GB.
\item Support for 64 bit machines, e.g. amd64.
\item Ability to encrypt communications between daemons using stunnel.
\item Support ANSI and IBM tape labels.
-\item Support for Unicode filenames (e.g. Chinese) on Win32 machines.
-
+\item Support for Unicode filenames (e.g. Chinese) on Win32 machines on
+ 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).
\end{itemize}
\subsection*{Advantages of Bacula Over Other Backup Programs}
\addcontentsline{toc}{subsection}{Current Implementation Restrictions}
\begin{itemize}
-\item Typical of Microsoft, not all files can always be saved on WinNT, Win2K
- and WinXP when they are in use by another program. Anyone knowing the magic
- incantations, please step forward. The files that are skipped seem to be in
- exclusive use by some other process, and don't appear to be too important.
+\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 a later version.
\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.
-\item Event handlers are not yet implemented (e.g. when Job terminates do
- this, ...)
\item File System Modules (configurable routines for saving/restoring special
- files).
+ files) are not yet implemented.
\item Data encryption of the Volume contents.
\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 There is no concept of a Pool of backup devices (i.e. if device
- /dev/nst0 is busy, use /dev/nst1, ...).
- \end{itemize}
+\end{itemize}
\subsection*{Design Limitations or Restrictions}
\index[general]{Restrictions!Design Limitations or }
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 planned to be corrected in
+ a future version by switching to the Unicode API.
\end{itemize}
projects / bacula / docs / blobdiff