1 \chapter{New Features in 7.0.0}
2 This chapter presents the new features that have been added to
3 the various versions of Bacula.
5 \section{New Features in 7.0.0}
7 \subsection{Storage daemon to Storage daemon}
8 Bacula version 7.0 permits SD to SD transfer of Copy and Migration
9 Jobs. This permits what is commonly referred to as replication or
10 off-site transfer of Bacula backups. It occurs automatically, if
11 the source SD and destination SD of a Copy or Migration job are
12 different. The following picture shows how this works.
14 \includegraphics[width=0.8\linewidth]{sd-to-sd}
16 \subsection{SD Calls Client}
17 If the {\bf SD Calls Client} directive is set to true in a Client resource
18 any Backup, Restore, Verify, Copy, or Migration Job where the client
19 is involved, the client will wait for the Storage daemon to contact it.
20 By default this directive is set to false, and the Client will call
21 the Storage daemon. This directive can be useful if your Storage daemon
22 is behind a firewall that permits outgoing connections but not incoming
23 one. The following picture shows the communications connection paths in
26 \includegraphics[width=0.8\linewidth]{sd-calls-client}
28 \subsection{Next Pool}
29 In previous versions of Bacula the Next Pool directive could be
30 specified in the Pool resource for use with Migration and Copy Jobs.
31 The Next Pool concept has been
32 extended in Bacula version 7.0.0 to allow you to specify the
33 Next Pool directive in the Job resource as well. If specified in
34 the Job resource, it will override any value specified in the Pool
37 In addition to being permitted in the Job resource, the
38 {\bf nextpool=xxx} specification can be specified as a run
39 override in the {\bf run} directive of a Schedule resource.
40 Any {\bf nextpool} specification in a {\bf run}
41 directive will override any other specification in either
44 In general, more information is displayed in the Job log
45 on exactly which Next Pool specification is ultimately used.
47 \subsection{status storage}
48 The bconsole {\bf status storage} has been modified to attempt to eliminate
49 duplicate storage resources and only show one that references any given
50 storage daemon. This might be confusing at first, but tends to make a
51 much more compact list of storage resource from which to select if there
52 are multiple storage devices in the same storage daemon.
54 If you want the old behavior (always display all storage resources) simply
55 add the keyword {\bf select} to the command -- i.e. use
56 {\bf status select storage}.
62 \subsection{status schedule}
63 A new status command option called {\bf scheduled} has been implemented
64 in bconsole. By default it will display 20 lines of the next scheduled
65 jobs. For example, with the default bacula-dir.conf configuration file,
66 a bconsole command {\bf status scheduled} produces:
70 Level Type Pri Scheduled Job Name Schedule
71 ======================================================================
72 Differential Backup 10 Sun 30-Mar 23:05 BackupClient1 WeeklyCycle
73 Incremental Backup 10 Mon 24-Mar 23:05 BackupClient1 WeeklyCycle
74 Incremental Backup 10 Tue 25-Mar 23:05 BackupClient1 WeeklyCycle
76 Full Backup 11 Mon 24-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
77 Full Backup 11 Wed 26-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
82 Note, the output is listed by the Jobs found, and is not sorted
86 This command has a number of options, most of which act as filters:
88 \item {\bf days=nn} This specifies the number of days to list. The default is
89 10 but can be set from 0 to 500.
90 \item {\bf limit=nn} This specifies the limit to the number of lines to print.
91 The default is 100 but can be any number in the range 0 to 2000.
92 \item {\bf time="YYYY-MM-DD HH:MM:SS"} Sets the start time for listing the
93 scheduled jobs. The default is to use the current time. Note, the
94 time value must be specified inside double quotes and must be in
95 the exact form shown above.
96 \item {\bf schedule=schedule-name} This option restricts the output to
98 \item {\bf job=job-name} This option restricts the output to the specified
102 \subsection{Data Encryption Cipher Configuration}
103 Bacula version 7.0 and later now allows to configure the data
104 encryption cipher and the digest algorithm. The cipher was forced to AES
105 128, and it is now possible to choose between the following ciphers:
108 \item AES128 (default)
114 The digest algorithm was set to SHA1 or SHA256 depending on the local
116 options. We advise you to not modify the PkiDigest default setting. Please,
117 refer to OpenSSL documentation to know about pro and cons on these options.
126 \subsection{New Truncate Command}
127 We have added a new truncate command to bconsole, which
128 will truncate a Volume if the Volume is purged and if
129 the Volume is also marked {\bf Action On Purge = Truncate}.
130 This feature was originally added in Bacula version 5.0.1,
131 but the mechanism for actually doing the truncate required
132 the user to enter a command such as:
135 purge volume action=truncate storage=File pool=Default
138 The above command is now simplified to be:
141 truncate storage=File pool=Default
144 \subsection{New Resume Command}
145 This command does exactly the same thing as a
146 {\bf restart} command but for some users the
147 name may be more logical since in general the
148 {\bf restart} command is used to rerun running
149 a Job that had been canceled or had failed.
151 \subsection{Migration/Copy/VirtualFull Performance Enhancements}
152 The Bacula Storage daemon now permits multiple jobs to simultaneously read
153 the same disk Volume, which gives substantial performance enhancements when
154 running Migration, Copy, or VirtualFull jobs that read disk Volumes. Our
155 testing shows that when running multiple simultaneous jobs, the jobs can
156 finish up to ten times faster with this version of Bacula. This is
157 built-in to the Storage daemon, so it happens automatically and
160 \subsection{VirtualFull Backup Consolidation Enhancements}
161 By default Bacula selects jobs automatically for a VirtualFull,
162 however, you may want to create the Virtual backup based on a
163 particular backup (point in time) that exists.
165 For example, if you have the following backup Jobs in your catalog:
167 +-------+---------+-------+----------+----------+-----------+
168 | JobId | Name | Level | JobFiles | JobBytes | JobStatus |
169 +-------+---------+-------+----------+----------+-----------+
170 | 1 | Vbackup | F | 1754 | 50118554 | T |
171 | 2 | Vbackup | I | 1 | 4 | T |
172 | 3 | Vbackup | I | 1 | 4 | T |
173 | 4 | Vbackup | D | 2 | 8 | T |
174 | 5 | Vbackup | I | 1 | 6 | T |
175 | 6 | Vbackup | I | 10 | 60 | T |
176 | 7 | Vbackup | I | 11 | 65 | T |
177 | 8 | Save | F | 1758 | 50118564 | T |
178 +-------+---------+-------+----------+----------+-----------+
181 and you want to consolidate only the first 3 jobs and create a
182 virtual backup equivalent to Job 1 + Job 2 + Job 3, you will use
183 \texttt{jobid=3} in the \texttt{run} command, then Bacula will select the
184 previous Full backup, the previous Differential (if any) and all subsequent
188 run job=Vbackup jobid=3 level=VirtualFull
191 If you want to consolidate a specific job list, you must specify the exact
192 list of jobs to merge in the run command line. For example, to consolidate
193 the last Differential and all subsequent Incremental, you will use
194 \texttt{jobid=4,5,6,7} or \texttt{jobid=4-7} on the run command line. As one
195 of the Job in the list is a Differential backup, Bacula will set the new job
196 level to Differential. If the list is composed only with Incremental jobs,
197 the new job will have a level set to Incremental.
200 run job=Vbackup jobid=4-7 level=VirtualFull
203 When using this feature, Bacula will automatically discard jobs that are
204 not related to the current Job. For example, specifying
205 \texttt{jobid=7,8}, Bacula will discard JobId 8 because it is not
206 part of the same backup Job.
208 We do not recommend it, but really want to consolidate jobs that have
209 different names (so probably different clients, filesets, etc...), you must
210 use \texttt{alljobid=} keyword instead of \texttt{jobid=}.
213 run job=Vbackup alljobid=1-3,6-8 level=VirtualFull
217 \subsection{FD Storage Address}
219 When the Director is behind a NAT, in a WAN area, to connect to
221 the StorageDaemon, the Director uses an ``external'' ip address,
222 and the FileDaemon should use an ``internal'' IP address to contact the
225 The normal way to handle this situation is to use a canonical name such as
226 ``storage-server'' that will be resolved on the Director side as the WAN
227 address and on the Client side as the LAN address. This is now possible to
228 configure this parameter using the new directive \texttt{FDStorageAddress} in
229 the Storage or Client resource.
232 \includegraphics[width=0.8\linewidth]{BackupOverWan1}
233 \label{fig:fdstorageaddress}
239 FD Storage Address = 10.0.0.1
245 % # or in the Client resouce
252 FD Storage Address = 10.0.0.1
258 Note that using the Client \texttt{FDStorageAddress} directive will not allow
259 to use multiple Storage Daemon, all Backup or Restore requests will be sent to
260 the specified \texttt{FDStorageAddress}.
262 \subsection{Job Bandwidth Limitation}
264 The new {\bf Job Bandwidth Limitation} directive may be added to the File
265 daemon's and/or Director's configuration to limit the bandwidth used by a
266 Job on a Client. It can be set in the File daemon's conf file for all Jobs
267 run in that File daemon, or it can be set for each Job in the Director's
268 conf file. The speed is always specified in bytes per second.
274 Working Directory = /some/path
275 Pid Directory = /some/path
277 Maximum Bandwidth Per Job = 5Mb/s
281 The above example would cause any jobs running with the FileDaemon to not
282 exceed 5 megabytes per second of throughput when sending data to the
283 Storage Daemon. Note, the speed is always specified in bytes per second
284 (not in bits per second), and the case (upper/lower) of the specification
285 characters is ignored (i.e. 1MB/s = 1Mb/s).
287 You may specify the following speed parameter modifiers:
288 k/s (1,000 bytes per second), kb/s (1,024 bytes per second),
289 m/s (1,000,000 bytes per second), or mb/s (1,048,576 bytes per second).
295 FileSet = FS_localhost
298 Maximum Bandwidth = 5Mb/s
303 The above example would cause Job \texttt{localhost-data} to not exceed 5MB/s
304 of throughput when sending data from the File daemon to the Storage daemon.
306 A new console command \texttt{setbandwidth} permits to set dynamically the
307 maximum throughput of a running Job or for future jobs of a Client.
310 * setbandwidth limit=1000 jobid=10
313 Please note that the value specified for the \texttt{limit} command
314 line parameter is always in units of 1024 bytes (i.e. the number
315 is multiplied by 1024 to give the number of bytes per second). As
316 a consequence, the above limit of 1000 will be interpreted as a
317 limit of 1000 * 1024 = 1,024,000 bytes per second.
320 This project was funded by Bacula Systems.
323 \subsection{Maximum Concurrent Read Jobs}
324 This is a new directive that can be used in the {\bf bacula-dir.conf} file
325 in the Storage resource. The main purpose is to limit the number
326 of concurrent Copy, Migration, and VirtualFull jobs so that
327 they don't monopolize all the Storage drives causing a deadlock situation
328 where all the drives are allocated for reading but none remain for
329 writing. This deadlock situation can occur when running multiple
330 simultaneous Copy, Migration, and VirtualFull jobs.
333 The default value is set to 0 (zero), which means there is no
334 limit on the number of read jobs. Note, limiting the read jobs
335 does not apply to Restore jobs, which are normally started by
336 hand. A reasonable value for this directive is one half the number
337 of drives that the Storage resource has rounded down. Doing so,
338 will leave the same number of drives for writing and will generally
339 avoid over committing drives and a deadlock.
342 \subsection{Director job Codes in Message Resource Commands}
343 Before submitting the specified mail command to the operating system, Bacula
344 performs character substitution like in Runscript commands. Bacula will now
345 perform also specific Director character substitution.
348 The code for this feature was contributed by Bastian Friedrich.
350 \subsection{Additions to RunScript variables}
351 The following variables are now available in runscripts:
353 \item current PID using \%P
354 \item if the job is a clone job using \%C
358 RunAfterJob = "/bin/echo Pid=%P isCloned=%C"
362 \subsection{Read Only Storage Devices}
363 This version of Bacula permits defining a Storage daemon device
364 to be read-only. That is if the {\bf ReadOnly} directive is specified and
365 enabled, the drive can only be used for read operations.
366 The the {\bf ReadOnly} directive can be defined in any bacula-sd.conf
367 Device resource, and is most useful to reserve one or more
368 drives for restores. An example is:
374 \subsection{New Prune ``Expired'' Volume Command}
375 It is now possible to prune all volumes
376 (from a pool, or globally) that are ``expired''. This option can be
377 scheduled after or before the backup of the Catalog and can be
378 combined with the Truncate On Purge option. The Expired Prune option can
379 be used instead of the \texttt{manual\_prune.pl} script.
382 * prune expired volumes
384 * prune expired volumes pool=FullPool
387 To schedule this option automatically, it can be added to the BackupCatalog job
395 Console = "prune expired volume yes"
401 \subsection{Hardlink Performance Enhancements}
402 If you use a program such as Cyrus IMAP that creates very large numbers
403 of hardlinks, the time to build the interactive restore tree can be
404 excessively long. This version of Bacula has a new feature that
405 automatically keeps the hardlinks associated with the restore tree
406 in memory, which consumes a bit more memory but vastly speeds up
407 building the tree. If the memory usage is too big for your system, you
408 can reduce the amount of memory used during the restore command by
409 adding the option {\bf optimizespeed=false} on the bconsole run
412 This feature was developed by Josip Almasi, and enhanced to be runtime
413 dynamic by Kern Sibbald.
415 \subsection{DisableCommand Directive}
416 There is a new Directive named {\bf Disable Command} that
417 can be put in the File daemon Client or Director resource.
418 If it is in the Client, it applies globally, otherwise the
419 directive applies only to the Director in which it is found.
420 The Disable Command adds security to your File daemon by
421 disabling certain commands. The commands that can be
447 On or more of these command keywords can be placed in quotes and separated
448 by spaces on the Disable Command directive line. Note: the commands must
449 be written exactly as they appear above.
451 \subsection{Multiple Console Directors}
452 Support for multiple bconsole and bat Directors in the bconsole.conf and
453 bat.conf files has been implemented and/or improved.
455 \subsection{Restricted Consoles}
456 Better support for Restricted consoles has been implement for bconsole and
459 \subsection{Configuration Files}
460 In previous versions of Bacula the configuration files for each component
461 were limited to a maximum of 499 bytes per configuration file line. This
462 version of Bacula permits unlimited input line lengths. This can be
463 especially useful for specifying more complicated Migration/Copy SQL
464 statements and in creating long restricted console ACL lists.
466 \subsection{Maximum Spawned Jobs}
467 The Job resource now permits specifying a number of {\bf Maximum Spawn
468 Jobs}. The default is 300. This directive can be useful if you have
469 big hardware and you do a lot of Migration/Copy jobs which start
470 at the same time. In prior versions of Bacula, Migration/Copy
471 was limited to spawning a maximum of 100 jobs at a time.
473 \subsection{Progress Meter}
474 The new File daemon has been enhanced to send its progress (files
475 processed and bytes written) to the Director every 30 seconds. These
476 figures can then be displayed with a bconsole {\bf status dir}
479 \subsection{Scheduling a 6th Week}
480 Prior version of Bacula permits specifying 1st through 5th week of
481 a month (first through fifth) as a keyword on the {\bf run}
482 directive of a Schedule resource. This version of Bacula also permits
483 specifying the 6th week of a month with the keyword {\bf sixth} or
486 \subsection{Scheduling the Last Day of a Month}
487 This version of Bacula now permits specifying the {\bf lastday}
488 keyword in the {\bf run} directive of a Schedule resource.
489 If {\bf lastday} is specified, it will apply only to those months
490 specified on the {\bf run} directive. Note: by default all months
493 \subsection{Improvements to Cancel and Restart bconsole Commands}
494 The Restart bconsole command now allow selection of either
495 canceled or failed jobs to be restarted. In addition both the
496 {\bf cancel} and {\bf restart} bconsole commands permit entering
497 a number of JobIds separated by commas or a range of JobIds indicated
498 by a dash between the begin and end range (e.g. 3-10). Finally the
499 two commands also allow one to enter the special keyword {\bf all}
500 to select all the appropriate Jobs.
502 \subsection{bconsole Performance Improvements}
503 In previous versions of Bacula certain bconsole commands could wait a long
504 time due to catalog lock contention. This was especially noticeable
505 when a large number of jobs were running and putting their attributes
506 into the catalog. This version uses a separate catalog connection that
507 should significantly enhance performance.
509 \subsection{New .bvfs\_decode\_lstat Command}
510 There is a new bconsole command, which is
511 {\bf .bvfs\_decode\_lstat} it requires one argument, which
512 is {\bf lstat="lstat value to decode"}. An example command
513 in bconsole and the output might be:
517 .bvfs_decode_lstat lstat="A A EHt B A A A JP BAA B BTL/A7 BTL/A7 BTL/A7 A A C"
535 \subsection*{New Debug Options}
537 In Bacula Enterprise version 8.0 and later, we introduced new options to
538 the \texttt{setdebug} command.
542 If the \texttt{options} parameter is set, the following arguments can be
543 used to control debug functions.
546 \item [0] clear debug flags
547 \item [i] Turn off, ignore bwrite() errors on restore on File Daemon
548 \item [d] Turn off decomp of BackupRead() streams on File Daemon
549 \item [t] Turn on timestamp in traces
550 \item [T] Turn off timestamp in traces
551 \item [c] Truncate trace file if trace file is activated
552 \item [l] Turn on recoding events on P() and V()
553 \item [p] Turn on the display of the event ring when doing a bactrace
558 The following command will truncate the trace file and will turn on timestamps
562 * setdebug level=10 trace=1 options=ct fd
567 It is now possible to use \textsl{class} of debug messages called \texttt{tags}
568 to control the debug output of Bacula daemons.
571 \item [all] Display all debug messages
572 \item [bvfs] Display BVFS debug messages
573 \item [sql] Display SQL related debug messages
574 \item [memory] Display memory and poolmem allocation messages
575 \item [scheduler] Display scheduler related debug messages
579 * setdebug level=10 tags=bvfs,sql,memory
580 * setdebug level=10 tags=!bvfs
582 # bacula-dir -t -d 200,bvfs,sql
585 The \texttt{tags} option is composed of a list of tags, tags are separated by
586 ``,'' or ``+'' or ``-'' or ``!''. To disable a specific tag, use ``-'' or ``!''
587 in front of the tag. Note that more tags will come in future versions.
589 %\LTXtable{\linewidth}{table_debugtags}
592 \chapter{New Features in 5.2.13}
593 This chapter presents the new features that have been added to the current
594 Community version of Bacula that is now released.
596 \subsection{Additions to RunScript variables}
597 You can have access to Director name using \%D in your runscript
601 RunAfterJob = "/bin/echo Director=%D
604 \section{New Features in 5.2.1}
605 This chapter presents the new features were added in the
606 Community release version 5.2.1.
608 There are additional features (plugins) available in the Enterprise version
609 that are described in another chapter. A subscription to Bacula Systems
610 is required for the Enterprise version.
612 \subsection{LZO Compression}
614 LZO compression has been to the File daemon. From the user's point of view,
615 it works like the GZIP compression (just replace {\bf compression=GZIP} with
616 {\bf compression=LZO}).
621 Options {compression=LZO }
627 LZO provides a much faster compression and decompression speed but lower
628 compression ratio than GZIP. It is a good option when you backup to disk. For
629 tape, the hardware compression is almost always a better option.
631 LZO is a good alternative for GZIP1 when you don't want to slow down your
632 backup. With a modern CPU it should be able to run almost as fast as:
635 \item your client can read data from disk. Unless you have very fast disks like
636 SSD or large/fast RAID array.
637 \item the data transfers between the file daemon and the storage daemon even on
641 Note, Bacula uses compression level LZO1X-1.
644 The code for this feature was contributed by Laurent Papier.
646 \subsection{New Tray Monitor}
648 Since the old integrated Windows tray monitor doesn't work with
649 recent Windows versions, we have written a new Qt Tray Monitor that is available
650 for both Linux and Windows. In addition to all the previous features,
651 this new version allows you to run Backups from
652 the tray monitor menu.
656 \includegraphics[width=0.8\linewidth]{tray-monitor}
657 \label{fig:traymonitor}
658 \caption{New tray monitor}
663 \includegraphics[width=0.8\linewidth]{tray-monitor1}
664 \label{fig:traymonitor1}
665 \caption{Run a Job through the new tray monitor}
669 To be able to run a job from the tray monitor, you need to
670 allow specific commands in the Director monitor console:
675 CommandACL = status, .clients, .jobs, .pools, .storage, .filesets, .messages, run
676 ClientACL = *all* # you can restrict to a specific host
688 This project was funded by Bacula Systems and is available with Bacula
689 the Enterprise Edition and the Community Edition.
691 \subsection{Purge Migration Job}
693 The new {\bf Purge Migration Job} directive may be added to the Migration
694 Job definition in the Director's configuration file. When it is enabled
695 the Job that was migrated during a migration will be purged at
696 the end of the migration job.
704 Client = localhost-fd
707 Storage = DiskChanger
710 Selection Pattern = ".*Save"
712 Purge Migration Job = yes
718 This project was submitted by Dunlap Blake; testing and documentation was funded
721 \subsection{Changes in Bvfs (Bacula Virtual FileSystem)}
723 Bat has now a bRestore panel that uses Bvfs to display files and
728 \includegraphics[width=0.8\linewidth]{bat-brestore}
729 \label{fig:batbrestore}
730 \caption{Bat Brestore Panel}
733 the Bvfs module works correctly with BaseJobs, Copy and Migration jobs.
736 This project was funded by Bacula Systems.
738 \subsubsection*{General notes}
741 \item All fields are separated by a tab
742 \item You can specify \texttt{limit=} and \texttt{offset=} to list smoothly
743 records in very big directories
744 \item All operations (except cache creation) are designed to run instantly
745 \item At this time, Bvfs works faster on PostgreSQL than MySQL catalog. If you
746 can contribute new faster SQL queries we will be happy, else don't complain
748 \item The cache creation is dependent of the number of directories. As Bvfs
749 shares information across jobs, the first creation can be slow
750 \item All fields are separated by a tab
751 \item Due to potential encoding problem, it's advised to always use pathid in
755 \subsubsection*{Get dependent jobs from a given JobId}
757 Bvfs allows you to query the catalog against any combination of jobs. You
758 can combine all Jobs and all FileSet for a Client in a single session.
760 To get all JobId needed to restore a particular job, you can use the
761 \texttt{.bvfs\_get\_jobids} command.
764 .bvfs_get_jobids jobid=num [all]
768 .bvfs_get_jobids jobid=10
770 .bvfs_get_jobids jobid=10 all
774 In this example, a normal restore will need to use JobIds 1,2,5,10 to
775 compute a complete restore of the system.
777 With the \texttt{all} option, the Director will use all defined FileSet for
780 \subsubsection*{Generating Bvfs cache}
782 The \texttt{.bvfs\_update} command computes the directory cache for jobs
783 specified in argument, or for all jobs if unspecified.
786 .bvfs_update [jobid=numlist]
791 .bvfs_update jobid=1,2,3
794 You can run the cache update process in a RunScript after the catalog backup.
796 \subsubsection*{Get all versions of a specific file}
798 Bvfs allows you to find all versions of a specific file for a given Client with
799 the \texttt{.bvfs\_version} command. To avoid problems with encoding, this
800 function uses only PathId and FilenameId. The jobid argument is mandatory but
804 .bvfs_versions client=filedaemon pathid=num filenameid=num jobid=1
805 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
806 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
813 .bvfs_versions client=localhost-fd pathid=1 fnid=47 jobid=1
814 1 47 52 12 gD HRid IGk D Po Po A P BAA I A /uPgWaxMgKZlnMti7LChyA Vol1 1
817 \subsubsection*{List directories}
819 Bvfs allows you to list directories in a specific path.
821 .bvfs_lsdirs pathid=num path=/apath jobid=numlist limit=num offset=num
822 PathId FilenameId FileId JobId LStat Path
823 PathId FilenameId FileId JobId LStat Path
824 PathId FilenameId FileId JobId LStat Path
828 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
829 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record
830 listed is a directory.
833 .bvfs_lsdirs pathid=4 jobid=1,11,12
834 4 0 0 0 A A A A A A A A A A A A A A .
835 5 0 0 0 A A A A A A A A A A A A A A ..
836 3 0 0 0 A A A A A A A A A A A A A A regress/
839 In this example, to list directories present in \texttt{regress/}, you can use
841 .bvfs_lsdirs pathid=3 jobid=1,11,12
842 3 0 0 0 A A A A A A A A A A A A A A .
843 4 0 0 0 A A A A A A A A A A A A A A ..
844 2 0 0 0 A A A A A A A A A A A A A A tmp/
847 \subsubsection*{List files}
849 Bvfs allows you to list files in a specific path.
851 .bvfs_lsfiles pathid=num path=/apath jobid=numlist limit=num offset=num
852 PathId FilenameId FileId JobId LStat Path
853 PathId FilenameId FileId JobId LStat Path
854 PathId FilenameId FileId JobId LStat Path
858 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
859 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record listed
863 .bvfs_lsfiles pathid=4 jobid=1,11,12
864 4 0 0 0 A A A A A A A A A A A A A A .
865 5 0 0 0 A A A A A A A A A A A A A A ..
866 1 0 0 0 A A A A A A A A A A A A A A regress/
869 In this example, to list files present in \texttt{regress/}, you can use
871 .bvfs_lsfiles pathid=1 jobid=1,11,12
872 1 47 52 12 gD HRid IGk BAA I BMqcPH BMqcPE BMqe+t A titi
873 1 49 53 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B toto
874 1 48 54 12 gD HRie IGk BAA I BMqcPH BMqcPE BMqe+3 A tutu
875 1 45 55 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B ficheriro1.txt
876 1 46 56 12 gD HRie IGk BAA I BMqe/K BMqcPE BMqe+3 D ficheriro2.txt
879 \subsubsection*{Restore set of files}
881 Bvfs allows you to create a SQL table that contains files that you want to
882 restore. This table can be provided to a restore command with the file option.
885 .bvfs_restore fileid=numlist dirid=numlist hardlink=numlist path=b2num
887 restore file=?b2num ...
890 To include a directory (with \texttt{dirid}), Bvfs needs to run a query to
891 select all files. This query could be time consuming.
893 \texttt{hardlink} list is always composed of a series of two numbers (jobid,
894 fileindex). This information can be found in the LinkFI field of the LStat
897 The \texttt{path} argument represents the name of the table that Bvfs will
898 store results. The format of this table is \texttt{b2[0-9]+}. (Should start by
899 b2 and followed by digits).
904 .bvfs_restore fileid=1,2,3,4 hardlink=10,15,10,20 jobid=10 path=b20001
908 \subsubsection*{Cleanup after Restore}
910 To drop the table used by the restore command, you can use the
911 \texttt{.bvfs\_cleanup} command.
914 .bvfs_cleanup path=b20001
917 \subsubsection*{Clearing the BVFS Cache}
919 To clear the BVFS cache, you can use the \texttt{.bvfs\_clear\_cache} command.
922 .bvfs_clear_cache yes
926 \subsection{Changes in the Pruning Algorithm}
928 We rewrote the job pruning algorithm in this version. Previously, in some users
929 reported that the pruning process at the end of jobs was very long. It should
930 not be longer the case. Now, Bacula won't prune automatically a Job if this
931 particular Job is needed to restore data. Example:
935 JobId: 2 Level: Incremental
936 JobId: 3 Level: Incremental
937 JobId: 4 Level: Differential
938 .. Other incrementals up to now
941 In this example, if the Job Retention defined in the Pool or in the Client
942 resource causes that Jobs with Jobid in 1,2,3,4 can be pruned, Bacula will
943 detect that JobId 1 and 4 are essential to restore data at the current state
944 and will prune only JobId 2 and 3.
946 \texttt{Important}, this change affect only the automatic pruning step after a
947 Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the
948 \texttt{VolumeRetention} period, important jobs can be pruned.
950 \subsection{Ability to Verify any specified Job}
951 You now have the ability to tell Bacula which Job should verify instead of
952 automatically verify just the last one.
954 This feature can be used with VolumeToCatalog, DiskToCatalog and Catalog level.
956 To verify a given job, just specify the Job jobid in argument when starting the
959 *run job=VerifyVolume jobid=1 level=VolumeToCatalog
961 JobName: VerifyVolume
962 Level: VolumeToCatalog
965 Pool: Default (From Job resource)
966 Storage: File (From Job resource)
967 Verify Job: VerifyVol.2010-09-08_14.17.17_03
968 Verify List: /tmp/regress/working/VerifyVol.bsr
969 When: 2010-09-08 14:17:31
971 OK to run? (yes/mod/no):
975 This project was funded by Bacula Systems and is available with Bacula
976 Enterprise Edition and Community Edition.
978 \subsection{Additions to RunScript variables}
979 You can have access to JobBytes and JobFiles using \%b and \%F in your runscript
980 command. The Client address is now available through \%h.
983 RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%F ClientAddress=%h"
986 %\subsection{Changes in drivetype.exe}
988 %Now the \texttt{drivetype.exe} program allows you to list all local hard
989 %drives. It can help to build dynamic FileSet on Windows.
992 %File = "\\|\"c:/program files/bacula/bin32/drivetype\" -l -a"
996 \subsection{Additions to the Plugin API}
997 The bfuncs structure has been extended to include a number of
1000 \subsubsection{bfuncs}
1001 The bFuncs structure defines the callback entry points within Bacula
1002 that the plugin can use register events, get Bacula values, set
1003 Bacula values, and send messages to the Job output or debug output.
1005 The exact definition as of this writing is:
1007 typedef struct s_baculaFuncs {
1010 bRC (*registerBaculaEvents)(bpContext *ctx, ...);
1011 bRC (*getBaculaValue)(bpContext *ctx, bVariable var, void *value);
1012 bRC (*setBaculaValue)(bpContext *ctx, bVariable var, void *value);
1013 bRC (*JobMessage)(bpContext *ctx, const char *file, int line,
1014 int type, utime_t mtime, const char *fmt, ...);
1015 bRC (*DebugMessage)(bpContext *ctx, const char *file, int line,
1016 int level, const char *fmt, ...);
1017 void *(*baculaMalloc)(bpContext *ctx, const char *file, int line,
1019 void (*baculaFree)(bpContext *ctx, const char *file, int line, void *mem);
1021 /* New functions follow */
1022 bRC (*AddExclude)(bpContext *ctx, const char *file);
1023 bRC (*AddInclude)(bpContext *ctx, const char *file);
1024 bRC (*AddIncludeOptions)(bpContext *ctx, const char *opts);
1025 bRC (*AddRegex)(bpContext *ctx, const char *item, int type);
1026 bRC (*AddWild)(bpContext *ctx, const char *item, int type);
1027 bRC (*checkChanges)(bpContext *ctx, struct save_pkt *sp);
1033 \item [AddExclude] can be called to exclude a file. The file
1034 string passed may include wildcards that will be interpreted by
1035 the {\bf fnmatch} subroutine. This function can be called
1036 multiple times, and each time the file specified will be added
1037 to the list of files to be excluded. Note, this function only
1038 permits adding excludes of specific file or directory names,
1039 or files matched by the rather simple fnmatch mechanism.
1040 See below for information on doing wild-card and regex excludes.
1042 \item [NewPreInclude] can be called to create a new Include block. This
1043 block will be added after the current defined Include block. This
1044 function can be called multiple times, but each time, it will create
1045 a new Include section (not normally needed). This function should
1046 be called only if you want to add an entirely new Include block.
1048 \item [NewInclude] can be called to create a new Include block. This
1049 block will be added before any user defined Include blocks. This
1050 function can be called multiple times, but each time, it will create
1051 a new Include section (not normally needed). This function should
1052 be called only if you want to add an entirely new Include block.
1054 \item [AddInclude] can be called to add new files/directories to
1055 be included. They are added to the current Include block. If
1056 NewInclude has not been included, the current Include block is
1057 the last one that the user created. This function
1058 should be used only if you want to add totally new files/directories
1059 to be included in the backup.
1061 \item [NewOptions] adds a new Options block to the current Include
1062 in front of any other Options blocks. This permits the plugin to
1063 add exclude directives (wild-cards and regexes) in front of the
1064 user Options, and thus prevent certain files from being backed up.
1065 This can be useful if the plugin backs up files, and they should
1066 not be also backed up by the main Bacula code. This function
1067 may be called multiple times, and each time, it creates a new
1068 prepended Options block. Note: normally you want to call this
1069 entry point prior to calling AddOptions, AddRegex, or AddWild.
1071 \item [AddOptions] allows the plugin it set options in
1072 the current Options block, which is normally created with the
1073 NewOptions call just prior to adding Include Options.
1074 The permitted options are passed as a character string, where
1075 each character has a specific meaning as defined below:
1078 \item [a] always replace files (default).
1079 \item [e] exclude rather than include.
1080 \item [h] no recursion into subdirectories.
1081 \item [H] do not handle hard links.
1082 \item [i] ignore case in wildcard and regex matches.
1083 \item [M] compute an MD5 sum.
1084 \item [p] use a portable data format on Windows (not recommended).
1085 \item [R] backup resource forks and Findr Info.
1086 \item [r] read from a fifo
1087 \item [S1] compute an SHA1 sum.
1088 \item [S2] compute an SHA256 sum.
1089 \item [S3] comput an SHA512 sum.
1090 \item [s] handle sparse files.
1091 \item [m] use st\_mtime only for file differences.
1092 \item [k] restore the st\_atime after accessing a file.
1093 \item [A] enable ACL backup.
1094 \item [Vxxx:] specify verify options. Must terminate with :
1095 \item [Cxxx:] specify accurate options. Must terminate with :
1096 \item [Jxxx:] specify base job Options. Must terminate with :
1097 \item [Pnnn:] specify integer nnn paths to strip. Must terminate with :
1099 \item [Zn] specify gzip compression level n.
1100 \item [K] do not use st\_atime in backup decision.
1101 \item [c] check if file changed during backup.
1102 \item [N] honor no dump flag.
1103 \item [X] enable backup of extended attributes.
1106 \item [AddRegex] adds a regex expression to the current Options block.
1107 The following options are permitted:
1109 \item [ ] (a blank) regex applies to whole path and filename.
1110 \item [F] regex applies only to the filename (directory or path stripped).
1111 \item [D] regex applies only to the directory (path) part of the name.
1114 \item [AddWild] adds a wildcard expression to the current Options block.
1115 The following options are permitted:
1117 \item [ ] (a blank) regex applies to whole path and filename.
1118 \item [F] regex applies only to the filename (directory or path stripped).
1119 \item [D] regex applies only to the directory (path) part of the name.
1122 \item [checkChanges] call the \texttt{check\_changes()} function in Bacula code
1123 that can use Accurate code to compare the file information in argument with
1124 the previous file information. The \texttt{delta\_seq} attribute of the
1125 \texttt{save\_pkt} will be updated, and the call will return
1126 \texttt{bRC\_Seen} if the core code wouldn't decide to backup it.
1131 \subsubsection{Bacula events}
1132 The list of events has been extended to include:
1138 bEventStartBackupJob = 3,
1139 bEventEndBackupJob = 4,
1140 bEventStartRestoreJob = 5,
1141 bEventEndRestoreJob = 6,
1142 bEventStartVerifyJob = 7,
1143 bEventEndVerifyJob = 8,
1144 bEventBackupCommand = 9,
1145 bEventRestoreCommand = 10,
1150 bEventCancelCommand = 13,
1151 bEventVssBackupAddComponents = 14,
1152 bEventVssRestoreLoadComponentMetadata = 15,
1153 bEventVssRestoreSetComponentsSelected = 16,
1154 bEventRestoreObject = 17,
1155 bEventEndFileSet = 18,
1156 bEventPluginCommand = 19,
1157 bEventVssBeforeCloseRestore = 20,
1158 bEventVssPrepareSnapshot = 21
1164 \item [bEventCancelCommand] is called whenever the currently
1165 running Job is canceled */
1167 \item [bEventVssBackupAddComponents]
1169 \item [bEventVssPrepareSnapshot] is called before creating VSS snapshots, it
1170 provides a char[27] table where the plugin can add Windows drives that will
1171 be used during the Job. You need to add them without duplicates, and you can
1172 use in \texttt{fd\_common.h} \texttt{add\_drive()} and \texttt{copy\_drives()}
1176 \subsection{ACL enhancements}
1178 The following enhancements are made to the Bacula Filed with regards to
1179 Access Control Lists (ACLs)
1182 \item Added support for AIX 5.3 and later new aclx\_get interface which supports
1183 POSIX and NFSv4 ACLs.
1184 \item Added support for new acl types on FreeBSD 8.1 and later which supports
1185 POSIX and NFSv4 ACLs.
1186 \item Some generic cleanups for internal ACL handling.
1187 \item Fix for acl storage on OSX
1188 \item Cleanup of configure checks for ACL detection, now configure only
1189 tests for a certain interface type based on the operating system
1190 this should give less false positives on detection. Also when ACLs
1191 are detected no other acl checks are performed anymore.
1195 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
1196 and is available with Bacula Enterprise Edition and Community Edition.
1198 \subsection{XATTR enhancements}
1200 The following enhancements are made to the Bacula Filed with regards to
1201 Extended Attributes (XATTRs)
1204 \item Added support for IRIX extended attributes using the attr\_get interface.
1205 \item Added support for Tru64 (OSF1) extended attributes using the
1206 getproplist interface.
1207 \item Added support for AIX extended attributes available in AIX 6.x
1208 and higher using the listea/getea/setea interface.
1209 \item Added some debugging to generic xattr code so it easier to
1211 \item Cleanup of configure checks for XATTR detection, now configure only
1212 tests for a certain interface type based on the operating system
1213 this should give less false positives on detection. Also when xattrs
1214 are detected no other xattr checks are performed anymore.
1218 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
1219 and is available with Bacula Enterprise Edition and Community Edition.
1221 \subsection{Class Based Database Backend Drivers}
1223 The main Bacula Director code is independent of the SQL backend
1224 in version 5.2.0 and greater. This means that the Bacula Director can be
1225 packaged by itself, then each of the different SQL backends supported can
1226 be packaged separately. It is possible to build all the DB backends at the
1227 same time by including multiple database options at the same time.
1229 ./configure can be run with multiple database configure options.
1236 Order of testing for databases is:
1243 Each configured backend generates a file named:
1244 \verb+libbaccats-<sql_backend_name>-<version>.so+
1245 A dummy catalog library is created named libbaccats-version.so
1247 At configure time the first detected backend is used as the so called
1248 default backend and at install time the dummy
1249 \verb+libbaccats-<version>.so+ is replaced with the default backend type.
1251 If you configure all three backends you get three backend libraries and the
1252 postgresql gets installed as the default.
1254 When you want to switch to another database, first save any old catalog you
1255 may have then you can copy one of the three backend libraries over the
1256 \verb+libbaccats-<version>.so+ e.g.
1258 An actual command, depending on your Bacula version might be:
1260 cp libbaccats-postgresql-5.2.2.so libbaccats-5.2.2.so
1263 where the \verb+5.2.2+ must be replaced by the Bacula release
1266 Then you must update the default backend in the following files:
1269 create_bacula_database
1270 drop_bacula_database
1272 grant_bacula_privileges
1275 update_bacula_tables
1278 And re-run all the above scripts. Please note, this means
1279 you will have a new empty database and if you had a previous
1280 one it will be lost.
1282 All current database backend drivers for catalog information are rewritten
1283 to use a set of multi inherited C++ classes which abstract the specific
1284 database specific internals and make sure we have a more stable generic
1285 interface with the rest of SQL code. From now on there is a strict
1286 boundary between the SQL code and the low-level database functions. This
1287 new interface should also make it easier to add a new backend for a
1288 currently unsupported database. As part of the rewrite the SQLite 2 code
1289 was removed (e.g. only SQLite 3 is now supported). An extra bonus of the
1290 new code is that you can configure multiple backends in the configure and
1291 build all backends in one compile session and select the correct database
1292 backend at install time. This should make it a lot easier for packages
1298 We also added cursor support for PostgreSQL backend, this improves memory
1299 usage for large installation.
1302 This project was implemented by Planets Communications B.V. and ELM
1303 Consultancy B.V. and Bacula Systems and is available with both the Bacula
1304 Enterprise Edition and the Community Edition.
1306 \subsection{Hash List Enhancements}
1308 The htable hash table class has been extended with extra hash functions for
1309 handling next to char pointer hashes also 32 bits and 64 bits hash keys.
1310 Also the hash table initialization routines have been enhanced with
1311 support for passing a hint as to the number of initial pages to use
1312 for the size of the hash table. Until now the hash table always used
1313 a fixed value of 10 Mb. The private hash functions of the mountpoint entry
1314 cache have been rewritten to use the new htable class with a small memory
1318 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
1319 and Bacula Systems and is available with Bacula Enterprise Edition and
1324 %%% =====================================================================
1329 \section{Release Version 5.0.3}
1331 There are no new features in version 5.0.2. This version simply fixes a
1332 number of bugs found in version 5.0.1 during the ongoing development
1335 \section{Release Version 5.0.2}
1337 There are no new features in version 5.0.2. This version simply fixes a
1338 number of bugs found in version 5.0.1 during the ongoing development
1344 \section{New Features in 5.0.1}
1346 This chapter presents the new features that are in the released Bacula version
1347 5.0.1. This version mainly fixes a number of bugs found in version 5.0.0 during
1348 the ongoing development process.
1350 \subsection{Truncate Volume after Purge}
1351 \label{sec:actiononpurge}
1353 The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate
1354 the volume when it is purged with the new command \texttt{purge volume
1355 action}. It is useful to prevent disk based volumes from consuming too much
1361 Action On Purge = Truncate
1366 As usual you can also set this property with the \texttt{update volume} command
1368 *update volume=xxx ActionOnPurge=Truncate
1369 *update volume=xxx actiononpurge=None
1372 To ask Bacula to truncate your \texttt{Purged} volumes, you need to use the
1373 following command in interactive mode or in a RunScript as shown after:
1375 *purge volume action=truncate storage=File allpools
1376 # or by default, action=all
1377 *purge volume action storage=File pool=Default
1380 This is possible to specify the volume name, the media type, the pool, the
1381 storage, etc\dots (see \texttt{help purge}) Be sure that your storage device is
1382 idle when you decide to run this command.
1386 Name = CatalogBackup
1391 Console = "purge volume action=all allpools storage=File"
1396 \textbf{Important note}: This feature doesn't work as
1397 expected in version 5.0.0. Please do not use it before version 5.0.1.
1399 \subsection{Allow Higher Duplicates}
1400 This directive did not work correctly and has been depreciated
1401 (disabled) in version 5.0.1. Please remove it from your bacula-dir.conf
1402 file as it will be removed in a future release.
1404 \subsection{Cancel Lower Level Duplicates}
1405 This directive was added in Bacula version 5.0.1. It compares the
1406 level of a new backup job to old jobs of the same name, if any,
1407 and will kill the job which has a lower level than the other one.
1408 If the levels are the same (i.e. both are Full backups), then
1409 nothing is done and the other Cancel XXX Duplicate directives
1412 \section{New Features in 5.0.0}
1414 \subsection{Maximum Concurrent Jobs for Devices}
1415 \label{sec:maximumconcurrentjobdevice}
1417 {\bf Maximum Concurrent Jobs} is a new Device directive in the Storage
1418 Daemon configuration permits setting the maximum number of Jobs that can
1419 run concurrently on a specified Device. Using this directive, it is
1420 possible to have different Jobs using multiple drives, because when the
1421 Maximum Concurrent Jobs limit is reached, the Storage Daemon will start new
1422 Jobs on any other available compatible drive. This facilitates writing to
1423 multiple drives with multiple Jobs that all use the same Pool.
1425 This project was funded by Bacula Systems.
1427 \subsection{Restore from Multiple Storage Daemons}
1428 \index[general]{Restore}
1430 Previously, you were able to restore from multiple devices in a single Storage
1431 Daemon. Now, Bacula is able to restore from multiple Storage Daemons. For
1432 example, if your full backup runs on a Storage Daemon with an autochanger, and
1433 your incremental jobs use another Storage Daemon with lots of disks, Bacula
1434 will switch automatically from one Storage Daemon to an other within the same
1437 You must upgrade your File Daemon to version 3.1.3 or greater to use this
1440 This project was funded by Bacula Systems with the help of Equiinet.
1442 \subsection{File Deduplication using Base Jobs}
1443 A base job is sort of like a Full save except that you will want the FileSet to
1444 contain only files that are unlikely to change in the future (i.e. a snapshot
1445 of most of your system after installing it). After the base job has been run,
1446 when you are doing a Full save, you specify one or more Base jobs to be used.
1447 All files that have been backed up in the Base job/jobs but not modified will
1448 then be excluded from the backup. During a restore, the Base jobs will be
1449 automatically pulled in where necessary.
1451 This is something none of the competition does, as far as we know (except
1452 perhaps BackupPC, which is a Perl program that saves to disk only). It is big
1453 win for the user, it makes Bacula stand out as offering a unique optimization
1454 that immediately saves time and money. Basically, imagine that you have 100
1455 nearly identical Windows or Linux machine containing the OS and user files.
1456 Now for the OS part, a Base job will be backed up once, and rather than making
1457 100 copies of the OS, there will be only one. If one or more of the systems
1458 have some files updated, no problem, they will be automatically restored.
1460 See the \ilink{Base Job Chapter}{basejobs} for more information.
1462 This project was funded by Bacula Systems.
1464 \subsection{AllowCompression = \lt{}yes\vb{}no\gt{}}
1465 \index[dir]{AllowCompression}
1467 This new directive may be added to Storage resource within the Director's
1468 configuration to allow users to selectively disable the client compression for
1469 any job which writes to this storage resource.
1475 Address = ultrium-tape
1476 Password = storage_password # Password for Storage Daemon
1479 AllowCompression = No # Tape drive has hardware compression
1482 The above example would cause any jobs running with the UltriumTape storage
1483 resource to run without compression from the client file daemons. This
1484 effectively overrides any compression settings defined at the FileSet level.
1486 This feature is probably most useful if you have a tape drive which supports
1487 hardware compression. By setting the \texttt{AllowCompression = No} directive
1488 for your tape drive storage resource, you can avoid additional load on the file
1489 daemon and possibly speed up tape backups.
1491 This project was funded by Collaborative Fusion, Inc.
1493 \subsection{Accurate Fileset Options}
1494 \label{sec:accuratefileset}
1496 In previous versions, the accurate code used the file creation and modification
1497 times to determine if a file was modified or not. Now you can specify which
1498 attributes to use (time, size, checksum, permission, owner, group, \dots),
1499 similar to the Verify options.
1515 \item {\bf i} compare the inodes
1516 \item {\bf p} compare the permission bits
1517 \item {\bf n} compare the number of links
1518 \item {\bf u} compare the user id
1519 \item {\bf g} compare the group id
1520 \item {\bf s} compare the size
1521 \item {\bf a} compare the access time
1522 \item {\bf m} compare the modification time (st\_mtime)
1523 \item {\bf c} compare the change time (st\_ctime)
1524 \item {\bf d} report file size decreases
1525 \item {\bf 5} compare the MD5 signature
1526 \item {\bf 1} compare the SHA1 signature
1529 \textbf{Important note:} If you decide to use checksum in Accurate jobs,
1530 the File Daemon will have to read all files even if they normally would not
1531 be saved. This increases the I/O load, but also the accuracy of the
1532 deduplication. By default, Bacula will check modification/creation time
1535 This project was funded by Bacula Systems.
1537 \subsection{Tab-completion for Bconsole}
1538 \label{sec:tabcompletion}
1540 If you build \texttt{bconsole} with readline support, you will be able to use
1541 the new auto-completion mode. This mode supports all commands, gives help
1542 inside command, and lists resources when required. It works also in the restore
1545 To use this feature, you should have readline development package loaded on
1546 your system, and use the following option in configure.
1548 ./configure --with-readline=/usr/include/readline --disable-conio ...
1551 The new bconsole won't be able to tab-complete with older directors.
1553 This project was funded by Bacula Systems.
1555 \subsection{Pool File and Job Retention}
1556 \label{sec:poolfilejobretention}
1558 We added two new Pool directives, \texttt{FileRetention} and
1559 \texttt{JobRetention}, that take precedence over Client directives of the same
1560 name. It allows you to control the Catalog pruning algorithm Pool by Pool. For
1561 example, you can decide to increase Retention times for Archive or OffSite Pool.
1563 It seems obvious to us, but apparently not to some users, that given the
1564 definition above that the Pool File and Job Retention periods is a global
1565 override for the normal Client based pruning, which means that when the
1566 Job is pruned, the pruning will apply globally to that particular Job.
1568 Currently, there is a bug in the implementation that causes any Pool
1569 retention periods specified to apply to {\bf all} Pools for that
1570 particular Client. Thus we suggest that you avoid using these two
1571 directives until this implementation problem is corrected.
1573 \subsection{Read-only File Daemon using capabilities}
1574 \label{sec:fdreadonly}
1575 This feature implements support of keeping \textbf{ReadAll} capabilities after
1576 UID/GID switch, this allows FD to keep root read but drop write permission.
1578 It introduces new \texttt{bacula-fd} option (\texttt{-k}) specifying that
1579 \textbf{ReadAll} capabilities should be kept after UID/GID switch.
1582 root@localhost:~# bacula-fd -k -u nobody -g nobody
1585 The code for this feature was contributed by our friends at AltLinux.
1587 \subsection{Bvfs API}
1590 To help developers of restore GUI interfaces, we have added new \textsl{dot
1591 commands} that permit browsing the catalog in a very simple way.
1594 \item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update
1595 the Bvfs cache in the catalog. You need to run it before any access to the
1598 \item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command
1599 will list all directories in the specified \texttt{path} or
1600 \texttt{pathid}. Using \texttt{pathid} avoids problems with character
1601 encoding of path/filenames.
1603 \item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command
1604 will list all files in the specified \texttt{path} or \texttt{pathid}. Using
1605 \texttt{pathid} avoids problems with character encoding.
1608 You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of
1609 data that will be displayed.
1612 * .bvfs_update jobid=1,2
1614 * .bvfs_lsdir path=/ jobid=1,2
1617 This project was funded by Bacula Systems.
1619 \subsection{Testing your Tape Drive}
1620 \label{sec:btapespeed}
1622 To determine the best configuration of your tape drive, you can run the new
1623 \texttt{speed} command available in the \texttt{btape} program.
1625 This command can have the following arguments:
1627 \item[\texttt{file\_size=n}] Specify the Maximum File Size for this test
1628 (between 1 and 5GB). This counter is in GB.
1629 \item[\texttt{nb\_file=n}] Specify the number of file to be written. The amount
1630 of data should be greater than your memory ($file\_size*nb\_file$).
1631 \item[\texttt{skip\_zero}] This flag permits to skip tests with constant
1633 \item[\texttt{skip\_random}] This flag permits to skip tests with random
1635 \item[\texttt{skip\_raw}] This flag permits to skip tests with raw access.
1636 \item[\texttt{skip\_block}] This flag permits to skip tests with Bacula block
1641 *speed file_size=3 skip_raw
1642 btape.c:1078 Test with zero data and bacula block structure.
1643 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
1644 ++++++++++++++++++++++++++++++++++++++++++
1645 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
1646 btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 MB/s
1648 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 MB/s
1650 btape.c:1090 Test with random data, should give the minimum throughput.
1651 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
1652 +++++++++++++++++++++++++++++++++++++++++++
1653 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
1654 btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 MB/s
1655 +++++++++++++++++++++++++++++++++++++++++++
1657 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s
1661 When using compression, the random test will give your the minimum throughput
1662 of your drive . The test using constant string will give you the maximum speed
1663 of your hardware chain. (CPU, memory, SCSI card, cable, drive, tape).
1665 You can change the block size in the Storage Daemon configuration file.
1667 \subsection{New {\bf Block Checksum} Device Directive}
1668 You may now turn off the Block Checksum (CRC32) code
1669 that Bacula uses when writing blocks to a Volume. This is
1676 doing so can reduce the Storage daemon CPU usage slightly. It
1677 will also permit Bacula to read a Volume that has corrupted data.
1679 The default is {\bf yes} -- i.e. the checksum is computed on write
1680 and checked on read.
1682 We do not recommend to turn this off particularly on older tape
1683 drives or for disk Volumes where doing so may allow corrupted data
1686 \subsection{New Bat Features}
1688 Those new features were funded by Bacula Systems.
1690 \subsubsection{Media List View}
1692 By clicking on ``Media'', you can see the list of all your volumes. You will be
1693 able to filter by Pool, Media Type, Location,\dots And sort the result directly
1694 in the table. The old ``Media'' view is now known as ``Pool''.
1695 \begin{figure}[htbp]
1697 \includegraphics[width=0.8\linewidth]{bat-mediaview}
1698 \label{fig:mediaview}
1702 \subsubsection{Media Information View}
1704 By double-clicking on a volume (on the Media list, in the Autochanger content
1705 or in the Job information panel), you can access a detailed overview of your
1706 Volume. (cf figure \vref{fig:mediainfo}.)
1707 \begin{figure}[htbp]
1709 \includegraphics[width=0.8\linewidth]{bat11}
1710 \caption{Media information}
1711 \label{fig:mediainfo}
1714 \subsubsection{Job Information View}
1716 By double-clicking on a Job record (on the Job run list or in the Media
1717 information panel), you can access a detailed overview of your Job. (cf
1718 figure \vref{fig:jobinfo}.)
1719 \begin{figure}[htbp]
1721 \includegraphics[width=0.8\linewidth]{bat12}
1722 \caption{Job information}
1726 \subsubsection{Autochanger Content View}
1728 By double-clicking on a Storage record (on the Storage list panel), you can
1729 access a detailed overview of your Autochanger. (cf figure \vref{fig:jobinfo}.)
1730 \begin{figure}[htbp]
1732 \includegraphics[width=0.8\linewidth]{bat13}
1733 \caption{Autochanger content}
1734 \label{fig:achcontent}
1737 To use this feature, you need to use the latest mtx-changer script
1738 version. (With new \texttt{listall} and \texttt{transfer} commands)
1740 \subsection{Bat on Windows}
1741 We have ported {\bf bat} to Windows and it is now installed
1742 by default when the installer is run. It works quite well
1743 on Win32, but has not had a lot of testing there, so your
1744 feedback would be welcome. Unfortunately, even though it is
1745 installed by default, it does not yet work on 64 bit Windows
1748 \subsection{New Win32 Installer}
1749 The Win32 installer has been modified in several very important
1752 \item You must deinstall any current version of the
1753 Win32 File daemon before upgrading to the new one.
1754 If you forget to do so, the new installation will fail.
1755 To correct this failure, you must manually shutdown
1756 and deinstall the old File daemon.
1757 \item All files (other than menu links) are installed
1758 in {\bf c:/Program Files/Bacula}.
1759 \item The installer no longer sets this
1760 file to require administrator privileges by default. If you want
1761 to do so, please do it manually using the {\bf cacls} program.
1764 cacls "C:\Program Files\Bacula" /T /G SYSTEM:F Administrators:F
1766 \item The server daemons (Director and Storage daemon) are
1767 no longer included in the Windows installer. If you want the
1768 Windows servers, you will either need to build them yourself (note
1769 they have not been ported to 64 bits), or you can contact
1770 Bacula Systems about this.
1773 \subsection{Win64 Installer}
1774 We have corrected a number of problems that required manual
1775 editing of the conf files. In most cases, it should now
1776 install and work. {\bf bat} is by default installed in
1777 {\bf c:/Program Files/Bacula/bin32} rather than
1778 {\bf c:/Program Files/Bacula} as is the case with the 32
1779 bit Windows installer.
1781 \subsection{Linux Bare Metal Recovery USB Key}
1782 We have made a number of significant improvements in the
1783 Bare Metal Recovery USB key. Please see the README files
1784 it the {\bf rescue} release for more details.
1786 We are working on an equivalent USB key for Windows bare
1787 metal recovery, but it will take some time to develop it (best
1788 estimate 3Q2010 or 4Q2010)
1791 \subsection{bconsole Timeout Option}
1792 You can now use the -u option of {\bf bconsole} to set a timeout in seconds
1793 for commands. This is useful with GUI programs that use {\bf bconsole}
1794 to interface to the Director.
1796 \subsection{Important Changes}
1797 \label{sec:importantchanges}
1800 \item You are now allowed to Migrate, Copy, and Virtual Full to read and write
1801 to the same Pool. The Storage daemon ensures that you do not read and
1802 write to the same Volume.
1803 \item The \texttt{Device Poll Interval} is now 5 minutes. (previously did not
1805 \item Virtually all the features of {\bf mtx-changer} have
1806 now been parametrized, which allows you to configure
1807 mtx-changer without changing it. There is a new configuration file {\bf mtx-changer.conf}
1808 that contains variables that you can set to configure mtx-changer.
1809 This configuration file will not be overwritten during upgrades.
1810 We encourage you to submit any changes
1811 that are made to mtx-changer and to parametrize it all in
1812 mtx-changer.conf so that all configuration will be done by
1813 changing only mtx-changer.conf.
1814 \item The new \texttt{mtx-changer} script has two new options, \texttt{listall}
1815 and \texttt{transfer}. Please configure them as appropriate
1816 in mtx-changer.conf.
1817 \item To enhance security of the \texttt{BackupCatalog} job, we provide a new
1818 script (\texttt{make\_catalog\_backup.pl}) that does not expose your catalog
1819 password. If you want to use the new script, you will need to
1820 manually change the \texttt{BackupCatalog} Job definition.
1821 \item The \texttt{bconsole} \texttt{help} command now accepts
1822 an argument, which if provided produces information on that
1823 command (ex: \texttt{help run}).
1827 \subsubsection*{Truncate volume after purge}
1829 Note that the Truncate Volume after purge feature doesn't work as expected
1830 in 5.0.0 version. Please, don't use it before version 5.0.1.
1832 \subsubsection{Custom Catalog queries}
1834 If you wish to add specialized commands that list the contents of the catalog,
1835 you can do so by adding them to the \texttt{query.sql} file. This
1836 \texttt{query.sql} file is now empty by default. The file
1837 \texttt{examples/sample-query.sql} has an a number of sample commands
1838 you might find useful.
1840 \subsubsection{Deprecated parts}
1842 The following items have been \textbf{deprecated} for a long time, and are now
1843 removed from the code.
1846 \item Support for SQLite 2
1849 \subsection{Misc Changes}
1850 \label{sec:miscchanges}
1853 \item Updated Nagios check\_bacula
1854 \item Updated man files
1855 \item Added OSX package generation script in platforms/darwin
1856 \item Added Spanish and Ukrainian Bacula translations
1857 \item Enable/disable command shows only Jobs that can change
1858 \item Added \texttt{show disabled} command to show disabled Jobs
1859 \item Many ACL improvements
1860 \item Added Level to FD status Job output
1861 \item Begin Ingres DB driver (not yet working)
1862 \item Split RedHat spec files into bacula, bat, mtx, and docs
1863 \item Reorganized the manuals (fewer separate manuals)
1864 \item Added lock/unlock order protection in lock manager
1865 \item Allow 64 bit sizes for a number of variables
1866 \item Fixed several deadlocks or potential race conditions in the SD
1869 \chapter{Released Version 3.0.3 and 3.0.3a}
1871 There are no new features in version 3.0.3. This version simply fixes a
1872 number of bugs found in version 3.0.2 during the ongoing development
1875 \section{New Features in Released Version 3.0.2}
1877 This chapter presents the new features added to the
1878 Released Bacula Version 3.0.2.
1880 \subsection{Full Restore from a Given JobId}
1881 \index[general]{Restore menu}
1883 This feature allows selecting a single JobId and having Bacula
1884 automatically select all the other jobs that comprise a full backup up to
1885 and including the selected date (through JobId).
1887 Assume we start with the following jobs:
1889 +-------+--------------+---------------------+-------+----------+------------+
1890 | jobid | client | starttime | level | jobfiles | jobbytes |
1891 +-------+--------------+---------------------+-------+----------+------------
1892 | 6 | localhost-fd | 2009-07-15 11:45:49 | I | 2 | 0 |
1893 | 5 | localhost-fd | 2009-07-15 11:45:45 | I | 15 | 44143 |
1894 | 3 | localhost-fd | 2009-07-15 11:45:38 | I | 1 | 10 |
1895 | 1 | localhost-fd | 2009-07-15 11:45:30 | F | 1527 | 44143073 |
1896 +-------+--------------+---------------------+-------+----------+------------+
1899 Below is an example of this new feature (which is number 12 in the
1904 To select the JobIds, you have the following choices:
1905 1: List last 20 Jobs run
1906 2: List Jobs where a given File is saved
1908 12: Select full restore to a specified Job date
1911 Select item: (1-13): 12
1912 Enter JobId to get the state to restore: 5
1913 Selecting jobs to build the Full state at 2009-07-15 11:45:45
1914 You have selected the following JobIds: 1,3,5
1916 Building directory tree for JobId(s) 1,3,5 ... +++++++++++++++++++
1917 1,444 files inserted into the tree.
1920 This project was funded by Bacula Systems.
1922 \subsection{Source Address}
1923 \index[general]{Source Address}
1925 A feature has been added which allows the administrator to specify the address
1926 from which the Director and File daemons will establish connections. This
1927 may be used to simplify system configuration overhead when working in complex
1928 networks utilizing multi-homing and policy-routing.
1930 To accomplish this, two new configuration directives have been implemented:
1933 FDSourceAddress=10.0.1.20 # Always initiate connections from this address
1937 DirSourceAddress=10.0.1.10 # Always initiate connections from this address
1941 Simply adding specific host routes on the OS
1942 would have an undesirable side-effect: any
1943 application trying to contact the destination host would be forced to use the
1944 more specific route possibly diverting management traffic onto a backup VLAN.
1945 Instead of adding host routes for each client connected to a multi-homed backup
1946 server (for example where there are management and backup VLANs), one can
1947 use the new directives to specify a specific source address at the application
1950 Additionally, this allows the simplification and abstraction of firewall rules
1951 when dealing with a Hot-Standby director or storage daemon configuration. The
1952 Hot-standby pair may share a CARP address, which connections must be sourced
1953 from, while system services listen and act from the unique interface addresses.
1955 This project was funded by Collaborative Fusion, Inc.
1957 \subsection{Show volume availability when doing restore}
1959 When doing a restore the selection dialog ends by displaying this
1963 The job will require the following
1964 Volume(s) Storage(s) SD Device(s)
1965 ===========================================================================
1966 *000741L3 LTO-4 LTO3
1967 *000866L3 LTO-4 LTO3
1968 *000765L3 LTO-4 LTO3
1969 *000764L3 LTO-4 LTO3
1970 *000756L3 LTO-4 LTO3
1971 *001759L3 LTO-4 LTO3
1972 *001763L3 LTO-4 LTO3
1976 Volumes marked with ``*'' are online (in the autochanger).
1979 This should help speed up large restores by minimizing the time spent
1980 waiting for the operator to discover that he must change tapes in the library.
1982 This project was funded by Bacula Systems.
1984 \subsection{Accurate estimate command}
1986 The \texttt{estimate} command can now use the accurate code to detect changes
1987 and give a better estimation.
1989 You can set the accurate behavior on the command line by using
1990 \texttt{accurate=yes\vb{}no} or use the Job setting as default value.
1993 * estimate listing accurate=yes level=incremental job=BackupJob
1996 This project was funded by Bacula Systems.
1998 \section{New Features in 3.0.0}
1999 \label{NewFeaturesChapter}
2000 \index[general]{New Features}
2002 This chapter presents the new features added to the development 2.5.x
2003 versions to be released as Bacula version 3.0.0 sometime in April 2009.
2005 \subsection{Accurate Backup}
2006 \index[general]{Accurate Backup}
2008 As with most other backup programs, by default Bacula decides what files to
2009 backup for Incremental and Differential backup by comparing the change
2010 (st\_ctime) and modification (st\_mtime) times of the file to the time the last
2011 backup completed. If one of those two times is later than the last backup
2012 time, then the file will be backed up. This does not, however, permit tracking
2013 what files have been deleted and will miss any file with an old time that may
2014 have been restored to or moved onto the client filesystem.
2016 \subsubsection{Accurate = \lt{}yes\vb{}no\gt{}}
2017 If the {\bf Accurate = \lt{}yes\vb{}no\gt{}} directive is enabled (default no) in
2018 the Job resource, the job will be run as an Accurate Job. For a {\bf Full}
2019 backup, there is no difference, but for {\bf Differential} and {\bf
2020 Incremental} backups, the Director will send a list of all previous files
2021 backed up, and the File daemon will use that list to determine if any new files
2022 have been added or or moved and if any files have been deleted. This allows
2023 Bacula to make an accurate backup of your system to that point in time so that
2024 if you do a restore, it will restore your system exactly.
2027 about using Accurate backup is that it requires more resources (CPU and memory)
2028 on both the Director and the Client machines to create the list of previous
2029 files backed up, to send that list to the File daemon, for the File daemon to
2030 keep the list (possibly very big) in memory, and for the File daemon to do
2031 comparisons between every file in the FileSet and the list. In particular,
2032 if your client has lots of files (more than a few million), you will need
2033 lots of memory on the client machine.
2035 Accurate must not be enabled when backing up with a plugin that is not
2036 specially designed to work with Accurate. If you enable it, your restores
2037 will probably not work correctly.
2039 This project was funded by Bacula Systems.
2043 \subsection{Copy Jobs}
2044 \index[general]{Copy Jobs}
2046 A new {\bf Copy} job type 'C' has been implemented. It is similar to the
2047 existing Migration feature with the exception that the Job that is copied is
2048 left unchanged. This essentially creates two identical copies of the same
2049 backup. However, the copy is treated as a copy rather than a backup job, and
2050 hence is not directly available for restore. The {\bf restore} command lists
2051 copy jobs and allows selection of copies by using \texttt{jobid=}
2052 option. If the keyword {\bf copies} is present on the command line, Bacula will
2053 display the list of all copies for selected jobs.
2058 These JobIds have copies as follows:
2059 +-------+------------------------------------+-----------+------------------+
2060 | JobId | Job | CopyJobId | MediaType |
2061 +-------+------------------------------------+-----------+------------------+
2062 | 2 | CopyJobSave.2009-02-17_16.31.00.11 | 7 | DiskChangerMedia |
2063 +-------+------------------------------------+-----------+------------------+
2064 +-------+-------+----------+----------+---------------------+------------------+
2065 | JobId | Level | JobFiles | JobBytes | StartTime | VolumeName |
2066 +-------+-------+----------+----------+---------------------+------------------+
2067 | 19 | F | 6274 | 76565018 | 2009-02-17 16:30:45 | ChangerVolume002 |
2068 | 2 | I | 1 | 5 | 2009-02-17 16:30:51 | FileVolume001 |
2069 +-------+-------+----------+----------+---------------------+------------------+
2070 You have selected the following JobIds: 19,2
2072 Building directory tree for JobId(s) 19,2 ... ++++++++++++++++++++++++++++++++++++++++++++
2073 5,611 files inserted into the tree.
2078 The Copy Job runs without using the File daemon by copying the data from the
2079 old backup Volume to a different Volume in a different Pool. See the Migration
2080 documentation for additional details. For copy Jobs there is a new selection
2081 directive named {\bf PoolUncopiedJobs} which selects all Jobs that were
2082 not already copied to another Pool.
2084 As with Migration, the Client, Volume, Job, or SQL query, are
2085 other possible ways of selecting the Jobs to be copied. Selection
2086 types like SmallestVolume, OldestVolume, PoolOccupancy and PoolTime also
2087 work, but are probably more suited for Migration Jobs.
2089 If Bacula finds a Copy of a job record that is purged (deleted) from the catalog,
2090 it will promote the Copy to a \textsl{real} backup job and will make it available for
2091 automatic restore. If more than one Copy is available, it will promote the copy
2092 with the smallest JobId.
2094 A nice solution which can be built with the new Copy feature is often
2095 called disk-to-disk-to-tape backup (DTDTT). A sample config could
2096 look something like the one below:
2100 Name = FullBackupsVirtualPool
2102 Purge Oldest Volume = Yes
2104 NextPool = FullBackupsTapePool
2108 Name = FullBackupsTapePool
2112 Volume Retention = 365 days
2113 Storage = superloader
2117 # Fake fileset for copy jobs
2129 # Fake client for copy jobs
2139 # Default template for a CopyDiskToTape Job
2142 Name = CopyDiskToTape
2144 Messages = StandardCopy
2147 Selection Type = PoolUncopiedJobs
2148 Maximum Concurrent Jobs = 10
2150 Allow Duplicate Jobs = Yes
2151 Cancel Queued Duplicates = No
2152 Cancel Running Duplicates = No
2157 Name = DaySchedule7:00
2158 Run = Level=Full daily at 7:00
2162 Name = CopyDiskToTapeFullBackups
2164 Schedule = DaySchedule7:00
2165 Pool = FullBackupsVirtualPool
2166 JobDefs = CopyDiskToTape
2170 The example above had 2 pool which are copied using the PoolUncopiedJobs
2171 selection criteria. Normal Full backups go to the Virtual pool and are copied
2172 to the Tape pool the next morning.
2174 The command \texttt{list copies [jobid=x,y,z]} lists copies for a given
2179 +-------+------------------------------------+-----------+------------------+
2180 | JobId | Job | CopyJobId | MediaType |
2181 +-------+------------------------------------+-----------+------------------+
2182 | 9 | CopyJobSave.2008-12-20_22.26.49.05 | 11 | DiskChangerMedia |
2183 +-------+------------------------------------+-----------+------------------+
2186 \subsection{ACL Updates}
2187 \index[general]{ACL Updates}
2188 The whole ACL code had been overhauled and in this version each platforms has
2189 different streams for each type of acl available on such an platform. As ACLs
2190 between platforms tend to be not that portable (most implement POSIX acls but
2191 some use an other draft or a completely different format) we currently only
2192 allow certain platform specific ACL streams to be decoded and restored on the
2193 same platform that they were created on. The old code allowed to restore ACL
2194 cross platform but the comments already mention that not being to wise. For
2195 backward compatibility the new code will accept the two old ACL streams and
2196 handle those with the platform specific handler. But for all new backups it
2197 will save the ACLs using the new streams.
2199 Currently the following platforms support ACLs:
2203 \item {\bf Darwin/OSX}
2212 Currently we support the following ACL types (these ACL streams use a reserved
2213 part of the stream numbers):
2216 \item {\bf STREAM\_ACL\_AIX\_TEXT} 1000 AIX specific string representation from
2218 \item {\bf STREAM\_ACL\_DARWIN\_ACCESS\_ACL} 1001 Darwin (OSX) specific acl\_t
2219 string representation from acl\_to\_text (POSIX acl)
2220 \item {\bf STREAM\_ACL\_FREEBSD\_DEFAULT\_ACL} 1002 FreeBSD specific acl\_t
2221 string representation from acl\_to\_text (POSIX acl) for default acls.
2222 \item {\bf STREAM\_ACL\_FREEBSD\_ACCESS\_ACL} 1003 FreeBSD specific acl\_t
2223 string representation from acl\_to\_text (POSIX acl) for access acls.
2224 \item {\bf STREAM\_ACL\_HPUX\_ACL\_ENTRY} 1004 HPUX specific acl\_entry
2225 string representation from acltostr (POSIX acl)
2226 \item {\bf STREAM\_ACL\_IRIX\_DEFAULT\_ACL} 1005 IRIX specific acl\_t string
2227 representation from acl\_to\_text (POSIX acl) for default acls.
2228 \item {\bf STREAM\_ACL\_IRIX\_ACCESS\_ACL} 1006 IRIX specific acl\_t string
2229 representation from acl\_to\_text (POSIX acl) for access acls.
2230 \item {\bf STREAM\_ACL\_LINUX\_DEFAULT\_ACL} 1007 Linux specific acl\_t
2231 string representation from acl\_to\_text (POSIX acl) for default acls.
2232 \item {\bf STREAM\_ACL\_LINUX\_ACCESS\_ACL} 1008 Linux specific acl\_t string
2233 representation from acl\_to\_text (POSIX acl) for access acls.
2234 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_ACL} 1009 Tru64 specific acl\_t
2235 string representation from acl\_to\_text (POSIX acl) for default acls.
2236 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_DIR\_ACL} 1010 Tru64 specific acl\_t
2237 string representation from acl\_to\_text (POSIX acl) for default acls.
2238 \item {\bf STREAM\_ACL\_TRU64\_ACCESS\_ACL} 1011 Tru64 specific acl\_t string
2239 representation from acl\_to\_text (POSIX acl) for access acls.
2240 \item {\bf STREAM\_ACL\_SOLARIS\_ACLENT} 1012 Solaris specific aclent\_t
2241 string representation from acltotext or acl\_totext (POSIX acl)
2242 \item {\bf STREAM\_ACL\_SOLARIS\_ACE} 1013 Solaris specific ace\_t string
2243 representation from from acl\_totext (NFSv4 or ZFS acl)
2246 In future versions we might support conversion functions from one type of acl
2247 into an other for types that are either the same or easily convertible. For now
2248 the streams are separate and restoring them on a platform that doesn't
2249 recognize them will give you a warning.
2251 \subsection{Extended Attributes}
2252 \index[general]{Extended Attributes}
2253 Something that was on the project list for some time is now implemented for
2254 platforms that support a similar kind of interface. Its the support for backup
2255 and restore of so called extended attributes. As extended attributes are so
2256 platform specific these attributes are saved in separate streams for each
2257 platform. Restores of the extended attributes can only be performed on the
2258 same platform the backup was done. There is support for all types of extended
2259 attributes, but restoring from one type of filesystem onto an other type of
2260 filesystem on the same platform may lead to surprises. As extended attributes
2261 can contain any type of data they are stored as a series of so called
2262 value-pairs. This data must be seen as mostly binary and is stored as such.
2263 As security labels from selinux are also extended attributes this option also
2264 stores those labels and no specific code is enabled for handling selinux
2267 Currently the following platforms support extended attributes:
2269 \item {\bf Darwin/OSX}
2275 On Linux acls are also extended attributes, as such when you enable ACLs on a
2276 Linux platform it will NOT save the same data twice e.g. it will save the ACLs
2277 and not the same extended attribute.
2279 To enable the backup of extended attributes please add the following to your
2294 \subsection{Shared objects}
2295 \index[general]{Shared objects}
2296 A default build of Bacula will now create the libraries as shared objects
2297 (.so) rather than static libraries as was previously the case.
2298 The shared libraries are built using {\bf libtool} so it should be quite
2301 An important advantage of using shared objects is that on a machine with the
2302 Directory, File daemon, the Storage daemon, and a console, you will have only
2303 one copy of the code in memory rather than four copies. Also the total size of
2304 the binary release is smaller since the library code appears only once rather
2305 than once for every program that uses it; this results in significant reduction
2306 in the size of the binaries particularly for the utility tools.
2308 In order for the system loader to find the shared objects when loading the
2309 Bacula binaries, the Bacula shared objects must either be in a shared object
2310 directory known to the loader (typically /usr/lib) or they must be in the
2311 directory that may be specified on the {\bf ./configure} line using the {\bf
2312 {-}{-}libdir} option as:
2315 ./configure --libdir=/full-path/dir
2318 the default is /usr/lib. If {-}{-}libdir is specified, there should be
2319 no need to modify your loader configuration provided that
2320 the shared objects are installed in that directory (Bacula
2321 does this with the make install command). The shared objects
2322 that Bacula references are:
2331 These files are symbolically linked to the real shared object file,
2332 which has a version number to permit running multiple versions of
2333 the libraries if desired (not normally the case).
2335 If you have problems with libtool or you wish to use the old
2336 way of building static libraries, or you want to build a static
2337 version of Bacula you may disable
2338 libtool on the configure command line with:
2341 ./configure --disable-libtool
2345 \subsection{Building Static versions of Bacula}
2346 \index[general]{Static linking}
2347 In order to build static versions of Bacula, in addition
2348 to configuration options that were needed you now must
2349 also add --disable-libtool. Example
2352 ./configure --enable-static-client-only --disable-libtool
2356 \subsection{Virtual Backup (Vbackup)}
2357 \index[general]{Virtual Backup}
2358 \index[general]{Vbackup}
2360 Bacula's virtual backup feature is often called Synthetic Backup or
2361 Consolidation in other backup products. It permits you to consolidate the
2362 previous Full backup plus the most recent Differential backup and any
2363 subsequent Incremental backups into a new Full backup. This new Full
2364 backup will then be considered as the most recent Full for any future
2365 Incremental or Differential backups. The VirtualFull backup is
2366 accomplished without contacting the client by reading the previous backup
2367 data and writing it to a volume in a different pool.
2369 In some respects the Vbackup feature works similar to a Migration job, in
2370 that Bacula normally reads the data from the pool specified in the
2371 Job resource, and writes it to the {\bf Next Pool} specified in the
2372 Job resource. Note, this means that usually the output from the Virtual
2373 Backup is written into a different pool from where your prior backups
2374 are saved. Doing it this way guarantees that you will not get a deadlock
2375 situation attempting to read and write to the same volume in the Storage
2376 daemon. If you then want to do subsequent backups, you may need to
2377 move the Virtual Full Volume back to your normal backup pool.
2378 Alternatively, you can set your {\bf Next Pool} to point to the current
2379 pool. This will cause Bacula to read and write to Volumes in the
2380 current pool. In general, this will work, because Bacula will
2381 not allow reading and writing on the same Volume. In any case, once
2382 a VirtualFull has been created, and a restore is done involving the
2383 most current Full, it will read the Volume or Volumes by the VirtualFull
2384 regardless of in which Pool the Volume is found.
2386 The Vbackup is enabled on a Job by Job in the Job resource by specifying
2387 a level of {\bf VirtualFull}.
2389 A typical Job resource definition might look like the following:
2396 FileSet = "Full Set"
2403 # Default pool definition
2407 Recycle = yes # Automatically recycle Volumes
2408 AutoPrune = yes # Prune expired volumes
2409 Volume Retention = 365d # one year
2417 Recycle = yes # Automatically recycle Volumes
2418 AutoPrune = yes # Prune expired volumes
2419 Volume Retention = 365d # one year
2420 Storage = DiskChanger
2423 # Definition of file storage device
2428 Device = FileStorage
2430 Maximum Concurrent Jobs = 5
2433 # Definition of DDS Virtual tape disk storage device
2436 Address = localhost # N.B. Use a fully qualified name here
2438 Device = DiskChanger
2439 Media Type = DiskChangerMedia
2440 Maximum Concurrent Jobs = 4
2445 Then in bconsole or via a Run schedule, you would run the job as:
2448 run job=MyBackup level=Full
2449 run job=MyBackup level=Incremental
2450 run job=MyBackup level=Differential
2451 run job=MyBackup level=Incremental
2452 run job=MyBackup level=Incremental
2455 So providing there were changes between each of those jobs, you would end up
2456 with a Full backup, a Differential, which includes the first Incremental
2457 backup, then two Incremental backups. All the above jobs would be written to
2458 the {\bf Default} pool.
2460 To consolidate those backups into a new Full backup, you would run the
2464 run job=MyBackup level=VirtualFull
2467 And it would produce a new Full backup without using the client, and the output
2468 would be written to the {\bf Full} Pool which uses the Diskchanger Storage.
2470 If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
2473 Note, the Start and End time of the Virtual Full backup is set to the
2474 values for the last job included in the Virtual Full (in the above example,
2475 it is an Increment). This is so that if another incremental is done, which
2476 will be based on the Virtual Full, it will backup all files from the
2477 last Job included in the Virtual Full rather than from the time the Virtual
2478 Full was actually run.
2482 \subsection{Catalog Format}
2483 \index[general]{Catalog Format}
2484 Bacula 3.0 comes with some changes to the catalog format. The upgrade
2485 operation will convert the FileId field of the File table from 32 bits (max 4
2486 billion table entries) to 64 bits (very large number of items). The
2487 conversion process can take a bit of time and will likely DOUBLE THE SIZE of
2488 your catalog during the conversion. Also you won't be able to run jobs during
2489 this conversion period. For example, a 3 million file catalog will take 2
2490 minutes to upgrade on a normal machine. Please don't forget to make a valid
2491 backup of your database before executing the upgrade script. See the
2492 ReleaseNotes for additional details.
2494 \subsection{64 bit Windows Client}
2495 \index[general]{Win64 Client}
2496 Unfortunately, Microsoft's implementation of Volume Shadown Copy (VSS) on
2497 their 64 bit OS versions is not compatible with a 32 bit Bacula Client.
2498 As a consequence, we are also releasing a 64 bit version of the Bacula
2499 Windows Client (win64bacula-3.0.0.exe) that does work with VSS.
2500 These binaries should only be installed on 64 bit Windows operating systems.
2501 What is important is not your hardware but whether or not you have
2502 a 64 bit version of the Windows OS.
2504 Compared to the Win32 Bacula Client, the 64 bit release contains a few differences:
2506 \item Before installing the Win64 Bacula Client, you must totally
2507 deinstall any prior 2.4.x Client installation using the
2508 Bacula deinstallation (see the menu item). You may want
2509 to save your .conf files first.
2510 \item Only the Client (File daemon) is ported to Win64, the Director
2511 and the Storage daemon are not in the 64 bit Windows installer.
2512 \item bwx-console is not yet ported.
2513 \item bconsole is ported but it has not been tested.
2514 \item The documentation is not included in the installer.
2515 \item Due to Vista security restrictions imposed on a default installation
2516 of Vista, before upgrading the Client, you must manually stop
2517 any prior version of Bacula from running, otherwise the install
2519 \item Due to Vista security restrictions imposed on a default installation
2520 of Vista, attempting to edit the conf files via the menu items
2521 will fail. You must directly edit the files with appropriate
2522 permissions. Generally double clicking on the appropriate .conf
2523 file will work providing you have sufficient permissions.
2524 \item All Bacula files are now installed in
2525 {\bf C:/Program Files/Bacula} except the main menu items,
2526 which are installed as before. This vastly simplifies the installation.
2527 \item If you are running on a foreign language version of Windows, most
2528 likely {\bf C:/Program Files} does not exist, so you should use the
2529 Custom installation and enter an appropriate location to install
2531 \item The 3.0.0 Win32 Client continues to install files in the locations used
2532 by prior versions. For the next version we will convert it to use
2533 the same installation conventions as the Win64 version.
2536 This project was funded by Bacula Systems.
2539 \subsection{Duplicate Job Control}
2540 \index[general]{Duplicate Jobs}
2541 The new version of Bacula provides four new directives that
2542 give additional control over what Bacula does if duplicate jobs
2543 are started. A duplicate job in the sense we use it here means
2544 a second or subsequent job with the same name starts. This
2545 happens most frequently when the first job runs longer than expected because no
2546 tapes are available.
2548 The four directives each take as an argument a {\bf yes} or {\bf no} value and
2549 are specified in the Job resource.
2553 \subsubsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}}
2554 \index[general]{Allow Duplicate Jobs}
2555 If this directive is set to {\bf yes}, duplicate jobs will be run. If
2556 the directive is set to {\bf no} (default) then only one job of a given name
2557 may run at one time, and the action that Bacula takes to ensure only
2558 one job runs is determined by the other directives (see below).
2560 If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs
2561 are present and none of the three directives given below permit
2562 Canceling a job, then the current job (the second one started)
2565 \subsubsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}}
2566 \index[general]{Allow Higher Duplicates}
2567 This directive was in version 5.0.0, but does not work as
2568 expected. If used, it should always be set to no. In later versions
2569 of Bacula the directive is disabled (disregarded).
2571 \subsubsection{Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}}
2572 \index[general]{Cancel Running Duplicates}
2573 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
2574 if this directive is set to {\bf yes} any job that is already running
2575 will be canceled. The default is {\bf no}.
2577 \subsubsection{Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}}
2578 \index[general]{Cancel Queued Duplicates}
2579 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
2580 if this directive is set to {\bf yes} any job that is
2581 already queued to run but not yet running will be canceled.
2582 The default is {\bf no}.
2585 \subsection{TLS Authentication}
2586 \index[general]{TLS Authentication}
2587 In Bacula version 2.5.x and later, in addition to the normal Bacula
2588 CRAM-MD5 authentication that is used to authenticate each Bacula
2589 connection, you can specify that you want TLS Authentication as well,
2590 which will provide more secure authentication.
2592 This new feature uses Bacula's existing TLS code (normally used for
2593 communications encryption) to do authentication. To use it, you must
2594 specify all the TLS directives normally used to enable communications
2595 encryption (TLS Enable, TLS Verify Peer, TLS Certificate, ...) and
2598 \subsubsection{TLS Authenticate = yes}
2600 TLS Authenticate = yes
2603 in the main daemon configuration resource (Director for the Director,
2604 Client for the File daemon, and Storage for the Storage daemon).
2606 When {\bf TLS Authenticate} is enabled, after doing the CRAM-MD5
2607 authentication, Bacula will also do TLS authentication, then TLS
2608 encryption will be turned off, and the rest of the communication between
2609 the two Bacula daemons will be done without encryption.
2611 If you want to encrypt communications data, use the normal TLS directives
2612 but do not turn on {\bf TLS Authenticate}.
2614 \subsection{bextract non-portable Win32 data}
2615 \index[general]{bextract handles Win32 non-portable data}
2616 {\bf bextract} has been enhanced to be able to restore
2617 non-portable Win32 data to any OS. Previous versions were
2618 unable to restore non-portable Win32 data to machines that
2619 did not have the Win32 BackupRead and BackupWrite API calls.
2621 \subsection{State File updated at Job Termination}
2622 \index[general]{State File}
2623 In previous versions of Bacula, the state file, which provides a
2624 summary of previous jobs run in the {\bf status} command output was
2625 updated only when Bacula terminated, thus if the daemon crashed, the
2626 state file might not contain all the run data. This version of
2627 the Bacula daemons updates the state file on each job termination.
2629 \subsection{MaxFullInterval = \lt{}time-interval\gt{}}
2630 \index[general]{MaxFullInterval}
2631 The new Job resource directive {\bf Max Full Interval = \lt{}time-interval\gt{}}
2632 can be used to specify the maximum time interval between {\bf Full} backup
2633 jobs. When a job starts, if the time since the last Full backup is
2634 greater than the specified interval, and the job would normally be an
2635 {\bf Incremental} or {\bf Differential}, it will be automatically
2636 upgraded to a {\bf Full} backup.
2638 \subsection{MaxDiffInterval = \lt{}time-interval\gt{}}
2639 \index[general]{MaxDiffInterval}
2640 The new Job resource directive {\bf Max Diff Interval = \lt{}time-interval\gt{}}
2641 can be used to specify the maximum time interval between {\bf Differential} backup
2642 jobs. When a job starts, if the time since the last Differential backup is
2643 greater than the specified interval, and the job would normally be an
2644 {\bf Incremental}, it will be automatically
2645 upgraded to a {\bf Differential} backup.
2647 \subsection{Honor No Dump Flag = \lt{}yes\vb{}no\gt{}}
2648 \index[general]{MaxDiffInterval}
2649 On FreeBSD systems, each file has a {\bf no dump flag} that can be set
2650 by the user, and when it is set it is an indication to backup programs
2651 to not backup that particular file. This version of Bacula contains a
2652 new Options directive within a FileSet resource, which instructs Bacula to
2653 obey this flag. The new directive is:
2656 Honor No Dump Flag = yes\vb{}no
2659 The default value is {\bf no}.
2662 \subsection{Exclude Dir Containing = \lt{}filename-string\gt{}}
2663 \index[general]{IgnoreDir}
2664 The {\bf ExcludeDirContaining = \lt{}filename\gt{}} is a new directive that
2665 can be added to the Include section of the FileSet resource. If the specified
2666 filename ({\bf filename-string}) is found on the Client in any directory to be
2667 backed up, the whole directory will be ignored (not backed up). For example:
2670 # List of files to be backed up
2678 Exclude Dir Containing = .excludeme
2683 But in /home, there may be hundreds of directories of users and some
2684 people want to indicate that they don't want to have certain
2685 directories backed up. For example, with the above FileSet, if
2686 the user or sysadmin creates a file named {\bf .excludeme} in
2687 specific directories, such as
2690 /home/user/www/cache/.excludeme
2691 /home/user/temp/.excludeme
2694 then Bacula will not backup the two directories named:
2697 /home/user/www/cache
2701 NOTE: subdirectories will not be backed up. That is, the directive
2702 applies to the two directories in question and any children (be they
2703 files, directories, etc).
2706 \subsection{Bacula Plugins}
2707 \index[general]{Plugin}
2708 Support for shared object plugins has been implemented in the Linux, Unix
2709 and Win32 File daemons. The API will be documented separately in
2710 the Developer's Guide or in a new document. For the moment, there is
2711 a single plugin named {\bf bpipe} that allows an external program to
2712 get control to backup and restore a file.
2714 Plugins are also planned (partially implemented) in the Director and the
2717 \subsubsection{Plugin Directory}
2718 \index[general]{Plugin Directory}
2719 Each daemon (DIR, FD, SD) has a new {\bf Plugin Directory} directive that may
2720 be added to the daemon definition resource. The directory takes a quoted
2721 string argument, which is the name of the directory in which the daemon can
2722 find the Bacula plugins. If this directive is not specified, Bacula will not
2723 load any plugins. Since each plugin has a distinctive name, all the daemons
2724 can share the same plugin directory.
2726 \subsubsection{Plugin Options}
2727 \index[general]{Plugin Options}
2728 The {\bf Plugin Options} directive takes a quoted string
2729 argument (after the equal sign) and may be specified in the
2730 Job resource. The options specified will be passed to all plugins
2731 when they are run. This each plugin must know what it is looking
2732 for. The value defined in the Job resource can be modified
2733 by the user when he runs a Job via the {\bf bconsole} command line
2736 Note: this directive may be specified, and there is code to modify
2737 the string in the run command, but the plugin options are not yet passed to
2738 the plugin (i.e. not fully implemented).
2740 \subsubsection{Plugin Options ACL}
2741 \index[general]{Plugin Options ACL}
2742 The {\bf Plugin Options ACL} directive may be specified in the
2743 Director's Console resource. It functions as all the other ACL commands
2744 do by permitting users running restricted consoles to specify a
2745 {\bf Plugin Options} that overrides the one specified in the Job
2746 definition. Without this directive restricted consoles may not modify
2749 \subsubsection{Plugin = \lt{}plugin-command-string\gt{}}
2750 \index[general]{Plugin}
2751 The {\bf Plugin} directive is specified in the Include section of
2752 a FileSet resource where you put your {\bf File = xxx} directives.
2763 Plugin = "bpipe:..."
2768 In the above example, when the File daemon is processing the directives
2769 in the Include section, it will first backup all the files in {\bf /home}
2770 then it will load the plugin named {\bf bpipe} (actually bpipe-dir.so) from
2771 the Plugin Directory. The syntax and semantics of the Plugin directive
2772 require the first part of the string up to the colon (:) to be the name
2773 of the plugin. Everything after the first colon is ignored by the File daemon but
2774 is passed to the plugin. Thus the plugin writer may define the meaning of the
2775 rest of the string as he wishes.
2777 Please see the next section for information about the {\bf bpipe} Bacula
2780 \subsection{The bpipe Plugin}
2781 \index[general]{The bpipe Plugin}
2782 The {\bf bpipe} plugin is provided in the directory src/plugins/fd/bpipe-fd.c of
2783 the Bacula source distribution. When the plugin is compiled and linking into
2784 the resulting dynamic shared object (DSO), it will have the name {\bf bpipe-fd.so}.
2785 Please note that this is a very simple plugin that was written for
2786 demonstration and test purposes. It is and can be used in production, but
2787 that was never really intended.
2789 The purpose of the plugin is to provide an interface to any system program for
2790 backup and restore. As specified above the {\bf bpipe} plugin is specified in
2791 the Include section of your Job's FileSet resource. The full syntax of the
2792 plugin directive as interpreted by the {\bf bpipe} plugin (each plugin is free
2793 to specify the sytax as it wishes) is:
2796 Plugin = "<field1>:<field2>:<field3>:<field4>"
2801 \item {\bf field1} is the name of the plugin with the trailing {\bf -fd.so}
2802 stripped off, so in this case, we would put {\bf bpipe} in this field.
2804 \item {\bf field2} specifies the namespace, which for {\bf bpipe} is the
2805 pseudo path and filename under which the backup will be saved. This pseudo
2806 path and filename will be seen by the user in the restore file tree.
2807 For example, if the value is {\bf /MYSQL/regress.sql}, the data
2808 backed up by the plugin will be put under that "pseudo" path and filename.
2809 You must be careful to choose a naming convention that is unique to avoid
2810 a conflict with a path and filename that actually exists on your system.
2812 \item {\bf field3} for the {\bf bpipe} plugin
2813 specifies the "reader" program that is called by the plugin during
2814 backup to read the data. {\bf bpipe} will call this program by doing a
2817 \item {\bf field4} for the {\bf bpipe} plugin
2818 specifies the "writer" program that is called by the plugin during
2819 restore to write the data back to the filesystem.
2822 Please note that for two items above describing the "reader" and "writer"
2823 fields, these programs are "executed" by Bacula, which
2824 means there is no shell interpretation of any command line arguments
2825 you might use. If you want to use shell characters (redirection of input
2826 or output, ...), then we recommend that you put your command or commands
2827 in a shell script and execute the script. In addition if you backup a
2828 file with the reader program, when running the writer program during
2829 the restore, Bacula will not automatically create the path to the file.
2830 Either the path must exist, or you must explicitly do so with your command
2831 or in a shell script.
2833 Putting it all together, the full plugin directive line might look
2837 Plugin = "bpipe:/MYSQL/regress.sql:mysqldump -f
2838 --opt --databases bacula:mysql"
2841 The directive has been split into two lines, but within the {\bf bacula-dir.conf} file
2842 would be written on a single line.
2844 This causes the File daemon to call the {\bf bpipe} plugin, which will write
2845 its data into the "pseudo" file {\bf /MYSQL/regress.sql} by calling the
2846 program {\bf mysqldump -f --opt --database bacula} to read the data during
2847 backup. The mysqldump command outputs all the data for the database named
2848 {\bf bacula}, which will be read by the plugin and stored in the backup.
2849 During restore, the data that was backed up will be sent to the program
2850 specified in the last field, which in this case is {\bf mysql}. When
2851 {\bf mysql} is called, it will read the data sent to it by the plugn
2852 then write it back to the same database from which it came ({\bf bacula}
2855 The {\bf bpipe} plugin is a generic pipe program, that simply transmits
2856 the data from a specified program to Bacula for backup, and then from Bacula to
2857 a specified program for restore.
2859 By using different command lines to {\bf bpipe},
2860 you can backup any kind of data (ASCII or binary) depending
2861 on the program called.
2863 \subsection{Microsoft Exchange Server 2003/2007 Plugin}
2864 \index[general]{Microsoft Exchange Server 2003/2007 Plugin}
2865 \subsubsection{Background}
2866 The Exchange plugin was made possible by a funded development project
2867 between Equiinet Ltd -- www.equiinet.com (many thanks) and Bacula Systems.
2868 The code for the plugin was written by James Harper, and the Bacula core
2869 code by Kern Sibbald. All the code for this funded development has become
2870 part of the Bacula project. Thanks to everyone who made it happen.
2872 \subsubsection{Concepts}
2873 Although it is possible to backup Exchange using Bacula VSS the Exchange
2874 plugin adds a good deal of functionality, because while Bacula VSS
2875 completes a full backup (snapshot) of Exchange, it does
2876 not support Incremental or Differential backups, restoring is more
2877 complicated, and a single database restore is not possible.
2879 Microsoft Exchange organises its storage into Storage Groups with
2880 Databases inside them. A default installation of Exchange will have a
2881 single Storage Group called 'First Storage Group', with two Databases
2882 inside it, "Mailbox Store (SERVER NAME)" and
2883 "Public Folder Store (SERVER NAME)",
2884 which hold user email and public folders respectively.
2886 In the default configuration, Exchange logs everything that happens to
2887 log files, such that if you have a backup, and all the log files since,
2888 you can restore to the present time. Each Storage Group has its own set
2889 of log files and operates independently of any other Storage Groups. At
2890 the Storage Group level, the logging can be turned off by enabling a
2891 function called "Enable circular logging". At this time the Exchange
2892 plugin will not function if this option is enabled.
2894 The plugin allows backing up of entire storage groups, and the restoring
2895 of entire storage groups or individual databases. Backing up and
2896 restoring at the individual mailbox or email item is not supported but
2897 can be simulated by use of the "Recovery" Storage Group (see below).
2899 \subsubsection{Installing}
2900 The Exchange plugin requires a DLL that is shipped with Microsoft
2901 Exchanger Server called {\bf esebcli2.dll}. Assuming Exchange is installed
2902 correctly the Exchange plugin should find this automatically and run
2903 without any additional installation.
2905 If the DLL can not be found automatically it will need to be copied into
2906 the Bacula installation
2907 directory (eg C:\verb+\+Program Files\verb+\+Bacula\verb+\+bin). The Exchange API DLL is
2908 named esebcli2.dll and is found in C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+bin on a
2909 default Exchange installation.
2911 \subsubsection{Backing Up}
2912 To back up an Exchange server the Fileset definition must contain at
2913 least {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"} for
2914 the backup to work correctly. The 'exchange:' bit tells Bacula to look
2915 for the exchange plugin, the '@EXCHANGE' bit makes sure all the backed
2916 up files are prefixed with something that isn't going to share a name
2917 with something outside the plugin, and the 'Microsoft Information Store'
2918 bit is required also. It is also possible to add the name of a storage
2919 group to the "Plugin =" line, eg \\
2920 {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"} \\
2921 if you want only a single storage group backed up.
2923 Additionally, you can suffix the 'Plugin =' directive with
2924 ":notrunconfull" which will tell the plugin not to truncate the Exchange
2925 database at the end of a full backup.
2927 An Incremental or Differential backup will backup only the database logs
2928 for each Storage Group by inspecting the "modified date" on each
2929 physical log file. Because of the way the Exchange API works, the last
2930 logfile backed up on each backup will always be backed up by the next
2931 Incremental or Differential backup too. This adds 5MB to each
2932 Incremental or Differential backup size but otherwise does not cause any
2935 By default, a normal VSS fileset containing all the drive letters will
2936 also back up the Exchange databases using VSS. This will interfere with
2937 the plugin and Exchange's shared ideas of when the last full backup was
2938 done, and may also truncate log files incorrectly. It is important,
2939 therefore, that the Exchange database files be excluded from the backup,
2940 although the folders the files are in should be included, or they will
2941 have to be recreated manually if a bare metal restore is done.
2946 File = C:/Program Files/Exchsrvr/mdbdata
2947 Plugin = "exchange:..."
2950 File = C:/Program Files/Exchsrvr/mdbdata/E00.chk
2951 File = C:/Program Files/Exchsrvr/mdbdata/E00.log
2952 File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log
2953 File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log
2954 File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log
2955 File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log
2956 File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb
2961 The advantage of excluding the above files is that you can significantly
2962 reduce the size of your backup since all the important Exchange files
2963 will be properly saved by the Plugin.
2966 \subsubsection{Restoring}
2967 The restore operation is much the same as a normal Bacula restore, with
2968 the following provisos:
2971 \item The {\bf Where} restore option must not be specified
2972 \item Each Database directory must be marked as a whole. You cannot just
2973 select (say) the .edb file and not the others.
2974 \item If a Storage Group is restored, the directory of the Storage Group
2976 \item It is possible to restore only a subset of the available log files,
2977 but they {\bf must} be contiguous. Exchange will fail to restore correctly
2978 if a log file is missing from the sequence of log files
2979 \item Each database to be restored must be dismounted and marked as "Can be
2980 overwritten by restore"
2981 \item If an entire Storage Group is to be restored (eg all databases and
2982 logs in the Storage Group), then it is best to manually delete the
2983 database files from the server (eg C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+mdbdata\verb+\+*)
2984 as Exchange can get confused by stray log files lying around.
2987 \subsubsection{Restoring to the Recovery Storage Group}
2988 The concept of the Recovery Storage Group is well documented by
2990 \elink{http://support.microsoft.com/kb/824126}{http://support.microsoft.com/kb/824126},
2991 but to briefly summarize...
2993 Microsoft Exchange allows the creation of an additional Storage Group
2994 called the Recovery Storage Group, which is used to restore an older
2995 copy of a database (e.g. before a mailbox was deleted) into without
2996 messing with the current live data. This is required as the Standard and
2997 Small Business Server versions of Exchange can not ordinarily have more
2998 than one Storage Group.
3000 To create the Recovery Storage Group, drill down to the Server in Exchange
3001 System Manager, right click, and select
3002 {\bf "New -> Recovery Storage Group..."}. Accept or change the file
3003 locations and click OK. On the Recovery Storage Group, right click and
3004 select {\bf "Add Database to Recover..."} and select the database you will
3007 Restore only the single database nominated as the database in the
3008 Recovery Storage Group. Exchange will redirect the restore to the
3009 Recovery Storage Group automatically.
3010 Then run the restore.
3012 \subsubsection{Restoring on Microsoft Server 2007}
3013 Apparently the {\bf Exmerge} program no longer exists in Microsoft Server
3014 2007, and hence you use a new procedure for recovering a single mail box.
3015 This procedure is documented by Microsoft at:
3016 \elink{http://technet.microsoft.com/en-us/library/aa997694.aspx}{http://technet.microsoft.com/en-us/library/aa997694.aspx},
3017 and involves using the {\bf Restore-Mailbox} and {\bf
3018 Get-Mailbox Statistics} shell commands.
3020 \subsubsection{Caveats}
3021 This plugin is still being developed, so you should consider it
3022 currently in BETA test, and thus use in a production environment
3023 should be done only after very careful testing.
3025 When doing a full backup, the Exchange database logs are truncated by
3026 Exchange as soon as the plugin has completed the backup. If the data
3027 never makes it to the backup medium (eg because of spooling) then the
3028 logs will still be truncated, but they will also not have been backed
3029 up. A solution to this is being worked on. You will have to schedule a
3030 new Full backup to ensure that your next backups will be usable.
3032 The "Enable Circular Logging" option cannot be enabled or the plugin
3035 Exchange insists that a successful Full backup must have taken place if
3036 an Incremental or Differential backup is desired, and the plugin will
3037 fail if this is not the case. If a restore is done, Exchange will
3038 require that a Full backup be done before an Incremental or Differential
3041 The plugin will most likely not work well if another backup application
3042 (eg NTBACKUP) is backing up the Exchange database, especially if the
3043 other backup application is truncating the log files.
3045 The Exchange plugin has not been tested with the {\bf Accurate} option, so
3046 we recommend either carefully testing or that you avoid this option for
3049 The Exchange plugin is not called during processing the bconsole {\bf
3050 estimate} command, and so anything that would be backed up by the plugin
3051 will not be added to the estimate total that is displayed.
3054 \subsection{libdbi Framework}
3055 \index[general]{libdbi Framework}
3056 As a general guideline, Bacula has support for a few catalog database drivers
3057 (MySQL, PostgreSQL, SQLite)
3058 coded natively by the Bacula team. With the libdbi implementation, which is a
3059 Bacula driver that uses libdbi to access the catalog, we have an open field to
3060 use many different kinds database engines following the needs of users.
3062 The according to libdbi (http://libdbi.sourceforge.net/) project: libdbi
3063 implements a database-independent abstraction layer in C, similar to the
3064 DBI/DBD layer in Perl. Writing one generic set of code, programmers can
3065 leverage the power of multiple databases and multiple simultaneous database
3066 connections by using this framework.
3068 Currently the libdbi driver in Bacula project only supports the same drivers
3069 natively coded in Bacula. However the libdbi project has support for many
3070 others database engines. You can view the list at
3071 http://libdbi-drivers.sourceforge.net/. In the future all those drivers can be
3072 supported by Bacula, however, they must be tested properly by the Bacula team.
3074 Some of benefits of using libdbi are:
3076 \item The possibility to use proprietary databases engines in which your
3077 proprietary licenses prevent the Bacula team from developing the driver.
3078 \item The possibility to use the drivers written for the libdbi project.
3079 \item The possibility to use other database engines without recompiling Bacula
3080 to use them. Just change one line in bacula-dir.conf
3081 \item Abstract Database access, this is, unique point to code and profiling
3082 catalog database access.
3085 The following drivers have been tested:
3087 \item PostgreSQL, with and without batch insert
3088 \item Mysql, with and without batch insert
3093 In the future, we will test and approve to use others databases engines
3094 (proprietary or not) like DB2, Oracle, Microsoft SQL.
3096 To compile Bacula to support libdbi we need to configure the code with the
3097 --with-dbi and --with-dbi-driver=[database] ./configure options, where
3098 [database] is the database engine to be used with Bacula (of course we can
3099 change the driver in file bacula-dir.conf, see below). We must configure the
3100 access port of the database engine with the option --with-db-port, because the
3101 libdbi framework doesn't know the default access port of each database.
3103 The next phase is checking (or configuring) the bacula-dir.conf, example:
3107 dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
3108 dbname = regress; user = regress; password = ""
3112 The parameter {\bf dbdriver} indicates that we will use the driver dbi with a
3113 mysql database. Currently the drivers supported by Bacula are: postgresql,
3114 mysql, sqlite, sqlite3; these are the names that may be added to string "dbi:".
3116 The following limitations apply when Bacula is set to use the libdbi framework:
3117 - Not tested on the Win32 platform
3118 - A little performance is lost if comparing with native database driver.
3119 The reason is bound with the database driver provided by libdbi and the
3120 simple fact that one more layer of code was added.
3122 It is important to remember, when compiling Bacula with libdbi, the
3123 following packages are needed:
3125 \item libdbi version 1.0.0, http://libdbi.sourceforge.net/
3126 \item libdbi-drivers 1.0.0, http://libdbi-drivers.sourceforge.net/
3129 You can download them and compile them on your system or install the packages
3130 from your OS distribution.
3132 \subsection{Console Command Additions and Enhancements}
3133 \index[general]{Console Additions}
3135 \subsubsection{Display Autochanger Content}
3136 \index[general]{StatusSlots}
3138 The {\bf status slots storage=\lt{}storage-name\gt{}} command displays
3139 autochanger content.
3143 Slot | Volume Name | Status | Media Type | Pool |
3144 ------+---------------+----------+-------------------+------------|
3145 1 | 00001 | Append | DiskChangerMedia | Default |
3146 2 | 00002 | Append | DiskChangerMedia | Default |
3147 3*| 00003 | Append | DiskChangerMedia | Scratch |
3152 If you an asterisk ({\bf *}) appears after the slot number, you must run an
3153 {\bf update slots} command to synchronize autochanger content with your
3156 \subsubsection{list joblog job=xxx or jobid=nnn}
3157 \index[general]{list joblog}
3158 A new list command has been added that allows you to list the contents
3159 of the Job Log stored in the catalog for either a Job Name (fully qualified)
3160 or for a particular JobId. The {\bf llist} command will include a line with
3161 the time and date of the entry.
3163 Note for the catalog to have Job Log entries, you must have a directive
3170 In your Director's {\bf Messages} resource.
3172 \subsubsection{Use separator for multiple commands}
3173 \index[general]{Command Separator}
3174 When using bconsole with readline, you can set the command separator with
3175 \textbf{@separator} command to one
3176 of those characters to write commands who require multiple input in one line.
3178 !$%&'()*+,-/:;<>?[]^`{|}~
3181 \subsubsection{Deleting Volumes}
3182 The delete volume bconsole command has been modified to
3183 require an asterisk (*) in front of a MediaId otherwise the
3184 value you enter is a taken to be a Volume name. This is so that
3185 users may delete numeric Volume names. The previous Bacula versions
3186 assumed that all input that started with a number was a MediaId.
3188 This new behavior is indicated in the prompt if you read it
3191 \subsection{Bare Metal Recovery}
3192 The old bare metal recovery project is essentially dead. One
3193 of the main features of it was that it would build a recovery
3194 CD based on the kernel on your system. The problem was that
3195 every distribution has a different boot procedure and different
3196 scripts, and worse yet, the boot procedures and scripts change
3197 from one distribution to another. This meant that maintaining
3198 (keeping up with the changes) the rescue CD was too much work.
3200 To replace it, a new bare metal recovery USB boot stick has been developed
3201 by Bacula Systems. This technology involves remastering a Ubuntu LiveCD to
3202 boot from a USB key.
3206 \item Recovery can be done from within graphical environment.
3207 \item Recovery can be done in a shell.
3208 \item Ubuntu boots on a large number of Linux systems.
3209 \item The process of updating the system and adding new
3210 packages is not too difficult.
3211 \item The USB key can easily be upgraded to newer Ubuntu versions.
3212 \item The USB key has writable partitions for modifications to
3213 the OS and for modification to your home directory.
3214 \item You can add new files/directories to the USB key very easily.
3215 \item You can save the environment from multiple machines on
3217 \item Bacula Systems is funding its ongoing development.
3220 The disadvantages are:
3222 \item The USB key is usable but currently under development.
3223 \item Not everyone may be familiar with Ubuntu (no worse
3225 \item Some older OSes cannot be booted from USB. This can
3226 be resolved by first booting a Ubuntu LiveCD then plugging
3228 \item Currently the documentation is sketchy and not yet added
3229 to the main manual. See below ...
3232 The documentation and the code can be found in the {\bf rescue} package
3233 in the directory {\bf linux/usb}.
3235 \subsection{Miscellaneous}
3236 \index[general]{Misc New Features}
3238 \subsubsection{Allow Mixed Priority = \lt{}yes\vb{}no\gt{}}
3239 \index[general]{Allow Mixed Priority}
3240 This directive is only implemented in version 2.5 and later. When
3241 set to {\bf yes} (default {\bf no}), this job may run even if lower
3242 priority jobs are already running. This means a high priority job
3243 will not have to wait for other jobs to finish before starting.
3244 The scheduler will only mix priorities when all running jobs have
3247 Note that only higher priority jobs will start early. Suppose the
3248 director will allow two concurrent jobs, and that two jobs with
3249 priority 10 are running, with two more in the queue. If a job with
3250 priority 5 is added to the queue, it will be run as soon as one of
3251 the running jobs finishes. However, new priority 10 jobs will not
3252 be run until the priority 5 job has finished.
3254 \subsubsection{Bootstrap File Directive -- FileRegex}
3255 \index[general]{Bootstrap File Directive}
3256 {\bf FileRegex} is a new command that can be added to the bootstrap
3257 (.bsr) file. The value is a regular expression. When specified, only
3258 matching filenames will be restored.
3260 During a restore, if all File records are pruned from the catalog
3261 for a Job, normally Bacula can restore only all files saved. That
3262 is there is no way using the catalog to select individual files.
3263 With this new feature, Bacula will ask if you want to specify a Regex
3264 expression for extracting only a part of the full backup.
3267 Building directory tree for JobId(s) 1,3 ...
3268 There were no files inserted into the tree, so file selection
3269 is not possible.Most likely your retention policy pruned the files
3271 Do you want to restore all the files? (yes\vb{}no): no
3273 Regexp matching files to restore? (empty to abort): /tmp/regress/(bin|tests)/
3274 Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr
3277 \subsubsection{Bootstrap File Optimization Changes}
3278 In order to permit proper seeking on disk files, we have extended the bootstrap
3279 file format to include a {\bf VolStartAddr} and {\bf VolEndAddr} records. Each
3280 takes a 64 bit unsigned integer range (i.e. nnn-mmm) which defines the start
3281 address range and end address range respectively. These two directives replace
3282 the {\bf VolStartFile}, {\bf VolEndFile}, {\bf VolStartBlock} and {\bf
3283 VolEndBlock} directives. Bootstrap files containing the old directives will
3284 still work, but will not properly take advantage of proper disk seeking, and
3285 may read completely to the end of a disk volume during a restore. With the new
3286 format (automatically generated by the new Director), restores will seek
3287 properly and stop reading the volume when all the files have been restored.
3289 \subsubsection{Solaris ZFS/NFSv4 ACLs}
3290 This is an upgrade of the previous Solaris ACL backup code
3291 to the new library format, which will backup both the old
3292 POSIX(UFS) ACLs as well as the ZFS ACLs.
3294 The new code can also restore POSIX(UFS) ACLs to a ZFS filesystem
3295 (it will translate the POSIX(UFS)) ACL into a ZFS/NFSv4 one) it can also
3296 be used to transfer from UFS to ZFS filesystems.
3299 \subsubsection{Virtual Tape Emulation}
3300 \index[general]{Virtual Tape Emulation}
3301 We now have a Virtual Tape emulator that allows us to run though 99.9\% of
3302 the tape code but actually reading and writing to a disk file. Used with the
3303 \textbf{disk-changer} script, you can now emulate an autochanger with 10 drives
3304 and 700 slots. This feature is most useful in testing. It is enabled
3305 by using {\bf Device Type = vtape} in the Storage daemon's Device
3306 directive. This feature is only implemented on Linux machines and should not be
3307 used for production.
3309 \subsubsection{Bat Enhancements}
3310 \index[general]{Bat Enhancements}
3311 Bat (the Bacula Administration Tool) GUI program has been significantly
3312 enhanced and stabilized. In particular, there are new table based status
3313 commands; it can now be easily localized using Qt4 Linguist.
3315 The Bat communications protocol has been significantly enhanced to improve
3316 GUI handling. Note, you {\bf must} use a the bat that is distributed with
3317 the Director you are using otherwise the communications protocol will not
3320 \subsubsection{RunScript Enhancements}
3321 \index[general]{RunScript Enhancements}
3322 The {\bf RunScript} resource has been enhanced to permit multiple
3323 commands per RunScript. Simply specify multiple {\bf Command} directives
3330 Command = "/bin/echo test"
3331 Command = "/bin/echo an other test"
3332 Command = "/bin/echo 3 commands in the same runscript"
3339 A new Client RunScript {\bf RunsWhen} keyword of {\bf AfterVSS} has been
3340 implemented, which runs the command after the Volume Shadow Copy has been made.
3342 Console commands can be specified within a RunScript by using:
3343 {\bf Console = \lt{}command\gt{}}, however, this command has not been
3344 carefully tested and debugged and is known to easily crash the Director.
3345 We would appreciate feedback. Due to the recursive nature of this command, we
3346 may remove it before the final release.
3348 \subsubsection{Status Enhancements}
3349 \index[general]{Status Enhancements}
3350 The bconsole {\bf status dir} output has been enhanced to indicate
3351 Storage daemon job spooling and despooling activity.
3353 \subsubsection{Connect Timeout}
3354 \index[general]{Connect Timeout}
3355 The default connect timeout to the File
3356 daemon has been set to 3 minutes. Previously it was 30 minutes.
3358 \subsubsection{ftruncate for NFS Volumes}
3359 \index[general]{ftruncate for NFS Volumes}
3360 If you write to a Volume mounted by NFS (say on a local file server),
3361 in previous Bacula versions, when the Volume was recycled, it was not
3362 properly truncated because NFS does not implement ftruncate (file
3363 truncate). This is now corrected in the new version because we have
3364 written code (actually a kind user) that deletes and recreates the Volume,
3365 thus accomplishing the same thing as a truncate.
3367 \subsubsection{Support for Ubuntu}
3368 The new version of Bacula now recognizes the Ubuntu (and Kubuntu)
3369 version of Linux, and thus now provides correct autostart routines.
3370 Since Ubuntu officially supports Bacula, you can also obtain any
3371 recent release of Bacula from the Ubuntu repositories.
3373 \subsubsection{Recycle Pool = \lt{}pool-name\gt{}}
3374 \index[general]{Recycle Pool}
3375 The new \textbf{RecyclePool} directive defines to which pool the Volume will
3376 be placed (moved) when it is recycled. Without this directive, a Volume will
3377 remain in the same pool when it is recycled. With this directive, it can be
3378 moved automatically to any existing pool during a recycle. This directive is
3379 probably most useful when defined in the Scratch pool, so that volumes will
3380 be recycled back into the Scratch pool.
3382 \subsubsection{FD Version}
3383 \index[general]{FD Version}
3384 The File daemon to Director protocol now includes a version
3385 number, which although there is no visible change for users,
3386 will help us in future versions automatically determine
3387 if a File daemon is not compatible.
3389 \subsubsection{Max Run Sched Time = \lt{}time-period-in-seconds\gt{}}
3390 \index[general]{Max Run Sched Time}
3391 The time specifies the maximum allowed time that a job may run, counted from
3392 when the job was scheduled. This can be useful to prevent jobs from running
3393 during working hours. We can see it like \texttt{Max Start Delay + Max Run
3396 \subsubsection{Max Wait Time = \lt{}time-period-in-seconds\gt{}}
3397 \index[general]{Max Wait Time}
3398 Previous \textbf{MaxWaitTime} directives aren't working as expected, instead
3399 of checking the maximum allowed time that a job may block for a resource,
3400 those directives worked like \textbf{MaxRunTime}. Some users are reporting to
3401 use \textbf{Incr/Diff/Full Max Wait Time} to control the maximum run time of
3402 their job depending on the level. Now, they have to use
3403 \textbf{Incr/Diff/Full Max Run Time}. \textbf{Incr/Diff/Full Max Wait Time}
3404 directives are now deprecated.
3406 \subsubsection{Incremental|Differential Max Wait Time = \lt{}time-period-in-seconds\gt{}}
3407 \index[general]{Incremental Max Wait Time}
3408 \index[general]{Differential Max Wait Time}
3410 These directives have been deprecated in favor of
3411 \texttt{Incremental|Differential Max Run Time}.
3413 \subsubsection{Max Run Time directives}
3414 \index[general]{Max Run Time directives}
3415 Using \textbf{Full/Diff/Incr Max Run Time}, it's now possible to specify the
3416 maximum allowed time that a job can run depending on the level.
3418 \addcontentsline{lof}{figure}{Job time control directives}
3420 \includegraphics[width=\linewidth]{different_time}
3423 \subsubsection{Statistics Enhancements}
3424 \index[general]{Statistics Enhancements}
3425 If you (or probably your boss) want to have statistics on your backups to
3426 provide some \textit{Service Level Agreement} indicators, you could use a few
3427 SQL queries on the Job table to report how many:
3431 \item jobs have been successful
3432 \item files have been backed up
3436 However, these statistics are accurate only if your job retention is greater
3437 than your statistics period. Ie, if jobs are purged from the catalog, you won't
3438 be able to use them.
3440 Now, you can use the \textbf{update stats [days=num]} console command to fill
3441 the JobHistory table with new Job records. If you want to be sure to take in
3442 account only \textbf{good jobs}, ie if one of your important job has failed but
3443 you have fixed the problem and restarted it on time, you probably want to
3444 delete the first \textit{bad} job record and keep only the successful one. For
3445 that simply let your staff do the job, and update JobHistory table after two or
3446 three days depending on your organization using the \textbf{[days=num]} option.
3448 These statistics records aren't used for restoring, but mainly for
3449 capacity planning, billings, etc.
3451 The Bweb interface provides a statistics module that can use this feature. You
3452 can also use tools like Talend or extract information by yourself.
3454 The \textbf{Statistics Retention = \lt{}time\gt{}} director directive defines
3455 the length of time that Bacula will keep statistics job records in the Catalog
3456 database after the Job End time. (In \texttt{JobHistory} table) When this time
3457 period expires, and if user runs \texttt{prune stats} command, Bacula will
3458 prune (remove) Job records that are older than the specified period.
3460 You can use the following Job resource in your nightly \textbf{BackupCatalog}
3461 job to maintain statistics.
3464 Name = BackupCatalog
3467 Console = "update stats days=3"
3468 Console = "prune stats yes"
3475 \subsubsection{ScratchPool = \lt{}pool-resource-name\gt{}}
3476 \index[general]{ScratchPool}
3477 This directive permits to specify a specific \textsl{Scratch} pool for the
3478 current pool. This is useful when using multiple storage sharing the same
3479 mediatype or when you want to dedicate volumes to a particular set of pool.
3481 \subsubsection{Enhanced Attribute Despooling}
3482 \index[general]{Attribute Despooling}
3483 If the storage daemon and the Director are on the same machine, the spool file
3484 that contains attributes is read directly by the Director instead of being
3485 transmitted across the network. That should reduce load and speedup insertion.
3487 \subsubsection{SpoolSize = \lt{}size-specification-in-bytes\gt{}}
3488 \index[general]{SpoolSize}
3489 A new Job directive permits to specify the spool size per job. This is used
3490 in advanced job tunning. {\bf SpoolSize={\it bytes}}
3492 \subsubsection{MaximumConsoleConnections = \lt{}number\gt{}}
3493 \index[general]{MaximumConsoleConnections}
3494 A new director directive permits to specify the maximum number of Console
3495 Connections that could run concurrently. The default is set to 20, but you may
3496 set it to a larger number.
3498 \subsubsection{VerId = \lt{}string\gt{}}
3499 \index[general]{VerId}
3500 A new director directive permits to specify a personnal identifier that will be
3501 displayed in the \texttt{version} command.
3503 \subsubsection{dbcheck enhancements}
3504 \index[general]{dbcheck enhancements}
3505 If you are using Mysql, dbcheck will now ask you if you want to create
3506 temporary indexes to speed up orphaned Path and Filename elimination.
3508 A new \texttt{-B} option allows you to print catalog information in a simple
3509 text based format. This is useful to backup it in a secure way.
3524 You can now specify the database connection port in the command line.
3526 \subsubsection{{-}{-}docdir configure option}
3527 \index[general]{{-}{-}docdir configure option}
3528 You can use {-}{-}docdir= on the ./configure command to
3529 specify the directory where you want Bacula to install the
3530 LICENSE, ReleaseNotes, ChangeLog, ... files. The default is
3531 {\bf /usr/share/doc/bacula}.
3533 \subsubsection{{-}{-}htmldir configure option}
3534 \index[general]{{-}{-}htmldir configure option}
3535 You can use {-}{-}htmldir= on the ./configure command to
3536 specify the directory where you want Bacula to install the bat html help
3537 files. The default is {\bf /usr/share/doc/bacula/html}
3539 \subsubsection{{-}{-}with-plugindir configure option}
3540 \index[general]{{-}{-}plugindir configure option}
3541 You can use {-}{-}plugindir= on the ./configure command to
3542 specify the directory where you want Bacula to install
3543 the plugins (currently only bpipe-fd). The default is