New Features in 3.0.0
Keywords: main

Subsections

- Accurate Backup
  - Accurate = yesno
- Copy Jobs
- ACL Updates
- Extended Attributes
- Shared objects
- Building Static versions of Bacula
- Virtual Backup (Vbackup)
- Catalog Format
- 64 bit Windows Client
- Duplicate Job Control
  - Allow Duplicate Jobs = yesno
  - Allow Higher Duplicates = yesno
  - Cancel Running Duplicates = yesno
  - Cancel Queued Duplicates = yesno
- TLS Authentication
  - TLS Authenticate = yes
- bextract non-portable Win32 data
- State File updated at Job Termination
- MaxFullInterval = time-interval
- MaxDiffInterval = time-interval
- Honor No Dump Flag = yesno
- Exclude Dir Containing = filename-string
- Bacula Plugins
  - Plugin Directory
  - Plugin Options
  - Plugin Options ACL
  - Plugin = plugin-command-string
- The bpipe Plugin
- Microsoft Exchange Server 2003/2007 Plugin
  - Background
  - Concepts
  - Installing
  - Backing Up
  - Restoring
  - Restoring to the Recovery Storage Group
  - Restoring on Microsoft Server 2007
  - Caveats
- libdbi Framework
- Console Command Additions and Enhancements
  - Display Autochanger Content
  - list joblog job=xxx or jobid=nnn
  - Use separator for multiple commands
  - Deleting Volumes
- Bare Metal Recovery
- Miscellaneous
  - Allow Mixed Priority = yesno
  - Bootstrap File Directive - FileRegex
  - Bootstrap File Optimization Changes
  - Solaris ZFS/NFSv4 ACLs
  - Virtual Tape Emulation
  - Bat Enhancements
  - RunScript Enhancements
  - Status Enhancements
  - Connect Timeout
  - ftruncate for NFS Volumes
  - Support for Ubuntu
  - Recycle Pool = pool-name
  - FD Version
  - Max Run Sched Time = time-period-in-seconds
  - Max Wait Time = time-period-in-seconds
  - Incremental|Differential Max Wait Time = time-period-in-seconds
  - Max Run Time directives
  - Statistics Enhancements
  - ScratchPool = pool-resource-name
  - Enhanced Attribute Despooling
  - SpoolSize = size-specification-in-bytes
  - MaximumConsoleConnections = number
  - VerId = string
  - dbcheck enhancements
  - -docdir configure option
  - -htmldir configure option
  - -with-plugindir configure option

#
New Features in 3.0.0

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.

# 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 (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.

## Accurate = yesno

If the Accurate = yesno directive is enabled (default no) in the Job resource, the job will be run as an Accurate Job. For a Full backup, there is no difference, but for Differential and Incremental 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.

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.

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.

This project was funded by Bacula Systems.

# Copy Jobs

A new Copy 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 restore command lists copy jobs and allows selection of copies by using `jobid=` option. If the keyword copies is present on the command line, Bacula will display the list of all copies for selected jobs.

    * 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.
    ...

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 PoolUncopiedJobs which selects all Jobs that were not already copied to another Pool.

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.

If Bacula finds a Copy of a job record that is purged (deleted) from the catalog, it will promote the Copy to a real 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.

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:

    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
    }

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.

The command `list copies [jobid=x,y,z]` lists copies for a given jobid.

    *list copies
    +-------+------------------------------------+-----------+------------------+
    | JobId | Job                                | CopyJobId | MediaType        |
    +-------+------------------------------------+-----------+------------------+
    |     9 | CopyJobSave.2008-12-20_22.26.49.05 |        11 | DiskChangerMedia |
    +-------+------------------------------------+-----------+------------------+

# ACL Updates

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.

Currently the following platforms support ACLs:

- AIX
- Darwin/OSX
- FreeBSD
- HPUX
- IRIX
- Linux
- Tru64
- Solaris

Currently we support the following ACL types (these ACL streams use a reserved part of the stream numbers):

