1 \chapter{New Features in Bacula Enterprise 6.0.x}
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 \chapter{New Features in Bacula Enterprise 6.0.5}
12 \section{Maximum Reload Requests}
14 The new Director directive \texttt{Maximum Reload Requests} permits to
15 configure the number of reload requests that can be done while jobs are
21 Maximum Reload Requests = 64
27 \section{FD Storage Address}
29 When the Director is behind a NAT, in a WAN area, to connect to
31 the StorageDaemon, the Director uses an "external" ip address,
32 and the FileDaemon should use an "internal" ip address to contact the
35 The normal way to handle this situation is to use a canonical name such as
36 "storage-server" that will be resolved on the Director side as the WAN address
37 and on the Client side as the LAN address. This is now possible to configure
38 this parameter using the new \texttt{FDStorageAddress} Storage
44 \includegraphics[width=10cm]{\idir BackupOverWan1}
45 \label{fig:fdstorageaddress}
46 \caption{Backup over WAN}
53 FD Storage Address = 10.0.0.1
59 % # or in the Client resouce
64 % FD Storage Address = 10.0.0.1
70 % Note that using the Client \texttt{FDStorageAddress} directive will not allow
71 % to use multiple Storage Daemon, all Backup or Restore requests will be sent to
72 % the specified \texttt{FDStorageAddress}.
74 \chapter{New Features in Bacula Enterprise 6.0.0}
76 \section{Incomplete Jobs}
77 During a backup, if the Storage daemon experiences disconnection
78 with the File daemon during backup (normally a comm line problem
79 or possibly an FD failure), under conditions that the SD determines
80 to be safe it will make the failed job as Incomplete rather than
81 failed. This is done only if there is sufficient valid backup
82 data that was written to the Volume. The advantage of an Incomplete
83 job is that it can be restarted by the new bconsole {\bf restart}
84 command from the point where it left off rather than from the
85 beginning of the jobs as is the case with a cancel.
87 \section{The Stop Command}
88 Bacula has been enhanced to provide a {\bf stop} command,
89 very similar to the {\bf cancel} command with the main difference
90 that the Job that is stopped is marked as Incomplete so that
91 it can be restarted later by the {\bf restart} command where
92 it left off (see below). The {\bf stop} command with no
93 arguments, will like the cancel command, prompt you with the
94 list of running jobs allowing you to select one, which might
95 look like the following:
100 1: JobId=3 Job=Incremental.2012-03-26_12.04.26_07
101 2: JobId=4 Job=Incremental.2012-03-26_12.04.30_08
102 3: JobId=5 Job=Incremental.2012-03-26_12.04.36_09
103 Choose Job to stop (1-3): 2
104 2001 Job "Incremental.2012-03-26_12.04.30_08" marked to be stopped.
105 3000 JobId=4 Job="Incremental.2012-03-26_12.04.30_08" marked to be stopped.
108 \section{The Restart Command}
109 The new {\bf Restart command} allows console users to restart
110 a canceled, failed, or incomplete Job. For canceled and failed
111 Jobs, the Job will restart from the beginning. For incomplete
112 Jobs the Job will restart at the point that it was stopped either
113 by a stop command or by some recoverable failure.
116 If you enter the {\bf restart} command in bconsole, you will get the
121 You have the following choices:
126 Select termination code: (1-4):
129 If you select the {\bf All} option, you may see something like:
132 Select termination code: (1-4): 4
133 +-------+-------------+---------------------+------+-------+----------+-----------+-----------+
134 | jobid | name | starttime | type | level | jobfiles |
135 jobbytes | jobstatus |
136 +-------+-------------+---------------------+------+-------+----------+-----------+-----------+
137 | 1 | Incremental | 2012-03-26 12:15:21 | B | F | 0 |
139 | 2 | Incremental | 2012-03-26 12:18:14 | B | F | 350 |
141 | 3 | Incremental | 2012-03-26 12:18:30 | B | F | 0 |
143 | 4 | Incremental | 2012-03-26 12:18:38 | B | F | 331 |
145 +-------+-------------+---------------------+------+-------+----------+-----------+-----------+
146 Enter the JobId list to select:
149 Then you may enter one or more JobIds to be restarted, which may
150 take the form of a list of JobIds separated by commas, and/or JobId
151 ranges such as {\bf 1-4}, which indicates you want to restart JobIds
152 1 through 4, inclusive.
154 \section{Support for Exchange Incremental Backups}
155 The Bacula Enterprise version 6.0 VSS plugin now supports
156 Full and Incremental backups for Exchange. We strongly
157 recommend that you do not attempt to run Differential jobs with
158 Exchange as it is likely to produce a situation where restores
159 will no longer select the correct jobs, and thus the
160 Windows Exchange VSS writer will fail when applying log files.
161 There is a Bacula Systems Enterprise white paper that provides
162 the details of backup and restore of Exchange 2010 with the
166 Restores can be done while Exchange is running, but you
167 must first unmount (dismount in Microsoft terms) any database
168 you wish to restore and explicitly mark them to permit a
169 restore operation (see the white paper for details).
172 This project was funded by Bacula Systems and is available with the Bacula
175 \section{Support for MSSQL Block Level Backups}
176 With the addition of block level backup support to the
177 Bacula Enterprise VSS MSSQL component, you can now do
178 Differential backups in addition to Full backups.
179 Differential backups use Microsoft's partial block backup
180 (a block differencing or deduplication that we call Delta).
181 This partial block backup permits backing up only those
182 blocks that have changed. Database restores can be made while
183 the MSSQL server is running, but any databases selected for
184 restore will be automatically taken offline by the MSSQL
185 server during the restore process.
187 Incremental backups for MSSQL are not support by
188 Microsoft. We strongly recommend that you not perform Incremental
189 backups with MSSQL as they will probably produce a situation
190 where restore will no longer work correctly.
193 We are currently working on producing a white paper that will give more
194 details of backup and restore with MSSQL. One point to note is that during
195 a restore, you will normally not want to restore the {\bf master} database.
196 You must exclude it from the backup selections that you have made or the
200 It is possible to restore the {\bf master} database, but you must
201 first shutdown the MSSQL server, then you must perform special
202 recovery commands. Please see Microsoft documentation on how
203 to restore the master database.
206 This project was funded by Bacula Systems and is available with the Bacula
210 \section{Job Bandwidth Limitation}
212 The new {\bf Job Bandwidth Limitation} directive may be added to the File
213 daemon's and/or Director's configuration to limit the bandwidth used by a Job
214 on a Client. It can be set in the File daemon's conf file for all Jobs run in
215 that File daemon, or it can be set for each Job in the Director's conf file.
221 Working Directory = /some/path
222 Pid Directory = /some/path
224 Maximum Bandwidth Per Job = 5Mb/s
228 The above example would cause any jobs running with the FileDaemon to not
229 exceed 5Mb/s of throughput when sending data to the Storage Daemon.
231 You can specify the speed parameter in k/s, Kb/s, m/s, Mb/s.
237 FileSet = FS_localhost
240 Maximum Bandwidth = 5Mb/s
245 The above example would cause Job \texttt{localhost-data} to not exceed 5MB/s
246 of throughput when sending data from the File daemon to the Storage daemon.
248 A new console command \texttt{setbandwidth} permits to set dynamically the
249 maximum throughput of a running Job or for future jobs of a Client.
252 * setbandwidth limit=1000000 jobid=10
255 The \texttt{limit} parameter is in Kb/s.
258 This project was funded by Bacula Systems and is available in
259 the Enterprise Edition.
261 \section{Incremental/Differential Block Level Difference Backup}
263 The new \texttt{delta} Plugin is able to compute and apply signature-based file
264 differences. It can be used to backup only changes in a big binary file like
265 Outlook PST, VirtualBox/VMware images or database files.
267 It supports both Incremental and Differential backups and stores signatures
268 database in the File Daemon working directory. This plugin is available on all
269 platform including Windows 32 and 64bit.
271 Accurate option should be turned on in the Job resource.
284 Plugin = "delta:/home/eric/.VirtualBox/HardDisks/lenny-i386.vdi"
289 Name = DeltaFS-Include
297 # Use the Options{} filtering and options
298 File = /home/user/.VirtualBox
304 Please contact Bacula Systems support to get Delta Plugin specific
308 This project was funded by Bacula Systems and is available with the Bacula
311 \section{SAN Shared Tape Storage Plugin}
313 The problem with backing up multiple servers at the same time to the
314 same tape library (or autoloader) is that if both servers access the
315 same tape drive same time, you will very likely get data corruption.
316 This is where the Bacula Systems shared tape storage plugin comes into play. The
317 plugin ensures that only one server at a time can connect to each device
318 (tape drive) by using the SPC-3 SCSI reservation protocol. Please contact
319 Bacula Systems support to get SAN Shared Storage Plugin specific
323 This project was funded by Bacula Systems and is available with Bacula
326 \section{Advanced Autochanger Usage}
328 The new \texttt{Shared Storage} Director's directive is a Bacula Enterprise
329 feature that allows you to share volumes between different Storage
330 resources. This directive should be used \textbf{only} if all \texttt{Media
331 Type} are correctly set across all Devices.
333 The \texttt{Shared Storage} directive should be used when using the SAN
334 Shared Storage plugin or when accessing from the Director Storage resources
335 directly to Devices of an Autochanger.
337 When sharing volumes between different Storage resources, you will
338 need also to use the \texttt{reset-storageid} script before using the
339 \texttt{update slots} command. This script can be scheduled once a day in
343 $ /opt/bacula/scripts/reset-storageid MediaType StorageName
345 * update slots storage=StorageName drive=0
348 Please contact Bacula Systems support to get help on this advanced
352 This project was funded by Bacula Systems and is available with Bacula
355 \section{Enhancement of the NDMP Plugin}
357 The previous NDMP Plugin 4.0 was fully supporting only the NetApp hardware, the
358 new NDMP Plugin should now be able to support all NAS vendors with the
359 \texttt{volume\_format} plugin command option.
361 On some NDMP devices such as Celera or Blueray, the administrator can use arbitrary
362 volume structure name, ex:
366 /rootvolume/volume_tmp
370 The NDMP plugin should be aware of the structure organization in order to
371 detect if the administrator wants to restore in a new volume
372 (\texttt{where=/dev/vol\_tmp}) or inside a subdirectory of the targeted volume
373 (\texttt{where=/tmp}).
380 Plugin = "ndmp:host=nasbox user=root pass=root file=/dev/vol1 volume_format=/dev/"
385 Please contact Bacula Systems support to get NDMP Plugin specific
389 This project was funded by Bacula Systems and is available with the Bacula
392 \section{Always Backup a File}
394 When the Accurate mode is turned on, you can decide to always backup a file
395 by using then new {\bf A} Accurate option in your FileSet. For example:
418 This project was funded by Bacula Systems based on an idea of James Harper and
419 is available with the Bacula Enterprise Edition.
421 \section{Setting Accurate Mode During at Runtime}
423 You are now able to specify the Accurate mode on the \texttt{run} command and
424 in the Schedule resource.
427 * run accurate=yes job=Test
433 Run = Full 1st sun at 23:05
434 Run = Differential accurate=yes 2nd-5th sun at 23:05
435 Run = Incremental accurate=no mon-sat at 23:05
439 It can allow you to save memory and and CPU resources on the catalog server in
443 These advanced tuning options are available with the Bacula Enterprise Edition.
445 % Common with community
446 \section{Additions to RunScript variables}
447 You can have access to JobBytes, JobFiles and Director name using \%b, \%F and \%D
448 in your runscript command. The Client address is now available through \%h.
451 RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%F ClientAddress=%h Dir=%D"
454 \section{LZO Compression}
456 LZO compression was added in the Unix File Daemon. From the user point of view,
457 it works like the GZIP compression (just replace {\bf compression=GZIP} with
458 {\bf compression=LZO}).
463 Options { compression=LZO }
469 LZO provides much faster compression and decompression speed but lower
470 compression ratio than GZIP. It is a good option when you backup to disk. For
471 tape, the built-in compression may be a better option.
473 LZO is a good alternative for GZIP1 when you don't want to slow down your
474 backup. On a modern CPU it should be able to run almost as fast as:
477 \item your client can read data from disk. Unless you have very fast disks like
478 SSD or large/fast RAID array.
479 \item the data transfers between the file daemon and the storage daemon even on
483 Note that bacula only use one compression level LZO1X-1.
486 The code for this feature was contributed by Laurent Papier.
488 \section{New Tray Monitor}
490 Since the old integrated Windows tray monitor doesn't work with
491 recent Windows versions, we have written a new Qt Tray Monitor that is available
492 for both Linux and Windows. In addition to all the previous features,
493 this new version allows you to run Backups from
494 the tray monitor menu.
498 \includegraphics[width=10cm]{\idir tray-monitor}
499 \label{fig:traymonitor}
500 \caption{New tray monitor}
505 \includegraphics[width=10cm]{\idir tray-monitor1}
506 \label{fig:traymonitor1}
507 \caption{Run a Job through the new tray monitor}
511 To be able to run a job from the tray monitor, you need to
512 allow specific commands in the Director monitor console:
517 CommandACL = status, .clients, .jobs, .pools, .storage, .filesets, .messages, run
518 ClientACL = *all* # you can restrict to a specific host
530 This project was funded by Bacula Systems and is available with Bacula
531 the Enterprise Edition and the Community Edition.
533 \section{Purge Migration Job}
535 The new {\bf Purge Migration Job} directive may be added to the Migration
536 Job definition in the Director's configuration file. When it is enabled
537 the Job that was migrated during a migration will be purged at
538 the end of the migration job.
546 Client = localhost-fd
549 Storage = DiskChanger
552 Selection Pattern = ".*Save"
554 Purge Migration Job = yes
560 This project was submitted by Dunlap Blake; testing and documentation was funded
563 \section{Changes in the Pruning Algorithm}
565 We rewrote the job pruning algorithm in this version. Previously, in some users
566 reported that the pruning process at the end of jobs was very long. It should
567 not be longer the case. Now, Bacula won't prune automatically a Job if this
568 particular Job is needed to restore data. Example:
572 JobId: 2 Level: Incremental
573 JobId: 3 Level: Incremental
574 JobId: 4 Level: Differential
575 .. Other incrementals up to now
578 In this example, if the Job Retention defined in the Pool or in the Client
579 resource causes that Jobs with Jobid in 1,2,3,4 can be pruned, Bacula will
580 detect that JobId 1 and 4 are essential to restore data at the current state
581 and will prune only JobId 2 and 3.
583 \texttt{Important}, this change affect only the automatic pruning step after a
584 Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the
585 \texttt{VolumeRetention} period, important jobs can be pruned.
587 \section{Ability to Verify any specified Job}
588 You now have the ability to tell Bacula which Job should verify instead of
589 automatically verify just the last one.
591 This feature can be used with VolumeToCatalog, DiskToCatalog and Catalog level.
593 To verify a given job, just specify the Job jobid in argument when starting the
596 *run job=VerifyVolume jobid=1 level=VolumeToCatalog
598 JobName: VerifyVolume
599 Level: VolumeToCatalog
602 Pool: Default (From Job resource)
603 Storage: File (From Job resource)
604 Verify Job: VerifyVol.2010-09-08_14.17.17_03
605 Verify List: /tmp/regress/working/VerifyVol.bsr
606 When: 2010-09-08 14:17:31
608 OK to run? (yes/mod/no):
612 This project was funded by Bacula Systems and is available with Bacula
613 Enterprise Edition and Community Edition.