1 \chapter{New Features in 5.1.x}
2 This chapter presents the new features that have been added to the
3 current version of Bacula that is under development. This version will be
4 released at some later date, probably near the end of 2010.
6 \section{Purge Migration Job when Completed}
8 A new directive may be added to the Migration Job definition in the Director
9 configuration file to purge the job migrated at the end of a migration.
23 Selection Pattern = ".*Save"
25 Purge Migrated Job = yes
31 This project was submited by Dunlap Blake, testing and documentation was funded
34 \section{Job Bandwidth Limitation}
36 A new directive may be added to FileDaemon or Director to allow users to limit
37 the bandwidth used by a Job on a Client. It can be set for all Jobs globally,
38 per Directors in the File Daemon configuration, or per Job in the Director
45 Working Directory = /some/path
46 Pid Directory = /some/path
48 Maximum Bandwidth Per Job = 5MB/s
52 The above example would cause any jobs running with the FileDaemon to not
53 exceed 5MB/s of throughput when sending data to the Storage Daemon.
55 You can specify the speed parameter in k/s, kb/s, m/s, mb/s.
61 FileSet = FS_localhost
64 Maximum Bandwidth = 5MB/s
69 The above example would cause job \texttt{localhost-data} to not exceed 5MB/s
70 of throughput when sending data to the Storage Daemon.
72 A new console command \texttt{setbandwidth} permits to set dynamically the
73 maximum throughput of a running Job or for future jobs of a Client.
76 * setbandwidth limit=1000000 jobid=10
79 The \texttt{limit} parameter is in kb/s.
82 This project was funded by Bacula Systems and is available with Bacula
83 Enterprise Edition and Community Edition.
85 \section{Support for MSSQL Block Level Backup}
87 This project was funded by Bacula Systems and is available with Bacula
90 \section{Support for NDMP protocol}
92 The new \texttt{ndmp} Plugin is able to backup a NAS through NDMP protocol
93 using \textbf{Filer to server} approach, where the Filer is backing up across
94 the LAN to your Bacula server.
96 Accurate option should be turned on in the Job resource.
108 Plugin = "ndmp:host=nasbox user=root pass=root file=/vol/vol1"
113 This project was funded by Bacula Systems and is available with Bacula
116 \section{Incremental/Differential Block Level Difference Backup}
118 The new \texttt{delta} Plugin is able to compute and apply signature-based file
119 differences. It can be used to backup only changes in a big binary file like
120 Outlook PST, VirtualBox/VmWare images or database files.
122 It supports both Incremental and Differential backups and stores signatures
123 database in the File Daemon working directory. This plugin is available on all
124 plateform including Windows 32 and 64bit.
126 Accurate option should be turned on in the Job resource.
138 Plugin = "delta:/home/eric/.VirtualBox/HardDisks/lenny-i386.vdi"
143 This project was funded by Bacula Systems and is available with Bacula
146 \section{Include All Windows Drives in FileSet}
148 The \texttt{alldrives} Windows Plugin allows you to include all local drives
149 with a simple directive. This plugin is available for Windows 64 and 32 bit.
161 You exclude some specific drives with the \texttt{exclude} option.
168 Plugin = "alldrives: exclude=D,E"
174 This project was funded by Bacula Systems and is available with Bacula
177 \section{Changes in Bvfs (Bacula Virtual FileSystem)}
179 Bat has now a bRestore panel that uses Bvfs to display files and
180 directories. It's still experimental.
182 \texttt{Important}, the Bvfs module is not currently compatible with BaseJobs,
183 Copy and Migration jobs.
186 This project was funded by Bacula Systems.
188 \subsection*{General notes}
191 \item All fields are separated by a tab
192 \item You can specify \texttt{limit=} and \texttt{offset=} to list smoothly
193 records in very big directories
194 \item All operations (except cache creation) are designed to run instantly
195 \item At this time, Bvfs works faster on PostgreSQL than MySQL catalog. If you
196 can contribute new faster SQL queries we will be happy, else don't complain
198 \item The cache creation is dependent of the number of directories. As Bvfs
199 shares information accross jobs, the first creation can be slow
200 \item All fields are separated by a tab
201 \item Due to potential encoding problem, it's advised to allways use pathid in
205 \subsection*{Get dependent jobs from a given JobId}
207 Bvfs allows you to query the catalog against any combination of jobs. You
208 can combine all Jobs and all FileSet for a Client in a single session.
210 To get all JobId needed to restore a particular job, you can use the
211 \texttt{.bvfs\_get\_jobids} command.
214 .bvfs_get_jobids jobid=num [all]
218 .bvfs_get_jobids jobid=10
220 .bvfs_get_jobids jobid=10 all
224 In this example, a normal restore will need to use JobIds 1,2,5,10 to
225 compute a complete restore of the system.
227 With the \texttt{all} option, the Director will use all defined FileSet for
230 \subsection*{Generating Bvfs cache}
232 The \texttt{.bvfs\_update} command computes the directory cache for jobs
233 specified in argument, or for all jobs if unspecified.
236 .bvfs_update [jobid=numlist]
241 .bvfs_update jobid=1,2,3
244 You can run the cache update process in a RunScript after the catalog backup.
246 \subsection*{Get all versions of a specific file}
248 Bvfs allows you to find all versions of a specific file for a given Client with
249 the \texttt{.bvfs\_version} command. To avoid problems with encoding, this
250 function uses only PathId and FilenameId. The jobid argument is mandatory but
254 .bvfs_versions client=filedaemon pathid=num filenameid=num jobid=1
255 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
256 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
263 .bvfs_versions client=localhost-fd pathid=1 fnid=47 jobid=1
264 1 47 52 12 gD HRid IGk D Po Po A P BAA I A /uPgWaxMgKZlnMti7LChyA Vol1 1
267 \subsection*{List directories}
269 Bvfs allows you to list directories in a specific path.
271 .bvfs_lsdirs pathid=num path=/apath jobid=numlist limit=num offset=num
272 PathId FilenameId FileId JobId LStat Path
273 PathId FilenameId FileId JobId LStat Path
274 PathId FilenameId FileId JobId LStat Path
278 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
279 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record
280 listed is a directory.
283 .bvfs_lsdirs pathid=4 jobid=1,11,12
284 4 0 0 0 A A A A A A A A A A A A A A .
285 5 0 0 0 A A A A A A A A A A A A A A ..
286 3 0 0 0 A A A A A A A A A A A A A A regress/
289 In this example, to list directories present in \texttt{regress/}, you can use
291 .bvfs_lsdirs pathid=3 jobid=1,11,12
292 3 0 0 0 A A A A A A A A A A A A A A .
293 4 0 0 0 A A A A A A A A A A A A A A ..
294 2 0 0 0 A A A A A A A A A A A A A A tmp/
297 \subsection*{List files}
299 Bvfs allows you to list files in a specific path.
301 .bvfs_lsfiles pathid=num path=/apath jobid=numlist limit=num offset=num
302 PathId FilenameId FileId JobId LStat Path
303 PathId FilenameId FileId JobId LStat Path
304 PathId FilenameId FileId JobId LStat Path
308 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
309 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record listed
313 .bvfs_lsfiles pathid=4 jobid=1,11,12
314 4 0 0 0 A A A A A A A A A A A A A A .
315 5 0 0 0 A A A A A A A A A A A A A A ..
316 1 0 0 0 A A A A A A A A A A A A A A regress/
319 In this example, to list files present in \texttt{regress/}, you can use
321 .bvfs_lsfiles pathid=1 jobid=1,11,12
322 1 47 52 12 gD HRid IGk BAA I BMqcPH BMqcPE BMqe+t A titi
323 1 49 53 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B toto
324 1 48 54 12 gD HRie IGk BAA I BMqcPH BMqcPE BMqe+3 A tutu
325 1 45 55 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B ficheriro1.txt
326 1 46 56 12 gD HRie IGk BAA I BMqe/K BMqcPE BMqe+3 D ficheriro2.txt
329 \subsection*{Restore set of files}
331 Bvfs allows you to create a SQL table that contains files that you want to
332 restore. This table can be provided to a restore command with the file option.
335 .bvfs_restore fileid=numlist dirid=numlist hardlink=numlist path=b2num
337 restore file=?b2num ...
340 To include a directory (with \texttt{dirid}), Bvfs needs to run a query to
341 select all files. This query could be time consuming.
343 \texttt{hardlink} list is always composed of a serie of two numbers (jobid,
344 fileindex). This information can be found in the LinkFI field of the LStat
347 The \texttt{path} argument represents the name of the table that Bvfs will
348 store results. The format of this table is \texttt{b2[0-9]+}. (Should start by
349 b2 and followed by digits).
354 .bvfs_restore fileid=1,2,3,4 hardlink=10,15,10,20 jobid=10 path=b20001
358 \subsection*{Cleanup after restore}
360 To drop the table used by the restore command, you can use the
361 \texttt{.bvfs\_cleanup} command.
364 .bvfs_cleanup path=b20001
367 \section{Changes in the pruning algorithm}
369 We rewrote the job pruning algorithm in this version. Previously, in some users
370 reported that the pruning process at the end of jobs was very long. It should
371 not be longer the case. Now, Bacula won't prune automatically a Job if this
372 particular Job is needed to restore data. Example:
376 JobId: 2 Level: Incremental
377 JobId: 3 Level: Incremental
378 JobId: 4 Level: Differential
379 .. Other incrementals up to now
382 In this example, if the Job Retention defined in the Pool or in the Client
383 resource causes that Jobs with Jobid in 1,2,3,4 can be pruned, Bacula will
384 detect that JobId 1 and 4 are essential to restore data at the current state
385 and will prune only JobId 2 and 3.
387 \texttt{Important}, this change affect only the automatic pruning step after a
388 Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the
389 \texttt{VolumeRetention} period, important jobs can be pruned.
391 \section{Ability to Verify any specified Job}
392 You now have the ability to tell Bacula which Job should verify instead of
393 automatically verify just the last one.
395 This feature can be used with VolumeToCatalog, DiskToCatalog and Catalog level.
397 To verify a given job, just specify the Job jobid in argument when starting the
400 *run job=VerifyVolume jobid=1 level=VolumeToCatalog
402 JobName: VerifyVolume
403 Level: VolumeToCatalog
406 Pool: Default (From Job resource)
407 Storage: File (From Job resource)
408 Verify Job: VerifyVol.2010-09-08_14.17.17_03
409 Verify List: /tmp/regress/working/VerifyVol.bsr
410 When: 2010-09-08 14:17:31
412 OK to run? (yes/mod/no):
416 This project was funded by Bacula Systems and is available with Bacula
417 Enterprise Edition and Community Edition.
419 \section{Additions to RunScript variables}
420 You can have access to JobBytes and JobFiles using \%b and \%f in your runscript
421 command. The Client address is now available through \%h.
424 RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%f ClientAddress=%h"
427 %\section{Changes in drivetype.exe}
429 %Now the \texttt{drivetype.exe} program allows you to list all local hard
430 %drives. It can help to build dynamic FileSet on Windows.
433 %File = "\\|\"c:/program files/bacula/bin32/drivetype\" -l -a"
437 \section{Additions to the Plugin API}
438 The bfuncs structure has been extended to include a number of
442 The bFuncs structure defines the callback entry points within Bacula
443 that the plugin can use register events, get Bacula values, set
444 Bacula values, and send messages to the Job output or debug output.
446 The exact definition as of this writing is:
448 typedef struct s_baculaFuncs {
451 bRC (*registerBaculaEvents)(bpContext *ctx, ...);
452 bRC (*getBaculaValue)(bpContext *ctx, bVariable var, void *value);
453 bRC (*setBaculaValue)(bpContext *ctx, bVariable var, void *value);
454 bRC (*JobMessage)(bpContext *ctx, const char *file, int line,
455 int type, utime_t mtime, const char *fmt, ...);
456 bRC (*DebugMessage)(bpContext *ctx, const char *file, int line,
457 int level, const char *fmt, ...);
458 void *(*baculaMalloc)(bpContext *ctx, const char *file, int line,
460 void (*baculaFree)(bpContext *ctx, const char *file, int line, void *mem);
462 /* New functions follow */
463 bRC (*AddExclude)(bpContext *ctx, const char *file);
464 bRC (*AddInclude)(bpContext *ctx, const char *file);
465 bRC (*AddIncludeOptions)(bpContext *ctx, const char *opts);
466 bRC (*AddRegex)(bpContext *ctx, const char *item, int type);
467 bRC (*AddWild)(bpContext *ctx, const char *item, int type);
468 bRC (*checkChanges)(bpContext *ctx, struct save_pkt *sp);
474 \item [AddExclude] can be called to exclude a file. The file
475 string passed may include wildcards that will be interpreted by
476 the {\bf fnmatch} subroutine. This function can be called
477 multiple times, and each time the file specified will be added
478 to the list of files to be excluded. Note, this function only
479 permits adding excludes of specific file or directory names,
480 or files matched by the rather simple fnmatch mechanism.
481 See below for information on doing wild-card and regex excludes.
483 \item [NewInclude] can be called to create a new Include block. This
484 block will be added before any user defined Include blocks. This
485 function can be called multiple times, but each time, it will create
486 a new Include section (not normally needed). This function should
487 be called only if you want to add an entirely new Include block.
489 \item [AddInclude] can be called to add new files/directories to
490 be included. They are added to the current Include block. If
491 NewInclude has not been included, the current Include block is
492 the last one that the user created. This function
493 should be used only if you want to add totally new files/directories
494 to be included in the backup.
496 \item [NewOptions] adds a new Options block to the current Include
497 in front of any other Options blocks. This permits the plugin to
498 add exclude directives (wild-cards and regexes) in front of the
499 user Options, and thus prevent certain files from being backed up.
500 This can be useful if the plugin backs up files, and they should
501 not be also backed up by the main Bacula code. This function
502 may be called multiple times, and each time, it creates a new
503 prepended Options block. Note: normally you want to call this
504 entry point prior to calling AddOptions, AddRegex, or AddWild.
506 \item [AddOptions] allows the plugin it set options in
507 the current Options block, which is normally created with the
508 NewOptions call just prior to adding Include Options.
509 The permitted options are passed as a character string, where
510 each character has a specific meaning as defined below:
513 \item [a] always replace files (default).
514 \item [e] exclude rather than include.
515 \item [h] no recursion into subdirectories.
516 \item [H] do not handle hard links.
517 \item [i] ignore case in wildcard and regex matches.
518 \item [M] compute an MD5 sum.
519 \item [p] use a portable data format on Windows (not recommended).
520 \item [R] backup resource forks and Findr Info.
521 \item [r] read from a fifo
522 \item [S1] compute an SHA1 sum.
523 \item [S2] compute an SHA256 sum.
524 \item [S3] comput an SHA512 sum.
525 \item [s] handle sparse files.
526 \item [m] use st\_mtime only for file differences.
527 \item [k] restore the st\_atime after accessing a file.
528 \item [A] enable ACL backup.
529 \item [Vxxx:] specify verify options. Must terminate with :
530 \item [Cxxx:] specify accurate options. Must terminate with :
531 \item [Jxxx:] specify base job Options. Must terminate with :
532 \item [Pnnn:] specify integer nnn paths to strip. Must terminate with :
534 \item [Zn] specify gzip compression level n.
535 \item [K] do not use st\_atime in backup decision.
536 \item [c] check if file changed during backup.
537 \item [N] honor no dump flag.
538 \item [X] enable backup of extended attributes.
541 \item [AddRegex] adds a regex expression to the current Options block.
542 The fillowing options are permitted:
544 \item [ ] (a blank) regex applies to whole path and filename.
545 \item [F] regex applies only to the filename (directory or path stripped).
546 \item [D] regex applies only to the directory (path) part of the name.
549 \item [AddWild] adds a wildcard expression to the current Options block.
550 The fillowing options are permitted:
552 \item [ ] (a blank) regex applies to whole path and filename.
553 \item [F] regex applies only to the filename (directory or path stripped).
554 \item [D] regex applies only to the directory (path) part of the name.
557 \item [checkChanges] call the \texttt{check\_changes()} function in Bacula code
558 that can use Accurate code to compare the file information in argument with
559 the previous file information. The \texttt{delta\_seq} attribute of the
560 \texttt{save\_pkt} will be updated, and the call will return
561 \texttt{bRC\_Seen} if the core code wouldn't decide to backup it.
566 \subsection{Bacula events}
567 The list of events has been extended to include:
573 bEventStartBackupJob = 3,
574 bEventEndBackupJob = 4,
575 bEventStartRestoreJob = 5,
576 bEventEndRestoreJob = 6,
577 bEventStartVerifyJob = 7,
578 bEventEndVerifyJob = 8,
579 bEventBackupCommand = 9,
580 bEventRestoreCommand = 10,
585 bEventCancelCommand = 13,
586 bEventVssBackupAddComponents = 14,
587 bEventVssRestoreLoadComponentMetadata = 15,
588 bEventVssRestoreSetComponentsSelected = 16,
589 bEventRestoreObject = 17,
590 bEventEndFileSet = 18,
591 bEventPluginCommand = 19,
592 bEventVssBeforeCloseRestore = 20,
593 bEventVssPrepareSnapshot = 21
599 \item [bEventCancelCommand] is called whenever the currently
600 running Job is cancelled */
602 \item [bEventVssBackupAddComponents]
604 \item [bEventVssPrepareSnapshot] is called before creating VSS snapshots, it
605 provides a char[27] table where the plugin can add Windows drives that will
606 be used during the Job. You need to add them without duplicates, and you can
607 use in \texttt{fd\_common.h} \texttt{add\_drive()} and \texttt{copy\_drives()}
611 \chapter{Release Version 5.0.3}
613 There are no new features in version 5.0.2. This version simply fixes a
614 number of bugs found in version 5.0.1 during the onging development
617 \chapter{Release Version 5.0.2}
619 There are no new features in version 5.0.2. This version simply fixes a
620 number of bugs found in version 5.0.1 during the onging development
626 \chapter{New Features in 5.0.1}
628 This chapter presents the new features that are in the released Bacula version
629 5.0.1. This version mainly fixes a number of bugs found in version 5.0.0 during
630 the onging development process.
632 \section{Truncate Volume after Purge}
633 \label{sec:actiononpurge}
635 The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate
636 the volume when it is purged with the new command \texttt{purge volume
637 action}. It is useful to prevent disk based volumes from consuming too much
643 Action On Purge = Truncate
648 As usual you can also set this property with the \texttt{update volume} command
650 *update volume=xxx ActionOnPurge=Truncate
651 *update volume=xxx actiononpurge=None
654 To ask Bacula to truncate your \texttt{Purged} volumes, you need to use the
655 following command in interactive mode or in a RunScript as shown after:
657 *purge volume action=truncate storage=File allpools
658 # or by default, action=all
659 *purge volume action storage=File pool=Default
662 This is possible to specify the volume name, the media type, the pool, the
663 storage, etc\dots (see \texttt{help purge}) Be sure that your storage device is
664 idle when you decide to run this command.
673 Console = "purge volume action=all allpools storage=File"
678 \textbf{Important note}: This feature doesn't work as
679 expected in version 5.0.0. Please do not use it before version 5.0.1.
681 \section{Allow Higher Duplicates}
682 This directive did not work correctly and has been depreciated
683 (disabled) in version 5.0.1. Please remove it from your bacula-dir.conf
684 file as it will be removed in a future rlease.
686 \section{Cancel Lower Level Duplicates}
687 This directive was added in Bacula version 5.0.1. It compares the
688 level of a new backup job to old jobs of the same name, if any,
689 and will kill the job which has a lower level than the other one.
690 If the levels are the same (i.e. both are Full backups), then
691 nothing is done and the other Cancel XXX Duplicate directives
694 \chapter{New Features in 5.0.0}
696 \section{Maximum Concurent Jobs for Devices}
697 \label{sec:maximumconcurentjobdevice}
699 {\bf Maximum Concurrent Jobs} is a new Device directive in the Storage
700 Daemon configuration permits setting the maximum number of Jobs that can
701 run concurrently on a specified Device. Using this directive, it is
702 possible to have different Jobs using multiple drives, because when the
703 Maximum Concurrent Jobs limit is reached, the Storage Daemon will start new
704 Jobs on any other available compatible drive. This facilitates writing to
705 multiple drives with multiple Jobs that all use the same Pool.
707 This project was funded by Bacula Systems.
709 \section{Restore from Multiple Storage Daemons}
710 \index[general]{Restore}
712 Previously, you were able to restore from multiple devices in a single Storage
713 Daemon. Now, Bacula is able to restore from multiple Storage Daemons. For
714 example, if your full backup runs on a Storage Daemon with an autochanger, and
715 your incremental jobs use another Storage Daemon with lots of disks, Bacula
716 will switch automatically from one Storage Daemon to an other within the same
719 You must upgrade your File Daemon to version 3.1.3 or greater to use this
722 This project was funded by Bacula Systems with the help of Equiinet.
724 \section{File Deduplication using Base Jobs}
725 A base job is sort of like a Full save except that you will want the FileSet to
726 contain only files that are unlikely to change in the future (i.e. a snapshot
727 of most of your system after installing it). After the base job has been run,
728 when you are doing a Full save, you specify one or more Base jobs to be used.
729 All files that have been backed up in the Base job/jobs but not modified will
730 then be excluded from the backup. During a restore, the Base jobs will be
731 automatically pulled in where necessary.
733 This is something none of the competition does, as far as we know (except
734 perhaps BackupPC, which is a Perl program that saves to disk only). It is big
735 win for the user, it makes Bacula stand out as offering a unique optimization
736 that immediately saves time and money. Basically, imagine that you have 100
737 nearly identical Windows or Linux machine containing the OS and user files.
738 Now for the OS part, a Base job will be backed up once, and rather than making
739 100 copies of the OS, there will be only one. If one or more of the systems
740 have some files updated, no problem, they will be automatically restored.
742 See the \ilink{Base Job Chapter}{basejobs} for more information.
744 This project was funded by Bacula Systems.
746 \section{AllowCompression = \lt{}yes\vb{}no\gt{}}
747 \index[dir]{AllowCompression}
749 This new directive may be added to Storage resource within the Director's
750 configuration to allow users to selectively disable the client compression for
751 any job which writes to this storage resource.
757 Address = ultrium-tape
758 Password = storage_password # Password for Storage Daemon
761 AllowCompression = No # Tape drive has hardware compression
764 The above example would cause any jobs running with the UltriumTape storage
765 resource to run without compression from the client file daemons. This
766 effectively overrides any compression settings defined at the FileSet level.
768 This feature is probably most useful if you have a tape drive which supports
769 hardware compression. By setting the \texttt{AllowCompression = No} directive
770 for your tape drive storage resource, you can avoid additional load on the file
771 daemon and possibly speed up tape backups.
773 This project was funded by Collaborative Fusion, Inc.
775 \section{Accurate Fileset Options}
776 \label{sec:accuratefileset}
778 In previous versions, the accurate code used the file creation and modification
779 times to determine if a file was modified or not. Now you can specify which
780 attributes to use (time, size, checksum, permission, owner, group, \dots),
781 similar to the Verify options.
797 \item {\bf i} compare the inodes
798 \item {\bf p} compare the permission bits
799 \item {\bf n} compare the number of links
800 \item {\bf u} compare the user id
801 \item {\bf g} compare the group id
802 \item {\bf s} compare the size
803 \item {\bf a} compare the access time
804 \item {\bf m} compare the modification time (st\_mtime)
805 \item {\bf c} compare the change time (st\_ctime)
806 \item {\bf d} report file size decreases
807 \item {\bf 5} compare the MD5 signature
808 \item {\bf 1} compare the SHA1 signature
811 \textbf{Important note:} If you decide to use checksum in Accurate jobs,
812 the File Daemon will have to read all files even if they normally would not
813 be saved. This increases the I/O load, but also the accuracy of the
814 deduplication. By default, Bacula will check modification/creation time
817 This project was funded by Bacula Systems.
819 \section{Tab-completion for Bconsole}
820 \label{sec:tabcompletion}
822 If you build \texttt{bconsole} with readline support, you will be able to use
823 the new auto-completion mode. This mode supports all commands, gives help
824 inside command, and lists resources when required. It works also in the restore
827 To use this feature, you should have readline development package loaded on
828 your system, and use the following option in configure.
830 ./configure --with-readline=/usr/include/readline --disable-conio ...
833 The new bconsole won't be able to tab-complete with older directors.
835 This project was funded by Bacula Systems.
837 \section{Pool File and Job Retention}
838 \label{sec:poolfilejobretention}
840 We added two new Pool directives, \texttt{FileRetention} and
841 \texttt{JobRetention}, that take precedence over Client directives of the same
842 name. It allows you to control the Catalog pruning algorithm Pool by Pool. For
843 example, you can decide to increase Retention times for Archive or OffSite Pool.
845 It seems obvious to us, but apparently not to some users, that given the
846 definition above that the Pool File and Job Retention periods is a global
847 override for the normal Client based prunning, which means that when the
848 Job is prunned, the prunning will apply globally to that particular Job.
850 Currently, there is a bug in the implementation that causes any Pool
851 retention periods specified to apply to {\bf all} Pools for that
852 particular Client. Thus we suggest that you avoid using these two
853 directives until this implementation problem is corrected.
855 \section{Read-only File Daemon using capabilities}
856 \label{sec:fdreadonly}
857 This feature implements support of keeping \textbf{ReadAll} capabilities after
858 UID/GID switch, this allows FD to keep root read but drop write permission.
860 It introduces new \texttt{bacula-fd} option (\texttt{-k}) specifying that
861 \textbf{ReadAll} capabilities should be kept after UID/GID switch.
864 root@localhost:~# bacula-fd -k -u nobody -g nobody
867 The code for this feature was contributed by our friends at AltLinux.
872 To help developers of restore GUI interfaces, we have added new \textsl{dot
873 commands} that permit browsing the catalog in a very simple way.
876 \item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update
877 the Bvfs cache in the catalog. You need to run it before any access to the
880 \item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command
881 will list all directories in the specified \texttt{path} or
882 \texttt{pathid}. Using \texttt{pathid} avoids problems with character
883 encoding of path/filenames.
885 \item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command
886 will list all files in the specified \texttt{path} or \texttt{pathid}. Using
887 \texttt{pathid} avoids problems with character encoding.
890 You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of
891 data that will be displayed.
894 * .bvfs_update jobid=1,2
896 * .bvfs_lsdir path=/ jobid=1,2
899 This project was funded by Bacula Systems.
901 \section{Testing your Tape Drive}
902 \label{sec:btapespeed}
904 To determine the best configuration of your tape drive, you can run the new
905 \texttt{speed} command available in the \texttt{btape} program.
907 This command can have the following arguments:
909 \item[\texttt{file\_size=n}] Specify the Maximum File Size for this test
910 (between 1 and 5GB). This counter is in GB.
911 \item[\texttt{nb\_file=n}] Specify the number of file to be written. The amount
912 of data should be greater than your memory ($file\_size*nb\_file$).
913 \item[\texttt{skip\_zero}] This flag permits to skip tests with constant
915 \item[\texttt{skip\_random}] This flag permits to skip tests with random
917 \item[\texttt{skip\_raw}] This flag permits to skip tests with raw access.
918 \item[\texttt{skip\_block}] This flag permits to skip tests with Bacula block
923 *speed file_size=3 skip_raw
924 btape.c:1078 Test with zero data and bacula block structure.
925 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
926 ++++++++++++++++++++++++++++++++++++++++++
927 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
928 btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 MB/s
930 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 MB/s
932 btape.c:1090 Test with random data, should give the minimum throughput.
933 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
934 +++++++++++++++++++++++++++++++++++++++++++
935 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
936 btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 MB/s
937 +++++++++++++++++++++++++++++++++++++++++++
939 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s
943 When using compression, the random test will give your the minimum throughput
944 of your drive . The test using constant string will give you the maximum speed
945 of your hardware chain. (cpu, memory, scsi card, cable, drive, tape).
947 You can change the block size in the Storage Daemon configuration file.
949 \section{New {\bf Block Checksum} Device Directive}
950 You may now turn off the Block Checksum (CRC32) code
951 that Bacula uses when writing blocks to a Volume. This is
958 doing so can reduce the Storage daemon CPU usage slightly. It
959 will also permit Bacula to read a Volume that has corrupted data.
961 The default is {\bf yes} -- i.e. the checksum is computed on write
964 We do not recommend to turn this off particularly on older tape
965 drives or for disk Volumes where doing so may allow corrupted data
968 \section{New Bat Features}
970 Those new features were funded by Bacula Systems.
972 \subsection{Media List View}
974 By clicking on ``Media'', you can see the list of all your volumes. You will be
975 able to filter by Pool, Media Type, Location,\dots And sort the result directly
976 in the table. The old ``Media'' view is now known as ``Pool''.
979 \includegraphics[width=13cm]{\idir bat-mediaview.eps}
980 \label{fig:mediaview}
984 \subsection{Media Information View}
986 By double-clicking on a volume (on the Media list, in the Autochanger content
987 or in the Job information panel), you can access a detailed overview of your
988 Volume. (cf \ref{fig:mediainfo}.)
991 \includegraphics[width=13cm]{\idir bat11.eps}
992 \caption{Media information}
993 \label{fig:mediainfo}
996 \subsection{Job Information View}
998 By double-clicking on a Job record (on the Job run list or in the Media
999 information panel), you can access a detailed overview of your Job. (cf
1001 \begin{figure}[htbp]
1003 \includegraphics[width=13cm]{\idir bat12.eps}
1004 \caption{Job information}
1008 \subsection{Autochanger Content View}
1010 By double-clicking on a Storage record (on the Storage list panel), you can
1011 access a detailed overview of your Autochanger. (cf \ref{fig:jobinfo}.)
1012 \begin{figure}[htbp]
1014 \includegraphics[width=13cm]{\idir bat13.eps}
1015 \caption{Autochanger content}
1016 \label{fig:achcontent}
1019 To use this feature, you need to use the latest mtx-changer script
1020 version. (With new \texttt{listall} and \texttt{transfer} commands)
1022 \section{Bat on Windows}
1023 We have ported {\bf bat} to Windows and it is now installed
1024 by default when the installer is run. It works quite well
1025 on Win32, but has not had a lot of testing there, so your
1026 feedback would be welcome. Unfortunately, eventhough it is
1027 installed by default, it does not yet work on 64 bit Windows
1030 \section{New Win32 Installer}
1031 The Win32 installer has been modified in several very important
1034 \item You must deinstall any current version of the
1035 Win32 File daemon before upgrading to the new one.
1036 If you forget to do so, the new installation will fail.
1037 To correct this failure, you must manually shutdown
1038 and deinstall the old File daemon.
1039 \item All files (other than menu links) are installed
1040 in {\bf c:/Program Files/Bacula}.
1041 \item The installer no longer sets this
1042 file to require administrator privileges by default. If you want
1043 to do so, please do it manually using the {\bf cacls} program.
1046 cacls "C:\Program Files\Bacula" /T /G SYSTEM:F Administrators:F
1048 \item The server daemons (Director and Storage daemon) are
1049 no longer included in the Windows installer. If you want the
1050 Windows servers, you will either need to build them yourself (note
1051 they have not been ported to 64 bits), or you can contact
1052 Bacula Systems about this.
1055 \section{Win64 Installer}
1056 We have corrected a number of problems that required manual
1057 editing of the conf files. In most cases, it should now
1058 install and work. {\bf bat} is by default installed in
1059 {\bf c:/Program Files/Bacula/bin32} rather than
1060 {\bf c:/Program Files/Bacula} as is the case with the 32
1061 bit Windows installer.
1063 \section{Linux Bare Metal Recovery USB Key}
1064 We have made a number of significant improvements in the
1065 Bare Metal Recovery USB key. Please see the README files
1066 it the {\bf rescue} release for more details.
1068 We are working on an equivalent USB key for Windows bare
1069 metal recovery, but it will take some time to develop it (best
1070 estimate 3Q2010 or 4Q2010)
1073 \section{bconsole Timeout Option}
1074 You can now use the -u option of {\bf bconsole} to set a timeout in seconds
1075 for commands. This is useful with GUI programs that use {\bf bconsole}
1076 to interface to the Director.
1078 \section{Important Changes}
1079 \label{sec:importantchanges}
1082 \item You are now allowed to Migrate, Copy, and Virtual Full to read and write
1083 to the same Pool. The Storage daemon ensures that you do not read and
1084 write to the same Volume.
1085 \item The \texttt{Device Poll Interval} is now 5 minutes. (previously did not
1087 \item Virtually all the features of {\bf mtx-changer} have
1088 now been parameterized, which allows you to configure
1089 mtx-changer without changing it. There is a new configuration file {\bf mtx-changer.conf}
1090 that contains variables that you can set to configure mtx-changer.
1091 This configuration file will not be overwritten during upgrades.
1092 We encourage you to submit any changes
1093 that are made to mtx-changer and to parameterize it all in
1094 mtx-changer.conf so that all configuration will be done by
1095 changing only mtx-changer.conf.
1096 \item The new \texttt{mtx-changer} script has two new options, \texttt{listall}
1097 and \texttt{transfer}. Please configure them as appropriate
1098 in mtx-changer.conf.
1099 \item To enhance security of the \texttt{BackupCatalog} job, we provide a new
1100 script (\texttt{make\_catalog\_backup.pl}) that does not expose your catalog
1101 password. If you want to use the new script, you will need to
1102 manually change the \texttt{BackupCatalog} Job definition.
1103 \item The \texttt{bconsole} \texttt{help} command now accepts
1104 an argument, which if provided produces information on that
1105 command (ex: \texttt{help run}).
1109 \subsubsection*{Truncate volume after purge}
1111 Note that the Truncate Volume after purge feature doesn't work as expected
1112 in 5.0.0 version. Please, don't use it before version 5.0.1.
1114 \subsection{Custom Catalog queries}
1116 If you wish to add specialized commands that list the contents of the catalog,
1117 you can do so by adding them to the \texttt{query.sql} file. This
1118 \texttt{query.sql} file is now empty by default. The file
1119 \texttt{examples/sample-query.sql} has an a number of sample commands
1120 you might find useful.
1122 \subsection{Deprecated parts}
1124 The following items have been \textbf{deprecated} for a long time, and are now
1125 removed from the code.
1128 \item Support for SQLite 2
1131 \section{Misc Changes}
1132 \label{sec:miscchanges}
1135 \item Updated Nagios check\_bacula
1136 \item Updated man files
1137 \item Added OSX package generation script in platforms/darwin
1138 \item Added Spanish and Ukrainian Bacula translations
1139 \item Enable/disable command shows only Jobs that can change
1140 \item Added \texttt{show disabled} command to show disabled Jobs
1141 \item Many ACL improvements
1142 \item Added Level to FD status Job output
1143 \item Begin Ingres DB driver (not yet working)
1144 \item Split RedHat spec files into bacula, bat, mtx, and docs
1145 \item Reorganized the manuals (fewer separate manuals)
1146 \item Added lock/unlock order protection in lock manager
1147 \item Allow 64 bit sizes for a number of variables
1148 \item Fixed several deadlocks or potential race conditions in the SD
1151 \chapter{Released Version 3.0.3 and 3.0.3a}
1153 There are no new features in version 3.0.3. This version simply fixes a
1154 number of bugs found in version 3.0.2 during the onging development
1157 \chapter{New Features in Released Version 3.0.2}
1159 This chapter presents the new features added to the
1160 Released Bacula Version 3.0.2.
1162 \section{Full Restore from a Given JobId}
1163 \index[general]{Restore menu}
1165 This feature allows selecting a single JobId and having Bacula
1166 automatically select all the other jobs that comprise a full backup up to
1167 and including the selected date (through JobId).
1169 Assume we start with the following jobs:
1171 +-------+--------------+---------------------+-------+----------+------------+
1172 | jobid | client | starttime | level | jobfiles | jobbytes |
1173 +-------+--------------+---------------------+-------+----------+------------
1174 | 6 | localhost-fd | 2009-07-15 11:45:49 | I | 2 | 0 |
1175 | 5 | localhost-fd | 2009-07-15 11:45:45 | I | 15 | 44143 |
1176 | 3 | localhost-fd | 2009-07-15 11:45:38 | I | 1 | 10 |
1177 | 1 | localhost-fd | 2009-07-15 11:45:30 | F | 1527 | 44143073 |
1178 +-------+--------------+---------------------+-------+----------+------------+
1181 Below is an example of this new feature (which is number 12 in the
1186 To select the JobIds, you have the following choices:
1187 1: List last 20 Jobs run
1188 2: List Jobs where a given File is saved
1190 12: Select full restore to a specified Job date
1193 Select item: (1-13): 12
1194 Enter JobId to get the state to restore: 5
1195 Selecting jobs to build the Full state at 2009-07-15 11:45:45
1196 You have selected the following JobIds: 1,3,5
1198 Building directory tree for JobId(s) 1,3,5 ... +++++++++++++++++++
1199 1,444 files inserted into the tree.
1202 This project was funded by Bacula Systems.
1204 \section{Source Address}
1205 \index[general]{Source Address}
1207 A feature has been added which allows the administrator to specify the address
1208 from which the Director and File daemons will establish connections. This
1209 may be used to simplify system configuration overhead when working in complex
1210 networks utilizing multi-homing and policy-routing.
1212 To accomplish this, two new configuration directives have been implemented:
1215 FDSourceAddress=10.0.1.20 # Always initiate connections from this address
1219 DirSourceAddress=10.0.1.10 # Always initiate connections from this address
1223 Simply adding specific host routes on the OS
1224 would have an undesirable side-effect: any
1225 application trying to contact the destination host would be forced to use the
1226 more specific route possibly diverting management traffic onto a backup VLAN.
1227 Instead of adding host routes for each client connected to a multi-homed backup
1228 server (for example where there are management and backup VLANs), one can
1229 use the new directives to specify a specific source address at the application
1232 Additionally, this allows the simplification and abstraction of firewall rules
1233 when dealing with a Hot-Standby director or storage daemon configuration. The
1234 Hot-standby pair may share a CARP address, which connections must be sourced
1235 from, while system services listen and act from the unique interface addresses.
1237 This project was funded by Collaborative Fusion, Inc.
1239 \section{Show volume availability when doing restore}
1241 When doing a restore the selection dialog ends by displaying this
1245 The job will require the following
1246 Volume(s) Storage(s) SD Device(s)
1247 ===========================================================================
1248 *000741L3 LTO-4 LTO3
1249 *000866L3 LTO-4 LTO3
1250 *000765L3 LTO-4 LTO3
1251 *000764L3 LTO-4 LTO3
1252 *000756L3 LTO-4 LTO3
1253 *001759L3 LTO-4 LTO3
1254 *001763L3 LTO-4 LTO3
1258 Volumes marked with ``*'' are online (in the autochanger).
1261 This should help speed up large restores by minimizing the time spent
1262 waiting for the operator to discover that he must change tapes in the library.
1264 This project was funded by Bacula Systems.
1266 \section{Accurate estimate command}
1268 The \texttt{estimate} command can now use the accurate code to detect changes
1269 and give a better estimation.
1271 You can set the accurate behavior on the command line by using
1272 \texttt{accurate=yes\vb{}no} or use the Job setting as default value.
1275 * estimate listing accurate=yes level=incremental job=BackupJob
1278 This project was funded by Bacula Systems.
1280 \chapter{New Features in 3.0.0}
1281 \label{NewFeaturesChapter}
1282 \index[general]{New Features}
1284 This chapter presents the new features added to the development 2.5.x
1285 versions to be released as Bacula version 3.0.0 sometime in April 2009.
1287 \section{Accurate Backup}
1288 \index[general]{Accurate Backup}
1290 As with most other backup programs, by default Bacula decides what files to
1291 backup for Incremental and Differental backup by comparing the change
1292 (st\_ctime) and modification (st\_mtime) times of the file to the time the last
1293 backup completed. If one of those two times is later than the last backup
1294 time, then the file will be backed up. This does not, however, permit tracking
1295 what files have been deleted and will miss any file with an old time that may
1296 have been restored to or moved onto the client filesystem.
1298 \subsection{Accurate = \lt{}yes\vb{}no\gt{}}
1299 If the {\bf Accurate = \lt{}yes\vb{}no\gt{}} directive is enabled (default no) in
1300 the Job resource, the job will be run as an Accurate Job. For a {\bf Full}
1301 backup, there is no difference, but for {\bf Differential} and {\bf
1302 Incremental} backups, the Director will send a list of all previous files
1303 backed up, and the File daemon will use that list to determine if any new files
1304 have been added or or moved and if any files have been deleted. This allows
1305 Bacula to make an accurate backup of your system to that point in time so that
1306 if you do a restore, it will restore your system exactly.
1309 about using Accurate backup is that it requires more resources (CPU and memory)
1310 on both the Director and the Client machines to create the list of previous
1311 files backed up, to send that list to the File daemon, for the File daemon to
1312 keep the list (possibly very big) in memory, and for the File daemon to do
1313 comparisons between every file in the FileSet and the list. In particular,
1314 if your client has lots of files (more than a few million), you will need
1315 lots of memory on the client machine.
1317 Accurate must not be enabled when backing up with a plugin that is not
1318 specially designed to work with Accurate. If you enable it, your restores
1319 will probably not work correctly.
1321 This project was funded by Bacula Systems.
1326 \index[general]{Copy Jobs}
1328 A new {\bf Copy} job type 'C' has been implemented. It is similar to the
1329 existing Migration feature with the exception that the Job that is copied is
1330 left unchanged. This essentially creates two identical copies of the same
1331 backup. However, the copy is treated as a copy rather than a backup job, and
1332 hence is not directly available for restore. The {\bf restore} command lists
1333 copy jobs and allows selection of copies by using \texttt{jobid=}
1334 option. If the keyword {\bf copies} is present on the command line, Bacula will
1335 display the list of all copies for selected jobs.
1340 These JobIds have copies as follows:
1341 +-------+------------------------------------+-----------+------------------+
1342 | JobId | Job | CopyJobId | MediaType |
1343 +-------+------------------------------------+-----------+------------------+
1344 | 2 | CopyJobSave.2009-02-17_16.31.00.11 | 7 | DiskChangerMedia |
1345 +-------+------------------------------------+-----------+------------------+
1346 +-------+-------+----------+----------+---------------------+------------------+
1347 | JobId | Level | JobFiles | JobBytes | StartTime | VolumeName |
1348 +-------+-------+----------+----------+---------------------+------------------+
1349 | 19 | F | 6274 | 76565018 | 2009-02-17 16:30:45 | ChangerVolume002 |
1350 | 2 | I | 1 | 5 | 2009-02-17 16:30:51 | FileVolume001 |
1351 +-------+-------+----------+----------+---------------------+------------------+
1352 You have selected the following JobIds: 19,2
1354 Building directory tree for JobId(s) 19,2 ... ++++++++++++++++++++++++++++++++++++++++++++
1355 5,611 files inserted into the tree.
1360 The Copy Job runs without using the File daemon by copying the data from the
1361 old backup Volume to a different Volume in a different Pool. See the Migration
1362 documentation for additional details. For copy Jobs there is a new selection
1363 directive named {\bf PoolUncopiedJobs} which selects all Jobs that were
1364 not already copied to another Pool.
1366 As with Migration, the Client, Volume, Job, or SQL query, are
1367 other possible ways of selecting the Jobs to be copied. Selection
1368 types like SmallestVolume, OldestVolume, PoolOccupancy and PoolTime also
1369 work, but are probably more suited for Migration Jobs.
1371 If Bacula finds a Copy of a job record that is purged (deleted) from the catalog,
1372 it will promote the Copy to a \textsl{real} backup job and will make it available for
1373 automatic restore. If more than one Copy is available, it will promote the copy
1374 with the smallest JobId.
1376 A nice solution which can be built with the new Copy feature is often
1377 called disk-to-disk-to-tape backup (DTDTT). A sample config could
1378 look something like the one below:
1382 Name = FullBackupsVirtualPool
1384 Purge Oldest Volume = Yes
1386 NextPool = FullBackupsTapePool
1390 Name = FullBackupsTapePool
1394 Volume Retention = 365 days
1395 Storage = superloader
1399 # Fake fileset for copy jobs
1411 # Fake client for copy jobs
1421 # Default template for a CopyDiskToTape Job
1424 Name = CopyDiskToTape
1426 Messages = StandardCopy
1429 Selection Type = PoolUncopiedJobs
1430 Maximum Concurrent Jobs = 10
1432 Allow Duplicate Jobs = Yes
1433 Cancel Queued Duplicates = No
1434 Cancel Running Duplicates = No
1439 Name = DaySchedule7:00
1440 Run = Level=Full daily at 7:00
1444 Name = CopyDiskToTapeFullBackups
1446 Schedule = DaySchedule7:00
1447 Pool = FullBackupsVirtualPool
1448 JobDefs = CopyDiskToTape
1452 The example above had 2 pool which are copied using the PoolUncopiedJobs
1453 selection criteria. Normal Full backups go to the Virtual pool and are copied
1454 to the Tape pool the next morning.
1456 The command \texttt{list copies [jobid=x,y,z]} lists copies for a given
1461 +-------+------------------------------------+-----------+------------------+
1462 | JobId | Job | CopyJobId | MediaType |
1463 +-------+------------------------------------+-----------+------------------+
1464 | 9 | CopyJobSave.2008-12-20_22.26.49.05 | 11 | DiskChangerMedia |
1465 +-------+------------------------------------+-----------+------------------+
1468 \section{ACL Updates}
1469 \index[general]{ACL Updates}
1470 The whole ACL code had been overhauled and in this version each platforms has
1471 different streams for each type of acl available on such an platform. As ACLs
1472 between platforms tend to be not that portable (most implement POSIX acls but
1473 some use an other draft or a completely different format) we currently only
1474 allow certain platform specific ACL streams to be decoded and restored on the
1475 same platform that they were created on. The old code allowed to restore ACL
1476 cross platform but the comments already mention that not being to wise. For
1477 backward compatability the new code will accept the two old ACL streams and
1478 handle those with the platform specific handler. But for all new backups it
1479 will save the ACLs using the new streams.
1481 Currently the following platforms support ACLs:
1485 \item {\bf Darwin/OSX}
1494 Currently we support the following ACL types (these ACL streams use a reserved
1495 part of the stream numbers):
1498 \item {\bf STREAM\_ACL\_AIX\_TEXT} 1000 AIX specific string representation from
1500 \item {\bf STREAM\_ACL\_DARWIN\_ACCESS\_ACL} 1001 Darwin (OSX) specific acl\_t
1501 string representation from acl\_to\_text (POSIX acl)
1502 \item {\bf STREAM\_ACL\_FREEBSD\_DEFAULT\_ACL} 1002 FreeBSD specific acl\_t
1503 string representation from acl\_to\_text (POSIX acl) for default acls.
1504 \item {\bf STREAM\_ACL\_FREEBSD\_ACCESS\_ACL} 1003 FreeBSD specific acl\_t
1505 string representation from acl\_to\_text (POSIX acl) for access acls.
1506 \item {\bf STREAM\_ACL\_HPUX\_ACL\_ENTRY} 1004 HPUX specific acl\_entry
1507 string representation from acltostr (POSIX acl)
1508 \item {\bf STREAM\_ACL\_IRIX\_DEFAULT\_ACL} 1005 IRIX specific acl\_t string
1509 representation from acl\_to\_text (POSIX acl) for default acls.
1510 \item {\bf STREAM\_ACL\_IRIX\_ACCESS\_ACL} 1006 IRIX specific acl\_t string
1511 representation from acl\_to\_text (POSIX acl) for access acls.
1512 \item {\bf STREAM\_ACL\_LINUX\_DEFAULT\_ACL} 1007 Linux specific acl\_t
1513 string representation from acl\_to\_text (POSIX acl) for default acls.
1514 \item {\bf STREAM\_ACL\_LINUX\_ACCESS\_ACL} 1008 Linux specific acl\_t string
1515 representation from acl\_to\_text (POSIX acl) for access acls.
1516 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_ACL} 1009 Tru64 specific acl\_t
1517 string representation from acl\_to\_text (POSIX acl) for default acls.
1518 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_DIR\_ACL} 1010 Tru64 specific acl\_t
1519 string representation from acl\_to\_text (POSIX acl) for default acls.
1520 \item {\bf STREAM\_ACL\_TRU64\_ACCESS\_ACL} 1011 Tru64 specific acl\_t string
1521 representation from acl\_to\_text (POSIX acl) for access acls.
1522 \item {\bf STREAM\_ACL\_SOLARIS\_ACLENT} 1012 Solaris specific aclent\_t
1523 string representation from acltotext or acl\_totext (POSIX acl)
1524 \item {\bf STREAM\_ACL\_SOLARIS\_ACE} 1013 Solaris specific ace\_t string
1525 representation from from acl\_totext (NFSv4 or ZFS acl)
1528 In future versions we might support conversion functions from one type of acl
1529 into an other for types that are either the same or easily convertable. For now
1530 the streams are seperate and restoring them on a platform that doesn't
1531 recognize them will give you a warning.
1533 \section{Extended Attributes}
1534 \index[general]{Extended Attributes}
1535 Something that was on the project list for some time is now implemented for
1536 platforms that support a similar kind of interface. Its the support for backup
1537 and restore of so called extended attributes. As extended attributes are so
1538 platform specific these attributes are saved in seperate streams for each
1539 platform. Restores of the extended attributes can only be performed on the
1540 same platform the backup was done. There is support for all types of extended
1541 attributes, but restoring from one type of filesystem onto an other type of
1542 filesystem on the same platform may lead to supprises. As extended attributes
1543 can contain any type of data they are stored as a series of so called
1544 value-pairs. This data must be seen as mostly binary and is stored as such.
1545 As security labels from selinux are also extended attributes this option also
1546 stores those labels and no specific code is enabled for handling selinux
1549 Currently the following platforms support extended attributes:
1551 \item {\bf Darwin/OSX}
1557 On linux acls are also extended attributes, as such when you enable ACLs on a
1558 Linux platform it will NOT save the same data twice e.g. it will save the ACLs
1559 and not the same exteneded attribute.
1561 To enable the backup of extended attributes please add the following to your
1576 \section{Shared objects}
1577 \index[general]{Shared objects}
1578 A default build of Bacula will now create the libraries as shared objects
1579 (.so) rather than static libraries as was previously the case.
1580 The shared libraries are built using {\bf libtool} so it should be quite
1583 An important advantage of using shared objects is that on a machine with the
1584 Directory, File daemon, the Storage daemon, and a console, you will have only
1585 one copy of the code in memory rather than four copies. Also the total size of
1586 the binary release is smaller since the library code appears only once rather
1587 than once for every program that uses it; this results in significant reduction
1588 in the size of the binaries particularly for the utility tools.
1590 In order for the system loader to find the shared objects when loading the
1591 Bacula binaries, the Bacula shared objects must either be in a shared object
1592 directory known to the loader (typically /usr/lib) or they must be in the
1593 directory that may be specified on the {\bf ./configure} line using the {\bf
1594 {-}{-}libdir} option as:
1597 ./configure --libdir=/full-path/dir
1600 the default is /usr/lib. If {-}{-}libdir is specified, there should be
1601 no need to modify your loader configuration provided that
1602 the shared objects are installed in that directory (Bacula
1603 does this with the make install command). The shared objects
1604 that Bacula references are:
1613 These files are symbolically linked to the real shared object file,
1614 which has a version number to permit running multiple versions of
1615 the libraries if desired (not normally the case).
1617 If you have problems with libtool or you wish to use the old
1618 way of building static libraries, or you want to build a static
1619 version of Bacula you may disable
1620 libtool on the configure command line with:
1623 ./configure --disable-libtool
1627 \section{Building Static versions of Bacula}
1628 \index[general]{Static linking}
1629 In order to build static versions of Bacula, in addition
1630 to configuration options that were needed you now must
1631 also add --disable-libtool. Example
1634 ./configure --enable-static-client-only --disable-libtool
1638 \section{Virtual Backup (Vbackup)}
1639 \index[general]{Virtual Backup}
1640 \index[general]{Vbackup}
1642 Bacula's virtual backup feature is often called Synthetic Backup or
1643 Consolidation in other backup products. It permits you to consolidate the
1644 previous Full backup plus the most recent Differential backup and any
1645 subsequent Incremental backups into a new Full backup. This new Full
1646 backup will then be considered as the most recent Full for any future
1647 Incremental or Differential backups. The VirtualFull backup is
1648 accomplished without contacting the client by reading the previous backup
1649 data and writing it to a volume in a different pool.
1651 In some respects the Vbackup feature works similar to a Migration job, in
1652 that Bacula normally reads the data from the pool specified in the
1653 Job resource, and writes it to the {\bf Next Pool} specified in the
1654 Job resource. Note, this means that usually the output from the Virtual
1655 Backup is written into a different pool from where your prior backups
1656 are saved. Doing it this way guarantees that you will not get a deadlock
1657 situation attempting to read and write to the same volume in the Storage
1658 daemon. If you then want to do subsequent backups, you may need to
1659 move the Virtual Full Volume back to your normal backup pool.
1660 Alternatively, you can set your {\bf Next Pool} to point to the current
1661 pool. This will cause Bacula to read and write to Volumes in the
1662 current pool. In general, this will work, because Bacula will
1663 not allow reading and writing on the same Volume. In any case, once
1664 a VirtualFull has been created, and a restore is done involving the
1665 most current Full, it will read the Volume or Volumes by the VirtualFull
1666 regardless of in which Pool the Volume is found.
1668 The Vbackup is enabled on a Job by Job in the Job resource by specifying
1669 a level of {\bf VirtualFull}.
1671 A typical Job resource definition might look like the following:
1678 FileSet = "Full Set"
1685 # Default pool definition
1689 Recycle = yes # Automatically recycle Volumes
1690 AutoPrune = yes # Prune expired volumes
1691 Volume Retention = 365d # one year
1699 Recycle = yes # Automatically recycle Volumes
1700 AutoPrune = yes # Prune expired volumes
1701 Volume Retention = 365d # one year
1702 Storage = DiskChanger
1705 # Definition of file storage device
1710 Device = FileStorage
1712 Maximum Concurrent Jobs = 5
1715 # Definition of DDS Virtual tape disk storage device
1718 Address = localhost # N.B. Use a fully qualified name here
1720 Device = DiskChanger
1721 Media Type = DiskChangerMedia
1722 Maximum Concurrent Jobs = 4
1727 Then in bconsole or via a Run schedule, you would run the job as:
1730 run job=MyBackup level=Full
1731 run job=MyBackup level=Incremental
1732 run job=MyBackup level=Differential
1733 run job=MyBackup level=Incremental
1734 run job=MyBackup level=Incremental
1737 So providing there were changes between each of those jobs, you would end up
1738 with a Full backup, a Differential, which includes the first Incremental
1739 backup, then two Incremental backups. All the above jobs would be written to
1740 the {\bf Default} pool.
1742 To consolidate those backups into a new Full backup, you would run the
1746 run job=MyBackup level=VirtualFull
1749 And it would produce a new Full backup without using the client, and the output
1750 would be written to the {\bf Full} Pool which uses the Diskchanger Storage.
1752 If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
1755 Note, the Start and End time of the Virtual Full backup is set to the
1756 values for the last job included in the Virtual Full (in the above example,
1757 it is an Increment). This is so that if another incremental is done, which
1758 will be based on the Virtual Full, it will backup all files from the
1759 last Job included in the Virtual Full rather than from the time the Virtual
1760 Full was actually run.
1764 \section{Catalog Format}
1765 \index[general]{Catalog Format}
1766 Bacula 3.0 comes with some changes to the catalog format. The upgrade
1767 operation will convert the FileId field of the File table from 32 bits (max 4
1768 billion table entries) to 64 bits (very large number of items). The
1769 conversion process can take a bit of time and will likely DOUBLE THE SIZE of
1770 your catalog during the conversion. Also you won't be able to run jobs during
1771 this conversion period. For example, a 3 million file catalog will take 2
1772 minutes to upgrade on a normal machine. Please don't forget to make a valid
1773 backup of your database before executing the upgrade script. See the
1774 ReleaseNotes for additional details.
1776 \section{64 bit Windows Client}
1777 \index[general]{Win64 Client}
1778 Unfortunately, Microsoft's implementation of Volume Shadown Copy (VSS) on
1779 their 64 bit OS versions is not compatible with a 32 bit Bacula Client.
1780 As a consequence, we are also releasing a 64 bit version of the Bacula
1781 Windows Client (win64bacula-3.0.0.exe) that does work with VSS.
1782 These binaries should only be installed on 64 bit Windows operating systems.
1783 What is important is not your hardware but whether or not you have
1784 a 64 bit version of the Windows OS.
1786 Compared to the Win32 Bacula Client, the 64 bit release contains a few differences:
1788 \item Before installing the Win64 Bacula Client, you must totally
1789 deinstall any prior 2.4.x Client installation using the
1790 Bacula deinstallation (see the menu item). You may want
1791 to save your .conf files first.
1792 \item Only the Client (File daemon) is ported to Win64, the Director
1793 and the Storage daemon are not in the 64 bit Windows installer.
1794 \item bwx-console is not yet ported.
1795 \item bconsole is ported but it has not been tested.
1796 \item The documentation is not included in the installer.
1797 \item Due to Vista security restrictions imposed on a default installation
1798 of Vista, before upgrading the Client, you must manually stop
1799 any prior version of Bacula from running, otherwise the install
1801 \item Due to Vista security restrictions imposed on a default installation
1802 of Vista, attempting to edit the conf files via the menu items
1803 will fail. You must directly edit the files with appropriate
1804 permissions. Generally double clicking on the appropriate .conf
1805 file will work providing you have sufficient permissions.
1806 \item All Bacula files are now installed in
1807 {\bf C:/Program Files/Bacula} except the main menu items,
1808 which are installed as before. This vastly simplifies the installation.
1809 \item If you are running on a foreign language version of Windows, most
1810 likely {\bf C:/Program Files} does not exist, so you should use the
1811 Custom installation and enter an appropriate location to install
1813 \item The 3.0.0 Win32 Client continues to install files in the locations used
1814 by prior versions. For the next version we will convert it to use
1815 the same installation conventions as the Win64 version.
1818 This project was funded by Bacula Systems.
1821 \section{Duplicate Job Control}
1822 \index[general]{Duplicate Jobs}
1823 The new version of Bacula provides four new directives that
1824 give additional control over what Bacula does if duplicate jobs
1825 are started. A duplicate job in the sense we use it here means
1826 a second or subsequent job with the same name starts. This
1827 happens most frequently when the first job runs longer than expected because no
1828 tapes are available.
1830 The four directives each take as an argument a {\bf yes} or {\bf no} value and
1831 are specified in the Job resource.
1835 \subsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}}
1836 \index[general]{Allow Duplicate Jobs}
1837 If this directive is set to {\bf yes}, duplicate jobs will be run. If
1838 the directive is set to {\bf no} (default) then only one job of a given name
1839 may run at one time, and the action that Bacula takes to ensure only
1840 one job runs is determined by the other directives (see below).
1842 If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs
1843 are present and none of the three directives given below permit
1844 cancelling a job, then the current job (the second one started)
1847 \subsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}}
1848 \index[general]{Allow Higher Duplicates}
1849 This directive was in version 5.0.0, but does not work as
1850 expected. If used, it should always be set to no. In later versions
1851 of Bacula the directive is disabled (disregarded).
1853 \subsection{Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}}
1854 \index[general]{Cancel Running Duplicates}
1855 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1856 if this directive is set to {\bf yes} any job that is already running
1857 will be canceled. The default is {\bf no}.
1859 \subsection{Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}}
1860 \index[general]{Cancel Queued Duplicates}
1861 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1862 if this directive is set to {\bf yes} any job that is
1863 already queued to run but not yet running will be canceled.
1864 The default is {\bf no}.
1867 \section{TLS Authentication}
1868 \index[general]{TLS Authentication}
1869 In Bacula version 2.5.x and later, in addition to the normal Bacula
1870 CRAM-MD5 authentication that is used to authenticate each Bacula
1871 connection, you can specify that you want TLS Authentication as well,
1872 which will provide more secure authentication.
1874 This new feature uses Bacula's existing TLS code (normally used for
1875 communications encryption) to do authentication. To use it, you must
1876 specify all the TLS directives normally used to enable communications
1877 encryption (TLS Enable, TLS Verify Peer, TLS Certificate, ...) and
1880 \subsection{TLS Authenticate = yes}
1882 TLS Authenticate = yes
1885 in the main daemon configuration resource (Director for the Director,
1886 Client for the File daemon, and Storage for the Storage daemon).
1888 When {\bf TLS Authenticate} is enabled, after doing the CRAM-MD5
1889 authentication, Bacula will also do TLS authentication, then TLS
1890 encryption will be turned off, and the rest of the communication between
1891 the two Bacula daemons will be done without encryption.
1893 If you want to encrypt communications data, use the normal TLS directives
1894 but do not turn on {\bf TLS Authenticate}.
1896 \section{bextract non-portable Win32 data}
1897 \index[general]{bextract handles Win32 non-portable data}
1898 {\bf bextract} has been enhanced to be able to restore
1899 non-portable Win32 data to any OS. Previous versions were
1900 unable to restore non-portable Win32 data to machines that
1901 did not have the Win32 BackupRead and BackupWrite API calls.
1903 \section{State File updated at Job Termination}
1904 \index[general]{State File}
1905 In previous versions of Bacula, the state file, which provides a
1906 summary of previous jobs run in the {\bf status} command output was
1907 updated only when Bacula terminated, thus if the daemon crashed, the
1908 state file might not contain all the run data. This version of
1909 the Bacula daemons updates the state file on each job termination.
1911 \section{MaxFullInterval = \lt{}time-interval\gt{}}
1912 \index[general]{MaxFullInterval}
1913 The new Job resource directive {\bf Max Full Interval = \lt{}time-interval\gt{}}
1914 can be used to specify the maximum time interval between {\bf Full} backup
1915 jobs. When a job starts, if the time since the last Full backup is
1916 greater than the specified interval, and the job would normally be an
1917 {\bf Incremental} or {\bf Differential}, it will be automatically
1918 upgraded to a {\bf Full} backup.
1920 \section{MaxDiffInterval = \lt{}time-interval\gt{}}
1921 \index[general]{MaxDiffInterval}
1922 The new Job resource directive {\bf Max Diff Interval = \lt{}time-interval\gt{}}
1923 can be used to specify the maximum time interval between {\bf Differential} backup
1924 jobs. When a job starts, if the time since the last Differential backup is
1925 greater than the specified interval, and the job would normally be an
1926 {\bf Incremental}, it will be automatically
1927 upgraded to a {\bf Differential} backup.
1929 \section{Honor No Dump Flag = \lt{}yes\vb{}no\gt{}}
1930 \index[general]{MaxDiffInterval}
1931 On FreeBSD systems, each file has a {\bf no dump flag} that can be set
1932 by the user, and when it is set it is an indication to backup programs
1933 to not backup that particular file. This version of Bacula contains a
1934 new Options directive within a FileSet resource, which instructs Bacula to
1935 obey this flag. The new directive is:
1938 Honor No Dump Flag = yes\vb{}no
1941 The default value is {\bf no}.
1944 \section{Exclude Dir Containing = \lt{}filename-string\gt{}}
1945 \index[general]{IgnoreDir}
1946 The {\bf ExcludeDirContaining = \lt{}filename\gt{}} is a new directive that
1947 can be added to the Include section of the FileSet resource. If the specified
1948 filename ({\bf filename-string}) is found on the Client in any directory to be
1949 backed up, the whole directory will be ignored (not backed up). For example:
1952 # List of files to be backed up
1960 Exclude Dir Containing = .excludeme
1965 But in /home, there may be hundreds of directories of users and some
1966 people want to indicate that they don't want to have certain
1967 directories backed up. For example, with the above FileSet, if
1968 the user or sysadmin creates a file named {\bf .excludeme} in
1969 specific directories, such as
1972 /home/user/www/cache/.excludeme
1973 /home/user/temp/.excludeme
1976 then Bacula will not backup the two directories named:
1979 /home/user/www/cache
1983 NOTE: subdirectories will not be backed up. That is, the directive
1984 applies to the two directories in question and any children (be they
1985 files, directories, etc).
1988 \section{Bacula Plugins}
1989 \index[general]{Plugin}
1990 Support for shared object plugins has been implemented in the Linux, Unix
1991 and Win32 File daemons. The API will be documented separately in
1992 the Developer's Guide or in a new document. For the moment, there is
1993 a single plugin named {\bf bpipe} that allows an external program to
1994 get control to backup and restore a file.
1996 Plugins are also planned (partially implemented) in the Director and the
1999 \subsection{Plugin Directory}
2000 \index[general]{Plugin Directory}
2001 Each daemon (DIR, FD, SD) has a new {\bf Plugin Directory} directive that may
2002 be added to the daemon definition resource. The directory takes a quoted
2003 string argument, which is the name of the directory in which the daemon can
2004 find the Bacula plugins. If this directive is not specified, Bacula will not
2005 load any plugins. Since each plugin has a distinctive name, all the daemons
2006 can share the same plugin directory.
2008 \subsection{Plugin Options}
2009 \index[general]{Plugin Options}
2010 The {\bf Plugin Options} directive takes a quoted string
2011 arguement (after the equal sign) and may be specified in the
2012 Job resource. The options specified will be passed to all plugins
2013 when they are run. This each plugin must know what it is looking
2014 for. The value defined in the Job resource can be modified
2015 by the user when he runs a Job via the {\bf bconsole} command line
2018 Note: this directive may be specified, and there is code to modify
2019 the string in the run command, but the plugin options are not yet passed to
2020 the plugin (i.e. not fully implemented).
2022 \subsection{Plugin Options ACL}
2023 \index[general]{Plugin Options ACL}
2024 The {\bf Plugin Options ACL} directive may be specified in the
2025 Director's Console resource. It functions as all the other ACL commands
2026 do by permitting users running restricted consoles to specify a
2027 {\bf Plugin Options} that overrides the one specified in the Job
2028 definition. Without this directive restricted consoles may not modify
2031 \subsection{Plugin = \lt{}plugin-command-string\gt{}}
2032 \index[general]{Plugin}
2033 The {\bf Plugin} directive is specified in the Include section of
2034 a FileSet resource where you put your {\bf File = xxx} directives.
2045 Plugin = "bpipe:..."
2050 In the above example, when the File daemon is processing the directives
2051 in the Include section, it will first backup all the files in {\bf /home}
2052 then it will load the plugin named {\bf bpipe} (actually bpipe-dir.so) from
2053 the Plugin Directory. The syntax and semantics of the Plugin directive
2054 require the first part of the string up to the colon (:) to be the name
2055 of the plugin. Everything after the first colon is ignored by the File daemon but
2056 is passed to the plugin. Thus the plugin writer may define the meaning of the
2057 rest of the string as he wishes.
2059 Please see the next section for information about the {\bf bpipe} Bacula
2062 \section{The bpipe Plugin}
2063 \index[general]{The bpipe Plugin}
2064 The {\bf bpipe} plugin is provided in the directory src/plugins/fd/bpipe-fd.c of
2065 the Bacula source distribution. When the plugin is compiled and linking into
2066 the resulting dynamic shared object (DSO), it will have the name {\bf bpipe-fd.so}.
2067 Please note that this is a very simple plugin that was written for
2068 demonstration and test purposes. It is and can be used in production, but
2069 that was never really intended.
2071 The purpose of the plugin is to provide an interface to any system program for
2072 backup and restore. As specified above the {\bf bpipe} plugin is specified in
2073 the Include section of your Job's FileSet resource. The full syntax of the
2074 plugin directive as interpreted by the {\bf bpipe} plugin (each plugin is free
2075 to specify the sytax as it wishes) is:
2078 Plugin = "<field1>:<field2>:<field3>:<field4>"
2083 \item {\bf field1} is the name of the plugin with the trailing {\bf -fd.so}
2084 stripped off, so in this case, we would put {\bf bpipe} in this field.
2086 \item {\bf field2} specifies the namespace, which for {\bf bpipe} is the
2087 pseudo path and filename under which the backup will be saved. This pseudo
2088 path and filename will be seen by the user in the restore file tree.
2089 For example, if the value is {\bf /MYSQL/regress.sql}, the data
2090 backed up by the plugin will be put under that "pseudo" path and filename.
2091 You must be careful to choose a naming convention that is unique to avoid
2092 a conflict with a path and filename that actually exists on your system.
2094 \item {\bf field3} for the {\bf bpipe} plugin
2095 specifies the "reader" program that is called by the plugin during
2096 backup to read the data. {\bf bpipe} will call this program by doing a
2099 \item {\bf field4} for the {\bf bpipe} plugin
2100 specifies the "writer" program that is called by the plugin during
2101 restore to write the data back to the filesystem.
2104 Please note that for two items above describing the "reader" and "writer"
2105 fields, these programs are "executed" by Bacula, which
2106 means there is no shell interpretation of any command line arguments
2107 you might use. If you want to use shell characters (redirection of input
2108 or output, ...), then we recommend that you put your command or commands
2109 in a shell script and execute the script. In addition if you backup a
2110 file with the reader program, when running the writer program during
2111 the restore, Bacula will not automatically create the path to the file.
2112 Either the path must exist, or you must explicitly do so with your command
2113 or in a shell script.
2115 Putting it all together, the full plugin directive line might look
2119 Plugin = "bpipe:/MYSQL/regress.sql:mysqldump -f
2120 --opt --databases bacula:mysql"
2123 The directive has been split into two lines, but within the {\bf bacula-dir.conf} file
2124 would be written on a single line.
2126 This causes the File daemon to call the {\bf bpipe} plugin, which will write
2127 its data into the "pseudo" file {\bf /MYSQL/regress.sql} by calling the
2128 program {\bf mysqldump -f --opt --database bacula} to read the data during
2129 backup. The mysqldump command outputs all the data for the database named
2130 {\bf bacula}, which will be read by the plugin and stored in the backup.
2131 During restore, the data that was backed up will be sent to the program
2132 specified in the last field, which in this case is {\bf mysql}. When
2133 {\bf mysql} is called, it will read the data sent to it by the plugn
2134 then write it back to the same database from which it came ({\bf bacula}
2137 The {\bf bpipe} plugin is a generic pipe program, that simply transmits
2138 the data from a specified program to Bacula for backup, and then from Bacula to
2139 a specified program for restore.
2141 By using different command lines to {\bf bpipe},
2142 you can backup any kind of data (ASCII or binary) depending
2143 on the program called.
2145 \section{Microsoft Exchange Server 2003/2007 Plugin}
2146 \index[general]{Microsoft Exchange Server 2003/2007 Plugin}
2147 \subsection{Background}
2148 The Exchange plugin was made possible by a funded development project
2149 between Equiinet Ltd -- www.equiinet.com (many thanks) and Bacula Systems.
2150 The code for the plugin was written by James Harper, and the Bacula core
2151 code by Kern Sibbald. All the code for this funded development has become
2152 part of the Bacula project. Thanks to everyone who made it happen.
2154 \subsection{Concepts}
2155 Although it is possible to backup Exchange using Bacula VSS the Exchange
2156 plugin adds a good deal of functionality, because while Bacula VSS
2157 completes a full backup (snapshot) of Exchange, it does
2158 not support Incremental or Differential backups, restoring is more
2159 complicated, and a single database restore is not possible.
2161 Microsoft Exchange organises its storage into Storage Groups with
2162 Databases inside them. A default installation of Exchange will have a
2163 single Storage Group called 'First Storage Group', with two Databases
2164 inside it, "Mailbox Store (SERVER NAME)" and
2165 "Public Folder Store (SERVER NAME)",
2166 which hold user email and public folders respectively.
2168 In the default configuration, Exchange logs everything that happens to
2169 log files, such that if you have a backup, and all the log files since,
2170 you can restore to the present time. Each Storage Group has its own set
2171 of log files and operates independently of any other Storage Groups. At
2172 the Storage Group level, the logging can be turned off by enabling a
2173 function called "Enable circular logging". At this time the Exchange
2174 plugin will not function if this option is enabled.
2176 The plugin allows backing up of entire storage groups, and the restoring
2177 of entire storage groups or individual databases. Backing up and
2178 restoring at the individual mailbox or email item is not supported but
2179 can be simulated by use of the "Recovery" Storage Group (see below).
2181 \subsection{Installing}
2182 The Exchange plugin requires a DLL that is shipped with Microsoft
2183 Exchanger Server called {\bf esebcli2.dll}. Assuming Exchange is installed
2184 correctly the Exchange plugin should find this automatically and run
2185 without any additional installation.
2187 If the DLL can not be found automatically it will need to be copied into
2188 the Bacula installation
2189 directory (eg C:\verb+\+Program Files\verb+\+Bacula\verb+\+bin). The Exchange API DLL is
2190 named esebcli2.dll and is found in C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+bin on a
2191 default Exchange installation.
2193 \subsection{Backing Up}
2194 To back up an Exchange server the Fileset definition must contain at
2195 least {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"} for
2196 the backup to work correctly. The 'exchange:' bit tells Bacula to look
2197 for the exchange plugin, the '@EXCHANGE' bit makes sure all the backed
2198 up files are prefixed with something that isn't going to share a name
2199 with something outside the plugin, and the 'Microsoft Information Store'
2200 bit is required also. It is also possible to add the name of a storage
2201 group to the "Plugin =" line, eg \\
2202 {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"} \\
2203 if you want only a single storage group backed up.
2205 Additionally, you can suffix the 'Plugin =' directive with
2206 ":notrunconfull" which will tell the plugin not to truncate the Exchange
2207 database at the end of a full backup.
2209 An Incremental or Differential backup will backup only the database logs
2210 for each Storage Group by inspecting the "modified date" on each
2211 physical log file. Because of the way the Exchange API works, the last
2212 logfile backed up on each backup will always be backed up by the next
2213 Incremental or Differential backup too. This adds 5MB to each
2214 Incremental or Differential backup size but otherwise does not cause any
2217 By default, a normal VSS fileset containing all the drive letters will
2218 also back up the Exchange databases using VSS. This will interfere with
2219 the plugin and Exchange's shared ideas of when the last full backup was
2220 done, and may also truncate log files incorrectly. It is important,
2221 therefore, that the Exchange database files be excluded from the backup,
2222 although the folders the files are in should be included, or they will
2223 have to be recreated manually if a baremetal restore is done.
2228 File = C:/Program Files/Exchsrvr/mdbdata
2229 Plugin = "exchange:..."
2232 File = C:/Program Files/Exchsrvr/mdbdata/E00.chk
2233 File = C:/Program Files/Exchsrvr/mdbdata/E00.log
2234 File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log
2235 File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log
2236 File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log
2237 File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log
2238 File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb
2243 The advantage of excluding the above files is that you can significantly
2244 reduce the size of your backup since all the important Exchange files
2245 will be properly saved by the Plugin.
2248 \subsection{Restoring}
2249 The restore operation is much the same as a normal Bacula restore, with
2250 the following provisos:
2253 \item The {\bf Where} restore option must not be specified
2254 \item Each Database directory must be marked as a whole. You cannot just
2255 select (say) the .edb file and not the others.
2256 \item If a Storage Group is restored, the directory of the Storage Group
2258 \item It is possible to restore only a subset of the available log files,
2259 but they {\bf must} be contiguous. Exchange will fail to restore correctly
2260 if a log file is missing from the sequence of log files
2261 \item Each database to be restored must be dismounted and marked as "Can be
2262 overwritten by restore"
2263 \item If an entire Storage Group is to be restored (eg all databases and
2264 logs in the Storage Group), then it is best to manually delete the
2265 database files from the server (eg C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+mdbdata\verb+\+*)
2266 as Exchange can get confused by stray log files lying around.
2269 \subsection{Restoring to the Recovery Storage Group}
2270 The concept of the Recovery Storage Group is well documented by
2272 \elink{http://support.microsoft.com/kb/824126}{http://support.microsoft.com/kb/824126},
2273 but to briefly summarize...
2275 Microsoft Exchange allows the creation of an additional Storage Group
2276 called the Recovery Storage Group, which is used to restore an older
2277 copy of a database (e.g. before a mailbox was deleted) into without
2278 messing with the current live data. This is required as the Standard and
2279 Small Business Server versions of Exchange can not ordinarily have more
2280 than one Storage Group.
2282 To create the Recovery Storage Group, drill down to the Server in Exchange
2283 System Manager, right click, and select
2284 {\bf "New -> Recovery Storage Group..."}. Accept or change the file
2285 locations and click OK. On the Recovery Storage Group, right click and
2286 select {\bf "Add Database to Recover..."} and select the database you will
2289 Restore only the single database nominated as the database in the
2290 Recovery Storage Group. Exchange will redirect the restore to the
2291 Recovery Storage Group automatically.
2292 Then run the restore.
2294 \subsection{Restoring on Microsoft Server 2007}
2295 Apparently the {\bf Exmerge} program no longer exists in Microsoft Server
2296 2007, and henc you use a new proceedure for recovering a single mail box.
2297 This procedure is ducomented by Microsoft at:
2298 \elink{http://technet.microsoft.com/en-us/library/aa997694.aspx}{http://technet.microsoft.com/en-us/library/aa997694.aspx},
2299 and involves using the {\bf Restore-Mailbox} and {\bf
2300 Get-MailboxStatistics} shell commands.
2302 \subsection{Caveats}
2303 This plugin is still being developed, so you should consider it
2304 currently in BETA test, and thus use in a production environment
2305 should be done only after very careful testing.
2307 When doing a full backup, the Exchange database logs are truncated by
2308 Exchange as soon as the plugin has completed the backup. If the data
2309 never makes it to the backup medium (eg because of spooling) then the
2310 logs will still be truncated, but they will also not have been backed
2311 up. A solution to this is being worked on. You will have to schedule a
2312 new Full backup to ensure that your next backups will be usable.
2314 The "Enable Circular Logging" option cannot be enabled or the plugin
2317 Exchange insists that a successful Full backup must have taken place if
2318 an Incremental or Differential backup is desired, and the plugin will
2319 fail if this is not the case. If a restore is done, Exchange will
2320 require that a Full backup be done before an Incremental or Differential
2323 The plugin will most likely not work well if another backup application
2324 (eg NTBACKUP) is backing up the Exchange database, especially if the
2325 other backup application is truncating the log files.
2327 The Exchange plugin has not been tested with the {\bf Accurate} option, so
2328 we recommend either carefully testing or that you avoid this option for
2331 The Exchange plugin is not called during processing the bconsole {\bf
2332 estimate} command, and so anything that would be backed up by the plugin
2333 will not be added to the estimate total that is displayed.
2336 \section{libdbi Framework}
2337 \index[general]{libdbi Framework}
2338 As a general guideline, Bacula has support for a few catalog database drivers
2339 (MySQL, PostgreSQL, SQLite)
2340 coded natively by the Bacula team. With the libdbi implementation, which is a
2341 Bacula driver that uses libdbi to access the catalog, we have an open field to
2342 use many different kinds database engines following the needs of users.
2344 The according to libdbi (http://libdbi.sourceforge.net/) project: libdbi
2345 implements a database-independent abstraction layer in C, similar to the
2346 DBI/DBD layer in Perl. Writing one generic set of code, programmers can
2347 leverage the power of multiple databases and multiple simultaneous database
2348 connections by using this framework.
2350 Currently the libdbi driver in Bacula project only supports the same drivers
2351 natively coded in Bacula. However the libdbi project has support for many
2352 others database engines. You can view the list at
2353 http://libdbi-drivers.sourceforge.net/. In the future all those drivers can be
2354 supported by Bacula, however, they must be tested properly by the Bacula team.
2356 Some of benefits of using libdbi are:
2358 \item The possibility to use proprietary databases engines in which your
2359 proprietary licenses prevent the Bacula team from developing the driver.
2360 \item The possibility to use the drivers written for the libdbi project.
2361 \item The possibility to use other database engines without recompiling Bacula
2362 to use them. Just change one line in bacula-dir.conf
2363 \item Abstract Database access, this is, unique point to code and profiling
2364 catalog database access.
2367 The following drivers have been tested:
2369 \item PostgreSQL, with and without batch insert
2370 \item Mysql, with and without batch insert
2375 In the future, we will test and approve to use others databases engines
2376 (proprietary or not) like DB2, Oracle, Microsoft SQL.
2378 To compile Bacula to support libdbi we need to configure the code with the
2379 --with-dbi and --with-dbi-driver=[database] ./configure options, where
2380 [database] is the database engine to be used with Bacula (of course we can
2381 change the driver in file bacula-dir.conf, see below). We must configure the
2382 access port of the database engine with the option --with-db-port, because the
2383 libdbi framework doesn't know the default access port of each database.
2385 The next phase is checking (or configuring) the bacula-dir.conf, example:
2389 dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
2390 dbname = regress; user = regress; password = ""
2394 The parameter {\bf dbdriver} indicates that we will use the driver dbi with a
2395 mysql database. Currently the drivers supported by Bacula are: postgresql,
2396 mysql, sqlite, sqlite3; these are the names that may be added to string "dbi:".
2398 The following limitations apply when Bacula is set to use the libdbi framework:
2399 - Not tested on the Win32 platform
2400 - A little performance is lost if comparing with native database driver.
2401 The reason is bound with the database driver provided by libdbi and the
2402 simple fact that one more layer of code was added.
2404 It is important to remember, when compiling Bacula with libdbi, the
2405 following packages are needed:
2407 \item libdbi version 1.0.0, http://libdbi.sourceforge.net/
2408 \item libdbi-drivers 1.0.0, http://libdbi-drivers.sourceforge.net/
2411 You can download them and compile them on your system or install the packages
2412 from your OS distribution.
2414 \section{Console Command Additions and Enhancements}
2415 \index[general]{Console Additions}
2417 \subsection{Display Autochanger Content}
2418 \index[general]{StatusSlots}
2420 The {\bf status slots storage=\lt{}storage-name\gt{}} command displays
2421 autochanger content.
2425 Slot | Volume Name | Status | Media Type | Pool |
2426 ------+---------------+----------+-------------------+------------|
2427 1 | 00001 | Append | DiskChangerMedia | Default |
2428 2 | 00002 | Append | DiskChangerMedia | Default |
2429 3*| 00003 | Append | DiskChangerMedia | Scratch |
2434 If you an asterisk ({\bf *}) appears after the slot number, you must run an
2435 {\bf update slots} command to synchronize autochanger content with your
2438 \subsection{list joblog job=xxx or jobid=nnn}
2439 \index[general]{list joblog}
2440 A new list command has been added that allows you to list the contents
2441 of the Job Log stored in the catalog for either a Job Name (fully qualified)
2442 or for a particular JobId. The {\bf llist} command will include a line with
2443 the time and date of the entry.
2445 Note for the catalog to have Job Log entries, you must have a directive
2452 In your Director's {\bf Messages} resource.
2454 \subsection{Use separator for multiple commands}
2455 \index[general]{Command Separator}
2456 When using bconsole with readline, you can set the command separator with
2457 \textbf{@separator} command to one
2458 of those characters to write commands who require multiple input in one line.
2460 !$%&'()*+,-/:;<>?[]^`{|}~
2463 \subsection{Deleting Volumes}
2464 The delete volume bconsole command has been modified to
2465 require an asterisk (*) in front of a MediaId otherwise the
2466 value you enter is a taken to be a Volume name. This is so that
2467 users may delete numeric Volume names. The previous Bacula versions
2468 assumed that all input that started with a number was a MediaId.
2470 This new behavior is indicated in the prompt if you read it
2473 \section{Bare Metal Recovery}
2474 The old bare metal recovery project is essentially dead. One
2475 of the main features of it was that it would build a recovery
2476 CD based on the kernel on your system. The problem was that
2477 every distribution has a different boot procedure and different
2478 scripts, and worse yet, the boot procedures and scripts change
2479 from one distribution to another. This meant that maintaining
2480 (keeping up with the changes) the rescue CD was too much work.
2482 To replace it, a new bare metal recovery USB boot stick has been developed
2483 by Bacula Systems. This technology involves remastering a Ubuntu LiveCD to
2484 boot from a USB key.
2488 \item Recovery can be done from within graphical environment.
2489 \item Recovery can be done in a shell.
2490 \item Ubuntu boots on a large number of Linux systems.
2491 \item The process of updating the system and adding new
2492 packages is not too difficult.
2493 \item The USB key can easily be upgraded to newer Ubuntu versions.
2494 \item The USB key has writable partitions for modifications to
2495 the OS and for modification to your home directory.
2496 \item You can add new files/directories to the USB key very easily.
2497 \item You can save the environment from multiple machines on
2499 \item Bacula Systems is funding its ongoing development.
2502 The disadvantages are:
2504 \item The USB key is usable but currently under development.
2505 \item Not everyone may be familiar with Ubuntu (no worse
2507 \item Some older OSes cannot be booted from USB. This can
2508 be resolved by first booting a Ubuntu LiveCD then plugging
2510 \item Currently the documentation is sketchy and not yet added
2511 to the main manual. See below ...
2514 The documentation and the code can be found in the {\bf rescue} package
2515 in the directory {\bf linux/usb}.
2517 \section{Miscellaneous}
2518 \index[general]{Misc New Features}
2520 \subsection{Allow Mixed Priority = \lt{}yes\vb{}no\gt{}}
2521 \index[general]{Allow Mixed Priority}
2522 This directive is only implemented in version 2.5 and later. When
2523 set to {\bf yes} (default {\bf no}), this job may run even if lower
2524 priority jobs are already running. This means a high priority job
2525 will not have to wait for other jobs to finish before starting.
2526 The scheduler will only mix priorities when all running jobs have
2529 Note that only higher priority jobs will start early. Suppose the
2530 director will allow two concurrent jobs, and that two jobs with
2531 priority 10 are running, with two more in the queue. If a job with
2532 priority 5 is added to the queue, it will be run as soon as one of
2533 the running jobs finishes. However, new priority 10 jobs will not
2534 be run until the priority 5 job has finished.
2536 \subsection{Bootstrap File Directive -- FileRegex}
2537 \index[general]{Bootstrap File Directive}
2538 {\bf FileRegex} is a new command that can be added to the bootstrap
2539 (.bsr) file. The value is a regular expression. When specified, only
2540 matching filenames will be restored.
2542 During a restore, if all File records are pruned from the catalog
2543 for a Job, normally Bacula can restore only all files saved. That
2544 is there is no way using the catalog to select individual files.
2545 With this new feature, Bacula will ask if you want to specify a Regex
2546 expression for extracting only a part of the full backup.
2549 Building directory tree for JobId(s) 1,3 ...
2550 There were no files inserted into the tree, so file selection
2551 is not possible.Most likely your retention policy pruned the files
2553 Do you want to restore all the files? (yes\vb{}no): no
2555 Regexp matching files to restore? (empty to abort): /tmp/regress/(bin|tests)/
2556 Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr
2559 \subsection{Bootstrap File Optimization Changes}
2560 In order to permit proper seeking on disk files, we have extended the bootstrap
2561 file format to include a {\bf VolStartAddr} and {\bf VolEndAddr} records. Each
2562 takes a 64 bit unsigned integer range (i.e. nnn-mmm) which defines the start
2563 address range and end address range respectively. These two directives replace
2564 the {\bf VolStartFile}, {\bf VolEndFile}, {\bf VolStartBlock} and {\bf
2565 VolEndBlock} directives. Bootstrap files containing the old directives will
2566 still work, but will not properly take advantage of proper disk seeking, and
2567 may read completely to the end of a disk volume during a restore. With the new
2568 format (automatically generated by the new Director), restores will seek
2569 properly and stop reading the volume when all the files have been restored.
2571 \subsection{Solaris ZFS/NFSv4 ACLs}
2572 This is an upgrade of the previous Solaris ACL backup code
2573 to the new library format, which will backup both the old
2574 POSIX(UFS) ACLs as well as the ZFS ACLs.
2576 The new code can also restore POSIX(UFS) ACLs to a ZFS filesystem
2577 (it will translate the POSIX(UFS)) ACL into a ZFS/NFSv4 one) it can also
2578 be used to transfer from UFS to ZFS filesystems.
2581 \subsection{Virtual Tape Emulation}
2582 \index[general]{Virtual Tape Emulation}
2583 We now have a Virtual Tape emulator that allows us to run though 99.9\% of
2584 the tape code but actually reading and writing to a disk file. Used with the
2585 \textbf{disk-changer} script, you can now emulate an autochanger with 10 drives
2586 and 700 slots. This feature is most useful in testing. It is enabled
2587 by using {\bf Device Type = vtape} in the Storage daemon's Device
2588 directive. This feature is only implemented on Linux machines and should not be
2589 used for production.
2591 \subsection{Bat Enhancements}
2592 \index[general]{Bat Enhancements}
2593 Bat (the Bacula Administration Tool) GUI program has been significantly
2594 enhanced and stabilized. In particular, there are new table based status
2595 commands; it can now be easily localized using Qt4 Linguist.
2597 The Bat communications protocol has been significantly enhanced to improve
2598 GUI handling. Note, you {\bf must} use a the bat that is distributed with
2599 the Director you are using otherwise the communications protocol will not
2602 \subsection{RunScript Enhancements}
2603 \index[general]{RunScript Enhancements}
2604 The {\bf RunScript} resource has been enhanced to permit multiple
2605 commands per RunScript. Simply specify multiple {\bf Command} directives
2612 Command = "/bin/echo test"
2613 Command = "/bin/echo an other test"
2614 Command = "/bin/echo 3 commands in the same runscript"
2621 A new Client RunScript {\bf RunsWhen} keyword of {\bf AfterVSS} has been
2622 implemented, which runs the command after the Volume Shadow Copy has been made.
2624 Console commands can be specified within a RunScript by using:
2625 {\bf Console = \lt{}command\gt{}}, however, this command has not been
2626 carefully tested and debugged and is known to easily crash the Director.
2627 We would appreciate feedback. Due to the recursive nature of this command, we
2628 may remove it before the final release.
2630 \subsection{Status Enhancements}
2631 \index[general]{Status Enhancements}
2632 The bconsole {\bf status dir} output has been enhanced to indicate
2633 Storage daemon job spooling and despooling activity.
2635 \subsection{Connect Timeout}
2636 \index[general]{Connect Timeout}
2637 The default connect timeout to the File
2638 daemon has been set to 3 minutes. Previously it was 30 minutes.
2640 \subsection{ftruncate for NFS Volumes}
2641 \index[general]{ftruncate for NFS Volumes}
2642 If you write to a Volume mounted by NFS (say on a local file server),
2643 in previous Bacula versions, when the Volume was recycled, it was not
2644 properly truncated because NFS does not implement ftruncate (file
2645 truncate). This is now corrected in the new version because we have
2646 written code (actually a kind user) that deletes and recreates the Volume,
2647 thus accomplishing the same thing as a truncate.
2649 \subsection{Support for Ubuntu}
2650 The new version of Bacula now recognizes the Ubuntu (and Kubuntu)
2651 version of Linux, and thus now provides correct autostart routines.
2652 Since Ubuntu officially supports Bacula, you can also obtain any
2653 recent release of Bacula from the Ubuntu repositories.
2655 \subsection{Recycle Pool = \lt{}pool-name\gt{}}
2656 \index[general]{Recycle Pool}
2657 The new \textbf{RecyclePool} directive defines to which pool the Volume will
2658 be placed (moved) when it is recycled. Without this directive, a Volume will
2659 remain in the same pool when it is recycled. With this directive, it can be
2660 moved automatically to any existing pool during a recycle. This directive is
2661 probably most useful when defined in the Scratch pool, so that volumes will
2662 be recycled back into the Scratch pool.
2664 \subsection{FD Version}
2665 \index[general]{FD Version}
2666 The File daemon to Director protocol now includes a version
2667 number, which although there is no visible change for users,
2668 will help us in future versions automatically determine
2669 if a File daemon is not compatible.
2671 \subsection{Max Run Sched Time = \lt{}time-period-in-seconds\gt{}}
2672 \index[general]{Max Run Sched Time}
2673 The time specifies the maximum allowed time that a job may run, counted from
2674 when the job was scheduled. This can be useful to prevent jobs from running
2675 during working hours. We can see it like \texttt{Max Start Delay + Max Run
2678 \subsection{Max Wait Time = \lt{}time-period-in-seconds\gt{}}
2679 \index[general]{Max Wait Time}
2680 Previous \textbf{MaxWaitTime} directives aren't working as expected, instead
2681 of checking the maximum allowed time that a job may block for a resource,
2682 those directives worked like \textbf{MaxRunTime}. Some users are reporting to
2683 use \textbf{Incr/Diff/Full Max Wait Time} to control the maximum run time of
2684 their job depending on the level. Now, they have to use
2685 \textbf{Incr/Diff/Full Max Run Time}. \textbf{Incr/Diff/Full Max Wait Time}
2686 directives are now deprecated.
2688 \subsection{Incremental|Differential Max Wait Time = \lt{}time-period-in-seconds\gt{}}
2689 \index[general]{Incremental Max Wait Time}
2690 \index[general]{Differential Max Wait Time}
2692 These directives have been deprecated in favor of
2693 \texttt{Incremental|Differential Max Run Time}.
2695 \subsection{Max Run Time directives}
2696 \index[general]{Max Run Time directives}
2697 Using \textbf{Full/Diff/Incr Max Run Time}, it's now possible to specify the
2698 maximum allowed time that a job can run depending on the level.
2700 \addcontentsline{lof}{figure}{Job time control directives}
2701 \includegraphics{\idir different_time.eps}
2703 \subsection{Statistics Enhancements}
2704 \index[general]{Statistics Enhancements}
2705 If you (or probably your boss) want to have statistics on your backups to
2706 provide some \textit{Service Level Agreement} indicators, you could use a few
2707 SQL queries on the Job table to report how many:
2711 \item jobs have been successful
2712 \item files have been backed up
2716 However, these statistics are accurate only if your job retention is greater
2717 than your statistics period. Ie, if jobs are purged from the catalog, you won't
2718 be able to use them.
2720 Now, you can use the \textbf{update stats [days=num]} console command to fill
2721 the JobHistory table with new Job records. If you want to be sure to take in
2722 account only \textbf{good jobs}, ie if one of your important job has failed but
2723 you have fixed the problem and restarted it on time, you probably want to
2724 delete the first \textit{bad} job record and keep only the successful one. For
2725 that simply let your staff do the job, and update JobHistory table after two or
2726 three days depending on your organization using the \textbf{[days=num]} option.
2728 These statistics records aren't used for restoring, but mainly for
2729 capacity planning, billings, etc.
2731 The Bweb interface provides a statistics module that can use this feature. You
2732 can also use tools like Talend or extract information by yourself.
2734 The \textbf{Statistics Retention = \lt{}time\gt{}} director directive defines
2735 the length of time that Bacula will keep statistics job records in the Catalog
2736 database after the Job End time. (In \texttt{JobHistory} table) When this time
2737 period expires, and if user runs \texttt{prune stats} command, Bacula will
2738 prune (remove) Job records that are older than the specified period.
2740 You can use the following Job resource in your nightly \textbf{BackupCatalog}
2741 job to maintain statistics.
2744 Name = BackupCatalog
2747 Console = "update stats days=3"
2748 Console = "prune stats yes"
2755 \subsection{ScratchPool = \lt{}pool-resource-name\gt{}}
2756 \index[general]{ScratchPool}
2757 This directive permits to specify a specific \textsl{Scratch} pool for the
2758 current pool. This is useful when using multiple storage sharing the same
2759 mediatype or when you want to dedicate volumes to a particular set of pool.
2761 \subsection{Enhanced Attribute Despooling}
2762 \index[general]{Attribute Despooling}
2763 If the storage daemon and the Director are on the same machine, the spool file
2764 that contains attributes is read directly by the Director instead of being
2765 transmitted across the network. That should reduce load and speedup insertion.
2767 \subsection{SpoolSize = \lt{}size-specification-in-bytes\gt{}}
2768 \index[general]{SpoolSize}
2769 A new Job directive permits to specify the spool size per job. This is used
2770 in advanced job tunning. {\bf SpoolSize={\it bytes}}
2772 \subsection{MaximumConsoleConnections = \lt{}number\gt{}}
2773 \index[general]{MaximumConsoleConnections}
2774 A new director directive permits to specify the maximum number of Console
2775 Connections that could run concurrently. The default is set to 20, but you may
2776 set it to a larger number.
2778 \subsection{VerId = \lt{}string\gt{}}
2779 \index[general]{VerId}
2780 A new director directive permits to specify a personnal identifier that will be
2781 displayed in the \texttt{version} command.
2783 \subsection{dbcheck enhancements}
2784 \index[general]{dbcheck enhancements}
2785 If you are using Mysql, dbcheck will now ask you if you want to create
2786 temporary indexes to speed up orphaned Path and Filename elimination.
2788 A new \texttt{-B} option allows you to print catalog information in a simple
2789 text based format. This is useful to backup it in a secure way.
2804 You can now specify the database connection port in the command line.
2806 \subsection{{-}{-}docdir configure option}
2807 \index[general]{{-}{-}docdir configure option}
2808 You can use {-}{-}docdir= on the ./configure command to
2809 specify the directory where you want Bacula to install the
2810 LICENSE, ReleaseNotes, ChangeLog, ... files. The default is
2811 {\bf /usr/share/doc/bacula}.
2813 \subsection{{-}{-}htmldir configure option}
2814 \index[general]{{-}{-}htmldir configure option}
2815 You can use {-}{-}htmldir= on the ./configure command to
2816 specify the directory where you want Bacula to install the bat html help
2817 files. The default is {\bf /usr/share/doc/bacula/html}
2819 \subsection{{-}{-}with-plugindir configure option}
2820 \index[general]{{-}{-}plugindir configure option}
2821 You can use {-}{-}plugindir= on the ./configure command to
2822 specify the directory where you want Bacula to install
2823 the plugins (currently only bpipe-fd). The default is