1 \chapter{New Features in 5.2.x}
2 This chapter presents the new features that have been added to the next
3 Community version of Bacula that is not yet released.
5 \chapter{New Features in 5.2.2}
6 This chapter presents the new features that have been added to the current
7 Community version of Bacula that is now released.
9 \section{Additions to RunScript variables}
10 You can have access to Director name using \%D in your runscript
14 RunAfterJob = "/bin/echo Director=%D
17 \chapter{New Features in 5.2.1}
18 This chapter presents the new features were added in the
19 Community release version 5.2.1.
21 There are additional features (plugins) available in the Enterprise version
22 that are described in another chapter. A subscription to Bacula Systems
23 is required for the Enterprise version.
25 \section{LZO Compression}
27 LZO compression was added in the Unix File Daemon. From the user point of view,
28 it works like the GZIP compression (just replace {\bf compression=GZIP} with
29 {\bf compression=LZO}).
34 Options { compression=LZO }
40 LZO provides much faster compression and decompression speed but lower
41 compression ratio than GZIP. It is a good option when you backup to disk. For
42 tape, the built-in compression may be a better option.
44 LZO is a good altenative for GZIP1 when you don't want to slow down your
45 backup. On a modern CPU it should be able to run almost as fast as:
48 \item your client can read data from disk. Unless you have very fast disks like
49 SSD or large/fast RAID array.
50 \item the data transfers between the file daemon and the storage daemon even on
54 Note that bacula only use one compression level LZO1X-1.
57 The code for this feature was contributed by Laurent Papier.
59 \section{New Tray Monitor}
61 Since the old integrated Windows tray monitor doesn't work with
62 recent Windows versions, we have written a new Qt Tray Monitor that is available
63 for both Linux and Windows. In addition to all the previous features,
64 this new version allows you to run Backups from
65 the tray monitor menu.
69 \includegraphics[width=10cm]{\idir tray-monitor}
70 \label{fig:traymonitor}
71 \caption{New tray monitor}
76 \includegraphics[width=10cm]{\idir tray-monitor1}
77 \label{fig:traymonitor1}
78 \caption{Run a Job through the new tray monitor}
82 To be able to run a job from the tray monitor, you need to
83 allow specific commands in the Director monitor console:
88 CommandACL = status, .clients, .jobs, .pools, .storage, .filesets, .messages, run
89 ClientACL = *all* # you can restrict to a specific host
101 This project was funded by Bacula Systems and is available with Bacula
102 the Enterprise Edition and the Community Edition.
104 \section{Purge Migration Job}
106 The new {\bf Purge Migration Job} directive may be added to the Migration
107 Job definition in the Director's configuration file. When it is enabled
108 the Job that was migrated during a migration will be purged at
109 the end of the migration job.
117 Client = localhost-fd
120 Storage = DiskChanger
123 Selection Pattern = ".*Save"
125 Purge Migration Job = yes
131 This project was submited by Dunlap Blake; testing and documentation was funded
134 \section{Changes in Bvfs (Bacula Virtual FileSystem)}
136 Bat has now a bRestore panel that uses Bvfs to display files and
141 \includegraphics[width=12cm]{\idir bat-brestore}
142 \label{fig:batbrestore}
143 \caption{Bat Brestore Panel}
146 the Bvfs module works correctly with BaseJobs, Copy and Migration jobs.
149 This project was funded by Bacula Systems.
151 \subsection*{General notes}
154 \item All fields are separated by a tab
155 \item You can specify \texttt{limit=} and \texttt{offset=} to list smoothly
156 records in very big directories
157 \item All operations (except cache creation) are designed to run instantly
158 \item At this time, Bvfs works faster on PostgreSQL than MySQL catalog. If you
159 can contribute new faster SQL queries we will be happy, else don't complain
161 \item The cache creation is dependent of the number of directories. As Bvfs
162 shares information accross jobs, the first creation can be slow
163 \item All fields are separated by a tab
164 \item Due to potential encoding problem, it's advised to allways use pathid in
168 \subsection*{Get dependent jobs from a given JobId}
170 Bvfs allows you to query the catalog against any combination of jobs. You
171 can combine all Jobs and all FileSet for a Client in a single session.
173 To get all JobId needed to restore a particular job, you can use the
174 \texttt{.bvfs\_get\_jobids} command.
177 .bvfs_get_jobids jobid=num [all]
181 .bvfs_get_jobids jobid=10
183 .bvfs_get_jobids jobid=10 all
187 In this example, a normal restore will need to use JobIds 1,2,5,10 to
188 compute a complete restore of the system.
190 With the \texttt{all} option, the Director will use all defined FileSet for
193 \subsection*{Generating Bvfs cache}
195 The \texttt{.bvfs\_update} command computes the directory cache for jobs
196 specified in argument, or for all jobs if unspecified.
199 .bvfs_update [jobid=numlist]
204 .bvfs_update jobid=1,2,3
207 You can run the cache update process in a RunScript after the catalog backup.
209 \subsection*{Get all versions of a specific file}
211 Bvfs allows you to find all versions of a specific file for a given Client with
212 the \texttt{.bvfs\_version} command. To avoid problems with encoding, this
213 function uses only PathId and FilenameId. The jobid argument is mandatory but
217 .bvfs_versions client=filedaemon pathid=num filenameid=num jobid=1
218 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
219 PathId FilenameId FileId JobId LStat Md5 VolName Inchanger
226 .bvfs_versions client=localhost-fd pathid=1 fnid=47 jobid=1
227 1 47 52 12 gD HRid IGk D Po Po A P BAA I A /uPgWaxMgKZlnMti7LChyA Vol1 1
230 \subsection*{List directories}
232 Bvfs allows you to list directories in a specific path.
234 .bvfs_lsdirs pathid=num path=/apath jobid=numlist limit=num offset=num
235 PathId FilenameId FileId JobId LStat Path
236 PathId FilenameId FileId JobId LStat Path
237 PathId FilenameId FileId JobId LStat Path
241 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
242 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record
243 listed is a directory.
246 .bvfs_lsdirs pathid=4 jobid=1,11,12
247 4 0 0 0 A A A A A A A A A A A A A A .
248 5 0 0 0 A A A A A A A A A A A A A A ..
249 3 0 0 0 A A A A A A A A A A A A A A regress/
252 In this example, to list directories present in \texttt{regress/}, you can use
254 .bvfs_lsdirs pathid=3 jobid=1,11,12
255 3 0 0 0 A A A A A A A A A A A A A A .
256 4 0 0 0 A A A A A A A A A A A A A A ..
257 2 0 0 0 A A A A A A A A A A A A A A tmp/
260 \subsection*{List files}
262 Bvfs allows you to list files in a specific path.
264 .bvfs_lsfiles pathid=num path=/apath jobid=numlist limit=num offset=num
265 PathId FilenameId FileId JobId LStat Path
266 PathId FilenameId FileId JobId LStat Path
267 PathId FilenameId FileId JobId LStat Path
271 You need to \texttt{pathid} or \texttt{path}. Using \texttt{path=""} will list
272 ``/'' on Unix and all drives on Windows. If FilenameId is 0, the record listed
276 .bvfs_lsfiles pathid=4 jobid=1,11,12
277 4 0 0 0 A A A A A A A A A A A A A A .
278 5 0 0 0 A A A A A A A A A A A A A A ..
279 1 0 0 0 A A A A A A A A A A A A A A regress/
282 In this example, to list files present in \texttt{regress/}, you can use
284 .bvfs_lsfiles pathid=1 jobid=1,11,12
285 1 47 52 12 gD HRid IGk BAA I BMqcPH BMqcPE BMqe+t A titi
286 1 49 53 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B toto
287 1 48 54 12 gD HRie IGk BAA I BMqcPH BMqcPE BMqe+3 A tutu
288 1 45 55 12 gD HRid IGk BAA I BMqe/K BMqcPE BMqe+t B ficheriro1.txt
289 1 46 56 12 gD HRie IGk BAA I BMqe/K BMqcPE BMqe+3 D ficheriro2.txt
292 \subsection*{Restore set of files}
294 Bvfs allows you to create a SQL table that contains files that you want to
295 restore. This table can be provided to a restore command with the file option.
298 .bvfs_restore fileid=numlist dirid=numlist hardlink=numlist path=b2num
300 restore file=?b2num ...
303 To include a directory (with \texttt{dirid}), Bvfs needs to run a query to
304 select all files. This query could be time consuming.
306 \texttt{hardlink} list is always composed of a serie of two numbers (jobid,
307 fileindex). This information can be found in the LinkFI field of the LStat
310 The \texttt{path} argument represents the name of the table that Bvfs will
311 store results. The format of this table is \texttt{b2[0-9]+}. (Should start by
312 b2 and followed by digits).
317 .bvfs_restore fileid=1,2,3,4 hardlink=10,15,10,20 jobid=10 path=b20001
321 \subsection*{Cleanup after Restore}
323 To drop the table used by the restore command, you can use the
324 \texttt{.bvfs\_cleanup} command.
327 .bvfs_cleanup path=b20001
330 \subsection*{Clearing the BVFS Cache}
332 To clear the BVFS cache, you can use the \texttt{.bvfs\_clear_cache} command.
335 .bvfs_clear_cache yes
339 \section{Changes in the Pruning Algorithm}
341 We rewrote the job pruning algorithm in this version. Previously, in some users
342 reported that the pruning process at the end of jobs was very long. It should
343 not be longer the case. Now, Bacula won't prune automatically a Job if this
344 particular Job is needed to restore data. Example:
348 JobId: 2 Level: Incremental
349 JobId: 3 Level: Incremental
350 JobId: 4 Level: Differential
351 .. Other incrementals up to now
354 In this example, if the Job Retention defined in the Pool or in the Client
355 resource causes that Jobs with Jobid in 1,2,3,4 can be pruned, Bacula will
356 detect that JobId 1 and 4 are essential to restore data at the current state
357 and will prune only JobId 2 and 3.
359 \texttt{Important}, this change affect only the automatic pruning step after a
360 Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the
361 \texttt{VolumeRetention} period, important jobs can be pruned.
363 \section{Ability to Verify any specified Job}
364 You now have the ability to tell Bacula which Job should verify instead of
365 automatically verify just the last one.
367 This feature can be used with VolumeToCatalog, DiskToCatalog and Catalog level.
369 To verify a given job, just specify the Job jobid in argument when starting the
372 *run job=VerifyVolume jobid=1 level=VolumeToCatalog
374 JobName: VerifyVolume
375 Level: VolumeToCatalog
378 Pool: Default (From Job resource)
379 Storage: File (From Job resource)
380 Verify Job: VerifyVol.2010-09-08_14.17.17_03
381 Verify List: /tmp/regress/working/VerifyVol.bsr
382 When: 2010-09-08 14:17:31
384 OK to run? (yes/mod/no):
388 This project was funded by Bacula Systems and is available with Bacula
389 Enterprise Edition and Community Edition.
391 \section{Additions to RunScript variables}
392 You can have access to JobBytes and JobFiles using \%b and \%F in your runscript
393 command. The Client address is now available through \%h.
396 RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%F ClientAddress=%h"
399 %\section{Changes in drivetype.exe}
401 %Now the \texttt{drivetype.exe} program allows you to list all local hard
402 %drives. It can help to build dynamic FileSet on Windows.
405 %File = "\\|\"c:/program files/bacula/bin32/drivetype\" -l -a"
409 \section{Additions to the Plugin API}
410 The bfuncs structure has been extended to include a number of
414 The bFuncs structure defines the callback entry points within Bacula
415 that the plugin can use register events, get Bacula values, set
416 Bacula values, and send messages to the Job output or debug output.
418 The exact definition as of this writing is:
420 typedef struct s_baculaFuncs {
423 bRC (*registerBaculaEvents)(bpContext *ctx, ...);
424 bRC (*getBaculaValue)(bpContext *ctx, bVariable var, void *value);
425 bRC (*setBaculaValue)(bpContext *ctx, bVariable var, void *value);
426 bRC (*JobMessage)(bpContext *ctx, const char *file, int line,
427 int type, utime_t mtime, const char *fmt, ...);
428 bRC (*DebugMessage)(bpContext *ctx, const char *file, int line,
429 int level, const char *fmt, ...);
430 void *(*baculaMalloc)(bpContext *ctx, const char *file, int line,
432 void (*baculaFree)(bpContext *ctx, const char *file, int line, void *mem);
434 /* New functions follow */
435 bRC (*AddExclude)(bpContext *ctx, const char *file);
436 bRC (*AddInclude)(bpContext *ctx, const char *file);
437 bRC (*AddIncludeOptions)(bpContext *ctx, const char *opts);
438 bRC (*AddRegex)(bpContext *ctx, const char *item, int type);
439 bRC (*AddWild)(bpContext *ctx, const char *item, int type);
440 bRC (*checkChanges)(bpContext *ctx, struct save_pkt *sp);
446 \item [AddExclude] can be called to exclude a file. The file
447 string passed may include wildcards that will be interpreted by
448 the {\bf fnmatch} subroutine. This function can be called
449 multiple times, and each time the file specified will be added
450 to the list of files to be excluded. Note, this function only
451 permits adding excludes of specific file or directory names,
452 or files matched by the rather simple fnmatch mechanism.
453 See below for information on doing wild-card and regex excludes.
455 \item [NewInclude] can be called to create a new Include block. This
456 block will be added before any user defined Include blocks. This
457 function can be called multiple times, but each time, it will create
458 a new Include section (not normally needed). This function should
459 be called only if you want to add an entirely new Include block.
461 \item [AddInclude] can be called to add new files/directories to
462 be included. They are added to the current Include block. If
463 NewInclude has not been included, the current Include block is
464 the last one that the user created. This function
465 should be used only if you want to add totally new files/directories
466 to be included in the backup.
468 \item [NewOptions] adds a new Options block to the current Include
469 in front of any other Options blocks. This permits the plugin to
470 add exclude directives (wild-cards and regexes) in front of the
471 user Options, and thus prevent certain files from being backed up.
472 This can be useful if the plugin backs up files, and they should
473 not be also backed up by the main Bacula code. This function
474 may be called multiple times, and each time, it creates a new
475 prepended Options block. Note: normally you want to call this
476 entry point prior to calling AddOptions, AddRegex, or AddWild.
478 \item [AddOptions] allows the plugin it set options in
479 the current Options block, which is normally created with the
480 NewOptions call just prior to adding Include Options.
481 The permitted options are passed as a character string, where
482 each character has a specific meaning as defined below:
485 \item [a] always replace files (default).
486 \item [e] exclude rather than include.
487 \item [h] no recursion into subdirectories.
488 \item [H] do not handle hard links.
489 \item [i] ignore case in wildcard and regex matches.
490 \item [M] compute an MD5 sum.
491 \item [p] use a portable data format on Windows (not recommended).
492 \item [R] backup resource forks and Findr Info.
493 \item [r] read from a fifo
494 \item [S1] compute an SHA1 sum.
495 \item [S2] compute an SHA256 sum.
496 \item [S3] comput an SHA512 sum.
497 \item [s] handle sparse files.
498 \item [m] use st\_mtime only for file differences.
499 \item [k] restore the st\_atime after accessing a file.
500 \item [A] enable ACL backup.
501 \item [Vxxx:] specify verify options. Must terminate with :
502 \item [Cxxx:] specify accurate options. Must terminate with :
503 \item [Jxxx:] specify base job Options. Must terminate with :
504 \item [Pnnn:] specify integer nnn paths to strip. Must terminate with :
506 \item [Zn] specify gzip compression level n.
507 \item [K] do not use st\_atime in backup decision.
508 \item [c] check if file changed during backup.
509 \item [N] honor no dump flag.
510 \item [X] enable backup of extended attributes.
513 \item [AddRegex] adds a regex expression to the current Options block.
514 The fillowing options are permitted:
516 \item [ ] (a blank) regex applies to whole path and filename.
517 \item [F] regex applies only to the filename (directory or path stripped).
518 \item [D] regex applies only to the directory (path) part of the name.
521 \item [AddWild] adds a wildcard expression to the current Options block.
522 The fillowing options are permitted:
524 \item [ ] (a blank) regex applies to whole path and filename.
525 \item [F] regex applies only to the filename (directory or path stripped).
526 \item [D] regex applies only to the directory (path) part of the name.
529 \item [checkChanges] call the \texttt{check\_changes()} function in Bacula code
530 that can use Accurate code to compare the file information in argument with
531 the previous file information. The \texttt{delta\_seq} attribute of the
532 \texttt{save\_pkt} will be updated, and the call will return
533 \texttt{bRC\_Seen} if the core code wouldn't decide to backup it.
538 \subsection{Bacula events}
539 The list of events has been extended to include:
545 bEventStartBackupJob = 3,
546 bEventEndBackupJob = 4,
547 bEventStartRestoreJob = 5,
548 bEventEndRestoreJob = 6,
549 bEventStartVerifyJob = 7,
550 bEventEndVerifyJob = 8,
551 bEventBackupCommand = 9,
552 bEventRestoreCommand = 10,
557 bEventCancelCommand = 13,
558 bEventVssBackupAddComponents = 14,
559 bEventVssRestoreLoadComponentMetadata = 15,
560 bEventVssRestoreSetComponentsSelected = 16,
561 bEventRestoreObject = 17,
562 bEventEndFileSet = 18,
563 bEventPluginCommand = 19,
564 bEventVssBeforeCloseRestore = 20,
565 bEventVssPrepareSnapshot = 21
571 \item [bEventCancelCommand] is called whenever the currently
572 running Job is cancelled */
574 \item [bEventVssBackupAddComponents]
576 \item [bEventVssPrepareSnapshot] is called before creating VSS snapshots, it
577 provides a char[27] table where the plugin can add Windows drives that will
578 be used during the Job. You need to add them without duplicates, and you can
579 use in \texttt{fd\_common.h} \texttt{add\_drive()} and \texttt{copy\_drives()}
583 \section{ACL enhancements}
585 The following enhancements are made to the Bacula Filed with regards to
586 Access Control Lists (ACLs)
589 \item Added support for AIX 5.3 and later new aclx\_get interface which supports
590 POSIX and NFSv4 ACLs.
591 \item Added support for new acl types on FreeBSD 8.1 and later which supports
592 POSIX and NFSv4 ACLs.
593 \item Some generic cleanups for internal ACL handling.
594 \item Fix for acl storage on OSX
595 \item Cleanup of configure checks for ACL detection, now configure only
596 tests for a certain interface type based on the operating system
597 this should give less false possitives on detection. Also when acls
598 are detected no other acl checks are performed anymore.
602 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
603 and is available with Bacula Enterprise Edition and Community Edition.
605 \section{XATTR enhancements}
607 The following enhancements are made to the Bacula Filed with regards to
608 Extended Attributes (XATTRs)
611 \item Added support for IRIX extended attributes using the attr\_get interface.
612 \item Added support for Tru64 (OSF1) extended attributes using the
613 getproplist interface.
614 \item Added support for AIX extended attributes available in AIX 6.x
615 and higher using the listea/getea/setea interface.
616 \item Added some debugging to generic xattr code so it easier to
618 \item Cleanup of configure checks for XATTR detection, now configure only
619 tests for a certain interface type based on the operating system
620 this should give less false possitives on detection. Also when xattrs
621 are detected no other xattr checks are performed anymore.
625 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
626 and is available with Bacula Enterprise Edition and Community Edition.
628 \section{Class Based Database Backend Drivers}
630 The main Bacula Director code is independent of the SQL backend
631 in version 5.2.0 and greater. This means that the Bacula Director can be
632 packaged by itself, then each of the different SQL backends supported can
633 be packaged separately. It is possible to build all the DB backends at the
634 same time by including multiple database options at the same time.
636 ./configure can be run with multiple database configure options.
643 Order of testing for databases is:
650 Each configured backend generates a file named:
651 \verb+libbaccats-<sql_backend_name>-<version>.so+
652 A dummy catalog library is created named libbaccats-version.so
654 At configure time the first detected backend is used as the so called
655 default backend and at install time the dummy
656 \verb+libbaccats-<version>.so+ is replaced with the default backend type.
658 If you configure all three backends you get three backend libraries and the
659 postgresql gets installed as the default.
661 When you want to switch to another database, first save any old catalog you
662 may have then you can copy one of the three backend libraries over the
663 \verb+libbaccats-<version>.so+ e.g.
665 An actual command, depending on your Bacula version might be:
667 cp libbaccats-postgresql-5.2.2.so libbaccats-5.2.2.so
670 where the \verb+5.2.2+ must be replaced by the Bacula release
673 Then you must update the default backend in the following files:
676 create_bacula_database
679 grant_bacula_privileges
685 And re-run all the above scripts. Please note, this means
686 you will have a new empty database and if you had a previous
689 All current database backend drivers for catalog information are rewritten
690 to use a set of multi inherited C++ classes which abstract the specific
691 database specific internals and make sure we have a more stable generic
692 interface with the rest of sql code. From now on there is a strict
693 boundery between the SQL code and the low-level database functions. This
694 new interface should also make it easier to add a new backend for a
695 currently unsupported database. As part of the rewrite the SQLite 2 code
696 was removed (e.g. only SQLite 3 is now supported). An extra bonus of the
697 new code is that you can configure multiple backends in the configure and
698 build all backends in one compile session and select the correct database
699 backend at install time. This should make it a lot easier for packages
705 We also added cursor support for PostgreSQL backend, this improves memory
706 usage for large installation.
709 This project was implemented by Planets Communications B.V. and ELM
710 Consultancy B.V. and Bacula Systems and is available with both the Bacula
711 Enterprise Edition and the Community Edition.
713 \section{Hash List Enhancements}
715 The htable hash table class has been extended with extra hash functions for
716 handling next to char pointer hashes also 32 bits and 64 bits hash keys.
717 Also the hash table initialization routines have been enhanced with
718 support for passing a hint as to the number of initial pages to use
719 for the size of the hash table. Until now the hash table always used
720 a fixed value of 10 Mb. The private hash functions of the mountpoint entry
721 cache have been rewritten to use the new htable class with a small memory
725 This project was funded by Planets Communications B.V. and ELM Consultancy B.V.
726 and Bacula Systems and is available with Bacula Enterprise Edition and
731 %%% =====================================================================
736 \chapter{Release Version 5.0.3}
738 There are no new features in version 5.0.2. This version simply fixes a
739 number of bugs found in version 5.0.1 during the onging development
742 \chapter{Release Version 5.0.2}
744 There are no new features in version 5.0.2. This version simply fixes a
745 number of bugs found in version 5.0.1 during the onging development
751 \chapter{New Features in 5.0.1}
753 This chapter presents the new features that are in the released Bacula version
754 5.0.1. This version mainly fixes a number of bugs found in version 5.0.0 during
755 the onging development process.
757 \section{Truncate Volume after Purge}
758 \label{sec:actiononpurge}
760 The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate
761 the volume when it is purged with the new command \texttt{purge volume
762 action}. It is useful to prevent disk based volumes from consuming too much
768 Action On Purge = Truncate
773 As usual you can also set this property with the \texttt{update volume} command
775 *update volume=xxx ActionOnPurge=Truncate
776 *update volume=xxx actiononpurge=None
779 To ask Bacula to truncate your \texttt{Purged} volumes, you need to use the
780 following command in interactive mode or in a RunScript as shown after:
782 *purge volume action=truncate storage=File allpools
783 # or by default, action=all
784 *purge volume action storage=File pool=Default
787 This is possible to specify the volume name, the media type, the pool, the
788 storage, etc\dots (see \texttt{help purge}) Be sure that your storage device is
789 idle when you decide to run this command.
798 Console = "purge volume action=all allpools storage=File"
803 \textbf{Important note}: This feature doesn't work as
804 expected in version 5.0.0. Please do not use it before version 5.0.1.
806 \section{Allow Higher Duplicates}
807 This directive did not work correctly and has been depreciated
808 (disabled) in version 5.0.1. Please remove it from your bacula-dir.conf
809 file as it will be removed in a future rlease.
811 \section{Cancel Lower Level Duplicates}
812 This directive was added in Bacula version 5.0.1. It compares the
813 level of a new backup job to old jobs of the same name, if any,
814 and will kill the job which has a lower level than the other one.
815 If the levels are the same (i.e. both are Full backups), then
816 nothing is done and the other Cancel XXX Duplicate directives
819 \chapter{New Features in 5.0.0}
821 \section{Maximum Concurrent Jobs for Devices}
822 \label{sec:maximumconcurrentjobdevice}
824 {\bf Maximum Concurrent Jobs} is a new Device directive in the Storage
825 Daemon configuration permits setting the maximum number of Jobs that can
826 run concurrently on a specified Device. Using this directive, it is
827 possible to have different Jobs using multiple drives, because when the
828 Maximum Concurrent Jobs limit is reached, the Storage Daemon will start new
829 Jobs on any other available compatible drive. This facilitates writing to
830 multiple drives with multiple Jobs that all use the same Pool.
832 This project was funded by Bacula Systems.
834 \section{Restore from Multiple Storage Daemons}
835 \index[general]{Restore}
837 Previously, you were able to restore from multiple devices in a single Storage
838 Daemon. Now, Bacula is able to restore from multiple Storage Daemons. For
839 example, if your full backup runs on a Storage Daemon with an autochanger, and
840 your incremental jobs use another Storage Daemon with lots of disks, Bacula
841 will switch automatically from one Storage Daemon to an other within the same
844 You must upgrade your File Daemon to version 3.1.3 or greater to use this
847 This project was funded by Bacula Systems with the help of Equiinet.
849 \section{File Deduplication using Base Jobs}
850 A base job is sort of like a Full save except that you will want the FileSet to
851 contain only files that are unlikely to change in the future (i.e. a snapshot
852 of most of your system after installing it). After the base job has been run,
853 when you are doing a Full save, you specify one or more Base jobs to be used.
854 All files that have been backed up in the Base job/jobs but not modified will
855 then be excluded from the backup. During a restore, the Base jobs will be
856 automatically pulled in where necessary.
858 This is something none of the competition does, as far as we know (except
859 perhaps BackupPC, which is a Perl program that saves to disk only). It is big
860 win for the user, it makes Bacula stand out as offering a unique optimization
861 that immediately saves time and money. Basically, imagine that you have 100
862 nearly identical Windows or Linux machine containing the OS and user files.
863 Now for the OS part, a Base job will be backed up once, and rather than making
864 100 copies of the OS, there will be only one. If one or more of the systems
865 have some files updated, no problem, they will be automatically restored.
867 See the \ilink{Base Job Chapter}{basejobs} for more information.
869 This project was funded by Bacula Systems.
871 \section{AllowCompression = \lt{}yes\vb{}no\gt{}}
872 \index[dir]{AllowCompression}
874 This new directive may be added to Storage resource within the Director's
875 configuration to allow users to selectively disable the client compression for
876 any job which writes to this storage resource.
882 Address = ultrium-tape
883 Password = storage_password # Password for Storage Daemon
886 AllowCompression = No # Tape drive has hardware compression
889 The above example would cause any jobs running with the UltriumTape storage
890 resource to run without compression from the client file daemons. This
891 effectively overrides any compression settings defined at the FileSet level.
893 This feature is probably most useful if you have a tape drive which supports
894 hardware compression. By setting the \texttt{AllowCompression = No} directive
895 for your tape drive storage resource, you can avoid additional load on the file
896 daemon and possibly speed up tape backups.
898 This project was funded by Collaborative Fusion, Inc.
900 \section{Accurate Fileset Options}
901 \label{sec:accuratefileset}
903 In previous versions, the accurate code used the file creation and modification
904 times to determine if a file was modified or not. Now you can specify which
905 attributes to use (time, size, checksum, permission, owner, group, \dots),
906 similar to the Verify options.
922 \item {\bf i} compare the inodes
923 \item {\bf p} compare the permission bits
924 \item {\bf n} compare the number of links
925 \item {\bf u} compare the user id
926 \item {\bf g} compare the group id
927 \item {\bf s} compare the size
928 \item {\bf a} compare the access time
929 \item {\bf m} compare the modification time (st\_mtime)
930 \item {\bf c} compare the change time (st\_ctime)
931 \item {\bf d} report file size decreases
932 \item {\bf 5} compare the MD5 signature
933 \item {\bf 1} compare the SHA1 signature
936 \textbf{Important note:} If you decide to use checksum in Accurate jobs,
937 the File Daemon will have to read all files even if they normally would not
938 be saved. This increases the I/O load, but also the accuracy of the
939 deduplication. By default, Bacula will check modification/creation time
942 This project was funded by Bacula Systems.
944 \section{Tab-completion for Bconsole}
945 \label{sec:tabcompletion}
947 If you build \texttt{bconsole} with readline support, you will be able to use
948 the new auto-completion mode. This mode supports all commands, gives help
949 inside command, and lists resources when required. It works also in the restore
952 To use this feature, you should have readline development package loaded on
953 your system, and use the following option in configure.
955 ./configure --with-readline=/usr/include/readline --disable-conio ...
958 The new bconsole won't be able to tab-complete with older directors.
960 This project was funded by Bacula Systems.
962 \section{Pool File and Job Retention}
963 \label{sec:poolfilejobretention}
965 We added two new Pool directives, \texttt{FileRetention} and
966 \texttt{JobRetention}, that take precedence over Client directives of the same
967 name. It allows you to control the Catalog pruning algorithm Pool by Pool. For
968 example, you can decide to increase Retention times for Archive or OffSite Pool.
970 It seems obvious to us, but apparently not to some users, that given the
971 definition above that the Pool File and Job Retention periods is a global
972 override for the normal Client based prunning, which means that when the
973 Job is prunned, the prunning will apply globally to that particular Job.
975 Currently, there is a bug in the implementation that causes any Pool
976 retention periods specified to apply to {\bf all} Pools for that
977 particular Client. Thus we suggest that you avoid using these two
978 directives until this implementation problem is corrected.
980 \section{Read-only File Daemon using capabilities}
981 \label{sec:fdreadonly}
982 This feature implements support of keeping \textbf{ReadAll} capabilities after
983 UID/GID switch, this allows FD to keep root read but drop write permission.
985 It introduces new \texttt{bacula-fd} option (\texttt{-k}) specifying that
986 \textbf{ReadAll} capabilities should be kept after UID/GID switch.
989 root@localhost:~# bacula-fd -k -u nobody -g nobody
992 The code for this feature was contributed by our friends at AltLinux.
997 To help developers of restore GUI interfaces, we have added new \textsl{dot
998 commands} that permit browsing the catalog in a very simple way.
1001 \item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update
1002 the Bvfs cache in the catalog. You need to run it before any access to the
1005 \item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command
1006 will list all directories in the specified \texttt{path} or
1007 \texttt{pathid}. Using \texttt{pathid} avoids problems with character
1008 encoding of path/filenames.
1010 \item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command
1011 will list all files in the specified \texttt{path} or \texttt{pathid}. Using
1012 \texttt{pathid} avoids problems with character encoding.
1015 You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of
1016 data that will be displayed.
1019 * .bvfs_update jobid=1,2
1021 * .bvfs_lsdir path=/ jobid=1,2
1024 This project was funded by Bacula Systems.
1026 \section{Testing your Tape Drive}
1027 \label{sec:btapespeed}
1029 To determine the best configuration of your tape drive, you can run the new
1030 \texttt{speed} command available in the \texttt{btape} program.
1032 This command can have the following arguments:
1034 \item[\texttt{file\_size=n}] Specify the Maximum File Size for this test
1035 (between 1 and 5GB). This counter is in GB.
1036 \item[\texttt{nb\_file=n}] Specify the number of file to be written. The amount
1037 of data should be greater than your memory ($file\_size*nb\_file$).
1038 \item[\texttt{skip\_zero}] This flag permits to skip tests with constant
1040 \item[\texttt{skip\_random}] This flag permits to skip tests with random
1042 \item[\texttt{skip\_raw}] This flag permits to skip tests with raw access.
1043 \item[\texttt{skip\_block}] This flag permits to skip tests with Bacula block
1048 *speed file_size=3 skip_raw
1049 btape.c:1078 Test with zero data and bacula block structure.
1050 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
1051 ++++++++++++++++++++++++++++++++++++++++++
1052 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
1053 btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 MB/s
1055 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 MB/s
1057 btape.c:1090 Test with random data, should give the minimum throughput.
1058 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
1059 +++++++++++++++++++++++++++++++++++++++++++
1060 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
1061 btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 MB/s
1062 +++++++++++++++++++++++++++++++++++++++++++
1064 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s
1068 When using compression, the random test will give your the minimum throughput
1069 of your drive . The test using constant string will give you the maximum speed
1070 of your hardware chain. (cpu, memory, scsi card, cable, drive, tape).
1072 You can change the block size in the Storage Daemon configuration file.
1074 \section{New {\bf Block Checksum} Device Directive}
1075 You may now turn off the Block Checksum (CRC32) code
1076 that Bacula uses when writing blocks to a Volume. This is
1083 doing so can reduce the Storage daemon CPU usage slightly. It
1084 will also permit Bacula to read a Volume that has corrupted data.
1086 The default is {\bf yes} -- i.e. the checksum is computed on write
1087 and checked on read.
1089 We do not recommend to turn this off particularly on older tape
1090 drives or for disk Volumes where doing so may allow corrupted data
1093 \section{New Bat Features}
1095 Those new features were funded by Bacula Systems.
1097 \subsection{Media List View}
1099 By clicking on ``Media'', you can see the list of all your volumes. You will be
1100 able to filter by Pool, Media Type, Location,\dots And sort the result directly
1101 in the table. The old ``Media'' view is now known as ``Pool''.
1102 \begin{figure}[htbp]
1104 \includegraphics[width=13cm]{\idir bat-mediaview.eps}
1105 \label{fig:mediaview}
1109 \subsection{Media Information View}
1111 By double-clicking on a volume (on the Media list, in the Autochanger content
1112 or in the Job information panel), you can access a detailed overview of your
1113 Volume. (cf \ref{fig:mediainfo}.)
1114 \begin{figure}[htbp]
1116 \includegraphics[width=13cm]{\idir bat11.eps}
1117 \caption{Media information}
1118 \label{fig:mediainfo}
1121 \subsection{Job Information View}
1123 By double-clicking on a Job record (on the Job run list or in the Media
1124 information panel), you can access a detailed overview of your Job. (cf
1126 \begin{figure}[htbp]
1128 \includegraphics[width=13cm]{\idir bat12.eps}
1129 \caption{Job information}
1133 \subsection{Autochanger Content View}
1135 By double-clicking on a Storage record (on the Storage list panel), you can
1136 access a detailed overview of your Autochanger. (cf \ref{fig:jobinfo}.)
1137 \begin{figure}[htbp]
1139 \includegraphics[width=13cm]{\idir bat13.eps}
1140 \caption{Autochanger content}
1141 \label{fig:achcontent}
1144 To use this feature, you need to use the latest mtx-changer script
1145 version. (With new \texttt{listall} and \texttt{transfer} commands)
1147 \section{Bat on Windows}
1148 We have ported {\bf bat} to Windows and it is now installed
1149 by default when the installer is run. It works quite well
1150 on Win32, but has not had a lot of testing there, so your
1151 feedback would be welcome. Unfortunately, eventhough it is
1152 installed by default, it does not yet work on 64 bit Windows
1155 \section{New Win32 Installer}
1156 The Win32 installer has been modified in several very important
1159 \item You must deinstall any current version of the
1160 Win32 File daemon before upgrading to the new one.
1161 If you forget to do so, the new installation will fail.
1162 To correct this failure, you must manually shutdown
1163 and deinstall the old File daemon.
1164 \item All files (other than menu links) are installed
1165 in {\bf c:/Program Files/Bacula}.
1166 \item The installer no longer sets this
1167 file to require administrator privileges by default. If you want
1168 to do so, please do it manually using the {\bf cacls} program.
1171 cacls "C:\Program Files\Bacula" /T /G SYSTEM:F Administrators:F
1173 \item The server daemons (Director and Storage daemon) are
1174 no longer included in the Windows installer. If you want the
1175 Windows servers, you will either need to build them yourself (note
1176 they have not been ported to 64 bits), or you can contact
1177 Bacula Systems about this.
1180 \section{Win64 Installer}
1181 We have corrected a number of problems that required manual
1182 editing of the conf files. In most cases, it should now
1183 install and work. {\bf bat} is by default installed in
1184 {\bf c:/Program Files/Bacula/bin32} rather than
1185 {\bf c:/Program Files/Bacula} as is the case with the 32
1186 bit Windows installer.
1188 \section{Linux Bare Metal Recovery USB Key}
1189 We have made a number of significant improvements in the
1190 Bare Metal Recovery USB key. Please see the README files
1191 it the {\bf rescue} release for more details.
1193 We are working on an equivalent USB key for Windows bare
1194 metal recovery, but it will take some time to develop it (best
1195 estimate 3Q2010 or 4Q2010)
1198 \section{bconsole Timeout Option}
1199 You can now use the -u option of {\bf bconsole} to set a timeout in seconds
1200 for commands. This is useful with GUI programs that use {\bf bconsole}
1201 to interface to the Director.
1203 \section{Important Changes}
1204 \label{sec:importantchanges}
1207 \item You are now allowed to Migrate, Copy, and Virtual Full to read and write
1208 to the same Pool. The Storage daemon ensures that you do not read and
1209 write to the same Volume.
1210 \item The \texttt{Device Poll Interval} is now 5 minutes. (previously did not
1212 \item Virtually all the features of {\bf mtx-changer} have
1213 now been parameterized, which allows you to configure
1214 mtx-changer without changing it. There is a new configuration file {\bf mtx-changer.conf}
1215 that contains variables that you can set to configure mtx-changer.
1216 This configuration file will not be overwritten during upgrades.
1217 We encourage you to submit any changes
1218 that are made to mtx-changer and to parameterize it all in
1219 mtx-changer.conf so that all configuration will be done by
1220 changing only mtx-changer.conf.
1221 \item The new \texttt{mtx-changer} script has two new options, \texttt{listall}
1222 and \texttt{transfer}. Please configure them as appropriate
1223 in mtx-changer.conf.
1224 \item To enhance security of the \texttt{BackupCatalog} job, we provide a new
1225 script (\texttt{make\_catalog\_backup.pl}) that does not expose your catalog
1226 password. If you want to use the new script, you will need to
1227 manually change the \texttt{BackupCatalog} Job definition.
1228 \item The \texttt{bconsole} \texttt{help} command now accepts
1229 an argument, which if provided produces information on that
1230 command (ex: \texttt{help run}).
1234 \subsubsection*{Truncate volume after purge}
1236 Note that the Truncate Volume after purge feature doesn't work as expected
1237 in 5.0.0 version. Please, don't use it before version 5.0.1.
1239 \subsection{Custom Catalog queries}
1241 If you wish to add specialized commands that list the contents of the catalog,
1242 you can do so by adding them to the \texttt{query.sql} file. This
1243 \texttt{query.sql} file is now empty by default. The file
1244 \texttt{examples/sample-query.sql} has an a number of sample commands
1245 you might find useful.
1247 \subsection{Deprecated parts}
1249 The following items have been \textbf{deprecated} for a long time, and are now
1250 removed from the code.
1253 \item Support for SQLite 2
1256 \section{Misc Changes}
1257 \label{sec:miscchanges}
1260 \item Updated Nagios check\_bacula
1261 \item Updated man files
1262 \item Added OSX package generation script in platforms/darwin
1263 \item Added Spanish and Ukrainian Bacula translations
1264 \item Enable/disable command shows only Jobs that can change
1265 \item Added \texttt{show disabled} command to show disabled Jobs
1266 \item Many ACL improvements
1267 \item Added Level to FD status Job output
1268 \item Begin Ingres DB driver (not yet working)
1269 \item Split RedHat spec files into bacula, bat, mtx, and docs
1270 \item Reorganized the manuals (fewer separate manuals)
1271 \item Added lock/unlock order protection in lock manager
1272 \item Allow 64 bit sizes for a number of variables
1273 \item Fixed several deadlocks or potential race conditions in the SD
1276 \chapter{Released Version 3.0.3 and 3.0.3a}
1278 There are no new features in version 3.0.3. This version simply fixes a
1279 number of bugs found in version 3.0.2 during the onging development
1282 \chapter{New Features in Released Version 3.0.2}
1284 This chapter presents the new features added to the
1285 Released Bacula Version 3.0.2.
1287 \section{Full Restore from a Given JobId}
1288 \index[general]{Restore menu}
1290 This feature allows selecting a single JobId and having Bacula
1291 automatically select all the other jobs that comprise a full backup up to
1292 and including the selected date (through JobId).
1294 Assume we start with the following jobs:
1296 +-------+--------------+---------------------+-------+----------+------------+
1297 | jobid | client | starttime | level | jobfiles | jobbytes |
1298 +-------+--------------+---------------------+-------+----------+------------
1299 | 6 | localhost-fd | 2009-07-15 11:45:49 | I | 2 | 0 |
1300 | 5 | localhost-fd | 2009-07-15 11:45:45 | I | 15 | 44143 |
1301 | 3 | localhost-fd | 2009-07-15 11:45:38 | I | 1 | 10 |
1302 | 1 | localhost-fd | 2009-07-15 11:45:30 | F | 1527 | 44143073 |
1303 +-------+--------------+---------------------+-------+----------+------------+
1306 Below is an example of this new feature (which is number 12 in the
1311 To select the JobIds, you have the following choices:
1312 1: List last 20 Jobs run
1313 2: List Jobs where a given File is saved
1315 12: Select full restore to a specified Job date
1318 Select item: (1-13): 12
1319 Enter JobId to get the state to restore: 5
1320 Selecting jobs to build the Full state at 2009-07-15 11:45:45
1321 You have selected the following JobIds: 1,3,5
1323 Building directory tree for JobId(s) 1,3,5 ... +++++++++++++++++++
1324 1,444 files inserted into the tree.
1327 This project was funded by Bacula Systems.
1329 \section{Source Address}
1330 \index[general]{Source Address}
1332 A feature has been added which allows the administrator to specify the address
1333 from which the Director and File daemons will establish connections. This
1334 may be used to simplify system configuration overhead when working in complex
1335 networks utilizing multi-homing and policy-routing.
1337 To accomplish this, two new configuration directives have been implemented:
1340 FDSourceAddress=10.0.1.20 # Always initiate connections from this address
1344 DirSourceAddress=10.0.1.10 # Always initiate connections from this address
1348 Simply adding specific host routes on the OS
1349 would have an undesirable side-effect: any
1350 application trying to contact the destination host would be forced to use the
1351 more specific route possibly diverting management traffic onto a backup VLAN.
1352 Instead of adding host routes for each client connected to a multi-homed backup
1353 server (for example where there are management and backup VLANs), one can
1354 use the new directives to specify a specific source address at the application
1357 Additionally, this allows the simplification and abstraction of firewall rules
1358 when dealing with a Hot-Standby director or storage daemon configuration. The
1359 Hot-standby pair may share a CARP address, which connections must be sourced
1360 from, while system services listen and act from the unique interface addresses.
1362 This project was funded by Collaborative Fusion, Inc.
1364 \section{Show volume availability when doing restore}
1366 When doing a restore the selection dialog ends by displaying this
1370 The job will require the following
1371 Volume(s) Storage(s) SD Device(s)
1372 ===========================================================================
1373 *000741L3 LTO-4 LTO3
1374 *000866L3 LTO-4 LTO3
1375 *000765L3 LTO-4 LTO3
1376 *000764L3 LTO-4 LTO3
1377 *000756L3 LTO-4 LTO3
1378 *001759L3 LTO-4 LTO3
1379 *001763L3 LTO-4 LTO3
1383 Volumes marked with ``*'' are online (in the autochanger).
1386 This should help speed up large restores by minimizing the time spent
1387 waiting for the operator to discover that he must change tapes in the library.
1389 This project was funded by Bacula Systems.
1391 \section{Accurate estimate command}
1393 The \texttt{estimate} command can now use the accurate code to detect changes
1394 and give a better estimation.
1396 You can set the accurate behavior on the command line by using
1397 \texttt{accurate=yes\vb{}no} or use the Job setting as default value.
1400 * estimate listing accurate=yes level=incremental job=BackupJob
1403 This project was funded by Bacula Systems.
1405 \chapter{New Features in 3.0.0}
1406 \label{NewFeaturesChapter}
1407 \index[general]{New Features}
1409 This chapter presents the new features added to the development 2.5.x
1410 versions to be released as Bacula version 3.0.0 sometime in April 2009.
1412 \section{Accurate Backup}
1413 \index[general]{Accurate Backup}
1415 As with most other backup programs, by default Bacula decides what files to
1416 backup for Incremental and Differental backup by comparing the change
1417 (st\_ctime) and modification (st\_mtime) times of the file to the time the last
1418 backup completed. If one of those two times is later than the last backup
1419 time, then the file will be backed up. This does not, however, permit tracking
1420 what files have been deleted and will miss any file with an old time that may
1421 have been restored to or moved onto the client filesystem.
1423 \subsection{Accurate = \lt{}yes\vb{}no\gt{}}
1424 If the {\bf Accurate = \lt{}yes\vb{}no\gt{}} directive is enabled (default no) in
1425 the Job resource, the job will be run as an Accurate Job. For a {\bf Full}
1426 backup, there is no difference, but for {\bf Differential} and {\bf
1427 Incremental} backups, the Director will send a list of all previous files
1428 backed up, and the File daemon will use that list to determine if any new files
1429 have been added or or moved and if any files have been deleted. This allows
1430 Bacula to make an accurate backup of your system to that point in time so that
1431 if you do a restore, it will restore your system exactly.
1434 about using Accurate backup is that it requires more resources (CPU and memory)
1435 on both the Director and the Client machines to create the list of previous
1436 files backed up, to send that list to the File daemon, for the File daemon to
1437 keep the list (possibly very big) in memory, and for the File daemon to do
1438 comparisons between every file in the FileSet and the list. In particular,
1439 if your client has lots of files (more than a few million), you will need
1440 lots of memory on the client machine.
1442 Accurate must not be enabled when backing up with a plugin that is not
1443 specially designed to work with Accurate. If you enable it, your restores
1444 will probably not work correctly.
1446 This project was funded by Bacula Systems.
1451 \index[general]{Copy Jobs}
1453 A new {\bf Copy} job type 'C' has been implemented. It is similar to the
1454 existing Migration feature with the exception that the Job that is copied is
1455 left unchanged. This essentially creates two identical copies of the same
1456 backup. However, the copy is treated as a copy rather than a backup job, and
1457 hence is not directly available for restore. The {\bf restore} command lists
1458 copy jobs and allows selection of copies by using \texttt{jobid=}
1459 option. If the keyword {\bf copies} is present on the command line, Bacula will
1460 display the list of all copies for selected jobs.
1465 These JobIds have copies as follows:
1466 +-------+------------------------------------+-----------+------------------+
1467 | JobId | Job | CopyJobId | MediaType |
1468 +-------+------------------------------------+-----------+------------------+
1469 | 2 | CopyJobSave.2009-02-17_16.31.00.11 | 7 | DiskChangerMedia |
1470 +-------+------------------------------------+-----------+------------------+
1471 +-------+-------+----------+----------+---------------------+------------------+
1472 | JobId | Level | JobFiles | JobBytes | StartTime | VolumeName |
1473 +-------+-------+----------+----------+---------------------+------------------+
1474 | 19 | F | 6274 | 76565018 | 2009-02-17 16:30:45 | ChangerVolume002 |
1475 | 2 | I | 1 | 5 | 2009-02-17 16:30:51 | FileVolume001 |
1476 +-------+-------+----------+----------+---------------------+------------------+
1477 You have selected the following JobIds: 19,2
1479 Building directory tree for JobId(s) 19,2 ... ++++++++++++++++++++++++++++++++++++++++++++
1480 5,611 files inserted into the tree.
1485 The Copy Job runs without using the File daemon by copying the data from the
1486 old backup Volume to a different Volume in a different Pool. See the Migration
1487 documentation for additional details. For copy Jobs there is a new selection
1488 directive named {\bf PoolUncopiedJobs} which selects all Jobs that were
1489 not already copied to another Pool.
1491 As with Migration, the Client, Volume, Job, or SQL query, are
1492 other possible ways of selecting the Jobs to be copied. Selection
1493 types like SmallestVolume, OldestVolume, PoolOccupancy and PoolTime also
1494 work, but are probably more suited for Migration Jobs.
1496 If Bacula finds a Copy of a job record that is purged (deleted) from the catalog,
1497 it will promote the Copy to a \textsl{real} backup job and will make it available for
1498 automatic restore. If more than one Copy is available, it will promote the copy
1499 with the smallest JobId.
1501 A nice solution which can be built with the new Copy feature is often
1502 called disk-to-disk-to-tape backup (DTDTT). A sample config could
1503 look something like the one below:
1507 Name = FullBackupsVirtualPool
1509 Purge Oldest Volume = Yes
1511 NextPool = FullBackupsTapePool
1515 Name = FullBackupsTapePool
1519 Volume Retention = 365 days
1520 Storage = superloader
1524 # Fake fileset for copy jobs
1536 # Fake client for copy jobs
1546 # Default template for a CopyDiskToTape Job
1549 Name = CopyDiskToTape
1551 Messages = StandardCopy
1554 Selection Type = PoolUncopiedJobs
1555 Maximum Concurrent Jobs = 10
1557 Allow Duplicate Jobs = Yes
1558 Cancel Queued Duplicates = No
1559 Cancel Running Duplicates = No
1564 Name = DaySchedule7:00
1565 Run = Level=Full daily at 7:00
1569 Name = CopyDiskToTapeFullBackups
1571 Schedule = DaySchedule7:00
1572 Pool = FullBackupsVirtualPool
1573 JobDefs = CopyDiskToTape
1577 The example above had 2 pool which are copied using the PoolUncopiedJobs
1578 selection criteria. Normal Full backups go to the Virtual pool and are copied
1579 to the Tape pool the next morning.
1581 The command \texttt{list copies [jobid=x,y,z]} lists copies for a given
1586 +-------+------------------------------------+-----------+------------------+
1587 | JobId | Job | CopyJobId | MediaType |
1588 +-------+------------------------------------+-----------+------------------+
1589 | 9 | CopyJobSave.2008-12-20_22.26.49.05 | 11 | DiskChangerMedia |
1590 +-------+------------------------------------+-----------+------------------+
1593 \section{ACL Updates}
1594 \index[general]{ACL Updates}
1595 The whole ACL code had been overhauled and in this version each platforms has
1596 different streams for each type of acl available on such an platform. As ACLs
1597 between platforms tend to be not that portable (most implement POSIX acls but
1598 some use an other draft or a completely different format) we currently only
1599 allow certain platform specific ACL streams to be decoded and restored on the
1600 same platform that they were created on. The old code allowed to restore ACL
1601 cross platform but the comments already mention that not being to wise. For
1602 backward compatability the new code will accept the two old ACL streams and
1603 handle those with the platform specific handler. But for all new backups it
1604 will save the ACLs using the new streams.
1606 Currently the following platforms support ACLs:
1610 \item {\bf Darwin/OSX}
1619 Currently we support the following ACL types (these ACL streams use a reserved
1620 part of the stream numbers):
1623 \item {\bf STREAM\_ACL\_AIX\_TEXT} 1000 AIX specific string representation from
1625 \item {\bf STREAM\_ACL\_DARWIN\_ACCESS\_ACL} 1001 Darwin (OSX) specific acl\_t
1626 string representation from acl\_to\_text (POSIX acl)
1627 \item {\bf STREAM\_ACL\_FREEBSD\_DEFAULT\_ACL} 1002 FreeBSD specific acl\_t
1628 string representation from acl\_to\_text (POSIX acl) for default acls.
1629 \item {\bf STREAM\_ACL\_FREEBSD\_ACCESS\_ACL} 1003 FreeBSD specific acl\_t
1630 string representation from acl\_to\_text (POSIX acl) for access acls.
1631 \item {\bf STREAM\_ACL\_HPUX\_ACL\_ENTRY} 1004 HPUX specific acl\_entry
1632 string representation from acltostr (POSIX acl)
1633 \item {\bf STREAM\_ACL\_IRIX\_DEFAULT\_ACL} 1005 IRIX specific acl\_t string
1634 representation from acl\_to\_text (POSIX acl) for default acls.
1635 \item {\bf STREAM\_ACL\_IRIX\_ACCESS\_ACL} 1006 IRIX specific acl\_t string
1636 representation from acl\_to\_text (POSIX acl) for access acls.
1637 \item {\bf STREAM\_ACL\_LINUX\_DEFAULT\_ACL} 1007 Linux specific acl\_t
1638 string representation from acl\_to\_text (POSIX acl) for default acls.
1639 \item {\bf STREAM\_ACL\_LINUX\_ACCESS\_ACL} 1008 Linux specific acl\_t string
1640 representation from acl\_to\_text (POSIX acl) for access acls.
1641 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_ACL} 1009 Tru64 specific acl\_t
1642 string representation from acl\_to\_text (POSIX acl) for default acls.
1643 \item {\bf STREAM\_ACL\_TRU64\_DEFAULT\_DIR\_ACL} 1010 Tru64 specific acl\_t
1644 string representation from acl\_to\_text (POSIX acl) for default acls.
1645 \item {\bf STREAM\_ACL\_TRU64\_ACCESS\_ACL} 1011 Tru64 specific acl\_t string
1646 representation from acl\_to\_text (POSIX acl) for access acls.
1647 \item {\bf STREAM\_ACL\_SOLARIS\_ACLENT} 1012 Solaris specific aclent\_t
1648 string representation from acltotext or acl\_totext (POSIX acl)
1649 \item {\bf STREAM\_ACL\_SOLARIS\_ACE} 1013 Solaris specific ace\_t string
1650 representation from from acl\_totext (NFSv4 or ZFS acl)
1653 In future versions we might support conversion functions from one type of acl
1654 into an other for types that are either the same or easily convertable. For now
1655 the streams are seperate and restoring them on a platform that doesn't
1656 recognize them will give you a warning.
1658 \section{Extended Attributes}
1659 \index[general]{Extended Attributes}
1660 Something that was on the project list for some time is now implemented for
1661 platforms that support a similar kind of interface. Its the support for backup
1662 and restore of so called extended attributes. As extended attributes are so
1663 platform specific these attributes are saved in seperate streams for each
1664 platform. Restores of the extended attributes can only be performed on the
1665 same platform the backup was done. There is support for all types of extended
1666 attributes, but restoring from one type of filesystem onto an other type of
1667 filesystem on the same platform may lead to supprises. As extended attributes
1668 can contain any type of data they are stored as a series of so called
1669 value-pairs. This data must be seen as mostly binary and is stored as such.
1670 As security labels from selinux are also extended attributes this option also
1671 stores those labels and no specific code is enabled for handling selinux
1674 Currently the following platforms support extended attributes:
1676 \item {\bf Darwin/OSX}
1682 On linux acls are also extended attributes, as such when you enable ACLs on a
1683 Linux platform it will NOT save the same data twice e.g. it will save the ACLs
1684 and not the same exteneded attribute.
1686 To enable the backup of extended attributes please add the following to your
1701 \section{Shared objects}
1702 \index[general]{Shared objects}
1703 A default build of Bacula will now create the libraries as shared objects
1704 (.so) rather than static libraries as was previously the case.
1705 The shared libraries are built using {\bf libtool} so it should be quite
1708 An important advantage of using shared objects is that on a machine with the
1709 Directory, File daemon, the Storage daemon, and a console, you will have only
1710 one copy of the code in memory rather than four copies. Also the total size of
1711 the binary release is smaller since the library code appears only once rather
1712 than once for every program that uses it; this results in significant reduction
1713 in the size of the binaries particularly for the utility tools.
1715 In order for the system loader to find the shared objects when loading the
1716 Bacula binaries, the Bacula shared objects must either be in a shared object
1717 directory known to the loader (typically /usr/lib) or they must be in the
1718 directory that may be specified on the {\bf ./configure} line using the {\bf
1719 {-}{-}libdir} option as:
1722 ./configure --libdir=/full-path/dir
1725 the default is /usr/lib. If {-}{-}libdir is specified, there should be
1726 no need to modify your loader configuration provided that
1727 the shared objects are installed in that directory (Bacula
1728 does this with the make install command). The shared objects
1729 that Bacula references are:
1738 These files are symbolically linked to the real shared object file,
1739 which has a version number to permit running multiple versions of
1740 the libraries if desired (not normally the case).
1742 If you have problems with libtool or you wish to use the old
1743 way of building static libraries, or you want to build a static
1744 version of Bacula you may disable
1745 libtool on the configure command line with:
1748 ./configure --disable-libtool
1752 \section{Building Static versions of Bacula}
1753 \index[general]{Static linking}
1754 In order to build static versions of Bacula, in addition
1755 to configuration options that were needed you now must
1756 also add --disable-libtool. Example
1759 ./configure --enable-static-client-only --disable-libtool
1763 \section{Virtual Backup (Vbackup)}
1764 \index[general]{Virtual Backup}
1765 \index[general]{Vbackup}
1767 Bacula's virtual backup feature is often called Synthetic Backup or
1768 Consolidation in other backup products. It permits you to consolidate the
1769 previous Full backup plus the most recent Differential backup and any
1770 subsequent Incremental backups into a new Full backup. This new Full
1771 backup will then be considered as the most recent Full for any future
1772 Incremental or Differential backups. The VirtualFull backup is
1773 accomplished without contacting the client by reading the previous backup
1774 data and writing it to a volume in a different pool.
1776 In some respects the Vbackup feature works similar to a Migration job, in
1777 that Bacula normally reads the data from the pool specified in the
1778 Job resource, and writes it to the {\bf Next Pool} specified in the
1779 Job resource. Note, this means that usually the output from the Virtual
1780 Backup is written into a different pool from where your prior backups
1781 are saved. Doing it this way guarantees that you will not get a deadlock
1782 situation attempting to read and write to the same volume in the Storage
1783 daemon. If you then want to do subsequent backups, you may need to
1784 move the Virtual Full Volume back to your normal backup pool.
1785 Alternatively, you can set your {\bf Next Pool} to point to the current
1786 pool. This will cause Bacula to read and write to Volumes in the
1787 current pool. In general, this will work, because Bacula will
1788 not allow reading and writing on the same Volume. In any case, once
1789 a VirtualFull has been created, and a restore is done involving the
1790 most current Full, it will read the Volume or Volumes by the VirtualFull
1791 regardless of in which Pool the Volume is found.
1793 The Vbackup is enabled on a Job by Job in the Job resource by specifying
1794 a level of {\bf VirtualFull}.
1796 A typical Job resource definition might look like the following:
1803 FileSet = "Full Set"
1810 # Default pool definition
1814 Recycle = yes # Automatically recycle Volumes
1815 AutoPrune = yes # Prune expired volumes
1816 Volume Retention = 365d # one year
1824 Recycle = yes # Automatically recycle Volumes
1825 AutoPrune = yes # Prune expired volumes
1826 Volume Retention = 365d # one year
1827 Storage = DiskChanger
1830 # Definition of file storage device
1835 Device = FileStorage
1837 Maximum Concurrent Jobs = 5
1840 # Definition of DDS Virtual tape disk storage device
1843 Address = localhost # N.B. Use a fully qualified name here
1845 Device = DiskChanger
1846 Media Type = DiskChangerMedia
1847 Maximum Concurrent Jobs = 4
1852 Then in bconsole or via a Run schedule, you would run the job as:
1855 run job=MyBackup level=Full
1856 run job=MyBackup level=Incremental
1857 run job=MyBackup level=Differential
1858 run job=MyBackup level=Incremental
1859 run job=MyBackup level=Incremental
1862 So providing there were changes between each of those jobs, you would end up
1863 with a Full backup, a Differential, which includes the first Incremental
1864 backup, then two Incremental backups. All the above jobs would be written to
1865 the {\bf Default} pool.
1867 To consolidate those backups into a new Full backup, you would run the
1871 run job=MyBackup level=VirtualFull
1874 And it would produce a new Full backup without using the client, and the output
1875 would be written to the {\bf Full} Pool which uses the Diskchanger Storage.
1877 If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
1880 Note, the Start and End time of the Virtual Full backup is set to the
1881 values for the last job included in the Virtual Full (in the above example,
1882 it is an Increment). This is so that if another incremental is done, which
1883 will be based on the Virtual Full, it will backup all files from the
1884 last Job included in the Virtual Full rather than from the time the Virtual
1885 Full was actually run.
1889 \section{Catalog Format}
1890 \index[general]{Catalog Format}
1891 Bacula 3.0 comes with some changes to the catalog format. The upgrade
1892 operation will convert the FileId field of the File table from 32 bits (max 4
1893 billion table entries) to 64 bits (very large number of items). The
1894 conversion process can take a bit of time and will likely DOUBLE THE SIZE of
1895 your catalog during the conversion. Also you won't be able to run jobs during
1896 this conversion period. For example, a 3 million file catalog will take 2
1897 minutes to upgrade on a normal machine. Please don't forget to make a valid
1898 backup of your database before executing the upgrade script. See the
1899 ReleaseNotes for additional details.
1901 \section{64 bit Windows Client}
1902 \index[general]{Win64 Client}
1903 Unfortunately, Microsoft's implementation of Volume Shadown Copy (VSS) on
1904 their 64 bit OS versions is not compatible with a 32 bit Bacula Client.
1905 As a consequence, we are also releasing a 64 bit version of the Bacula
1906 Windows Client (win64bacula-3.0.0.exe) that does work with VSS.
1907 These binaries should only be installed on 64 bit Windows operating systems.
1908 What is important is not your hardware but whether or not you have
1909 a 64 bit version of the Windows OS.
1911 Compared to the Win32 Bacula Client, the 64 bit release contains a few differences:
1913 \item Before installing the Win64 Bacula Client, you must totally
1914 deinstall any prior 2.4.x Client installation using the
1915 Bacula deinstallation (see the menu item). You may want
1916 to save your .conf files first.
1917 \item Only the Client (File daemon) is ported to Win64, the Director
1918 and the Storage daemon are not in the 64 bit Windows installer.
1919 \item bwx-console is not yet ported.
1920 \item bconsole is ported but it has not been tested.
1921 \item The documentation is not included in the installer.
1922 \item Due to Vista security restrictions imposed on a default installation
1923 of Vista, before upgrading the Client, you must manually stop
1924 any prior version of Bacula from running, otherwise the install
1926 \item Due to Vista security restrictions imposed on a default installation
1927 of Vista, attempting to edit the conf files via the menu items
1928 will fail. You must directly edit the files with appropriate
1929 permissions. Generally double clicking on the appropriate .conf
1930 file will work providing you have sufficient permissions.
1931 \item All Bacula files are now installed in
1932 {\bf C:/Program Files/Bacula} except the main menu items,
1933 which are installed as before. This vastly simplifies the installation.
1934 \item If you are running on a foreign language version of Windows, most
1935 likely {\bf C:/Program Files} does not exist, so you should use the
1936 Custom installation and enter an appropriate location to install
1938 \item The 3.0.0 Win32 Client continues to install files in the locations used
1939 by prior versions. For the next version we will convert it to use
1940 the same installation conventions as the Win64 version.
1943 This project was funded by Bacula Systems.
1946 \section{Duplicate Job Control}
1947 \index[general]{Duplicate Jobs}
1948 The new version of Bacula provides four new directives that
1949 give additional control over what Bacula does if duplicate jobs
1950 are started. A duplicate job in the sense we use it here means
1951 a second or subsequent job with the same name starts. This
1952 happens most frequently when the first job runs longer than expected because no
1953 tapes are available.
1955 The four directives each take as an argument a {\bf yes} or {\bf no} value and
1956 are specified in the Job resource.
1960 \subsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}}
1961 \index[general]{Allow Duplicate Jobs}
1962 If this directive is set to {\bf yes}, duplicate jobs will be run. If
1963 the directive is set to {\bf no} (default) then only one job of a given name
1964 may run at one time, and the action that Bacula takes to ensure only
1965 one job runs is determined by the other directives (see below).
1967 If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs
1968 are present and none of the three directives given below permit
1969 cancelling a job, then the current job (the second one started)
1972 \subsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}}
1973 \index[general]{Allow Higher Duplicates}
1974 This directive was in version 5.0.0, but does not work as
1975 expected. If used, it should always be set to no. In later versions
1976 of Bacula the directive is disabled (disregarded).
1978 \subsection{Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}}
1979 \index[general]{Cancel Running Duplicates}
1980 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1981 if this directive is set to {\bf yes} any job that is already running
1982 will be canceled. The default is {\bf no}.
1984 \subsection{Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}}
1985 \index[general]{Cancel Queued Duplicates}
1986 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1987 if this directive is set to {\bf yes} any job that is
1988 already queued to run but not yet running will be canceled.
1989 The default is {\bf no}.
1992 \section{TLS Authentication}
1993 \index[general]{TLS Authentication}
1994 In Bacula version 2.5.x and later, in addition to the normal Bacula
1995 CRAM-MD5 authentication that is used to authenticate each Bacula
1996 connection, you can specify that you want TLS Authentication as well,
1997 which will provide more secure authentication.
1999 This new feature uses Bacula's existing TLS code (normally used for
2000 communications encryption) to do authentication. To use it, you must
2001 specify all the TLS directives normally used to enable communications
2002 encryption (TLS Enable, TLS Verify Peer, TLS Certificate, ...) and
2005 \subsection{TLS Authenticate = yes}
2007 TLS Authenticate = yes
2010 in the main daemon configuration resource (Director for the Director,
2011 Client for the File daemon, and Storage for the Storage daemon).
2013 When {\bf TLS Authenticate} is enabled, after doing the CRAM-MD5
2014 authentication, Bacula will also do TLS authentication, then TLS
2015 encryption will be turned off, and the rest of the communication between
2016 the two Bacula daemons will be done without encryption.
2018 If you want to encrypt communications data, use the normal TLS directives
2019 but do not turn on {\bf TLS Authenticate}.
2021 \section{bextract non-portable Win32 data}
2022 \index[general]{bextract handles Win32 non-portable data}
2023 {\bf bextract} has been enhanced to be able to restore
2024 non-portable Win32 data to any OS. Previous versions were
2025 unable to restore non-portable Win32 data to machines that
2026 did not have the Win32 BackupRead and BackupWrite API calls.
2028 \section{State File updated at Job Termination}
2029 \index[general]{State File}
2030 In previous versions of Bacula, the state file, which provides a
2031 summary of previous jobs run in the {\bf status} command output was
2032 updated only when Bacula terminated, thus if the daemon crashed, the
2033 state file might not contain all the run data. This version of
2034 the Bacula daemons updates the state file on each job termination.
2036 \section{MaxFullInterval = \lt{}time-interval\gt{}}
2037 \index[general]{MaxFullInterval}
2038 The new Job resource directive {\bf Max Full Interval = \lt{}time-interval\gt{}}
2039 can be used to specify the maximum time interval between {\bf Full} backup
2040 jobs. When a job starts, if the time since the last Full backup is
2041 greater than the specified interval, and the job would normally be an
2042 {\bf Incremental} or {\bf Differential}, it will be automatically
2043 upgraded to a {\bf Full} backup.
2045 \section{MaxDiffInterval = \lt{}time-interval\gt{}}
2046 \index[general]{MaxDiffInterval}
2047 The new Job resource directive {\bf Max Diff Interval = \lt{}time-interval\gt{}}
2048 can be used to specify the maximum time interval between {\bf Differential} backup
2049 jobs. When a job starts, if the time since the last Differential backup is
2050 greater than the specified interval, and the job would normally be an
2051 {\bf Incremental}, it will be automatically
2052 upgraded to a {\bf Differential} backup.
2054 \section{Honor No Dump Flag = \lt{}yes\vb{}no\gt{}}
2055 \index[general]{MaxDiffInterval}
2056 On FreeBSD systems, each file has a {\bf no dump flag} that can be set
2057 by the user, and when it is set it is an indication to backup programs
2058 to not backup that particular file. This version of Bacula contains a
2059 new Options directive within a FileSet resource, which instructs Bacula to
2060 obey this flag. The new directive is:
2063 Honor No Dump Flag = yes\vb{}no
2066 The default value is {\bf no}.
2069 \section{Exclude Dir Containing = \lt{}filename-string\gt{}}
2070 \index[general]{IgnoreDir}
2071 The {\bf ExcludeDirContaining = \lt{}filename\gt{}} is a new directive that
2072 can be added to the Include section of the FileSet resource. If the specified
2073 filename ({\bf filename-string}) is found on the Client in any directory to be
2074 backed up, the whole directory will be ignored (not backed up). For example:
2077 # List of files to be backed up
2085 Exclude Dir Containing = .excludeme
2090 But in /home, there may be hundreds of directories of users and some
2091 people want to indicate that they don't want to have certain
2092 directories backed up. For example, with the above FileSet, if
2093 the user or sysadmin creates a file named {\bf .excludeme} in
2094 specific directories, such as
2097 /home/user/www/cache/.excludeme
2098 /home/user/temp/.excludeme
2101 then Bacula will not backup the two directories named:
2104 /home/user/www/cache
2108 NOTE: subdirectories will not be backed up. That is, the directive
2109 applies to the two directories in question and any children (be they
2110 files, directories, etc).
2113 \section{Bacula Plugins}
2114 \index[general]{Plugin}
2115 Support for shared object plugins has been implemented in the Linux, Unix
2116 and Win32 File daemons. The API will be documented separately in
2117 the Developer's Guide or in a new document. For the moment, there is
2118 a single plugin named {\bf bpipe} that allows an external program to
2119 get control to backup and restore a file.
2121 Plugins are also planned (partially implemented) in the Director and the
2124 \subsection{Plugin Directory}
2125 \index[general]{Plugin Directory}
2126 Each daemon (DIR, FD, SD) has a new {\bf Plugin Directory} directive that may
2127 be added to the daemon definition resource. The directory takes a quoted
2128 string argument, which is the name of the directory in which the daemon can
2129 find the Bacula plugins. If this directive is not specified, Bacula will not
2130 load any plugins. Since each plugin has a distinctive name, all the daemons
2131 can share the same plugin directory.
2133 \subsection{Plugin Options}
2134 \index[general]{Plugin Options}
2135 The {\bf Plugin Options} directive takes a quoted string
2136 arguement (after the equal sign) and may be specified in the
2137 Job resource. The options specified will be passed to all plugins
2138 when they are run. This each plugin must know what it is looking
2139 for. The value defined in the Job resource can be modified
2140 by the user when he runs a Job via the {\bf bconsole} command line
2143 Note: this directive may be specified, and there is code to modify
2144 the string in the run command, but the plugin options are not yet passed to
2145 the plugin (i.e. not fully implemented).
2147 \subsection{Plugin Options ACL}
2148 \index[general]{Plugin Options ACL}
2149 The {\bf Plugin Options ACL} directive may be specified in the
2150 Director's Console resource. It functions as all the other ACL commands
2151 do by permitting users running restricted consoles to specify a
2152 {\bf Plugin Options} that overrides the one specified in the Job
2153 definition. Without this directive restricted consoles may not modify
2156 \subsection{Plugin = \lt{}plugin-command-string\gt{}}
2157 \index[general]{Plugin}
2158 The {\bf Plugin} directive is specified in the Include section of
2159 a FileSet resource where you put your {\bf File = xxx} directives.
2170 Plugin = "bpipe:..."
2175 In the above example, when the File daemon is processing the directives
2176 in the Include section, it will first backup all the files in {\bf /home}
2177 then it will load the plugin named {\bf bpipe} (actually bpipe-dir.so) from
2178 the Plugin Directory. The syntax and semantics of the Plugin directive
2179 require the first part of the string up to the colon (:) to be the name
2180 of the plugin. Everything after the first colon is ignored by the File daemon but
2181 is passed to the plugin. Thus the plugin writer may define the meaning of the
2182 rest of the string as he wishes.
2184 Please see the next section for information about the {\bf bpipe} Bacula
2187 \section{The bpipe Plugin}
2188 \index[general]{The bpipe Plugin}
2189 The {\bf bpipe} plugin is provided in the directory src/plugins/fd/bpipe-fd.c of
2190 the Bacula source distribution. When the plugin is compiled and linking into
2191 the resulting dynamic shared object (DSO), it will have the name {\bf bpipe-fd.so}.
2192 Please note that this is a very simple plugin that was written for
2193 demonstration and test purposes. It is and can be used in production, but
2194 that was never really intended.
2196 The purpose of the plugin is to provide an interface to any system program for
2197 backup and restore. As specified above the {\bf bpipe} plugin is specified in
2198 the Include section of your Job's FileSet resource. The full syntax of the
2199 plugin directive as interpreted by the {\bf bpipe} plugin (each plugin is free
2200 to specify the sytax as it wishes) is:
2203 Plugin = "<field1>:<field2>:<field3>:<field4>"
2208 \item {\bf field1} is the name of the plugin with the trailing {\bf -fd.so}
2209 stripped off, so in this case, we would put {\bf bpipe} in this field.
2211 \item {\bf field2} specifies the namespace, which for {\bf bpipe} is the
2212 pseudo path and filename under which the backup will be saved. This pseudo
2213 path and filename will be seen by the user in the restore file tree.
2214 For example, if the value is {\bf /MYSQL/regress.sql}, the data
2215 backed up by the plugin will be put under that "pseudo" path and filename.
2216 You must be careful to choose a naming convention that is unique to avoid
2217 a conflict with a path and filename that actually exists on your system.
2219 \item {\bf field3} for the {\bf bpipe} plugin
2220 specifies the "reader" program that is called by the plugin during
2221 backup to read the data. {\bf bpipe} will call this program by doing a
2224 \item {\bf field4} for the {\bf bpipe} plugin
2225 specifies the "writer" program that is called by the plugin during
2226 restore to write the data back to the filesystem.
2229 Please note that for two items above describing the "reader" and "writer"
2230 fields, these programs are "executed" by Bacula, which
2231 means there is no shell interpretation of any command line arguments
2232 you might use. If you want to use shell characters (redirection of input
2233 or output, ...), then we recommend that you put your command or commands
2234 in a shell script and execute the script. In addition if you backup a
2235 file with the reader program, when running the writer program during
2236 the restore, Bacula will not automatically create the path to the file.
2237 Either the path must exist, or you must explicitly do so with your command
2238 or in a shell script.
2240 Putting it all together, the full plugin directive line might look
2244 Plugin = "bpipe:/MYSQL/regress.sql:mysqldump -f
2245 --opt --databases bacula:mysql"
2248 The directive has been split into two lines, but within the {\bf bacula-dir.conf} file
2249 would be written on a single line.
2251 This causes the File daemon to call the {\bf bpipe} plugin, which will write
2252 its data into the "pseudo" file {\bf /MYSQL/regress.sql} by calling the
2253 program {\bf mysqldump -f --opt --database bacula} to read the data during
2254 backup. The mysqldump command outputs all the data for the database named
2255 {\bf bacula}, which will be read by the plugin and stored in the backup.
2256 During restore, the data that was backed up will be sent to the program
2257 specified in the last field, which in this case is {\bf mysql}. When
2258 {\bf mysql} is called, it will read the data sent to it by the plugn
2259 then write it back to the same database from which it came ({\bf bacula}
2262 The {\bf bpipe} plugin is a generic pipe program, that simply transmits
2263 the data from a specified program to Bacula for backup, and then from Bacula to
2264 a specified program for restore.
2266 By using different command lines to {\bf bpipe},
2267 you can backup any kind of data (ASCII or binary) depending
2268 on the program called.
2270 \section{Microsoft Exchange Server 2003/2007 Plugin}
2271 \index[general]{Microsoft Exchange Server 2003/2007 Plugin}
2272 \subsection{Background}
2273 The Exchange plugin was made possible by a funded development project
2274 between Equiinet Ltd -- www.equiinet.com (many thanks) and Bacula Systems.
2275 The code for the plugin was written by James Harper, and the Bacula core
2276 code by Kern Sibbald. All the code for this funded development has become
2277 part of the Bacula project. Thanks to everyone who made it happen.
2279 \subsection{Concepts}
2280 Although it is possible to backup Exchange using Bacula VSS the Exchange
2281 plugin adds a good deal of functionality, because while Bacula VSS
2282 completes a full backup (snapshot) of Exchange, it does
2283 not support Incremental or Differential backups, restoring is more
2284 complicated, and a single database restore is not possible.
2286 Microsoft Exchange organises its storage into Storage Groups with
2287 Databases inside them. A default installation of Exchange will have a
2288 single Storage Group called 'First Storage Group', with two Databases
2289 inside it, "Mailbox Store (SERVER NAME)" and
2290 "Public Folder Store (SERVER NAME)",
2291 which hold user email and public folders respectively.
2293 In the default configuration, Exchange logs everything that happens to
2294 log files, such that if you have a backup, and all the log files since,
2295 you can restore to the present time. Each Storage Group has its own set
2296 of log files and operates independently of any other Storage Groups. At
2297 the Storage Group level, the logging can be turned off by enabling a
2298 function called "Enable circular logging". At this time the Exchange
2299 plugin will not function if this option is enabled.
2301 The plugin allows backing up of entire storage groups, and the restoring
2302 of entire storage groups or individual databases. Backing up and
2303 restoring at the individual mailbox or email item is not supported but
2304 can be simulated by use of the "Recovery" Storage Group (see below).
2306 \subsection{Installing}
2307 The Exchange plugin requires a DLL that is shipped with Microsoft
2308 Exchanger Server called {\bf esebcli2.dll}. Assuming Exchange is installed
2309 correctly the Exchange plugin should find this automatically and run
2310 without any additional installation.
2312 If the DLL can not be found automatically it will need to be copied into
2313 the Bacula installation
2314 directory (eg C:\verb+\+Program Files\verb+\+Bacula\verb+\+bin). The Exchange API DLL is
2315 named esebcli2.dll and is found in C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+bin on a
2316 default Exchange installation.
2318 \subsection{Backing Up}
2319 To back up an Exchange server the Fileset definition must contain at
2320 least {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"} for
2321 the backup to work correctly. The 'exchange:' bit tells Bacula to look
2322 for the exchange plugin, the '@EXCHANGE' bit makes sure all the backed
2323 up files are prefixed with something that isn't going to share a name
2324 with something outside the plugin, and the 'Microsoft Information Store'
2325 bit is required also. It is also possible to add the name of a storage
2326 group to the "Plugin =" line, eg \\
2327 {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"} \\
2328 if you want only a single storage group backed up.
2330 Additionally, you can suffix the 'Plugin =' directive with
2331 ":notrunconfull" which will tell the plugin not to truncate the Exchange
2332 database at the end of a full backup.
2334 An Incremental or Differential backup will backup only the database logs
2335 for each Storage Group by inspecting the "modified date" on each
2336 physical log file. Because of the way the Exchange API works, the last
2337 logfile backed up on each backup will always be backed up by the next
2338 Incremental or Differential backup too. This adds 5MB to each
2339 Incremental or Differential backup size but otherwise does not cause any
2342 By default, a normal VSS fileset containing all the drive letters will
2343 also back up the Exchange databases using VSS. This will interfere with
2344 the plugin and Exchange's shared ideas of when the last full backup was
2345 done, and may also truncate log files incorrectly. It is important,
2346 therefore, that the Exchange database files be excluded from the backup,
2347 although the folders the files are in should be included, or they will
2348 have to be recreated manually if a baremetal restore is done.
2353 File = C:/Program Files/Exchsrvr/mdbdata
2354 Plugin = "exchange:..."
2357 File = C:/Program Files/Exchsrvr/mdbdata/E00.chk
2358 File = C:/Program Files/Exchsrvr/mdbdata/E00.log
2359 File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log
2360 File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log
2361 File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log
2362 File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log
2363 File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb
2368 The advantage of excluding the above files is that you can significantly
2369 reduce the size of your backup since all the important Exchange files
2370 will be properly saved by the Plugin.
2373 \subsection{Restoring}
2374 The restore operation is much the same as a normal Bacula restore, with
2375 the following provisos:
2378 \item The {\bf Where} restore option must not be specified
2379 \item Each Database directory must be marked as a whole. You cannot just
2380 select (say) the .edb file and not the others.
2381 \item If a Storage Group is restored, the directory of the Storage Group
2383 \item It is possible to restore only a subset of the available log files,
2384 but they {\bf must} be contiguous. Exchange will fail to restore correctly
2385 if a log file is missing from the sequence of log files
2386 \item Each database to be restored must be dismounted and marked as "Can be
2387 overwritten by restore"
2388 \item If an entire Storage Group is to be restored (eg all databases and
2389 logs in the Storage Group), then it is best to manually delete the
2390 database files from the server (eg C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+mdbdata\verb+\+*)
2391 as Exchange can get confused by stray log files lying around.
2394 \subsection{Restoring to the Recovery Storage Group}
2395 The concept of the Recovery Storage Group is well documented by
2397 \elink{http://support.microsoft.com/kb/824126}{http://support.microsoft.com/kb/824126},
2398 but to briefly summarize...
2400 Microsoft Exchange allows the creation of an additional Storage Group
2401 called the Recovery Storage Group, which is used to restore an older
2402 copy of a database (e.g. before a mailbox was deleted) into without
2403 messing with the current live data. This is required as the Standard and
2404 Small Business Server versions of Exchange can not ordinarily have more
2405 than one Storage Group.
2407 To create the Recovery Storage Group, drill down to the Server in Exchange
2408 System Manager, right click, and select
2409 {\bf "New -> Recovery Storage Group..."}. Accept or change the file
2410 locations and click OK. On the Recovery Storage Group, right click and
2411 select {\bf "Add Database to Recover..."} and select the database you will
2414 Restore only the single database nominated as the database in the
2415 Recovery Storage Group. Exchange will redirect the restore to the
2416 Recovery Storage Group automatically.
2417 Then run the restore.
2419 \subsection{Restoring on Microsoft Server 2007}
2420 Apparently the {\bf Exmerge} program no longer exists in Microsoft Server
2421 2007, and henc you use a new proceedure for recovering a single mail box.
2422 This procedure is ducomented by Microsoft at:
2423 \elink{http://technet.microsoft.com/en-us/library/aa997694.aspx}{http://technet.microsoft.com/en-us/library/aa997694.aspx},
2424 and involves using the {\bf Restore-Mailbox} and {\bf
2425 Get-MailboxStatistics} shell commands.
2427 \subsection{Caveats}
2428 This plugin is still being developed, so you should consider it
2429 currently in BETA test, and thus use in a production environment
2430 should be done only after very careful testing.
2432 When doing a full backup, the Exchange database logs are truncated by
2433 Exchange as soon as the plugin has completed the backup. If the data
2434 never makes it to the backup medium (eg because of spooling) then the
2435 logs will still be truncated, but they will also not have been backed
2436 up. A solution to this is being worked on. You will have to schedule a
2437 new Full backup to ensure that your next backups will be usable.
2439 The "Enable Circular Logging" option cannot be enabled or the plugin
2442 Exchange insists that a successful Full backup must have taken place if
2443 an Incremental or Differential backup is desired, and the plugin will
2444 fail if this is not the case. If a restore is done, Exchange will
2445 require that a Full backup be done before an Incremental or Differential
2448 The plugin will most likely not work well if another backup application
2449 (eg NTBACKUP) is backing up the Exchange database, especially if the
2450 other backup application is truncating the log files.
2452 The Exchange plugin has not been tested with the {\bf Accurate} option, so
2453 we recommend either carefully testing or that you avoid this option for
2456 The Exchange plugin is not called during processing the bconsole {\bf
2457 estimate} command, and so anything that would be backed up by the plugin
2458 will not be added to the estimate total that is displayed.
2461 \section{libdbi Framework}
2462 \index[general]{libdbi Framework}
2463 As a general guideline, Bacula has support for a few catalog database drivers
2464 (MySQL, PostgreSQL, SQLite)
2465 coded natively by the Bacula team. With the libdbi implementation, which is a
2466 Bacula driver that uses libdbi to access the catalog, we have an open field to
2467 use many different kinds database engines following the needs of users.
2469 The according to libdbi (http://libdbi.sourceforge.net/) project: libdbi
2470 implements a database-independent abstraction layer in C, similar to the
2471 DBI/DBD layer in Perl. Writing one generic set of code, programmers can
2472 leverage the power of multiple databases and multiple simultaneous database
2473 connections by using this framework.
2475 Currently the libdbi driver in Bacula project only supports the same drivers
2476 natively coded in Bacula. However the libdbi project has support for many
2477 others database engines. You can view the list at
2478 http://libdbi-drivers.sourceforge.net/. In the future all those drivers can be
2479 supported by Bacula, however, they must be tested properly by the Bacula team.
2481 Some of benefits of using libdbi are:
2483 \item The possibility to use proprietary databases engines in which your
2484 proprietary licenses prevent the Bacula team from developing the driver.
2485 \item The possibility to use the drivers written for the libdbi project.
2486 \item The possibility to use other database engines without recompiling Bacula
2487 to use them. Just change one line in bacula-dir.conf
2488 \item Abstract Database access, this is, unique point to code and profiling
2489 catalog database access.
2492 The following drivers have been tested:
2494 \item PostgreSQL, with and without batch insert
2495 \item Mysql, with and without batch insert
2500 In the future, we will test and approve to use others databases engines
2501 (proprietary or not) like DB2, Oracle, Microsoft SQL.
2503 To compile Bacula to support libdbi we need to configure the code with the
2504 --with-dbi and --with-dbi-driver=[database] ./configure options, where
2505 [database] is the database engine to be used with Bacula (of course we can
2506 change the driver in file bacula-dir.conf, see below). We must configure the
2507 access port of the database engine with the option --with-db-port, because the
2508 libdbi framework doesn't know the default access port of each database.
2510 The next phase is checking (or configuring) the bacula-dir.conf, example:
2514 dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
2515 dbname = regress; user = regress; password = ""
2519 The parameter {\bf dbdriver} indicates that we will use the driver dbi with a
2520 mysql database. Currently the drivers supported by Bacula are: postgresql,
2521 mysql, sqlite, sqlite3; these are the names that may be added to string "dbi:".
2523 The following limitations apply when Bacula is set to use the libdbi framework:
2524 - Not tested on the Win32 platform
2525 - A little performance is lost if comparing with native database driver.
2526 The reason is bound with the database driver provided by libdbi and the
2527 simple fact that one more layer of code was added.
2529 It is important to remember, when compiling Bacula with libdbi, the
2530 following packages are needed:
2532 \item libdbi version 1.0.0, http://libdbi.sourceforge.net/
2533 \item libdbi-drivers 1.0.0, http://libdbi-drivers.sourceforge.net/
2536 You can download them and compile them on your system or install the packages
2537 from your OS distribution.
2539 \section{Console Command Additions and Enhancements}
2540 \index[general]{Console Additions}
2542 \subsection{Display Autochanger Content}
2543 \index[general]{StatusSlots}
2545 The {\bf status slots storage=\lt{}storage-name\gt{}} command displays
2546 autochanger content.
2550 Slot | Volume Name | Status | Media Type | Pool |
2551 ------+---------------+----------+-------------------+------------|
2552 1 | 00001 | Append | DiskChangerMedia | Default |
2553 2 | 00002 | Append | DiskChangerMedia | Default |
2554 3*| 00003 | Append | DiskChangerMedia | Scratch |
2559 If you an asterisk ({\bf *}) appears after the slot number, you must run an
2560 {\bf update slots} command to synchronize autochanger content with your
2563 \subsection{list joblog job=xxx or jobid=nnn}
2564 \index[general]{list joblog}
2565 A new list command has been added that allows you to list the contents
2566 of the Job Log stored in the catalog for either a Job Name (fully qualified)
2567 or for a particular JobId. The {\bf llist} command will include a line with
2568 the time and date of the entry.
2570 Note for the catalog to have Job Log entries, you must have a directive
2577 In your Director's {\bf Messages} resource.
2579 \subsection{Use separator for multiple commands}
2580 \index[general]{Command Separator}
2581 When using bconsole with readline, you can set the command separator with
2582 \textbf{@separator} command to one
2583 of those characters to write commands who require multiple input in one line.
2585 !$%&'()*+,-/:;<>?[]^`{|}~
2588 \subsection{Deleting Volumes}
2589 The delete volume bconsole command has been modified to
2590 require an asterisk (*) in front of a MediaId otherwise the
2591 value you enter is a taken to be a Volume name. This is so that
2592 users may delete numeric Volume names. The previous Bacula versions
2593 assumed that all input that started with a number was a MediaId.
2595 This new behavior is indicated in the prompt if you read it
2598 \section{Bare Metal Recovery}
2599 The old bare metal recovery project is essentially dead. One
2600 of the main features of it was that it would build a recovery
2601 CD based on the kernel on your system. The problem was that
2602 every distribution has a different boot procedure and different
2603 scripts, and worse yet, the boot procedures and scripts change
2604 from one distribution to another. This meant that maintaining
2605 (keeping up with the changes) the rescue CD was too much work.
2607 To replace it, a new bare metal recovery USB boot stick has been developed
2608 by Bacula Systems. This technology involves remastering a Ubuntu LiveCD to
2609 boot from a USB key.
2613 \item Recovery can be done from within graphical environment.
2614 \item Recovery can be done in a shell.
2615 \item Ubuntu boots on a large number of Linux systems.
2616 \item The process of updating the system and adding new
2617 packages is not too difficult.
2618 \item The USB key can easily be upgraded to newer Ubuntu versions.
2619 \item The USB key has writable partitions for modifications to
2620 the OS and for modification to your home directory.
2621 \item You can add new files/directories to the USB key very easily.
2622 \item You can save the environment from multiple machines on
2624 \item Bacula Systems is funding its ongoing development.
2627 The disadvantages are:
2629 \item The USB key is usable but currently under development.
2630 \item Not everyone may be familiar with Ubuntu (no worse
2632 \item Some older OSes cannot be booted from USB. This can
2633 be resolved by first booting a Ubuntu LiveCD then plugging
2635 \item Currently the documentation is sketchy and not yet added
2636 to the main manual. See below ...
2639 The documentation and the code can be found in the {\bf rescue} package
2640 in the directory {\bf linux/usb}.
2642 \section{Miscellaneous}
2643 \index[general]{Misc New Features}
2645 \subsection{Allow Mixed Priority = \lt{}yes\vb{}no\gt{}}
2646 \index[general]{Allow Mixed Priority}
2647 This directive is only implemented in version 2.5 and later. When
2648 set to {\bf yes} (default {\bf no}), this job may run even if lower
2649 priority jobs are already running. This means a high priority job
2650 will not have to wait for other jobs to finish before starting.
2651 The scheduler will only mix priorities when all running jobs have
2654 Note that only higher priority jobs will start early. Suppose the
2655 director will allow two concurrent jobs, and that two jobs with
2656 priority 10 are running, with two more in the queue. If a job with
2657 priority 5 is added to the queue, it will be run as soon as one of
2658 the running jobs finishes. However, new priority 10 jobs will not
2659 be run until the priority 5 job has finished.
2661 \subsection{Bootstrap File Directive -- FileRegex}
2662 \index[general]{Bootstrap File Directive}
2663 {\bf FileRegex} is a new command that can be added to the bootstrap
2664 (.bsr) file. The value is a regular expression. When specified, only
2665 matching filenames will be restored.
2667 During a restore, if all File records are pruned from the catalog
2668 for a Job, normally Bacula can restore only all files saved. That
2669 is there is no way using the catalog to select individual files.
2670 With this new feature, Bacula will ask if you want to specify a Regex
2671 expression for extracting only a part of the full backup.
2674 Building directory tree for JobId(s) 1,3 ...
2675 There were no files inserted into the tree, so file selection
2676 is not possible.Most likely your retention policy pruned the files
2678 Do you want to restore all the files? (yes\vb{}no): no
2680 Regexp matching files to restore? (empty to abort): /tmp/regress/(bin|tests)/
2681 Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr
2684 \subsection{Bootstrap File Optimization Changes}
2685 In order to permit proper seeking on disk files, we have extended the bootstrap
2686 file format to include a {\bf VolStartAddr} and {\bf VolEndAddr} records. Each
2687 takes a 64 bit unsigned integer range (i.e. nnn-mmm) which defines the start
2688 address range and end address range respectively. These two directives replace
2689 the {\bf VolStartFile}, {\bf VolEndFile}, {\bf VolStartBlock} and {\bf
2690 VolEndBlock} directives. Bootstrap files containing the old directives will
2691 still work, but will not properly take advantage of proper disk seeking, and
2692 may read completely to the end of a disk volume during a restore. With the new
2693 format (automatically generated by the new Director), restores will seek
2694 properly and stop reading the volume when all the files have been restored.
2696 \subsection{Solaris ZFS/NFSv4 ACLs}
2697 This is an upgrade of the previous Solaris ACL backup code
2698 to the new library format, which will backup both the old
2699 POSIX(UFS) ACLs as well as the ZFS ACLs.
2701 The new code can also restore POSIX(UFS) ACLs to a ZFS filesystem
2702 (it will translate the POSIX(UFS)) ACL into a ZFS/NFSv4 one) it can also
2703 be used to transfer from UFS to ZFS filesystems.
2706 \subsection{Virtual Tape Emulation}
2707 \index[general]{Virtual Tape Emulation}
2708 We now have a Virtual Tape emulator that allows us to run though 99.9\% of
2709 the tape code but actually reading and writing to a disk file. Used with the
2710 \textbf{disk-changer} script, you can now emulate an autochanger with 10 drives
2711 and 700 slots. This feature is most useful in testing. It is enabled
2712 by using {\bf Device Type = vtape} in the Storage daemon's Device
2713 directive. This feature is only implemented on Linux machines and should not be
2714 used for production.
2716 \subsection{Bat Enhancements}
2717 \index[general]{Bat Enhancements}
2718 Bat (the Bacula Administration Tool) GUI program has been significantly
2719 enhanced and stabilized. In particular, there are new table based status
2720 commands; it can now be easily localized using Qt4 Linguist.
2722 The Bat communications protocol has been significantly enhanced to improve
2723 GUI handling. Note, you {\bf must} use a the bat that is distributed with
2724 the Director you are using otherwise the communications protocol will not
2727 \subsection{RunScript Enhancements}
2728 \index[general]{RunScript Enhancements}
2729 The {\bf RunScript} resource has been enhanced to permit multiple
2730 commands per RunScript. Simply specify multiple {\bf Command} directives
2737 Command = "/bin/echo test"
2738 Command = "/bin/echo an other test"
2739 Command = "/bin/echo 3 commands in the same runscript"
2746 A new Client RunScript {\bf RunsWhen} keyword of {\bf AfterVSS} has been
2747 implemented, which runs the command after the Volume Shadow Copy has been made.
2749 Console commands can be specified within a RunScript by using:
2750 {\bf Console = \lt{}command\gt{}}, however, this command has not been
2751 carefully tested and debugged and is known to easily crash the Director.
2752 We would appreciate feedback. Due to the recursive nature of this command, we
2753 may remove it before the final release.
2755 \subsection{Status Enhancements}
2756 \index[general]{Status Enhancements}
2757 The bconsole {\bf status dir} output has been enhanced to indicate
2758 Storage daemon job spooling and despooling activity.
2760 \subsection{Connect Timeout}
2761 \index[general]{Connect Timeout}
2762 The default connect timeout to the File
2763 daemon has been set to 3 minutes. Previously it was 30 minutes.
2765 \subsection{ftruncate for NFS Volumes}
2766 \index[general]{ftruncate for NFS Volumes}
2767 If you write to a Volume mounted by NFS (say on a local file server),
2768 in previous Bacula versions, when the Volume was recycled, it was not
2769 properly truncated because NFS does not implement ftruncate (file
2770 truncate). This is now corrected in the new version because we have
2771 written code (actually a kind user) that deletes and recreates the Volume,
2772 thus accomplishing the same thing as a truncate.
2774 \subsection{Support for Ubuntu}
2775 The new version of Bacula now recognizes the Ubuntu (and Kubuntu)
2776 version of Linux, and thus now provides correct autostart routines.
2777 Since Ubuntu officially supports Bacula, you can also obtain any
2778 recent release of Bacula from the Ubuntu repositories.
2780 \subsection{Recycle Pool = \lt{}pool-name\gt{}}
2781 \index[general]{Recycle Pool}
2782 The new \textbf{RecyclePool} directive defines to which pool the Volume will
2783 be placed (moved) when it is recycled. Without this directive, a Volume will
2784 remain in the same pool when it is recycled. With this directive, it can be
2785 moved automatically to any existing pool during a recycle. This directive is
2786 probably most useful when defined in the Scratch pool, so that volumes will
2787 be recycled back into the Scratch pool.
2789 \subsection{FD Version}
2790 \index[general]{FD Version}
2791 The File daemon to Director protocol now includes a version
2792 number, which although there is no visible change for users,
2793 will help us in future versions automatically determine
2794 if a File daemon is not compatible.
2796 \subsection{Max Run Sched Time = \lt{}time-period-in-seconds\gt{}}
2797 \index[general]{Max Run Sched Time}
2798 The time specifies the maximum allowed time that a job may run, counted from
2799 when the job was scheduled. This can be useful to prevent jobs from running
2800 during working hours. We can see it like \texttt{Max Start Delay + Max Run
2803 \subsection{Max Wait Time = \lt{}time-period-in-seconds\gt{}}
2804 \index[general]{Max Wait Time}
2805 Previous \textbf{MaxWaitTime} directives aren't working as expected, instead
2806 of checking the maximum allowed time that a job may block for a resource,
2807 those directives worked like \textbf{MaxRunTime}. Some users are reporting to
2808 use \textbf{Incr/Diff/Full Max Wait Time} to control the maximum run time of
2809 their job depending on the level. Now, they have to use
2810 \textbf{Incr/Diff/Full Max Run Time}. \textbf{Incr/Diff/Full Max Wait Time}
2811 directives are now deprecated.
2813 \subsection{Incremental|Differential Max Wait Time = \lt{}time-period-in-seconds\gt{}}
2814 \index[general]{Incremental Max Wait Time}
2815 \index[general]{Differential Max Wait Time}
2817 These directives have been deprecated in favor of
2818 \texttt{Incremental|Differential Max Run Time}.
2820 \subsection{Max Run Time directives}
2821 \index[general]{Max Run Time directives}
2822 Using \textbf{Full/Diff/Incr Max Run Time}, it's now possible to specify the
2823 maximum allowed time that a job can run depending on the level.
2825 \addcontentsline{lof}{figure}{Job time control directives}
2826 \includegraphics{\idir different_time.eps}
2828 \subsection{Statistics Enhancements}
2829 \index[general]{Statistics Enhancements}
2830 If you (or probably your boss) want to have statistics on your backups to
2831 provide some \textit{Service Level Agreement} indicators, you could use a few
2832 SQL queries on the Job table to report how many:
2836 \item jobs have been successful
2837 \item files have been backed up
2841 However, these statistics are accurate only if your job retention is greater
2842 than your statistics period. Ie, if jobs are purged from the catalog, you won't
2843 be able to use them.
2845 Now, you can use the \textbf{update stats [days=num]} console command to fill
2846 the JobHistory table with new Job records. If you want to be sure to take in
2847 account only \textbf{good jobs}, ie if one of your important job has failed but
2848 you have fixed the problem and restarted it on time, you probably want to
2849 delete the first \textit{bad} job record and keep only the successful one. For
2850 that simply let your staff do the job, and update JobHistory table after two or
2851 three days depending on your organization using the \textbf{[days=num]} option.
2853 These statistics records aren't used for restoring, but mainly for
2854 capacity planning, billings, etc.
2856 The Bweb interface provides a statistics module that can use this feature. You
2857 can also use tools like Talend or extract information by yourself.
2859 The \textbf{Statistics Retention = \lt{}time\gt{}} director directive defines
2860 the length of time that Bacula will keep statistics job records in the Catalog
2861 database after the Job End time. (In \texttt{JobHistory} table) When this time
2862 period expires, and if user runs \texttt{prune stats} command, Bacula will
2863 prune (remove) Job records that are older than the specified period.
2865 You can use the following Job resource in your nightly \textbf{BackupCatalog}
2866 job to maintain statistics.
2869 Name = BackupCatalog
2872 Console = "update stats days=3"
2873 Console = "prune stats yes"
2880 \subsection{ScratchPool = \lt{}pool-resource-name\gt{}}
2881 \index[general]{ScratchPool}
2882 This directive permits to specify a specific \textsl{Scratch} pool for the
2883 current pool. This is useful when using multiple storage sharing the same
2884 mediatype or when you want to dedicate volumes to a particular set of pool.
2886 \subsection{Enhanced Attribute Despooling}
2887 \index[general]{Attribute Despooling}
2888 If the storage daemon and the Director are on the same machine, the spool file
2889 that contains attributes is read directly by the Director instead of being
2890 transmitted across the network. That should reduce load and speedup insertion.
2892 \subsection{SpoolSize = \lt{}size-specification-in-bytes\gt{}}
2893 \index[general]{SpoolSize}
2894 A new Job directive permits to specify the spool size per job. This is used
2895 in advanced job tunning. {\bf SpoolSize={\it bytes}}
2897 \subsection{MaximumConsoleConnections = \lt{}number\gt{}}
2898 \index[general]{MaximumConsoleConnections}
2899 A new director directive permits to specify the maximum number of Console
2900 Connections that could run concurrently. The default is set to 20, but you may
2901 set it to a larger number.
2903 \subsection{VerId = \lt{}string\gt{}}
2904 \index[general]{VerId}
2905 A new director directive permits to specify a personnal identifier that will be
2906 displayed in the \texttt{version} command.
2908 \subsection{dbcheck enhancements}
2909 \index[general]{dbcheck enhancements}
2910 If you are using Mysql, dbcheck will now ask you if you want to create
2911 temporary indexes to speed up orphaned Path and Filename elimination.
2913 A new \texttt{-B} option allows you to print catalog information in a simple
2914 text based format. This is useful to backup it in a secure way.
2929 You can now specify the database connection port in the command line.
2931 \subsection{{-}{-}docdir configure option}
2932 \index[general]{{-}{-}docdir configure option}
2933 You can use {-}{-}docdir= on the ./configure command to
2934 specify the directory where you want Bacula to install the
2935 LICENSE, ReleaseNotes, ChangeLog, ... files. The default is
2936 {\bf /usr/share/doc/bacula}.
2938 \subsection{{-}{-}htmldir configure option}
2939 \index[general]{{-}{-}htmldir configure option}
2940 You can use {-}{-}htmldir= on the ./configure command to
2941 specify the directory where you want Bacula to install the bat html help
2942 files. The default is {\bf /usr/share/doc/bacula/html}
2944 \subsection{{-}{-}with-plugindir configure option}
2945 \index[general]{{-}{-}plugindir configure option}
2946 You can use {-}{-}plugindir= on the ./configure command to
2947 specify the directory where you want Bacula to install
2948 the plugins (currently only bpipe-fd). The default is