- STREAM_ACL_AIX_TEXT 1000 AIX specific string representation from acl_get
- STREAM_ACL_DARWIN_ACCESS_ACL 1001 Darwin (OSX) specific acl_t string representation from acl_to_text (POSIX acl)
- STREAM_ACL_FREEBSD_DEFAULT_ACL 1002 FreeBSD specific acl_t string representation from acl_to_text (POSIX acl) for default acls.
- STREAM_ACL_FREEBSD_ACCESS_ACL 1003 FreeBSD specific acl_t string representation from acl_to_text (POSIX acl) for access acls.
- STREAM_ACL_HPUX_ACL_ENTRY 1004 HPUX specific acl_entry string representation from acltostr (POSIX acl)
- STREAM_ACL_IRIX_DEFAULT_ACL 1005 IRIX specific acl_t string representation from acl_to_text (POSIX acl) for default acls.
- STREAM_ACL_IRIX_ACCESS_ACL 1006 IRIX specific acl_t string representation from acl_to_text (POSIX acl) for access acls.
- STREAM_ACL_LINUX_DEFAULT_ACL 1007 Linux specific acl_t string representation from acl_to_text (POSIX acl) for default acls.
- STREAM_ACL_LINUX_ACCESS_ACL 1008 Linux specific acl_t string representation from acl_to_text (POSIX acl) for access acls.
- STREAM_ACL_TRU64_DEFAULT_ACL 1009 Tru64 specific acl_t string representation from acl_to_text (POSIX acl) for default acls.
- STREAM_ACL_TRU64_DEFAULT_DIR_ACL 1010 Tru64 specific acl_t string representation from acl_to_text (POSIX acl) for default acls.
- STREAM_ACL_TRU64_ACCESS_ACL 1011 Tru64 specific acl_t string representation from acl_to_text (POSIX acl) for access acls.
- STREAM_ACL_SOLARIS_ACLENT 1012 Solaris specific aclent_t string representation from acltotext or acl_totext (POSIX acl)
- STREAM_ACL_SOLARIS_ACE 1013 Solaris specific ace_t string representation from from acl_totext (NFSv4 or ZFS acl)

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.

# 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. 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.

Currently the following platforms support extended attributes:

- Darwin/OSX
- FreeBSD
- Linux
- NetBSD

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.

To enable the backup of extended attributes please add the following to your fileset definition.

      FileSet {
        Name = "MyFileSet"
        Include {
          Options {
            signature = MD5
            xattrsupport = yes
          }
          File = ...
        }
      }

# Shared objects

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 libtool so it should be quite portable.

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.

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 ./configure line using the -libdir option as:

      ./configure --libdir=/full-path/dir

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:

    libbaccfg.so
    libbacfind.so
    libbacpy.so
    libbac.so

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).

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:

      ./configure --disable-libtool

# Building Static versions of Bacula

In order to build static versions of Bacula, in addition to configuration options that were needed you now must also add -disable-libtool. Example

      ./configure --enable-static-client-only --disable-libtool

# Virtual Backup (Vbackup)

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.

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 Next Pool 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 Next Pool 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.

The Vbackup is enabled on a Job by Job in the Job resource by specifying a level of VirtualFull.

A typical Job resource definition might look like the following:

    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
    }

Then in bconsole or via a Run schedule, you would run the job as:

    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

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 Default pool.

To consolidate those backups into a new Full backup, you would run the following:

    run job=MyBackup level=VirtualFull

And it would produce a new Full backup without using the client, and the output would be written to the Full Pool which uses the Diskchanger Storage.

If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will fail with an error.

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.

# Catalog Format

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.

# 64 bit Windows Client

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.

Compared to the Win32 Bacula Client, the 64 bit release contains a few differences:

