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 commande \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 Enterprise
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 Outlook
120 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 Enterprise
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 function
250 uses only PathId and FilenameId. The jobid argument is mandatory but unused.
253 .bvfs_versions client=filedaemon pathid=num filenameid=num jobid=1
254 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
255 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
262 .bvfs_versions client=localhost-fd pathid=1 fnid=47 jobid=1
263 1 47 52 12 gD HRid IGk D Po Po A P BAA I A /uPgWaxMgKZlnMti7LChyA Vol1 1
266 \subsection*{List directories}
268 Bvfs allows you to list directories in a specific path.
270 .bvfs_lsdirs pathid=num path=/apath jobid=numlist limit=num offset=num
271 PathId FilenameId FileId JobId LStat Path
272 PathId FilenameId FileId JobId LStat Path
273 PathId FilenameId FileId JobId LStat Path
277 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
278 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record
279 listed is a directory.
282 .bvfs_lsdirs pathid=4 jobid=1,11,12
283 4 0 0 0 A A A A A A A A A A A A A A .
284 5 0 0 0 A A A A A A A A A A A A A A ..
285 3 0 0 0 A A A A A A A A A A A A A A regress/
288 In this example, to list directories present in \texttt{regress/}, you can use
290 .bvfs_lsdirs pathid=3 jobid=1,11,12
291 3 0 0 0 A A A A A A A A A A A A A A .
292 4 0 0 0 A A A A A A A A A A A A A A ..
293 2 0 0 0 A A A A A A A A A A A A A A tmp/
296 \subsection*{List files}
298 Bvfs allows you to list files in a specific path.
300 .bvfs_lsfiles pathid=num path=/apath jobid=numlist limit=num offset=num
301 PathId FilenameId FileId JobId LStat Path
302 PathId FilenameId FileId JobId LStat Path
303 PathId FilenameId FileId JobId LStat Path
307 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
308 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record listed
312 .bvfs_lsfiles pathid=4 jobid=1,11,12
313 4 0 0 0 A A A A A A A A A A A A A A .
314 5 0 0 0 A A A A A A A A A A A A A A ..
315 1 0 0 0 A A A A A A A A A A A A A A regress/
318 In this example, to list files present in \texttt{regress/}, you can use
320 .bvfs_lsfiles pathid=1 jobid=1,11,12
321 1 47 52 12 gD HRid IGk BAA I BMqcPH BMqcPE BMqe+t A titi
322 1 49 53 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B toto
323 1 48 54 12 gD HRie IGk BAA I BMqcPH BMqcPE BMqe+3 A tutu
324 1 45 55 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B ficheriro1.txt
325 1 46 56 12 gD HRie IGk BAA I BMqe/K BMqcPE BMqe+3 D ficheriro2.txt
328 \subsection*{Restore set of files}
330 Bvfs allows you to create a SQL table that contains files that you want to
331 restore. This table can be provided to a restore command with the file option.
334 .bvfs_restore fileid=numlist dirid=numlist hardlink=numlist path=b2num
336 restore file=?b2num ...
339 To include a directory (with \texttt{dirid}), Bvfs needs to run a query to
340 select all files. This query could be time consuming.
342 \texttt{hardlink} list is always composed of a serie of two numbers (jobid,
343 fileindex). This information can be found in the LinkFI field of the LStat
346 The \texttt{path} argument represents the name of the table that Bvfs will
347 store results. The format of this table is \texttt{b2[0-9]+}. (Should start by
348 b2 and followed by digits).
353 .bvfs_restore fileid=1,2,3,4 hardlink=10,15,10,20 jobid=10 path=b20001
357 \subsection*{Cleanup after restore}
359 To drop the table used by the restore command, you can use the
360 \texttt{.bvfs\_cleanup} command.
363 .bvfs_cleanup path=b20001
366 \section{Changes in the pruning algorithm}
368 We rewrote the job pruning algorithm in this version. Previously, in some users
369 reported that the pruning process at the end of jobs was very long. It should
370 not be longer the case. Now, Bacula won't prune automatically a Job if this
371 particular Job is needed to restore data. Example:
375 JobId: 2 Level: Incremental
376 JobId: 3 Level: Incremental
377 JobId: 4 Level: Differential
378 .. Other incrementals up to now
381 In this example, if the Job Retention defined in the Pool or in the Client
382 resource causes that Jobs with Jobid in 1,2,3,4 can be pruned, Bacula will
383 detect that JobId 1 and 4 are essential to restore data at the current state
384 and will prune only JobId 2 and 3.
386 \texttt{Important}, this change affect only the automatic pruning step after a
387 Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the
388 \texttt{VolumeRetention} period, important jobs can be pruned.
390 \section{Ability to Verify any specified Job}
391 You now have the ability to tell Bacula which Job should verify instead of
392 automatically verify just the last one.
394 This feature can be used with VolumeToCatalog, DiskToCatalog and Catalog level.
396 To verify a given job, just specify the Job jobid in argument when starting the
399 *run job=VerifyVolume jobid=1 level=VolumeToCatalog
401 JobName: VerifyVolume
402 Level: VolumeToCatalog
405 Pool: Default (From Job resource)
406 Storage: File (From Job resource)
407 Verify Job: VerifyVol.2010-09-08_14.17.17_03
408 Verify List: /tmp/regress/working/VerifyVol.bsr
409 When: 2010-09-08 14:17:31
411 OK to run? (yes/mod/no):
415 This project was funded by Bacula Systems and is available with Bacula
416 Enterprise Edition and Community Edition.
418 \section{Additions to RunScript variables}
419 You can have access to JobBytes and JobFiles using %b and %f in your runscript
423 RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%f"
426 %\section{Changes in drivetype.exe}
428 %Now the \texttt{drivetype.exe} program allows you to list all local hard
429 %drives. It can help to build dynamic FileSet on Windows.
432 %File = "\\|\"c:/program files/bacula/bin32/drivetype\" -l -a"
436 \section{Additions to the Plugin API}
437 The bfuncs structure has been extended to include a number of
441 The bFuncs structure defines the callback entry points within Bacula
442 that the plugin can use register events, get Bacula values, set
443 Bacula values, and send messages to the Job output or debug output.
445 The exact definition as of this writing is:
447 typedef struct s_baculaFuncs {
450 bRC (*registerBaculaEvents)(bpContext *ctx, ...);
451 bRC (*getBaculaValue)(bpContext *ctx, bVariable var, void *value);
452 bRC (*setBaculaValue)(bpContext *ctx, bVariable var, void *value);
453 bRC (*JobMessage)(bpContext *ctx, const char *file, int line,
454 int type, utime_t mtime, const char *fmt, ...);
455 bRC (*DebugMessage)(bpContext *ctx, const char *file, int line,
456 int level, const char *fmt, ...);
457 void *(*baculaMalloc)(bpContext *ctx, const char *file, int line,
459 void (*baculaFree)(bpContext *ctx, const char *file, int line, void *mem);
461 /* New functions follow */
462 bRC (*AddExclude)(bpContext *ctx, const char *file);
463 bRC (*AddInclude)(bpContext *ctx, const char *file);
464 bRC (*AddIncludeOptions)(bpContext *ctx, const char *opts);
465 bRC (*AddRegex)(bpContext *ctx, const char *item, int type);
466 bRC (*AddWild)(bpContext *ctx, const char *item, int type);
467 bRC (*checkChanges)(bpContext *ctx, struct save_pkt *sp);
473 \item [AddExclude] can be called to exclude a file. The file
474 string passed may include wildcards that will be interpreted by
475 the {\bf fnmatch} subroutine. This function can be called
476 multiple times, and each time the file specified will be added
477 to the list of files to be excluded. Note, this function only
478 permits adding excludes of specific file or directory names,
479 or files matched by the rather simple fnmatch mechanism.
480 See below for information on doing wild-card and regex excludes.
482 \item [NewInclude] can be called to create a new Include block. This
483 block will be added before any user defined Include blocks. This
484 function can be called multiple times, but each time, it will create
485 a new Include section (not normally needed). This function should
486 be called only if you want to add an entirely new Include block.
488 \item [AddInclude] can be called to add new files/directories to
489 be included. They are added to the current Include block. If
490 NewInclude has not been included, the current Include block is
491 the last one that the user created. This function
492 should be used only if you want to add totally new files/directories
493 to be included in the backup.
495 \item [NewOptions] adds a new Options block to the current Include
496 in front of any other Options blocks. This permits the plugin to
497 add exclude directives (wild-cards and regexes) in front of the
498 user Options, and thus prevent certain files from being backed up.
499 This can be useful if the plugin backs up files, and they should
500 not be also backed up by the main Bacula code. This function
501 may be called multiple times, and each time, it creates a new
502 prepended Options block. Note: normally you want to call this
503 entry point prior to calling AddOptions, AddRegex, or AddWild.
505 \item [AddOptions] allows the plugin it set options in
506 the current Options block, which is normally created with the
507 NewOptions call just prior to adding Include Options.
508 The permitted options are passed as a character string, where
509 each character has a specific meaning as defined below:
512 \item [a] always replace files (default).
513 \item [e] exclude rather than include.
514 \item [h] no recursion into subdirectories.
515 \item [H] do not handle hard links.
516 \item [i] ignore case in wildcard and regex matches.
517 \item [M] compute an MD5 sum.
518 \item [p] use a portable data format on Windows (not recommended).
519 \item [R] backup resource forks and Findr Info.
520 \item [r] read from a fifo
521 \item [S1] compute an SHA1 sum.
522 \item [S2] compute an SHA256 sum.
523 \item [S3] comput an SHA512 sum.
524 \item [s] handle sparse files.
525 \item [m] use st\_mtime only for file differences.
526 \item [k] restore the st\_atime after accessing a file.
527 \item [A] enable ACL backup.
528 \item [Vxxx:] specify verify options. Must terminate with :
529 \item [Cxxx:] specify accurate options. Must terminate with :
530 \item [Jxxx:] specify base job Options. Must terminate with :
531 \item [Pnnn:] specify integer nnn paths to strip. Must terminate with :
533 \item [Zn] specify gzip compression level n.
534 \item [K] do not use st\_atime in backup decision.
535 \item [c] check if file changed during backup.
536 \item [N] honor no dump flag.
537 \item [X] enable backup of extended attributes.
540 \item [AddRegex] adds a regex expression to the current Options block.
541 The fillowing options are permitted:
543 \item [ ] (a blank) regex applies to whole path and filename.
544 \item [F] regex applies only to the filename (directory or path stripped).
545 \item [D] regex applies only to the directory (path) part of the name.
548 \item [AddWild] adds a wildcard expression to the current Options block.
549 The fillowing options are permitted:
551 \item [ ] (a blank) regex applies to whole path and filename.
552 \item [F] regex applies only to the filename (directory or path stripped).
553 \item [D] regex applies only to the directory (path) part of the name.
556 \item [checkChanges] call the \texttt{check\_changes()} function in Bacula code
557 that can use Accurate code to compare the file information in argument with
558 the previous file information. The \texttt{delta\_seq} attribute of the
559 \texttt{save\_pkt} will be updated, and the call will return
560 \texttt{bRC\_Seen} if the core code wouldn't decide to backup it.
565 \subsection{Bacula events}
566 The list of events has been extended to include:
572 bEventStartBackupJob = 3,
573 bEventEndBackupJob = 4,
574 bEventStartRestoreJob = 5,
575 bEventEndRestoreJob = 6,
576 bEventStartVerifyJob = 7,
577 bEventEndVerifyJob = 8,
578 bEventBackupCommand = 9,
579 bEventRestoreCommand = 10,
584 bEventCancelCommand = 13,
585 bEventVssBackupAddComponents = 14,
586 bEventVssRestoreLoadComponentMetadata = 15,
587 bEventVssRestoreSetComponentsSelected = 16,
588 bEventRestoreObject = 17,
589 bEventEndFileSet = 18,
590 bEventPluginCommand = 19,
591 bEventVssBeforeCloseRestore = 20,
592 bEventVssPrepareSnapshot = 21
598 \item [bEventCancelCommand] is called whenever the currently
599 running Job is cancelled */
601 \item [bEventVssBackupAddComponents]
603 \item [bEventVssPrepareSnapshot] is called before creating VSS snapshots, it
604 provides a char[27] table where the plugin can add Windows drives that will
605 be used during the Job. You need to add them without duplicates, and you can
606 use in \texttt{fd\_common.h} \texttt{add\_drive()} and \texttt{copy\_drives()}
610 \chapter{Release Version 5.0.3}
612 There are no new features in version 5.0.2. This version simply fixes a
613 number of bugs found in version 5.0.1 during the onging development
616 \chapter{Release Version 5.0.2}
618 There are no new features in version 5.0.2. This version simply fixes a
619 number of bugs found in version 5.0.1 during the onging development
625 \chapter{New Features in 5.0.1}
627 This chapter presents the new features that are in the released Bacula version
628 5.0.1. This version mainly fixes a number of bugs found in version 5.0.0 during
629 the onging development process.
631 \section{Truncate Volume after Purge}
632 \label{sec:actiononpurge}
634 The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate
635 the volume when it is purged with the new command \texttt{purge volume
636 action}. It is useful to prevent disk based volumes from consuming too much
642 Action On Purge = Truncate
647 As usual you can also set this property with the \texttt{update volume} command
649 *update volume=xxx ActionOnPurge=Truncate
650 *update volume=xxx actiononpurge=None
653 To ask Bacula to truncate your \texttt{Purged} volumes, you need to use the
654 following command in interactive mode or in a RunScript as shown after:
656 *purge volume action=truncate storage=File allpools
657 # or by default, action=all
658 *purge volume action storage=File pool=Default
661 This is possible to specify the volume name, the media type, the pool, the
662 storage, etc\dots (see \texttt{help purge}) Be sure that your storage device is
663 idle when you decide to run this command.
672 Console = "purge volume action=all allpools storage=File"
677 \textbf{Important note}: This feature doesn't work as
678 expected in version 5.0.0. Please do not use it before version 5.0.1.
680 \section{Allow Higher Duplicates}
681 This directive did not work correctly and has been depreciated
682 (disabled) in version 5.0.1. Please remove it from your bacula-dir.conf
683 file as it will be removed in a future rlease.
685 \section{Cancel Lower Level Duplicates}
686 This directive was added in Bacula version 5.0.1. It compares the
687 level of a new backup job to old jobs of the same name, if any,
688 and will kill the job which has a lower level than the other one.
689 If the levels are the same (i.e. both are Full backups), then
690 nothing is done and the other Cancel XXX Duplicate directives
693 \chapter{New Features in 5.0.0}
695 \section{Maximum Concurent Jobs for Devices}
696 \label{sec:maximumconcurentjobdevice}
698 {\bf Maximum Concurrent Jobs} is a new Device directive in the Storage
699 Daemon configuration permits setting the maximum number of Jobs that can
700 run concurrently on a specified Device. Using this directive, it is
701 possible to have different Jobs using multiple drives, because when the
702 Maximum Concurrent Jobs limit is reached, the Storage Daemon will start new
703 Jobs on any other available compatible drive. This facilitates writing to
704 multiple drives with multiple Jobs that all use the same Pool.
706 This project was funded by Bacula Systems.
708 \section{Restore from Multiple Storage Daemons}
709 \index[general]{Restore}
711 Previously, you were able to restore from multiple devices in a single Storage
712 Daemon. Now, Bacula is able to restore from multiple Storage Daemons. For
713 example, if your full backup runs on a Storage Daemon with an autochanger, and
714 your incremental jobs use another Storage Daemon with lots of disks, Bacula
715 will switch automatically from one Storage Daemon to an other within the same
718 You must upgrade your File Daemon to version 3.1.3 or greater to use this
721 This project was funded by Bacula Systems with the help of Equiinet.
723 \section{File Deduplication using Base Jobs}
724 A base job is sort of like a Full save except that you will want the FileSet to
725 contain only files that are unlikely to change in the future (i.e. a snapshot
726 of most of your system after installing it). After the base job has been run,
727 when you are doing a Full save, you specify one or more Base jobs to be used.
728 All files that have been backed up in the Base job/jobs but not modified will
729 then be excluded from the backup. During a restore, the Base jobs will be
730 automatically pulled in where necessary.
732 This is something none of the competition does, as far as we know (except
733 perhaps BackupPC, which is a Perl program that saves to disk only). It is big
734 win for the user, it makes Bacula stand out as offering a unique optimization
735 that immediately saves time and money. Basically, imagine that you have 100
736 nearly identical Windows or Linux machine containing the OS and user files.
737 Now for the OS part, a Base job will be backed up once, and rather than making
738 100 copies of the OS, there will be only one. If one or more of the systems
739 have some files updated, no problem, they will be automatically restored.
741 See the \ilink{Base Job Chapter}{basejobs} for more information.
743 This project was funded by Bacula Systems.
745 \section{AllowCompression = \lt{}yes\vb{}no\gt{}}
746 \index[dir]{AllowCompression}
748 This new directive may be added to Storage resource within the Director's
749 configuration to allow users to selectively disable the client compression for
750 any job which writes to this storage resource.
756 Address = ultrium-tape
757 Password = storage_password # Password for Storage Daemon
760 AllowCompression = No # Tape drive has hardware compression
763 The above example would cause any jobs running with the UltriumTape storage
764 resource to run without compression from the client file daemons. This
765 effectively overrides any compression settings defined at the FileSet level.
767 This feature is probably most useful if you have a tape drive which supports
768 hardware compression. By setting the \texttt{AllowCompression = No} directive
769 for your tape drive storage resource, you can avoid additional load on the file
770 daemon and possibly speed up tape backups.
772 This project was funded by Collaborative Fusion, Inc.
774 \section{Accurate Fileset Options}
775 \label{sec:accuratefileset}
777 In previous versions, the accurate code used the file creation and modification
778 times to determine if a file was modified or not. Now you can specify which
779 attributes to use (time, size, checksum, permission, owner, group, \dots),
780 similar to the Verify options.
796 \item {\bf i} compare the inodes
797 \item {\bf p} compare the permission bits
798 \item {\bf n} compare the number of links
799 \item {\bf u} compare the user id
800 \item {\bf g} compare the group id
801 \item {\bf s} compare the size
802 \item {\bf a} compare the access time
803 \item {\bf m} compare the modification time (st\_mtime)
804 \item {\bf c} compare the change time (st\_ctime)
805 \item {\bf d} report file size decreases
806 \item {\bf 5} compare the MD5 signature
807 \item {\bf 1} compare the SHA1 signature
810 \textbf{Important note:} If you decide to use checksum in Accurate jobs,
811 the File Daemon will have to read all files even if they normally would not
812 be saved. This increases the I/O load, but also the accuracy of the
813 deduplication. By default, Bacula will check modification/creation time
816 This project was funded by Bacula Systems.
818 \section{Tab-completion for Bconsole}
819 \label{sec:tabcompletion}
821 If you build \texttt{bconsole} with readline support, you will be able to use
822 the new auto-completion mode. This mode supports all commands, gives help
823 inside command, and lists resources when required. It works also in the restore
826 To use this feature, you should have readline development package loaded on
827 your system, and use the following option in configure.
829 ./configure --with-readline=/usr/include/readline --disable-conio ...
832 The new bconsole won't be able to tab-complete with older directors.
834 This project was funded by Bacula Systems.
836 \section{Pool File and Job Retention}
837 \label{sec:poolfilejobretention}
839 We added two new Pool directives, \texttt{FileRetention} and
840 \texttt{JobRetention}, that take precedence over Client directives of the same
841 name. It allows you to control the Catalog pruning algorithm Pool by Pool. For
842 example, you can decide to increase Retention times for Archive or OffSite Pool.
844 It seems obvious to us, but apparently not to some users, that given the
845 definition above that the Pool File and Job Retention periods is a global
846 override for the normal Client based prunning, which means that when the
847 Job is prunned, the prunning will apply globally to that particular Job.
849 Currently, there is a bug in the implementation that causes any Pool
850 retention periods specified to apply to {\bf all} Pools for that
851 particular Client. Thus we suggest that you avoid using these two
852 directives until this implementation problem is corrected.
854 \section{Read-only File Daemon using capabilities}
855 \label{sec:fdreadonly}
856 This feature implements support of keeping \textbf{ReadAll} capabilities after
857 UID/GID switch, this allows FD to keep root read but drop write permission.
859 It introduces new \texttt{bacula-fd} option (\texttt{-k}) specifying that
860 \textbf{ReadAll} capabilities should be kept after UID/GID switch.
863 root@localhost:~# bacula-fd -k -u nobody -g nobody
866 The code for this feature was contributed by our friends at AltLinux.
871 To help developers of restore GUI interfaces, we have added new \textsl{dot
872 commands} that permit browsing the catalog in a very simple way.
875 \item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update
876 the Bvfs cache in the catalog. You need to run it before any access to the
879 \item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command
880 will list all directories in the specified \texttt{path} or
881 \texttt{pathid}. Using \texttt{pathid} avoids problems with character
882 encoding of path/filenames.
884 \item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command
885 will list all files in the specified \texttt{path} or \texttt{pathid}. Using
886 \texttt{pathid} avoids problems with character encoding.
889 You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of
890 data that will be displayed.
893 * .bvfs_update jobid=1,2
895 * .bvfs_lsdir path=/ jobid=1,2
898 This project was funded by Bacula Systems.
900 \section{Testing your Tape Drive}
901 \label{sec:btapespeed}
903 To determine the best configuration of your tape drive, you can run the new
904 \texttt{speed} command available in the \texttt{btape} program.
906 This command can have the following arguments:
908 \item[\texttt{file\_size=n}] Specify the Maximum File Size for this test
909 (between 1 and 5GB). This counter is in GB.
910 \item[\texttt{nb\_file=n}] Specify the number of file to be written. The amount
911 of data should be greater than your memory ($file\_size*nb\_file$).
912 \item[\texttt{skip\_zero}] This flag permits to skip tests with constant
914 \item[\texttt{skip\_random}] This flag permits to skip tests with random
916 \item[\texttt{skip\_raw}] This flag permits to skip tests with raw access.
917 \item[\texttt{skip\_block}] This flag permits to skip tests with Bacula block
922 *speed file_size=3 skip_raw
923 btape.c:1078 Test with zero data and bacula block structure.
924 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
925 ++++++++++++++++++++++++++++++++++++++++++
926 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
927 btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 MB/s
929 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 MB/s
931 btape.c:1090 Test with random data, should give the minimum throughput.
932 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
933 +++++++++++++++++++++++++++++++++++++++++++
934 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
935 btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 MB/s
936 +++++++++++++++++++++++++++++++++++++++++++
938 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s
942 When using compression, the random test will give your the minimum throughput
943 of your drive . The test using constant string will give you the maximum speed
944 of your hardware chain. (cpu, memory, scsi card, cable, drive, tape).
946 You can change the block size in the Storage Daemon configuration file.
948 \section{New {\bf Block Checksum} Device Directive}
949 You may now turn off the Block Checksum (CRC32) code
950 that Bacula uses when writing blocks to a Volume. This is
957 doing so can reduce the Storage daemon CPU usage slightly. It
958 will also permit Bacula to read a Volume that has corrupted data.
960 The default is {\bf yes} -- i.e. the checksum is computed on write
963 We do not recommend to turn this off particularly on older tape
964 drives or for disk Volumes where doing so may allow corrupted data
967 \section{New Bat Features}
969 Those new features were funded by Bacula Systems.
971 \subsection{Media List View}
973 By clicking on ``Media'', you can see the list of all your volumes. You will be
974 able to filter by Pool, Media Type, Location,\dots And sort the result directly
975 in the table. The old ``Media'' view is now known as ``Pool''.
978 \includegraphics[width=13cm]{\idir bat-mediaview.eps}
979 \label{fig:mediaview}
983 \subsection{Media Information View}
985 By double-clicking on a volume (on the Media list, in the Autochanger content
986 or in the Job information panel), you can access a detailed overview of your
987 Volume. (cf \ref{fig:mediainfo}.)
990 \includegraphics[width=13cm]{\idir bat11.eps}
991 \caption{Media information}
992 \label{fig:mediainfo}
995 \subsection{Job Information View}
997 By double-clicking on a Job record (on the Job run list or in the Media
998 information panel), you can access a detailed overview of your Job. (cf
1000 \begin{figure}[htbp]
1002 \includegraphics[width=13cm]{\idir bat12.eps}
1003 \caption{Job information}
1007 \subsection{Autochanger Content View}
1009 By double-clicking on a Storage record (on the Storage list panel), you can
1010 access a detailed overview of your Autochanger. (cf \ref{fig:jobinfo}.)
1011 \begin{figure}[htbp]
1013 \includegraphics[width=13cm]{\idir bat13.eps}
1014 \caption{Autochanger content}
1015 \label{fig:achcontent}
1018 To use this feature, you need to use the latest mtx-changer script
1019 version. (With new \texttt{listall} and \texttt{transfer} commands)
1021 \section{Bat on Windows}
1022 We have ported {\bf bat} to Windows and it is now installed
1023 by default when the installer is run. It works quite well
1024 on Win32, but has not had a lot of testing there, so your
1025 feedback would be welcome. Unfortunately, eventhough it is
1026 installed by default, it does not yet work on 64 bit Windows
1029 \section{New Win32 Installer}
1030 The Win32 installer has been modified in several very important
1033 \item You must deinstall any current version of the
1034 Win32 File daemon before upgrading to the new one.
1035 If you forget to do so, the new installation will fail.
1036 To correct this failure, you must manually shutdown
1037 and deinstall the old File daemon.
1038 \item All files (other than menu links) are installed
1039 in {\bf c:/Program Files/Bacula}.
1040 \item The installer no longer sets this
1041 file to require administrator privileges by default. If you want
1042 to do so, please do it manually using the {\bf cacls} program.
1045 cacls "C:\Program Files\Bacula" /T /G SYSTEM:F Administrators:F
1047 \item The server daemons (Director and Storage daemon) are
1048 no longer included in the Windows installer. If you want the
1049 Windows servers, you will either need to build them yourself (note
1050 they have not been ported to 64 bits), or you can contact
1051 Bacula Systems about this.
1054 \section{Win64 Installer}
1055 We have corrected a number of problems that required manual
1056 editing of the conf files. In most cases, it should now
1057 install and work. {\bf bat} is by default installed in
1058 {\bf c:/Program Files/Bacula/bin32} rather than
1059 {\bf c:/Program Files/Bacula} as is the case with the 32
1060 bit Windows installer.
1062 \section{Linux Bare Metal Recovery USB Key}
1063 We have made a number of significant improvements in the
1064 Bare Metal Recovery USB key. Please see the README files
1065 it the {\bf rescue} release for more details.
1067 We are working on an equivalent USB key for Windows bare
1068 metal recovery, but it will take some time to develop it (best
1069 estimate 3Q2010 or 4Q2010)
1072 \section{bconsole Timeout Option}
1073 You can now use the -u option of {\bf bconsole} to set a timeout in seconds
1074 for commands. This is useful with GUI programs that use {\bf bconsole}
1075 to interface to the Director.
1077 \section{Important Changes}
1078 \label{sec:importantchanges}
1081 \item You are now allowed to Migrate, Copy, and Virtual Full to read and write
1082 to the same Pool. The Storage daemon ensures that you do not read and
1083 write to the same Volume.
1084 \item The \texttt{Device Poll Interval} is now 5 minutes. (previously did not
1086 \item Virtually all the features of {\bf mtx-changer} have
1087 now been parameterized, which allows you to configure
1088 mtx-changer without changing it. There is a new configuration file {\bf mtx-changer.conf}
1089 that contains variables that you can set to configure mtx-changer.
1090 This configuration file will not be overwritten during upgrades.
1091 We encourage you to submit any changes
1092 that are made to mtx-changer and to parameterize it all in
1093 mtx-changer.conf so that all configuration will be done by
1094 changing only mtx-changer.conf.
1095 \item The new \texttt{mtx-changer} script has two new options, \texttt{listall}
1096 and \texttt{transfer}. Please configure them as appropriate
1097 in mtx-changer.conf.
1098 \item To enhance security of the \texttt{BackupCatalog} job, we provide a new
1099 script (\texttt{make\_catalog\_backup.pl}) that does not expose your catalog
1100 password. If you want to use the new script, you will need to
1101 manually change the \texttt{BackupCatalog} Job definition.
1102 \item The \texttt{bconsole} \texttt{help} command now accepts
1103 an argument, which if provided produces information on that
1104 command (ex: \texttt{help run}).
1108 \subsubsection*{Truncate volume after purge}
1110 Note that the Truncate Volume after purge feature doesn't work as expected
1111 in 5.0.0 version. Please, don't use it before version 5.0.1.
1113 \subsection{Custom Catalog queries}
1115 If you wish to add specialized commands that list the contents of the catalog,
1116 you can do so by adding them to the \texttt{query.sql} file. This
1117 \texttt{query.sql} file is now empty by default. The file
1118 \texttt{examples/sample-query.sql} has an a number of sample commands
1119 you might find useful.
1121 \subsection{Deprecated parts}
1123 The following items have been \textbf{deprecated} for a long time, and are now
1124 removed from the code.
1127 \item Support for SQLite 2
1130 \section{Misc Changes}
1131 \label{sec:miscchanges}
1134 \item Updated Nagios check\_bacula
1135 \item Updated man files
1136 \item Added OSX package generation script in platforms/darwin
1137 \item Added Spanish and Ukrainian Bacula translations
1138 \item Enable/disable command shows only Jobs that can change
1139 \item Added \texttt{show disabled} command to show disabled Jobs
1140 \item Many ACL improvements
1141 \item Added Level to FD status Job output
1142 \item Begin Ingres DB driver (not yet working)
1143 \item Split RedHat spec files into bacula, bat, mtx, and docs
1144 \item Reorganized the manuals (fewer separate manuals)
1145 \item Added lock/unlock order protection in lock manager
1146 \item Allow 64 bit sizes for a number of variables
1147 \item Fixed several deadlocks or potential race conditions in the SD
1150 \chapter{Released Version 3.0.3 and 3.0.3a}
1152 There are no new features in version 3.0.3. This version simply fixes a
1153 number of bugs found in version 3.0.2 during the onging development
1156 \chapter{New Features in Released Version 3.0.2}
1158 This chapter presents the new features added to the
1159 Released Bacula Version 3.0.2.
1161 \section{Full Restore from a Given JobId}
1162 \index[general]{Restore menu}
1164 This feature allows selecting a single JobId and having Bacula
1165 automatically select all the other jobs that comprise a full backup up to
1166 and including the selected date (through JobId).
1168 Assume we start with the following jobs:
1170 +-------+--------------+---------------------+-------+----------+------------+
1171 | jobid | client | starttime | level | jobfiles | jobbytes |
1172 +-------+--------------+---------------------+-------+----------+------------
1173 | 6 | localhost-fd | 2009-07-15 11:45:49 | I | 2 | 0 |
1174 | 5 | localhost-fd | 2009-07-15 11:45:45 | I | 15 | 44143 |
1175 | 3 | localhost-fd | 2009-07-15 11:45:38 | I | 1 | 10 |
1176 | 1 | localhost-fd | 2009-07-15 11:45:30 | F | 1527 | 44143073 |
1177 +-------+--------------+---------------------+-------+----------+------------+
1180 Below is an example of this new feature (which is number 12 in the
1185 To select the JobIds, you have the following choices:
1186 1: List last 20 Jobs run
1187 2: List Jobs where a given File is saved
1189 12: Select full restore to a specified Job date
1192 Select item: (1-13): 12
1193 Enter JobId to get the state to restore: 5
1194 Selecting jobs to build the Full state at 2009-07-15 11:45:45
1195 You have selected the following JobIds: 1,3,5
1197 Building directory tree for JobId(s) 1,3,5 ... +++++++++++++++++++
1198 1,444 files inserted into the tree.
1201 This project was funded by Bacula Systems.
1203 \section{Source Address}
1204 \index[general]{Source Address}
1206 A feature has been added which allows the administrator to specify the address
1207 from which the Director and File daemons will establish connections. This
1208 may be used to simplify system configuration overhead when working in complex
1209 networks utilizing multi-homing and policy-routing.
1211 To accomplish this, two new configuration directives have been implemented:
1214 FDSourceAddress=10.0.1.20 # Always initiate connections from this address
1218 DirSourceAddress=10.0.1.10 # Always initiate connections from this address
1222 Simply adding specific host routes on the OS
1223 would have an undesirable side-effect: any
1224 application trying to contact the destination host would be forced to use the
1225 more specific route possibly diverting management traffic onto a backup VLAN.
1226 Instead of adding host routes for each client connected to a multi-homed backup
1227 server (for example where there are management and backup VLANs), one can
1228 use the new directives to specify a specific source address at the application
1231 Additionally, this allows the simplification and abstraction of firewall rules
1232 when dealing with a Hot-Standby director or storage daemon configuration. The
1233 Hot-standby pair may share a CARP address, which connections must be sourced
1234 from, while system services listen and act from the unique interface addresses.
1236 This project was funded by Collaborative Fusion, Inc.
1238 \section{Show volume availability when doing restore}
1240 When doing a restore the selection dialog ends by displaying this
1244 The job will require the following
1245 Volume(s) Storage(s) SD Device(s)
1246 ===========================================================================
1247 *000741L3 LTO-4 LTO3
1248 *000866L3 LTO-4 LTO3
1249 *000765L3 LTO-4 LTO3
1250 *000764L3 LTO-4 LTO3
1251 *000756L3 LTO-4 LTO3
1252 *001759L3 LTO-4 LTO3
1253 *001763L3 LTO-4 LTO3
1257 Volumes marked with ``*'' are online (in the autochanger).
1260 This should help speed up large restores by minimizing the time spent
1261 waiting for the operator to discover that he must change tapes in the library.
1263 This project was funded by Bacula Systems.
1265 \section{Accurate estimate command}
1267 The \texttt{estimate} command can now use the accurate code to detect changes
1268 and give a better estimation.
1270 You can set the accurate behavior on the command line by using
1271 \texttt{accurate=yes\vb{}no} or use the Job setting as default value.
1274 * estimate listing accurate=yes level=incremental job=BackupJob
1277 This project was funded by Bacula Systems.
1279 \chapter{New Features in 3.0.0}
1280 \label{NewFeaturesChapter}
1281 \index[general]{New Features}
1283 This chapter presents the new features added to the development 2.5.x
1284 versions to be released as Bacula version 3.0.0 sometime in April 2009.
1286 \section{Accurate Backup}
1287 \index[general]{Accurate Backup}
1289 As with most other backup programs, by default Bacula decides what files to
1290 backup for Incremental and Differental backup by comparing the change
1291 (st\_ctime) and modification (st\_mtime) times of the file to the time the last
1292 backup completed. If one of those two times is later than the last backup
1293 time, then the file will be backed up. This does not, however, permit tracking
1294 what files have been deleted and will miss any file with an old time that may
1295 have been restored to or moved onto the client filesystem.
1297 \subsection{Accurate = \lt{}yes\vb{}no\gt{}}
1298 If the {\bf Accurate = \lt{}yes\vb{}no\gt{}} directive is enabled (default no) in
1299 the Job resource, the job will be run as an Accurate Job. For a {\bf Full}
1300 backup, there is no difference, but for {\bf Differential} and {\bf
1301 Incremental} backups, the Director will send a list of all previous files
1302 backed up, and the File daemon will use that list to determine if any new files
1303 have been added or or moved and if any files have been deleted. This allows
1304 Bacula to make an accurate backup of your system to that point in time so that
1305 if you do a restore, it will restore your system exactly.
1308 about using Accurate backup is that it requires more resources (CPU and memory)
1309 on both the Director and the Client machines to create the list of previous
1310 files backed up, to send that list to the File daemon, for the File daemon to
1311 keep the list (possibly very big) in memory, and for the File daemon to do
1312 comparisons between every file in the FileSet and the list. In particular,
1313 if your client has lots of files (more than a few million), you will need
1314 lots of memory on the client machine.
1316 Accurate must not be enabled when backing up with a plugin that is not
1317 specially designed to work with Accurate. If you enable it, your restores
1318 will probably not work correctly.
1320 This project was funded by Bacula Systems.
1325 \index[general]{Copy Jobs}
1327 A new {\bf Copy} job type 'C' has been implemented. It is similar to the
1328 existing Migration feature with the exception that the Job that is copied is
1329 left unchanged. This essentially creates two identical copies of the same
1330 backup. However, the copy is treated as a copy rather than a backup job, and
1331 hence is not directly available for restore. The {\bf restore} command lists
1332 copy jobs and allows selection of copies by using \texttt{jobid=}
1333 option. If the keyword {\bf copies} is present on the command line, Bacula will
1334 display the list of all copies for selected jobs.
1339 These JobIds have copies as follows:
1340 +-------+------------------------------------+-----------+------------------+
1341 | JobId | Job | CopyJobId | MediaType |
1342 +-------+------------------------------------+-----------+------------------+
1343 | 2 | CopyJobSave.2009-02-17_16.31.00.11 | 7 | DiskChangerMedia |
1344 +-------+------------------------------------+-----------+------------------+
1345 +-------+-------+----------+----------+---------------------+------------------+
1346 | JobId | Level | JobFiles | JobBytes | StartTime | VolumeName |
1347 +-------+-------+----------+----------+---------------------+------------------+
1348 | 19 | F | 6274 | 76565018 | 2009-02-17 16:30:45 | ChangerVolume002 |
1349 | 2 | I | 1 | 5 | 2009-02-17 16:30:51 | FileVolume001 |
1350 +-------+-------+----------+----------+---------------------+------------------+
1351 You have selected the following JobIds: 19,2
1353 Building directory tree for JobId(s) 19,2 ... ++++++++++++++++++++++++++++++++++++++++++++
1354 5,611 files inserted into the tree.
1359 The Copy Job runs without using the File daemon by copying the data from the
1360 old backup Volume to a different Volume in a different Pool. See the Migration
1361 documentation for additional details. For copy Jobs there is a new selection
1362 directive named {\bf PoolUncopiedJobs} which selects all Jobs that were
1363 not already copied to another Pool.
1365 As with Migration, the Client, Volume, Job, or SQL query, are
1366 other possible ways of selecting the Jobs to be copied. Selection
1367 types like SmallestVolume, OldestVolume, PoolOccupancy and PoolTime also
1368 work, but are probably more suited for Migration Jobs.
1370 If Bacula finds a Copy of a job record that is purged (deleted) from the catalog,
1371 it will promote the Copy to a \textsl{real} backup job and will make it available for
1372 automatic restore. If more than one Copy is available, it will promote the copy
1373 with the smallest JobId.
1375 A nice solution which can be built with the new Copy feature is often
1376 called disk-to-disk-to-tape backup (DTDTT). A sample config could
1377 look something like the one below:
1381 Name = FullBackupsVirtualPool
1383 Purge Oldest Volume = Yes
1385 NextPool = FullBackupsTapePool
1389 Name = FullBackupsTapePool
1393 Volume Retention = 365 days
1394 Storage = superloader
1398 # Fake fileset for copy jobs
1410 # Fake client for copy jobs
1420 # Default template for a CopyDiskToTape Job
1423 Name = CopyDiskToTape
1425 Messages = StandardCopy
1428 Selection Type = PoolUncopiedJobs
1429 Maximum Concurrent Jobs = 10
1431 Allow Duplicate Jobs = Yes
1432 Cancel Queued Duplicates = No
1433 Cancel Running Duplicates = No
1438 Name = DaySchedule7:00
1439 Run = Level=Full daily at 7:00
1443 Name = CopyDiskToTapeFullBackups
1445 Schedule = DaySchedule7:00
1446 Pool = FullBackupsVirtualPool
1447 JobDefs = CopyDiskToTape
1451 The example above had 2 pool which are copied using the PoolUncopiedJobs
1452 selection criteria. Normal Full backups go to the Virtual pool and are copied
1453 to the Tape pool the next morning.
1455 The command \texttt{list copies [jobid=x,y,z]} lists copies for a given
1460 +-------+------------------------------------+-----------+------------------+
1461 | JobId | Job | CopyJobId | MediaType |
1462 +-------+------------------------------------+-----------+------------------+
1463 | 9 | CopyJobSave.2008-12-20_22.26.49.05 | 11 | DiskChangerMedia |
1464 +-------+------------------------------------+-----------+------------------+
1467 \section{ACL Updates}
1468 \index[general]{ACL Updates}
1469 The whole ACL code had been overhauled and in this version each platforms has
1470 different streams for each type of acl available on such an platform. As ACLs
1471 between platforms tend to be not that portable (most implement POSIX acls but
1472 some use an other draft or a completely different format) we currently only
1473 allow certain platform specific ACL streams to be decoded and restored on the
1474 same platform that they were created on. The old code allowed to restore ACL
1475 cross platform but the comments already mention that not being to wise. For
1476 backward compatability the new code will accept the two old ACL streams and
1477 handle those with the platform specific handler. But for all new backups it
1478 will save the ACLs using the new streams.
1480 Currently the following platforms support ACLs:
1484 \item {\bf Darwin/OSX}
1493 Currently we support the following ACL types (these ACL streams use a reserved
1494 part of the stream numbers):
1497 \item {\bf STREAM\_ACL\_AIX\_TEXT} 1000 AIX specific string representation from
1499 \item {\bf STREAM\_ACL\_DARWIN\_ACCESS\_ACL} 1001 Darwin (OSX) specific acl\_t
1500 string representation from acl\_to\_text (POSIX acl)
1501 \item {\bf STREAM\_ACL\_FREEBSD\_DEFAULT\_ACL} 1002 FreeBSD specific acl\_t
1502 string representation from acl\_to\_text (POSIX acl) for default acls.
1503 \item {\bf STREAM\_ACL\_FREEBSD\_ACCESS\_ACL} 1003 FreeBSD specific acl\_t
1504 string representation from acl\_to\_text (POSIX acl) for access acls.
1505 \item {\bf STREAM\_ACL\_HPUX\_ACL\_ENTRY} 1004 HPUX specific acl\_entry
1506 string representation from acltostr (POSIX acl)
1507 \item {\bf STREAM\_ACL\_IRIX\_DEFAULT\_ACL} 1005 IRIX specific acl\_t string
1508 representation from acl\_to\_text (POSIX acl) for default acls.
1509 \item {\bf STREAM\_ACL\_IRIX\_ACCESS\_ACL} 1006 IRIX specific acl\_t string
1510 representation from acl\_to\_text (POSIX acl) for access acls.
1511 \item {\bf STREAM\_ACL\_LINUX\_DEFAULT\_ACL} 1007 Linux specific acl\_t
1512 string representation from acl\_to\_text (POSIX acl) for default acls.
1513 \item {\bf STREAM\_ACL\_LINUX\_ACCESS\_ACL} 1008 Linux specific acl\_t string
1514 representation from acl\_to\_text (POSIX acl) for access acls.
1515 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_ACL} 1009 Tru64 specific acl\_t
1516 string representation from acl\_to\_text (POSIX acl) for default acls.
1517 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_DIR\_ACL} 1010 Tru64 specific acl\_t
1518 string representation from acl\_to\_text (POSIX acl) for default acls.
1519 \item {\bf STREAM\_ACL\_TRU64\_ACCESS\_ACL} 1011 Tru64 specific acl\_t string
1520 representation from acl\_to\_text (POSIX acl) for access acls.
1521 \item {\bf STREAM\_ACL\_SOLARIS\_ACLENT} 1012 Solaris specific aclent\_t
1522 string representation from acltotext or acl\_totext (POSIX acl)
1523 \item {\bf STREAM\_ACL\_SOLARIS\_ACE} 1013 Solaris specific ace\_t string
1524 representation from from acl\_totext (NFSv4 or ZFS acl)
1527 In future versions we might support conversion functions from one type of acl
1528 into an other for types that are either the same or easily convertable. For now
1529 the streams are seperate and restoring them on a platform that doesn't
1530 recognize them will give you a warning.
1532 \section{Extended Attributes}
1533 \index[general]{Extended Attributes}
1534 Something that was on the project list for some time is now implemented for
1535 platforms that support a similar kind of interface. Its the support for backup
1536 and restore of so called extended attributes. As extended attributes are so
1537 platform specific these attributes are saved in seperate streams for each
1538 platform. Restores of the extended attributes can only be performed on the
1539 same platform the backup was done. There is support for all types of extended
1540 attributes, but restoring from one type of filesystem onto an other type of
1541 filesystem on the same platform may lead to supprises. As extended attributes
1542 can contain any type of data they are stored as a series of so called
1543 value-pairs. This data must be seen as mostly binary and is stored as such.
1544 As security labels from selinux are also extended attributes this option also
1545 stores those labels and no specific code is enabled for handling selinux
1548 Currently the following platforms support extended attributes:
1550 \item {\bf Darwin/OSX}
1556 On linux acls are also extended attributes, as such when you enable ACLs on a
1557 Linux platform it will NOT save the same data twice e.g. it will save the ACLs
1558 and not the same exteneded attribute.
1560 To enable the backup of extended attributes please add the following to your
1575 \section{Shared objects}
1576 \index[general]{Shared objects}
1577 A default build of Bacula will now create the libraries as shared objects
1578 (.so) rather than static libraries as was previously the case.
1579 The shared libraries are built using {\bf libtool} so it should be quite
1582 An important advantage of using shared objects is that on a machine with the
1583 Directory, File daemon, the Storage daemon, and a console, you will have only
1584 one copy of the code in memory rather than four copies. Also the total size of
1585 the binary release is smaller since the library code appears only once rather
1586 than once for every program that uses it; this results in significant reduction
1587 in the size of the binaries particularly for the utility tools.
1589 In order for the system loader to find the shared objects when loading the
1590 Bacula binaries, the Bacula shared objects must either be in a shared object
1591 directory known to the loader (typically /usr/lib) or they must be in the
1592 directory that may be specified on the {\bf ./configure} line using the {\bf
1593 {-}{-}libdir} option as:
1596 ./configure --libdir=/full-path/dir
1599 the default is /usr/lib. If {-}{-}libdir is specified, there should be
1600 no need to modify your loader configuration provided that
1601 the shared objects are installed in that directory (Bacula
1602 does this with the make install command). The shared objects
1603 that Bacula references are:
1612 These files are symbolically linked to the real shared object file,
1613 which has a version number to permit running multiple versions of
1614 the libraries if desired (not normally the case).
1616 If you have problems with libtool or you wish to use the old
1617 way of building static libraries, or you want to build a static
1618 version of Bacula you may disable
1619 libtool on the configure command line with:
1622 ./configure --disable-libtool
1626 \section{Building Static versions of Bacula}
1627 \index[general]{Static linking}
1628 In order to build static versions of Bacula, in addition
1629 to configuration options that were needed you now must
1630 also add --disable-libtool. Example
1633 ./configure --enable-static-client-only --disable-libtool
1637 \section{Virtual Backup (Vbackup)}
1638 \index[general]{Virtual Backup}
1639 \index[general]{Vbackup}
1641 Bacula's virtual backup feature is often called Synthetic Backup or
1642 Consolidation in other backup products. It permits you to consolidate the
1643 previous Full backup plus the most recent Differential backup and any
1644 subsequent Incremental backups into a new Full backup. This new Full
1645 backup will then be considered as the most recent Full for any future
1646 Incremental or Differential backups. The VirtualFull backup is
1647 accomplished without contacting the client by reading the previous backup
1648 data and writing it to a volume in a different pool.
1650 In some respects the Vbackup feature works similar to a Migration job, in
1651 that Bacula normally reads the data from the pool specified in the
1652 Job resource, and writes it to the {\bf Next Pool} specified in the
1653 Job resource. Note, this means that usually the output from the Virtual
1654 Backup is written into a different pool from where your prior backups
1655 are saved. Doing it this way guarantees that you will not get a deadlock
1656 situation attempting to read and write to the same volume in the Storage
1657 daemon. If you then want to do subsequent backups, you may need to
1658 move the Virtual Full Volume back to your normal backup pool.
1659 Alternatively, you can set your {\bf Next Pool} to point to the current
1660 pool. This will cause Bacula to read and write to Volumes in the
1661 current pool. In general, this will work, because Bacula will
1662 not allow reading and writing on the same Volume. In any case, once
1663 a VirtualFull has been created, and a restore is done involving the
1664 most current Full, it will read the Volume or Volumes by the VirtualFull
1665 regardless of in which Pool the Volume is found.
1667 The Vbackup is enabled on a Job by Job in the Job resource by specifying
1668 a level of {\bf VirtualFull}.
1670 A typical Job resource definition might look like the following:
1677 FileSet = "Full Set"
1684 # Default pool definition
1688 Recycle = yes # Automatically recycle Volumes
1689 AutoPrune = yes # Prune expired volumes
1690 Volume Retention = 365d # one year
1698 Recycle = yes # Automatically recycle Volumes
1699 AutoPrune = yes # Prune expired volumes
1700 Volume Retention = 365d # one year
1701 Storage = DiskChanger
1704 # Definition of file storage device
1709 Device = FileStorage
1711 Maximum Concurrent Jobs = 5
1714 # Definition of DDS Virtual tape disk storage device
1717 Address = localhost # N.B. Use a fully qualified name here
1719 Device = DiskChanger
1720 Media Type = DiskChangerMedia
1721 Maximum Concurrent Jobs = 4
1726 Then in bconsole or via a Run schedule, you would run the job as:
1729 run job=MyBackup level=Full
1730 run job=MyBackup level=Incremental
1731 run job=MyBackup level=Differential
1732 run job=MyBackup level=Incremental
1733 run job=MyBackup level=Incremental
1736 So providing there were changes between each of those jobs, you would end up
1737 with a Full backup, a Differential, which includes the first Incremental
1738 backup, then two Incremental backups. All the above jobs would be written to
1739 the {\bf Default} pool.
1741 To consolidate those backups into a new Full backup, you would run the
1745 run job=MyBackup level=VirtualFull
1748 And it would produce a new Full backup without using the client, and the output
1749 would be written to the {\bf Full} Pool which uses the Diskchanger Storage.
1751 If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
1754 Note, the Start and End time of the Virtual Full backup is set to the
1755 values for the last job included in the Virtual Full (in the above example,
1756 it is an Increment). This is so that if another incremental is done, which
1757 will be based on the Virtual Full, it will backup all files from the
1758 last Job included in the Virtual Full rather than from the time the Virtual
1759 Full was actually run.
1763 \section{Catalog Format}
1764 \index[general]{Catalog Format}
1765 Bacula 3.0 comes with some changes to the catalog format. The upgrade
1766 operation will convert the FileId field of the File table from 32 bits (max 4
1767 billion table entries) to 64 bits (very large number of items). The
1768 conversion process can take a bit of time and will likely DOUBLE THE SIZE of
1769 your catalog during the conversion. Also you won't be able to run jobs during
1770 this conversion period. For example, a 3 million file catalog will take 2
1771 minutes to upgrade on a normal machine. Please don't forget to make a valid
1772 backup of your database before executing the upgrade script. See the
1773 ReleaseNotes for additional details.
1775 \section{64 bit Windows Client}
1776 \index[general]{Win64 Client}
1777 Unfortunately, Microsoft's implementation of Volume Shadown Copy (VSS) on
1778 their 64 bit OS versions is not compatible with a 32 bit Bacula Client.
1779 As a consequence, we are also releasing a 64 bit version of the Bacula
1780 Windows Client (win64bacula-3.0.0.exe) that does work with VSS.
1781 These binaries should only be installed on 64 bit Windows operating systems.
1782 What is important is not your hardware but whether or not you have
1783 a 64 bit version of the Windows OS.
1785 Compared to the Win32 Bacula Client, the 64 bit release contains a few differences:
1787 \item Before installing the Win64 Bacula Client, you must totally
1788 deinstall any prior 2.4.x Client installation using the
1789 Bacula deinstallation (see the menu item). You may want
1790 to save your .conf files first.
1791 \item Only the Client (File daemon) is ported to Win64, the Director
1792 and the Storage daemon are not in the 64 bit Windows installer.
1793 \item bwx-console is not yet ported.
1794 \item bconsole is ported but it has not been tested.
1795 \item The documentation is not included in the installer.
1796 \item Due to Vista security restrictions imposed on a default installation
1797 of Vista, before upgrading the Client, you must manually stop
1798 any prior version of Bacula from running, otherwise the install
1800 \item Due to Vista security restrictions imposed on a default installation
1801 of Vista, attempting to edit the conf files via the menu items
1802 will fail. You must directly edit the files with appropriate
1803 permissions. Generally double clicking on the appropriate .conf
1804 file will work providing you have sufficient permissions.
1805 \item All Bacula files are now installed in
1806 {\bf C:/Program Files/Bacula} except the main menu items,
1807 which are installed as before. This vastly simplifies the installation.
1808 \item If you are running on a foreign language version of Windows, most
1809 likely {\bf C:/Program Files} does not exist, so you should use the
1810 Custom installation and enter an appropriate location to install
1812 \item The 3.0.0 Win32 Client continues to install files in the locations used
1813 by prior versions. For the next version we will convert it to use
1814 the same installation conventions as the Win64 version.
1817 This project was funded by Bacula Systems.
1820 \section{Duplicate Job Control}
1821 \index[general]{Duplicate Jobs}
1822 The new version of Bacula provides four new directives that
1823 give additional control over what Bacula does if duplicate jobs
1824 are started. A duplicate job in the sense we use it here means
1825 a second or subsequent job with the same name starts. This
1826 happens most frequently when the first job runs longer than expected because no
1827 tapes are available.
1829 The four directives each take as an argument a {\bf yes} or {\bf no} value and
1830 are specified in the Job resource.
1834 \subsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}}
1835 \index[general]{Allow Duplicate Jobs}
1836 If this directive is set to {\bf yes}, duplicate jobs will be run. If
1837 the directive is set to {\bf no} (default) then only one job of a given name
1838 may run at one time, and the action that Bacula takes to ensure only
1839 one job runs is determined by the other directives (see below).
1841 If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs
1842 are present and none of the three directives given below permit
1843 cancelling a job, then the current job (the second one started)
1846 \subsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}}
1847 \index[general]{Allow Higher Duplicates}
1848 This directive was in version 5.0.0, but does not work as
1849 expected. If used, it should always be set to no. In later versions
1850 of Bacula the directive is disabled (disregarded).
1852 \subsection{Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}}
1853 \index[general]{Cancel Running Duplicates}
1854 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1855 if this directive is set to {\bf yes} any job that is already running
1856 will be canceled. The default is {\bf no}.
1858 \subsection{Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}}
1859 \index[general]{Cancel Queued Duplicates}
1860 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1861 if this directive is set to {\bf yes} any job that is
1862 already queued to run but not yet running will be canceled.
1863 The default is {\bf no}.
1866 \section{TLS Authentication}
1867 \index[general]{TLS Authentication}
1868 In Bacula version 2.5.x and later, in addition to the normal Bacula
1869 CRAM-MD5 authentication that is used to authenticate each Bacula
1870 connection, you can specify that you want TLS Authentication as well,
1871 which will provide more secure authentication.
1873 This new feature uses Bacula's existing TLS code (normally used for
1874 communications encryption) to do authentication. To use it, you must
1875 specify all the TLS directives normally used to enable communications
1876 encryption (TLS Enable, TLS Verify Peer, TLS Certificate, ...) and
1879 \subsection{TLS Authenticate = yes}
1881 TLS Authenticate = yes
1884 in the main daemon configuration resource (Director for the Director,
1885 Client for the File daemon, and Storage for the Storage daemon).
1887 When {\bf TLS Authenticate} is enabled, after doing the CRAM-MD5
1888 authentication, Bacula will also do TLS authentication, then TLS
1889 encryption will be turned off, and the rest of the communication between
1890 the two Bacula daemons will be done without encryption.
1892 If you want to encrypt communications data, use the normal TLS directives
1893 but do not turn on {\bf TLS Authenticate}.
1895 \section{bextract non-portable Win32 data}
1896 \index[general]{bextract handles Win32 non-portable data}
1897 {\bf bextract} has been enhanced to be able to restore
1898 non-portable Win32 data to any OS. Previous versions were
1899 unable to restore non-portable Win32 data to machines that
1900 did not have the Win32 BackupRead and BackupWrite API calls.
1902 \section{State File updated at Job Termination}
1903 \index[general]{State File}
1904 In previous versions of Bacula, the state file, which provides a
1905 summary of previous jobs run in the {\bf status} command output was
1906 updated only when Bacula terminated, thus if the daemon crashed, the
1907 state file might not contain all the run data. This version of
1908 the Bacula daemons updates the state file on each job termination.
1910 \section{MaxFullInterval = \lt{}time-interval\gt{}}
1911 \index[general]{MaxFullInterval}
1912 The new Job resource directive {\bf Max Full Interval = \lt{}time-interval\gt{}}
1913 can be used to specify the maximum time interval between {\bf Full} backup
1914 jobs. When a job starts, if the time since the last Full backup is
1915 greater than the specified interval, and the job would normally be an
1916 {\bf Incremental} or {\bf Differential}, it will be automatically
1917 upgraded to a {\bf Full} backup.
1919 \section{MaxDiffInterval = \lt{}time-interval\gt{}}
1920 \index[general]{MaxDiffInterval}
1921 The new Job resource directive {\bf Max Diff Interval = \lt{}time-interval\gt{}}
1922 can be used to specify the maximum time interval between {\bf Differential} backup
1923 jobs. When a job starts, if the time since the last Differential backup is
1924 greater than the specified interval, and the job would normally be an
1925 {\bf Incremental}, it will be automatically
1926 upgraded to a {\bf Differential} backup.
1928 \section{Honor No Dump Flag = \lt{}yes\vb{}no\gt{}}
1929 \index[general]{MaxDiffInterval}
1930 On FreeBSD systems, each file has a {\bf no dump flag} that can be set
1931 by the user, and when it is set it is an indication to backup programs
1932 to not backup that particular file. This version of Bacula contains a
1933 new Options directive within a FileSet resource, which instructs Bacula to
1934 obey this flag. The new directive is:
1937 Honor No Dump Flag = yes\vb{}no
1940 The default value is {\bf no}.
1943 \section{Exclude Dir Containing = \lt{}filename-string\gt{}}
1944 \index[general]{IgnoreDir}
1945 The {\bf ExcludeDirContaining = \lt{}filename\gt{}} is a new directive that
1946 can be added to the Include section of the FileSet resource. If the specified
1947 filename ({\bf filename-string}) is found on the Client in any directory to be
1948 backed up, the whole directory will be ignored (not backed up). For example:
1951 # List of files to be backed up
1959 Exclude Dir Containing = .excludeme
1964 But in /home, there may be hundreds of directories of users and some
1965 people want to indicate that they don't want to have certain
1966 directories backed up. For example, with the above FileSet, if
1967 the user or sysadmin creates a file named {\bf .excludeme} in
1968 specific directories, such as
1971 /home/user/www/cache/.excludeme
1972 /home/user/temp/.excludeme
1975 then Bacula will not backup the two directories named:
1978 /home/user/www/cache
1982 NOTE: subdirectories will not be backed up. That is, the directive
1983 applies to the two directories in question and any children (be they
1984 files, directories, etc).
1987 \section{Bacula Plugins}
1988 \index[general]{Plugin}
1989 Support for shared object plugins has been implemented in the Linux, Unix
1990 and Win32 File daemons. The API will be documented separately in
1991 the Developer's Guide or in a new document. For the moment, there is
1992 a single plugin named {\bf bpipe} that allows an external program to
1993 get control to backup and restore a file.
1995 Plugins are also planned (partially implemented) in the Director and the
1998 \subsection{Plugin Directory}
1999 \index[general]{Plugin Directory}
2000 Each daemon (DIR, FD, SD) has a new {\bf Plugin Directory} directive that may
2001 be added to the daemon definition resource. The directory takes a quoted
2002 string argument, which is the name of the directory in which the daemon can
2003 find the Bacula plugins. If this directive is not specified, Bacula will not
2004 load any plugins. Since each plugin has a distinctive name, all the daemons
2005 can share the same plugin directory.
2007 \subsection{Plugin Options}
2008 \index[general]{Plugin Options}
2009 The {\bf Plugin Options} directive takes a quoted string
2010 arguement (after the equal sign) and may be specified in the
2011 Job resource. The options specified will be passed to all plugins
2012 when they are run. This each plugin must know what it is looking
2013 for. The value defined in the Job resource can be modified
2014 by the user when he runs a Job via the {\bf bconsole} command line
2017 Note: this directive may be specified, and there is code to modify
2018 the string in the run command, but the plugin options are not yet passed to
2019 the plugin (i.e. not fully implemented).
2021 \subsection{Plugin Options ACL}
2022 \index[general]{Plugin Options ACL}
2023 The {\bf Plugin Options ACL} directive may be specified in the
2024 Director's Console resource. It functions as all the other ACL commands
2025 do by permitting users running restricted consoles to specify a
2026 {\bf Plugin Options} that overrides the one specified in the Job
2027 definition. Without this directive restricted consoles may not modify
2030 \subsection{Plugin = \lt{}plugin-command-string\gt{}}
2031 \index[general]{Plugin}
2032 The {\bf Plugin} directive is specified in the Include section of
2033 a FileSet resource where you put your {\bf File = xxx} directives.
2044 Plugin = "bpipe:..."
2049 In the above example, when the File daemon is processing the directives
2050 in the Include section, it will first backup all the files in {\bf /home}
2051 then it will load the plugin named {\bf bpipe} (actually bpipe-dir.so) from
2052 the Plugin Directory. The syntax and semantics of the Plugin directive
2053 require the first part of the string up to the colon (:) to be the name
2054 of the plugin. Everything after the first colon is ignored by the File daemon but
2055 is passed to the plugin. Thus the plugin writer may define the meaning of the
2056 rest of the string as he wishes.
2058 Please see the next section for information about the {\bf bpipe} Bacula
2061 \section{The bpipe Plugin}
2062 \index[general]{The bpipe Plugin}
2063 The {\bf bpipe} plugin is provided in the directory src/plugins/fd/bpipe-fd.c of
2064 the Bacula source distribution. When the plugin is compiled and linking into
2065 the resulting dynamic shared object (DSO), it will have the name {\bf bpipe-fd.so}.
2066 Please note that this is a very simple plugin that was written for
2067 demonstration and test purposes. It is and can be used in production, but
2068 that was never really intended.
2070 The purpose of the plugin is to provide an interface to any system program for
2071 backup and restore. As specified above the {\bf bpipe} plugin is specified in
2072 the Include section of your Job's FileSet resource. The full syntax of the
2073 plugin directive as interpreted by the {\bf bpipe} plugin (each plugin is free
2074 to specify the sytax as it wishes) is:
2077 Plugin = "<field1>:<field2>:<field3>:<field4>"
2082 \item {\bf field1} is the name of the plugin with the trailing {\bf -fd.so}
2083 stripped off, so in this case, we would put {\bf bpipe} in this field.
2085 \item {\bf field2} specifies the namespace, which for {\bf bpipe} is the
2086 pseudo path and filename under which the backup will be saved. This pseudo
2087 path and filename will be seen by the user in the restore file tree.
2088 For example, if the value is {\bf /MYSQL/regress.sql}, the data
2089 backed up by the plugin will be put under that "pseudo" path and filename.
2090 You must be careful to choose a naming convention that is unique to avoid
2091 a conflict with a path and filename that actually exists on your system.
2093 \item {\bf field3} for the {\bf bpipe} plugin
2094 specifies the "reader" program that is called by the plugin during
2095 backup to read the data. {\bf bpipe} will call this program by doing a
2098 \item {\bf field4} for the {\bf bpipe} plugin
2099 specifies the "writer" program that is called by the plugin during
2100 restore to write the data back to the filesystem.
2103 Please note that for two items above describing the "reader" and "writer"
2104 fields, these programs are "executed" by Bacula, which
2105 means there is no shell interpretation of any command line arguments
2106 you might use. If you want to use shell characters (redirection of input
2107 or output, ...), then we recommend that you put your command or commands
2108 in a shell script and execute the script. In addition if you backup a
2109 file with the reader program, when running the writer program during
2110 the restore, Bacula will not automatically create the path to the file.
2111 Either the path must exist, or you must explicitly do so with your command
2112 or in a shell script.
2114 Putting it all together, the full plugin directive line might look
2118 Plugin = "bpipe:/MYSQL/regress.sql:mysqldump -f
2119 --opt --databases bacula:mysql"
2122 The directive has been split into two lines, but within the {\bf bacula-dir.conf} file
2123 would be written on a single line.
2125 This causes the File daemon to call the {\bf bpipe} plugin, which will write
2126 its data into the "pseudo" file {\bf /MYSQL/regress.sql} by calling the
2127 program {\bf mysqldump -f --opt --database bacula} to read the data during
2128 backup. The mysqldump command outputs all the data for the database named
2129 {\bf bacula}, which will be read by the plugin and stored in the backup.
2130 During restore, the data that was backed up will be sent to the program
2131 specified in the last field, which in this case is {\bf mysql}. When
2132 {\bf mysql} is called, it will read the data sent to it by the plugn
2133 then write it back to the same database from which it came ({\bf bacula}
2136 The {\bf bpipe} plugin is a generic pipe program, that simply transmits
2137 the data from a specified program to Bacula for backup, and then from Bacula to
2138 a specified program for restore.
2140 By using different command lines to {\bf bpipe},
2141 you can backup any kind of data (ASCII or binary) depending
2142 on the program called.
2144 \section{Microsoft Exchange Server 2003/2007 Plugin}
2145 \index[general]{Microsoft Exchange Server 2003/2007 Plugin}
2146 \subsection{Background}
2147 The Exchange plugin was made possible by a funded development project
2148 between Equiinet Ltd -- www.equiinet.com (many thanks) and Bacula Systems.
2149 The code for the plugin was written by James Harper, and the Bacula core
2150 code by Kern Sibbald. All the code for this funded development has become
2151 part of the Bacula project. Thanks to everyone who made it happen.
2153 \subsection{Concepts}
2154 Although it is possible to backup Exchange using Bacula VSS the Exchange
2155 plugin adds a good deal of functionality, because while Bacula VSS
2156 completes a full backup (snapshot) of Exchange, it does
2157 not support Incremental or Differential backups, restoring is more
2158 complicated, and a single database restore is not possible.
2160 Microsoft Exchange organises its storage into Storage Groups with
2161 Databases inside them. A default installation of Exchange will have a
2162 single Storage Group called 'First Storage Group', with two Databases
2163 inside it, "Mailbox Store (SERVER NAME)" and
2164 "Public Folder Store (SERVER NAME)",
2165 which hold user email and public folders respectively.
2167 In the default configuration, Exchange logs everything that happens to
2168 log files, such that if you have a backup, and all the log files since,
2169 you can restore to the present time. Each Storage Group has its own set
2170 of log files and operates independently of any other Storage Groups. At
2171 the Storage Group level, the logging can be turned off by enabling a
2172 function called "Enable circular logging". At this time the Exchange
2173 plugin will not function if this option is enabled.
2175 The plugin allows backing up of entire storage groups, and the restoring
2176 of entire storage groups or individual databases. Backing up and
2177 restoring at the individual mailbox or email item is not supported but
2178 can be simulated by use of the "Recovery" Storage Group (see below).
2180 \subsection{Installing}
2181 The Exchange plugin requires a DLL that is shipped with Microsoft
2182 Exchanger Server called {\bf esebcli2.dll}. Assuming Exchange is installed
2183 correctly the Exchange plugin should find this automatically and run
2184 without any additional installation.
2186 If the DLL can not be found automatically it will need to be copied into
2187 the Bacula installation
2188 directory (eg C:\verb+\+Program Files\verb+\+Bacula\verb+\+bin). The Exchange API DLL is
2189 named esebcli2.dll and is found in C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+bin on a
2190 default Exchange installation.
2192 \subsection{Backing Up}
2193 To back up an Exchange server the Fileset definition must contain at
2194 least {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"} for
2195 the backup to work correctly. The 'exchange:' bit tells Bacula to look
2196 for the exchange plugin, the '@EXCHANGE' bit makes sure all the backed
2197 up files are prefixed with something that isn't going to share a name
2198 with something outside the plugin, and the 'Microsoft Information Store'
2199 bit is required also. It is also possible to add the name of a storage
2200 group to the "Plugin =" line, eg \\
2201 {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"} \\
2202 if you want only a single storage group backed up.
2204 Additionally, you can suffix the 'Plugin =' directive with
2205 ":notrunconfull" which will tell the plugin not to truncate the Exchange
2206 database at the end of a full backup.
2208 An Incremental or Differential backup will backup only the database logs
2209 for each Storage Group by inspecting the "modified date" on each
2210 physical log file. Because of the way the Exchange API works, the last
2211 logfile backed up on each backup will always be backed up by the next
2212 Incremental or Differential backup too. This adds 5MB to each
2213 Incremental or Differential backup size but otherwise does not cause any
2216 By default, a normal VSS fileset containing all the drive letters will
2217 also back up the Exchange databases using VSS. This will interfere with
2218 the plugin and Exchange's shared ideas of when the last full backup was
2219 done, and may also truncate log files incorrectly. It is important,
2220 therefore, that the Exchange database files be excluded from the backup,
2221 although the folders the files are in should be included, or they will
2222 have to be recreated manually if a baremetal restore is done.
2227 File = C:/Program Files/Exchsrvr/mdbdata
2228 Plugin = "exchange:..."
2231 File = C:/Program Files/Exchsrvr/mdbdata/E00.chk
2232 File = C:/Program Files/Exchsrvr/mdbdata/E00.log
2233 File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log
2234 File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log
2235 File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log
2236 File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log
2237 File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb
2242 The advantage of excluding the above files is that you can significantly
2243 reduce the size of your backup since all the important Exchange files
2244 will be properly saved by the Plugin.
2247 \subsection{Restoring}
2248 The restore operation is much the same as a normal Bacula restore, with
2249 the following provisos:
2252 \item The {\bf Where} restore option must not be specified
2253 \item Each Database directory must be marked as a whole. You cannot just
2254 select (say) the .edb file and not the others.
2255 \item If a Storage Group is restored, the directory of the Storage Group
2257 \item It is possible to restore only a subset of the available log files,
2258 but they {\bf must} be contiguous. Exchange will fail to restore correctly
2259 if a log file is missing from the sequence of log files
2260 \item Each database to be restored must be dismounted and marked as "Can be
2261 overwritten by restore"
2262 \item If an entire Storage Group is to be restored (eg all databases and
2263 logs in the Storage Group), then it is best to manually delete the
2264 database files from the server (eg C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+mdbdata\verb+\+*)
2265 as Exchange can get confused by stray log files lying around.
2268 \subsection{Restoring to the Recovery Storage Group}
2269 The concept of the Recovery Storage Group is well documented by
2271 \elink{http://support.microsoft.com/kb/824126}{http://support.microsoft.com/kb/824126},
2272 but to briefly summarize...
2274 Microsoft Exchange allows the creation of an additional Storage Group
2275 called the Recovery Storage Group, which is used to restore an older
2276 copy of a database (e.g. before a mailbox was deleted) into without
2277 messing with the current live data. This is required as the Standard and
2278 Small Business Server versions of Exchange can not ordinarily have more
2279 than one Storage Group.
2281 To create the Recovery Storage Group, drill down to the Server in Exchange
2282 System Manager, right click, and select
2283 {\bf "New -> Recovery Storage Group..."}. Accept or change the file
2284 locations and click OK. On the Recovery Storage Group, right click and
2285 select {\bf "Add Database to Recover..."} and select the database you will
2288 Restore only the single database nominated as the database in the
2289 Recovery Storage Group. Exchange will redirect the restore to the
2290 Recovery Storage Group automatically.
2291 Then run the restore.
2293 \subsection{Restoring on Microsoft Server 2007}
2294 Apparently the {\bf Exmerge} program no longer exists in Microsoft Server
2295 2007, and henc you use a new proceedure for recovering a single mail box.
2296 This procedure is ducomented by Microsoft at:
2297 \elink{http://technet.microsoft.com/en-us/library/aa997694.aspx}{http://technet.microsoft.com/en-us/library/aa997694.aspx},
2298 and involves using the {\bf Restore-Mailbox} and {\bf
2299 Get-MailboxStatistics} shell commands.
2301 \subsection{Caveats}
2302 This plugin is still being developed, so you should consider it
2303 currently in BETA test, and thus use in a production environment
2304 should be done only after very careful testing.
2306 When doing a full backup, the Exchange database logs are truncated by
2307 Exchange as soon as the plugin has completed the backup. If the data
2308 never makes it to the backup medium (eg because of spooling) then the
2309 logs will still be truncated, but they will also not have been backed
2310 up. A solution to this is being worked on. You will have to schedule a
2311 new Full backup to ensure that your next backups will be usable.
2313 The "Enable Circular Logging" option cannot be enabled or the plugin
2316 Exchange insists that a successful Full backup must have taken place if
2317 an Incremental or Differential backup is desired, and the plugin will
2318 fail if this is not the case. If a restore is done, Exchange will
2319 require that a Full backup be done before an Incremental or Differential
2322 The plugin will most likely not work well if another backup application
2323 (eg NTBACKUP) is backing up the Exchange database, especially if the
2324 other backup application is truncating the log files.
2326 The Exchange plugin has not been tested with the {\bf Accurate} option, so
2327 we recommend either carefully testing or that you avoid this option for
2330 The Exchange plugin is not called during processing the bconsole {\bf
2331 estimate} command, and so anything that would be backed up by the plugin
2332 will not be added to the estimate total that is displayed.
2335 \section{libdbi Framework}
2336 \index[general]{libdbi Framework}
2337 As a general guideline, Bacula has support for a few catalog database drivers
2338 (MySQL, PostgreSQL, SQLite)
2339 coded natively by the Bacula team. With the libdbi implementation, which is a
2340 Bacula driver that uses libdbi to access the catalog, we have an open field to
2341 use many different kinds database engines following the needs of users.
2343 The according to libdbi (http://libdbi.sourceforge.net/) project: libdbi
2344 implements a database-independent abstraction layer in C, similar to the
2345 DBI/DBD layer in Perl. Writing one generic set of code, programmers can
2346 leverage the power of multiple databases and multiple simultaneous database
2347 connections by using this framework.
2349 Currently the libdbi driver in Bacula project only supports the same drivers
2350 natively coded in Bacula. However the libdbi project has support for many
2351 others database engines. You can view the list at
2352 http://libdbi-drivers.sourceforge.net/. In the future all those drivers can be
2353 supported by Bacula, however, they must be tested properly by the Bacula team.
2355 Some of benefits of using libdbi are:
2357 \item The possibility to use proprietary databases engines in which your
2358 proprietary licenses prevent the Bacula team from developing the driver.
2359 \item The possibility to use the drivers written for the libdbi project.
2360 \item The possibility to use other database engines without recompiling Bacula
2361 to use them. Just change one line in bacula-dir.conf
2362 \item Abstract Database access, this is, unique point to code and profiling
2363 catalog database access.
2366 The following drivers have been tested:
2368 \item PostgreSQL, with and without batch insert
2369 \item Mysql, with and without batch insert
2374 In the future, we will test and approve to use others databases engines
2375 (proprietary or not) like DB2, Oracle, Microsoft SQL.
2377 To compile Bacula to support libdbi we need to configure the code with the
2378 --with-dbi and --with-dbi-driver=[database] ./configure options, where
2379 [database] is the database engine to be used with Bacula (of course we can
2380 change the driver in file bacula-dir.conf, see below). We must configure the
2381 access port of the database engine with the option --with-db-port, because the
2382 libdbi framework doesn't know the default access port of each database.
2384 The next phase is checking (or configuring) the bacula-dir.conf, example:
2388 dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
2389 dbname = regress; user = regress; password = ""
2393 The parameter {\bf dbdriver} indicates that we will use the driver dbi with a
2394 mysql database. Currently the drivers supported by Bacula are: postgresql,
2395 mysql, sqlite, sqlite3; these are the names that may be added to string "dbi:".
2397 The following limitations apply when Bacula is set to use the libdbi framework:
2398 - Not tested on the Win32 platform
2399 - A little performance is lost if comparing with native database driver.
2400 The reason is bound with the database driver provided by libdbi and the
2401 simple fact that one more layer of code was added.
2403 It is important to remember, when compiling Bacula with libdbi, the
2404 following packages are needed:
2406 \item libdbi version 1.0.0, http://libdbi.sourceforge.net/
2407 \item libdbi-drivers 1.0.0, http://libdbi-drivers.sourceforge.net/
2410 You can download them and compile them on your system or install the packages
2411 from your OS distribution.
2413 \section{Console Command Additions and Enhancements}
2414 \index[general]{Console Additions}
2416 \subsection{Display Autochanger Content}
2417 \index[general]{StatusSlots}
2419 The {\bf status slots storage=\lt{}storage-name\gt{}} command displays
2420 autochanger content.
2424 Slot | Volume Name | Status | Media Type | Pool |
2425 ------+---------------+----------+-------------------+------------|
2426 1 | 00001 | Append | DiskChangerMedia | Default |
2427 2 | 00002 | Append | DiskChangerMedia | Default |
2428 3*| 00003 | Append | DiskChangerMedia | Scratch |
2433 If you an asterisk ({\bf *}) appears after the slot number, you must run an
2434 {\bf update slots} command to synchronize autochanger content with your
2437 \subsection{list joblog job=xxx or jobid=nnn}
2438 \index[general]{list joblog}
2439 A new list command has been added that allows you to list the contents
2440 of the Job Log stored in the catalog for either a Job Name (fully qualified)
2441 or for a particular JobId. The {\bf llist} command will include a line with
2442 the time and date of the entry.
2444 Note for the catalog to have Job Log entries, you must have a directive
2451 In your Director's {\bf Messages} resource.
2453 \subsection{Use separator for multiple commands}
2454 \index[general]{Command Separator}
2455 When using bconsole with readline, you can set the command separator with
2456 \textbf{@separator} command to one
2457 of those characters to write commands who require multiple input in one line.
2459 !$%&'()*+,-/:;<>?[]^`{|}~
2462 \subsection{Deleting Volumes}
2463 The delete volume bconsole command has been modified to
2464 require an asterisk (*) in front of a MediaId otherwise the
2465 value you enter is a taken to be a Volume name. This is so that
2466 users may delete numeric Volume names. The previous Bacula versions
2467 assumed that all input that started with a number was a MediaId.
2469 This new behavior is indicated in the prompt if you read it
2472 \section{Bare Metal Recovery}
2473 The old bare metal recovery project is essentially dead. One
2474 of the main features of it was that it would build a recovery
2475 CD based on the kernel on your system. The problem was that
2476 every distribution has a different boot procedure and different
2477 scripts, and worse yet, the boot procedures and scripts change
2478 from one distribution to another. This meant that maintaining
2479 (keeping up with the changes) the rescue CD was too much work.
2481 To replace it, a new bare metal recovery USB boot stick has been developed
2482 by Bacula Systems. This technology involves remastering a Ubuntu LiveCD to
2483 boot from a USB key.
2487 \item Recovery can be done from within graphical environment.
2488 \item Recovery can be done in a shell.
2489 \item Ubuntu boots on a large number of Linux systems.
2490 \item The process of updating the system and adding new
2491 packages is not too difficult.
2492 \item The USB key can easily be upgraded to newer Ubuntu versions.
2493 \item The USB key has writable partitions for modifications to
2494 the OS and for modification to your home directory.
2495 \item You can add new files/directories to the USB key very easily.
2496 \item You can save the environment from multiple machines on
2498 \item Bacula Systems is funding its ongoing development.
2501 The disadvantages are:
2503 \item The USB key is usable but currently under development.
2504 \item Not everyone may be familiar with Ubuntu (no worse
2506 \item Some older OSes cannot be booted from USB. This can
2507 be resolved by first booting a Ubuntu LiveCD then plugging
2509 \item Currently the documentation is sketchy and not yet added
2510 to the main manual. See below ...
2513 The documentation and the code can be found in the {\bf rescue} package
2514 in the directory {\bf linux/usb}.
2516 \section{Miscellaneous}
2517 \index[general]{Misc New Features}
2519 \subsection{Allow Mixed Priority = \lt{}yes\vb{}no\gt{}}
2520 \index[general]{Allow Mixed Priority}
2521 This directive is only implemented in version 2.5 and later. When
2522 set to {\bf yes} (default {\bf no}), this job may run even if lower
2523 priority jobs are already running. This means a high priority job
2524 will not have to wait for other jobs to finish before starting.
2525 The scheduler will only mix priorities when all running jobs have
2528 Note that only higher priority jobs will start early. Suppose the
2529 director will allow two concurrent jobs, and that two jobs with
2530 priority 10 are running, with two more in the queue. If a job with
2531 priority 5 is added to the queue, it will be run as soon as one of
2532 the running jobs finishes. However, new priority 10 jobs will not
2533 be run until the priority 5 job has finished.
2535 \subsection{Bootstrap File Directive -- FileRegex}
2536 \index[general]{Bootstrap File Directive}
2537 {\bf FileRegex} is a new command that can be added to the bootstrap
2538 (.bsr) file. The value is a regular expression. When specified, only
2539 matching filenames will be restored.
2541 During a restore, if all File records are pruned from the catalog
2542 for a Job, normally Bacula can restore only all files saved. That
2543 is there is no way using the catalog to select individual files.
2544 With this new feature, Bacula will ask if you want to specify a Regex
2545 expression for extracting only a part of the full backup.
2548 Building directory tree for JobId(s) 1,3 ...
2549 There were no files inserted into the tree, so file selection
2550 is not possible.Most likely your retention policy pruned the files
2552 Do you want to restore all the files? (yes\vb{}no): no
2554 Regexp matching files to restore? (empty to abort): /tmp/regress/(bin|tests)/
2555 Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr
2558 \subsection{Bootstrap File Optimization Changes}
2559 In order to permit proper seeking on disk files, we have extended the bootstrap
2560 file format to include a {\bf VolStartAddr} and {\bf VolEndAddr} records. Each
2561 takes a 64 bit unsigned integer range (i.e. nnn-mmm) which defines the start
2562 address range and end address range respectively. These two directives replace
2563 the {\bf VolStartFile}, {\bf VolEndFile}, {\bf VolStartBlock} and {\bf
2564 VolEndBlock} directives. Bootstrap files containing the old directives will
2565 still work, but will not properly take advantage of proper disk seeking, and
2566 may read completely to the end of a disk volume during a restore. With the new
2567 format (automatically generated by the new Director), restores will seek
2568 properly and stop reading the volume when all the files have been restored.
2570 \subsection{Solaris ZFS/NFSv4 ACLs}
2571 This is an upgrade of the previous Solaris ACL backup code
2572 to the new library format, which will backup both the old
2573 POSIX(UFS) ACLs as well as the ZFS ACLs.
2575 The new code can also restore POSIX(UFS) ACLs to a ZFS filesystem
2576 (it will translate the POSIX(UFS)) ACL into a ZFS/NFSv4 one) it can also
2577 be used to transfer from UFS to ZFS filesystems.
2580 \subsection{Virtual Tape Emulation}
2581 \index[general]{Virtual Tape Emulation}
2582 We now have a Virtual Tape emulator that allows us to run though 99.9\% of
2583 the tape code but actually reading and writing to a disk file. Used with the
2584 \textbf{disk-changer} script, you can now emulate an autochanger with 10 drives
2585 and 700 slots. This feature is most useful in testing. It is enabled
2586 by using {\bf Device Type = vtape} in the Storage daemon's Device
2587 directive. This feature is only implemented on Linux machines and should not be
2588 used for production.
2590 \subsection{Bat Enhancements}
2591 \index[general]{Bat Enhancements}
2592 Bat (the Bacula Administration Tool) GUI program has been significantly
2593 enhanced and stabilized. In particular, there are new table based status
2594 commands; it can now be easily localized using Qt4 Linguist.
2596 The Bat communications protocol has been significantly enhanced to improve
2597 GUI handling. Note, you {\bf must} use a the bat that is distributed with
2598 the Director you are using otherwise the communications protocol will not
2601 \subsection{RunScript Enhancements}
2602 \index[general]{RunScript Enhancements}
2603 The {\bf RunScript} resource has been enhanced to permit multiple
2604 commands per RunScript. Simply specify multiple {\bf Command} directives
2611 Command = "/bin/echo test"
2612 Command = "/bin/echo an other test"
2613 Command = "/bin/echo 3 commands in the same runscript"
2620 A new Client RunScript {\bf RunsWhen} keyword of {\bf AfterVSS} has been
2621 implemented, which runs the command after the Volume Shadow Copy has been made.
2623 Console commands can be specified within a RunScript by using:
2624 {\bf Console = \lt{}command\gt{}}, however, this command has not been
2625 carefully tested and debugged and is known to easily crash the Director.
2626 We would appreciate feedback. Due to the recursive nature of this command, we
2627 may remove it before the final release.
2629 \subsection{Status Enhancements}
2630 \index[general]{Status Enhancements}
2631 The bconsole {\bf status dir} output has been enhanced to indicate
2632 Storage daemon job spooling and despooling activity.
2634 \subsection{Connect Timeout}
2635 \index[general]{Connect Timeout}
2636 The default connect timeout to the File
2637 daemon has been set to 3 minutes. Previously it was 30 minutes.
2639 \subsection{ftruncate for NFS Volumes}
2640 \index[general]{ftruncate for NFS Volumes}
2641 If you write to a Volume mounted by NFS (say on a local file server),
2642 in previous Bacula versions, when the Volume was recycled, it was not
2643 properly truncated because NFS does not implement ftruncate (file
2644 truncate). This is now corrected in the new version because we have
2645 written code (actually a kind user) that deletes and recreates the Volume,
2646 thus accomplishing the same thing as a truncate.
2648 \subsection{Support for Ubuntu}
2649 The new version of Bacula now recognizes the Ubuntu (and Kubuntu)
2650 version of Linux, and thus now provides correct autostart routines.
2651 Since Ubuntu officially supports Bacula, you can also obtain any
2652 recent release of Bacula from the Ubuntu repositories.
2654 \subsection{Recycle Pool = \lt{}pool-name\gt{}}
2655 \index[general]{Recycle Pool}
2656 The new \textbf{RecyclePool} directive defines to which pool the Volume will
2657 be placed (moved) when it is recycled. Without this directive, a Volume will
2658 remain in the same pool when it is recycled. With this directive, it can be
2659 moved automatically to any existing pool during a recycle. This directive is
2660 probably most useful when defined in the Scratch pool, so that volumes will
2661 be recycled back into the Scratch pool.
2663 \subsection{FD Version}
2664 \index[general]{FD Version}
2665 The File daemon to Director protocol now includes a version
2666 number, which although there is no visible change for users,
2667 will help us in future versions automatically determine
2668 if a File daemon is not compatible.
2670 \subsection{Max Run Sched Time = \lt{}time-period-in-seconds\gt{}}
2671 \index[general]{Max Run Sched Time}
2672 The time specifies the maximum allowed time that a job may run, counted from
2673 when the job was scheduled. This can be useful to prevent jobs from running
2674 during working hours. We can see it like \texttt{Max Start Delay + Max Run
2677 \subsection{Max Wait Time = \lt{}time-period-in-seconds\gt{}}
2678 \index[general]{Max Wait Time}
2679 Previous \textbf{MaxWaitTime} directives aren't working as expected, instead
2680 of checking the maximum allowed time that a job may block for a resource,
2681 those directives worked like \textbf{MaxRunTime}. Some users are reporting to
2682 use \textbf{Incr/Diff/Full Max Wait Time} to control the maximum run time of
2683 their job depending on the level. Now, they have to use
2684 \textbf{Incr/Diff/Full Max Run Time}. \textbf{Incr/Diff/Full Max Wait Time}
2685 directives are now deprecated.
2687 \subsection{Incremental|Differential Max Wait Time = \lt{}time-period-in-seconds\gt{}}
2688 \index[general]{Incremental Max Wait Time}
2689 \index[general]{Differential Max Wait Time}
2691 These directives have been deprecated in favor of
2692 \texttt{Incremental|Differential Max Run Time}.
2694 \subsection{Max Run Time directives}
2695 \index[general]{Max Run Time directives}
2696 Using \textbf{Full/Diff/Incr Max Run Time}, it's now possible to specify the
2697 maximum allowed time that a job can run depending on the level.
2699 \addcontentsline{lof}{figure}{Job time control directives}
2700 \includegraphics{\idir different_time.eps}
2702 \subsection{Statistics Enhancements}
2703 \index[general]{Statistics Enhancements}
2704 If you (or probably your boss) want to have statistics on your backups to
2705 provide some \textit{Service Level Agreement} indicators, you could use a few
2706 SQL queries on the Job table to report how many:
2710 \item jobs have been successful
2711 \item files have been backed up
2715 However, these statistics are accurate only if your job retention is greater
2716 than your statistics period. Ie, if jobs are purged from the catalog, you won't
2717 be able to use them.
2719 Now, you can use the \textbf{update stats [days=num]} console command to fill
2720 the JobHistory table with new Job records. If you want to be sure to take in
2721 account only \textbf{good jobs}, ie if one of your important job has failed but
2722 you have fixed the problem and restarted it on time, you probably want to
2723 delete the first \textit{bad} job record and keep only the successful one. For
2724 that simply let your staff do the job, and update JobHistory table after two or
2725 three days depending on your organization using the \textbf{[days=num]} option.
2727 These statistics records aren't used for restoring, but mainly for
2728 capacity planning, billings, etc.
2730 The Bweb interface provides a statistics module that can use this feature. You
2731 can also use tools like Talend or extract information by yourself.
2733 The \textbf{Statistics Retention = \lt{}time\gt{}} director directive defines
2734 the length of time that Bacula will keep statistics job records in the Catalog
2735 database after the Job End time. (In \texttt{JobHistory} table) When this time
2736 period expires, and if user runs \texttt{prune stats} command, Bacula will
2737 prune (remove) Job records that are older than the specified period.
2739 You can use the following Job resource in your nightly \textbf{BackupCatalog}
2740 job to maintain statistics.
2743 Name = BackupCatalog
2746 Console = "update stats days=3"
2747 Console = "prune stats yes"
2754 \subsection{ScratchPool = \lt{}pool-resource-name\gt{}}
2755 \index[general]{ScratchPool}
2756 This directive permits to specify a specific \textsl{Scratch} pool for the
2757 current pool. This is useful when using multiple storage sharing the same
2758 mediatype or when you want to dedicate volumes to a particular set of pool.
2760 \subsection{Enhanced Attribute Despooling}
2761 \index[general]{Attribute Despooling}
2762 If the storage daemon and the Director are on the same machine, the spool file
2763 that contains attributes is read directly by the Director instead of being
2764 transmitted across the network. That should reduce load and speedup insertion.
2766 \subsection{SpoolSize = \lt{}size-specification-in-bytes\gt{}}
2767 \index[general]{SpoolSize}
2768 A new Job directive permits to specify the spool size per job. This is used
2769 in advanced job tunning. {\bf SpoolSize={\it bytes}}
2771 \subsection{MaximumConsoleConnections = \lt{}number\gt{}}
2772 \index[general]{MaximumConsoleConnections}
2773 A new director directive permits to specify the maximum number of Console
2774 Connections that could run concurrently. The default is set to 20, but you may
2775 set it to a larger number.
2777 \subsection{VerId = \lt{}string\gt{}}
2778 \index[general]{VerId}
2779 A new director directive permits to specify a personnal identifier that will be
2780 displayed in the \texttt{version} command.
2782 \subsection{dbcheck enhancements}
2783 \index[general]{dbcheck enhancements}
2784 If you are using Mysql, dbcheck will now ask you if you want to create
2785 temporary indexes to speed up orphaned Path and Filename elimination.
2787 A new \texttt{-B} option allows you to print catalog information in a simple
2788 text based format. This is useful to backup it in a secure way.
2803 You can now specify the database connection port in the command line.
2805 \subsection{{-}{-}docdir configure option}
2806 \index[general]{{-}{-}docdir configure option}
2807 You can use {-}{-}docdir= on the ./configure command to
2808 specify the directory where you want Bacula to install the
2809 LICENSE, ReleaseNotes, ChangeLog, ... files. The default is
2810 {\bf /usr/share/doc/bacula}.
2812 \subsection{{-}{-}htmldir configure option}
2813 \index[general]{{-}{-}htmldir configure option}
2814 You can use {-}{-}htmldir= on the ./configure command to
2815 specify the directory where you want Bacula to install the bat html help
2816 files. The default is {\bf /usr/share/doc/bacula/html}
2818 \subsection{{-}{-}with-plugindir configure option}
2819 \index[general]{{-}{-}plugindir configure option}
2820 You can use {-}{-}plugindir= on the ./configure command to
2821 specify the directory where you want Bacula to install
2822 the plugins (currently only bpipe-fd). The default is