1 \chapter{New Features in Bacula Enterprise}
2 This chapter presents the new features that have been added to the
3 current Enterprise version of Bacula.
4 These features are available only with a Bacula Systems subscription.
6 In addition to the features in this chapter, the Enterprise version
7 will include the Community features described in the Community new Features
10 \section{Bacula Enterprise 6.0.6}
12 \subsection{Incremental Accelerator Plugin for NetApp}
14 The Incremental Accelerator for NetApp Plugin is designed to simplify the
15 backup and restore procedure of your NetApp NAS hosting a huge number of files.
17 \smallskip{} When using the NetApp HFC Plugin, Bacula Enterprise will query the
18 NetApp device to get the list of all files modified since the last backup
19 instead of having to walk through the entire filesystem. Once Bacula have the
20 list of all files to back's up, it will use a standard network share (such as
21 NFS or CIFS) to access files.
24 This project was funded by Bacula Systems and is available with the Bacula
27 \subsection{PostgreSQL Plugin}
29 The PostgreSQL plugin is designed to simplify the backup and restore procedure
30 of your PostgreSQL cluster, the backup administrator doesn't need to learn about
31 internals of Postgres backup techniques or write complex scripts. The plugin
32 will automatically take care for you to backup essential information such as
33 configuration, users definition or tablespaces. The PostgreSQL plugin supports
34 both dump and Point In Time Recovery (PITR) backup techniques.
37 This project was funded by Bacula Systems and is available with the Bacula
40 \subsection{Maximum Reload Requests}
42 The new Director directive \texttt{Maximum Reload Requests} permits to
43 configure the number of reload requests that can be done while jobs are
49 Maximum Reload Requests = 64
55 \subsection{FD Storage Address}
57 When the Director is behind a NAT, in a WAN area, to connect to
59 the StorageDaemon, the Director uses an ``external'' ip address,
60 and the FileDaemon should use an ``internal'' IP address to contact the
63 The normal way to handle this situation is to use a canonical name such as
64 ``storage-server'' that will be resolved on the Director side as the WAN address
65 and on the Client side as the LAN address. This is now possible to configure
66 this parameter using the new \texttt{FDStorageAddress} Storage
70 \bsysimageH{BackupOverWan1}{Backup Over WAN}{figbs6:fdstorageaddress}
71 % \label{fig:fdstorageaddress}
77 FD Storage Address = 10.0.0.1
83 % # or in the Client resouce
88 % FD Storage Address = 10.0.0.1
94 % Note that using the Client \texttt{FDStorageAddress} directive will not allow
95 % to use multiple Storage Daemon, all Backup or Restore requests will be sent to
96 % the specified \texttt{FDStorageAddress}.
98 \subsection{Maximum Concurrent Read Jobs}
99 This is a new directive that can be used in the {\bf bacula-dir.conf} file
100 in the Storage resource. The main purpose is to limit the number
101 of concurrent Copy, Migration, and VirtualFull jobs so that
102 they don't monopolize all the Storage drives causing a deadlock situation
103 where all the drives are allocated for reading but none remain for
104 writing. This deadlock situation can occur when running multiple
105 simultaneous Copy, Migration, and VirtualFull jobs.
108 The default value is set to 0 (zero), which means there is no
109 limit on the number of read jobs. Note, limiting the read jobs
110 does not apply to Restore jobs, which are normally started by
111 hand. A reasonable value for this directive is one half the number
112 of drives that the Storage resource has rounded down. Doing so,
113 will leave the same number of drives for writing and will generally
114 avoid over commiting drives and a deadlock.
117 \section{Bacula Enterprise 6.0.4}
119 \subsection{VMWare vSphere VADP Plugin}
121 The Bacula Enterprise vSphere plugin provides virtual
122 machine bare metal recovery, while the backup at the guest level simplify data
123 protection of critical applications.
125 The plugin integrates the VMware's Changed Block Tracking (CBT) technology to
126 ensure only blocks that have changed since the initial Full, and/or the last
127 Incremental or Differential Backup are sent to the current Incremental or
128 Differential backup stream to give you more efficient backups and reduced
131 \subsection{Oracle RMAN Plugin}
133 The Bacula Enterprise Oracle Plugin is designed to simplify the backup and
134 restore procedure of your Oracle Database instance, the backup administrator
135 don't need to learn about internals of Oracle backup techniques or write
136 complex scripts. The Bacula Enterprise Oracle plugin supports both dump and
137 Point In Time Recovery (PITR) with RMAN backup techniques.
139 \section{Bacula Enterprise 6.0.0}
141 \subsection{Incomplete Jobs}
142 During a backup, if the Storage daemon experiences disconnection
143 with the File daemon during backup (normally a comm line problem
144 or possibly an FD failure), under conditions that the SD determines
145 to be safe it will make the failed job as Incomplete rather than
146 failed. This is done only if there is sufficient valid backup
147 data that was written to the Volume. The advantage of an Incomplete
148 job is that it can be restarted by the new bconsole {\bf restart}
149 command from the point where it left off rather than from the
150 beginning of the jobs as is the case with a cancel.
152 \subsection{The Stop Command}
153 Bacula has been enhanced to provide a {\bf stop} command,
154 very similar to the {\bf cancel} command with the main difference
155 that the Job that is stopped is marked as Incomplete so that
156 it can be restarted later by the {\bf restart} command where
157 it left off (see below). The {\bf stop} command with no
158 arguments, will like the cancel command, prompt you with the
159 list of running jobs allowing you to select one, which might
160 look like the following:
165 1: JobId=3 Job=Incremental.2012-03-26_12.04.26_07
166 2: JobId=4 Job=Incremental.2012-03-26_12.04.30_08
167 3: JobId=5 Job=Incremental.2012-03-26_12.04.36_09
168 Choose Job to stop (1-3): 2
169 2001 Job "Incremental.2012-03-26_12.04.30_08" marked to be stopped.
170 3000 JobId=4 Job="Incremental.2012-03-26_12.04.30_08" marked to be stopped.
173 \subsection{The Restart Command}
174 The new {\bf Restart command} allows console users to restart
175 a canceled, failed, or incomplete Job. For canceled and failed
176 Jobs, the Job will restart from the beginning. For incomplete
177 Jobs the Job will restart at the point that it was stopped either
178 by a stop command or by some recoverable failure.
181 If you enter the {\bf restart} command in bconsole, you will get the
186 You have the following choices:
191 Select termination code: (1-4):
194 If you select the {\bf All} option, you may see something like:
197 Select termination code: (1-4): 4
198 +-------+-------------+---------------------+------+-------+----------+-----------+-----------+
199 | jobid | name | starttime | type | level | jobfiles |
200 jobbytes | jobstatus |
201 +-------+-------------+---------------------+------+-------+----------+-----------+-----------+
202 | 1 | Incremental | 2012-03-26 12:15:21 | B | F | 0 |
204 | 2 | Incremental | 2012-03-26 12:18:14 | B | F | 350 |
206 | 3 | Incremental | 2012-03-26 12:18:30 | B | F | 0 |
208 | 4 | Incremental | 2012-03-26 12:18:38 | B | F | 331 |
210 +-------+-------------+---------------------+------+-------+----------+-----------+-----------+
211 Enter the JobId list to select:
214 Then you may enter one or more JobIds to be restarted, which may
215 take the form of a list of JobIds separated by commas, and/or JobId
216 ranges such as {\bf 1-4}, which indicates you want to restart JobIds
217 1 through 4, inclusive.
219 \subsection{Support for Exchange Incremental Backups}
220 The Bacula Enterprise version 6.0 VSS plugin now supports
221 Full and Incremental backups for Exchange. We strongly
222 recommend that you do not attempt to run Differential jobs with
223 Exchange as it is likely to produce a situation where restores
224 will no longer select the correct jobs, and thus the
225 Windows Exchange VSS writer will fail when applying log files.
226 There is a Bacula Systems Enterprise white paper that provides
227 the details of backup and restore of Exchange 2010 with the
231 Restores can be done while Exchange is running, but you
232 must first unmount (dismount in Microsoft terms) any database
233 you wish to restore and explicitly mark them to permit a
234 restore operation (see the white paper for details).
237 This project was funded by Bacula Systems and is available with the Bacula
240 \subsection{Support for MSSQL Block Level Backups}
241 With the addition of block level backup support to the
242 Bacula Enterprise VSS MSSQL component, you can now do
243 Differential backups in addition to Full backups.
244 Differential backups use Microsoft's partial block backup
245 (a block differencing or deduplication that we call Delta).
246 This partial block backup permits backing up only those
247 blocks that have changed. Database restores can be made while
248 the MSSQL server is running, but any databases selected for
249 restore will be automatically taken offline by the MSSQL
250 server during the restore process.
252 Incremental backups for MSSQL are not support by
253 Microsoft. We strongly recommend that you not perform Incremental
254 backups with MSSQL as they will probably produce a situation
255 where restore will no longer work correctly.
258 We are currently working on producing a white paper that will give more
259 details of backup and restore with MSSQL. One point to note is that during
260 a restore, you will normally not want to restore the {\bf master} database.
261 You must exclude it from the backup selections that you have made or the
265 It is possible to restore the {\bf master} database, but you must
266 first shutdown the MSSQL server, then you must perform special
267 recovery commands. Please see Microsoft documentation on how
268 to restore the master database.
271 This project was funded by Bacula Systems and is available with the Bacula
275 \subsection{Job Bandwidth Limitation}
277 The new {\bf Job Bandwidth Limitation} directive may be added to the File
278 daemon's and/or Director's configuration to limit the bandwidth used by a Job
279 on a Client. It can be set in the File daemon's conf file for all Jobs run in
280 that File daemon, or it can be set for each Job in the Director's conf file.
286 Working Directory = /some/path
287 Pid Directory = /some/path
289 Maximum Bandwidth Per Job = 5Mb/s
293 The above example would cause any jobs running with the FileDaemon to not
294 exceed 5Mb/s of throughput when sending data to the Storage Daemon.
296 You can specify the speed parameter in k/s, Kb/s, m/s, Mb/s.
302 FileSet = FS_localhost
305 Maximum Bandwidth = 5Mb/s
310 The above example would cause Job \texttt{localhost-data} to not exceed 5MB/s
311 of throughput when sending data from the File daemon to the Storage daemon.
313 A new console command \texttt{setbandwidth} permits to set dynamically the
314 maximum throughput of a running Job or for future jobs of a Client.
317 * setbandwidth limit=1000000 jobid=10
320 The \texttt{limit} parameter is in Kb/s.
323 This project was funded by Bacula Systems and is available in
324 the Enterprise Edition.
326 \subsection{Incremental/Differential Block Level Difference Backup}
328 The new \texttt{delta} Plugin is able to compute and apply signature-based file
329 differences. It can be used to backup only changes in a big binary file like
330 Outlook PST, VirtualBox/VMware images or database files.
332 It supports both Incremental and Differential backups and stores signatures
333 database in the File Daemon working directory. This plugin is available on all
334 platform including Windows 32 and 64bit.
336 Accurate option should be turned on in the Job resource.
349 Plugin = "delta:/home/eric/.VirtualBox/HardDisks/lenny-i386.vdi"
354 Name = DeltaFS-Include
362 # Use the Options{} filtering and options
363 File = /home/user/.VirtualBox
369 Please contact Bacula Systems support to get Delta Plugin specific
373 This project was funded by Bacula Systems and is available with the Bacula
376 \subsection{SAN Shared Tape Storage Plugin}
378 The problem with backing up multiple servers at the same time to the
379 same tape library (or autoloader) is that if both servers access the
380 same tape drive same time, you will very likely get data corruption.
381 This is where the Bacula Systems shared tape storage plugin comes into play. The
382 plugin ensures that only one server at a time can connect to each device
383 (tape drive) by using the SPC-3 SCSI reservation protocol. Please contact
384 Bacula Systems support to get SAN Shared Storage Plugin specific
388 This project was funded by Bacula Systems and is available with Bacula
391 \subsection{Advanced Autochanger Usage}
393 The new \texttt{Shared Storage} Director's directive is a Bacula Enterprise
394 feature that allows you to share volumes between different Storage
395 resources. This directive should be used \textbf{only} if all \texttt{Media
396 Type} are correctly set across all Devices.
398 The \texttt{Shared Storage} directive should be used when using the SAN
399 Shared Storage plugin or when accessing from the Director Storage resources
400 directly to Devices of an Autochanger.
402 When sharing volumes between different Storage resources, you will
403 need also to use the \texttt{reset-storageid} script before using the
404 \texttt{update slots} command. This script can be scheduled once a day in
408 $ /opt/bacula/scripts/reset-storageid MediaType StorageName
410 * update slots storage=StorageName drive=0
413 Please contact Bacula Systems support to get help on this advanced
417 This project was funded by Bacula Systems and is available with Bacula
420 \subsection{Enhancement of the NDMP Plugin}
422 The previous NDMP Plugin 4.0 was fully supporting only the NetApp hardware, the
423 new NDMP Plugin should now be able to support all NAS vendors with the
424 \texttt{volume\_format} plugin command option.
426 On some NDMP devices such as Celera or Blueray, the administrator can use arbitrary
427 volume structure name, ex:
431 /rootvolume/volume_tmp
435 The NDMP plugin should be aware of the structure organization in order to
436 detect if the administrator wants to restore in a new volume
437 (\texttt{where=/dev/vol\_tmp}) or inside a subdirectory of the targeted volume
438 (\texttt{where=/tmp}).
445 Plugin = "ndmp:host=nasbox user=root pass=root file=/dev/vol1 volume_format=/dev/"
450 Please contact Bacula Systems support to get NDMP Plugin specific
454 This project was funded by Bacula Systems and is available with the Bacula
457 \subsection{Always Backup a File}
459 When the Accurate mode is turned on, you can decide to always backup a file
460 by using then new {\bf A} Accurate option in your FileSet. For example:
483 This project was funded by Bacula Systems based on an idea of James Harper and
484 is available with the Bacula Enterprise Edition.
486 \subsection{Setting Accurate Mode During at Runtime}
488 You are now able to specify the Accurate mode on the \texttt{run} command and
489 in the Schedule resource.
492 * run accurate=yes job=Test
498 Run = Full 1st sun at 23:05
499 Run = Differential accurate=yes 2nd-5th sun at 23:05
500 Run = Incremental accurate=no mon-sat at 23:05
504 It can allow you to save memory and and CPU resources on the catalog server in
508 These advanced tuning options are available with the Bacula Enterprise Edition.
510 % Common with community
511 \subsection{Additions to RunScript variables}
512 You can have access to JobBytes, JobFiles and Director name using \%b, \%F and \%D
513 in your runscript command. The Client address is now available through \%h.
516 RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%F ClientAddress=%h Dir=%D"
519 \subsection{LZO Compression}
521 LZO compression was added in the Unix File Daemon. From the user point of view,
522 it works like the GZIP compression (just replace {\bf compression=GZIP} with
523 {\bf compression=LZO}).
528 Options { compression=LZO }
534 LZO provides much faster compression and decompression speed but lower
535 compression ratio than GZIP. It is a good option when you backup to disk. For
536 tape, the built-in compression may be a better option.
538 LZO is a good alternative for GZIP1 when you don't want to slow down your
539 backup. On a modern CPU it should be able to run almost as fast as:
542 \item your client can read data from disk. Unless you have very fast disks like
543 SSD or large/fast RAID array.
544 \item the data transfers between the file daemon and the storage daemon even on
548 Note that bacula only use one compression level LZO1X-1.
551 The code for this feature was contributed by Laurent Papier.
553 \subsection{New Tray Monitor}
555 Since the old integrated Windows tray monitor doesn't work with
556 recent Windows versions, we have written a new Qt Tray Monitor that is available
557 for both Linux and Windows. In addition to all the previous features,
558 this new version allows you to run Backups from
559 the tray monitor menu.
561 %\begin{figure}[htbp]
563 % \includegraphics[width=10cm]{\idir
564 \bsysimageH{tray-monitor}{New tray monitor}{figbs6:traymonitor}
565 % \label{fig:traymonitor}
566 % \caption{New tray monitor}
569 %\begin{figure}[htbp]
571 \bsysimageH{tray-monitor1}{Run a Job through the new tray monitor}{figbs6:traymonitor1}
572 % \includegraphics[width=10cm]{\idir tray-monitor1}
573 % \label{fig:traymonitor1}
574 % \caption{Run a Job through the new tray monitor}
578 To be able to run a job from the tray monitor, you need to
579 allow specific commands in the Director monitor console:
584 CommandACL = status, .clients, .jobs, .pools, .storage, .filesets, .messages, run
585 ClientACL = *all* # you can restrict to a specific host
597 This project was funded by Bacula Systems and is available with Bacula
598 the Enterprise Edition and the Community Edition.
600 \subsection{Purge Migration Job}
602 The new {\bf Purge Migration Job} directive may be added to the Migration
603 Job definition in the Director's configuration file. When it is enabled
604 the Job that was migrated during a migration will be purged at
605 the end of the migration job.
613 Client = localhost-fd
616 Storage = DiskChanger
619 Selection Pattern = ".*Save"
621 Purge Migration Job = yes
627 This project was submitted by Dunlap Blake; testing and documentation was funded
630 \subsection{Changes in the Pruning Algorithm}
632 We rewrote the job pruning algorithm in this version. Previously, in some users
633 reported that the pruning process at the end of jobs was very long. It should
634 not be longer the case. Now, Bacula won't prune automatically a Job if this
635 particular Job is needed to restore data. Example:
639 JobId: 2 Level: Incremental
640 JobId: 3 Level: Incremental
641 JobId: 4 Level: Differential
642 .. Other incrementals up to now
645 In this example, if the Job Retention defined in the Pool or in the Client
646 resource causes that Jobs with Jobid in 1,2,3,4 can be pruned, Bacula will
647 detect that JobId 1 and 4 are essential to restore data at the current state
648 and will prune only JobId 2 and 3.
650 \texttt{Important}, this change affect only the automatic pruning step after a
651 Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the
652 \texttt{VolumeRetention} period, important jobs can be pruned.
654 \subsection{Ability to Verify any specified Job}
655 You now have the ability to tell Bacula which Job should verify instead of
656 automatically verify just the last one.
658 This feature can be used with VolumeToCatalog, DiskToCatalog and Catalog level.
660 To verify a given job, just specify the Job jobid in argument when starting the
663 *run job=VerifyVolume jobid=1 level=VolumeToCatalog
665 JobName: VerifyVolume
666 Level: VolumeToCatalog
669 Pool: Default (From Job resource)
670 Storage: File (From Job resource)
671 Verify Job: VerifyVol.2010-09-08_14.17.17_03
672 Verify List: /tmp/regress/working/VerifyVol.bsr
673 When: 2010-09-08 14:17:31
675 OK to run? (yes/mod/no):
679 This project was funded by Bacula Systems and is available with Bacula
680 Enterprise Edition and Community Edition.