failed. This is done only if there is sufficient valid backup
data that was written to the Volume. The advantage of an Incomplete
job is that it can be restarted by the new bconsole {\bf restart}
-command.
+command from the point where it left off rather than from the
+beginning of the jobs as is the case with a cancel.
\section{The Stop Command}
-Bacula has been enhanced to provid a {\bf stop} command,
+Bacula has been enhanced to provide a {\bf stop} command,
very similar to the {\bf cancel} command with the main difference
-that the Job that is stopped is marked as Incomplete. This permits
-the Job to be started later by the {\bf restart} command (see below).
+that the Job that is stopped is marked as Incomplete so that
+it can be restarted later by the {\bf restart} command where
+it left off (see below). The {\bf stop} command with no
+arguments, will like the cancel command, prompt you with the
+list of running jobs allowing you to select one, which might
+look like the following:
+
+\begin{verbatim}
+*stop
+Select Job:
+ 1: JobId=3 Job=Incremental.2012-03-26_12.04.26_07
+ 2: JobId=4 Job=Incremental.2012-03-26_12.04.30_08
+ 3: JobId=5 Job=Incremental.2012-03-26_12.04.36_09
+Choose Job to stop (1-3): 2
+2001 Job "Incremental.2012-03-26_12.04.30_08" marked to be stopped.
+3000 JobId=4 Job="Incremental.2012-03-26_12.04.30_08" marked to be stopped.
+\end{verbatim}
\section{The Restart Command}
The new {\bf Restart command} allows console users to restart
-a cancelled, failed, or incomplete Job. For cancelled and failed
+a canceled, failed, or incomplete Job. For canceled and failed
Jobs, the Job will restart from the beginning. For incomplete
Jobs the Job will restart at the point that it was stopped either
by a stop command or by some recoverable failure.
-\section{Support for Exchange Differential and Incremental Backups}
+\smallskip
+If you enter the {\bf restart} command in bconsole, you will get the
+following prompts:
+
+\begin{verbatim}
+*restart
+You have the following choices:
+ 1: Incomplete
+ 2: Canceled
+ 3: Failed
+ 4: All
+Select termination code: (1-4):
+\end{verbatim}
+
+If you select the {\bf All} option, you may see something like:
+
+\begin{verbatim}
+Select termination code: (1-4): 4
++-------+-------------+---------------------+------+-------+----------+-----------+-----------+
+| jobid | name | starttime | type | level | jobfiles |
+jobbytes | jobstatus |
++-------+-------------+---------------------+------+-------+----------+-----------+-----------+
+| 1 | Incremental | 2012-03-26 12:15:21 | B | F | 0 |
+ 0 | A |
+| 2 | Incremental | 2012-03-26 12:18:14 | B | F | 350 |
+4,013,397 | I |
+| 3 | Incremental | 2012-03-26 12:18:30 | B | F | 0 |
+ 0 | A |
+| 4 | Incremental | 2012-03-26 12:18:38 | B | F | 331 |
+3,548,058 | I |
++-------+-------------+---------------------+------+-------+----------+-----------+-----------+
+Enter the JobId list to select:
+\end{verbatim}
+
+Then you may enter one or more JobIds to be restarted, which may
+take the form of a list of JobIds separated by commas, and/or JobId
+ranges such as {\bf 1-4}, which indicates you want to restart JobIds
+1 through 4, inclusive.
+
+\section{Support for Exchange Incremental Backups}
The Bacula Enterprise version 6.0 VSS plugin now supports
-Full, Differential, and Incremental backups for Exchange.
+Full and Incremental backups for Exchange. We strongly
+recommend that you do not attempt to run Differential jobs with
+Exchange as it is likely to produce a situation where restores
+will no longer select the correct jobs, and thus the
+Windows Exchange VSS writer will fail when applying log files.
There is a Bacula Systems Enterprise white paper that provides
the details of backup and restore of Exchange 2010 with the
Bacula VSS plugin.
+\smallskip
+Restores can be done while Exchange is running, but you
+must first unmount (dismount in Microsoft terms) any database
+you wish to restore and explicitly mark them to permit a
+restore operation (see the white paper for details).
+
+\smallskip
This project was funded by Bacula Systems and is available with the Bacula
Enterprise Edition.
With the addition of block level backup support to the
Bacula Enterprise VSS MSSQL component, you can now do
Differential backups in addition to Full backups.
-Incremental backups for MSSQL are not support by
-Microsoft.
+Differential backups use Microsoft's partial block backup
+(a block differencing or deduplication that we call Delta).
+This partial block backup permits backing up only those
+blocks that have changed. Database restores can be made while
+the MSSQL server is running, but any databases selected for
+restore will be automatically taken offline by the MSSQL
+server during the restore process.
+Incremental backups for MSSQL are not support by
+Microsoft. We strongly recommend that you not perform Incremental
+backups with MSSQL as they will probably produce a situation
+where restore will no longer work correctly.
+
+\smallskip
+ We are currently working on producing a white paper that will give more
+details of backup and restore with MSSQL. One point to note is that during
+a restore, you will normally not want to restore the {\bf master} database.
+You must exclude it from the backup selections that you have made or the
+restore will fail.
+
+\smallskip
+It is possible to restore the {\bf master} database, but you must
+first shutdown the MSSQL server, then you must perform special
+recovery commands. Please see Microsoft documentation on how
+to restore the master database.
+
+\smallskip
This project was funded by Bacula Systems and is available with the Bacula
Enterprise Edition.
The new \texttt{delta} Plugin is able to compute and apply signature-based file
differences. It can be used to backup only changes in a big binary file like
-Outlook PST, VirtualBox/VmWare images or database files.
+Outlook PST, VirtualBox/VMware images or database files.
It supports both Incremental and Differential backups and stores signatures
database in the File Daemon working directory. This plugin is available on all
compression ratio than GZIP. It is a good option when you backup to disk. For
tape, the built-in compression may be a better option.
-LZO is a good altenative for GZIP1 when you don't want to slow down your
+LZO is a good alternative for GZIP1 when you don't want to slow down your
backup. On a modern CPU it should be able to run almost as fast as:
\begin{itemize}
\medskip
-This project was submited by Dunlap Blake; testing and documentation was funded
+This project was submitted by Dunlap Blake; testing and documentation was funded
by Bacula Systems.
\section{Changes in the Pruning Algorithm}
compression ratio than GZIP. It is a good option when you backup to disk. For
tape, the hardware compression is almost always a better option.
-LZO is a good altenative for GZIP1 when you don't want to slow down your
+LZO is a good alternative for GZIP1 when you don't want to slow down your
backup. With a modern CPU it should be able to run almost as fast as:
\begin{itemize}
\medskip
-This project was submited by Dunlap Blake; testing and documentation was funded
+This project was submitted by Dunlap Blake; testing and documentation was funded
by Bacula Systems.
\section{Changes in Bvfs (Bacula Virtual FileSystem)}
can contribute new faster SQL queries we will be happy, else don't complain
about speed.
\item The cache creation is dependent of the number of directories. As Bvfs
- shares information accross jobs, the first creation can be slow
+ shares information across jobs, the first creation can be slow
\item All fields are separated by a tab
-\item Due to potential encoding problem, it's advised to allways use pathid in
+\item Due to potential encoding problem, it's advised to always use pathid in
queries.
\end{itemize}
To include a directory (with \texttt{dirid}), Bvfs needs to run a query to
select all files. This query could be time consuming.
-\texttt{hardlink} list is always composed of a serie of two numbers (jobid,
+\texttt{hardlink} list is always composed of a series of two numbers (jobid,
fileindex). This information can be found in the LinkFI field of the LStat
packet.
\end{description}
\item [AddRegex] adds a regex expression to the current Options block.
- The fillowing options are permitted:
+ The following options are permitted:
\begin{description}
\item [ ] (a blank) regex applies to whole path and filename.
\item [F] regex applies only to the filename (directory or path stripped).
\end{description}
\item [AddWild] adds a wildcard expression to the current Options block.
- The fillowing options are permitted:
+ The following options are permitted:
\begin{description}
\item [ ] (a blank) regex applies to whole path and filename.
\item [F] regex applies only to the filename (directory or path stripped).
\begin{description}
\item [bEventCancelCommand] is called whenever the currently
- running Job is cancelled */
+ running Job is canceled */
\item [bEventVssBackupAddComponents]
\item Fix for acl storage on OSX
\item Cleanup of configure checks for ACL detection, now configure only
tests for a certain interface type based on the operating system
- this should give less false possitives on detection. Also when acls
+ this should give less false positives on detection. Also when ACLs
are detected no other acl checks are performed anymore.
\end{itemize}
debug.
\item Cleanup of configure checks for XATTR detection, now configure only
tests for a certain interface type based on the operating system
- this should give less false possitives on detection. Also when xattrs
+ this should give less false positives on detection. Also when xattrs
are detected no other xattr checks are performed anymore.
\end{itemize}
All current database backend drivers for catalog information are rewritten
to use a set of multi inherited C++ classes which abstract the specific
database specific internals and make sure we have a more stable generic
-interface with the rest of sql code. From now on there is a strict
-boundery between the SQL code and the low-level database functions. This
+interface with the rest of SQL code. From now on there is a strict
+boundary between the SQL code and the low-level database functions. This
new interface should also make it easier to add a new backend for a
currently unsupported database. As part of the rewrite the SQLite 2 code
was removed (e.g. only SQLite 3 is now supported). An extra bonus of the
\chapter{Release Version 5.0.3}
There are no new features in version 5.0.2. This version simply fixes a
-number of bugs found in version 5.0.1 during the onging development
+number of bugs found in version 5.0.1 during the ongoing development
process.
\chapter{Release Version 5.0.2}
There are no new features in version 5.0.2. This version simply fixes a
-number of bugs found in version 5.0.1 during the onging development
+number of bugs found in version 5.0.1 during the ongoing development
process.
%%
This chapter presents the new features that are in the released Bacula version
5.0.1. This version mainly fixes a number of bugs found in version 5.0.0 during
-the onging development process.
+the ongoing development process.
\section{Truncate Volume after Purge}
\label{sec:actiononpurge}
\section{Allow Higher Duplicates}
This directive did not work correctly and has been depreciated
(disabled) in version 5.0.1. Please remove it from your bacula-dir.conf
-file as it will be removed in a future rlease.
+file as it will be removed in a future release.
\section{Cancel Lower Level Duplicates}
This directive was added in Bacula version 5.0.1. It compares the
It seems obvious to us, but apparently not to some users, that given the
definition above that the Pool File and Job Retention periods is a global
-override for the normal Client based prunning, which means that when the
-Job is prunned, the prunning will apply globally to that particular Job.
+override for the normal Client based pruning, which means that when the
+Job is pruned, the pruning will apply globally to that particular Job.
Currently, there is a bug in the implementation that causes any Pool
retention periods specified to apply to {\bf all} Pools for that
When using compression, the random test will give your the minimum throughput
of your drive . The test using constant string will give you the maximum speed
-of your hardware chain. (cpu, memory, scsi card, cable, drive, tape).
+of your hardware chain. (CPU, memory, SCSI card, cable, drive, tape).
You can change the block size in the Storage Daemon configuration file.
We have ported {\bf bat} to Windows and it is now installed
by default when the installer is run. It works quite well
on Win32, but has not had a lot of testing there, so your
-feedback would be welcome. Unfortunately, eventhough it is
+feedback would be welcome. Unfortunately, even though it is
installed by default, it does not yet work on 64 bit Windows
operating systems.
\item The \texttt{Device Poll Interval} is now 5 minutes. (previously did not
poll by default).
\item Virtually all the features of {\bf mtx-changer} have
- now been parameterized, which allows you to configure
+ now been parametrized, which allows you to configure
mtx-changer without changing it. There is a new configuration file {\bf mtx-changer.conf}
that contains variables that you can set to configure mtx-changer.
This configuration file will not be overwritten during upgrades.
We encourage you to submit any changes
- that are made to mtx-changer and to parameterize it all in
+ that are made to mtx-changer and to parametrize it all in
mtx-changer.conf so that all configuration will be done by
changing only mtx-changer.conf.
\item The new \texttt{mtx-changer} script has two new options, \texttt{listall}
\chapter{Released Version 3.0.3 and 3.0.3a}
There are no new features in version 3.0.3. This version simply fixes a
-number of bugs found in version 3.0.2 during the onging development
+number of bugs found in version 3.0.2 during the ongoing development
process.
\chapter{New Features in Released Version 3.0.2}
\index[general]{Accurate Backup}
As with most other backup programs, by default Bacula decides what files to
-backup for Incremental and Differental backup by comparing the change
+backup for Incremental and Differential backup by comparing the change
(st\_ctime) and modification (st\_mtime) times of the file to the time the last
backup completed. If one of those two times is later than the last backup
time, then the file will be backed up. This does not, however, permit tracking
allow certain platform specific ACL streams to be decoded and restored on the
same platform that they were created on. The old code allowed to restore ACL
cross platform but the comments already mention that not being to wise. For
-backward compatability the new code will accept the two old ACL streams and
+backward compatibility the new code will accept the two old ACL streams and
handle those with the platform specific handler. But for all new backups it
will save the ACLs using the new streams.
\end{itemize}
In future versions we might support conversion functions from one type of acl
-into an other for types that are either the same or easily convertable. For now
-the streams are seperate and restoring them on a platform that doesn't
+into an other for types that are either the same or easily convertible. For now
+the streams are separate and restoring them on a platform that doesn't
recognize them will give you a warning.
\section{Extended Attributes}
Something that was on the project list for some time is now implemented for
platforms that support a similar kind of interface. Its the support for backup
and restore of so called extended attributes. As extended attributes are so
-platform specific these attributes are saved in seperate streams for each
+platform specific these attributes are saved in separate streams for each
platform. Restores of the extended attributes can only be performed on the
same platform the backup was done. There is support for all types of extended
attributes, but restoring from one type of filesystem onto an other type of
-filesystem on the same platform may lead to supprises. As extended attributes
+filesystem on the same platform may lead to surprises. As extended attributes
can contain any type of data they are stored as a series of so called
value-pairs. This data must be seen as mostly binary and is stored as such.
As security labels from selinux are also extended attributes this option also
\item {\bf NetBSD}
\end{itemize}
-On linux acls are also extended attributes, as such when you enable ACLs on a
+On Linux acls are also extended attributes, as such when you enable ACLs on a
Linux platform it will NOT save the same data twice e.g. it will save the ACLs
-and not the same exteneded attribute.
+and not the same extended attribute.
To enable the backup of extended attributes please add the following to your
fileset definition.
If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs
are present and none of the three directives given below permit
- cancelling a job, then the current job (the second one started)
- will be cancelled.
+ Canceling a job, then the current job (the second one started)
+ will be canceled.
\subsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}}
\index[general]{Allow Higher Duplicates}
\subsection{Plugin Options}
\index[general]{Plugin Options}
The {\bf Plugin Options} directive takes a quoted string
-arguement (after the equal sign) and may be specified in the
+argument (after the equal sign) and may be specified in the
Job resource. The options specified will be passed to all plugins
when they are run. This each plugin must know what it is looking
for. The value defined in the Job resource can be modified
done, and may also truncate log files incorrectly. It is important,
therefore, that the Exchange database files be excluded from the backup,
although the folders the files are in should be included, or they will
-have to be recreated manually if a baremetal restore is done.
+have to be recreated manually if a bare metal restore is done.
\begin{verbatim}
FileSet {
\subsection{Restoring on Microsoft Server 2007}
Apparently the {\bf Exmerge} program no longer exists in Microsoft Server
-2007, and henc you use a new proceedure for recovering a single mail box.
-This procedure is ducomented by Microsoft at:
+2007, and hence you use a new procedure for recovering a single mail box.
+This procedure is documented by Microsoft at:
\elink{http://technet.microsoft.com/en-us/library/aa997694.aspx}{http://technet.microsoft.com/en-us/library/aa997694.aspx},
and involves using the {\bf Restore-Mailbox} and {\bf
-Get-MailboxStatistics} shell commands.
+Get-Mailbox Statistics} shell commands.
\subsection{Caveats}
This plugin is still being developed, so you should consider it
projects / bacula / docs / commitdiff