1. 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.
2. Only the Client (File daemon) is ported to Win64, the Director and the Storage daemon are not in the 64 bit Windows installer.
3. bwx-console is not yet ported.
4. bconsole is ported but it has not been tested.
5. The documentation is not included in the installer.
6. 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.
7. 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.
8. All Bacula files are now installed in C:/Program Files/Bacula except the main menu items, which are installed as before. This vastly simplifies the installation.
9. If you are running on a foreign language version of Windows, most likely C:/Program Files does not exist, so you should use the Custom installation and enter an appropriate location to install the files.
10. 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.

This project was funded by Bacula Systems.

# Duplicate Job Control

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.

The four directives each take as an argument a yes or no value and are specified in the Job resource.

They are:

## Allow Duplicate Jobs = yesno

If this directive is set to yes, duplicate jobs will be run. If the directive is set to no (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).

If Allow Duplicate Jobs is set to 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.

## Allow Higher Duplicates = yesno

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).

## Cancel Running Duplicates = yesno

If Allow Duplicate Jobs is set to no and if this directive is set to yes any job that is already running will be canceled. The default is no.

## Cancel Queued Duplicates = yesno

If Allow Duplicate Jobs is set to no and if this directive is set to yes any job that is already queued to run but not yet running will be canceled. The default is no.

# TLS Authentication

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.

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:

## TLS Authenticate = yes

    TLS Authenticate = yes

in the main daemon configuration resource (Director for the Director, Client for the File daemon, and Storage for the Storage daemon).

When TLS Authenticate 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.

If you want to encrypt communications data, use the normal TLS directives but do not turn on TLS Authenticate.

# bextract non-portable Win32 data

bextract 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.

# State File updated at Job Termination

In previous versions of Bacula, the state file, which provides a summary of previous jobs run in the status 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.

# MaxFullInterval = time-interval

The new Job resource directive Max Full Interval = time-interval can be used to specify the maximum time interval between Full 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 Incremental or Differential, it will be automatically upgraded to a Full backup.

# MaxDiffInterval = time-interval

The new Job resource directive Max Diff Interval = time-interval can be used to specify the maximum time interval between Differential 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 Incremental, it will be automatically upgraded to a Differential backup.

# Honor No Dump Flag = yesno

On FreeBSD systems, each file has a no dump flag 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:

      Honor No Dump Flag = yes\vb{}no

The default value is no.

# Exclude Dir Containing = filename-string

The ExcludeDirContaining = filename is a new directive that can be added to the Include section of the FileSet resource. If the specified filename (filename-string) is found on the Client in any directory to be backed up, the whole directory will be ignored (not backed up). For example:

      # List of files to be backed up
      FileSet {
        Name = "MyFileSet"
        Include {
          Options {
            signature = MD5
          }
          File = /home
          Exclude Dir Containing = .excludeme
        }
      }

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 .excludeme in specific directories, such as

       /home/user/www/cache/.excludeme
       /home/user/temp/.excludeme

then Bacula will not backup the two directories named:

       /home/user/www/cache
       /home/user/temp

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).

# Bacula Plugins

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 bpipe that allows an external program to get control to backup and restore a file.

Plugins are also planned (partially implemented) in the Director and the Storage daemon.

## Plugin Directory

Each daemon (DIR, FD, SD) has a new Plugin Directory 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.

## Plugin Options

The Plugin Options 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 bconsole command line prompts.

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).

## Plugin Options ACL

The Plugin Options ACL 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 Plugin Options that overrides the one specified in the Job definition. Without this directive restricted consoles may not modify the Plugin Options.

## Plugin = plugin-command-string

The Plugin directive is specified in the Include section of a FileSet resource where you put your File = xxx directives. For example:

      FileSet {
        Name = "MyFileSet"
        Include {
          Options {
            signature = MD5
          }
          File = /home
          Plugin = "bpipe:..."
        }
      }

