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 schedule}
48 A new status command option called {\bf scheduled} has been implemented
49 in bconsole. By default it will display 20 lines of the next scheduled
50 jobs. For example, with the default bacula-dir.conf configuration file,
51 a bconsole command {\bf status scheduled} produces:
55 Level Type Pri Scheduled Job Name Schedule
56 ======================================================================
57 Differential Backup 10 Sun 30-Mar 23:05 BackupClient1 WeeklyCycle
58 Incremental Backup 10 Mon 24-Mar 23:05 BackupClient1 WeeklyCycle
59 Incremental Backup 10 Tue 25-Mar 23:05 BackupClient1 WeeklyCycle
61 Full Backup 11 Mon 24-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
62 Full Backup 11 Wed 26-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
67 Note, the output is listed by the Jobs found, and is not sorted
71 This command has a number of options, most of which act as filters:
73 \item {\bf days=nn} This specifies the number of days to list. The default is
74 10 but can be set from 0 to 500.
75 \item {\bf limit=nn} This specifies the limit to the number of lines to print.
76 The default is 100 but can be any number in the range 0 to 2000.
77 \item {\bf time="YYYY-MM-DD HH:MM:SS"} Sets the start time for listing the
78 scheduled jobs. The default is to use the current time. Note, the
79 time value must be specified inside double quotes and must be in
80 the exact form shown above.
81 \item {\bf schedule=schedule-name} This option restricts the output to
83 \item {\bf job=job-name} This option restricts the output to the specified
87 \subsection{Data Encryption Cipher Configuration}
88 Bacula version 7.0 and later now allows to configure the data
89 encryption cipher and the digest algorithm. The cipher was forced to AES
90 128, and it is now possible to choose between the following ciphers:
93 \item AES128 (default)
99 The digest algorithm was set to SHA1 or SHA256 depending on the local
101 options. We advise you to not modify the PkiDigest default setting. Please,
102 refer to OpenSSL documentation to know about pro and cons on these options.
111 \subsection{New Truncate Command}
112 We have added a new truncate command to bconsole, which
113 will truncate a Volume if the Volume is purged and if
114 the Volume is also marked {\bf Action On Purge = Truncate}.
115 This feature was originally added in Bacula version 5.0.1,
116 but the mechanism for actually doing the truncate required
117 the user to enter a command such as:
120 purge volume action=truncate storage=File pool=Default
123 The above command is now simplified to be:
126 truncate storage=File pool=Default
129 \subsection{New Resume Command}
130 This command does exactly the same thing as a
131 {\bf restart} command but for some users the
132 name may be more logical since in general the
133 {\bf restart} command is used to resume running
134 a Job that was incompleted.
136 \subsection{Migration/Copy/VirtualFull Performance Enhancements}
137 The Bacula Storage daemon now permits multiple jobs to simultaneously read
138 the same disk Volume, which gives substantial performance enhancements when
139 running Migration, Copy, or VirtualFull jobs that read disk Volumes. Our
140 testing shows that when running multiple simultaneous jobs, the jobs can
141 finish up to ten times faster with this version of Bacula. This is
142 built-in to the Storage daemon, so it happens automatically and
145 \subsection{VirtualFull Backup Consolidation Enhancements}
146 By default Bacula selects jobs automatically for a VirtualFull,
147 however, you may want to create the Virtual backup based on a
148 particular backup (point in time) that exists.
150 For example, if you have the following backup Jobs in your catalog:
152 +-------+---------+-------+----------+----------+-----------+
153 | JobId | Name | Level | JobFiles | JobBytes | JobStatus |
154 +-------+---------+-------+----------+----------+-----------+
155 | 1 | Vbackup | F | 1754 | 50118554 | T |
156 | 2 | Vbackup | I | 1 | 4 | T |
157 | 3 | Vbackup | I | 1 | 4 | T |
158 | 4 | Vbackup | D | 2 | 8 | T |
159 | 5 | Vbackup | I | 1 | 6 | T |
160 | 6 | Vbackup | I | 10 | 60 | T |
161 | 7 | Vbackup | I | 11 | 65 | T |
162 | 8 | Save | F | 1758 | 50118564 | T |
163 +-------+---------+-------+----------+----------+-----------+
166 and you want to consolidate only the first 3 jobs and create a
167 virtual backup equivalent to Job 1 + Job 2 + Job 3, you will use
168 \texttt{jobid=3} in the \texttt{run} command, then Bacula will select the
169 previous Full backup, the previous Differential (if any) and all subsequent
173 run job=Vbackup jobid=3 level=VirtualFull
176 If you want to consolidate a specific job list, you must specify the exact
177 list of jobs to merge in the run command line. For example, to consolidate
178 the last Differential and all subsequent Incremental, you will use
179 \texttt{jobid=4,5,6,7} or \texttt{jobid=4-7} on the run command line. As one
180 of the Job in the list is a Differential backup, Bacula will set the new job
181 level to Differential. If the list is composed only with Incremental jobs,
182 the new job will have a level set to Incremental.
185 run job=Vbackup jobid=4-7 level=VirtualFull
188 When using this feature, Bacula will automatically discard jobs that are
189 not related to the current Job. For example, specifying
190 \texttt{jobid=7,8}, Bacula will discard JobId 8 because it is not
191 part of the same backup Job.
193 We do not recommend it, but really want to consolidate jobs that have
194 different names (so probably different clients, filesets, etc...), you must
195 use \texttt{alljobid=} keyword instead of \texttt{jobid=}.
198 run job=Vbackup alljobid=1-3,6-8 level=VirtualFull
202 \subsection{FD Storage Address}
204 When the Director is behind a NAT, in a WAN area, to connect to
206 the StorageDaemon, the Director uses an ``external'' ip address,
207 and the FileDaemon should use an ``internal'' IP address to contact the
210 The normal way to handle this situation is to use a canonical name such as
211 ``storage-server'' that will be resolved on the Director side as the WAN
212 address and on the Client side as the LAN address. This is now possible to
213 configure this parameter using the new directive \texttt{FDStorageAddress} in
214 the Storage or Client resource.
217 \includegraphics[width=0.8\linewidth]{BackupOverWan1}
218 \label{fig:fdstorageaddress}
224 FD Storage Address = 10.0.0.1
230 % # or in the Client resouce
237 FD Storage Address = 10.0.0.1
243 Note that using the Client \texttt{FDStorageAddress} directive will not allow
244 to use multiple Storage Daemon, all Backup or Restore requests will be sent to
245 the specified \texttt{FDStorageAddress}.
247 \subsection{Job Bandwidth Limitation}
249 The new {\bf Job Bandwidth Limitation} directive may be added to the File
250 daemon's and/or Director's configuration to limit the bandwidth used by a
251 Job on a Client. It can be set in the File daemon's conf file for all Jobs
252 run in that File daemon, or it can be set for each Job in the Director's
253 conf file. The speed is always specified in bytes per second.
259 Working Directory = /some/path
260 Pid Directory = /some/path
262 Maximum Bandwidth Per Job = 5Mb/s
266 The above example would cause any jobs running with the FileDaemon to not
267 exceed 5 megabytes per second of throughput when sending data to the
268 Storage Daemon. Note, the speed is always specified in bytes per second
269 (not in bits per second), and the case (upper/lower) of the specification
270 characters is ignored (i.e. 1MB/s = 1Mb/s).
272 You may specify the following speed parameter modifiers:
273 k/s (1,000 bytes per second), kb/s (1,024 bytes per second),
274 m/s (1,000,000 bytes per second), or mb/s (1,048,576 bytes per second).
280 FileSet = FS_localhost
283 Maximum Bandwidth = 5Mb/s
288 The above example would cause Job \texttt{localhost-data} to not exceed 5MB/s
289 of throughput when sending data from the File daemon to the Storage daemon.
291 A new console command \texttt{setbandwidth} permits to set dynamically the
292 maximum throughput of a running Job or for future jobs of a Client.
295 * setbandwidth limit=1000 jobid=10
298 Please note that the value specified for the \texttt{limit} command
299 line parameter is always in units of 1024 bytes (i.e. the number
300 is multiplied by 1024 to give the number of bytes per second). As
301 a consequence, the above limit of 1000 will be interpreted as a
302 limit of 1000 * 1024 = 1,024,000 bytes per second.
305 This project was funded by Bacula Systems.
308 \subsection{Maximum Concurrent Read Jobs}
309 This is a new directive that can be used in the {\bf bacula-dir.conf} file
310 in the Storage resource. The main purpose is to limit the number
311 of concurrent Copy, Migration, and VirtualFull jobs so that
312 they don't monopolize all the Storage drives causing a deadlock situation
313 where all the drives are allocated for reading but none remain for
314 writing. This deadlock situation can occur when running multiple
315 simultaneous Copy, Migration, and VirtualFull jobs.
318 The default value is set to 0 (zero), which means there is no
319 limit on the number of read jobs. Note, limiting the read jobs
320 does not apply to Restore jobs, which are normally started by
321 hand. A reasonable value for this directive is one half the number
322 of drives that the Storage resource has rounded down. Doing so,
323 will leave the same number of drives for writing and will generally
324 avoid over committing drives and a deadlock.
327 \subsection{Director job Codes in Message Resource Commands}
328 Before submitting the specified mail command to the operating system, Bacula
329 performs character substitution like in Runscript commands. Bacula will now
330 perform also specific Director character substitution.
333 The code for this feature was contributed by Bastian Friedrich.
335 \subsection{Additions to RunScript variables}
336 The following variables are now available in runscripts:
338 \item current PID using \%P
339 \item if the job is a clone job using \%C
343 RunAfterJob = "/bin/echo Pid=%P isCloned=%C"
347 \subsection{Read Only Storage Devices}
348 This version of Bacula permits defining a Storage deamon device
349 to be read-only. That is if the {\bf ReadOnly} directive is specified and
350 enabled, the drive can only be used for read operations.
351 The the {\bf ReadOnly} directive can be defined in any bacula-sd.conf
352 Device resource, and is most useful to reserve one or more
353 drives for restores. An example is:
359 \subsection{New Prune ``Expired'' Volume Command}
360 It is now possible to prune all volumes
361 (from a pool, or globally) that are ``expired''. This option can be
362 scheduled after or before the backup of the Catalog and can be
363 combined with the Truncate On Purge option. The Expired Prune option can
364 be used instead of the \texttt{manual\_prune.pl} script.
367 * prune expired volumes
369 * prune expired volumes pool=FullPool
372 To schedule this option automatically, it can be added to the BackupCatalog job
380 Console = "prune expired volume yes"
386 \subsection{Hardlink Performance Enhancements}
387 If you use a program such as Cyrus IMAP that creates very large numbers
388 of hardlinks, the time to build the interactive restore tree can be
389 excessively long. This version of Bacula has a new feature that
390 automatically keeps the hardlinks associated with the restore tree
391 in memory, which consumes a bit more memory but vastly speeds up
392 building the tree. If the memory usage is too big for your system, you
393 can reduce the amount of memory used during the restore command by
394 adding the option {\bf optimizespeed=false} on the bconsole run
397 This feature was developed by Josip Almasi, and enhanced to be runtime
398 dynamic by Kern Sibbald.
400 \subsection{Multiple Console Directors}
401 Support for multiple bconsole and bat Directors in the bconsole.conf and
402 bat.conf files has been implemented and/or improved.
404 \subsection{Restricted Consoles}
405 Better support for Restricted consoles has been implement for bconsole and
408 \subsection{Configuration Files}
409 In previous versions of Bacula the configuration files for each component
410 were limited to a maximum of 499 bytes per configuration file line. This
411 version of Bacula permits unlimited input line lengths. This can be
412 especially useful for specifying more complicated Migration/Copy SQL
413 statements and in creating long restricted console ACL lists.
415 \subsection{Maximum Spawned Jobs}
416 The Job resource now permits specifing a number of {\bf Maximum Spawn
417 Jobs}. The default is 300. This directive can be useful if you have
418 big hardware and you do a lot of Migration/Copy jobs which start
419 at the same time. In prior versions of Bacula, Migration/Copy
420 was limited to spawning a maximum of 100 jobs at a time.
422 \subsection{Progress Meter}
423 The new File daemon has been enhanced to send its progress (files
424 processed and bytes written) to the Director every 30 seconds. These
425 figures can then be displayed with a bconsole {\bf status dir}
428 \subsection{Scheduling a 6th Week}
429 Prior version of Bacula permits specifying 1st through 5th week of
430 a month (first through fifth) as a keyword on the {\bf run}
431 directive of a Schedule resource. This version of Bacula also permits
432 specifying the 6th week of a month with the keyword {\bf sixth} or
435 \subsection{Secheduling the Last Day of a Month}
436 This version of Bacula now premits specifying the {\bf lastday}
437 keyword in the {\bf run} directive of a Schedule resource.
438 If {\bf lastday} is specified, it will apply only to those months
439 specified on the {\bf run} directive. Note: by default all months
442 \subsection{Improvements to Cancel and Restart bconsole Commands}
443 The Restart bconsole command now allow selection of either
444 canceled or failed jobs to be restarted. In addition both the
445 {\bf cancel} and {\bf restart} bconsole commands permit entering
446 a number of JobIds separated by commas or a range of JobIds indicated
447 by a dash between the begin and end range (e.g. 3-10). Finally the
448 two commands also allow one to enter the special keyword {\bf all}
449 to select all the appropriate Jobs.
451 \subsection{bconsole Performance Improvements}
452 In previous versions of Bacula certain bconsole commands could wait a long
453 time due to catalog lock contention. This was especially noticable
454 when a large number of jobs were running and putting their attributes
455 into the catalog. This version uses a separate catalog connection that
456 should significantly enhance performance.
461 \subsection*{New Debug Options}
463 In Bacula Enterprise version 8.0 and later, we introduced new options to
464 the \texttt{setdebug} command.
468 If the \texttt{options} parameter is set, the following arguments can be
469 used to control debug functions.
472 \item [0] clear debug flags
473 \item [i] Turn off, ignore bwrite() errors on restore on File Daemon
474 \item [d] Turn off decomp of BackupRead() streams on File Daemon
475 \item [t] Turn on timestamp in traces
476 \item [T] Turn off timestamp in traces
477 \item [c] Truncate trace file if trace file is activated
478 \item [l] Turn on recoding events on P() and V()
479 \item [p] Turn on the display of the event ring when doing a bactrace
484 The following command will truncate the trace file and will turn on timestamps
488 * setdebug level=10 trace=1 options=ct fd
493 It is now possible to use \textsl{class} of debug messages called \texttt{tags}
494 to control the debug output of Bacula daemons.
497 \item [all] Display all debug messages
498 \item [bvfs] Display BVFS debug messages
499 \item [sql] Display SQL related debug messages
500 \item [memory] Display memory and poolmem allocation messages
501 \item [scheduler] Display scheduler related debug messages
505 * setdebug level=10 tags=bvfs,sql,memory
506 * setdebug level=10 tags=!bvfs
508 # bacula-dir -t -d 200,bvfs,sql
511 The \texttt{tags} option is composed of a list of tags, tags are separated by
512 ``,'' or ``+'' or ``-'' or ``!''. To disable a specific tag, use ``-'' or ``!''
513 in front of the tag. Note that more tags will come in future versions.
515 %\LTXtable{\linewidth}{table_debugtags}
518 \chapter{New Features in 5.2.13}
519 This chapter presents the new features that have been added to the current
520 Community version of Bacula that is now released.
522 \subsection{Additions to RunScript variables}
523 You can have access to Director name using \%D in your runscript
527 RunAfterJob = "/bin/echo Director=%D
530 \section{New Features in 5.2.1}
531 This chapter presents the new features were added in the
532 Community release version 5.2.1.
534 There are additional features (plugins) available in the Enterprise version
535 that are described in another chapter. A subscription to Bacula Systems
536 is required for the Enterprise version.
538 \subsection{LZO Compression}
540 LZO compression has been to the File daemon. From the user's point of view,
541 it works like the GZIP compression (just replace {\bf compression=GZIP} with
542 {\bf compression=LZO}).
547 Options {compression=LZO }
553 LZO provides a much faster compression and decompression speed but lower
554 compression ratio than GZIP. It is a good option when you backup to disk. For
555 tape, the hardware compression is almost always a better option.
557 LZO is a good alternative for GZIP1 when you don't want to slow down your
558 backup. With a modern CPU it should be able to run almost as fast as:
561 \item your client can read data from disk. Unless you have very fast disks like
562 SSD or large/fast RAID array.
563 \item the data transfers between the file daemon and the storage daemon even on
567 Note, Bacula uses compression level LZO1X-1.
570 The code for this feature was contributed by Laurent Papier.
572 \subsection{New Tray Monitor}
574 Since the old integrated Windows tray monitor doesn't work with
575 recent Windows versions, we have written a new Qt Tray Monitor that is available
576 for both Linux and Windows. In addition to all the previous features,
577 this new version allows you to run Backups from
578 the tray monitor menu.
582 \includegraphics[width=0.8\linewidth]{tray-monitor}
583 \label{fig:traymonitor}
584 \caption{New tray monitor}
589 \includegraphics[width=0.8\linewidth]{tray-monitor1}
590 \label{fig:traymonitor1}
591 \caption{Run a Job through the new tray monitor}
595 To be able to run a job from the tray monitor, you need to
596 allow specific commands in the Director monitor console:
601 CommandACL = status, .clients, .jobs, .pools, .storage, .filesets, .messages, run
602 ClientACL = *all* # you can restrict to a specific host
614 This project was funded by Bacula Systems and is available with Bacula
615 the Enterprise Edition and the Community Edition.
617 \subsection{Purge Migration Job}
619 The new {\bf Purge Migration Job} directive may be added to the Migration
620 Job definition in the Director's configuration file. When it is enabled
621 the Job that was migrated during a migration will be purged at
622 the end of the migration job.
630 Client = localhost-fd
633 Storage = DiskChanger
636 Selection Pattern = ".*Save"
638 Purge Migration Job = yes
644 This project was submitted by Dunlap Blake; testing and documentation was funded
647 \subsection{Changes in Bvfs (Bacula Virtual FileSystem)}
649 Bat has now a bRestore panel that uses Bvfs to display files and
654 \includegraphics[width=0.8\linewidth]{bat-brestore}
655 \label{fig:batbrestore}
656 \caption{Bat Brestore Panel}
659 the Bvfs module works correctly with BaseJobs, Copy and Migration jobs.
662 This project was funded by Bacula Systems.
664 \subsubsection*{General notes}
667 \item All fields are separated by a tab
668 \item You can specify \texttt{limit=} and \texttt{offset=} to list smoothly
669 records in very big directories
670 \item All operations (except cache creation) are designed to run instantly
671 \item At this time, Bvfs works faster on PostgreSQL than MySQL catalog. If you
672 can contribute new faster SQL queries we will be happy, else don't complain
674 \item The cache creation is dependent of the number of directories. As Bvfs
675 shares information across jobs, the first creation can be slow
676 \item All fields are separated by a tab
677 \item Due to potential encoding problem, it's advised to always use pathid in
681 \subsubsection*{Get dependent jobs from a given JobId}
683 Bvfs allows you to query the catalog against any combination of jobs. You
684 can combine all Jobs and all FileSet for a Client in a single session.
686 To get all JobId needed to restore a particular job, you can use the
687 \texttt{.bvfs\_get\_jobids} command.
690 .bvfs_get_jobids jobid=num [all]
694 .bvfs_get_jobids jobid=10
696 .bvfs_get_jobids jobid=10 all
700 In this example, a normal restore will need to use JobIds 1,2,5,10 to
701 compute a complete restore of the system.
703 With the \texttt{all} option, the Director will use all defined FileSet for
706 \subsubsection*{Generating Bvfs cache}
708 The \texttt{.bvfs\_update} command computes the directory cache for jobs
709 specified in argument, or for all jobs if unspecified.
712 .bvfs_update [jobid=numlist]
717 .bvfs_update jobid=1,2,3
720 You can run the cache update process in a RunScript after the catalog backup.
722 \subsubsection*{Get all versions of a specific file}
724 Bvfs allows you to find all versions of a specific file for a given Client with
725 the \texttt{.bvfs\_version} command. To avoid problems with encoding, this
726 function uses only PathId and FilenameId. The jobid argument is mandatory but
730 .bvfs_versions client=filedaemon pathid=num filenameid=num jobid=1
731 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
732 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
739 .bvfs_versions client=localhost-fd pathid=1 fnid=47 jobid=1
740 1 47 52 12 gD HRid IGk D Po Po A P BAA I A /uPgWaxMgKZlnMti7LChyA Vol1 1
743 \subsubsection*{List directories}
745 Bvfs allows you to list directories in a specific path.
747 .bvfs_lsdirs pathid=num path=/apath jobid=numlist limit=num offset=num
748 PathId FilenameId FileId JobId LStat Path
749 PathId FilenameId FileId JobId LStat Path
750 PathId FilenameId FileId JobId LStat Path
754 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
755 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record
756 listed is a directory.
759 .bvfs_lsdirs pathid=4 jobid=1,11,12
760 4 0 0 0 A A A A A A A A A A A A A A .
761 5 0 0 0 A A A A A A A A A A A A A A ..
762 3 0 0 0 A A A A A A A A A A A A A A regress/
765 In this example, to list directories present in \texttt{regress/}, you can use
767 .bvfs_lsdirs pathid=3 jobid=1,11,12
768 3 0 0 0 A A A A A A A A A A A A A A .
769 4 0 0 0 A A A A A A A A A A A A A A ..
770 2 0 0 0 A A A A A A A A A A A A A A tmp/
773 \subsubsection*{List files}
775 Bvfs allows you to list files in a specific path.
777 .bvfs_lsfiles pathid=num path=/apath jobid=numlist limit=num offset=num
778 PathId FilenameId FileId JobId LStat Path
779 PathId FilenameId FileId JobId LStat Path
780 PathId FilenameId FileId JobId LStat Path
784 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
785 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record listed
789 .bvfs_lsfiles pathid=4 jobid=1,11,12
790 4 0 0 0 A A A A A A A A A A A A A A .
791 5 0 0 0 A A A A A A A A A A A A A A ..
792 1 0 0 0 A A A A A A A A A A A A A A regress/
795 In this example, to list files present in \texttt{regress/}, you can use
797 .bvfs_lsfiles pathid=1 jobid=1,11,12
798 1 47 52 12 gD HRid IGk BAA I BMqcPH BMqcPE BMqe+t A titi
799 1 49 53 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B toto
800 1 48 54 12 gD HRie IGk BAA I BMqcPH BMqcPE BMqe+3 A tutu
801 1 45 55 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B ficheriro1.txt
802 1 46 56 12 gD HRie IGk BAA I BMqe/K BMqcPE BMqe+3 D ficheriro2.txt
805 \subsubsection*{Restore set of files}
807 Bvfs allows you to create a SQL table that contains files that you want to
808 restore. This table can be provided to a restore command with the file option.
811 .bvfs_restore fileid=numlist dirid=numlist hardlink=numlist path=b2num
813 restore file=?b2num ...
816 To include a directory (with \texttt{dirid}), Bvfs needs to run a query to
817 select all files. This query could be time consuming.
819 \texttt{hardlink} list is always composed of a series of two numbers (jobid,
820 fileindex). This information can be found in the LinkFI field of the LStat
823 The \texttt{path} argument represents the name of the table that Bvfs will
824 store results. The format of this table is \texttt{b2[0-9]+}. (Should start by
825 b2 and followed by digits).
830 .bvfs_restore fileid=1,2,3,4 hardlink=10,15,10,20 jobid=10 path=b20001
834 \subsubsection*{Cleanup after Restore}
836 To drop the table used by the restore command, you can use the
837 \texttt{.bvfs\_cleanup} command.
840 .bvfs_cleanup path=b20001
843 \subsubsection*{Clearing the BVFS Cache}
845 To clear the BVFS cache, you can use the \texttt{.bvfs\_clear\_cache} command.
848 .bvfs_clear_cache yes
852 \subsection{Changes in the Pruning Algorithm}
854 We rewrote the job pruning algorithm in this version. Previously, in some users
855 reported that the pruning process at the end of jobs was very long. It should
856 not be longer the case. Now, Bacula won't prune automatically a Job if this
857 particular Job is needed to restore data. Example:
861 JobId: 2 Level: Incremental
862 JobId: 3 Level: Incremental
863 JobId: 4 Level: Differential
864 .. Other incrementals up to now
867 In this example, if the Job Retention defined in the Pool or in the Client
868 resource causes that Jobs with Jobid in 1,2,3,4 can be pruned, Bacula will
869 detect that JobId 1 and 4 are essential to restore data at the current state
870 and will prune only JobId 2 and 3.
872 \texttt{Important}, this change affect only the automatic pruning step after a
873 Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the
874 \texttt{VolumeRetention} period, important jobs can be pruned.
876 \subsection{Ability to Verify any specified Job}
877 You now have the ability to tell Bacula which Job should verify instead of
878 automatically verify just the last one.
880 This feature can be used with VolumeToCatalog, DiskToCatalog and Catalog level.
882 To verify a given job, just specify the Job jobid in argument when starting the
885 *run job=VerifyVolume jobid=1 level=VolumeToCatalog
887 JobName: VerifyVolume
888 Level: VolumeToCatalog
891 Pool: Default (From Job resource)
892 Storage: File (From Job resource)
893 Verify Job: VerifyVol.2010-09-08_14.17.17_03
894 Verify List: /tmp/regress/working/VerifyVol.bsr
895 When: 2010-09-08 14:17:31
897 OK to run? (yes/mod/no):
901 This project was funded by Bacula Systems and is available with Bacula
902 Enterprise Edition and Community Edition.
904 \subsection{Additions to RunScript variables}
905 You can have access to JobBytes and JobFiles using \%b and \%F in your runscript
906 command. The Client address is now available through \%h.
909 RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%F ClientAddress=%h"
912 %\subsection{Changes in drivetype.exe}
914 %Now the \texttt{drivetype.exe} program allows you to list all local hard
915 %drives. It can help to build dynamic FileSet on Windows.
918 %File = "\\|\"c:/program files/bacula/bin32/drivetype\" -l -a"
922 \subsection{Additions to the Plugin API}
923 The bfuncs structure has been extended to include a number of
926 \subsubsection{bfuncs}
927 The bFuncs structure defines the callback entry points within Bacula
928 that the plugin can use register events, get Bacula values, set
929 Bacula values, and send messages to the Job output or debug output.
931 The exact definition as of this writing is:
933 typedef struct s_baculaFuncs {
936 bRC (*registerBaculaEvents)(bpContext *ctx, ...);
937 bRC (*getBaculaValue)(bpContext *ctx, bVariable var, void *value);
938 bRC (*setBaculaValue)(bpContext *ctx, bVariable var, void *value);
939 bRC (*JobMessage)(bpContext *ctx, const char *file, int line,
940 int type, utime_t mtime, const char *fmt, ...);
941 bRC (*DebugMessage)(bpContext *ctx, const char *file, int line,
942 int level, const char *fmt, ...);
943 void *(*baculaMalloc)(bpContext *ctx, const char *file, int line,
945 void (*baculaFree)(bpContext *ctx, const char *file, int line, void *mem);
947 /* New functions follow */
948 bRC (*AddExclude)(bpContext *ctx, const char *file);
949 bRC (*AddInclude)(bpContext *ctx, const char *file);
950 bRC (*AddIncludeOptions)(bpContext *ctx, const char *opts);
951 bRC (*AddRegex)(bpContext *ctx, const char *item, int type);
952 bRC (*AddWild)(bpContext *ctx, const char *item, int type);
953 bRC (*checkChanges)(bpContext *ctx, struct save_pkt *sp);
959 \item [AddExclude] can be called to exclude a file. The file
960 string passed may include wildcards that will be interpreted by
961 the {\bf fnmatch} subroutine. This function can be called
962 multiple times, and each time the file specified will be added
963 to the list of files to be excluded. Note, this function only
964 permits adding excludes of specific file or directory names,
965 or files matched by the rather simple fnmatch mechanism.
966 See below for information on doing wild-card and regex excludes.
968 \item [NewPreInclude] can be called to create a new Include block. This
969 block will be added after the current defined Include block. This
970 function can be called multiple times, but each time, it will create
971 a new Include section (not normally needed). This function should
972 be called only if you want to add an entirely new Include block.
974 \item [NewInclude] can be called to create a new Include block. This
975 block will be added before any user defined Include blocks. This
976 function can be called multiple times, but each time, it will create
977 a new Include section (not normally needed). This function should
978 be called only if you want to add an entirely new Include block.
980 \item [AddInclude] can be called to add new files/directories to
981 be included. They are added to the current Include block. If
982 NewInclude has not been included, the current Include block is
983 the last one that the user created. This function
984 should be used only if you want to add totally new files/directories
985 to be included in the backup.
987 \item [NewOptions] adds a new Options block to the current Include
988 in front of any other Options blocks. This permits the plugin to
989 add exclude directives (wild-cards and regexes) in front of the
990 user Options, and thus prevent certain files from being backed up.
991 This can be useful if the plugin backs up files, and they should
992 not be also backed up by the main Bacula code. This function
993 may be called multiple times, and each time, it creates a new
994 prepended Options block. Note: normally you want to call this
995 entry point prior to calling AddOptions, AddRegex, or AddWild.
997 \item [AddOptions] allows the plugin it set options in
998 the current Options block, which is normally created with the
999 NewOptions call just prior to adding Include Options.
1000 The permitted options are passed as a character string, where
1001 each character has a specific meaning as defined below:
1004 \item [a] always replace files (default).
1005 \item [e] exclude rather than include.
1006 \item [h] no recursion into subdirectories.
1007 \item [H] do not handle hard links.
1008 \item [i] ignore case in wildcard and regex matches.
1009 \item [M] compute an MD5 sum.
1010 \item [p] use a portable data format on Windows (not recommended).
1011 \item [R] backup resource forks and Findr Info.
1012 \item [r] read from a fifo
1013 \item [S1] compute an SHA1 sum.
1014 \item [S2] compute an SHA256 sum.
1015 \item [S3] comput an SHA512 sum.
1016 \item [s] handle sparse files.
1017 \item [m] use st\_mtime only for file differences.
1018 \item [k] restore the st\_atime after accessing a file.
1019 \item [A] enable ACL backup.
1020 \item [Vxxx:] specify verify options. Must terminate with :
1021 \item [Cxxx:] specify accurate options. Must terminate with :
1022 \item [Jxxx:] specify base job Options. Must terminate with :
1023 \item [Pnnn:] specify integer nnn paths to strip. Must terminate with :
1025 \item [Zn] specify gzip compression level n.
1026 \item [K] do not use st\_atime in backup decision.
1027 \item [c] check if file changed during backup.
1028 \item [N] honor no dump flag.
1029 \item [X] enable backup of extended attributes.
1032 \item [AddRegex] adds a regex expression to the current Options block.
1033 The following options are permitted:
1035 \item [ ] (a blank) regex applies to whole path and filename.
1036 \item [F] regex applies only to the filename (directory or path stripped).
1037 \item [D] regex applies only to the directory (path) part of the name.
1040 \item [AddWild] adds a wildcard expression to the current Options block.
1041 The following options are permitted:
1043 \item [ ] (a blank) regex applies to whole path and filename.
1044 \item [F] regex applies only to the filename (directory or path stripped).
1045 \item [D] regex applies only to the directory (path) part of the name.
1048 \item [checkChanges] call the \texttt{check\_changes()} function in Bacula code
1049 that can use Accurate code to compare the file information in argument with
1050 the previous file information. The \texttt{delta\_seq} attribute of the
1051 \texttt{save\_pkt} will be updated, and the call will return
1052 \texttt{bRC\_Seen} if the core code wouldn't decide to backup it.
1057 \subsubsection{Bacula events}
1058 The list of events has been extended to include:
1064 bEventStartBackupJob = 3,
1065 bEventEndBackupJob = 4,
1066 bEventStartRestoreJob = 5,
1067 bEventEndRestoreJob = 6,
1068 bEventStartVerifyJob = 7,
1069 bEventEndVerifyJob = 8,
1070 bEventBackupCommand = 9,
1071 bEventRestoreCommand = 10,
1076 bEventCancelCommand = 13,
1077 bEventVssBackupAddComponents = 14,
1078 bEventVssRestoreLoadComponentMetadata = 15,
1079 bEventVssRestoreSetComponentsSelected = 16,
1080 bEventRestoreObject = 17,
1081 bEventEndFileSet = 18,
1082 bEventPluginCommand = 19,
1083 bEventVssBeforeCloseRestore = 20,
1084 bEventVssPrepareSnapshot = 21
1090 \item [bEventCancelCommand] is called whenever the currently
1091 running Job is canceled */
1093 \item [bEventVssBackupAddComponents]
1095 \item [bEventVssPrepareSnapshot] is called before creating VSS snapshots, it
1096 provides a char[27] table where the plugin can add Windows drives that will
1097 be used during the Job. You need to add them without duplicates, and you can
1098 use in \texttt{fd\_common.h} \texttt{add\_drive()} and \texttt{copy\_drives()}
1102 \subsection{ACL enhancements}
1104 The following enhancements are made to the Bacula Filed with regards to
1105 Access Control Lists (ACLs)
1108 \item Added support for AIX 5.3 and later new aclx\_get interface which supports
1109 POSIX and NFSv4 ACLs.
1110 \item Added support for new acl types on FreeBSD 8.1 and later which supports
1111 POSIX and NFSv4 ACLs.
1112 \item Some generic cleanups for internal ACL handling.
1113 \item Fix for acl storage on OSX
1114 \item Cleanup of configure checks for ACL detection, now configure only
1115 tests for a certain interface type based on the operating system
1116 this should give less false positives on detection. Also when ACLs
1117 are detected no other acl checks are performed anymore.
1121 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
1122 and is available with Bacula Enterprise Edition and Community Edition.
1124 \subsection{XATTR enhancements}
1126 The following enhancements are made to the Bacula Filed with regards to
1127 Extended Attributes (XATTRs)
1130 \item Added support for IRIX extended attributes using the attr\_get interface.
1131 \item Added support for Tru64 (OSF1) extended attributes using the
1132 getproplist interface.
1133 \item Added support for AIX extended attributes available in AIX 6.x
1134 and higher using the listea/getea/setea interface.
1135 \item Added some debugging to generic xattr code so it easier to
1137 \item Cleanup of configure checks for XATTR detection, now configure only
1138 tests for a certain interface type based on the operating system
1139 this should give less false positives on detection. Also when xattrs
1140 are detected no other xattr checks are performed anymore.
1144 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
1145 and is available with Bacula Enterprise Edition and Community Edition.
1147 \subsection{Class Based Database Backend Drivers}
1149 The main Bacula Director code is independent of the SQL backend
1150 in version 5.2.0 and greater. This means that the Bacula Director can be
1151 packaged by itself, then each of the different SQL backends supported can
1152 be packaged separately. It is possible to build all the DB backends at the
1153 same time by including multiple database options at the same time.
1155 ./configure can be run with multiple database configure options.
1162 Order of testing for databases is:
1169 Each configured backend generates a file named:
1170 \verb+libbaccats-<sql_backend_name>-<version>.so+
1171 A dummy catalog library is created named libbaccats-version.so
1173 At configure time the first detected backend is used as the so called
1174 default backend and at install time the dummy
1175 \verb+libbaccats-<version>.so+ is replaced with the default backend type.
1177 If you configure all three backends you get three backend libraries and the
1178 postgresql gets installed as the default.
1180 When you want to switch to another database, first save any old catalog you
1181 may have then you can copy one of the three backend libraries over the
1182 \verb+libbaccats-<version>.so+ e.g.
1184 An actual command, depending on your Bacula version might be:
1186 cp libbaccats-postgresql-5.2.2.so libbaccats-5.2.2.so
1189 where the \verb+5.2.2+ must be replaced by the Bacula release
1192 Then you must update the default backend in the following files:
1195 create_bacula_database
1196 drop_bacula_database
1198 grant_bacula_privileges
1201 update_bacula_tables
1204 And re-run all the above scripts. Please note, this means
1205 you will have a new empty database and if you had a previous
1206 one it will be lost.
1208 All current database backend drivers for catalog information are rewritten
1209 to use a set of multi inherited C++ classes which abstract the specific
1210 database specific internals and make sure we have a more stable generic
1211 interface with the rest of SQL code. From now on there is a strict
1212 boundary between the SQL code and the low-level database functions. This
1213 new interface should also make it easier to add a new backend for a
1214 currently unsupported database. As part of the rewrite the SQLite 2 code
1215 was removed (e.g. only SQLite 3 is now supported). An extra bonus of the
1216 new code is that you can configure multiple backends in the configure and
1217 build all backends in one compile session and select the correct database
1218 backend at install time. This should make it a lot easier for packages
1224 We also added cursor support for PostgreSQL backend, this improves memory
1225 usage for large installation.
1228 This project was implemented by Planets Communications B.V. and ELM
1229 Consultancy B.V. and Bacula Systems and is available with both the Bacula
1230 Enterprise Edition and the Community Edition.
1232 \subsection{Hash List Enhancements}
1234 The htable hash table class has been extended with extra hash functions for
1235 handling next to char pointer hashes also 32 bits and 64 bits hash keys.
1236 Also the hash table initialization routines have been enhanced with
1237 support for passing a hint as to the number of initial pages to use
1238 for the size of the hash table. Until now the hash table always used
1239 a fixed value of 10 Mb. The private hash functions of the mountpoint entry
1240 cache have been rewritten to use the new htable class with a small memory
1244 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
1245 and Bacula Systems and is available with Bacula Enterprise Edition and
1250 %%% =====================================================================
1255 \section{Release Version 5.0.3}
1257 There are no new features in version 5.0.2. This version simply fixes a
1258 number of bugs found in version 5.0.1 during the ongoing development
1261 \section{Release Version 5.0.2}
1263 There are no new features in version 5.0.2. This version simply fixes a
1264 number of bugs found in version 5.0.1 during the ongoing development
1270 \section{New Features in 5.0.1}
1272 This chapter presents the new features that are in the released Bacula version
1273 5.0.1. This version mainly fixes a number of bugs found in version 5.0.0 during
1274 the ongoing development process.
1276 \subsection{Truncate Volume after Purge}
1277 \label{sec:actiononpurge}
1279 The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate
1280 the volume when it is purged with the new command \texttt{purge volume
1281 action}. It is useful to prevent disk based volumes from consuming too much
1287 Action On Purge = Truncate
1292 As usual you can also set this property with the \texttt{update volume} command
1294 *update volume=xxx ActionOnPurge=Truncate
1295 *update volume=xxx actiononpurge=None
1298 To ask Bacula to truncate your \texttt{Purged} volumes, you need to use the
1299 following command in interactive mode or in a RunScript as shown after:
1301 *purge volume action=truncate storage=File allpools
1302 # or by default, action=all
1303 *purge volume action storage=File pool=Default
1306 This is possible to specify the volume name, the media type, the pool, the
1307 storage, etc\dots (see \texttt{help purge}) Be sure that your storage device is
1308 idle when you decide to run this command.
1312 Name = CatalogBackup
1317 Console = "purge volume action=all allpools storage=File"
1322 \textbf{Important note}: This feature doesn't work as
1323 expected in version 5.0.0. Please do not use it before version 5.0.1.
1325 \subsection{Allow Higher Duplicates}
1326 This directive did not work correctly and has been depreciated
1327 (disabled) in version 5.0.1. Please remove it from your bacula-dir.conf
1328 file as it will be removed in a future release.
1330 \subsection{Cancel Lower Level Duplicates}
1331 This directive was added in Bacula version 5.0.1. It compares the
1332 level of a new backup job to old jobs of the same name, if any,
1333 and will kill the job which has a lower level than the other one.
1334 If the levels are the same (i.e. both are Full backups), then
1335 nothing is done and the other Cancel XXX Duplicate directives
1338 \section{New Features in 5.0.0}
1340 \subsection{Maximum Concurrent Jobs for Devices}
1341 \label{sec:maximumconcurrentjobdevice}
1343 {\bf Maximum Concurrent Jobs} is a new Device directive in the Storage
1344 Daemon configuration permits setting the maximum number of Jobs that can
1345 run concurrently on a specified Device. Using this directive, it is
1346 possible to have different Jobs using multiple drives, because when the
1347 Maximum Concurrent Jobs limit is reached, the Storage Daemon will start new
1348 Jobs on any other available compatible drive. This facilitates writing to
1349 multiple drives with multiple Jobs that all use the same Pool.
1351 This project was funded by Bacula Systems.
1353 \subsection{Restore from Multiple Storage Daemons}
1354 \index[general]{Restore}
1356 Previously, you were able to restore from multiple devices in a single Storage
1357 Daemon. Now, Bacula is able to restore from multiple Storage Daemons. For
1358 example, if your full backup runs on a Storage Daemon with an autochanger, and
1359 your incremental jobs use another Storage Daemon with lots of disks, Bacula
1360 will switch automatically from one Storage Daemon to an other within the same
1363 You must upgrade your File Daemon to version 3.1.3 or greater to use this
1366 This project was funded by Bacula Systems with the help of Equiinet.
1368 \subsection{File Deduplication using Base Jobs}
1369 A base job is sort of like a Full save except that you will want the FileSet to
1370 contain only files that are unlikely to change in the future (i.e. a snapshot
1371 of most of your system after installing it). After the base job has been run,
1372 when you are doing a Full save, you specify one or more Base jobs to be used.
1373 All files that have been backed up in the Base job/jobs but not modified will
1374 then be excluded from the backup. During a restore, the Base jobs will be
1375 automatically pulled in where necessary.
1377 This is something none of the competition does, as far as we know (except
1378 perhaps BackupPC, which is a Perl program that saves to disk only). It is big
1379 win for the user, it makes Bacula stand out as offering a unique optimization
1380 that immediately saves time and money. Basically, imagine that you have 100
1381 nearly identical Windows or Linux machine containing the OS and user files.
1382 Now for the OS part, a Base job will be backed up once, and rather than making
1383 100 copies of the OS, there will be only one. If one or more of the systems
1384 have some files updated, no problem, they will be automatically restored.
1386 See the \ilink{Base Job Chapter}{basejobs} for more information.
1388 This project was funded by Bacula Systems.
1390 \subsection{AllowCompression = \lt{}yes\vb{}no\gt{}}
1391 \index[dir]{AllowCompression}
1393 This new directive may be added to Storage resource within the Director's
1394 configuration to allow users to selectively disable the client compression for
1395 any job which writes to this storage resource.
1401 Address = ultrium-tape
1402 Password = storage_password # Password for Storage Daemon
1405 AllowCompression = No # Tape drive has hardware compression
1408 The above example would cause any jobs running with the UltriumTape storage
1409 resource to run without compression from the client file daemons. This
1410 effectively overrides any compression settings defined at the FileSet level.
1412 This feature is probably most useful if you have a tape drive which supports
1413 hardware compression. By setting the \texttt{AllowCompression = No} directive
1414 for your tape drive storage resource, you can avoid additional load on the file
1415 daemon and possibly speed up tape backups.
1417 This project was funded by Collaborative Fusion, Inc.
1419 \subsection{Accurate Fileset Options}
1420 \label{sec:accuratefileset}
1422 In previous versions, the accurate code used the file creation and modification
1423 times to determine if a file was modified or not. Now you can specify which
1424 attributes to use (time, size, checksum, permission, owner, group, \dots),
1425 similar to the Verify options.
1441 \item {\bf i} compare the inodes
1442 \item {\bf p} compare the permission bits
1443 \item {\bf n} compare the number of links
1444 \item {\bf u} compare the user id
1445 \item {\bf g} compare the group id
1446 \item {\bf s} compare the size
1447 \item {\bf a} compare the access time
1448 \item {\bf m} compare the modification time (st\_mtime)
1449 \item {\bf c} compare the change time (st\_ctime)
1450 \item {\bf d} report file size decreases
1451 \item {\bf 5} compare the MD5 signature
1452 \item {\bf 1} compare the SHA1 signature
1455 \textbf{Important note:} If you decide to use checksum in Accurate jobs,
1456 the File Daemon will have to read all files even if they normally would not
1457 be saved. This increases the I/O load, but also the accuracy of the
1458 deduplication. By default, Bacula will check modification/creation time
1461 This project was funded by Bacula Systems.
1463 \subsection{Tab-completion for Bconsole}
1464 \label{sec:tabcompletion}
1466 If you build \texttt{bconsole} with readline support, you will be able to use
1467 the new auto-completion mode. This mode supports all commands, gives help
1468 inside command, and lists resources when required. It works also in the restore
1471 To use this feature, you should have readline development package loaded on
1472 your system, and use the following option in configure.
1474 ./configure --with-readline=/usr/include/readline --disable-conio ...
1477 The new bconsole won't be able to tab-complete with older directors.
1479 This project was funded by Bacula Systems.
1481 \subsection{Pool File and Job Retention}
1482 \label{sec:poolfilejobretention}
1484 We added two new Pool directives, \texttt{FileRetention} and
1485 \texttt{JobRetention}, that take precedence over Client directives of the same
1486 name. It allows you to control the Catalog pruning algorithm Pool by Pool. For
1487 example, you can decide to increase Retention times for Archive or OffSite Pool.
1489 It seems obvious to us, but apparently not to some users, that given the
1490 definition above that the Pool File and Job Retention periods is a global
1491 override for the normal Client based pruning, which means that when the
1492 Job is pruned, the pruning will apply globally to that particular Job.
1494 Currently, there is a bug in the implementation that causes any Pool
1495 retention periods specified to apply to {\bf all} Pools for that
1496 particular Client. Thus we suggest that you avoid using these two
1497 directives until this implementation problem is corrected.
1499 \subsection{Read-only File Daemon using capabilities}
1500 \label{sec:fdreadonly}
1501 This feature implements support of keeping \textbf{ReadAll} capabilities after
1502 UID/GID switch, this allows FD to keep root read but drop write permission.
1504 It introduces new \texttt{bacula-fd} option (\texttt{-k}) specifying that
1505 \textbf{ReadAll} capabilities should be kept after UID/GID switch.
1508 root@localhost:~# bacula-fd -k -u nobody -g nobody
1511 The code for this feature was contributed by our friends at AltLinux.
1513 \subsection{Bvfs API}
1516 To help developers of restore GUI interfaces, we have added new \textsl{dot
1517 commands} that permit browsing the catalog in a very simple way.
1520 \item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update
1521 the Bvfs cache in the catalog. You need to run it before any access to the
1524 \item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command
1525 will list all directories in the specified \texttt{path} or
1526 \texttt{pathid}. Using \texttt{pathid} avoids problems with character
1527 encoding of path/filenames.
1529 \item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command
1530 will list all files in the specified \texttt{path} or \texttt{pathid}. Using
1531 \texttt{pathid} avoids problems with character encoding.
1534 You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of
1535 data that will be displayed.
1538 * .bvfs_update jobid=1,2
1540 * .bvfs_lsdir path=/ jobid=1,2
1543 This project was funded by Bacula Systems.
1545 \subsection{Testing your Tape Drive}
1546 \label{sec:btapespeed}
1548 To determine the best configuration of your tape drive, you can run the new
1549 \texttt{speed} command available in the \texttt{btape} program.
1551 This command can have the following arguments:
1553 \item[\texttt{file\_size=n}] Specify the Maximum File Size for this test
1554 (between 1 and 5GB). This counter is in GB.
1555 \item[\texttt{nb\_file=n}] Specify the number of file to be written. The amount
1556 of data should be greater than your memory ($file\_size*nb\_file$).
1557 \item[\texttt{skip\_zero}] This flag permits to skip tests with constant
1559 \item[\texttt{skip\_random}] This flag permits to skip tests with random
1561 \item[\texttt{skip\_raw}] This flag permits to skip tests with raw access.
1562 \item[\texttt{skip\_block}] This flag permits to skip tests with Bacula block
1567 *speed file_size=3 skip_raw
1568 btape.c:1078 Test with zero data and bacula block structure.
1569 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
1570 ++++++++++++++++++++++++++++++++++++++++++
1571 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
1572 btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 MB/s
1574 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 MB/s
1576 btape.c:1090 Test with random data, should give the minimum throughput.
1577 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
1578 +++++++++++++++++++++++++++++++++++++++++++
1579 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
1580 btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 MB/s
1581 +++++++++++++++++++++++++++++++++++++++++++
1583 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s
1587 When using compression, the random test will give your the minimum throughput
1588 of your drive . The test using constant string will give you the maximum speed
1589 of your hardware chain. (CPU, memory, SCSI card, cable, drive, tape).
1591 You can change the block size in the Storage Daemon configuration file.
1593 \subsection{New {\bf Block Checksum} Device Directive}
1594 You may now turn off the Block Checksum (CRC32) code
1595 that Bacula uses when writing blocks to a Volume. This is
1602 doing so can reduce the Storage daemon CPU usage slightly. It
1603 will also permit Bacula to read a Volume that has corrupted data.
1605 The default is {\bf yes} -- i.e. the checksum is computed on write
1606 and checked on read.
1608 We do not recommend to turn this off particularly on older tape
1609 drives or for disk Volumes where doing so may allow corrupted data
1612 \subsection{New Bat Features}
1614 Those new features were funded by Bacula Systems.
1616 \subsubsection{Media List View}
1618 By clicking on ``Media'', you can see the list of all your volumes. You will be
1619 able to filter by Pool, Media Type, Location,\dots And sort the result directly
1620 in the table. The old ``Media'' view is now known as ``Pool''.
1621 \begin{figure}[htbp]
1623 \includegraphics[width=0.8\linewidth]{bat-mediaview}
1624 \label{fig:mediaview}
1628 \subsubsection{Media Information View}
1630 By double-clicking on a volume (on the Media list, in the Autochanger content
1631 or in the Job information panel), you can access a detailed overview of your
1632 Volume. (cf figure \vref{fig:mediainfo}.)
1633 \begin{figure}[htbp]
1635 \includegraphics[width=0.8\linewidth]{bat11}
1636 \caption{Media information}
1637 \label{fig:mediainfo}
1640 \subsubsection{Job Information View}
1642 By double-clicking on a Job record (on the Job run list or in the Media
1643 information panel), you can access a detailed overview of your Job. (cf
1644 figure \vref{fig:jobinfo}.)
1645 \begin{figure}[htbp]
1647 \includegraphics[width=0.8\linewidth]{bat12}
1648 \caption{Job information}
1652 \subsubsection{Autochanger Content View}
1654 By double-clicking on a Storage record (on the Storage list panel), you can
1655 access a detailed overview of your Autochanger. (cf figure \vref{fig:jobinfo}.)
1656 \begin{figure}[htbp]
1658 \includegraphics[width=0.8\linewidth]{bat13}
1659 \caption{Autochanger content}
1660 \label{fig:achcontent}
1663 To use this feature, you need to use the latest mtx-changer script
1664 version. (With new \texttt{listall} and \texttt{transfer} commands)
1666 \subsection{Bat on Windows}
1667 We have ported {\bf bat} to Windows and it is now installed
1668 by default when the installer is run. It works quite well
1669 on Win32, but has not had a lot of testing there, so your
1670 feedback would be welcome. Unfortunately, even though it is
1671 installed by default, it does not yet work on 64 bit Windows
1674 \subsection{New Win32 Installer}
1675 The Win32 installer has been modified in several very important
1678 \item You must deinstall any current version of the
1679 Win32 File daemon before upgrading to the new one.
1680 If you forget to do so, the new installation will fail.
1681 To correct this failure, you must manually shutdown
1682 and deinstall the old File daemon.
1683 \item All files (other than menu links) are installed
1684 in {\bf c:/Program Files/Bacula}.
1685 \item The installer no longer sets this
1686 file to require administrator privileges by default. If you want
1687 to do so, please do it manually using the {\bf cacls} program.
1690 cacls "C:\Program Files\Bacula" /T /G SYSTEM:F Administrators:F
1692 \item The server daemons (Director and Storage daemon) are
1693 no longer included in the Windows installer. If you want the
1694 Windows servers, you will either need to build them yourself (note
1695 they have not been ported to 64 bits), or you can contact
1696 Bacula Systems about this.
1699 \subsection{Win64 Installer}
1700 We have corrected a number of problems that required manual
1701 editing of the conf files. In most cases, it should now
1702 install and work. {\bf bat} is by default installed in
1703 {\bf c:/Program Files/Bacula/bin32} rather than
1704 {\bf c:/Program Files/Bacula} as is the case with the 32
1705 bit Windows installer.
1707 \subsection{Linux Bare Metal Recovery USB Key}
1708 We have made a number of significant improvements in the
1709 Bare Metal Recovery USB key. Please see the README files
1710 it the {\bf rescue} release for more details.
1712 We are working on an equivalent USB key for Windows bare
1713 metal recovery, but it will take some time to develop it (best
1714 estimate 3Q2010 or 4Q2010)
1717 \subsection{bconsole Timeout Option}
1718 You can now use the -u option of {\bf bconsole} to set a timeout in seconds
1719 for commands. This is useful with GUI programs that use {\bf bconsole}
1720 to interface to the Director.
1722 \subsection{Important Changes}
1723 \label{sec:importantchanges}
1726 \item You are now allowed to Migrate, Copy, and Virtual Full to read and write
1727 to the same Pool. The Storage daemon ensures that you do not read and
1728 write to the same Volume.
1729 \item The \texttt{Device Poll Interval} is now 5 minutes. (previously did not
1731 \item Virtually all the features of {\bf mtx-changer} have
1732 now been parametrized, which allows you to configure
1733 mtx-changer without changing it. There is a new configuration file {\bf mtx-changer.conf}
1734 that contains variables that you can set to configure mtx-changer.
1735 This configuration file will not be overwritten during upgrades.
1736 We encourage you to submit any changes
1737 that are made to mtx-changer and to parametrize it all in
1738 mtx-changer.conf so that all configuration will be done by
1739 changing only mtx-changer.conf.
1740 \item The new \texttt{mtx-changer} script has two new options, \texttt{listall}
1741 and \texttt{transfer}. Please configure them as appropriate
1742 in mtx-changer.conf.
1743 \item To enhance security of the \texttt{BackupCatalog} job, we provide a new
1744 script (\texttt{make\_catalog\_backup.pl}) that does not expose your catalog
1745 password. If you want to use the new script, you will need to
1746 manually change the \texttt{BackupCatalog} Job definition.
1747 \item The \texttt{bconsole} \texttt{help} command now accepts
1748 an argument, which if provided produces information on that
1749 command (ex: \texttt{help run}).
1753 \subsubsection*{Truncate volume after purge}
1755 Note that the Truncate Volume after purge feature doesn't work as expected
1756 in 5.0.0 version. Please, don't use it before version 5.0.1.
1758 \subsubsection{Custom Catalog queries}
1760 If you wish to add specialized commands that list the contents of the catalog,
1761 you can do so by adding them to the \texttt{query.sql} file. This
1762 \texttt{query.sql} file is now empty by default. The file
1763 \texttt{examples/sample-query.sql} has an a number of sample commands
1764 you might find useful.
1766 \subsubsection{Deprecated parts}
1768 The following items have been \textbf{deprecated} for a long time, and are now
1769 removed from the code.
1772 \item Support for SQLite 2
1775 \subsection{Misc Changes}
1776 \label{sec:miscchanges}
1779 \item Updated Nagios check\_bacula
1780 \item Updated man files
1781 \item Added OSX package generation script in platforms/darwin
1782 \item Added Spanish and Ukrainian Bacula translations
1783 \item Enable/disable command shows only Jobs that can change
1784 \item Added \texttt{show disabled} command to show disabled Jobs
1785 \item Many ACL improvements
1786 \item Added Level to FD status Job output
1787 \item Begin Ingres DB driver (not yet working)
1788 \item Split RedHat spec files into bacula, bat, mtx, and docs
1789 \item Reorganized the manuals (fewer separate manuals)
1790 \item Added lock/unlock order protection in lock manager
1791 \item Allow 64 bit sizes for a number of variables
1792 \item Fixed several deadlocks or potential race conditions in the SD
1795 \chapter{Released Version 3.0.3 and 3.0.3a}
1797 There are no new features in version 3.0.3. This version simply fixes a
1798 number of bugs found in version 3.0.2 during the ongoing development
1801 \section{New Features in Released Version 3.0.2}
1803 This chapter presents the new features added to the
1804 Released Bacula Version 3.0.2.
1806 \subsection{Full Restore from a Given JobId}
1807 \index[general]{Restore menu}
1809 This feature allows selecting a single JobId and having Bacula
1810 automatically select all the other jobs that comprise a full backup up to
1811 and including the selected date (through JobId).
1813 Assume we start with the following jobs:
1815 +-------+--------------+---------------------+-------+----------+------------+
1816 | jobid | client | starttime | level | jobfiles | jobbytes |
1817 +-------+--------------+---------------------+-------+----------+------------
1818 | 6 | localhost-fd | 2009-07-15 11:45:49 | I | 2 | 0 |
1819 | 5 | localhost-fd | 2009-07-15 11:45:45 | I | 15 | 44143 |
1820 | 3 | localhost-fd | 2009-07-15 11:45:38 | I | 1 | 10 |
1821 | 1 | localhost-fd | 2009-07-15 11:45:30 | F | 1527 | 44143073 |
1822 +-------+--------------+---------------------+-------+----------+------------+
1825 Below is an example of this new feature (which is number 12 in the
1830 To select the JobIds, you have the following choices:
1831 1: List last 20 Jobs run
1832 2: List Jobs where a given File is saved
1834 12: Select full restore to a specified Job date
1837 Select item: (1-13): 12
1838 Enter JobId to get the state to restore: 5
1839 Selecting jobs to build the Full state at 2009-07-15 11:45:45
1840 You have selected the following JobIds: 1,3,5
1842 Building directory tree for JobId(s) 1,3,5 ... +++++++++++++++++++
1843 1,444 files inserted into the tree.
1846 This project was funded by Bacula Systems.
1848 \subsection{Source Address}
1849 \index[general]{Source Address}
1851 A feature has been added which allows the administrator to specify the address
1852 from which the Director and File daemons will establish connections. This
1853 may be used to simplify system configuration overhead when working in complex
1854 networks utilizing multi-homing and policy-routing.
1856 To accomplish this, two new configuration directives have been implemented:
1859 FDSourceAddress=10.0.1.20 # Always initiate connections from this address
1863 DirSourceAddress=10.0.1.10 # Always initiate connections from this address
1867 Simply adding specific host routes on the OS
1868 would have an undesirable side-effect: any
1869 application trying to contact the destination host would be forced to use the
1870 more specific route possibly diverting management traffic onto a backup VLAN.
1871 Instead of adding host routes for each client connected to a multi-homed backup
1872 server (for example where there are management and backup VLANs), one can
1873 use the new directives to specify a specific source address at the application
1876 Additionally, this allows the simplification and abstraction of firewall rules
1877 when dealing with a Hot-Standby director or storage daemon configuration. The
1878 Hot-standby pair may share a CARP address, which connections must be sourced
1879 from, while system services listen and act from the unique interface addresses.
1881 This project was funded by Collaborative Fusion, Inc.
1883 \subsection{Show volume availability when doing restore}
1885 When doing a restore the selection dialog ends by displaying this
1889 The job will require the following
1890 Volume(s) Storage(s) SD Device(s)
1891 ===========================================================================
1892 *000741L3 LTO-4 LTO3
1893 *000866L3 LTO-4 LTO3
1894 *000765L3 LTO-4 LTO3
1895 *000764L3 LTO-4 LTO3
1896 *000756L3 LTO-4 LTO3
1897 *001759L3 LTO-4 LTO3
1898 *001763L3 LTO-4 LTO3
1902 Volumes marked with ``*'' are online (in the autochanger).
1905 This should help speed up large restores by minimizing the time spent
1906 waiting for the operator to discover that he must change tapes in the library.
1908 This project was funded by Bacula Systems.
1910 \subsection{Accurate estimate command}
1912 The \texttt{estimate} command can now use the accurate code to detect changes
1913 and give a better estimation.
1915 You can set the accurate behavior on the command line by using
1916 \texttt{accurate=yes\vb{}no} or use the Job setting as default value.
1919 * estimate listing accurate=yes level=incremental job=BackupJob
1922 This project was funded by Bacula Systems.
1924 \section{New Features in 3.0.0}
1925 \label{NewFeaturesChapter}
1926 \index[general]{New Features}
1928 This chapter presents the new features added to the development 2.5.x
1929 versions to be released as Bacula version 3.0.0 sometime in April 2009.
1931 \subsection{Accurate Backup}
1932 \index[general]{Accurate Backup}
1934 As with most other backup programs, by default Bacula decides what files to
1935 backup for Incremental and Differential backup by comparing the change
1936 (st\_ctime) and modification (st\_mtime) times of the file to the time the last
1937 backup completed. If one of those two times is later than the last backup
1938 time, then the file will be backed up. This does not, however, permit tracking
1939 what files have been deleted and will miss any file with an old time that may
1940 have been restored to or moved onto the client filesystem.
1942 \subsubsection{Accurate = \lt{}yes\vb{}no\gt{}}
1943 If the {\bf Accurate = \lt{}yes\vb{}no\gt{}} directive is enabled (default no) in
1944 the Job resource, the job will be run as an Accurate Job. For a {\bf Full}
1945 backup, there is no difference, but for {\bf Differential} and {\bf
1946 Incremental} backups, the Director will send a list of all previous files
1947 backed up, and the File daemon will use that list to determine if any new files
1948 have been added or or moved and if any files have been deleted. This allows
1949 Bacula to make an accurate backup of your system to that point in time so that
1950 if you do a restore, it will restore your system exactly.
1953 about using Accurate backup is that it requires more resources (CPU and memory)
1954 on both the Director and the Client machines to create the list of previous
1955 files backed up, to send that list to the File daemon, for the File daemon to
1956 keep the list (possibly very big) in memory, and for the File daemon to do
1957 comparisons between every file in the FileSet and the list. In particular,
1958 if your client has lots of files (more than a few million), you will need
1959 lots of memory on the client machine.
1961 Accurate must not be enabled when backing up with a plugin that is not
1962 specially designed to work with Accurate. If you enable it, your restores
1963 will probably not work correctly.
1965 This project was funded by Bacula Systems.
1969 \subsection{Copy Jobs}
1970 \index[general]{Copy Jobs}
1972 A new {\bf Copy} job type 'C' has been implemented. It is similar to the
1973 existing Migration feature with the exception that the Job that is copied is
1974 left unchanged. This essentially creates two identical copies of the same
1975 backup. However, the copy is treated as a copy rather than a backup job, and
1976 hence is not directly available for restore. The {\bf restore} command lists
1977 copy jobs and allows selection of copies by using \texttt{jobid=}
1978 option. If the keyword {\bf copies} is present on the command line, Bacula will
1979 display the list of all copies for selected jobs.
1984 These JobIds have copies as follows:
1985 +-------+------------------------------------+-----------+------------------+
1986 | JobId | Job | CopyJobId | MediaType |
1987 +-------+------------------------------------+-----------+------------------+
1988 | 2 | CopyJobSave.2009-02-17_16.31.00.11 | 7 | DiskChangerMedia |
1989 +-------+------------------------------------+-----------+------------------+
1990 +-------+-------+----------+----------+---------------------+------------------+
1991 | JobId | Level | JobFiles | JobBytes | StartTime | VolumeName |
1992 +-------+-------+----------+----------+---------------------+------------------+
1993 | 19 | F | 6274 | 76565018 | 2009-02-17 16:30:45 | ChangerVolume002 |
1994 | 2 | I | 1 | 5 | 2009-02-17 16:30:51 | FileVolume001 |
1995 +-------+-------+----------+----------+---------------------+------------------+
1996 You have selected the following JobIds: 19,2
1998 Building directory tree for JobId(s) 19,2 ... ++++++++++++++++++++++++++++++++++++++++++++
1999 5,611 files inserted into the tree.
2004 The Copy Job runs without using the File daemon by copying the data from the
2005 old backup Volume to a different Volume in a different Pool. See the Migration
2006 documentation for additional details. For copy Jobs there is a new selection
2007 directive named {\bf PoolUncopiedJobs} which selects all Jobs that were
2008 not already copied to another Pool.
2010 As with Migration, the Client, Volume, Job, or SQL query, are
2011 other possible ways of selecting the Jobs to be copied. Selection
2012 types like SmallestVolume, OldestVolume, PoolOccupancy and PoolTime also
2013 work, but are probably more suited for Migration Jobs.
2015 If Bacula finds a Copy of a job record that is purged (deleted) from the catalog,
2016 it will promote the Copy to a \textsl{real} backup job and will make it available for
2017 automatic restore. If more than one Copy is available, it will promote the copy
2018 with the smallest JobId.
2020 A nice solution which can be built with the new Copy feature is often
2021 called disk-to-disk-to-tape backup (DTDTT). A sample config could
2022 look something like the one below:
2026 Name = FullBackupsVirtualPool
2028 Purge Oldest Volume = Yes
2030 NextPool = FullBackupsTapePool
2034 Name = FullBackupsTapePool
2038 Volume Retention = 365 days
2039 Storage = superloader
2043 # Fake fileset for copy jobs
2055 # Fake client for copy jobs
2065 # Default template for a CopyDiskToTape Job
2068 Name = CopyDiskToTape
2070 Messages = StandardCopy
2073 Selection Type = PoolUncopiedJobs
2074 Maximum Concurrent Jobs = 10
2076 Allow Duplicate Jobs = Yes
2077 Cancel Queued Duplicates = No
2078 Cancel Running Duplicates = No
2083 Name = DaySchedule7:00
2084 Run = Level=Full daily at 7:00
2088 Name = CopyDiskToTapeFullBackups
2090 Schedule = DaySchedule7:00
2091 Pool = FullBackupsVirtualPool
2092 JobDefs = CopyDiskToTape
2096 The example above had 2 pool which are copied using the PoolUncopiedJobs
2097 selection criteria. Normal Full backups go to the Virtual pool and are copied
2098 to the Tape pool the next morning.
2100 The command \texttt{list copies [jobid=x,y,z]} lists copies for a given
2105 +-------+------------------------------------+-----------+------------------+
2106 | JobId | Job | CopyJobId | MediaType |
2107 +-------+------------------------------------+-----------+------------------+
2108 | 9 | CopyJobSave.2008-12-20_22.26.49.05 | 11 | DiskChangerMedia |
2109 +-------+------------------------------------+-----------+------------------+
2112 \subsection{ACL Updates}
2113 \index[general]{ACL Updates}
2114 The whole ACL code had been overhauled and in this version each platforms has
2115 different streams for each type of acl available on such an platform. As ACLs
2116 between platforms tend to be not that portable (most implement POSIX acls but
2117 some use an other draft or a completely different format) we currently only
2118 allow certain platform specific ACL streams to be decoded and restored on the
2119 same platform that they were created on. The old code allowed to restore ACL
2120 cross platform but the comments already mention that not being to wise. For
2121 backward compatibility the new code will accept the two old ACL streams and
2122 handle those with the platform specific handler. But for all new backups it
2123 will save the ACLs using the new streams.
2125 Currently the following platforms support ACLs:
2129 \item {\bf Darwin/OSX}
2138 Currently we support the following ACL types (these ACL streams use a reserved
2139 part of the stream numbers):
2142 \item {\bf STREAM\_ACL\_AIX\_TEXT} 1000 AIX specific string representation from
2144 \item {\bf STREAM\_ACL\_DARWIN\_ACCESS\_ACL} 1001 Darwin (OSX) specific acl\_t
2145 string representation from acl\_to\_text (POSIX acl)
2146 \item {\bf STREAM\_ACL\_FREEBSD\_DEFAULT\_ACL} 1002 FreeBSD specific acl\_t
2147 string representation from acl\_to\_text (POSIX acl) for default acls.
2148 \item {\bf STREAM\_ACL\_FREEBSD\_ACCESS\_ACL} 1003 FreeBSD specific acl\_t
2149 string representation from acl\_to\_text (POSIX acl) for access acls.
2150 \item {\bf STREAM\_ACL\_HPUX\_ACL\_ENTRY} 1004 HPUX specific acl\_entry
2151 string representation from acltostr (POSIX acl)
2152 \item {\bf STREAM\_ACL\_IRIX\_DEFAULT\_ACL} 1005 IRIX specific acl\_t string
2153 representation from acl\_to\_text (POSIX acl) for default acls.
2154 \item {\bf STREAM\_ACL\_IRIX\_ACCESS\_ACL} 1006 IRIX specific acl\_t string
2155 representation from acl\_to\_text (POSIX acl) for access acls.
2156 \item {\bf STREAM\_ACL\_LINUX\_DEFAULT\_ACL} 1007 Linux specific acl\_t
2157 string representation from acl\_to\_text (POSIX acl) for default acls.
2158 \item {\bf STREAM\_ACL\_LINUX\_ACCESS\_ACL} 1008 Linux specific acl\_t string
2159 representation from acl\_to\_text (POSIX acl) for access acls.
2160 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_ACL} 1009 Tru64 specific acl\_t
2161 string representation from acl\_to\_text (POSIX acl) for default acls.
2162 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_DIR\_ACL} 1010 Tru64 specific acl\_t
2163 string representation from acl\_to\_text (POSIX acl) for default acls.
2164 \item {\bf STREAM\_ACL\_TRU64\_ACCESS\_ACL} 1011 Tru64 specific acl\_t string
2165 representation from acl\_to\_text (POSIX acl) for access acls.
2166 \item {\bf STREAM\_ACL\_SOLARIS\_ACLENT} 1012 Solaris specific aclent\_t
2167 string representation from acltotext or acl\_totext (POSIX acl)
2168 \item {\bf STREAM\_ACL\_SOLARIS\_ACE} 1013 Solaris specific ace\_t string
2169 representation from from acl\_totext (NFSv4 or ZFS acl)
2172 In future versions we might support conversion functions from one type of acl
2173 into an other for types that are either the same or easily convertible. For now
2174 the streams are separate and restoring them on a platform that doesn't
2175 recognize them will give you a warning.
2177 \subsection{Extended Attributes}
2178 \index[general]{Extended Attributes}
2179 Something that was on the project list for some time is now implemented for
2180 platforms that support a similar kind of interface. Its the support for backup
2181 and restore of so called extended attributes. As extended attributes are so
2182 platform specific these attributes are saved in separate streams for each
2183 platform. Restores of the extended attributes can only be performed on the
2184 same platform the backup was done. There is support for all types of extended
2185 attributes, but restoring from one type of filesystem onto an other type of
2186 filesystem on the same platform may lead to surprises. As extended attributes
2187 can contain any type of data they are stored as a series of so called
2188 value-pairs. This data must be seen as mostly binary and is stored as such.
2189 As security labels from selinux are also extended attributes this option also
2190 stores those labels and no specific code is enabled for handling selinux
2193 Currently the following platforms support extended attributes:
2195 \item {\bf Darwin/OSX}
2201 On Linux acls are also extended attributes, as such when you enable ACLs on a
2202 Linux platform it will NOT save the same data twice e.g. it will save the ACLs
2203 and not the same extended attribute.
2205 To enable the backup of extended attributes please add the following to your
2220 \subsection{Shared objects}
2221 \index[general]{Shared objects}
2222 A default build of Bacula will now create the libraries as shared objects
2223 (.so) rather than static libraries as was previously the case.
2224 The shared libraries are built using {\bf libtool} so it should be quite
2227 An important advantage of using shared objects is that on a machine with the
2228 Directory, File daemon, the Storage daemon, and a console, you will have only
2229 one copy of the code in memory rather than four copies. Also the total size of
2230 the binary release is smaller since the library code appears only once rather
2231 than once for every program that uses it; this results in significant reduction
2232 in the size of the binaries particularly for the utility tools.
2234 In order for the system loader to find the shared objects when loading the
2235 Bacula binaries, the Bacula shared objects must either be in a shared object
2236 directory known to the loader (typically /usr/lib) or they must be in the
2237 directory that may be specified on the {\bf ./configure} line using the {\bf
2238 {-}{-}libdir} option as:
2241 ./configure --libdir=/full-path/dir
2244 the default is /usr/lib. If {-}{-}libdir is specified, there should be
2245 no need to modify your loader configuration provided that
2246 the shared objects are installed in that directory (Bacula
2247 does this with the make install command). The shared objects
2248 that Bacula references are:
2257 These files are symbolically linked to the real shared object file,
2258 which has a version number to permit running multiple versions of
2259 the libraries if desired (not normally the case).
2261 If you have problems with libtool or you wish to use the old
2262 way of building static libraries, or you want to build a static
2263 version of Bacula you may disable
2264 libtool on the configure command line with:
2267 ./configure --disable-libtool
2271 \subsection{Building Static versions of Bacula}
2272 \index[general]{Static linking}
2273 In order to build static versions of Bacula, in addition
2274 to configuration options that were needed you now must
2275 also add --disable-libtool. Example
2278 ./configure --enable-static-client-only --disable-libtool
2282 \subsection{Virtual Backup (Vbackup)}
2283 \index[general]{Virtual Backup}
2284 \index[general]{Vbackup}
2286 Bacula's virtual backup feature is often called Synthetic Backup or
2287 Consolidation in other backup products. It permits you to consolidate the
2288 previous Full backup plus the most recent Differential backup and any
2289 subsequent Incremental backups into a new Full backup. This new Full
2290 backup will then be considered as the most recent Full for any future
2291 Incremental or Differential backups. The VirtualFull backup is
2292 accomplished without contacting the client by reading the previous backup
2293 data and writing it to a volume in a different pool.
2295 In some respects the Vbackup feature works similar to a Migration job, in
2296 that Bacula normally reads the data from the pool specified in the
2297 Job resource, and writes it to the {\bf Next Pool} specified in the
2298 Job resource. Note, this means that usually the output from the Virtual
2299 Backup is written into a different pool from where your prior backups
2300 are saved. Doing it this way guarantees that you will not get a deadlock
2301 situation attempting to read and write to the same volume in the Storage
2302 daemon. If you then want to do subsequent backups, you may need to
2303 move the Virtual Full Volume back to your normal backup pool.
2304 Alternatively, you can set your {\bf Next Pool} to point to the current
2305 pool. This will cause Bacula to read and write to Volumes in the
2306 current pool. In general, this will work, because Bacula will
2307 not allow reading and writing on the same Volume. In any case, once
2308 a VirtualFull has been created, and a restore is done involving the
2309 most current Full, it will read the Volume or Volumes by the VirtualFull
2310 regardless of in which Pool the Volume is found.
2312 The Vbackup is enabled on a Job by Job in the Job resource by specifying
2313 a level of {\bf VirtualFull}.
2315 A typical Job resource definition might look like the following:
2322 FileSet = "Full Set"
2329 # Default pool definition
2333 Recycle = yes # Automatically recycle Volumes
2334 AutoPrune = yes # Prune expired volumes
2335 Volume Retention = 365d # one year
2343 Recycle = yes # Automatically recycle Volumes
2344 AutoPrune = yes # Prune expired volumes
2345 Volume Retention = 365d # one year
2346 Storage = DiskChanger
2349 # Definition of file storage device
2354 Device = FileStorage
2356 Maximum Concurrent Jobs = 5
2359 # Definition of DDS Virtual tape disk storage device
2362 Address = localhost # N.B. Use a fully qualified name here
2364 Device = DiskChanger
2365 Media Type = DiskChangerMedia
2366 Maximum Concurrent Jobs = 4
2371 Then in bconsole or via a Run schedule, you would run the job as:
2374 run job=MyBackup level=Full
2375 run job=MyBackup level=Incremental
2376 run job=MyBackup level=Differential
2377 run job=MyBackup level=Incremental
2378 run job=MyBackup level=Incremental
2381 So providing there were changes between each of those jobs, you would end up
2382 with a Full backup, a Differential, which includes the first Incremental
2383 backup, then two Incremental backups. All the above jobs would be written to
2384 the {\bf Default} pool.
2386 To consolidate those backups into a new Full backup, you would run the
2390 run job=MyBackup level=VirtualFull
2393 And it would produce a new Full backup without using the client, and the output
2394 would be written to the {\bf Full} Pool which uses the Diskchanger Storage.
2396 If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
2399 Note, the Start and End time of the Virtual Full backup is set to the
2400 values for the last job included in the Virtual Full (in the above example,
2401 it is an Increment). This is so that if another incremental is done, which
2402 will be based on the Virtual Full, it will backup all files from the
2403 last Job included in the Virtual Full rather than from the time the Virtual
2404 Full was actually run.
2408 \subsection{Catalog Format}
2409 \index[general]{Catalog Format}
2410 Bacula 3.0 comes with some changes to the catalog format. The upgrade
2411 operation will convert the FileId field of the File table from 32 bits (max 4
2412 billion table entries) to 64 bits (very large number of items). The
2413 conversion process can take a bit of time and will likely DOUBLE THE SIZE of
2414 your catalog during the conversion. Also you won't be able to run jobs during
2415 this conversion period. For example, a 3 million file catalog will take 2
2416 minutes to upgrade on a normal machine. Please don't forget to make a valid
2417 backup of your database before executing the upgrade script. See the
2418 ReleaseNotes for additional details.
2420 \subsection{64 bit Windows Client}
2421 \index[general]{Win64 Client}
2422 Unfortunately, Microsoft's implementation of Volume Shadown Copy (VSS) on
2423 their 64 bit OS versions is not compatible with a 32 bit Bacula Client.
2424 As a consequence, we are also releasing a 64 bit version of the Bacula
2425 Windows Client (win64bacula-3.0.0.exe) that does work with VSS.
2426 These binaries should only be installed on 64 bit Windows operating systems.
2427 What is important is not your hardware but whether or not you have
2428 a 64 bit version of the Windows OS.
2430 Compared to the Win32 Bacula Client, the 64 bit release contains a few differences:
2432 \item Before installing the Win64 Bacula Client, you must totally
2433 deinstall any prior 2.4.x Client installation using the
2434 Bacula deinstallation (see the menu item). You may want
2435 to save your .conf files first.
2436 \item Only the Client (File daemon) is ported to Win64, the Director
2437 and the Storage daemon are not in the 64 bit Windows installer.
2438 \item bwx-console is not yet ported.
2439 \item bconsole is ported but it has not been tested.
2440 \item The documentation is not included in the installer.
2441 \item Due to Vista security restrictions imposed on a default installation
2442 of Vista, before upgrading the Client, you must manually stop
2443 any prior version of Bacula from running, otherwise the install
2445 \item Due to Vista security restrictions imposed on a default installation
2446 of Vista, attempting to edit the conf files via the menu items
2447 will fail. You must directly edit the files with appropriate
2448 permissions. Generally double clicking on the appropriate .conf
2449 file will work providing you have sufficient permissions.
2450 \item All Bacula files are now installed in
2451 {\bf C:/Program Files/Bacula} except the main menu items,
2452 which are installed as before. This vastly simplifies the installation.
2453 \item If you are running on a foreign language version of Windows, most
2454 likely {\bf C:/Program Files} does not exist, so you should use the
2455 Custom installation and enter an appropriate location to install
2457 \item The 3.0.0 Win32 Client continues to install files in the locations used
2458 by prior versions. For the next version we will convert it to use
2459 the same installation conventions as the Win64 version.
2462 This project was funded by Bacula Systems.
2465 \subsection{Duplicate Job Control}
2466 \index[general]{Duplicate Jobs}
2467 The new version of Bacula provides four new directives that
2468 give additional control over what Bacula does if duplicate jobs
2469 are started. A duplicate job in the sense we use it here means
2470 a second or subsequent job with the same name starts. This
2471 happens most frequently when the first job runs longer than expected because no
2472 tapes are available.
2474 The four directives each take as an argument a {\bf yes} or {\bf no} value and
2475 are specified in the Job resource.
2479 \subsubsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}}
2480 \index[general]{Allow Duplicate Jobs}
2481 If this directive is set to {\bf yes}, duplicate jobs will be run. If
2482 the directive is set to {\bf no} (default) then only one job of a given name
2483 may run at one time, and the action that Bacula takes to ensure only
2484 one job runs is determined by the other directives (see below).
2486 If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs
2487 are present and none of the three directives given below permit
2488 Canceling a job, then the current job (the second one started)
2491 \subsubsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}}
2492 \index[general]{Allow Higher Duplicates}
2493 This directive was in version 5.0.0, but does not work as
2494 expected. If used, it should always be set to no. In later versions
2495 of Bacula the directive is disabled (disregarded).
2497 \subsubsection{Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}}
2498 \index[general]{Cancel Running Duplicates}
2499 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
2500 if this directive is set to {\bf yes} any job that is already running
2501 will be canceled. The default is {\bf no}.
2503 \subsubsection{Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}}
2504 \index[general]{Cancel Queued Duplicates}
2505 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
2506 if this directive is set to {\bf yes} any job that is
2507 already queued to run but not yet running will be canceled.
2508 The default is {\bf no}.
2511 \subsection{TLS Authentication}
2512 \index[general]{TLS Authentication}
2513 In Bacula version 2.5.x and later, in addition to the normal Bacula
2514 CRAM-MD5 authentication that is used to authenticate each Bacula
2515 connection, you can specify that you want TLS Authentication as well,
2516 which will provide more secure authentication.
2518 This new feature uses Bacula's existing TLS code (normally used for
2519 communications encryption) to do authentication. To use it, you must
2520 specify all the TLS directives normally used to enable communications
2521 encryption (TLS Enable, TLS Verify Peer, TLS Certificate, ...) and
2524 \subsubsection{TLS Authenticate = yes}
2526 TLS Authenticate = yes
2529 in the main daemon configuration resource (Director for the Director,
2530 Client for the File daemon, and Storage for the Storage daemon).
2532 When {\bf TLS Authenticate} is enabled, after doing the CRAM-MD5
2533 authentication, Bacula will also do TLS authentication, then TLS
2534 encryption will be turned off, and the rest of the communication between
2535 the two Bacula daemons will be done without encryption.
2537 If you want to encrypt communications data, use the normal TLS directives
2538 but do not turn on {\bf TLS Authenticate}.
2540 \subsection{bextract non-portable Win32 data}
2541 \index[general]{bextract handles Win32 non-portable data}
2542 {\bf bextract} has been enhanced to be able to restore
2543 non-portable Win32 data to any OS. Previous versions were
2544 unable to restore non-portable Win32 data to machines that
2545 did not have the Win32 BackupRead and BackupWrite API calls.
2547 \subsection{State File updated at Job Termination}
2548 \index[general]{State File}
2549 In previous versions of Bacula, the state file, which provides a
2550 summary of previous jobs run in the {\bf status} command output was
2551 updated only when Bacula terminated, thus if the daemon crashed, the
2552 state file might not contain all the run data. This version of
2553 the Bacula daemons updates the state file on each job termination.
2555 \subsection{MaxFullInterval = \lt{}time-interval\gt{}}
2556 \index[general]{MaxFullInterval}
2557 The new Job resource directive {\bf Max Full Interval = \lt{}time-interval\gt{}}
2558 can be used to specify the maximum time interval between {\bf Full} backup
2559 jobs. When a job starts, if the time since the last Full backup is
2560 greater than the specified interval, and the job would normally be an
2561 {\bf Incremental} or {\bf Differential}, it will be automatically
2562 upgraded to a {\bf Full} backup.
2564 \subsection{MaxDiffInterval = \lt{}time-interval\gt{}}
2565 \index[general]{MaxDiffInterval}
2566 The new Job resource directive {\bf Max Diff Interval = \lt{}time-interval\gt{}}
2567 can be used to specify the maximum time interval between {\bf Differential} backup
2568 jobs. When a job starts, if the time since the last Differential backup is
2569 greater than the specified interval, and the job would normally be an
2570 {\bf Incremental}, it will be automatically
2571 upgraded to a {\bf Differential} backup.
2573 \subsection{Honor No Dump Flag = \lt{}yes\vb{}no\gt{}}
2574 \index[general]{MaxDiffInterval}
2575 On FreeBSD systems, each file has a {\bf no dump flag} that can be set
2576 by the user, and when it is set it is an indication to backup programs
2577 to not backup that particular file. This version of Bacula contains a
2578 new Options directive within a FileSet resource, which instructs Bacula to
2579 obey this flag. The new directive is:
2582 Honor No Dump Flag = yes\vb{}no
2585 The default value is {\bf no}.
2588 \subsection{Exclude Dir Containing = \lt{}filename-string\gt{}}
2589 \index[general]{IgnoreDir}
2590 The {\bf ExcludeDirContaining = \lt{}filename\gt{}} is a new directive that
2591 can be added to the Include section of the FileSet resource. If the specified
2592 filename ({\bf filename-string}) is found on the Client in any directory to be
2593 backed up, the whole directory will be ignored (not backed up). For example:
2596 # List of files to be backed up
2604 Exclude Dir Containing = .excludeme
2609 But in /home, there may be hundreds of directories of users and some
2610 people want to indicate that they don't want to have certain
2611 directories backed up. For example, with the above FileSet, if
2612 the user or sysadmin creates a file named {\bf .excludeme} in
2613 specific directories, such as
2616 /home/user/www/cache/.excludeme
2617 /home/user/temp/.excludeme
2620 then Bacula will not backup the two directories named:
2623 /home/user/www/cache
2627 NOTE: subdirectories will not be backed up. That is, the directive
2628 applies to the two directories in question and any children (be they
2629 files, directories, etc).
2632 \subsection{Bacula Plugins}
2633 \index[general]{Plugin}
2634 Support for shared object plugins has been implemented in the Linux, Unix
2635 and Win32 File daemons. The API will be documented separately in
2636 the Developer's Guide or in a new document. For the moment, there is
2637 a single plugin named {\bf bpipe} that allows an external program to
2638 get control to backup and restore a file.
2640 Plugins are also planned (partially implemented) in the Director and the
2643 \subsubsection{Plugin Directory}
2644 \index[general]{Plugin Directory}
2645 Each daemon (DIR, FD, SD) has a new {\bf Plugin Directory} directive that may
2646 be added to the daemon definition resource. The directory takes a quoted
2647 string argument, which is the name of the directory in which the daemon can
2648 find the Bacula plugins. If this directive is not specified, Bacula will not
2649 load any plugins. Since each plugin has a distinctive name, all the daemons
2650 can share the same plugin directory.
2652 \subsubsection{Plugin Options}
2653 \index[general]{Plugin Options}
2654 The {\bf Plugin Options} directive takes a quoted string
2655 argument (after the equal sign) and may be specified in the
2656 Job resource. The options specified will be passed to all plugins
2657 when they are run. This each plugin must know what it is looking
2658 for. The value defined in the Job resource can be modified
2659 by the user when he runs a Job via the {\bf bconsole} command line
2662 Note: this directive may be specified, and there is code to modify
2663 the string in the run command, but the plugin options are not yet passed to
2664 the plugin (i.e. not fully implemented).
2666 \subsubsection{Plugin Options ACL}
2667 \index[general]{Plugin Options ACL}
2668 The {\bf Plugin Options ACL} directive may be specified in the
2669 Director's Console resource. It functions as all the other ACL commands
2670 do by permitting users running restricted consoles to specify a
2671 {\bf Plugin Options} that overrides the one specified in the Job
2672 definition. Without this directive restricted consoles may not modify
2675 \subsubsection{Plugin = \lt{}plugin-command-string\gt{}}
2676 \index[general]{Plugin}
2677 The {\bf Plugin} directive is specified in the Include section of
2678 a FileSet resource where you put your {\bf File = xxx} directives.
2689 Plugin = "bpipe:..."
2694 In the above example, when the File daemon is processing the directives
2695 in the Include section, it will first backup all the files in {\bf /home}
2696 then it will load the plugin named {\bf bpipe} (actually bpipe-dir.so) from
2697 the Plugin Directory. The syntax and semantics of the Plugin directive
2698 require the first part of the string up to the colon (:) to be the name
2699 of the plugin. Everything after the first colon is ignored by the File daemon but
2700 is passed to the plugin. Thus the plugin writer may define the meaning of the
2701 rest of the string as he wishes.
2703 Please see the next section for information about the {\bf bpipe} Bacula
2706 \subsection{The bpipe Plugin}
2707 \index[general]{The bpipe Plugin}
2708 The {\bf bpipe} plugin is provided in the directory src/plugins/fd/bpipe-fd.c of
2709 the Bacula source distribution. When the plugin is compiled and linking into
2710 the resulting dynamic shared object (DSO), it will have the name {\bf bpipe-fd.so}.
2711 Please note that this is a very simple plugin that was written for
2712 demonstration and test purposes. It is and can be used in production, but
2713 that was never really intended.
2715 The purpose of the plugin is to provide an interface to any system program for
2716 backup and restore. As specified above the {\bf bpipe} plugin is specified in
2717 the Include section of your Job's FileSet resource. The full syntax of the
2718 plugin directive as interpreted by the {\bf bpipe} plugin (each plugin is free
2719 to specify the sytax as it wishes) is:
2722 Plugin = "<field1>:<field2>:<field3>:<field4>"
2727 \item {\bf field1} is the name of the plugin with the trailing {\bf -fd.so}
2728 stripped off, so in this case, we would put {\bf bpipe} in this field.
2730 \item {\bf field2} specifies the namespace, which for {\bf bpipe} is the
2731 pseudo path and filename under which the backup will be saved. This pseudo
2732 path and filename will be seen by the user in the restore file tree.
2733 For example, if the value is {\bf /MYSQL/regress.sql}, the data
2734 backed up by the plugin will be put under that "pseudo" path and filename.
2735 You must be careful to choose a naming convention that is unique to avoid
2736 a conflict with a path and filename that actually exists on your system.
2738 \item {\bf field3} for the {\bf bpipe} plugin
2739 specifies the "reader" program that is called by the plugin during
2740 backup to read the data. {\bf bpipe} will call this program by doing a
2743 \item {\bf field4} for the {\bf bpipe} plugin
2744 specifies the "writer" program that is called by the plugin during
2745 restore to write the data back to the filesystem.
2748 Please note that for two items above describing the "reader" and "writer"
2749 fields, these programs are "executed" by Bacula, which
2750 means there is no shell interpretation of any command line arguments
2751 you might use. If you want to use shell characters (redirection of input
2752 or output, ...), then we recommend that you put your command or commands
2753 in a shell script and execute the script. In addition if you backup a
2754 file with the reader program, when running the writer program during
2755 the restore, Bacula will not automatically create the path to the file.
2756 Either the path must exist, or you must explicitly do so with your command
2757 or in a shell script.
2759 Putting it all together, the full plugin directive line might look
2763 Plugin = "bpipe:/MYSQL/regress.sql:mysqldump -f
2764 --opt --databases bacula:mysql"
2767 The directive has been split into two lines, but within the {\bf bacula-dir.conf} file
2768 would be written on a single line.
2770 This causes the File daemon to call the {\bf bpipe} plugin, which will write
2771 its data into the "pseudo" file {\bf /MYSQL/regress.sql} by calling the
2772 program {\bf mysqldump -f --opt --database bacula} to read the data during
2773 backup. The mysqldump command outputs all the data for the database named
2774 {\bf bacula}, which will be read by the plugin and stored in the backup.
2775 During restore, the data that was backed up will be sent to the program
2776 specified in the last field, which in this case is {\bf mysql}. When
2777 {\bf mysql} is called, it will read the data sent to it by the plugn
2778 then write it back to the same database from which it came ({\bf bacula}
2781 The {\bf bpipe} plugin is a generic pipe program, that simply transmits
2782 the data from a specified program to Bacula for backup, and then from Bacula to
2783 a specified program for restore.
2785 By using different command lines to {\bf bpipe},
2786 you can backup any kind of data (ASCII or binary) depending
2787 on the program called.
2789 \subsection{Microsoft Exchange Server 2003/2007 Plugin}
2790 \index[general]{Microsoft Exchange Server 2003/2007 Plugin}
2791 \subsubsection{Background}
2792 The Exchange plugin was made possible by a funded development project
2793 between Equiinet Ltd -- www.equiinet.com (many thanks) and Bacula Systems.
2794 The code for the plugin was written by James Harper, and the Bacula core
2795 code by Kern Sibbald. All the code for this funded development has become
2796 part of the Bacula project. Thanks to everyone who made it happen.
2798 \subsubsection{Concepts}
2799 Although it is possible to backup Exchange using Bacula VSS the Exchange
2800 plugin adds a good deal of functionality, because while Bacula VSS
2801 completes a full backup (snapshot) of Exchange, it does
2802 not support Incremental or Differential backups, restoring is more
2803 complicated, and a single database restore is not possible.
2805 Microsoft Exchange organises its storage into Storage Groups with
2806 Databases inside them. A default installation of Exchange will have a
2807 single Storage Group called 'First Storage Group', with two Databases
2808 inside it, "Mailbox Store (SERVER NAME)" and
2809 "Public Folder Store (SERVER NAME)",
2810 which hold user email and public folders respectively.
2812 In the default configuration, Exchange logs everything that happens to
2813 log files, such that if you have a backup, and all the log files since,
2814 you can restore to the present time. Each Storage Group has its own set
2815 of log files and operates independently of any other Storage Groups. At
2816 the Storage Group level, the logging can be turned off by enabling a
2817 function called "Enable circular logging". At this time the Exchange
2818 plugin will not function if this option is enabled.
2820 The plugin allows backing up of entire storage groups, and the restoring
2821 of entire storage groups or individual databases. Backing up and
2822 restoring at the individual mailbox or email item is not supported but
2823 can be simulated by use of the "Recovery" Storage Group (see below).
2825 \subsubsection{Installing}
2826 The Exchange plugin requires a DLL that is shipped with Microsoft
2827 Exchanger Server called {\bf esebcli2.dll}. Assuming Exchange is installed
2828 correctly the Exchange plugin should find this automatically and run
2829 without any additional installation.
2831 If the DLL can not be found automatically it will need to be copied into
2832 the Bacula installation
2833 directory (eg C:\verb+\+Program Files\verb+\+Bacula\verb+\+bin). The Exchange API DLL is
2834 named esebcli2.dll and is found in C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+bin on a
2835 default Exchange installation.
2837 \subsubsection{Backing Up}
2838 To back up an Exchange server the Fileset definition must contain at
2839 least {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"} for
2840 the backup to work correctly. The 'exchange:' bit tells Bacula to look
2841 for the exchange plugin, the '@EXCHANGE' bit makes sure all the backed
2842 up files are prefixed with something that isn't going to share a name
2843 with something outside the plugin, and the 'Microsoft Information Store'
2844 bit is required also. It is also possible to add the name of a storage
2845 group to the "Plugin =" line, eg \\
2846 {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"} \\
2847 if you want only a single storage group backed up.
2849 Additionally, you can suffix the 'Plugin =' directive with
2850 ":notrunconfull" which will tell the plugin not to truncate the Exchange
2851 database at the end of a full backup.
2853 An Incremental or Differential backup will backup only the database logs
2854 for each Storage Group by inspecting the "modified date" on each
2855 physical log file. Because of the way the Exchange API works, the last
2856 logfile backed up on each backup will always be backed up by the next
2857 Incremental or Differential backup too. This adds 5MB to each
2858 Incremental or Differential backup size but otherwise does not cause any
2861 By default, a normal VSS fileset containing all the drive letters will
2862 also back up the Exchange databases using VSS. This will interfere with
2863 the plugin and Exchange's shared ideas of when the last full backup was
2864 done, and may also truncate log files incorrectly. It is important,
2865 therefore, that the Exchange database files be excluded from the backup,
2866 although the folders the files are in should be included, or they will
2867 have to be recreated manually if a bare metal restore is done.
2872 File = C:/Program Files/Exchsrvr/mdbdata
2873 Plugin = "exchange:..."
2876 File = C:/Program Files/Exchsrvr/mdbdata/E00.chk
2877 File = C:/Program Files/Exchsrvr/mdbdata/E00.log
2878 File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log
2879 File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log
2880 File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log
2881 File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log
2882 File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb
2887 The advantage of excluding the above files is that you can significantly
2888 reduce the size of your backup since all the important Exchange files
2889 will be properly saved by the Plugin.
2892 \subsubsection{Restoring}
2893 The restore operation is much the same as a normal Bacula restore, with
2894 the following provisos:
2897 \item The {\bf Where} restore option must not be specified
2898 \item Each Database directory must be marked as a whole. You cannot just
2899 select (say) the .edb file and not the others.
2900 \item If a Storage Group is restored, the directory of the Storage Group
2902 \item It is possible to restore only a subset of the available log files,
2903 but they {\bf must} be contiguous. Exchange will fail to restore correctly
2904 if a log file is missing from the sequence of log files
2905 \item Each database to be restored must be dismounted and marked as "Can be
2906 overwritten by restore"
2907 \item If an entire Storage Group is to be restored (eg all databases and
2908 logs in the Storage Group), then it is best to manually delete the
2909 database files from the server (eg C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+mdbdata\verb+\+*)
2910 as Exchange can get confused by stray log files lying around.
2913 \subsubsection{Restoring to the Recovery Storage Group}
2914 The concept of the Recovery Storage Group is well documented by
2916 \elink{http://support.microsoft.com/kb/824126}{http://support.microsoft.com/kb/824126},
2917 but to briefly summarize...
2919 Microsoft Exchange allows the creation of an additional Storage Group
2920 called the Recovery Storage Group, which is used to restore an older
2921 copy of a database (e.g. before a mailbox was deleted) into without
2922 messing with the current live data. This is required as the Standard and
2923 Small Business Server versions of Exchange can not ordinarily have more
2924 than one Storage Group.
2926 To create the Recovery Storage Group, drill down to the Server in Exchange
2927 System Manager, right click, and select
2928 {\bf "New -> Recovery Storage Group..."}. Accept or change the file
2929 locations and click OK. On the Recovery Storage Group, right click and
2930 select {\bf "Add Database to Recover..."} and select the database you will
2933 Restore only the single database nominated as the database in the
2934 Recovery Storage Group. Exchange will redirect the restore to the
2935 Recovery Storage Group automatically.
2936 Then run the restore.
2938 \subsubsection{Restoring on Microsoft Server 2007}
2939 Apparently the {\bf Exmerge} program no longer exists in Microsoft Server
2940 2007, and hence you use a new procedure for recovering a single mail box.
2941 This procedure is documented by Microsoft at:
2942 \elink{http://technet.microsoft.com/en-us/library/aa997694.aspx}{http://technet.microsoft.com/en-us/library/aa997694.aspx},
2943 and involves using the {\bf Restore-Mailbox} and {\bf
2944 Get-Mailbox Statistics} shell commands.
2946 \subsubsection{Caveats}
2947 This plugin is still being developed, so you should consider it
2948 currently in BETA test, and thus use in a production environment
2949 should be done only after very careful testing.
2951 When doing a full backup, the Exchange database logs are truncated by
2952 Exchange as soon as the plugin has completed the backup. If the data
2953 never makes it to the backup medium (eg because of spooling) then the
2954 logs will still be truncated, but they will also not have been backed
2955 up. A solution to this is being worked on. You will have to schedule a
2956 new Full backup to ensure that your next backups will be usable.
2958 The "Enable Circular Logging" option cannot be enabled or the plugin
2961 Exchange insists that a successful Full backup must have taken place if
2962 an Incremental or Differential backup is desired, and the plugin will
2963 fail if this is not the case. If a restore is done, Exchange will
2964 require that a Full backup be done before an Incremental or Differential
2967 The plugin will most likely not work well if another backup application
2968 (eg NTBACKUP) is backing up the Exchange database, especially if the
2969 other backup application is truncating the log files.
2971 The Exchange plugin has not been tested with the {\bf Accurate} option, so
2972 we recommend either carefully testing or that you avoid this option for
2975 The Exchange plugin is not called during processing the bconsole {\bf
2976 estimate} command, and so anything that would be backed up by the plugin
2977 will not be added to the estimate total that is displayed.
2980 \subsection{libdbi Framework}
2981 \index[general]{libdbi Framework}
2982 As a general guideline, Bacula has support for a few catalog database drivers
2983 (MySQL, PostgreSQL, SQLite)
2984 coded natively by the Bacula team. With the libdbi implementation, which is a
2985 Bacula driver that uses libdbi to access the catalog, we have an open field to
2986 use many different kinds database engines following the needs of users.
2988 The according to libdbi (http://libdbi.sourceforge.net/) project: libdbi
2989 implements a database-independent abstraction layer in C, similar to the
2990 DBI/DBD layer in Perl. Writing one generic set of code, programmers can
2991 leverage the power of multiple databases and multiple simultaneous database
2992 connections by using this framework.
2994 Currently the libdbi driver in Bacula project only supports the same drivers
2995 natively coded in Bacula. However the libdbi project has support for many
2996 others database engines. You can view the list at
2997 http://libdbi-drivers.sourceforge.net/. In the future all those drivers can be
2998 supported by Bacula, however, they must be tested properly by the Bacula team.
3000 Some of benefits of using libdbi are:
3002 \item The possibility to use proprietary databases engines in which your
3003 proprietary licenses prevent the Bacula team from developing the driver.
3004 \item The possibility to use the drivers written for the libdbi project.
3005 \item The possibility to use other database engines without recompiling Bacula
3006 to use them. Just change one line in bacula-dir.conf
3007 \item Abstract Database access, this is, unique point to code and profiling
3008 catalog database access.
3011 The following drivers have been tested:
3013 \item PostgreSQL, with and without batch insert
3014 \item Mysql, with and without batch insert
3019 In the future, we will test and approve to use others databases engines
3020 (proprietary or not) like DB2, Oracle, Microsoft SQL.
3022 To compile Bacula to support libdbi we need to configure the code with the
3023 --with-dbi and --with-dbi-driver=[database] ./configure options, where
3024 [database] is the database engine to be used with Bacula (of course we can
3025 change the driver in file bacula-dir.conf, see below). We must configure the
3026 access port of the database engine with the option --with-db-port, because the
3027 libdbi framework doesn't know the default access port of each database.
3029 The next phase is checking (or configuring) the bacula-dir.conf, example:
3033 dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
3034 dbname = regress; user = regress; password = ""
3038 The parameter {\bf dbdriver} indicates that we will use the driver dbi with a
3039 mysql database. Currently the drivers supported by Bacula are: postgresql,
3040 mysql, sqlite, sqlite3; these are the names that may be added to string "dbi:".
3042 The following limitations apply when Bacula is set to use the libdbi framework:
3043 - Not tested on the Win32 platform
3044 - A little performance is lost if comparing with native database driver.
3045 The reason is bound with the database driver provided by libdbi and the
3046 simple fact that one more layer of code was added.
3048 It is important to remember, when compiling Bacula with libdbi, the
3049 following packages are needed:
3051 \item libdbi version 1.0.0, http://libdbi.sourceforge.net/
3052 \item libdbi-drivers 1.0.0, http://libdbi-drivers.sourceforge.net/
3055 You can download them and compile them on your system or install the packages
3056 from your OS distribution.
3058 \subsection{Console Command Additions and Enhancements}
3059 \index[general]{Console Additions}
3061 \subsubsection{Display Autochanger Content}
3062 \index[general]{StatusSlots}
3064 The {\bf status slots storage=\lt{}storage-name\gt{}} command displays
3065 autochanger content.
3069 Slot | Volume Name | Status | Media Type | Pool |
3070 ------+---------------+----------+-------------------+------------|
3071 1 | 00001 | Append | DiskChangerMedia | Default |
3072 2 | 00002 | Append | DiskChangerMedia | Default |
3073 3*| 00003 | Append | DiskChangerMedia | Scratch |
3078 If you an asterisk ({\bf *}) appears after the slot number, you must run an
3079 {\bf update slots} command to synchronize autochanger content with your
3082 \subsubsection{list joblog job=xxx or jobid=nnn}
3083 \index[general]{list joblog}
3084 A new list command has been added that allows you to list the contents
3085 of the Job Log stored in the catalog for either a Job Name (fully qualified)
3086 or for a particular JobId. The {\bf llist} command will include a line with
3087 the time and date of the entry.
3089 Note for the catalog to have Job Log entries, you must have a directive
3096 In your Director's {\bf Messages} resource.
3098 \subsubsection{Use separator for multiple commands}
3099 \index[general]{Command Separator}
3100 When using bconsole with readline, you can set the command separator with
3101 \textbf{@separator} command to one
3102 of those characters to write commands who require multiple input in one line.
3104 !$%&'()*+,-/:;<>?[]^`{|}~
3107 \subsubsection{Deleting Volumes}
3108 The delete volume bconsole command has been modified to
3109 require an asterisk (*) in front of a MediaId otherwise the
3110 value you enter is a taken to be a Volume name. This is so that
3111 users may delete numeric Volume names. The previous Bacula versions
3112 assumed that all input that started with a number was a MediaId.
3114 This new behavior is indicated in the prompt if you read it
3117 \subsection{Bare Metal Recovery}
3118 The old bare metal recovery project is essentially dead. One
3119 of the main features of it was that it would build a recovery
3120 CD based on the kernel on your system. The problem was that
3121 every distribution has a different boot procedure and different
3122 scripts, and worse yet, the boot procedures and scripts change
3123 from one distribution to another. This meant that maintaining
3124 (keeping up with the changes) the rescue CD was too much work.
3126 To replace it, a new bare metal recovery USB boot stick has been developed
3127 by Bacula Systems. This technology involves remastering a Ubuntu LiveCD to
3128 boot from a USB key.
3132 \item Recovery can be done from within graphical environment.
3133 \item Recovery can be done in a shell.
3134 \item Ubuntu boots on a large number of Linux systems.
3135 \item The process of updating the system and adding new
3136 packages is not too difficult.
3137 \item The USB key can easily be upgraded to newer Ubuntu versions.
3138 \item The USB key has writable partitions for modifications to
3139 the OS and for modification to your home directory.
3140 \item You can add new files/directories to the USB key very easily.
3141 \item You can save the environment from multiple machines on
3143 \item Bacula Systems is funding its ongoing development.
3146 The disadvantages are:
3148 \item The USB key is usable but currently under development.
3149 \item Not everyone may be familiar with Ubuntu (no worse
3151 \item Some older OSes cannot be booted from USB. This can
3152 be resolved by first booting a Ubuntu LiveCD then plugging
3154 \item Currently the documentation is sketchy and not yet added
3155 to the main manual. See below ...
3158 The documentation and the code can be found in the {\bf rescue} package
3159 in the directory {\bf linux/usb}.
3161 \subsection{Miscellaneous}
3162 \index[general]{Misc New Features}
3164 \subsubsection{Allow Mixed Priority = \lt{}yes\vb{}no\gt{}}
3165 \index[general]{Allow Mixed Priority}
3166 This directive is only implemented in version 2.5 and later. When
3167 set to {\bf yes} (default {\bf no}), this job may run even if lower
3168 priority jobs are already running. This means a high priority job
3169 will not have to wait for other jobs to finish before starting.
3170 The scheduler will only mix priorities when all running jobs have
3173 Note that only higher priority jobs will start early. Suppose the
3174 director will allow two concurrent jobs, and that two jobs with
3175 priority 10 are running, with two more in the queue. If a job with
3176 priority 5 is added to the queue, it will be run as soon as one of
3177 the running jobs finishes. However, new priority 10 jobs will not
3178 be run until the priority 5 job has finished.
3180 \subsubsection{Bootstrap File Directive -- FileRegex}
3181 \index[general]{Bootstrap File Directive}
3182 {\bf FileRegex} is a new command that can be added to the bootstrap
3183 (.bsr) file. The value is a regular expression. When specified, only
3184 matching filenames will be restored.
3186 During a restore, if all File records are pruned from the catalog
3187 for a Job, normally Bacula can restore only all files saved. That
3188 is there is no way using the catalog to select individual files.
3189 With this new feature, Bacula will ask if you want to specify a Regex
3190 expression for extracting only a part of the full backup.
3193 Building directory tree for JobId(s) 1,3 ...
3194 There were no files inserted into the tree, so file selection
3195 is not possible.Most likely your retention policy pruned the files
3197 Do you want to restore all the files? (yes\vb{}no): no
3199 Regexp matching files to restore? (empty to abort): /tmp/regress/(bin|tests)/
3200 Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr
3203 \subsubsection{Bootstrap File Optimization Changes}
3204 In order to permit proper seeking on disk files, we have extended the bootstrap
3205 file format to include a {\bf VolStartAddr} and {\bf VolEndAddr} records. Each
3206 takes a 64 bit unsigned integer range (i.e. nnn-mmm) which defines the start
3207 address range and end address range respectively. These two directives replace
3208 the {\bf VolStartFile}, {\bf VolEndFile}, {\bf VolStartBlock} and {\bf
3209 VolEndBlock} directives. Bootstrap files containing the old directives will
3210 still work, but will not properly take advantage of proper disk seeking, and
3211 may read completely to the end of a disk volume during a restore. With the new
3212 format (automatically generated by the new Director), restores will seek
3213 properly and stop reading the volume when all the files have been restored.
3215 \subsubsection{Solaris ZFS/NFSv4 ACLs}
3216 This is an upgrade of the previous Solaris ACL backup code
3217 to the new library format, which will backup both the old
3218 POSIX(UFS) ACLs as well as the ZFS ACLs.
3220 The new code can also restore POSIX(UFS) ACLs to a ZFS filesystem
3221 (it will translate the POSIX(UFS)) ACL into a ZFS/NFSv4 one) it can also
3222 be used to transfer from UFS to ZFS filesystems.
3225 \subsubsection{Virtual Tape Emulation}
3226 \index[general]{Virtual Tape Emulation}
3227 We now have a Virtual Tape emulator that allows us to run though 99.9\% of
3228 the tape code but actually reading and writing to a disk file. Used with the
3229 \textbf{disk-changer} script, you can now emulate an autochanger with 10 drives
3230 and 700 slots. This feature is most useful in testing. It is enabled
3231 by using {\bf Device Type = vtape} in the Storage daemon's Device
3232 directive. This feature is only implemented on Linux machines and should not be
3233 used for production.
3235 \subsubsection{Bat Enhancements}
3236 \index[general]{Bat Enhancements}
3237 Bat (the Bacula Administration Tool) GUI program has been significantly
3238 enhanced and stabilized. In particular, there are new table based status
3239 commands; it can now be easily localized using Qt4 Linguist.
3241 The Bat communications protocol has been significantly enhanced to improve
3242 GUI handling. Note, you {\bf must} use a the bat that is distributed with
3243 the Director you are using otherwise the communications protocol will not
3246 \subsubsection{RunScript Enhancements}
3247 \index[general]{RunScript Enhancements}
3248 The {\bf RunScript} resource has been enhanced to permit multiple
3249 commands per RunScript. Simply specify multiple {\bf Command} directives
3256 Command = "/bin/echo test"
3257 Command = "/bin/echo an other test"
3258 Command = "/bin/echo 3 commands in the same runscript"
3265 A new Client RunScript {\bf RunsWhen} keyword of {\bf AfterVSS} has been
3266 implemented, which runs the command after the Volume Shadow Copy has been made.
3268 Console commands can be specified within a RunScript by using:
3269 {\bf Console = \lt{}command\gt{}}, however, this command has not been
3270 carefully tested and debugged and is known to easily crash the Director.
3271 We would appreciate feedback. Due to the recursive nature of this command, we
3272 may remove it before the final release.
3274 \subsubsection{Status Enhancements}
3275 \index[general]{Status Enhancements}
3276 The bconsole {\bf status dir} output has been enhanced to indicate
3277 Storage daemon job spooling and despooling activity.
3279 \subsubsection{Connect Timeout}
3280 \index[general]{Connect Timeout}
3281 The default connect timeout to the File
3282 daemon has been set to 3 minutes. Previously it was 30 minutes.
3284 \subsubsection{ftruncate for NFS Volumes}
3285 \index[general]{ftruncate for NFS Volumes}
3286 If you write to a Volume mounted by NFS (say on a local file server),
3287 in previous Bacula versions, when the Volume was recycled, it was not
3288 properly truncated because NFS does not implement ftruncate (file
3289 truncate). This is now corrected in the new version because we have
3290 written code (actually a kind user) that deletes and recreates the Volume,
3291 thus accomplishing the same thing as a truncate.
3293 \subsubsection{Support for Ubuntu}
3294 The new version of Bacula now recognizes the Ubuntu (and Kubuntu)
3295 version of Linux, and thus now provides correct autostart routines.
3296 Since Ubuntu officially supports Bacula, you can also obtain any
3297 recent release of Bacula from the Ubuntu repositories.
3299 \subsubsection{Recycle Pool = \lt{}pool-name\gt{}}
3300 \index[general]{Recycle Pool}
3301 The new \textbf{RecyclePool} directive defines to which pool the Volume will
3302 be placed (moved) when it is recycled. Without this directive, a Volume will
3303 remain in the same pool when it is recycled. With this directive, it can be
3304 moved automatically to any existing pool during a recycle. This directive is
3305 probably most useful when defined in the Scratch pool, so that volumes will
3306 be recycled back into the Scratch pool.
3308 \subsubsection{FD Version}
3309 \index[general]{FD Version}
3310 The File daemon to Director protocol now includes a version
3311 number, which although there is no visible change for users,
3312 will help us in future versions automatically determine
3313 if a File daemon is not compatible.
3315 \subsubsection{Max Run Sched Time = \lt{}time-period-in-seconds\gt{}}
3316 \index[general]{Max Run Sched Time}
3317 The time specifies the maximum allowed time that a job may run, counted from
3318 when the job was scheduled. This can be useful to prevent jobs from running
3319 during working hours. We can see it like \texttt{Max Start Delay + Max Run
3322 \subsubsection{Max Wait Time = \lt{}time-period-in-seconds\gt{}}
3323 \index[general]{Max Wait Time}
3324 Previous \textbf{MaxWaitTime} directives aren't working as expected, instead
3325 of checking the maximum allowed time that a job may block for a resource,
3326 those directives worked like \textbf{MaxRunTime}. Some users are reporting to
3327 use \textbf{Incr/Diff/Full Max Wait Time} to control the maximum run time of
3328 their job depending on the level. Now, they have to use
3329 \textbf{Incr/Diff/Full Max Run Time}. \textbf{Incr/Diff/Full Max Wait Time}
3330 directives are now deprecated.
3332 \subsubsection{Incremental|Differential Max Wait Time = \lt{}time-period-in-seconds\gt{}}
3333 \index[general]{Incremental Max Wait Time}
3334 \index[general]{Differential Max Wait Time}
3336 These directives have been deprecated in favor of
3337 \texttt{Incremental|Differential Max Run Time}.
3339 \subsubsection{Max Run Time directives}
3340 \index[general]{Max Run Time directives}
3341 Using \textbf{Full/Diff/Incr Max Run Time}, it's now possible to specify the
3342 maximum allowed time that a job can run depending on the level.
3344 \addcontentsline{lof}{figure}{Job time control directives}
3346 \includegraphics[width=\linewidth]{different_time}
3349 \subsubsection{Statistics Enhancements}
3350 \index[general]{Statistics Enhancements}
3351 If you (or probably your boss) want to have statistics on your backups to
3352 provide some \textit{Service Level Agreement} indicators, you could use a few
3353 SQL queries on the Job table to report how many:
3357 \item jobs have been successful
3358 \item files have been backed up
3362 However, these statistics are accurate only if your job retention is greater
3363 than your statistics period. Ie, if jobs are purged from the catalog, you won't
3364 be able to use them.
3366 Now, you can use the \textbf{update stats [days=num]} console command to fill
3367 the JobHistory table with new Job records. If you want to be sure to take in
3368 account only \textbf{good jobs}, ie if one of your important job has failed but
3369 you have fixed the problem and restarted it on time, you probably want to
3370 delete the first \textit{bad} job record and keep only the successful one. For
3371 that simply let your staff do the job, and update JobHistory table after two or
3372 three days depending on your organization using the \textbf{[days=num]} option.
3374 These statistics records aren't used for restoring, but mainly for
3375 capacity planning, billings, etc.
3377 The Bweb interface provides a statistics module that can use this feature. You
3378 can also use tools like Talend or extract information by yourself.
3380 The \textbf{Statistics Retention = \lt{}time\gt{}} director directive defines
3381 the length of time that Bacula will keep statistics job records in the Catalog
3382 database after the Job End time. (In \texttt{JobHistory} table) When this time
3383 period expires, and if user runs \texttt{prune stats} command, Bacula will
3384 prune (remove) Job records that are older than the specified period.
3386 You can use the following Job resource in your nightly \textbf{BackupCatalog}
3387 job to maintain statistics.
3390 Name = BackupCatalog
3393 Console = "update stats days=3"
3394 Console = "prune stats yes"
3401 \subsubsection{ScratchPool = \lt{}pool-resource-name\gt{}}
3402 \index[general]{ScratchPool}
3403 This directive permits to specify a specific \textsl{Scratch} pool for the
3404 current pool. This is useful when using multiple storage sharing the same
3405 mediatype or when you want to dedicate volumes to a particular set of pool.
3407 \subsubsection{Enhanced Attribute Despooling}
3408 \index[general]{Attribute Despooling}
3409 If the storage daemon and the Director are on the same machine, the spool file
3410 that contains attributes is read directly by the Director instead of being
3411 transmitted across the network. That should reduce load and speedup insertion.
3413 \subsubsection{SpoolSize = \lt{}size-specification-in-bytes\gt{}}
3414 \index[general]{SpoolSize}
3415 A new Job directive permits to specify the spool size per job. This is used
3416 in advanced job tunning. {\bf SpoolSize={\it bytes}}
3418 \subsubsection{MaximumConsoleConnections = \lt{}number\gt{}}
3419 \index[general]{MaximumConsoleConnections}
3420 A new director directive permits to specify the maximum number of Console
3421 Connections that could run concurrently. The default is set to 20, but you may
3422 set it to a larger number.
3424 \subsubsection{VerId = \lt{}string\gt{}}
3425 \index[general]{VerId}
3426 A new director directive permits to specify a personnal identifier that will be
3427 displayed in the \texttt{version} command.
3429 \subsubsection{dbcheck enhancements}
3430 \index[general]{dbcheck enhancements}
3431 If you are using Mysql, dbcheck will now ask you if you want to create
3432 temporary indexes to speed up orphaned Path and Filename elimination.
3434 A new \texttt{-B} option allows you to print catalog information in a simple
3435 text based format. This is useful to backup it in a secure way.
3450 You can now specify the database connection port in the command line.
3452 \subsubsection{{-}{-}docdir configure option}
3453 \index[general]{{-}{-}docdir configure option}
3454 You can use {-}{-}docdir= on the ./configure command to
3455 specify the directory where you want Bacula to install the
3456 LICENSE, ReleaseNotes, ChangeLog, ... files. The default is
3457 {\bf /usr/share/doc/bacula}.
3459 \subsubsection{{-}{-}htmldir configure option}
3460 \index[general]{{-}{-}htmldir configure option}
3461 You can use {-}{-}htmldir= on the ./configure command to
3462 specify the directory where you want Bacula to install the bat html help
3463 files. The default is {\bf /usr/share/doc/bacula/html}
3465 \subsubsection{{-}{-}with-plugindir configure option}
3466 \index[general]{{-}{-}plugindir configure option}
3467 You can use {-}{-}plugindir= on the ./configure command to
3468 specify the directory where you want Bacula to install
3469 the plugins (currently only bpipe-fd). The default is