Debian Codegraph @

manuals/en/concept/how-bacula-works.tex

raw
1 \chapter{How Bacula Works}
2 \section{Introduction}
3 \subsection{The Job}
4 The \emph{Job} is probably one of the most important terms to understand when working with Bacula. There are several types of Jobs, the most known and the most used\footnote{Going by the number of Jobs!} is the ``Backup'' Job. The most important is, in our opinion, the ``Restore'' Job. Some others, like ``Admin'' Jobs are also quite useful. All of them are described in more detail in the chapter~\vref{chap:jobs}.
5
6 \subsection{The Volume}
7 Another important term is the \emph{Volume}: a Volume is the place where Bacula stores backed up data. When backing up to tapes, a Volume is identical to a tape and when backing up to disks, a Volume is a file. To fully understand Volumes, please read the chapter \vref{chap:volumes} dedicated to their description.
8
9 \subsection{Good to Know}
10 \paragraph{Bacula backs up files}
11 By default, when working without special plugins, Bacula backs up files and nothing else.
12
13 \paragraph{Failed Jobs}
14 When running a backup Job, the Bacula client sends data and metadata to the Storage Daemon. In some situations a backup Job may fail. It is important to know that one can restore the already saved data from failed Jobs.
15
16 \section{Jobs Step by Step}
17 \subsection{Opening Sessions}
18 Bacula is network based and uses TCP/IP connections to exchange commands, information and data between its components. It needs to open sessions and these sessions are opened from one component to another one as shown figure~\vref{fig:opening-sessions}.
19
20 %\begin{absolutelynopagebreak}%
21 \begin{bitemize}
22 \item DIR $\Rightarrow$ FD
23 \item DIR $\Rightarrow$ SD
24 \item FD $\Rightarrow$\footnote{This is the default. However the session can be opened the other way with the ``SD calls Client'' directive} SD
25 \end{bitemize}%
26 %\end{absolutelynopagebreak}
27
28 \bimageH[0.75\linewidth]{bee8-sessions}{TCP/IP session ``directions''}{fig:opening-sessions}
29 %% \begin{figure}[htpb]
30 %% \begin{center}
31 %% \includegraphics[width=]
32 %% \caption
33 %% \end{center}
34 %% \end{figure}
35
36 \subsection{Data Stream}
37 When running a backup Job, the stream of data is sent from the File Daemon to the Storage Daemon (data plus metadata). At the end of a backup Job, the Storage daemon sends the metadata to the Director to be inserted into the Catalog (see figure~\vref{fig:datastream}).
38
39 \bimageH[0.75\linewidth]{bee8-data-flow}{Data and metadata streams}{fig:datastream}
40 %% \begin{figure}[htpb]
41 %% \begin{center}
42 %% \includegraphics[width=0.75\linewidth]{bee8-data-flow}
43 %% \caption{Data and metadata streams}\label{fig:datastream}
44 %% \end{center}
45 %% \end{figure}
46
47 \subsection{Catalog Database Management}
48 As mentioned earlier, Bacula stores its metadata in an SQL Catalog. PostgreSQL, MySQL and SQLite are the database engines that are supported by Bacula. We recommend to use SQLite only for basic testing purposes.
49
50 The Catalog management is directly related to keeping backup Jobs data available, and it is often automatically triggered by finishing Jobs.
51
52 \subsubsection{Retention periods}
53 There are various kinds of retention periods that Bacula uses: File Retention Period, Job Retention Period, and Volume Retention Period. Each of these retention periods defines the minimal time that specific records will be kept in the Catalog database. This should not be confused with the time that the data saved to a Volume is valid and available for restore -- in many cases, data will be available much longer\footnote{Actually the data remains on the Volume until the Volume is recycled or truncated.} than any of the Retention Periods configured.
54
55 \paragraph{The File Retention Period} determines the time that File records are kept in the Catalog database. This period is important for two reasons: the first is that as long as File records remain in the database, you can ``browse'' the database with a console btool and restore any individual file. Once the File records are removed or pruned from the database, the individual files of a backup Job can no longer be ``browsed''.
56
57 The second reason for carefully choosing the File Retention Period is because the database File records typically use the most storage space in the database. As a consequence, you must ensure that regular ``pruning'' of the database file records is done to keep your database from growing too big.
58
59 \paragraph{The Job Retention Period} is the length of time that Job records will be kept in the database. Note, all the File records are tied to the Job that saved those files. The File records can be purged, leaving the Job records. In this case, information will be available about the Jobs that ran, but not the details of the files that were backed up. When pruning a Job, Bacula will purge all its File records.
60
61 \paragraph{The Volume Retention Period} is the minimum time following the last write that a Volume will be kept until the Volume can be reused. Bacula will normally not overwrite a Volume that contains data still inside its Retention period, but if Bacula runs out of usable Volumes, it can select any Volume which is out of its Retention time for \emph{recycling}, at this time automatically removing the related Job and File information from the Catalog.
62
63 \subsubsection{Pruning}
64 To keep the Catalog to a manageable size, the backup information should be removed (pruned) from the Catalog after the defined File and Job Retention Periods. Bacula by default automatically prunes the catalog database entries according to the retention periods defined.
65
66 \subsubsection{Purging}
67 Once all the database records that concern a particular Volume have been ``pruned'' as described above respecting the retention periods, the Volume is said to be ``purged'' (i.e. has no more catalog entries).\par\medskip
68
69 It is, however, possible to submit commands to Bacula to purge specific information, which will not respect configured retention periods. Naturally, this is something that should only be done with the greatest care.
70
71 \subsection{Good to Know}
72 \paragraph{Getting space back} Bacula will try to keep your data safe as long as possible, thus purging a volume will not automatically reclaim the used space. %is not sufficient to get the space back before the recycling process.
73 %\paragraph{Reusing vs creation} Instead of reusing an existing volume, Bacula will try \textbf{first} to create a new one.
74 If you want to reuse space, you must configure Bacula accordingly\footnote{See chapter \vref{chap:volumes}}.
75
76 \section{Bacula Users and Administrators}\label{sec:how:users}
77 When considering enterprise backup and recovery environments, it is often useful to distinguish between different types or classes of people interacting with the backup and recovery tool:
78 \begin{description}
79 \item[Administrators] can control all aspects of Bacula, and modify its configuration.
80 \item[Operators] interact with Bacula, following defined procedures, are responsible for certain operational aspects, but do not touch the configuration.
81 \item[Users] or end-users are people who have no access to the Bacula configuration or all Bacula's features, but may access certain of its functions. A typical example is that a user can restore their own data, to their own computer, but can not see other backup data or access computers for which they are not responsible.
82 \end{description}
83
84 Bacula itself does not have the concept of users or administrators, but has ``Consoles'' (see section~\vref{sec:how:consoles}) that are designed to allow some users to have limited permissions regarding Bacula. However the \emph{BWeb Management Suite}, the Bacula Enterprise Web-based tool for management and configuration, includes the concepts of users, groups and permissions.
85
86 \section{Consoles}\label{sec:how:consoles}
87 \subsection{Overview}
88 To allow interaction from administrators or users, Bacula uses \emph{Consoles}.
89 The Bacula Console (sometimes called the User Agent) is a btool that allows the user or the System Administrator to interact with the Bacula Director Daemon while the daemon is running.
90 Note that, even when managing storage or checking client status, the Console interacts with the Director only, which in turn contacts the other daemons as needed.
91
92 The current Bacula Console comes in multiple versions:
93 \begin{bitemize}
94 \item a shell interface (TTY style),
95 \item a Qt GUI interface
96 \item Web GUI interfaces
97 \end{bitemize}
98 All permit the administrator or authorized users to interact with Bacula. You can determine the status of a particular Job, examine the contents of the Catalog as well as perform certain tape manipulations with the Console btool. Running Jobs is one of the more central tasks done with the Console.
99
100 Since the Console btool interacts with the Director through the network, the Console and Director btools do not necessarily need to run on the same machine.
101 In fact, in an installation containing a single tape drive, a certain minimal knowledge of the Console btool may be needed in order for Bacula to be able to write on more than one Volume, because when Bacula requests a new one, it waits until the user, via the Console btool, indicates that the new Volume is mounted or labeled to be used.
102
103 \subsection{Integration}
104 Because the Console is like other Bacula components, it requires configuration. To know more about Console configuration and/or management, please see the \emph{Console Configuration} chapter of the Bacula main manual (chapter 19).
105
106 \subsection{User Restrictions}
107 If you want to give access to a particular user (not overall Bacula administrator), you need to configure a console for him/her. In particular, it may be desirable to implement specific Access Control Lists to prevent users from accessing data they are not authorized for. This part is covered in the \emph{Console Configuration} chapter of the Bacula main manual (chapter 19).
108
109 \subsubsection{Non Bacula Enterprise Consoles}
110 There are many other GUI consoles available designed and proposed by the Bacula community. Here is a non-exhaustive list, ask the community if you want more information on one or another.
111 \begin{bitemize}
112 \item \btool{baculum} (see \bfootref{http://www.bacula.org/}{www.bacula.org})
113 \item \btool{bacula-web} (see \bfootref{http://www.bacula-web.org/}{www.bacula-web.org})
114 \item \btool{webacula} (see \bfootref{http://webacula.sourceforge.net/}{webacula.sourceforge.net})
115 \end{bitemize}
116
117 \section{Configuration}
118 \subsection{Installation Directory tree}
119 When installing the Bacula Enterprise version\footnote{Bacula Community version has its own installation process and default locations} the following directory tree is created\footnote{Some additional directories under \texttt{/opt/bacula} exist and are not presented here}:
120 \begin{bitemize}
121 \item \texttt{\textbf{/opt/bacula/bin}}: Bacula Enterprise binaries directory
122 \item \texttt{\textbf{/opt/bacula/working}}: Working directory
123 \item \texttt{\textbf{/opt/bacula/etc}}: Configuration files root directory
124 \item \texttt{\textbf{/opt/bacula/scripts}}: Scripts directory
125 \end{bitemize}
126
127 \subsection{Configuration Files}
128 Bacula's configuration is stored in plain text files, and a configuration file can include other files
129 \footnote{Actually, it is also possible to create configuration parts by btool or script, while the daemon reads its configuration or while a Job is executed.},
130 so it is possible to have a structured configuration file repository.
131
132 Each daemon has its own configuration consisting of a set of \emph{Resource} definitions. These resources are very similar from one service to another, but may contain different \emph{Directives} (records) depending on the service. For example, in the Director's resource file, the \bdirective{Director} resource defines the name of the Director, a number of global parameters and the password needed to access it from a Console. In the File Daemon configuration file, the \bdirective{Director} resource specifies which Directors are permitted to use the File Daemon.
133
134 \begin{bitemize}
135 \item Director $\Rightarrow$ \texttt{bacula-dir.conf}
136 \item File Daemon $\Rightarrow$ \texttt{bacula-fd.conf}
137 \item Storage Daemon $\Rightarrow$ \texttt{bacula-sd.conf}
138 \item bconsole $\Rightarrow$ \texttt{bconsole.conf}
139 \item BWeb Management Suite $\Rightarrow$ \texttt{bweb.conf} (this file is \textbf{not} structured the same way the others are!)
140 \item Bacula Administration Tool (aka BAT) $\Rightarrow$ \texttt{bat.conf}
141 \end{bitemize}
142 The configuration files must be written as plain \textbf{UTF-8}-encoded text files, which implies that any ASCII file is suitable.
143
144 \subsubsection{Director}
145 The configuration file defines a lot of resources such as:
146 \begin{bitemize}
147 \item the Director itself
148 \item at least one Restore Job
149 \item Other Job definitions
150 \item Schedules
151 \item FileSets
152 \item Storages
153 \item Clients
154 \item Catalogs
155 \item Messages
156 \item and others
157 \end{bitemize}
158 Director definition:
159 \begin{bVerbatim}
160 Director {
161 Name = the-name-of-the-director-dir
162 DIRport = 9101
163 QueryFile = "/opt/bacula/scripts/query.sql"
164 WorkingDirectory = "/opt/bacula/working"
165 PidDirectory = "/opt/bacula/working"
166 Maximum Concurrent Jobs = 10
167 Password = "password-for-the-console-to-access-the-director"
168 Messages = Daemon
169 Heartbeat Interval = 10
170 }
171 \end{bVerbatim}
172
173 A Schedule definition to specify one full backup on the Sunday of the 2\textsuperscript{nd} week of every second month starting in January, one differential on each Sunday except the Full's ones and an incremental backup six days a week:
174 \begin{bVerbatim}
175 Schedule {
176 Name = "NightlyCycle"
177 Run = Full jan,mar,may,jul,sep,nov 2nd sunday at 21:00
178 Run = Differential feb,apr,jun,aug,oct,dec 2nd sunday at 21:00
179 Run = Differential 1st,3rd-5th sunday at 21:00
180 Run = Incremental mon-sat at 21:00
181 }
182 \end{bVerbatim}
183 FileSet definition, backing up \texttt{/etc}, \texttt{/opt}, \texttt{/home}, etc. excluding some directories
184 \begin{bVerbatim}
185 FileSet {
186 Name = "fs-websites"
187 Include {
188 Options {
189 Signature = MD5
190 Compression = GZIP
191 }
192 File = /etc
193 File = /opt
194 File = /root
195 File = /home
196 File = /var/log
197 }
198 Exclude {
199 File = /home/websites/tmp
200 File = /home/websites/www/tmp/cache
201 File = /opt/bacula/working
202 File = /opt/bacula/archive
203 File = /.journal
204 File = /.fsck
205 }
206 }
207 \end{bVerbatim}
208
209 A Storage definition, as required by the Director, i.\,e. a name, an address, a port, and a media type. The director does not know about the hardware, only the storage daemon does:
210 \begin{bVerbatim}
211 Storage {
212 Name = Remote-Disk-Storage
213 Address = sd.bacula6.org
214 SDPort = 9103
215 Password = "password-for-the-director-to-access-the-storage"
216 Device = disk-autochanger
217 Media Type = da-mt
218 Maximum Concurrent Jobs = 50
219 Autochanger = Remote-Disk-Storage
220 }
221 \end{bVerbatim}
222
223 A client to back up:
224 \begin{bVerbatim}
225 Client {
226 Name = client-to-back-up-fd
227 Address = client.bacula6.org
228 FDPort = 9102
229 Catalog = BaculaCatalog
230 Password = "password-for-the-director-to-access-the-client"
231 File Retention = 10 days
232 Job Retention = 25 days
233 AutoPrune = no
234 }
235 \end{bVerbatim}
236
237 A pool definition:
238 \begin{bVerbatim}
239 Pool {
240 Name = the-pool-name
241 Pool Type = Backup
242 Recycle = yes
243 AutoPrune = no
244 Volume Retention = 30 days
245 Label Format = "pooldef-"
246 Maximum Volume Bytes = 8G
247 Maximum Volumes = 6
248 Storage = Remote-Disk-Storage
249 }
250 \end{bVerbatim}
251
252 A JobDef to handle common definitions for several Jobs:
253 \begin{bVerbatim}
254 JobDefs {
255 Name = "common-job-definitions"
256 Type = Backup
257 Level = Incremental
258 Messages = Standard
259 Schedule = NightlyCycle
260 Priority = 10
261 #
262 # The following setting saves some time sending
263 # all the metadata at the end of the job
264 Spool Attributes = yes
265 #
266 # A way to keep all of your BSR (bootstrap) files
267 # in one place with the same naming conventions
268 Write Bootstrap = "/opt/bacula/bsr/%c_%n.bsr"
269 }
270 \end{bVerbatim}
271
272 And then a Job using the above JobDefs:
273 \begin{bVerbatim}
274 Job {
275 Name = "back-up-job"
276 JobDefs = "common-job-definitions"
277 #
278 # The storage is defined inside the Pool Resource
279 # this is a best practice.
280 Pool = the-pool-name
281 Client = client-to-back-up-fd
282 FileSet = "fs-websites"
283 Schedule = NightlyCycle
284 #
285 # Below you have an example of how to include a file
286 # notice the "@" sign as first character
287 @/opt/bacula/etc/included-configuration-file.conf
288 }
289 \end{bVerbatim}
290
291 \subsubsection{File Daemon}
292 If you read carefully you will notice, on the Bacula client side, a Director Resource similar to this one:
293 \begin{bVerbatim}
294 Director {
295 Name = the-name-of-the-director-dir
296 Password = "password-for-the-director-to-access-the-client"
297 }
298 \end{bVerbatim}
299 which authorizes the Director \bhighlight{the-name-of-the-director-dir}, knowing the client password to access to the client below
300 \begin{bVerbatim}
301 FileDaemon {
302 Name = client-to-back-up-fd
303 FDport = 9102
304 WorkingDirectory = /opt/bacula/working
305 Pid Directory = /opt/bacula/working
306 Maximum Concurrent Jobs = 20
307 }
308 \end{bVerbatim}
309
310 \subsubsection{Storage Daemon}
311 Same thing here, the Director Resource
312 \begin{bVerbatim}
313 Director {
314 Name = the-name-of-the-director-dir
315 Password = "password-for-the-director-to-access-the-storage"
316 }
317 \end{bVerbatim}
318 authorizes the Director \bhighlight{the-name-of-the-director-dir}, knowing the storages password to access the storage daemon
319 \begin{bVerbatim}
320 Storage { # definition of myself
321 Name = bacula-storage-daemon-definition-sd
322 SDPort = 9103 # Director's port
323 WorkingDirectory = "/opt/bacula/working"
324 Pid Directory = "/opt/bacula/working"
325 Maximum Concurrent Jobs = 200
326 Heartbeat Interval = 10
327 }
328 \end{bVerbatim}
329 and therefore to use the devices defined on the Storage Daemon side for example
330 \begin{bVerbatim}
331 #
332 # This is a two drive autochanger definition
333 Autochanger {
334 Name = disk-autochanger
335 Device = drive1, drive2
336 # No changer command needed for virtual autochangers
337 Changer Command = ""
338 # No changer device needed either
339 Changer Device = "/dev/null"
340 }
341 #
342 # Drive 1 definition
343 Device {
344 Name = drive1
345 Archive Device = /bacula/da1
346 Media Type = da-mt
347 Drive Index = 0
348 Label Media = yes
349 Random Access = yes
350 AutomaticMount = yes
351 RemovableMedia = no
352 AlwaysOpen = no
353 Maximum Concurrent Jobs = 20
354 }
355 #
356 # Drive 2 is pretty much the same in this case
357 Device {
358 Name = drive2
359 #
360 # This is the same archive device as in drive1 definition
361 Archive Device = /bacula/da1
362 Media Type = da-mt
363 # Another drive, another drive index
364 Drive Index = 1
365 Label Media = yes
366 Random Access = yes
367 AutomaticMount = yes
368 RemovableMedia = no
369 AlwaysOpen = no
370 Maximum Concurrent Jobs = 20
371 }
372 \end{bVerbatim}
373
374 \subsubsection{\btool{bconsole}}
375 The following \texttt{bconsole.conf} content allows the Console to connect to the following Director:
376 \begin{bVerbatim}
377 Director {
378 Name = the-name-of-the-director-dir
379 DIRport = 9101
380 address = localhost
381 Password = "password-for-the-console-to-access-the-director"
382 }
383 \end{bVerbatim}
384
385 %%% TODO
386 %-- resources / directives
387 %-- config files / BMS
388 %-- reference manual (currently main manual - true reference manual to come)
389 %-- one configuration set per daemon
390
391 \subsection{BWeb Management Suite considerations}
392 The BWeb Management Suite (BMS) interface allows the administrator to manage the Bacula configuration through a Web interface. When using BMS for this purpose, the Bacula configuration files are split into pieces, all of them under the \texttt{conf.d} directory (\texttt{/opt/bacula/etc/conf.d}).
393
394 Figure~\vref{fig:bmsconfd} presents an example of a \texttt{conf.d} directory organization while the following is a tree representation of the same example.
395 \begin{bVerbatim}
396 conf.d/
397 |--- Console
398 | `-- v8-dir
399 | |--- bconsole.conf
400 | `-- Director
401 | `-- v8-dir.cfg
402 |--- Director
403 | `-- v8-dir
404 | |--- bacula-dir.conf
405 | |--- Catalog
406 | | `-- MyCatalog.cfg
407 | |--- Client
408 | | |--- v8-c1-fd.cfg
409 | | |--- v8-c2-fd.cfg
410 | | `-- v8-c3-fd.cfg
411 | |--- Console
412 | | `-- v8-mon.cfg
413 | |--- Director
414 | | `-- v8-dir.cfg
415 | |--- Fileset
416 | | |--- Catalog.cfg
417 | | |--- fs-postgres.cfg
418 | | `-- fs-tls.cfg
419 | |--- Job
420 | | |--- job-catalog.cfg
421 | | |--- job-postgres.cfg
422 | | |--- job-RestoreFiles.cfg
423 | | `-- job-tls.cfg
424 | |--- JobDefs
425 | | |--- defaultjob.cfg
426 | | `-- common.cfg
427 | |--- Messages
428 | | |--- Daemon.cfg
429 | | `-- Standard.cfg
430 | |--- Pool
431 | | |--- Dedup.cfg
432 | | |--- File.cfg
433 | | |--- common.cfg
434 | | `-- Scratch.cfg
435 | |--- Schedule
436 | | |--- FiveDays.cfg
437 | | |--- WeeklyCycleAfterBackup.cfg
438 | | `-- WeeklyCycle.cfg
439 | `-- Storage
440 | |--- Remote-Disk-Storage.cfg
441 | `-- File.cfg
442 |--- FileDaemon
443 | |--- v8-c1-fd
444 | | |--- bacula-fd.conf
445 | | |--- Director
446 | | | `-- v8-dir.cfg
447 | | |--- FileDaemon
448 | | | `-- v8-c1-fd.cfg
449 | | | `-- v8-mon.cfg
450 | | `-- Messages
451 | | `-- Standard.cfg
452 | |--- v8-c2-fd
453 | | |--- bacula-fd.conf
454 | | |--- Director
455 | | | |--- v8-dir.cfg
456 | | | `-- v8-mon.cfg
457 | | |--- FileDaemon
458 | | | `-- v8-c2-fd.cfg
459 | | `-- Messages
460 | | `-- Standard.cfg
461 | `-- v8-c3-fd
462 | |--- bacula-fd.conf
463 | |--- Director
464 | | `-- v8-dir.cfg
465 | |--- FileDaemon
466 | | `-- v8-c3-fd.cfg
467 | `-- Messages
468 | `-- Standard.cfg
469 `-- Storage
470 `-- v8-sd
471 |--- Autochanger
472 | `-- disk-autochanger.cfg
473 |--- bacula-sd.conf
474 |--- Device
475 | |--- drive1.cfg
476 | |--- drive2.cfg
477 | `-- File.cfg
478 |--- Director
479 | |--- v8-dir.cfg
480 | `-- v8-mon.cfg
481 |--- Messages
482 | `-- Standard.cfg
483 `-- Storage
484 `-- v8-sd.cfg
485 \end{bVerbatim}
486 \bimageH[\linewidth]{bee8-bms-confd}{\bdirectory{conf.d} typical graphical representation example}{fig:bmsconfd}
487 %% \begin{figure}
488 %% \includegraphics[width=\linewidth]{bee8-bms-confd}
489 %% \caption{\texttt{conf.d} directory typical graphical representation example}\label{fig:bmsconfd}
490 %% \end{figure}
491
492 \subsection{Good to Know}
493 Installing, understanding and managing Bacula configuration files is covered in-depth during the \textbf{Bacula Administration Course~I}. Even if this concept guide is here to help and give a quick overview of all concepts, attending this course, given in the US, Europe (Switzerland, Belgium, France) and in Japan is a strong recommendation.
494
495 \section{Encryption}
496 Bacula can encrypt the data it backs up (\textit{Data Encryption}), and independently of that, it can encrypt the network connections it uses (\textit{Transport Encryption}).
497
498 Both Data and Transport Encryption make use of industry-standard x509 Public Key Infrastructure, but the requirements differ a bit. In general, Data Encryption needs a minimum of infrastructure and configuration, while Transport Encryption may require much more effort of the Backup Administrator.
499
500 \subsection{Data Encryption}
501 Data Encryption happens on the client and needs a key pair in files stored on the client. Thus, the encrypted data may be inaccessible even to the backup administrators. If a \textit{Master Key} is desirable, so that data can be decrypted even if the client machine owner loses or has changed the keys, Bacula can be configured accordingly.
502
503 The client machine owner or administrator can be the only person responsible for the key files, which implies that additional tasks come into their realm of responsibility.
504
505 It is important to be aware that, while data itself is encrypted, metadata that is stored in the Catalog remains unencrypted -- file and path names, in particular, are easily visible to third parties with access to the network or the catalog database.
506
507 \subsection{Transport Encryption}
508 Transport Encryption, on the other hand, requires a full-blown, managed Public Key Infrastructure including a trusted and securely operated Certification Authority, secure deployment of keys and certificates, explicit configuration of trust relationships and a few lines of configuration in each Bacula configuration resource that refers to any Bacula component. Experience shows that configuring transport encryption for the first time is a challenge sometimes even to experienced Bacula administrators.\footnote{Fortunately, experience also shows that once over the first hurdle, things go considerably more smoothly!}
509
510 The overhead to operate and set up such an environment can be considerable and is, in general, not an area of expertise for backup and storage administrators. However, if a maximum of security is desired, it provides industry-standard protection against any sort of unauthorized data snooping and as such is particularly important when backups are done through insecure networks like the internet.
511
512 \subsection{Good to Know}
513 Data and Transport Encryption can be freely combined, but keep in mind that each layer of encryption adds CPU overhead and can thus decrease throughput and increase resource consumption.
514
515 Bacula can also use certificate-based authentication of its components, which is particularly useful if there are already certificates deployed for the involved computers.