In the above example, when the File daemon is processing the directives in the Include section, it will first backup all the files in /home then it will load the plugin named bpipe (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.

Please see the next section for information about the bpipe Bacula plugin.

# The bpipe Plugin

The bpipe 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 bpipe-fd.so. 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.

The purpose of the plugin is to provide an interface to any system program for backup and restore. As specified above the bpipe plugin is specified in the Include section of your Job's FileSet resource. The full syntax of the plugin directive as interpreted by the bpipe plugin (each plugin is free to specify the sytax as it wishes) is:

      Plugin = "<field1>:<field2>:<field3>:<field4>"

where

  field1 is the name of the plugin with the trailing -fd.so stripped off, so in this case, we would put bpipe in this field.

  field2 specifies the namespace, which for bpipe 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 /MYSQL/regress.sql, 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.

  field3 for the bpipe plugin specifies the "reader" program that is called by the plugin during backup to read the data. bpipe will call this program by doing a popen on it.

  field4 for the bpipe plugin specifies the "writer" program that is called by the plugin during restore to write the data back to the filesystem.

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.

Putting it all together, the full plugin directive line might look like the following:

    Plugin = "bpipe:/MYSQL/regress.sql:mysqldump -f
              --opt --databases bacula:mysql"

The directive has been split into two lines, but within the bacula-dir.conf file would be written on a single line.

This causes the File daemon to call the bpipe plugin, which will write its data into the "pseudo" file /MYSQL/regress.sql by calling the program mysqldump -f -opt -database bacula to read the data during backup. The mysqldump command outputs all the data for the database named bacula, 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 mysql. When mysql 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 (bacula in this case).

The bpipe 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.

By using different command lines to bpipe, you can backup any kind of data (ASCII or binary) depending on the program called.

# Microsoft Exchange Server 2003/2007 Plugin

## Background

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.

## Concepts

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.

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.

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.

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).

## Installing

The Exchange plugin requires a DLL that is shipped with Microsoft Exchanger Server called esebcli2.dll. Assuming Exchange is installed correctly the Exchange plugin should find this automatically and run without any additional installation.

