<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 2008 (1.71)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>New Features in 3.0.0</TITLE>
<META NAME="description" CONTENT="New Features in 3.0.0">
<META NAME="keywords" CONTENT="main">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="LaTeX2HTML v2008">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="main.css">
<LINK REL="next" HREF="Current_State_Bacula.html">
<LINK REL="previous" HREF="New_Features_in_Released.html">
<LINK REL="up" HREF="Bacula_Main_Reference.html">
<LINK REL="next" HREF="Current_State_Bacula.html">
</HEAD>
<BODY >
<!--Navigation Panel-->
<A NAME="tex2html1156"
HREF="Current_State_Bacula.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1150"
HREF="Bacula_Main_Reference.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1144"
HREF="New_Features_in_Released.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1152"
HREF="Contents.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1154"
HREF="Thanks.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1157"
HREF="Current_State_Bacula.html">The Current State of</A>
<B> Up:</B> <A NAME="tex2html1151"
HREF="Bacula_Main_Reference.html">Bacula Main Reference</A>
<B> Previous:</B> <A NAME="tex2html1145"
HREF="New_Features_in_Released.html">New Features in Released</A>
<B> <A NAME="tex2html1153"
HREF="Contents.html">Contents</A></B>
<B> <A NAME="tex2html1155"
HREF="Thanks.html">Index</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A NAME="tex2html1158"
HREF="New_Features_in_3_0_0.html#SECTION00810000000000000000">Accurate Backup</A>
<UL>
<LI><A NAME="tex2html1159"
HREF="New_Features_in_3_0_0.html#SECTION00811000000000000000">Accurate = yesno</A>
</UL>
<BR>
<LI><A NAME="tex2html1160"
HREF="New_Features_in_3_0_0.html#SECTION00820000000000000000">Copy Jobs</A>
<LI><A NAME="tex2html1161"
HREF="New_Features_in_3_0_0.html#SECTION00830000000000000000">ACL Updates</A>
<LI><A NAME="tex2html1162"
HREF="New_Features_in_3_0_0.html#SECTION00840000000000000000">Extended Attributes</A>
<LI><A NAME="tex2html1163"
HREF="New_Features_in_3_0_0.html#SECTION00850000000000000000">Shared objects</A>
<LI><A NAME="tex2html1164"
HREF="New_Features_in_3_0_0.html#SECTION00860000000000000000">Building Static versions of Bacula</A>
<LI><A NAME="tex2html1165"
HREF="New_Features_in_3_0_0.html#SECTION00870000000000000000">Virtual Backup (Vbackup)</A>
<LI><A NAME="tex2html1166"
HREF="New_Features_in_3_0_0.html#SECTION00880000000000000000">Catalog Format</A>
<LI><A NAME="tex2html1167"
HREF="New_Features_in_3_0_0.html#SECTION00890000000000000000">64 bit Windows Client</A>
<LI><A NAME="tex2html1168"
HREF="New_Features_in_3_0_0.html#SECTION008100000000000000000">Duplicate Job Control</A>
<UL>
<LI><A NAME="tex2html1169"
HREF="New_Features_in_3_0_0.html#SECTION008101000000000000000">Allow Duplicate Jobs = yesno</A>
<LI><A NAME="tex2html1170"
HREF="New_Features_in_3_0_0.html#SECTION008102000000000000000">Allow Higher Duplicates = yesno</A>
<LI><A NAME="tex2html1171"
HREF="New_Features_in_3_0_0.html#SECTION008103000000000000000">Cancel Running Duplicates = yesno</A>
<LI><A NAME="tex2html1172"
HREF="New_Features_in_3_0_0.html#SECTION008104000000000000000">Cancel Queued Duplicates = yesno</A>
</UL>
<BR>
<LI><A NAME="tex2html1173"
HREF="New_Features_in_3_0_0.html#SECTION008110000000000000000">TLS Authentication</A>
<UL>
<LI><A NAME="tex2html1174"
HREF="New_Features_in_3_0_0.html#SECTION008111000000000000000">TLS Authenticate = yes</A>
</UL>
<BR>
<LI><A NAME="tex2html1175"
HREF="New_Features_in_3_0_0.html#SECTION008120000000000000000">bextract non-portable Win32 data</A>
<LI><A NAME="tex2html1176"
HREF="New_Features_in_3_0_0.html#SECTION008130000000000000000">State File updated at Job Termination</A>
<LI><A NAME="tex2html1177"
HREF="New_Features_in_3_0_0.html#SECTION008140000000000000000">MaxFullInterval = time-interval</A>
<LI><A NAME="tex2html1178"
HREF="New_Features_in_3_0_0.html#SECTION008150000000000000000">MaxDiffInterval = time-interval</A>
<LI><A NAME="tex2html1179"
HREF="New_Features_in_3_0_0.html#SECTION008160000000000000000">Honor No Dump Flag = yesno</A>
<LI><A NAME="tex2html1180"
HREF="New_Features_in_3_0_0.html#SECTION008170000000000000000">Exclude Dir Containing = filename-string</A>
<LI><A NAME="tex2html1181"
HREF="New_Features_in_3_0_0.html#SECTION008180000000000000000">Bacula Plugins</A>
<UL>
<LI><A NAME="tex2html1182"
HREF="New_Features_in_3_0_0.html#SECTION008181000000000000000">Plugin Directory</A>
<LI><A NAME="tex2html1183"
HREF="New_Features_in_3_0_0.html#SECTION008182000000000000000">Plugin Options</A>
<LI><A NAME="tex2html1184"
HREF="New_Features_in_3_0_0.html#SECTION008183000000000000000">Plugin Options ACL</A>
<LI><A NAME="tex2html1185"
HREF="New_Features_in_3_0_0.html#SECTION008184000000000000000">Plugin = plugin-command-string</A>
</UL>
<BR>
<LI><A NAME="tex2html1186"
HREF="New_Features_in_3_0_0.html#SECTION008190000000000000000">The bpipe Plugin</A>
<LI><A NAME="tex2html1187"
HREF="New_Features_in_3_0_0.html#SECTION008200000000000000000">Microsoft Exchange Server 2003/2007 Plugin</A>
<UL>
<LI><A NAME="tex2html1188"
HREF="New_Features_in_3_0_0.html#SECTION008201000000000000000">Background</A>
<LI><A NAME="tex2html1189"
HREF="New_Features_in_3_0_0.html#SECTION008202000000000000000">Concepts</A>
<LI><A NAME="tex2html1190"
HREF="New_Features_in_3_0_0.html#SECTION008203000000000000000">Installing</A>
<LI><A NAME="tex2html1191"
HREF="New_Features_in_3_0_0.html#SECTION008204000000000000000">Backing Up</A>
<LI><A NAME="tex2html1192"
HREF="New_Features_in_3_0_0.html#SECTION008205000000000000000">Restoring</A>
<LI><A NAME="tex2html1193"
HREF="New_Features_in_3_0_0.html#SECTION008206000000000000000">Restoring to the Recovery Storage Group</A>
<LI><A NAME="tex2html1194"
HREF="New_Features_in_3_0_0.html#SECTION008207000000000000000">Restoring on Microsoft Server 2007</A>
<LI><A NAME="tex2html1195"
HREF="New_Features_in_3_0_0.html#SECTION008208000000000000000">Caveats</A>
</UL>
<BR>
<LI><A NAME="tex2html1196"
HREF="New_Features_in_3_0_0.html#SECTION008210000000000000000">libdbi Framework</A>
<LI><A NAME="tex2html1197"
HREF="New_Features_in_3_0_0.html#SECTION008220000000000000000">Console Command Additions and Enhancements</A>
<UL>
<LI><A NAME="tex2html1198"
HREF="New_Features_in_3_0_0.html#SECTION008221000000000000000">Display Autochanger Content</A>
<LI><A NAME="tex2html1199"
HREF="New_Features_in_3_0_0.html#SECTION008222000000000000000">list joblog job=xxx or jobid=nnn</A>
<LI><A NAME="tex2html1200"
HREF="New_Features_in_3_0_0.html#SECTION008223000000000000000">Use separator for multiple commands</A>
<LI><A NAME="tex2html1201"
HREF="New_Features_in_3_0_0.html#SECTION008224000000000000000">Deleting Volumes</A>
</UL>
<BR>
<LI><A NAME="tex2html1202"
HREF="New_Features_in_3_0_0.html#SECTION008230000000000000000">Bare Metal Recovery</A>
<LI><A NAME="tex2html1203"
HREF="New_Features_in_3_0_0.html#SECTION008240000000000000000">Miscellaneous</A>
<UL>
<LI><A NAME="tex2html1204"
HREF="New_Features_in_3_0_0.html#SECTION008241000000000000000">Allow Mixed Priority = yesno</A>
<LI><A NAME="tex2html1205"
HREF="New_Features_in_3_0_0.html#SECTION008242000000000000000">Bootstrap File Directive - FileRegex</A>
<LI><A NAME="tex2html1206"
HREF="New_Features_in_3_0_0.html#SECTION008243000000000000000">Bootstrap File Optimization Changes</A>
<LI><A NAME="tex2html1207"
HREF="New_Features_in_3_0_0.html#SECTION008244000000000000000">Solaris ZFS/NFSv4 ACLs</A>
<LI><A NAME="tex2html1208"
HREF="New_Features_in_3_0_0.html#SECTION008245000000000000000">Virtual Tape Emulation</A>
<LI><A NAME="tex2html1209"
HREF="New_Features_in_3_0_0.html#SECTION008246000000000000000">Bat Enhancements</A>
<LI><A NAME="tex2html1210"
HREF="New_Features_in_3_0_0.html#SECTION008247000000000000000">RunScript Enhancements</A>
<LI><A NAME="tex2html1211"
HREF="New_Features_in_3_0_0.html#SECTION008248000000000000000">Status Enhancements</A>
<LI><A NAME="tex2html1212"
HREF="New_Features_in_3_0_0.html#SECTION008249000000000000000">Connect Timeout</A>
<LI><A NAME="tex2html1213"
HREF="New_Features_in_3_0_0.html#SECTION0082410000000000000000">ftruncate for NFS Volumes</A>
<LI><A NAME="tex2html1214"
HREF="New_Features_in_3_0_0.html#SECTION0082411000000000000000">Support for Ubuntu</A>
<LI><A NAME="tex2html1215"
HREF="New_Features_in_3_0_0.html#SECTION0082412000000000000000">Recycle Pool = pool-name</A>
<LI><A NAME="tex2html1216"
HREF="New_Features_in_3_0_0.html#SECTION0082413000000000000000">FD Version</A>
<LI><A NAME="tex2html1217"
HREF="New_Features_in_3_0_0.html#SECTION0082414000000000000000">Max Run Sched Time = time-period-in-seconds</A>
<LI><A NAME="tex2html1218"
HREF="New_Features_in_3_0_0.html#SECTION0082415000000000000000">Max Wait Time = time-period-in-seconds</A>
<LI><A NAME="tex2html1219"
HREF="New_Features_in_3_0_0.html#SECTION0082416000000000000000">Incremental|Differential Max Wait Time = time-period-in-seconds</A>
<LI><A NAME="tex2html1220"
HREF="New_Features_in_3_0_0.html#SECTION0082417000000000000000">Max Run Time directives</A>
<LI><A NAME="tex2html1221"
HREF="New_Features_in_3_0_0.html#SECTION0082418000000000000000">Statistics Enhancements</A>
<LI><A NAME="tex2html1222"
HREF="New_Features_in_3_0_0.html#SECTION0082419000000000000000">ScratchPool = pool-resource-name</A>
<LI><A NAME="tex2html1223"
HREF="New_Features_in_3_0_0.html#SECTION0082420000000000000000">Enhanced Attribute Despooling</A>
<LI><A NAME="tex2html1224"
HREF="New_Features_in_3_0_0.html#SECTION0082421000000000000000">SpoolSize = size-specification-in-bytes</A>
<LI><A NAME="tex2html1225"
HREF="New_Features_in_3_0_0.html#SECTION0082422000000000000000">MaximumConsoleConnections = number</A>
<LI><A NAME="tex2html1226"
HREF="New_Features_in_3_0_0.html#SECTION0082423000000000000000">VerId = string</A>
<LI><A NAME="tex2html1227"
HREF="New_Features_in_3_0_0.html#SECTION0082424000000000000000">dbcheck enhancements</A>
<LI><A NAME="tex2html1228"
HREF="New_Features_in_3_0_0.html#SECTION0082425000000000000000">-docdir configure option</A>
<LI><A NAME="tex2html1229"
HREF="New_Features_in_3_0_0.html#SECTION0082426000000000000000">-htmldir configure option</A>
<LI><A NAME="tex2html1230"
HREF="New_Features_in_3_0_0.html#SECTION0082427000000000000000">-with-plugindir configure option</A>
</UL></UL>
<!--End of Table of Child-Links-->
<HR>
<H1><A NAME="SECTION00800000000000000000"></A>
<A NAME="NewFeaturesChapter"></A>
<BR>
New Features in 3.0.0
</H1>
<A NAME="624"></A>
<P>
This chapter presents the new features added to the development 2.5.x
versions to be released as Bacula version 3.0.0 sometime in April 2009.
<P>
<H1><A NAME="SECTION00810000000000000000">
Accurate Backup</A>
</H1>
<A NAME="626"></A>
<P>
As with most other backup programs, by default Bacula decides what files to
backup for Incremental and Differental 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
what files have been deleted and will miss any file with an old time that may
have been restored to or moved onto the client filesystem.
<P>
<H2><A NAME="SECTION00811000000000000000">
Accurate = yesno</A>
</H2>
If the <B>Accurate = yesno</B> directive is enabled (default no) in
the Job resource, the job will be run as an Accurate Job. For a <B>Full</B>
backup, there is no difference, but for <B>Differential</B> and <B> Incremental</B> backups, the Director will send a list of all previous files
backed up, and the File daemon will use that list to determine if any new files
have been added or or moved and if any files have been deleted. This allows
Bacula to make an accurate backup of your system to that point in time so that
if you do a restore, it will restore your system exactly.
<P>
One note of caution
about using Accurate backup is that it requires more resources (CPU and memory)
on both the Director and the Client machines to create the list of previous
files backed up, to send that list to the File daemon, for the File daemon to
keep the list (possibly very big) in memory, and for the File daemon to do
comparisons between every file in the FileSet and the list. In particular,
if your client has lots of files (more than a few million), you will need
lots of memory on the client machine.
<P>
Accurate must not be enabled when backing up with a plugin that is not
specially designed to work with Accurate. If you enable it, your restores
will probably not work correctly.
<P>
This project was funded by Bacula Systems.
<P>
<H1><A NAME="SECTION00820000000000000000">
Copy Jobs</A>
</H1>
<A NAME="637"></A>
<P>
A new <B>Copy</B> job type 'C' has been implemented. It is similar to the
existing Migration feature with the exception that the Job that is copied is
left unchanged. This essentially creates two identical copies of the same
backup. However, the copy is treated as a copy rather than a backup job, and
hence is not directly available for restore. The <B>restore</B> command lists
copy jobs and allows selection of copies by using <TT>jobid=</TT>
option. If the keyword <B>copies</B> is present on the command line, Bacula will
display the list of all copies for selected jobs.
<P>
<PRE>
* restore copies
[...]
These JobIds have copies as follows:
+-------+------------------------------------+-----------+------------------+
| JobId | Job | CopyJobId | MediaType |
+-------+------------------------------------+-----------+------------------+
| 2 | CopyJobSave.2009-02-17_16.31.00.11 | 7 | DiskChangerMedia |
+-------+------------------------------------+-----------+------------------+
+-------+-------+----------+----------+---------------------+------------------+
| JobId | Level | JobFiles | JobBytes | StartTime | VolumeName |
+-------+-------+----------+----------+---------------------+------------------+
| 19 | F | 6274 | 76565018 | 2009-02-17 16:30:45 | ChangerVolume002 |
| 2 | I | 1 | 5 | 2009-02-17 16:30:51 | FileVolume001 |
+-------+-------+----------+----------+---------------------+------------------+
You have selected the following JobIds: 19,2
Building directory tree for JobId(s) 19,2 ... ++++++++++++++++++++++++++++++++++++++++++++
5,611 files inserted into the tree.
...
</PRE>
<P>
The Copy Job runs without using the File daemon by copying the data from the
old backup Volume to a different Volume in a different Pool. See the Migration
documentation for additional details. For copy Jobs there is a new selection
directive named <B>PoolUncopiedJobs</B> which selects all Jobs that were
not already copied to another Pool.
<P>
As with Migration, the Client, Volume, Job, or SQL query, are
other possible ways of selecting the Jobs to be copied. Selection
types like SmallestVolume, OldestVolume, PoolOccupancy and PoolTime also
work, but are probably more suited for Migration Jobs.
<P>
If Bacula finds a Copy of a job record that is purged (deleted) from the catalog,
it will promote the Copy to a <I>real</I> backup job and will make it available for
automatic restore. If more than one Copy is available, it will promote the copy
with the smallest JobId.
<P>
A nice solution which can be built with the new Copy feature is often
called disk-to-disk-to-tape backup (DTDTT). A sample config could
look something like the one below:
<P>
<PRE>
Pool {
Name = FullBackupsVirtualPool
Pool Type = Backup
Purge Oldest Volume = Yes
Storage = vtl
NextPool = FullBackupsTapePool
}
Pool {
Name = FullBackupsTapePool
Pool Type = Backup
Recycle = Yes
AutoPrune = Yes
Volume Retention = 365 days
Storage = superloader
}
#
# Fake fileset for copy jobs
#
Fileset {
Name = None
Include {
Options {
signature = MD5
}
}
}
#
# Fake client for copy jobs
#
Client {
Name = None
Address = localhost
Password = "NoNe"
Catalog = MyCatalog
}
#
# Default template for a CopyDiskToTape Job
#
JobDefs {
Name = CopyDiskToTape
Type = Copy
Messages = StandardCopy
Client = None
FileSet = None
Selection Type = PoolUncopiedJobs
Maximum Concurrent Jobs = 10
SpoolData = No
Allow Duplicate Jobs = Yes
Cancel Queued Duplicates = No
Cancel Running Duplicates = No
Priority = 13
}
Schedule {
Name = DaySchedule7:00
Run = Level=Full daily at 7:00
}
Job {
Name = CopyDiskToTapeFullBackups
Enabled = Yes
Schedule = DaySchedule7:00
Pool = FullBackupsVirtualPool
JobDefs = CopyDiskToTape
}
</PRE>
<P>
The example above had 2 pool which are copied using the PoolUncopiedJobs
selection criteria. Normal Full backups go to the Virtual pool and are copied
to the Tape pool the next morning.
<P>
The command <TT>list copies [jobid=x,y,z]</TT> lists copies for a given
<B>jobid</B>.
<P>
<PRE>
*list copies
+-------+------------------------------------+-----------+------------------+
| JobId | Job | CopyJobId | MediaType |
+-------+------------------------------------+-----------+------------------+
| 9 | CopyJobSave.2008-12-20_22.26.49.05 | 11 | DiskChangerMedia |
+-------+------------------------------------+-----------+------------------+
</PRE>
<P>
<H1><A NAME="SECTION00830000000000000000">
ACL Updates</A>
</H1>
<A NAME="653"></A>
The whole ACL code had been overhauled and in this version each platforms has
different streams for each type of acl available on such an platform. As ACLs
between platforms tend to be not that portable (most implement POSIX acls but
some use an other draft or a completely different format) we currently only
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
handle those with the platform specific handler. But for all new backups it
will save the ACLs using the new streams.
<P>
Currently the following platforms support ACLs:
<P>
<UL>
<LI><B>AIX</B>
</LI>
<LI><B>Darwin/OSX</B>
</LI>
<LI><B>FreeBSD</B>
</LI>
<LI><B>HPUX</B>
</LI>
<LI><B>IRIX</B>
</LI>
<LI><B>Linux</B>
</LI>
<LI><B>Tru64</B>
</LI>
<LI><B>Solaris</B>
</LI>
</UL>
<P>
Currently we support the following ACL types (these ACL streams use a reserved
part of the stream numbers):
<P>
<UL>
<LI><B>STREAM_ACL_AIX_TEXT</B> 1000 AIX specific string representation from
acl_get
</LI>
<LI><B>STREAM_ACL_DARWIN_ACCESS_ACL</B> 1001 Darwin (OSX) specific acl_t
string representation from acl_to_text (POSIX acl)
</LI>
<LI><B>STREAM_ACL_FREEBSD_DEFAULT_ACL</B> 1002 FreeBSD specific acl_t
string representation from acl_to_text (POSIX acl) for default acls.
</LI>
<LI><B>STREAM_ACL_FREEBSD_ACCESS_ACL</B> 1003 FreeBSD specific acl_t
string representation from acl_to_text (POSIX acl) for access acls.
</LI>
<LI><B>STREAM_ACL_HPUX_ACL_ENTRY</B> 1004 HPUX specific acl_entry
string representation from acltostr (POSIX acl)
</LI>
<LI><B>STREAM_ACL_IRIX_DEFAULT_ACL</B> 1005 IRIX specific acl_t string
representation from acl_to_text (POSIX acl) for default acls.
</LI>
<LI><B>STREAM_ACL_IRIX_ACCESS_ACL</B> 1006 IRIX specific acl_t string
representation from acl_to_text (POSIX acl) for access acls.
</LI>
<LI><B>STREAM_ACL_LINUX_DEFAULT_ACL</B> 1007 Linux specific acl_t
string representation from acl_to_text (POSIX acl) for default acls.
</LI>
<LI><B>STREAM_ACL_LINUX_ACCESS_ACL</B> 1008 Linux specific acl_t string
representation from acl_to_text (POSIX acl) for access acls.
</LI>
<LI><B>STREAM_ACL_TRU64_DEFAULT_ACL</B> 1009 Tru64 specific acl_t
string representation from acl_to_text (POSIX acl) for default acls.
</LI>
<LI><B>STREAM_ACL_TRU64_DEFAULT_DIR_ACL</B> 1010 Tru64 specific acl_t
string representation from acl_to_text (POSIX acl) for default acls.
</LI>
<LI><B>STREAM_ACL_TRU64_ACCESS_ACL</B> 1011 Tru64 specific acl_t string
representation from acl_to_text (POSIX acl) for access acls.
</LI>
<LI><B>STREAM_ACL_SOLARIS_ACLENT</B> 1012 Solaris specific aclent_t
string representation from acltotext or acl_totext (POSIX acl)
</LI>
<LI><B>STREAM_ACL_SOLARIS_ACE</B> 1013 Solaris specific ace_t string
representation from from acl_totext (NFSv4 or ZFS acl)
</LI>
</UL>
<P>
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
recognize them will give you a warning.
<P>
<H1><A NAME="SECTION00840000000000000000">
Extended Attributes</A>
</H1>
<A NAME="681"></A>
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. 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
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
stores those labels and no specific code is enabled for handling selinux
security labels.
<P>
Currently the following platforms support extended attributes:
<UL>
<LI><B>Darwin/OSX</B>
</LI>
<LI><B>FreeBSD</B>
</LI>
<LI><B>Linux</B>
</LI>
<LI><B>NetBSD</B>
</LI>
</UL>
<P>
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.
<P>
To enable the backup of extended attributes please add the following to your
fileset definition.
<PRE>
FileSet {
Name = "MyFileSet"
Include {
Options {
signature = MD5
xattrsupport = yes
}
File = ...
}
}
</PRE>
<P>
<H1><A NAME="SECTION00850000000000000000">
Shared objects</A>
</H1>
<A NAME="691"></A>
A default build of Bacula will now create the libraries as shared objects
(.so) rather than static libraries as was previously the case.
The shared libraries are built using <B>libtool</B> so it should be quite
portable.
<P>
An important advantage of using shared objects is that on a machine with the
Directory, File daemon, the Storage daemon, and a console, you will have only
one copy of the code in memory rather than four copies. Also the total size of
the binary release is smaller since the library code appears only once rather
than once for every program that uses it; this results in significant reduction
in the size of the binaries particularly for the utility tools.
<P>
In order for the system loader to find the shared objects when loading the
Bacula binaries, the Bacula shared objects must either be in a shared object
directory known to the loader (typically /usr/lib) or they must be in the
directory that may be specified on the <B>./configure</B> line using the <B> -libdir</B> option as:
<P>
<PRE>
./configure --libdir=/full-path/dir
</PRE>
<P>
the default is /usr/lib. If -libdir is specified, there should be
no need to modify your loader configuration provided that
the shared objects are installed in that directory (Bacula
does this with the make install command). The shared objects
that Bacula references are:
<P>
<PRE>
libbaccfg.so
libbacfind.so
libbacpy.so
libbac.so
</PRE>
<P>
These files are symbolically linked to the real shared object file,
which has a version number to permit running multiple versions of
the libraries if desired (not normally the case).
<P>
If you have problems with libtool or you wish to use the old
way of building static libraries, or you want to build a static
version of Bacula you may disable
libtool on the configure command line with:
<P>
<PRE>
./configure --disable-libtool
</PRE>
<P>
<H1><A NAME="SECTION00860000000000000000">
Building Static versions of Bacula</A>
</H1>
<A NAME="705"></A>
In order to build static versions of Bacula, in addition
to configuration options that were needed you now must
also add -disable-libtool. Example
<P>
<PRE>
./configure --enable-static-client-only --disable-libtool
</PRE>
<P>
<H1><A NAME="SECTION00870000000000000000">
Virtual Backup (Vbackup)</A>
</H1>
<A NAME="709"></A>
<A NAME="710"></A>
<P>
Bacula's virtual backup feature is often called Synthetic Backup or
Consolidation in other backup products. It permits you to consolidate the
previous Full backup plus the most recent Differential backup and any
subsequent Incremental backups into a new Full backup. This new Full
backup will then be considered as the most recent Full for any future
Incremental or Differential backups. The VirtualFull backup is
accomplished without contacting the client by reading the previous backup
data and writing it to a volume in a different pool.
<P>
In some respects the Vbackup feature works similar to a Migration job, in
that Bacula normally reads the data from the pool specified in the
Job resource, and writes it to the <B>Next Pool</B> specified in the
Job resource. Note, this means that usually the output from the Virtual
Backup is written into a different pool from where your prior backups
are saved. Doing it this way guarantees that you will not get a deadlock
situation attempting to read and write to the same volume in the Storage
daemon. If you then want to do subsequent backups, you may need to
move the Virtual Full Volume back to your normal backup pool.
Alternatively, you can set your <B>Next Pool</B> to point to the current
pool. This will cause Bacula to read and write to Volumes in the
current pool. In general, this will work, because Bacula will
not allow reading and writing on the same Volume. In any case, once
a VirtualFull has been created, and a restore is done involving the
most current Full, it will read the Volume or Volumes by the VirtualFull
regardless of in which Pool the Volume is found.
<P>
The Vbackup is enabled on a Job by Job in the Job resource by specifying
a level of <B>VirtualFull</B>.
<P>
A typical Job resource definition might look like the following:
<P>
<PRE>
Job {
Name = "MyBackup"
Type = Backup
Client=localhost-fd
FileSet = "Full Set"
Storage = File
Messages = Standard
Pool = Default
SpoolData = yes
}
# Default pool definition
Pool {
Name = Default
Pool Type = Backup
Recycle = yes # Automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 365d # one year
NextPool = Full
Storage = File
}
Pool {
Name = Full
Pool Type = Backup
Recycle = yes # Automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 365d # one year
Storage = DiskChanger
}
# Definition of file storage device
Storage {
Name = File
Address = localhost
Password = "xxx"
Device = FileStorage
Media Type = File
Maximum Concurrent Jobs = 5
}
# Definition of DDS Virtual tape disk storage device
Storage {
Name = DiskChanger
Address = localhost # N.B. Use a fully qualified name here
Password = "yyy"
Device = DiskChanger
Media Type = DiskChangerMedia
Maximum Concurrent Jobs = 4
Autochanger = yes
}
</PRE>
<P>
Then in bconsole or via a Run schedule, you would run the job as:
<P>
<PRE>
run job=MyBackup level=Full
run job=MyBackup level=Incremental
run job=MyBackup level=Differential
run job=MyBackup level=Incremental
run job=MyBackup level=Incremental
</PRE>
<P>
So providing there were changes between each of those jobs, you would end up
with a Full backup, a Differential, which includes the first Incremental
backup, then two Incremental backups. All the above jobs would be written to
the <B>Default</B> pool.
<P>
To consolidate those backups into a new Full backup, you would run the
following:
<P>
<PRE>
run job=MyBackup level=VirtualFull
</PRE>
<P>
And it would produce a new Full backup without using the client, and the output
would be written to the <B>Full</B> Pool which uses the Diskchanger Storage.
<P>
If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
fail with an error.
<P>
Note, the Start and End time of the Virtual Full backup is set to the
values for the last job included in the Virtual Full (in the above example,
it is an Increment). This is so that if another incremental is done, which
will be based on the Virtual Full, it will backup all files from the
last Job included in the Virtual Full rather than from the time the Virtual
Full was actually run.
<P>
<H1><A NAME="SECTION00880000000000000000">
Catalog Format</A>
</H1>
<A NAME="723"></A>
Bacula 3.0 comes with some changes to the catalog format. The upgrade
operation will convert the FileId field of the File table from 32 bits (max 4
billion table entries) to 64 bits (very large number of items). The
conversion process can take a bit of time and will likely DOUBLE THE SIZE of
your catalog during the conversion. Also you won't be able to run jobs during
this conversion period. For example, a 3 million file catalog will take 2
minutes to upgrade on a normal machine. Please don't forget to make a valid
backup of your database before executing the upgrade script. See the
ReleaseNotes for additional details.
<P>
<H1><A NAME="SECTION00890000000000000000">
64 bit Windows Client</A>
</H1>
<A NAME="725"></A>
Unfortunately, Microsoft's implementation of Volume Shadown Copy (VSS) on
their 64 bit OS versions is not compatible with a 32 bit Bacula Client.
As a consequence, we are also releasing a 64 bit version of the Bacula
Windows Client (win64bacula-3.0.0.exe) that does work with VSS.
These binaries should only be installed on 64 bit Windows operating systems.
What is important is not your hardware but whether or not you have
a 64 bit version of the Windows OS.
<P>
Compared to the Win32 Bacula Client, the 64 bit release contains a few differences:
<OL>
<LI>Before installing the Win64 Bacula Client, you must totally
deinstall any prior 2.4.x Client installation using the
Bacula deinstallation (see the menu item). You may want
to save your .conf files first.
</LI>
<LI>Only the Client (File daemon) is ported to Win64, the Director
and the Storage daemon are not in the 64 bit Windows installer.
</LI>
<LI>bwx-console is not yet ported.
</LI>
<LI>bconsole is ported but it has not been tested.
</LI>
<LI>The documentation is not included in the installer.
</LI>
<LI>Due to Vista security restrictions imposed on a default installation
of Vista, before upgrading the Client, you must manually stop
any prior version of Bacula from running, otherwise the install
will fail.
</LI>
<LI>Due to Vista security restrictions imposed on a default installation
of Vista, attempting to edit the conf files via the menu items
will fail. You must directly edit the files with appropriate
permissions. Generally double clicking on the appropriate .conf
file will work providing you have sufficient permissions.
</LI>
<LI>All Bacula files are now installed in
<B>C:/Program Files/Bacula</B> except the main menu items,
which are installed as before. This vastly simplifies the installation.
</LI>
<LI>If you are running on a foreign language version of Windows, most
likely <B>C:/Program Files</B> does not exist, so you should use the
Custom installation and enter an appropriate location to install
the files.
</LI>
<LI>The 3.0.0 Win32 Client continues to install files in the locations used
by prior versions. For the next version we will convert it to use
the same installation conventions as the Win64 version.
</LI>
</OL>
<P>
This project was funded by Bacula Systems.
<P>
<H1><A NAME="SECTION008100000000000000000">
Duplicate Job Control</A>
</H1>
<A NAME="731"></A>
The new version of Bacula provides four new directives that
give additional control over what Bacula does if duplicate jobs
are started. A duplicate job in the sense we use it here means
a second or subsequent job with the same name starts. This
happens most frequently when the first job runs longer than expected because no
tapes are available.
<P>
The four directives each take as an argument a <B>yes</B> or <B>no</B> value and
are specified in the Job resource.
<P>
They are:
<P>
<H2><A NAME="SECTION008101000000000000000">
Allow Duplicate Jobs = yesno</A>
</H2>
<A NAME="737"></A>
If this directive is set to <B>yes</B>, duplicate jobs will be run. If
the directive is set to <B>no</B> (default) then only one job of a given name
may run at one time, and the action that Bacula takes to ensure only
one job runs is determined by the other directives (see below).
<P>
If <B>Allow Duplicate Jobs</B> is set to <B>no</B> 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.
<P>
<H2><A NAME="SECTION008102000000000000000">
Allow Higher Duplicates = yesno</A>
</H2>
<A NAME="745"></A>
This directive was in version 5.0.0, but does not work as
expected. If used, it should always be set to no. In later versions
of Bacula the directive is disabled (disregarded).
<P>
<H2><A NAME="SECTION008103000000000000000">
Cancel Running Duplicates = yesno</A>
</H2>
<A NAME="749"></A>
If <B>Allow Duplicate Jobs</B> is set to <B>no</B> and
if this directive is set to <B>yes</B> any job that is already running
will be canceled. The default is <B>no</B>.
<P>
<H2><A NAME="SECTION008104000000000000000">
Cancel Queued Duplicates = yesno</A>
</H2>
<A NAME="757"></A>
If <B>Allow Duplicate Jobs</B> is set to <B>no</B> and
if this directive is set to <B>yes</B> any job that is
already queued to run but not yet running will be canceled.
The default is <B>no</B>.
<P>
<H1><A NAME="SECTION008110000000000000000">
TLS Authentication</A>
</H1>
<A NAME="763"></A>
In Bacula version 2.5.x and later, in addition to the normal Bacula
CRAM-MD5 authentication that is used to authenticate each Bacula
connection, you can specify that you want TLS Authentication as well,
which will provide more secure authentication.
<P>
This new feature uses Bacula's existing TLS code (normally used for
communications encryption) to do authentication. To use it, you must
specify all the TLS directives normally used to enable communications
encryption (TLS Enable, TLS Verify Peer, TLS Certificate, ...) and
a new directive:
<P>
<H2><A NAME="SECTION008111000000000000000">
TLS Authenticate = yes</A>
</H2>
<PRE>
TLS Authenticate = yes
</PRE>
<P>
in the main daemon configuration resource (Director for the Director,
Client for the File daemon, and Storage for the Storage daemon).
<P>
When <B>TLS Authenticate</B> is enabled, after doing the CRAM-MD5
authentication, Bacula will also do TLS authentication, then TLS
encryption will be turned off, and the rest of the communication between
the two Bacula daemons will be done without encryption.
<P>
If you want to encrypt communications data, use the normal TLS directives
but do not turn on <B>TLS Authenticate</B>.
<P>
<H1><A NAME="SECTION008120000000000000000">
bextract non-portable Win32 data</A>
</H1>
<A NAME="770"></A>
<B>bextract</B> has been enhanced to be able to restore
non-portable Win32 data to any OS. Previous versions were
unable to restore non-portable Win32 data to machines that
did not have the Win32 BackupRead and BackupWrite API calls.
<P>
<H1><A NAME="SECTION008130000000000000000">
State File updated at Job Termination</A>
</H1>
<A NAME="773"></A>
In previous versions of Bacula, the state file, which provides a
summary of previous jobs run in the <B>status</B> command output was
updated only when Bacula terminated, thus if the daemon crashed, the
state file might not contain all the run data. This version of
the Bacula daemons updates the state file on each job termination.
<P>
<H1><A NAME="SECTION008140000000000000000">
MaxFullInterval = time-interval</A>
</H1>
<A NAME="777"></A>
The new Job resource directive <B>Max Full Interval = time-interval</B>
can be used to specify the maximum time interval between <B>Full</B> backup
jobs. When a job starts, if the time since the last Full backup is
greater than the specified interval, and the job would normally be an
<B>Incremental</B> or <B>Differential</B>, it will be automatically
upgraded to a <B>Full</B> backup.
<P>
<H1><A NAME="SECTION008150000000000000000">
MaxDiffInterval = time-interval</A>
</H1>
<A NAME="786"></A>
The new Job resource directive <B>Max Diff Interval = time-interval</B>
can be used to specify the maximum time interval between <B>Differential</B> backup
jobs. When a job starts, if the time since the last Differential backup is
greater than the specified interval, and the job would normally be an
<B>Incremental</B>, it will be automatically
upgraded to a <B>Differential</B> backup.
<P>
<H1><A NAME="SECTION008160000000000000000">
Honor No Dump Flag = yesno</A>
</H1>
<A NAME="795"></A>
On FreeBSD systems, each file has a <B>no dump flag</B> that can be set
by the user, and when it is set it is an indication to backup programs
to not backup that particular file. This version of Bacula contains a
new Options directive within a FileSet resource, which instructs Bacula to
obey this flag. The new directive is:
<P>
<PRE>
Honor No Dump Flag = yes\vb{}no
</PRE>
<P>
The default value is <B>no</B>.
<P>
<H1><A NAME="SECTION008170000000000000000">
Exclude Dir Containing = filename-string</A>
</H1>
<A NAME="802"></A>
The <B>ExcludeDirContaining = filename</B> is a new directive that
can be added to the Include section of the FileSet resource. If the specified
filename (<B>filename-string</B>) is found on the Client in any directory to be
backed up, the whole directory will be ignored (not backed up). For example:
<P>
<PRE>
# List of files to be backed up
FileSet {
Name = "MyFileSet"
Include {
Options {
signature = MD5
}
File = /home
Exclude Dir Containing = .excludeme
}
}
</PRE>
<P>
But in /home, there may be hundreds of directories of users and some
people want to indicate that they don't want to have certain
directories backed up. For example, with the above FileSet, if
the user or sysadmin creates a file named <B>.excludeme</B> in
specific directories, such as
<P>
<PRE>
/home/user/www/cache/.excludeme
/home/user/temp/.excludeme
</PRE>
<P>
then Bacula will not backup the two directories named:
<P>
<PRE>
/home/user/www/cache
/home/user/temp
</PRE>
<P>
NOTE: subdirectories will not be backed up. That is, the directive
applies to the two directories in question and any children (be they
files, directories, etc).
<P>
<H1><A NAME="SECTION008180000000000000000">
Bacula Plugins</A>
</H1>
<A NAME="814"></A>
Support for shared object plugins has been implemented in the Linux, Unix
and Win32 File daemons. The API will be documented separately in
the Developer's Guide or in a new document. For the moment, there is
a single plugin named <B>bpipe</B> that allows an external program to
get control to backup and restore a file.
<P>
Plugins are also planned (partially implemented) in the Director and the
Storage daemon.
<P>
<H2><A NAME="SECTION008181000000000000000">
Plugin Directory</A>
</H2>
<A NAME="817"></A>
Each daemon (DIR, FD, SD) has a new <B>Plugin Directory</B> directive that may
be added to the daemon definition resource. The directory takes a quoted
string argument, which is the name of the directory in which the daemon can
find the Bacula plugins. If this directive is not specified, Bacula will not
load any plugins. Since each plugin has a distinctive name, all the daemons
can share the same plugin directory.
<P>
<H2><A NAME="SECTION008182000000000000000">
Plugin Options</A>
</H2>
<A NAME="820"></A>
The <B>Plugin Options</B> directive takes a quoted string
arguement (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
by the user when he runs a Job via the <B>bconsole</B> command line
prompts.
<P>
Note: this directive may be specified, and there is code to modify
the string in the run command, but the plugin options are not yet passed to
the plugin (i.e. not fully implemented).
<P>
<H2><A NAME="SECTION008183000000000000000">
Plugin Options ACL</A>
</H2>
<A NAME="824"></A>
The <B>Plugin Options ACL</B> directive may be specified in the
Director's Console resource. It functions as all the other ACL commands
do by permitting users running restricted consoles to specify a
<B>Plugin Options</B> that overrides the one specified in the Job
definition. Without this directive restricted consoles may not modify
the Plugin Options.
<P>
<H2><A NAME="SECTION008184000000000000000">
Plugin = plugin-command-string</A>
</H2>
<A NAME="829"></A>
The <B>Plugin</B> directive is specified in the Include section of
a FileSet resource where you put your <B>File = xxx</B> directives.
For example:
<P>
<PRE>
FileSet {
Name = "MyFileSet"
Include {
Options {
signature = MD5
}
File = /home
Plugin = "bpipe:..."
}
}
</PRE>
<P>
In the above example, when the File daemon is processing the directives
in the Include section, it will first backup all the files in <B>/home</B>
then it will load the plugin named <B>bpipe</B> (actually bpipe-dir.so) from
the Plugin Directory. The syntax and semantics of the Plugin directive
require the first part of the string up to the colon (:) to be the name
of the plugin. Everything after the first colon is ignored by the File daemon but
is passed to the plugin. Thus the plugin writer may define the meaning of the
rest of the string as he wishes.
<P>
Please see the next section for information about the <B>bpipe</B> Bacula
plugin.
<P>
<H1><A NAME="SECTION008190000000000000000">
The bpipe Plugin</A>
</H1>
<A NAME="838"></A>
The <B>bpipe</B> plugin is provided in the directory src/plugins/fd/bpipe-fd.c of
the Bacula source distribution. When the plugin is compiled and linking into
the resulting dynamic shared object (DSO), it will have the name <B>bpipe-fd.so</B>.
Please note that this is a very simple plugin that was written for
demonstration and test purposes. It is and can be used in production, but
that was never really intended.
<P>
The purpose of the plugin is to provide an interface to any system program for
backup and restore. As specified above the <B>bpipe</B> plugin is specified in
the Include section of your Job's FileSet resource. The full syntax of the
plugin directive as interpreted by the <B>bpipe</B> plugin (each plugin is free
to specify the sytax as it wishes) is:
<P>
<PRE>
Plugin = "<field1>:<field2>:<field3>:<field4>"
</PRE>
<P>
where
<DL>
<DT></DT>
<DD><B>field1</B> is the name of the plugin with the trailing <B>-fd.so</B>
stripped off, so in this case, we would put <B>bpipe</B> in this field.
<P>
</DD>
<DT></DT>
<DD><B>field2</B> specifies the namespace, which for <B>bpipe</B> is the
pseudo path and filename under which the backup will be saved. This pseudo
path and filename will be seen by the user in the restore file tree.
For example, if the value is <B>/MYSQL/regress.sql</B>, the data
backed up by the plugin will be put under that "pseudo" path and filename.
You must be careful to choose a naming convention that is unique to avoid
a conflict with a path and filename that actually exists on your system.
<P>
</DD>
<DT></DT>
<DD><B>field3</B> for the <B>bpipe</B> plugin
specifies the "reader" program that is called by the plugin during
backup to read the data. <B>bpipe</B> will call this program by doing a
<B>popen</B> on it.
<P>
</DD>
<DT></DT>
<DD><B>field4</B> for the <B>bpipe</B> plugin
specifies the "writer" program that is called by the plugin during
restore to write the data back to the filesystem.
</DD>
</DL>
<P>
Please note that for two items above describing the "reader" and "writer"
fields, these programs are "executed" by Bacula, which
means there is no shell interpretation of any command line arguments
you might use. If you want to use shell characters (redirection of input
or output, ...), then we recommend that you put your command or commands
in a shell script and execute the script. In addition if you backup a
file with the reader program, when running the writer program during
the restore, Bacula will not automatically create the path to the file.
Either the path must exist, or you must explicitly do so with your command
or in a shell script.
<P>
Putting it all together, the full plugin directive line might look
like the following:
<P>
<PRE>
Plugin = "bpipe:/MYSQL/regress.sql:mysqldump -f
--opt --databases bacula:mysql"
</PRE>
<P>
The directive has been split into two lines, but within the <B>bacula-dir.conf</B> file
would be written on a single line.
<P>
This causes the File daemon to call the <B>bpipe</B> plugin, which will write
its data into the "pseudo" file <B>/MYSQL/regress.sql</B> by calling the
program <B>mysqldump -f -opt -database bacula</B> to read the data during
backup. The mysqldump command outputs all the data for the database named
<B>bacula</B>, which will be read by the plugin and stored in the backup.
During restore, the data that was backed up will be sent to the program
specified in the last field, which in this case is <B>mysql</B>. When
<B>mysql</B> is called, it will read the data sent to it by the plugn
then write it back to the same database from which it came (<B>bacula</B>
in this case).
<P>
The <B>bpipe</B> plugin is a generic pipe program, that simply transmits
the data from a specified program to Bacula for backup, and then from Bacula to
a specified program for restore.
<P>
By using different command lines to <B>bpipe</B>,
you can backup any kind of data (ASCII or binary) depending
on the program called.
<P>
<H1><A NAME="SECTION008200000000000000000">
Microsoft Exchange Server 2003/2007 Plugin</A>
</H1>
<A NAME="872"></A>
<H2><A NAME="SECTION008201000000000000000">
Background</A>
</H2>
The Exchange plugin was made possible by a funded development project
between Equiinet Ltd - www.equiinet.com (many thanks) and Bacula Systems.
The code for the plugin was written by James Harper, and the Bacula core
code by Kern Sibbald. All the code for this funded development has become
part of the Bacula project. Thanks to everyone who made it happen.
<P>
<H2><A NAME="SECTION008202000000000000000">
Concepts</A>
</H2>
Although it is possible to backup Exchange using Bacula VSS the Exchange
plugin adds a good deal of functionality, because while Bacula VSS
completes a full backup (snapshot) of Exchange, it does
not support Incremental or Differential backups, restoring is more
complicated, and a single database restore is not possible.
<P>
Microsoft Exchange organises its storage into Storage Groups with
Databases inside them. A default installation of Exchange will have a
single Storage Group called 'First Storage Group', with two Databases
inside it, "Mailbox Store (SERVER NAME)" and
"Public Folder Store (SERVER NAME)",
which hold user email and public folders respectively.
<P>
In the default configuration, Exchange logs everything that happens to
log files, such that if you have a backup, and all the log files since,
you can restore to the present time. Each Storage Group has its own set
of log files and operates independently of any other Storage Groups. At
the Storage Group level, the logging can be turned off by enabling a
function called "Enable circular logging". At this time the Exchange
plugin will not function if this option is enabled.
<P>
The plugin allows backing up of entire storage groups, and the restoring
of entire storage groups or individual databases. Backing up and
restoring at the individual mailbox or email item is not supported but
can be simulated by use of the "Recovery" Storage Group (see below).
<P>
<H2><A NAME="SECTION008203000000000000000">
Installing</A>
</H2>
The Exchange plugin requires a DLL that is shipped with Microsoft
Exchanger Server called <B>esebcli2.dll</B>. Assuming Exchange is installed
correctly the Exchange plugin should find this automatically and run
without any additional installation.
<P>
If the DLL can not be found automatically it will need to be copied into
the Bacula installation
directory (eg C:<code>\</code>Program Files<code>\</code>Bacula<code>\</code>bin). The Exchange API DLL is
named esebcli2.dll and is found in C:<code>\</code>Program Files<code>\</code>Exchsrvr<code>\</code>bin on a
default Exchange installation.
<P>
<H2><A NAME="SECTION008204000000000000000">
Backing Up</A>
</H2>
To back up an Exchange server the Fileset definition must contain at
least <B>Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"</B> for
the backup to work correctly. The 'exchange:' bit tells Bacula to look
for the exchange plugin, the '@EXCHANGE' bit makes sure all the backed
up files are prefixed with something that isn't going to share a name
with something outside the plugin, and the 'Microsoft Information Store'
bit is required also. It is also possible to add the name of a storage
group to the "Plugin =" line, eg
<BR><B>Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"</B>
<BR>
if you want only a single storage group backed up.
<P>
Additionally, you can suffix the 'Plugin =' directive with
":notrunconfull" which will tell the plugin not to truncate the Exchange
database at the end of a full backup.
<P>
An Incremental or Differential backup will backup only the database logs
for each Storage Group by inspecting the "modified date" on each
physical log file. Because of the way the Exchange API works, the last
logfile backed up on each backup will always be backed up by the next
Incremental or Differential backup too. This adds 5MB to each
Incremental or Differential backup size but otherwise does not cause any
problems.
<P>
By default, a normal VSS fileset containing all the drive letters will
also back up the Exchange databases using VSS. This will interfere with
the plugin and Exchange's shared ideas of when the last full backup was
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.
<P>
<PRE>
FileSet {
Include {
File = C:/Program Files/Exchsrvr/mdbdata
Plugin = "exchange:..."
}
Exclude {
File = C:/Program Files/Exchsrvr/mdbdata/E00.chk
File = C:/Program Files/Exchsrvr/mdbdata/E00.log
File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log
File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log
File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log
File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log
File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb
}
}
</PRE>
<P>
The advantage of excluding the above files is that you can significantly
reduce the size of your backup since all the important Exchange files
will be properly saved by the Plugin.
<P>
<H2><A NAME="SECTION008205000000000000000">
Restoring</A>
</H2>
The restore operation is much the same as a normal Bacula restore, with
the following provisos:
<P>
<UL>
<LI>The <B>Where</B> restore option must not be specified
</LI>
<LI>Each Database directory must be marked as a whole. You cannot just
select (say) the .edb file and not the others.
</LI>
<LI>If a Storage Group is restored, the directory of the Storage Group
must be marked too.
</LI>
<LI>It is possible to restore only a subset of the available log files,
but they <B>must</B> be contiguous. Exchange will fail to restore correctly
if a log file is missing from the sequence of log files
</LI>
<LI>Each database to be restored must be dismounted and marked as "Can be
overwritten by restore"
</LI>
<LI>If an entire Storage Group is to be restored (eg all databases and
logs in the Storage Group), then it is best to manually delete the
database files from the server (eg C:<code>\</code>Program Files<code>\</code>Exchsrvr<code>\</code>mdbdata<code>\</code>*)
as Exchange can get confused by stray log files lying around.
</LI>
</UL>
<P>
<H2><A NAME="SECTION008206000000000000000">
Restoring to the Recovery Storage Group</A>
</H2>
The concept of the Recovery Storage Group is well documented by
Microsoft
http://support.microsoft.com/kb/824126http://support.microsoft.com/kb/824126,
but to briefly summarize...
<P>
Microsoft Exchange allows the creation of an additional Storage Group
called the Recovery Storage Group, which is used to restore an older
copy of a database (e.g. before a mailbox was deleted) into without
messing with the current live data. This is required as the Standard and
Small Business Server versions of Exchange can not ordinarily have more
than one Storage Group.
<P>
To create the Recovery Storage Group, drill down to the Server in Exchange
System Manager, right click, and select
<B>"New -> Recovery Storage Group..."</B>. Accept or change the file
locations and click OK. On the Recovery Storage Group, right click and
select <B>"Add Database to Recover..."</B> and select the database you will
be restoring.
<P>
Restore only the single database nominated as the database in the
Recovery Storage Group. Exchange will redirect the restore to the
Recovery Storage Group automatically.
Then run the restore.
<P>
<H2><A NAME="SECTION008207000000000000000">
Restoring on Microsoft Server 2007</A>
</H2>
Apparently the <B>Exmerge</B> 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:
http://technet.microsoft.com/en-us/library/aa997694.aspxhttp://technet.microsoft.com/en-us/library/aa997694.aspx,
and involves using the <B>Restore-Mailbox</B> and <B>Get-MailboxStatistics</B> shell commands.
<P>
<H2><A NAME="SECTION008208000000000000000">
Caveats</A>
</H2>
This plugin is still being developed, so you should consider it
currently in BETA test, and thus use in a production environment
should be done only after very careful testing.
<P>
When doing a full backup, the Exchange database logs are truncated by
Exchange as soon as the plugin has completed the backup. If the data
never makes it to the backup medium (eg because of spooling) then the
logs will still be truncated, but they will also not have been backed
up. A solution to this is being worked on. You will have to schedule a
new Full backup to ensure that your next backups will be usable.
<P>
The "Enable Circular Logging" option cannot be enabled or the plugin
will fail.
<P>
Exchange insists that a successful Full backup must have taken place if
an Incremental or Differential backup is desired, and the plugin will
fail if this is not the case. If a restore is done, Exchange will
require that a Full backup be done before an Incremental or Differential
backup is done.
<P>
The plugin will most likely not work well if another backup application
(eg NTBACKUP) is backing up the Exchange database, especially if the
other backup application is truncating the log files.
<P>
The Exchange plugin has not been tested with the <B>Accurate</B> option, so
we recommend either carefully testing or that you avoid this option for
the current time.
<P>
The Exchange plugin is not called during processing the bconsole <B>estimate</B> command, and so anything that would be backed up by the plugin
will not be added to the estimate total that is displayed.
<P>
<H1><A NAME="SECTION008210000000000000000">
libdbi Framework</A>
</H1>
<A NAME="902"></A>
As a general guideline, Bacula has support for a few catalog database drivers
(MySQL, PostgreSQL, SQLite)
coded natively by the Bacula team. With the libdbi implementation, which is a
Bacula driver that uses libdbi to access the catalog, we have an open field to
use many different kinds database engines following the needs of users.
<P>
The according to libdbi (http://libdbi.sourceforge.net/) project: libdbi
implements a database-independent abstraction layer in C, similar to the
DBI/DBD layer in Perl. Writing one generic set of code, programmers can
leverage the power of multiple databases and multiple simultaneous database
connections by using this framework.
<P>
Currently the libdbi driver in Bacula project only supports the same drivers
natively coded in Bacula. However the libdbi project has support for many
others database engines. You can view the list at
http://libdbi-drivers.sourceforge.net/. In the future all those drivers can be
supported by Bacula, however, they must be tested properly by the Bacula team.
<P>
Some of benefits of using libdbi are:
<UL>
<LI>The possibility to use proprietary databases engines in which your
proprietary licenses prevent the Bacula team from developing the driver.
</LI>
<LI>The possibility to use the drivers written for the libdbi project.
</LI>
<LI>The possibility to use other database engines without recompiling Bacula
to use them. Just change one line in bacula-dir.conf
</LI>
<LI>Abstract Database access, this is, unique point to code and profiling
catalog database access.
</LI>
</UL>
<P>
The following drivers have been tested:
<UL>
<LI>PostgreSQL, with and without batch insert
</LI>
<LI>Mysql, with and without batch insert
</LI>
<LI>SQLite
</LI>
<LI>SQLite3
</LI>
</UL>
<P>
In the future, we will test and approve to use others databases engines
(proprietary or not) like DB2, Oracle, Microsoft SQL.
<P>
To compile Bacula to support libdbi we need to configure the code with the
-with-dbi and -with-dbi-driver=[database] ./configure options, where
[database] is the database engine to be used with Bacula (of course we can
change the driver in file bacula-dir.conf, see below). We must configure the
access port of the database engine with the option -with-db-port, because the
libdbi framework doesn't know the default access port of each database.
<P>
The next phase is checking (or configuring) the bacula-dir.conf, example:
<PRE>
Catalog {
Name = MyCatalog
dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
dbname = regress; user = regress; password = ""
}
</PRE>
<P>
The parameter <B>dbdriver</B> indicates that we will use the driver dbi with a
mysql database. Currently the drivers supported by Bacula are: postgresql,
mysql, sqlite, sqlite3; these are the names that may be added to string "dbi:".
<P>
The following limitations apply when Bacula is set to use the libdbi framework:
- Not tested on the Win32 platform
- A little performance is lost if comparing with native database driver.
The reason is bound with the database driver provided by libdbi and the
simple fact that one more layer of code was added.
<P>
It is important to remember, when compiling Bacula with libdbi, the
following packages are needed:
<UL>
<LI>libdbi version 1.0.0, http://libdbi.sourceforge.net/
</LI>
<LI>libdbi-drivers 1.0.0, http://libdbi-drivers.sourceforge.net/
</LI>
</UL>
<P>
You can download them and compile them on your system or install the packages
from your OS distribution.
<P>
<H1><A NAME="SECTION008220000000000000000">
Console Command Additions and Enhancements</A>
</H1>
<A NAME="913"></A>
<P>
<H2><A NAME="SECTION008221000000000000000">
Display Autochanger Content</A>
</H2>
<A NAME="915"></A>
<P>
The <B>status slots storage=storage-name</B> command displays
autochanger content.
<P>
<PRE>
Slot | Volume Name | Status | Media Type | Pool |
------+---------------+----------+-------------------+------------|
1 | 00001 | Append | DiskChangerMedia | Default |
2 | 00002 | Append | DiskChangerMedia | Default |
3*| 00003 | Append | DiskChangerMedia | Scratch |
4 | | | | |
</PRE>
<P>
If you an asterisk (<B>*</B>) appears after the slot number, you must run an
<B>update slots</B> command to synchronize autochanger content with your
catalog.
<P>
<H2><A NAME="SECTION008222000000000000000">
list joblog job=xxx or jobid=nnn</A>
</H2>
<A NAME="923"></A>
A new list command has been added that allows you to list the contents
of the Job Log stored in the catalog for either a Job Name (fully qualified)
or for a particular JobId. The <B>llist</B> command will include a line with
the time and date of the entry.
<P>
Note for the catalog to have Job Log entries, you must have a directive
such as:
<P>
<PRE>
catalog = all
</PRE>
<P>
In your Director's <B>Messages</B> resource.
<P>
<H2><A NAME="SECTION008223000000000000000">
Use separator for multiple commands</A>
</H2>
<A NAME="929"></A>
When using bconsole with readline, you can set the command separator with
<B>@separator</B> command to one
of those characters to write commands who require multiple input in one line.
<PRE>
!$%&'()*+,-/:;<>?[]^`{|}~
</PRE>
<P>
<H2><A NAME="SECTION008224000000000000000">
Deleting Volumes</A>
</H2>
The delete volume bconsole command has been modified to
require an asterisk (*) in front of a MediaId otherwise the
value you enter is a taken to be a Volume name. This is so that
users may delete numeric Volume names. The previous Bacula versions
assumed that all input that started with a number was a MediaId.
<P>
This new behavior is indicated in the prompt if you read it
carefully.
<P>
<H1><A NAME="SECTION008230000000000000000">
Bare Metal Recovery</A>
</H1>
The old bare metal recovery project is essentially dead. One
of the main features of it was that it would build a recovery
CD based on the kernel on your system. The problem was that
every distribution has a different boot procedure and different
scripts, and worse yet, the boot procedures and scripts change
from one distribution to another. This meant that maintaining
(keeping up with the changes) the rescue CD was too much work.
<P>
To replace it, a new bare metal recovery USB boot stick has been developed
by Bacula Systems. This technology involves remastering a Ubuntu LiveCD to
boot from a USB key.
<P>
Advantages:
<OL>
<LI>Recovery can be done from within graphical environment.
</LI>
<LI>Recovery can be done in a shell.
</LI>
<LI>Ubuntu boots on a large number of Linux systems.
</LI>
<LI>The process of updating the system and adding new
packages is not too difficult.
</LI>
<LI>The USB key can easily be upgraded to newer Ubuntu versions.
</LI>
<LI>The USB key has writable partitions for modifications to
the OS and for modification to your home directory.
</LI>
<LI>You can add new files/directories to the USB key very easily.
</LI>
<LI>You can save the environment from multiple machines on
one USB key.
</LI>
<LI>Bacula Systems is funding its ongoing development.
</LI>
</OL>
<P>
The disadvantages are:
<OL>
<LI>The USB key is usable but currently under development.
</LI>
<LI>Not everyone may be familiar with Ubuntu (no worse
than using Knoppix)
</LI>
<LI>Some older OSes cannot be booted from USB. This can
be resolved by first booting a Ubuntu LiveCD then plugging
in the USB key.
</LI>
<LI>Currently the documentation is sketchy and not yet added
to the main manual. See below ...
</LI>
</OL>
<P>
The documentation and the code can be found in the <B>rescue</B> package
in the directory <B>linux/usb</B>.
<P>
<H1><A NAME="SECTION008240000000000000000">
Miscellaneous</A>
</H1>
<A NAME="942"></A>
<P>
<H2><A NAME="SECTION008241000000000000000">
Allow Mixed Priority = yesno</A>
</H2>
<A NAME="946"></A>
This directive is only implemented in version 2.5 and later. When
set to <B>yes</B> (default <B>no</B>), this job may run even if lower
priority jobs are already running. This means a high priority job
will not have to wait for other jobs to finish before starting.
The scheduler will only mix priorities when all running jobs have
this set to true.
<P>
Note that only higher priority jobs will start early. Suppose the
director will allow two concurrent jobs, and that two jobs with
priority 10 are running, with two more in the queue. If a job with
priority 5 is added to the queue, it will be run as soon as one of
the running jobs finishes. However, new priority 10 jobs will not
be run until the priority 5 job has finished.
<P>
<H2><A NAME="SECTION008242000000000000000">
Bootstrap File Directive - FileRegex</A>
</H2>
<A NAME="950"></A>
<B>FileRegex</B> is a new command that can be added to the bootstrap
(.bsr) file. The value is a regular expression. When specified, only
matching filenames will be restored.
<P>
During a restore, if all File records are pruned from the catalog
for a Job, normally Bacula can restore only all files saved. That
is there is no way using the catalog to select individual files.
With this new feature, Bacula will ask if you want to specify a Regex
expression for extracting only a part of the full backup.
<P>
<PRE>
Building directory tree for JobId(s) 1,3 ...
There were no files inserted into the tree, so file selection
is not possible.Most likely your retention policy pruned the files
Do you want to restore all the files? (yes\vb{}no): no
Regexp matching files to restore? (empty to abort): /tmp/regress/(bin|tests)/
Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr
</PRE>
<P>
<H2><A NAME="SECTION008243000000000000000">
Bootstrap File Optimization Changes</A>
</H2>
In order to permit proper seeking on disk files, we have extended the bootstrap
file format to include a <B>VolStartAddr</B> and <B>VolEndAddr</B> records. Each
takes a 64 bit unsigned integer range (i.e. nnn-mmm) which defines the start
address range and end address range respectively. These two directives replace
the <B>VolStartFile</B>, <B>VolEndFile</B>, <B>VolStartBlock</B> and <B> VolEndBlock</B> directives. Bootstrap files containing the old directives will
still work, but will not properly take advantage of proper disk seeking, and
may read completely to the end of a disk volume during a restore. With the new
format (automatically generated by the new Director), restores will seek
properly and stop reading the volume when all the files have been restored.
<P>
<H2><A NAME="SECTION008244000000000000000">
Solaris ZFS/NFSv4 ACLs</A>
</H2>
This is an upgrade of the previous Solaris ACL backup code
to the new library format, which will backup both the old
POSIX(UFS) ACLs as well as the ZFS ACLs.
<P>
The new code can also restore POSIX(UFS) ACLs to a ZFS filesystem
(it will translate the POSIX(UFS)) ACL into a ZFS/NFSv4 one) it can also
be used to transfer from UFS to ZFS filesystems.
<P>
<H2><A NAME="SECTION008245000000000000000">
Virtual Tape Emulation</A>
</H2>
<A NAME="963"></A>
We now have a Virtual Tape emulator that allows us to run though 99.9% of
the tape code but actually reading and writing to a disk file. Used with the
<B>disk-changer</B> script, you can now emulate an autochanger with 10 drives
and 700 slots. This feature is most useful in testing. It is enabled
by using <B>Device Type = vtape</B> in the Storage daemon's Device
directive. This feature is only implemented on Linux machines and should not be
used for production.
<P>
<H2><A NAME="SECTION008246000000000000000">
Bat Enhancements</A>
</H2>
<A NAME="967"></A>
Bat (the Bacula Administration Tool) GUI program has been significantly
enhanced and stabilized. In particular, there are new table based status
commands; it can now be easily localized using Qt4 Linguist.
<P>
The Bat communications protocol has been significantly enhanced to improve
GUI handling. Note, you <B>must</B> use a the bat that is distributed with
the Director you are using otherwise the communications protocol will not
work.
<P>
<H2><A NAME="SECTION008247000000000000000">
RunScript Enhancements</A>
</H2>
<A NAME="970"></A>
The <B>RunScript</B> resource has been enhanced to permit multiple
commands per RunScript. Simply specify multiple <B>Command</B> directives
in your RunScript.
<P>
<PRE>
Job {
Name = aJob
RunScript {
Command = "/bin/echo test"
Command = "/bin/echo an other test"
Command = "/bin/echo 3 commands in the same runscript"
RunsWhen = Before
}
...
}
</PRE>
<P>
A new Client RunScript <B>RunsWhen</B> keyword of <B>AfterVSS</B> has been
implemented, which runs the command after the Volume Shadow Copy has been made.
<P>
Console commands can be specified within a RunScript by using:
<B>Console = command</B>, however, this command has not been
carefully tested and debugged and is known to easily crash the Director.
We would appreciate feedback. Due to the recursive nature of this command, we
may remove it before the final release.
<P>
<H2><A NAME="SECTION008248000000000000000">
Status Enhancements</A>
</H2>
<A NAME="980"></A>
The bconsole <B>status dir</B> output has been enhanced to indicate
Storage daemon job spooling and despooling activity.
<P>
<H2><A NAME="SECTION008249000000000000000">
Connect Timeout</A>
</H2>
<A NAME="983"></A>
The default connect timeout to the File
daemon has been set to 3 minutes. Previously it was 30 minutes.
<P>
<H2><A NAME="SECTION0082410000000000000000">
ftruncate for NFS Volumes</A>
</H2>
<A NAME="985"></A>
If you write to a Volume mounted by NFS (say on a local file server),
in previous Bacula versions, when the Volume was recycled, it was not
properly truncated because NFS does not implement ftruncate (file
truncate). This is now corrected in the new version because we have
written code (actually a kind user) that deletes and recreates the Volume,
thus accomplishing the same thing as a truncate.
<P>
<H2><A NAME="SECTION0082411000000000000000">
Support for Ubuntu</A>
</H2>
The new version of Bacula now recognizes the Ubuntu (and Kubuntu)
version of Linux, and thus now provides correct autostart routines.
Since Ubuntu officially supports Bacula, you can also obtain any
recent release of Bacula from the Ubuntu repositories.
<P>
<H2><A NAME="SECTION0082412000000000000000">
Recycle Pool = pool-name</A>
</H2>
<A NAME="989"></A>
The new <B>RecyclePool</B> directive defines to which pool the Volume will
be placed (moved) when it is recycled. Without this directive, a Volume will
remain in the same pool when it is recycled. With this directive, it can be
moved automatically to any existing pool during a recycle. This directive is
probably most useful when defined in the Scratch pool, so that volumes will
be recycled back into the Scratch pool.
<P>
<H2><A NAME="SECTION0082413000000000000000">
FD Version</A>
</H2>
<A NAME="992"></A>
The File daemon to Director protocol now includes a version
number, which although there is no visible change for users,
will help us in future versions automatically determine
if a File daemon is not compatible.
<P>
<H2><A NAME="SECTION0082414000000000000000">
Max Run Sched Time = time-period-in-seconds</A>
</H2>
<A NAME="995"></A>
The time specifies the maximum allowed time that a job may run, counted from
when the job was scheduled. This can be useful to prevent jobs from running
during working hours. We can see it like <TT>Max Start Delay + Max Run
Time</TT>.
<P>
<H2><A NAME="SECTION0082415000000000000000">
Max Wait Time = time-period-in-seconds</A>
</H2>
<A NAME="999"></A>
Previous <B>MaxWaitTime</B> directives aren't working as expected, instead
of checking the maximum allowed time that a job may block for a resource,
those directives worked like <B>MaxRunTime</B>. Some users are reporting to
use <B>Incr/Diff/Full Max Wait Time</B> to control the maximum run time of
their job depending on the level. Now, they have to use
<B>Incr/Diff/Full Max Run Time</B>. <B>Incr/Diff/Full Max Wait Time</B>
directives are now deprecated.
<P>
<H2><A NAME="SECTION0082416000000000000000">
Incremental|Differential Max Wait Time = time-period-in-seconds</A>
</H2>
<A NAME="1007"></A>
<A NAME="1008"></A>
<P>
These directives have been deprecated in favor of
<TT>Incremental|Differential Max Run Time</TT>.
<P>
<H2><A NAME="SECTION0082417000000000000000">
Max Run Time directives</A>
</H2>
<A NAME="1011"></A>
Using <B>Full/Diff/Incr Max Run Time</B>, it's now possible to specify the
maximum allowed time that a job can run depending on the level.
<P>
<DIV ALIGN="CENTER"><A NAME="1015"></A>
<TABLE>
<CAPTION ALIGN="BOTTOM"><STRONG>Figure 7.1:</STRONG>
Job time control directives</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER"> <IMG
WIDTH="586" HEIGHT="304" ALIGN="BOTTOM" BORDER="0"
SRC="img15.png"
ALT="\includegraphics[width=13cm]{different_time.eps}">
</DIV></TD></TR>
</TABLE>
</DIV>
<P>
<H2><A NAME="SECTION0082418000000000000000">
Statistics Enhancements</A>
</H2>
<A NAME="1018"></A>
If you (or probably your boss) want to have statistics on your backups to
provide some <I>Service Level Agreement</I> indicators, you could use a few
SQL queries on the Job table to report how many:
<P>
<UL>
<LI>jobs have run
</LI>
<LI>jobs have been successful
</LI>
<LI>files have been backed up
</LI>
<LI>...
</LI>
</UL>
<P>
However, these statistics are accurate only if your job retention is greater
than your statistics period. Ie, if jobs are purged from the catalog, you won't
be able to use them.
<P>
Now, you can use the <B>update stats [days=num]</B> console command to fill
the JobHistory table with new Job records. If you want to be sure to take in
account only <B>good jobs</B>, ie if one of your important job has failed but
you have fixed the problem and restarted it on time, you probably want to
delete the first <I>bad</I> job record and keep only the successful one. For
that simply let your staff do the job, and update JobHistory table after two or
three days depending on your organization using the <B>[days=num]</B> option.
<P>
These statistics records aren't used for restoring, but mainly for
capacity planning, billings, etc.
<P>
The Bweb interface provides a statistics module that can use this feature. You
can also use tools like Talend or extract information by yourself.
<P>
The <B>Statistics Retention = time</B> director directive defines
the length of time that Bacula will keep statistics job records in the Catalog
database after the Job End time. (In <TT>JobHistory</TT> table) When this time
period expires, and if user runs <TT>prune stats</TT> command, Bacula will
prune (remove) Job records that are older than the specified period.
<P>
You can use the following Job resource in your nightly <B>BackupCatalog</B>
job to maintain statistics.
<PRE>
Job {
Name = BackupCatalog
...
RunScript {
Console = "update stats days=3"
Console = "prune stats yes"
RunsWhen = After
RunsOnClient = no
}
}
</PRE>
<P>
<H2><A NAME="SECTION0082419000000000000000">
ScratchPool = pool-resource-name</A>
</H2>
<A NAME="1035"></A>
This directive permits to specify a specific <I>Scratch</I> pool for the
current pool. This is useful when using multiple storage sharing the same
mediatype or when you want to dedicate volumes to a particular set of pool.
<P>
<H2><A NAME="SECTION0082420000000000000000">
Enhanced Attribute Despooling</A>
</H2>
<A NAME="1038"></A>
If the storage daemon and the Director are on the same machine, the spool file
that contains attributes is read directly by the Director instead of being
transmitted across the network. That should reduce load and speedup insertion.
<P>
<H2><A NAME="SECTION0082421000000000000000">
SpoolSize = size-specification-in-bytes</A>
</H2>
<A NAME="1041"></A>
A new Job directive permits to specify the spool size per job. This is used
in advanced job tunning. <B>SpoolSize=<I>bytes</I></B>
<P>
<H2><A NAME="SECTION0082422000000000000000">
MaximumConsoleConnections = number</A>
</H2>
<A NAME="1045"></A>
A new director directive permits to specify the maximum number of Console
Connections that could run concurrently. The default is set to 20, but you may
set it to a larger number.
<P>
<H2><A NAME="SECTION0082423000000000000000">
VerId = string</A>
</H2>
<A NAME="1048"></A>
A new director directive permits to specify a personnal identifier that will be
displayed in the <TT>version</TT> command.
<P>
<H2><A NAME="SECTION0082424000000000000000">
dbcheck enhancements</A>
</H2>
<A NAME="1051"></A>
If you are using Mysql, dbcheck will now ask you if you want to create
temporary indexes to speed up orphaned Path and Filename elimination.
<P>
A new <TT>-B</TT> option allows you to print catalog information in a simple
text based format. This is useful to backup it in a secure way.
<P>
<PRE>
$ dbcheck -B
catalog=MyCatalog
db_type=SQLite
db_name=regress
db_driver=
db_user=regress
db_password=
db_address=
db_port=0
db_socket=
</PRE>
<P>
You can now specify the database connection port in the command line.
<P>
<H2><A NAME="SECTION0082425000000000000000">
-docdir configure option</A>
</H2>
<A NAME="1107"></A>
You can use -docdir= on the ./configure command to
specify the directory where you want Bacula to install the
LICENSE, ReleaseNotes, ChangeLog, ... files. The default is
<B>/usr/share/doc/bacula</B>.
<P>
<H2><A NAME="SECTION0082426000000000000000">
-htmldir configure option</A>
</H2>
<A NAME="1109"></A>
You can use -htmldir= on the ./configure command to
specify the directory where you want Bacula to install the bat html help
files. The default is <B>/usr/share/doc/bacula/html</B>
<P>
<H2><A NAME="SECTION0082427000000000000000">
-with-plugindir configure option</A>
</H2>
<A NAME="1111"></A>
You can use -plugindir= on the ./configure command to
specify the directory where you want Bacula to install
the plugins (currently only bpipe-fd). The default is
/usr/lib.
<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html1156"
HREF="Current_State_Bacula.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1150"
HREF="Bacula_Main_Reference.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1144"
HREF="New_Features_in_Released.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1152"
HREF="Contents.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1154"
HREF="Thanks.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1157"
HREF="Current_State_Bacula.html">The Current State of</A>
<B> Up:</B> <A NAME="tex2html1151"
HREF="Bacula_Main_Reference.html">Bacula Main Reference</A>
<B> Previous:</B> <A NAME="tex2html1145"
HREF="New_Features_in_Released.html">New Features in Released</A>
<B> <A NAME="tex2html1153"
HREF="Contents.html">Contents</A></B>
<B> <A NAME="tex2html1155"
HREF="Thanks.html">Index</A></B>
<!--End of Navigation Panel-->
<ADDRESS>
2012-01-24
</ADDRESS>
</BODY>
</HTML>
