1 \chapter{New Features in 3.1.4 (Development Version)}
2 \label{NewFeaturesChapter}
4 This chapter presents the new features that are currently under development
5 in the 3.1.x versions to be released as Bacula version 5.0.0 sometime in
6 late 2009 or early 2010.
8 \section{Truncate volume after purge}
9 \label{sec:actiononpurge}
11 The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate
12 the volume when it is purged. It is useful to prevent disk based volumes from
13 consuming too much space.
18 Action On Purge = Truncate
23 \section{Maximum Concurent Jobs for Devices}
24 \label{sec:maximumconcurentjobdevice}
26 {\bf Maximum Concurrent Jobs} is a new Device directive in the Storage
27 Daemon configuration permits setting the maximum number of Jobs that can
28 run concurrently on a specified Device. Using this directive, it is
29 possible to have different Jobs using multiple drives, because when the
30 Maximum Concurrent Jobs limit is reached, the Storage Daemon will start new
31 Jobs on any other available compatible drive. This facilitates writing to
32 multiple drives with multiple Jobs that all use the same Pool.
34 This project was funded by Bacula Systems.
36 \section{Restore from Multiple Storage Daemons}
37 \index[general]{Restore}
39 Previously, you were able to restore from multiple devices in a single Storage
40 Daemon. Now, Bacula is able to restore from multiple Storage Daemons. For
41 example, if your full backup runs on a Storage Daemon with an autochanger, and
42 your incremental jobs use another Storage Daemon with lots of disks, Bacula
43 will switch automatically from one Storage Daemon to an other within the same
46 You must upgrade your File Daemon to version 3.1.3 or greater to use this
49 This project was funded by Bacula Systems with the help of Equiinet.
51 \section{File Deduplication using Base Jobs}
52 A base job is sort of like a Full save except that you will want the FileSet to
53 contain only files that are unlikely to change in the future (i.e. a snapshot
54 of most of your system after installing it). After the base job has been run,
55 when you are doing a Full save, you specify one or more Base jobs to be used.
56 All files that have been backed up in the Base job/jobs but not modified will
57 then be excluded from the backup. During a restore, the Base jobs will be
58 automatically pulled in where necessary.
60 This is something none of the competition does, as far as we know (except
61 perhaps BackupPC, which is a Perl program that saves to disk only). It is big
62 win for the user, it makes Bacula stand out as offering a unique optimization
63 that immediately saves time and money. Basically, imagine that you have 100
64 nearly identical Windows or Linux machine containing the OS and user files.
65 Now for the OS part, a Base job will be backed up once, and rather than making
66 100 copies of the OS, there will be only one. If one or more of the systems
67 have some files updated, no problem, they will be automatically restored.
69 A new Job directive \texttt{Base=Jobx, Joby...} permits to specify the list of
70 files that will be used during Full backup as base.
81 Base = BackupZog4, BackupLinux
87 In this example, the job \texttt{BackupZog4} will use the most recent version
88 of all files contained in \texttt{BackupZog4} and \texttt{BackupLinux}
89 jobs. Base jobs should have run with \texttt{level=Base} to be used.
91 By default, Bacula will compare permissions bits, user and group fields,
92 modification time, size and the checksum of the file to choose between the
93 current backup and the BaseJob file list. You can change this behavior with the
94 \texttt{BaseJob} FileSet option. This option works like the \texttt{verify=}
95 one, that is described in the \ilink{FileSet}{FileSetResource} chapter.
112 This project was funded by Bacula Systems.
114 \section{AllowCompression = \lt{}yes\vb{}no\gt{}}
115 \index[dir]{AllowCompression}
117 This new directive may be added to Storage resource within the Director's
118 configuration to allow users to selectively disable the client compression for
119 any job which writes to this storage resource.
125 Address = ultrium-tape
126 Password = storage_password # Password for Storage Daemon
129 AllowCompression = No # Tape drive has hardware compression
132 The above example would cause any jobs running with the UltriumTape storage
133 resource to run without compression from the client file daemons. This
134 effectively overrides any compression settings defined at the FileSet level.
136 This feature is probably most useful if you have a tape drive which supports
137 hardware compression. By setting the \texttt{AllowCompression = No} directive
138 for your tape drive storage resource, you can avoid additional load on the file
139 daemon and possibly speed up tape backups.
141 This project was funded by Collaborative Fusion, Inc.
143 \section{Accurate Fileset Options}
144 \label{sec:accuratefileset}
146 In previous versions, the accurate code used the file creation and modification
147 times to determine if a file was modified or not. Now you can specify which
148 attributes to use (time, size, checksum, permission, owner, group, \dots),
149 similar to the Verify options.
165 \item {\bf i} compare the inodes
166 \item {\bf p} compare the permission bits
167 \item {\bf n} compare the number of links
168 \item {\bf u} compare the user id
169 \item {\bf g} compare the group id
170 \item {\bf s} compare the size
171 \item {\bf a} compare the access time
172 \item {\bf m} compare the modification time (st\_mtime)
173 \item {\bf c} compare the change time (st\_ctime)
174 \item {\bf d} report file size decreases
175 \item {\bf 5} compare the MD5 signature
176 \item {\bf 1} compare the SHA1 signature
179 \textbf{Important note:} If you decide to use checksum in Accurate jobs,
180 the File Daemon will have to read all files even if they normally would not
181 be saved. This increases the I/O load, but also the accuracy of the
182 deduplication. By default, Bacula will check modification/creation time
185 This project was funded by Bacula Systems.
187 \section{Tab-completion for Bconsole}
188 \label{sec:tabcompletion}
190 If you build \texttt{bconsole} with readline support, you will be able to use
191 the new auto-completion mode. This mode supports all commands, gives help
192 inside command, and lists resources when required. It works also in the restore
195 To use this feature, you should have readline development package loaded on
196 your system, and use the following option in configure.
198 ./configure --with-readline=/usr/include/readline --disable-conio ...
201 The new bconsole won't be able to tab-complete with older directors.
203 This project was funded by Bacula Systems.
205 \section{Pool File and Job retention}
206 \label{sec:poolfilejobretention}
209 We added two new Pool directives, \texttt{FileRetention} and
210 \texttt{JobRetention}, that take precedence over Client directives of the same
211 name. It allows you to control the Catalog pruning algorithm Pool by Pool. For
212 example, you can decide to increase Retention times for Archive or OffSite Pool.
214 \section{Read-only File Daemon using capabilities}
215 \label{sec:fdreadonly}
216 This feature implements support of keeping \textbf{ReadAll} capabilities after
217 UID/GID switch, this allows FD to keep root read but drop write permission.
219 It introduces new \texttt{bacula-fd} option (\texttt{-k}) specifying that
220 \textbf{ReadAll} capabilities should be kept after UID/GID switch.
223 root@localhost:~# bacula-fd -k -u nobody -g nobody
226 The code for this feature was contributed by AltLinux.
231 To help developers of restore GUI interfaces, we have added new \textsl{dot
232 commands} that permit browsing the catalog in a very simple way.
235 \item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update
236 the Bvfs cache in the catalog. You need to run it before any access to the
239 \item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command
240 will list all directories in the specified \texttt{path} or
241 \texttt{pathid}. Using \texttt{pathid} avoids problems with character
242 encoding of path/filenames.
244 \item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command
245 will list all files in the specified \texttt{path} or \texttt{pathid}. Using
246 \texttt{pathid} avoids problems with character encoding.
249 You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of
250 data that will be displayed.
253 * .bvfs_update jobid=1,2
255 * .bvfs_lsdir path=/ jobid=1,2
258 This project was funded by Bacula Systems.
260 \section{Testing your Tape Drive}
261 \label{sec:btapespeed}
263 To determine the best configuration of your tape drive, you can run the new
264 \texttt{speed} command available in the \texttt{btape} program.
266 This command can have the following arguments:
268 \item[\texttt{file\_size=n}] Specify the Maximum File Size for this test
269 (between 1 and 5GB). This counter is in GB.
270 \item[\texttt{nb\_file=n}] Specify the number of file to be written. The amount
271 of data should be greater than your memory ($file\_size*nb\_file$).
272 \item[\texttt{skip\_zero}] This flag permits to skip tests with constant
274 \item[\texttt{skip\_random}] This flag permits to skip tests with random
276 \item[\texttt{skip\_raw}] This flag permits to skip tests with raw access.
277 \item[\texttt{skip\_block}] This flag permits to skip tests with Bacula block
282 *speed file_size=3 skip_raw
283 btape.c:1078 Test with zero data and bacula block structure.
284 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
285 ++++++++++++++++++++++++++++++++++++++++++
286 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
287 btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 MB/s
289 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 MB/s
291 btape.c:1090 Test with random data, should give the minimum throughput.
292 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
293 +++++++++++++++++++++++++++++++++++++++++++
294 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
295 btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 MB/s
296 +++++++++++++++++++++++++++++++++++++++++++
298 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s
302 When using compression, the random test will give your the minimum throughput
303 of your drive . The test using constant string will give you the maximum speed
304 of your hardware chain. (cpu, memory, scsi card, cable, drive, tape).
306 You can change the block size in the Storage Daemon configuration file.
308 \section{New {\bf Block Checksum} Device Directive}
309 You may now turn off the Block Checksum (CRC32) code
310 that Bacula uses when writing blocks to a Volume. This is
317 doing so can reduce the Storage daemon CPU usage slightly. It
318 will also permit Bacula to read a Volume that has corrupted data.
320 The default is {\bf yes} -- i.e. the checksum is computed on write
323 We do not recommend to turn this off particularly on older tape
324 drives or for disk Volumes where doing so may allow corrupted data
327 \section{New Bat Features}
329 Those new features were funded by Bacula Systems.
331 \subsection{Media List View}
333 By clicking on ``Media'', you can see the list of all your volumes. You will be
334 able to filter by Pool, Media Type, Location,\dots And sort the result directly
335 in the table. The old ``Media'' view is now known as ``Pool''.
338 \includegraphics[width=13cm]{\idir bat-mediaview.eps}
339 \label{fig:mediaview}
343 \subsection{Media Information View}
345 By double-clicking on a volume (on the Media list, in the Autochanger content
346 or in the Job information panel), you can access a detailed overview of your
347 Volume. (cf \ref{fig:mediainfo}.)
350 \includegraphics[width=13cm]{\idir bat11.eps}
351 \caption{Media information}
352 \label{fig:mediainfo}
355 \subsection{Job Information View}
357 By double-clicking on a Job record (on the Job run list or in the Media
358 information panel), you can access a detailed overview of your Job. (cf
362 \includegraphics[width=13cm]{\idir bat12.eps}
363 \caption{Job information}
367 \subsection{Autochanger Content View}
369 By double-clicking on a Storage record (on the Storage list panel), you can
370 access a detailed overview of your Autochanger. (cf \ref{fig:jobinfo}.)
373 \includegraphics[width=13cm]{\idir bat13.eps}
374 \caption{Autochanger content}
375 \label{fig:achcontent}
378 To use this feature, you need to use the latest mtx-changer script
379 version. (With new \texttt{listall} and \texttt{transfer} commands)
381 \subsection{Win32 version}
383 Compilation instructions are available in \texttt{src/qt-console/README.mingw32}
385 \section{Console Timeout Option}
386 You can now use the -u option of bconsole to set a timeout for each command.
388 \section{Important behavior changes}
389 \label{sec:importantchanges}
392 \item You are now allowed to Migrate, Copy, and Virtual Full to read and write
394 \item The \texttt{Device Poll Interval} is now 5 minutes. (previously did not
396 \item The new \texttt{mtx-changer} script has two new options, \texttt{listall}
397 and \texttt{transfer}. Be sure to report your custom changes on it to be able
398 to use new functions.
399 \item To enhance security in the \texttt{BackupCatalog} job, we provide a new
400 script (\texttt{make\_catalog\_backup.pl}) that no longer expose your catalog
401 password. If you want to use the new version after an upgrade, you need to
402 manually change the \texttt{BackupCatalog} job definition.
403 \item The new \texttt{bconsole} \texttt{help} command can take now
404 the command that you want to explain as argument. (ex: \texttt{help run})
407 \subsection{Custom Catalog queries}
409 If you wish to add specialized commands that list the contents of the catalog,
410 you can do so by adding them to the \texttt{query.sql} file. This
411 \texttt{query.sql} file is now empty by default, and you can copy and past
412 examples from \texttt{examples/sample-query.sql} file.
414 \subsection{Deprecated parts}
416 The following items are \textbf{deprecated} for a long time, and are now
417 removed from the code.
420 \item Support for SQLite 2
423 \section{Misc changes}
424 \label{sec:miscchanges}
427 \item Updated Nagios check\_bacula
428 \item Updated man files
429 \item Added OSX package generation scripts
430 \item Added Spanish and Ukrainian Bacula translation
431 \item Enable/disable command shows only Jobs that can change
432 \item Added \texttt{show disabled} command to show disabled Jobs
433 \item Many ACL improvements
434 \item Added Level to FD status Job entry
435 \item Begin Ingres DB driver (not yet working)
436 \item Splited RedHat spec files into bacula, bat, mtx, and docs
437 \item Reorganized the manuals (fewer separate manuals)
438 \item Added lock/unlock order protection in lock manager
439 \item Allow 64 bit sizes for a number of variables
440 \item Fixed several deadlocks or potential race conditions from SD
443 \chapter{Released Version 3.0.3 and 3.0.3a}
445 There are no new features. This version simply fixes a number of bugs found in
446 version 3.0.2 during the onging development process.
448 \chapter{New Features in Released Version 3.0.2}
450 This chapter presents the new features added to the
451 Released Bacula Version 3.0.2.
453 \section{Full Restore from a Given JobId}
454 \index[general]{Restore menu}
456 This feature allows selecting a single JobId and having Bacula
457 automatically select all the other jobs that comprise a full backup up to
458 and including the selected date (through JobId).
460 Assume we start with the following jobs:
462 +-------+--------------+---------------------+-------+----------+------------+
463 | jobid | client | starttime | level | jobfiles | jobbytes |
464 +-------+--------------+---------------------+-------+----------+------------
465 | 6 | localhost-fd | 2009-07-15 11:45:49 | I | 2 | 0 |
466 | 5 | localhost-fd | 2009-07-15 11:45:45 | I | 15 | 44143 |
467 | 3 | localhost-fd | 2009-07-15 11:45:38 | I | 1 | 10 |
468 | 1 | localhost-fd | 2009-07-15 11:45:30 | F | 1527 | 44143073 |
469 +-------+--------------+---------------------+-------+----------+------------+
472 Below is an example of this new feature (which is number 12 in the
477 To select the JobIds, you have the following choices:
478 1: List last 20 Jobs run
479 2: List Jobs where a given File is saved
481 12: Select full restore to a specified Job date
484 Select item: (1-13): 12
485 Enter JobId to get the state to restore: 5
486 Selecting jobs to build the Full state at 2009-07-15 11:45:45
487 You have selected the following JobIds: 1,3,5
489 Building directory tree for JobId(s) 1,3,5 ... +++++++++++++++++++
490 1,444 files inserted into the tree.
493 This project was funded by Bacula Systems.
495 \section{Source Address}
496 \index[general]{Source Address}
498 A feature has been added which allows the administrator to specify the address
499 from which the Director and File daemons will establish connections. This
500 may be used to simplify system configuration overhead when working in complex
501 networks utilizing multi-homing and policy-routing.
503 To accomplish this, two new configuration directives have been implemented:
506 FDSourceAddress=10.0.1.20 # Always initiate connections from this address
510 DirSourceAddress=10.0.1.10 # Always initiate connections from this address
514 Simply adding specific host routes on the OS
515 would have an undesirable side-effect: any
516 application trying to contact the destination host would be forced to use the
517 more specific route possibly diverting management traffic onto a backup VLAN.
518 Instead of adding host routes for each client connected to a multi-homed backup
519 server (for example where there are management and backup VLANs), one can
520 use the new directives to specify a specific source address at the application
523 Additionally, this allows the simplification and abstraction of firewall rules
524 when dealing with a Hot-Standby director or storage daemon configuration. The
525 Hot-standby pair may share a CARP address, which connections must be sourced
526 from, while system services listen and act from the unique interface addresses.
528 This project was funded by Collaborative Fusion, Inc.
530 \section{Show volume availability when doing restore}
532 When doing a restore the selection dialog ends by displaying this
536 The job will require the following
537 Volume(s) Storage(s) SD Device(s)
538 ===========================================================================
549 Volumes marked with ``*'' are online (in the autochanger).
552 This should help speed up large restores by minimizing the time spent
553 waiting for the operator to discover that he must change tapes in the library.
555 This project was funded by Bacula Systems.
557 \section{Accurate estimate command}
559 The \texttt{estimate} command can now use the accurate code to detect changes
560 and give a better estimation.
562 You can set the accurate behavior on the command line by using
563 \texttt{accurate=yes\vb{}no} or use the Job setting as default value.
566 * estimate listing accurate=yes level=incremental job=BackupJob
569 This project was funded by Bacula Systems.
571 \chapter{New Features in 3.0.0}
572 \label{NewFeaturesChapter}
573 \index[general]{New Features}
575 This chapter presents the new features added to the development 2.5.x
576 versions to be released as Bacula version 3.0.0 sometime in April 2009.
578 \section{Accurate Backup}
579 \index[general]{Accurate Backup}
581 As with most other backup programs, by default Bacula decides what files to
582 backup for Incremental and Differental backup by comparing the change
583 (st\_ctime) and modification (st\_mtime) times of the file to the time the last
584 backup completed. If one of those two times is later than the last backup
585 time, then the file will be backed up. This does not, however, permit tracking
586 what files have been deleted and will miss any file with an old time that may
587 have been restored to or moved onto the client filesystem.
589 \subsection{Accurate = \lt{}yes\vb{}no\gt{}}
590 If the {\bf Accurate = \lt{}yes\vb{}no\gt{}} directive is enabled (default no) in
591 the Job resource, the job will be run as an Accurate Job. For a {\bf Full}
592 backup, there is no difference, but for {\bf Differential} and {\bf
593 Incremental} backups, the Director will send a list of all previous files
594 backed up, and the File daemon will use that list to determine if any new files
595 have been added or or moved and if any files have been deleted. This allows
596 Bacula to make an accurate backup of your system to that point in time so that
597 if you do a restore, it will restore your system exactly.
600 about using Accurate backup is that it requires more resources (CPU and memory)
601 on both the Director and the Client machines to create the list of previous
602 files backed up, to send that list to the File daemon, for the File daemon to
603 keep the list (possibly very big) in memory, and for the File daemon to do
604 comparisons between every file in the FileSet and the list. In particular,
605 if your client has lots of files (more than a few million), you will need
606 lots of memory on the client machine.
608 Accurate must not be enabled when backing up with a plugin that is not
609 specially designed to work with Accurate. If you enable it, your restores
610 will probably not work correctly.
612 This project was funded by Bacula Systems.
617 \index[general]{Copy Jobs}
619 A new {\bf Copy} job type 'C' has been implemented. It is similar to the
620 existing Migration feature with the exception that the Job that is copied is
621 left unchanged. This essentially creates two identical copies of the same
622 backup. However, the copy is treated as a copy rather than a backup job, and
623 hence is not directly available for restore. The {\bf restore} command lists
624 copy jobs and allows selection of copies by using \texttt{jobid=}
625 option. If the keyword {\bf copies} is present on the command line, Bacula will
626 display the list of all copies for selected jobs.
631 These JobIds have copies as follows:
632 +-------+------------------------------------+-----------+------------------+
633 | JobId | Job | CopyJobId | MediaType |
634 +-------+------------------------------------+-----------+------------------+
635 | 2 | CopyJobSave.2009-02-17_16.31.00.11 | 7 | DiskChangerMedia |
636 +-------+------------------------------------+-----------+------------------+
637 +-------+-------+----------+----------+---------------------+------------------+
638 | JobId | Level | JobFiles | JobBytes | StartTime | VolumeName |
639 +-------+-------+----------+----------+---------------------+------------------+
640 | 19 | F | 6274 | 76565018 | 2009-02-17 16:30:45 | ChangerVolume002 |
641 | 2 | I | 1 | 5 | 2009-02-17 16:30:51 | FileVolume001 |
642 +-------+-------+----------+----------+---------------------+------------------+
643 You have selected the following JobIds: 19,2
645 Building directory tree for JobId(s) 19,2 ... ++++++++++++++++++++++++++++++++++++++++++++
646 5,611 files inserted into the tree.
651 The Copy Job runs without using the File daemon by copying the data from the
652 old backup Volume to a different Volume in a different Pool. See the Migration
653 documentation for additional details. For copy Jobs there is a new selection
654 directive named {\bf PoolUncopiedJobs} which selects all Jobs that were
655 not already copied to another Pool.
657 As with Migration, the Client, Volume, Job, or SQL query, are
658 other possible ways of selecting the Jobs to be copied. Selection
659 types like SmallestVolume, OldestVolume, PoolOccupancy and PoolTime also
660 work, but are probably more suited for Migration Jobs.
662 If Bacula finds a Copy of a job record that is purged (deleted) from the catalog,
663 it will promote the Copy to a \textsl{real} backup job and will make it available for
664 automatic restore. If more than one Copy is available, it will promote the copy
665 with the smallest JobId.
667 A nice solution which can be built with the new Copy feature is often
668 called disk-to-disk-to-tape backup (DTDTT). A sample config could
669 look something like the one below:
673 Name = FullBackupsVirtualPool
675 Purge Oldest Volume = Yes
677 NextPool = FullBackupsTapePool
681 Name = FullBackupsTapePool
685 Volume Retention = 365 days
686 Storage = superloader
690 # Fake fileset for copy jobs
702 # Fake client for copy jobs
712 # Default template for a CopyDiskToTape Job
715 Name = CopyDiskToTape
717 Messages = StandardCopy
720 Selection Type = PoolUncopiedJobs
721 Maximum Concurrent Jobs = 10
723 Allow Duplicate Jobs = Yes
724 Allow Higher Duplicates = No
725 Cancel Queued Duplicates = No
726 Cancel Running Duplicates = No
731 Name = DaySchedule7:00
732 Run = Level=Full daily at 7:00
736 Name = CopyDiskToTapeFullBackups
738 Schedule = DaySchedule7:00
739 Pool = FullBackupsVirtualPool
740 JobDefs = CopyDiskToTape
744 The example above had 2 pool which are copied using the PoolUncopiedJobs
745 selection criteria. Normal Full backups go to the Virtual pool and are copied
746 to the Tape pool the next morning.
748 The command \texttt{list copies [jobid=x,y,z]} lists copies for a given
753 +-------+------------------------------------+-----------+------------------+
754 | JobId | Job | CopyJobId | MediaType |
755 +-------+------------------------------------+-----------+------------------+
756 | 9 | CopyJobSave.2008-12-20_22.26.49.05 | 11 | DiskChangerMedia |
757 +-------+------------------------------------+-----------+------------------+
760 \section{ACL Updates}
761 \index[general]{ACL Updates}
762 The whole ACL code had been overhauled and in this version each platforms has
763 different streams for each type of acl available on such an platform. As ACLs
764 between platforms tend to be not that portable (most implement POSIX acls but
765 some use an other draft or a completely different format) we currently only
766 allow certain platform specific ACL streams to be decoded and restored on the
767 same platform that they were created on. The old code allowed to restore ACL
768 cross platform but the comments already mention that not being to wise. For
769 backward compatability the new code will accept the two old ACL streams and
770 handle those with the platform specific handler. But for all new backups it
771 will save the ACLs using the new streams.
773 Currently the following platforms support ACLs:
777 \item {\bf Darwin/OSX}
786 Currently we support the following ACL types (these ACL streams use a reserved
787 part of the stream numbers):
790 \item {\bf STREAM\_ACL\_AIX\_TEXT} 1000 AIX specific string representation from
792 \item {\bf STREAM\_ACL\_DARWIN\_ACCESS\_ACL} 1001 Darwin (OSX) specific acl\_t
793 string representation from acl\_to\_text (POSIX acl)
794 \item {\bf STREAM\_ACL\_FREEBSD\_DEFAULT\_ACL} 1002 FreeBSD specific acl\_t
795 string representation from acl\_to\_text (POSIX acl) for default acls.
796 \item {\bf STREAM\_ACL\_FREEBSD\_ACCESS\_ACL} 1003 FreeBSD specific acl\_t
797 string representation from acl\_to\_text (POSIX acl) for access acls.
798 \item {\bf STREAM\_ACL\_HPUX\_ACL\_ENTRY} 1004 HPUX specific acl\_entry
799 string representation from acltostr (POSIX acl)
800 \item {\bf STREAM\_ACL\_IRIX\_DEFAULT\_ACL} 1005 IRIX specific acl\_t string
801 representation from acl\_to\_text (POSIX acl) for default acls.
802 \item {\bf STREAM\_ACL\_IRIX\_ACCESS\_ACL} 1006 IRIX specific acl\_t string
803 representation from acl\_to\_text (POSIX acl) for access acls.
804 \item {\bf STREAM\_ACL\_LINUX\_DEFAULT\_ACL} 1007 Linux specific acl\_t
805 string representation from acl\_to\_text (POSIX acl) for default acls.
806 \item {\bf STREAM\_ACL\_LINUX\_ACCESS\_ACL} 1008 Linux specific acl\_t string
807 representation from acl\_to\_text (POSIX acl) for access acls.
808 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_ACL} 1009 Tru64 specific acl\_t
809 string representation from acl\_to\_text (POSIX acl) for default acls.
810 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_DIR\_ACL} 1010 Tru64 specific acl\_t
811 string representation from acl\_to\_text (POSIX acl) for default acls.
812 \item {\bf STREAM\_ACL\_TRU64\_ACCESS\_ACL} 1011 Tru64 specific acl\_t string
813 representation from acl\_to\_text (POSIX acl) for access acls.
814 \item {\bf STREAM\_ACL\_SOLARIS\_ACLENT} 1012 Solaris specific aclent\_t
815 string representation from acltotext or acl\_totext (POSIX acl)
816 \item {\bf STREAM\_ACL\_SOLARIS\_ACE} 1013 Solaris specific ace\_t string
817 representation from from acl\_totext (NFSv4 or ZFS acl)
820 In future versions we might support conversion functions from one type of acl
821 into an other for types that are either the same or easily convertable. For now
822 the streams are seperate and restoring them on a platform that doesn't
823 recognize them will give you a warning.
825 \section{Extended Attributes}
826 \index[general]{Extended Attributes}
827 Something that was on the project list for some time is now implemented for
828 platforms that support a similar kind of interface. Its the support for backup
829 and restore of so called extended attributes. As extended attributes are so
830 platform specific these attributes are saved in seperate streams for each
831 platform. Restores of the extended attributes can only be performed on the
832 same platform the backup was done. There is support for all types of extended
833 attributes, but restoring from one type of filesystem onto an other type of
834 filesystem on the same platform may lead to supprises. As extended attributes
835 can contain any type of data they are stored as a series of so called
836 value-pairs. This data must be seen as mostly binary and is stored as such.
837 As security labels from selinux are also extended attributes this option also
838 stores those labels and no specific code is enabled for handling selinux
841 Currently the following platforms support extended attributes:
843 \item {\bf Darwin/OSX}
849 On linux acls are also extended attributes, as such when you enable ACLs on a
850 Linux platform it will NOT save the same data twice e.g. it will save the ACLs
851 and not the same exteneded attribute.
853 To enable the backup of extended attributes please add the following to your
868 \section{Shared objects}
869 \index[general]{Shared objects}
870 A default build of Bacula will now create the libraries as shared objects
871 (.so) rather than static libraries as was previously the case.
872 The shared libraries are built using {\bf libtool} so it should be quite
875 An important advantage of using shared objects is that on a machine with the
876 Directory, File daemon, the Storage daemon, and a console, you will have only
877 one copy of the code in memory rather than four copies. Also the total size of
878 the binary release is smaller since the library code appears only once rather
879 than once for every program that uses it; this results in significant reduction
880 in the size of the binaries particularly for the utility tools.
882 In order for the system loader to find the shared objects when loading the
883 Bacula binaries, the Bacula shared objects must either be in a shared object
884 directory known to the loader (typically /usr/lib) or they must be in the
885 directory that may be specified on the {\bf ./configure} line using the {\bf
886 {-}{-}libdir} option as:
889 ./configure --libdir=/full-path/dir
892 the default is /usr/lib. If {-}{-}libdir is specified, there should be
893 no need to modify your loader configuration provided that
894 the shared objects are installed in that directory (Bacula
895 does this with the make install command). The shared objects
896 that Bacula references are:
905 These files are symbolically linked to the real shared object file,
906 which has a version number to permit running multiple versions of
907 the libraries if desired (not normally the case).
909 If you have problems with libtool or you wish to use the old
910 way of building static libraries, or you want to build a static
911 version of Bacula you may disable
912 libtool on the configure command line with:
915 ./configure --disable-libtool
919 \section{Building Static versions of Bacula}
920 \index[general]{Static linking}
921 In order to build static versions of Bacula, in addition
922 to configuration options that were needed you now must
923 also add --disable-libtool. Example
926 ./configure --enable-static-client-only --disable-libtool
930 \section{Virtual Backup (Vbackup)}
931 \index[general]{Virtual Backup}
932 \index[general]{Vbackup}
934 Bacula's virtual backup feature is often called Synthetic Backup or
935 Consolidation in other backup products. It permits you to consolidate the
936 previous Full backup plus the most recent Differential backup and any
937 subsequent Incremental backups into a new Full backup. This new Full
938 backup will then be considered as the most recent Full for any future
939 Incremental or Differential backups. The VirtualFull backup is
940 accomplished without contacting the client by reading the previous backup
941 data and writing it to a volume in a different pool.
943 In some respects the Vbackup feature works similar to a Migration job, in
944 that Bacula normally reads the data from the pool specified in the
945 Job resource, and writes it to the {\bf Next Pool} specified in the
946 Job resource. Note, this means that usually the output from the Virtual
947 Backup is written into a different pool from where your prior backups
948 are saved. Doing it this way guarantees that you will not get a deadlock
949 situation attempting to read and write to the same volume in the Storage
950 daemon. If you then want to do subsequent backups, you may need to
951 move the Virtual Full Volume back to your normal backup pool.
952 Alternatively, you can set your {\bf Next Pool} to point to the current
953 pool. This will cause Bacula to read and write to Volumes in the
954 current pool. In general, this will work, because Bacula will
955 not allow reading and writing on the same Volume. In any case, once
956 a VirtualFull has been created, and a restore is done involving the
957 most current Full, it will read the Volume or Volumes by the VirtualFull
958 regardless of in which Pool the Volume is found.
960 The Vbackup is enabled on a Job by Job in the Job resource by specifying
961 a level of {\bf VirtualFull}.
963 A typical Job resource definition might look like the following:
977 # Default pool definition
981 Recycle = yes # Automatically recycle Volumes
982 AutoPrune = yes # Prune expired volumes
983 Volume Retention = 365d # one year
991 Recycle = yes # Automatically recycle Volumes
992 AutoPrune = yes # Prune expired volumes
993 Volume Retention = 365d # one year
994 Storage = DiskChanger
997 # Definition of file storage device
1002 Device = FileStorage
1004 Maximum Concurrent Jobs = 5
1007 # Definition of DDS Virtual tape disk storage device
1010 Address = localhost # N.B. Use a fully qualified name here
1012 Device = DiskChanger
1013 Media Type = DiskChangerMedia
1014 Maximum Concurrent Jobs = 4
1019 Then in bconsole or via a Run schedule, you would run the job as:
1022 run job=MyBackup level=Full
1023 run job=MyBackup level=Incremental
1024 run job=MyBackup level=Differential
1025 run job=MyBackup level=Incremental
1026 run job=MyBackup level=Incremental
1029 So providing there were changes between each of those jobs, you would end up
1030 with a Full backup, a Differential, which includes the first Incremental
1031 backup, then two Incremental backups. All the above jobs would be written to
1032 the {\bf Default} pool.
1034 To consolidate those backups into a new Full backup, you would run the
1038 run job=MyBackup level=VirtualFull
1041 And it would produce a new Full backup without using the client, and the output
1042 would be written to the {\bf Full} Pool which uses the Diskchanger Storage.
1044 If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
1047 Note, the Start and End time of the Virtual Full backup is set to the
1048 values for the last job included in the Virtual Full (in the above example,
1049 it is an Increment). This is so that if another incremental is done, which
1050 will be based on the Virtual Full, it will backup all files from the
1051 last Job included in the Virtual Full rather than from the time the Virtual
1052 Full was actually run.
1056 \section{Catalog Format}
1057 \index[general]{Catalog Format}
1058 Bacula 3.0 comes with some changes to the catalog format. The upgrade
1059 operation will convert the FileId field of the File table from 32 bits (max 4
1060 billion table entries) to 64 bits (very large number of items). The
1061 conversion process can take a bit of time and will likely DOUBLE THE SIZE of
1062 your catalog during the conversion. Also you won't be able to run jobs during
1063 this conversion period. For example, a 3 million file catalog will take 2
1064 minutes to upgrade on a normal machine. Please don't forget to make a valid
1065 backup of your database before executing the upgrade script. See the
1066 ReleaseNotes for additional details.
1068 \section{64 bit Windows Client}
1069 \index[general]{Win64 Client}
1070 Unfortunately, Microsoft's implementation of Volume Shadown Copy (VSS) on
1071 their 64 bit OS versions is not compatible with a 32 bit Bacula Client.
1072 As a consequence, we are also releasing a 64 bit version of the Bacula
1073 Windows Client (win64bacula-3.0.0.exe) that does work with VSS.
1074 These binaries should only be installed on 64 bit Windows operating systems.
1075 What is important is not your hardware but whether or not you have
1076 a 64 bit version of the Windows OS.
1078 Compared to the Win32 Bacula Client, the 64 bit release contains a few differences:
1080 \item Before installing the Win64 Bacula Client, you must totally
1081 deinstall any prior 2.4.x Client installation using the
1082 Bacula deinstallation (see the menu item). You may want
1083 to save your .conf files first.
1084 \item Only the Client (File daemon) is ported to Win64, the Director
1085 and the Storage daemon are not in the 64 bit Windows installer.
1086 \item bwx-console is not yet ported.
1087 \item bconsole is ported but it has not been tested.
1088 \item The documentation is not included in the installer.
1089 \item Due to Vista security restrictions imposed on a default installation
1090 of Vista, before upgrading the Client, you must manually stop
1091 any prior version of Bacula from running, otherwise the install
1093 \item Due to Vista security restrictions imposed on a default installation
1094 of Vista, attempting to edit the conf files via the menu items
1095 will fail. You must directly edit the files with appropriate
1096 permissions. Generally double clicking on the appropriate .conf
1097 file will work providing you have sufficient permissions.
1098 \item All Bacula files are now installed in
1099 {\bf C:/Program Files/Bacula} except the main menu items,
1100 which are installed as before. This vastly simplifies the installation.
1101 \item If you are running on a foreign language version of Windows, most
1102 likely {\bf C:/Program Files} does not exist, so you should use the
1103 Custom installation and enter an appropriate location to install
1105 \item The 3.0.0 Win32 Client continues to install files in the locations used
1106 by prior versions. For the next version we will convert it to use
1107 the same installation conventions as the Win64 version.
1110 This project was funded by Bacula Systems.
1113 \section{Duplicate Job Control}
1114 \index[general]{Duplicate Jobs}
1115 The new version of Bacula provides four new directives that
1116 give additional control over what Bacula does if duplicate jobs
1117 are started. A duplicate job in the sense we use it here means
1118 a second or subsequent job with the same name starts. This
1119 happens most frequently when the first job runs longer than expected because no
1120 tapes are available.
1122 The four directives each take as an argument a {\bf yes} or {\bf no} value and
1123 are specified in the Job resource.
1127 \subsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}}
1128 \index[general]{Allow Duplicate Jobs}
1129 If this directive is enabled duplicate jobs will be run. If
1130 the directive is set to {\bf no} (default) then only one job of a given name
1131 may run at one time, and the action that Bacula takes to ensure only
1132 one job runs is determined by the other directives (see below).
1134 If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs
1135 are present and none of the three directives given below permit
1136 cancelling a job, then the current job (the second one started)
1140 \subsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}}
1141 \index[general]{Allow Higher Duplicates}
1142 If this directive is set to {\bf yes} (default) the job with a higher
1143 priority (lower priority number) will be permitted to run, and
1144 the current job will be cancelled. If the
1145 priorities of the two jobs are the same, the outcome is determined by
1146 other directives (see below).
1148 \subsection{Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}}
1149 \index[general]{Cancel Queued Duplicates}
1150 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1151 if this directive is set to {\bf yes} any job that is
1152 already queued to run but not yet running will be canceled.
1153 The default is {\bf no}.
1155 \subsection{Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}}
1156 \index[general]{Cancel Running Duplicates}
1157 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1158 if this directive is set to {\bf yes} any job that is already running
1159 will be canceled. The default is {\bf no}.
1162 \section{TLS Authentication}
1163 \index[general]{TLS Authentication}
1164 In Bacula version 2.5.x and later, in addition to the normal Bacula
1165 CRAM-MD5 authentication that is used to authenticate each Bacula
1166 connection, you can specify that you want TLS Authentication as well,
1167 which will provide more secure authentication.
1169 This new feature uses Bacula's existing TLS code (normally used for
1170 communications encryption) to do authentication. To use it, you must
1171 specify all the TLS directives normally used to enable communications
1172 encryption (TLS Enable, TLS Verify Peer, TLS Certificate, ...) and
1175 \subsection{TLS Authenticate = yes}
1177 TLS Authenticate = yes
1180 in the main daemon configuration resource (Director for the Director,
1181 Client for the File daemon, and Storage for the Storage daemon).
1183 When {\bf TLS Authenticate} is enabled, after doing the CRAM-MD5
1184 authentication, Bacula will also do TLS authentication, then TLS
1185 encryption will be turned off, and the rest of the communication between
1186 the two Bacula daemons will be done without encryption.
1188 If you want to encrypt communications data, use the normal TLS directives
1189 but do not turn on {\bf TLS Authenticate}.
1191 \section{bextract non-portable Win32 data}
1192 \index[general]{bextract handles Win32 non-portable data}
1193 {\bf bextract} has been enhanced to be able to restore
1194 non-portable Win32 data to any OS. Previous versions were
1195 unable to restore non-portable Win32 data to machines that
1196 did not have the Win32 BackupRead and BackupWrite API calls.
1198 \section{State File updated at Job Termination}
1199 \index[general]{State File}
1200 In previous versions of Bacula, the state file, which provides a
1201 summary of previous jobs run in the {\bf status} command output was
1202 updated only when Bacula terminated, thus if the daemon crashed, the
1203 state file might not contain all the run data. This version of
1204 the Bacula daemons updates the state file on each job termination.
1206 \section{MaxFullInterval = \lt{}time-interval\gt{}}
1207 \index[general]{MaxFullInterval}
1208 The new Job resource directive {\bf Max Full Interval = \lt{}time-interval\gt{}}
1209 can be used to specify the maximum time interval between {\bf Full} backup
1210 jobs. When a job starts, if the time since the last Full backup is
1211 greater than the specified interval, and the job would normally be an
1212 {\bf Incremental} or {\bf Differential}, it will be automatically
1213 upgraded to a {\bf Full} backup.
1215 \section{MaxDiffInterval = \lt{}time-interval\gt{}}
1216 \index[general]{MaxDiffInterval}
1217 The new Job resource directive {\bf Max Diff Interval = \lt{}time-interval\gt{}}
1218 can be used to specify the maximum time interval between {\bf Differential} backup
1219 jobs. When a job starts, if the time since the last Differential backup is
1220 greater than the specified interval, and the job would normally be an
1221 {\bf Incremental}, it will be automatically
1222 upgraded to a {\bf Differential} backup.
1224 \section{Honor No Dump Flag = \lt{}yes\vb{}no\gt{}}
1225 \index[general]{MaxDiffInterval}
1226 On FreeBSD systems, each file has a {\bf no dump flag} that can be set
1227 by the user, and when it is set it is an indication to backup programs
1228 to not backup that particular file. This version of Bacula contains a
1229 new Options directive within a FileSet resource, which instructs Bacula to
1230 obey this flag. The new directive is:
1233 Honor No Dump Flag = yes\vb{}no
1236 The default value is {\bf no}.
1239 \section{Exclude Dir Containing = \lt{}filename-string\gt{}}
1240 \index[general]{IgnoreDir}
1241 The {\bf ExcludeDirContaining = \lt{}filename\gt{}} is a new directive that
1242 can be added to the Include section of the FileSet resource. If the specified
1243 filename ({\bf filename-string}) is found on the Client in any directory to be
1244 backed up, the whole directory will be ignored (not backed up). For example:
1247 # List of files to be backed up
1255 Exclude Dir Containing = .excludeme
1260 But in /home, there may be hundreds of directories of users and some
1261 people want to indicate that they don't want to have certain
1262 directories backed up. For example, with the above FileSet, if
1263 the user or sysadmin creates a file named {\bf .excludeme} in
1264 specific directories, such as
1267 /home/user/www/cache/.excludeme
1268 /home/user/temp/.excludeme
1271 then Bacula will not backup the two directories named:
1274 /home/user/www/cache
1278 NOTE: subdirectories will not be backed up. That is, the directive
1279 applies to the two directories in question and any children (be they
1280 files, directories, etc).
1283 \section{Bacula Plugins}
1284 \index[general]{Plugin}
1285 Support for shared object plugins has been implemented in the Linux, Unix
1286 and Win32 File daemons. The API will be documented separately in
1287 the Developer's Guide or in a new document. For the moment, there is
1288 a single plugin named {\bf bpipe} that allows an external program to
1289 get control to backup and restore a file.
1291 Plugins are also planned (partially implemented) in the Director and the
1294 \subsection{Plugin Directory}
1295 \index[general]{Plugin Directory}
1296 Each daemon (DIR, FD, SD) has a new {\bf Plugin Directory} directive that may
1297 be added to the daemon definition resource. The directory takes a quoted
1298 string argument, which is the name of the directory in which the daemon can
1299 find the Bacula plugins. If this directive is not specified, Bacula will not
1300 load any plugins. Since each plugin has a distinctive name, all the daemons
1301 can share the same plugin directory.
1303 \subsection{Plugin Options}
1304 \index[general]{Plugin Options}
1305 The {\bf Plugin Options} directive takes a quoted string
1306 arguement (after the equal sign) and may be specified in the
1307 Job resource. The options specified will be passed to all plugins
1308 when they are run. This each plugin must know what it is looking
1309 for. The value defined in the Job resource can be modified
1310 by the user when he runs a Job via the {\bf bconsole} command line
1313 Note: this directive may be specified, and there is code to modify
1314 the string in the run command, but the plugin options are not yet passed to
1315 the plugin (i.e. not fully implemented).
1317 \subsection{Plugin Options ACL}
1318 \index[general]{Plugin Options ACL}
1319 The {\bf Plugin Options ACL} directive may be specified in the
1320 Director's Console resource. It functions as all the other ACL commands
1321 do by permitting users running restricted consoles to specify a
1322 {\bf Plugin Options} that overrides the one specified in the Job
1323 definition. Without this directive restricted consoles may not modify
1326 \subsection{Plugin = \lt{}plugin-command-string\gt{}}
1327 \index[general]{Plugin}
1328 The {\bf Plugin} directive is specified in the Include section of
1329 a FileSet resource where you put your {\bf File = xxx} directives.
1340 Plugin = "bpipe:..."
1345 In the above example, when the File daemon is processing the directives
1346 in the Include section, it will first backup all the files in {\bf /home}
1347 then it will load the plugin named {\bf bpipe} (actually bpipe-dir.so) from
1348 the Plugin Directory. The syntax and semantics of the Plugin directive
1349 require the first part of the string up to the colon (:) to be the name
1350 of the plugin. Everything after the first colon is ignored by the File daemon but
1351 is passed to the plugin. Thus the plugin writer may define the meaning of the
1352 rest of the string as he wishes.
1354 Please see the next section for information about the {\bf bpipe} Bacula
1357 \section{The bpipe Plugin}
1358 \index[general]{The bpipe Plugin}
1359 The {\bf bpipe} plugin is provided in the directory src/plugins/fd/bpipe-fd.c of
1360 the Bacula source distribution. When the plugin is compiled and linking into
1361 the resulting dynamic shared object (DSO), it will have the name {\bf bpipe-fd.so}.
1363 The purpose of the plugin is to provide an interface to any system program for
1364 backup and restore. As specified above the {\bf bpipe} plugin is specified in
1365 the Include section of your Job's FileSet resource. The full syntax of the
1366 plugin directive as interpreted by the {\bf bpipe} plugin (each plugin is free
1367 to specify the sytax as it wishes) is:
1370 Plugin = "<field1>:<field2>:<field3>:<field4>"
1375 \item {\bf field1} is the name of the plugin with the trailing {\bf -fd.so}
1376 stripped off, so in this case, we would put {\bf bpipe} in this field.
1378 \item {\bf field2} specifies the namespace, which for {\bf bpipe} is the
1379 pseudo path and filename under which the backup will be saved. This pseudo
1380 path and filename will be seen by the user in the restore file tree.
1381 For example, if the value is {\bf /MYSQL/regress.sql}, the data
1382 backed up by the plugin will be put under that "pseudo" path and filename.
1383 You must be careful to choose a naming convention that is unique to avoid
1384 a conflict with a path and filename that actually exists on your system.
1386 \item {\bf field3} for the {\bf bpipe} plugin
1387 specifies the "reader" program that is called by the plugin during
1388 backup to read the data. {\bf bpipe} will call this program by doing a
1391 \item {\bf field4} for the {\bf bpipe} plugin
1392 specifies the "writer" program that is called by the plugin during
1393 restore to write the data back to the filesystem.
1396 Putting it all together, the full plugin directive line might look
1400 Plugin = "bpipe:/MYSQL/regress.sql:mysqldump -f
1401 --opt --databases bacula:mysql"
1404 The directive has been split into two lines, but within the {\bf bacula-dir.conf} file
1405 would be written on a single line.
1407 This causes the File daemon to call the {\bf bpipe} plugin, which will write
1408 its data into the "pseudo" file {\bf /MYSQL/regress.sql} by calling the
1409 program {\bf mysqldump -f --opt --database bacula} to read the data during
1410 backup. The mysqldump command outputs all the data for the database named
1411 {\bf bacula}, which will be read by the plugin and stored in the backup.
1412 During restore, the data that was backed up will be sent to the program
1413 specified in the last field, which in this case is {\bf mysql}. When
1414 {\bf mysql} is called, it will read the data sent to it by the plugn
1415 then write it back to the same database from which it came ({\bf bacula}
1418 The {\bf bpipe} plugin is a generic pipe program, that simply transmits
1419 the data from a specified program to Bacula for backup, and then from Bacula to
1420 a specified program for restore.
1422 By using different command lines to {\bf bpipe},
1423 you can backup any kind of data (ASCII or binary) depending
1424 on the program called.
1426 \section{Microsoft Exchange Server 2003/2007 Plugin}
1427 \index[general]{Microsoft Exchange Server 2003/2007 Plugin}
1428 \subsection{Background}
1429 The Exchange plugin was made possible by a funded development project
1430 between Equiinet Ltd -- www.equiinet.com (many thanks) and Bacula Systems.
1431 The code for the plugin was written by James Harper, and the Bacula core
1432 code by Kern Sibbald. All the code for this funded development has become
1433 part of the Bacula project. Thanks to everyone who made it happen.
1435 \subsection{Concepts}
1436 Although it is possible to backup Exchange using Bacula VSS the Exchange
1437 plugin adds a good deal of functionality, because while Bacula VSS
1438 completes a full backup (snapshot) of Exchange, it does
1439 not support Incremental or Differential backups, restoring is more
1440 complicated, and a single database restore is not possible.
1442 Microsoft Exchange organises its storage into Storage Groups with
1443 Databases inside them. A default installation of Exchange will have a
1444 single Storage Group called 'First Storage Group', with two Databases
1445 inside it, "Mailbox Store (SERVER NAME)" and
1446 "Public Folder Store (SERVER NAME)",
1447 which hold user email and public folders respectively.
1449 In the default configuration, Exchange logs everything that happens to
1450 log files, such that if you have a backup, and all the log files since,
1451 you can restore to the present time. Each Storage Group has its own set
1452 of log files and operates independently of any other Storage Groups. At
1453 the Storage Group level, the logging can be turned off by enabling a
1454 function called "Enable circular logging". At this time the Exchange
1455 plugin will not function if this option is enabled.
1457 The plugin allows backing up of entire storage groups, and the restoring
1458 of entire storage groups or individual databases. Backing up and
1459 restoring at the individual mailbox or email item is not supported but
1460 can be simulated by use of the "Recovery" Storage Group (see below).
1462 \subsection{Installing}
1463 The Exchange plugin requires a DLL that is shipped with Microsoft
1464 Exchanger Server called {\bf esebcli2.dll}. Assuming Exchange is installed
1465 correctly the Exchange plugin should find this automatically and run
1466 without any additional installation.
1468 If the DLL can not be found automatically it will need to be copied into
1469 the Bacula installation
1470 directory (eg C:\verb+\+Program Files\verb+\+Bacula\verb+\+bin). The Exchange API DLL is
1471 named esebcli2.dll and is found in C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+bin on a
1472 default Exchange installation.
1474 \subsection{Backing Up}
1475 To back up an Exchange server the Fileset definition must contain at
1476 least {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"} for
1477 the backup to work correctly. The 'exchange:' bit tells Bacula to look
1478 for the exchange plugin, the '@EXCHANGE' bit makes sure all the backed
1479 up files are prefixed with something that isn't going to share a name
1480 with something outside the plugin, and the 'Microsoft Information Store'
1481 bit is required also. It is also possible to add the name of a storage
1482 group to the "Plugin =" line, eg \\
1483 {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"} \\
1484 if you want only a single storage group backed up.
1486 Additionally, you can suffix the 'Plugin =' directive with
1487 ":notrunconfull" which will tell the plugin not to truncate the Exchange
1488 database at the end of a full backup.
1490 An Incremental or Differential backup will backup only the database logs
1491 for each Storage Group by inspecting the "modified date" on each
1492 physical log file. Because of the way the Exchange API works, the last
1493 logfile backed up on each backup will always be backed up by the next
1494 Incremental or Differential backup too. This adds 5MB to each
1495 Incremental or Differential backup size but otherwise does not cause any
1498 By default, a normal VSS fileset containing all the drive letters will
1499 also back up the Exchange databases using VSS. This will interfere with
1500 the plugin and Exchange's shared ideas of when the last full backup was
1501 done, and may also truncate log files incorrectly. It is important,
1502 therefore, that the Exchange database files be excluded from the backup,
1503 although the folders the files are in should be included, or they will
1504 have to be recreated manually if a baremetal restore is done.
1509 File = C:/Program Files/Exchsrvr/mdbdata
1510 Plugin = "exchange:..."
1513 File = C:/Program Files/Exchsrvr/mdbdata/E00.chk
1514 File = C:/Program Files/Exchsrvr/mdbdata/E00.log
1515 File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log
1516 File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log
1517 File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log
1518 File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log
1519 File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb
1524 The advantage of excluding the above files is that you can significantly
1525 reduce the size of your backup since all the important Exchange files
1526 will be properly saved by the Plugin.
1529 \subsection{Restoring}
1530 The restore operation is much the same as a normal Bacula restore, with
1531 the following provisos:
1534 \item The {\bf Where} restore option must not be specified
1535 \item Each Database directory must be marked as a whole. You cannot just
1536 select (say) the .edb file and not the others.
1537 \item If a Storage Group is restored, the directory of the Storage Group
1539 \item It is possible to restore only a subset of the available log files,
1540 but they {\bf must} be contiguous. Exchange will fail to restore correctly
1541 if a log file is missing from the sequence of log files
1542 \item Each database to be restored must be dismounted and marked as "Can be
1543 overwritten by restore"
1544 \item If an entire Storage Group is to be restored (eg all databases and
1545 logs in the Storage Group), then it is best to manually delete the
1546 database files from the server (eg C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+mdbdata\verb+\+*)
1547 as Exchange can get confused by stray log files lying around.
1550 \subsection{Restoring to the Recovery Storage Group}
1551 The concept of the Recovery Storage Group is well documented by
1553 \elink{http://support.microsoft.com/kb/824126}{http://support.microsoft.com/kb/824126},
1554 but to briefly summarize...
1556 Microsoft Exchange allows the creation of an additional Storage Group
1557 called the Recovery Storage Group, which is used to restore an older
1558 copy of a database (e.g. before a mailbox was deleted) into without
1559 messing with the current live data. This is required as the Standard and
1560 Small Business Server versions of Exchange can not ordinarily have more
1561 than one Storage Group.
1563 To create the Recovery Storage Group, drill down to the Server in Exchange
1564 System Manager, right click, and select
1565 {\bf "New -> Recovery Storage Group..."}. Accept or change the file
1566 locations and click OK. On the Recovery Storage Group, right click and
1567 select {\bf "Add Database to Recover..."} and select the database you will
1570 Restore only the single database nominated as the database in the
1571 Recovery Storage Group. Exchange will redirect the restore to the
1572 Recovery Storage Group automatically.
1573 Then run the restore.
1575 \subsection{Restoring on Microsoft Server 2007}
1576 Apparently the {\bf Exmerge} program no longer exists in Microsoft Server
1577 2007, and henc you use a new proceedure for recovering a single mail box.
1578 This procedure is ducomented by Microsoft at:
1579 \elink{http://technet.microsoft.com/en-us/library/aa997694.aspx}{http://technet.microsoft.com/en-us/library/aa997694.aspx},
1580 and involves using the {\bf Restore-Mailbox} and {\bf
1581 Get-MailboxStatistics} shell commands.
1583 \subsection{Caveats}
1584 This plugin is still being developed, so you should consider it
1585 currently in BETA test, and thus use in a production environment
1586 should be done only after very careful testing.
1588 When doing a full backup, the Exchange database logs are truncated by
1589 Exchange as soon as the plugin has completed the backup. If the data
1590 never makes it to the backup medium (eg because of spooling) then the
1591 logs will still be truncated, but they will also not have been backed
1592 up. A solution to this is being worked on. You will have to schedule a
1593 new Full backup to ensure that your next backups will be usable.
1595 The "Enable Circular Logging" option cannot be enabled or the plugin
1598 Exchange insists that a successful Full backup must have taken place if
1599 an Incremental or Differential backup is desired, and the plugin will
1600 fail if this is not the case. If a restore is done, Exchange will
1601 require that a Full backup be done before an Incremental or Differential
1604 The plugin will most likely not work well if another backup application
1605 (eg NTBACKUP) is backing up the Exchange database, especially if the
1606 other backup application is truncating the log files.
1608 The Exchange plugin has not been tested with the {\bf Accurate} option, so
1609 we recommend either carefully testing or that you avoid this option for
1612 The Exchange plugin is not called during processing the bconsole {\bf
1613 estimate} command, and so anything that would be backed up by the plugin
1614 will not be added to the estimate total that is displayed.
1617 \section{libdbi Framework}
1618 \index[general]{libdbi Framework}
1619 As a general guideline, Bacula has support for a few catalog database drivers
1620 (MySQL, PostgreSQL, SQLite)
1621 coded natively by the Bacula team. With the libdbi implementation, which is a
1622 Bacula driver that uses libdbi to access the catalog, we have an open field to
1623 use many different kinds database engines following the needs of users.
1625 The according to libdbi (http://libdbi.sourceforge.net/) project: libdbi
1626 implements a database-independent abstraction layer in C, similar to the
1627 DBI/DBD layer in Perl. Writing one generic set of code, programmers can
1628 leverage the power of multiple databases and multiple simultaneous database
1629 connections by using this framework.
1631 Currently the libdbi driver in Bacula project only supports the same drivers
1632 natively coded in Bacula. However the libdbi project has support for many
1633 others database engines. You can view the list at
1634 http://libdbi-drivers.sourceforge.net/. In the future all those drivers can be
1635 supported by Bacula, however, they must be tested properly by the Bacula team.
1637 Some of benefits of using libdbi are:
1639 \item The possibility to use proprietary databases engines in which your
1640 proprietary licenses prevent the Bacula team from developing the driver.
1641 \item The possibility to use the drivers written for the libdbi project.
1642 \item The possibility to use other database engines without recompiling Bacula
1643 to use them. Just change one line in bacula-dir.conf
1644 \item Abstract Database access, this is, unique point to code and profiling
1645 catalog database access.
1648 The following drivers have been tested:
1650 \item PostgreSQL, with and without batch insert
1651 \item Mysql, with and without batch insert
1656 In the future, we will test and approve to use others databases engines
1657 (proprietary or not) like DB2, Oracle, Microsoft SQL.
1659 To compile Bacula to support libdbi we need to configure the code with the
1660 --with-dbi and --with-dbi-driver=[database] ./configure options, where
1661 [database] is the database engine to be used with Bacula (of course we can
1662 change the driver in file bacula-dir.conf, see below). We must configure the
1663 access port of the database engine with the option --with-db-port, because the
1664 libdbi framework doesn't know the default access port of each database.
1666 The next phase is checking (or configuring) the bacula-dir.conf, example:
1670 dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
1671 dbname = regress; user = regress; password = ""
1675 The parameter {\bf dbdriver} indicates that we will use the driver dbi with a
1676 mysql database. Currently the drivers supported by Bacula are: postgresql,
1677 mysql, sqlite, sqlite3; these are the names that may be added to string "dbi:".
1679 The following limitations apply when Bacula is set to use the libdbi framework:
1680 - Not tested on the Win32 platform
1681 - A little performance is lost if comparing with native database driver.
1682 The reason is bound with the database driver provided by libdbi and the
1683 simple fact that one more layer of code was added.
1685 It is important to remember, when compiling Bacula with libdbi, the
1686 following packages are needed:
1688 \item libdbi version 1.0.0, http://libdbi.sourceforge.net/
1689 \item libdbi-drivers 1.0.0, http://libdbi-drivers.sourceforge.net/
1692 You can download them and compile them on your system or install the packages
1693 from your OS distribution.
1695 \section{Console Command Additions and Enhancements}
1696 \index[general]{Console Additions}
1698 \subsection{Display Autochanger Content}
1699 \index[general]{StatusSlots}
1701 The {\bf status slots storage=\lt{}storage-name\gt{}} command displays
1702 autochanger content.
1706 Slot | Volume Name | Status | Media Type | Pool |
1707 ------+---------------+----------+-------------------+------------|
1708 1 | 00001 | Append | DiskChangerMedia | Default |
1709 2 | 00002 | Append | DiskChangerMedia | Default |
1710 3*| 00003 | Append | DiskChangerMedia | Scratch |
1715 If you an asterisk ({\bf *}) appears after the slot number, you must run an
1716 {\bf update slots} command to synchronize autochanger content with your
1719 \subsection{list joblog job=xxx or jobid=nnn}
1720 \index[general]{list joblog}
1721 A new list command has been added that allows you to list the contents
1722 of the Job Log stored in the catalog for either a Job Name (fully qualified)
1723 or for a particular JobId. The {\bf llist} command will include a line with
1724 the time and date of the entry.
1726 Note for the catalog to have Job Log entries, you must have a directive
1733 In your Director's {\bf Messages} resource.
1735 \subsection{Use separator for multiple commands}
1736 \index[general]{Command Separator}
1737 When using bconsole with readline, you can set the command separator with
1738 \textbf{@separator} command to one
1739 of those characters to write commands who require multiple input in one line.
1741 !$%&'()*+,-/:;<>?[]^`{|}~
1744 \subsection{Deleting Volumes}
1745 The delete volume bconsole command has been modified to
1746 require an asterisk (*) in front of a MediaId otherwise the
1747 value you enter is a taken to be a Volume name. This is so that
1748 users may delete numeric Volume names. The previous Bacula versions
1749 assumed that all input that started with a number was a MediaId.
1751 This new behavior is indicated in the prompt if you read it
1754 \section{Bare Metal Recovery}
1755 The old bare metal recovery project is essentially dead. One
1756 of the main features of it was that it would build a recovery
1757 CD based on the kernel on your system. The problem was that
1758 every distribution has a different boot procedure and different
1759 scripts, and worse yet, the boot procedures and scripts change
1760 from one distribution to another. This meant that maintaining
1761 (keeping up with the changes) the rescue CD was too much work.
1763 To replace it, a new bare metal recovery USB boot stick has been developed
1764 by Bacula Systems. This technology involves remastering a Ubuntu LiveCD to
1765 boot from a USB key.
1769 \item Recovery can be done from within graphical environment.
1770 \item Recovery can be done in a shell.
1771 \item Ubuntu boots on a large number of Linux systems.
1772 \item The process of updating the system and adding new
1773 packages is not too difficult.
1774 \item The USB key can easily be upgraded to newer Ubuntu versions.
1775 \item The USB key has writable partitions for modifications to
1776 the OS and for modification to your home directory.
1777 \item You can add new files/directories to the USB key very easily.
1778 \item You can save the environment from multiple machines on
1780 \item Bacula Systems is funding its ongoing development.
1783 The disadvantages are:
1785 \item The USB key is usable but currently under development.
1786 \item Not everyone may be familiar with Ubuntu (no worse
1788 \item Some older OSes cannot be booted from USB. This can
1789 be resolved by first booting a Ubuntu LiveCD then plugging
1791 \item Currently the documentation is sketchy and not yet added
1792 to the main manual. See below ...
1795 The documentation and the code can be found in the {\bf rescue} package
1796 in the directory {\bf linux/usb}.
1798 \section{Miscellaneous}
1799 \index[general]{Misc New Features}
1801 \subsection{Allow Mixed Priority = \lt{}yes\vb{}no\gt{}}
1802 \index[general]{Allow Mixed Priority}
1803 This directive is only implemented in version 2.5 and later. When
1804 set to {\bf yes} (default {\bf no}), this job may run even if lower
1805 priority jobs are already running. This means a high priority job
1806 will not have to wait for other jobs to finish before starting.
1807 The scheduler will only mix priorities when all running jobs have
1810 Note that only higher priority jobs will start early. Suppose the
1811 director will allow two concurrent jobs, and that two jobs with
1812 priority 10 are running, with two more in the queue. If a job with
1813 priority 5 is added to the queue, it will be run as soon as one of
1814 the running jobs finishes. However, new priority 10 jobs will not
1815 be run until the priority 5 job has finished.
1817 \subsection{Bootstrap File Directive -- FileRegex}
1818 \index[general]{Bootstrap File Directive}
1819 {\bf FileRegex} is a new command that can be added to the bootstrap
1820 (.bsr) file. The value is a regular expression. When specified, only
1821 matching filenames will be restored.
1823 During a restore, if all File records are pruned from the catalog
1824 for a Job, normally Bacula can restore only all files saved. That
1825 is there is no way using the catalog to select individual files.
1826 With this new feature, Bacula will ask if you want to specify a Regex
1827 expression for extracting only a part of the full backup.
1830 Building directory tree for JobId(s) 1,3 ...
1831 There were no files inserted into the tree, so file selection
1832 is not possible.Most likely your retention policy pruned the files
1834 Do you want to restore all the files? (yes\vb{}no): no
1836 Regexp matching files to restore? (empty to abort): /tmp/regress/(bin|tests)/
1837 Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr
1840 \subsection{Bootstrap File Optimization Changes}
1841 In order to permit proper seeking on disk files, we have extended the bootstrap
1842 file format to include a {\bf VolStartAddr} and {\bf VolEndAddr} records. Each
1843 takes a 64 bit unsigned integer range (i.e. nnn-mmm) which defines the start
1844 address range and end address range respectively. These two directives replace
1845 the {\bf VolStartFile}, {\bf VolEndFile}, {\bf VolStartBlock} and {\bf
1846 VolEndBlock} directives. Bootstrap files containing the old directives will
1847 still work, but will not properly take advantage of proper disk seeking, and
1848 may read completely to the end of a disk volume during a restore. With the new
1849 format (automatically generated by the new Director), restores will seek
1850 properly and stop reading the volume when all the files have been restored.
1852 \subsection{Solaris ZFS/NFSv4 ACLs}
1853 This is an upgrade of the previous Solaris ACL backup code
1854 to the new library format, which will backup both the old
1855 POSIX(UFS) ACLs as well as the ZFS ACLs.
1857 The new code can also restore POSIX(UFS) ACLs to a ZFS filesystem
1858 (it will translate the POSIX(UFS)) ACL into a ZFS/NFSv4 one) it can also
1859 be used to transfer from UFS to ZFS filesystems.
1862 \subsection{Virtual Tape Emulation}
1863 \index[general]{Virtual Tape Emulation}
1864 We now have a Virtual Tape emulator that allows us to run though 99.9\% of
1865 the tape code but actually reading and writing to a disk file. Used with the
1866 \textbf{disk-changer} script, you can now emulate an autochanger with 10 drives
1867 and 700 slots. This feature is most useful in testing. It is enabled
1868 by using {\bf Device Type = vtape} in the Storage daemon's Device
1869 directive. This feature is only implemented on Linux machines and should not be
1870 used for production.
1872 \subsection{Bat Enhancements}
1873 \index[general]{Bat Enhancements}
1874 Bat (the Bacula Administration Tool) GUI program has been significantly
1875 enhanced and stabilized. In particular, there are new table based status
1876 commands; it can now be easily localized using Qt4 Linguist.
1878 The Bat communications protocol has been significantly enhanced to improve
1879 GUI handling. Note, you {\bf must} use a the bat that is distributed with
1880 the Director you are using otherwise the communications protocol will not
1883 \subsection{RunScript Enhancements}
1884 \index[general]{RunScript Enhancements}
1885 The {\bf RunScript} resource has been enhanced to permit multiple
1886 commands per RunScript. Simply specify multiple {\bf Command} directives
1893 Command = "/bin/echo test"
1894 Command = "/bin/echo an other test"
1895 Command = "/bin/echo 3 commands in the same runscript"
1902 A new Client RunScript {\bf RunsWhen} keyword of {\bf AfterVSS} has been
1903 implemented, which runs the command after the Volume Shadow Copy has been made.
1905 Console commands can be specified within a RunScript by using:
1906 {\bf Console = \lt{}command\gt{}}, however, this command has not been
1907 carefully tested and debugged and is known to easily crash the Director.
1908 We would appreciate feedback. Due to the recursive nature of this command, we
1909 may remove it before the final release.
1911 \subsection{Status Enhancements}
1912 \index[general]{Status Enhancements}
1913 The bconsole {\bf status dir} output has been enhanced to indicate
1914 Storage daemon job spooling and despooling activity.
1916 \subsection{Connect Timeout}
1917 \index[general]{Connect Timeout}
1918 The default connect timeout to the File
1919 daemon has been set to 3 minutes. Previously it was 30 minutes.
1921 \subsection{ftruncate for NFS Volumes}
1922 \index[general]{ftruncate for NFS Volumes}
1923 If you write to a Volume mounted by NFS (say on a local file server),
1924 in previous Bacula versions, when the Volume was recycled, it was not
1925 properly truncated because NFS does not implement ftruncate (file
1926 truncate). This is now corrected in the new version because we have
1927 written code (actually a kind user) that deletes and recreates the Volume,
1928 thus accomplishing the same thing as a truncate.
1930 \subsection{Support for Ubuntu}
1931 The new version of Bacula now recognizes the Ubuntu (and Kubuntu)
1932 version of Linux, and thus now provides correct autostart routines.
1933 Since Ubuntu officially supports Bacula, you can also obtain any
1934 recent release of Bacula from the Ubuntu repositories.
1936 \subsection{Recycle Pool = \lt{}pool-name\gt{}}
1937 \index[general]{Recycle Pool}
1938 The new \textbf{RecyclePool} directive defines to which pool the Volume will
1939 be placed (moved) when it is recycled. Without this directive, a Volume will
1940 remain in the same pool when it is recycled. With this directive, it can be
1941 moved automatically to any existing pool during a recycle. This directive is
1942 probably most useful when defined in the Scratch pool, so that volumes will
1943 be recycled back into the Scratch pool.
1945 \subsection{FD Version}
1946 \index[general]{FD Version}
1947 The File daemon to Director protocol now includes a version
1948 number, which although there is no visible change for users,
1949 will help us in future versions automatically determine
1950 if a File daemon is not compatible.
1952 \subsection{Max Run Sched Time = \lt{}time-period-in-seconds\gt{}}
1953 \index[general]{Max Run Sched Time}
1954 The time specifies the maximum allowed time that a job may run, counted from
1955 when the job was scheduled. This can be useful to prevent jobs from running
1956 during working hours. We can see it like \texttt{Max Start Delay + Max Run
1959 \subsection{Max Wait Time = \lt{}time-period-in-seconds\gt{}}
1960 \index[general]{Max Wait Time}
1961 Previous \textbf{MaxWaitTime} directives aren't working as expected, instead
1962 of checking the maximum allowed time that a job may block for a resource,
1963 those directives worked like \textbf{MaxRunTime}. Some users are reporting to
1964 use \textbf{Incr/Diff/Full Max Wait Time} to control the maximum run time of
1965 their job depending on the level. Now, they have to use
1966 \textbf{Incr/Diff/Full Max Run Time}. \textbf{Incr/Diff/Full Max Wait Time}
1967 directives are now deprecated.
1969 \subsection{Incremental|Differential Max Wait Time = \lt{}time-period-in-seconds\gt{}}
1970 \index[general]{Incremental Max Wait Time}
1971 \index[general]{Differential Max Wait Time}
1973 These directives have been deprecated in favor of
1974 \texttt{Incremental|Differential Max Run Time}.
1976 \subsection{Max Run Time directives}
1977 \index[general]{Max Run Time directives}
1978 Using \textbf{Full/Diff/Incr Max Run Time}, it's now possible to specify the
1979 maximum allowed time that a job can run depending on the level.
1981 \addcontentsline{lof}{figure}{Job time control directives}
1982 \includegraphics{\idir different_time.eps}
1984 \subsection{Statistics Enhancements}
1985 \index[general]{Statistics Enhancements}
1986 If you (or probably your boss) want to have statistics on your backups to
1987 provide some \textit{Service Level Agreement} indicators, you could use a few
1988 SQL queries on the Job table to report how many:
1992 \item jobs have been successful
1993 \item files have been backed up
1997 However, these statistics are accurate only if your job retention is greater
1998 than your statistics period. Ie, if jobs are purged from the catalog, you won't
1999 be able to use them.
2001 Now, you can use the \textbf{update stats [days=num]} console command to fill
2002 the JobHistory table with new Job records. If you want to be sure to take in
2003 account only \textbf{good jobs}, ie if one of your important job has failed but
2004 you have fixed the problem and restarted it on time, you probably want to
2005 delete the first \textit{bad} job record and keep only the successful one. For
2006 that simply let your staff do the job, and update JobHistory table after two or
2007 three days depending on your organization using the \textbf{[days=num]} option.
2009 These statistics records aren't used for restoring, but mainly for
2010 capacity planning, billings, etc.
2012 The Bweb interface provides a statistics module that can use this feature. You
2013 can also use tools like Talend or extract information by yourself.
2015 The \textbf{Statistics Retention = \lt{}time\gt{}} director directive defines
2016 the length of time that Bacula will keep statistics job records in the Catalog
2017 database after the Job End time. (In \texttt{JobHistory} table) When this time
2018 period expires, and if user runs \texttt{prune stats} command, Bacula will
2019 prune (remove) Job records that are older than the specified period.
2021 You can use the following Job resource in your nightly \textbf{BackupCatalog}
2022 job to maintain statistics.
2025 Name = BackupCatalog
2028 Console = "update stats days=3"
2029 Console = "prune stats yes"
2036 \subsection{ScratchPool = \lt{}pool-resource-name\gt{}}
2037 \index[general]{ScratchPool}
2038 This directive permits to specify a specific \textsl{Scratch} pool for the
2039 current pool. This is useful when using multiple storage sharing the same
2040 mediatype or when you want to dedicate volumes to a particular set of pool.
2042 \subsection{Enhanced Attribute Despooling}
2043 \index[general]{Attribute Despooling}
2044 If the storage daemon and the Director are on the same machine, the spool file
2045 that contains attributes is read directly by the Director instead of being
2046 transmitted across the network. That should reduce load and speedup insertion.
2048 \subsection{SpoolSize = \lt{}size-specification-in-bytes\gt{}}
2049 \index[general]{SpoolSize}
2050 A new Job directive permits to specify the spool size per job. This is used
2051 in advanced job tunning. {\bf SpoolSize={\it bytes}}
2053 \subsection{MaxConsoleConnections = \lt{}number\gt{}}
2054 \index[general]{MaxConsoleConnections}
2055 A new director directive permits to specify the maximum number of Console
2056 Connections that could run concurrently. The default is set to 20, but you may
2057 set it to a larger number.
2059 \subsection{VerId = \lt{}string\gt{}}
2060 \index[general]{VerId}
2061 A new director directive permits to specify a personnal identifier that will be
2062 displayed in the \texttt{version} command.
2064 \subsection{dbcheck enhancements}
2065 \index[general]{dbcheck enhancements}
2066 If you are using Mysql, dbcheck will now ask you if you want to create
2067 temporary indexes to speed up orphaned Path and Filename elimination.
2069 A new \texttt{-B} option allows you to print catalog information in a simple
2070 text based format. This is useful to backup it in a secure way.
2085 You can now specify the database connection port in the command line.
2087 \subsection{{-}{-}docdir configure option}
2088 \index[general]{{-}{-}docdir configure option}
2089 You can use {-}{-}docdir= on the ./configure command to
2090 specify the directory where you want Bacula to install the
2091 LICENSE, ReleaseNotes, ChangeLog, ... files. The default is
2092 {\bf /usr/share/doc/bacula}.
2094 \subsection{{-}{-}htmldir configure option}
2095 \index[general]{{-}{-}htmldir configure option}
2096 You can use {-}{-}htmldir= on the ./configure command to
2097 specify the directory where you want Bacula to install the bat html help
2098 files. The default is {\bf /usr/share/doc/bacula/html}
2100 \subsection{{-}{-}with-plugindir configure option}
2101 \index[general]{{-}{-}plugindir configure option}
2102 You can use {-}{-}plugindir= on the ./configure command to
2103 specify the directory where you want Bacula to install
2104 the plugins (currently only bpipe-fd). The default is