If the DLL can not be found automatically it will need to be copied into the Bacula installation directory (eg C:`\`Program Files`\`Bacula`\`bin). The Exchange API DLL is named esebcli2.dll and is found in C:`\`Program Files`\`Exchsrvr`\`bin on a default Exchange installation.

## Backing Up

To back up an Exchange server the Fileset definition must contain at least Plugin = "exchange:/@EXCHANGE/Microsoft Information Store" 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
Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"
if you want only a single storage group backed up.

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.

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.

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.

    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
       }
    }

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.

## Restoring

The restore operation is much the same as a normal Bacula restore, with the following provisos:

- The Where restore option must not be specified
- Each Database directory must be marked as a whole. You cannot just select (say) the .edb file and not the others.
- If a Storage Group is restored, the directory of the Storage Group must be marked too.
- It is possible to restore only a subset of the available log files, but they must be contiguous. Exchange will fail to restore correctly if a log file is missing from the sequence of log files
- Each database to be restored must be dismounted and marked as "Can be overwritten by restore"
- 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:`\`Program Files`\`Exchsrvr`\`mdbdata`\`*) as Exchange can get confused by stray log files lying around.

## Restoring to the Recovery Storage Group

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...

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.

To create the Recovery Storage Group, drill down to the Server in Exchange System Manager, right click, and select "New -> Recovery Storage Group...". Accept or change the file locations and click OK. On the Recovery Storage Group, right click and select "Add Database to Recover..." and select the database you will be restoring.

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.

## Restoring on Microsoft Server 2007

Apparently the 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: http://technet.microsoft.com/en-us/library/aa997694.aspxhttp://technet.microsoft.com/en-us/library/aa997694.aspx, and involves using the Restore-Mailbox and Get-MailboxStatistics shell commands.

## Caveats

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.

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.

The "Enable Circular Logging" option cannot be enabled or the plugin will fail.

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.

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.

The Exchange plugin has not been tested with the Accurate option, so we recommend either carefully testing or that you avoid this option for the current time.

The Exchange plugin is not called during processing the bconsole estimate command, and so anything that would be backed up by the plugin will not be added to the estimate total that is displayed.

# libdbi Framework

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.

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.

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.

Some of benefits of using libdbi are:

- The possibility to use proprietary databases engines in which your proprietary licenses prevent the Bacula team from developing the driver.
- The possibility to use the drivers written for the libdbi project.
- The possibility to use other database engines without recompiling Bacula to use them. Just change one line in bacula-dir.conf
- Abstract Database access, this is, unique point to code and profiling catalog database access.

The following drivers have been tested:

- PostgreSQL, with and without batch insert
- Mysql, with and without batch insert
- SQLite
- SQLite3

In the future, we will test and approve to use others databases engines (proprietary or not) like DB2, Oracle, Microsoft SQL.

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.

The next phase is checking (or configuring) the bacula-dir.conf, example:

    Catalog {
      Name = MyCatalog
      dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
      dbname = regress; user = regress; password = ""
    }

The parameter dbdriver 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:".

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.

It is important to remember, when compiling Bacula with libdbi, the following packages are needed:

- libdbi version 1.0.0, http://libdbi.sourceforge.net/
- libdbi-drivers 1.0.0, http://libdbi-drivers.sourceforge.net/

You can download them and compile them on your system or install the packages from your OS distribution.

# Console Command Additions and Enhancements

## Display Autochanger Content

The status slots storage=storage-name command displays autochanger content.

     Slot |  Volume Name  |  Status  |  Media Type       |   Pool     |
    ------+---------------+----------+-------------------+------------|
        1 |         00001 |   Append |  DiskChangerMedia |    Default |
        2 |         00002 |   Append |  DiskChangerMedia |    Default |
        3*|         00003 |   Append |  DiskChangerMedia |    Scratch |
        4 |               |          |                   |            |

If you an asterisk (*) appears after the slot number, you must run an update slots command to synchronize autochanger content with your catalog.

## list joblog job=xxx or jobid=nnn

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 llist command will include a line with the time and date of the entry.

Note for the catalog to have Job Log entries, you must have a directive such as:

      catalog = all

In your Director's Messages resource.

## Use separator for multiple commands

When using bconsole with readline, you can set the command separator with @separator command to one of those characters to write commands who require multiple input in one line.

      !$%&'()*+,-/:;<>?[]^`{|}~

## Deleting Volumes

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.

This new behavior is indicated in the prompt if you read it carefully.

# Bare Metal Recovery

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.

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.

Advantages:

1. Recovery can be done from within graphical environment.
2. Recovery can be done in a shell.
3. Ubuntu boots on a large number of Linux systems.
4. The process of updating the system and adding new packages is not too difficult.
5. The USB key can easily be upgraded to newer Ubuntu versions.
6. The USB key has writable partitions for modifications to the OS and for modification to your home directory.
7. You can add new files/directories to the USB key very easily.
8. You can save the environment from multiple machines on one USB key.
9. Bacula Systems is funding its ongoing development.

The disadvantages are:

1. The USB key is usable but currently under development.
2. Not everyone may be familiar with Ubuntu (no worse than using Knoppix)
3. Some older OSes cannot be booted from USB. This can be resolved by first booting a Ubuntu LiveCD then plugging in the USB key.
4. Currently the documentation is sketchy and not yet added to the main manual. See below ...

The documentation and the code can be found in the rescue package in the directory linux/usb.

# Miscellaneous

## Allow Mixed Priority = yesno

This directive is only implemented in version 2.5 and later. When set to yes (default no), 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.

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.

## Bootstrap File Directive - FileRegex

FileRegex 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.

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.

      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

## Bootstrap File Optimization Changes

In order to permit proper seeking on disk files, we have extended the bootstrap file format to include a VolStartAddr and VolEndAddr 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 VolStartFile, VolEndFile, VolStartBlock and VolEndBlock 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.

## Solaris ZFS/NFSv4 ACLs

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.

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.

## Virtual Tape Emulation

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 disk-changer 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 Device Type = vtape in the Storage daemon's Device directive. This feature is only implemented on Linux machines and should not be used for production.

## Bat Enhancements

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.

The Bat communications protocol has been significantly enhanced to improve GUI handling. Note, you must use a the bat that is distributed with the Director you are using otherwise the communications protocol will not work.

## RunScript Enhancements

The RunScript resource has been enhanced to permit multiple commands per RunScript. Simply specify multiple Command directives in your RunScript.

    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
      }
     ...
    }

A new Client RunScript RunsWhen keyword of AfterVSS has been implemented, which runs the command after the Volume Shadow Copy has been made.

Console commands can be specified within a RunScript by using: Console = command, 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.

## Status Enhancements

The bconsole status dir output has been enhanced to indicate Storage daemon job spooling and despooling activity.

## Connect Timeout

The default connect timeout to the File daemon has been set to 3 minutes. Previously it was 30 minutes.

## ftruncate for NFS Volumes

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.

## Support for Ubuntu

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.

## Recycle Pool = pool-name

The new RecyclePool 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.

## FD Version

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.

## Max Run Sched Time = time-period-in-seconds

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 `Max Start Delay + Max Run Time`.

## Max Wait Time = time-period-in-seconds

Previous MaxWaitTime 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 MaxRunTime. Some users are reporting to use Incr/Diff/Full Max Wait Time to control the maximum run time of their job depending on the level. Now, they have to use Incr/Diff/Full Max Run Time. Incr/Diff/Full Max Wait Time directives are now deprecated.

## Incremental|Differential Max Wait Time = time-period-in-seconds

These directives have been deprecated in favor of `Incremental|Differential Max Run Time`.

## Max Run Time directives

Using Full/Diff/Incr Max Run Time, it's now possible to specify the maximum allowed time that a job can run depending on the level.

## Statistics Enhancements

If you (or probably your boss) want to have statistics on your backups to provide some Service Level Agreement indicators, you could use a few SQL queries on the Job table to report how many:

- jobs have run
- jobs have been successful
- files have been backed up
- ...

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.

Now, you can use the update stats [days=num] console command to fill the JobHistory table with new Job records. If you want to be sure to take in account only good jobs, 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 bad 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 [days=num] option.

These statistics records aren't used for restoring, but mainly for capacity planning, billings, etc.

The Bweb interface provides a statistics module that can use this feature. You can also use tools like Talend or extract information by yourself.

The Statistics Retention = time director directive defines the length of time that Bacula will keep statistics job records in the Catalog database after the Job End time. (In `JobHistory` table) When this time period expires, and if user runs `prune stats` command, Bacula will prune (remove) Job records that are older than the specified period.

You can use the following Job resource in your nightly BackupCatalog job to maintain statistics.

    Job {
      Name = BackupCatalog
      ...
      RunScript {
        Console = "update stats days=3"
        Console = "prune stats yes"
        RunsWhen = After
        RunsOnClient = no
      }
    }

## ScratchPool = pool-resource-name

This directive permits to specify a specific Scratch 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.

## Enhanced Attribute Despooling

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.

## SpoolSize = size-specification-in-bytes

A new Job directive permits to specify the spool size per job. This is used in advanced job tunning. SpoolSize=bytes

## MaximumConsoleConnections = number

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.

## VerId = string

A new director directive permits to specify a personnal identifier that will be displayed in the `version` command.

## dbcheck enhancements

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.

A new `-B` option allows you to print catalog information in a simple text based format. This is useful to backup it in a secure way.

     $ dbcheck -B
     catalog=MyCatalog
     db_type=SQLite
     db_name=regress
     db_driver=
     db_user=regress
     db_password=
     db_address=
     db_port=0
     db_socket=

You can now specify the database connection port in the command line.

## -docdir configure option

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 /usr/share/doc/bacula.

## -htmldir configure option

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 /usr/share/doc/bacula/html

## -with-plugindir configure option

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.