4 \section*{Customizing the Configuration Files}
5 \label{_ChapterStart16}
6 \index[general]{Files!Customizing the Configuration }
7 \index[general]{Customizing the Configuration Files }
8 \addcontentsline{toc}{section}{Customizing the Configuration Files}
10 When each of the Bacula programs starts, it reads a configuration file
11 specified on the command line or the default {\bf bacula-dir.conf}, {\bf
12 bacula-fd.conf}, {\bf bacula-sd.conf}, or {\bf console.conf} for the Director
13 daemon, the File daemon, the Storage daemon, and the Console program
16 Each service (Director, Client, Storage, Console) has its own configuration
17 file containing a set of Resource definitions. These resources are very
18 similar from one service to another, but may contain different directives
19 (records) depending on the service. For example, in the Director's resource
20 file, the {\bf Director} resource defines the name of the Director, a number
21 of global Director parameters and his password. In the File daemon
22 configuration file, the {\bf Director} resource specifies which Directors are
23 permitted to use the File daemon.
25 Before running Bacula for the first time, you must customize the configuration
26 files for each daemon. Default configuration files will have been created by
27 the installation process, but you will need to modify them to correspond to
28 your system. An overall view of the resources can be seen in the following:
30 \addcontentsline{lof}{figure}{Bacula Objects}
31 \includegraphics{./bacula-objects.eps}
33 (thanks to Aristides Maniatis for the above graphic)
36 \subsection*{Resource Directive Format}
37 \index[general]{Resource Directive Format }
38 \index[general]{Format!Resource Directive }
39 \addcontentsline{toc}{subsection}{Resource Directive Format}
41 Although, you won't need to know the details of all the directives a basic
42 knowledge of Bacula resource directives is essential. Each directive contained
43 within the resource (within the braces) is composed of a keyword followed by
44 an equal sign (=) followed by one or more values. The keywords must be one of
45 the known Bacula resource record keywords, and it may be composed of upper or
46 lower case characters and spaces.
48 Each resource definition MUST contain a Name directive, and may optionally
49 contain a Description directive. The Name directive is used to
50 uniquely identify the resource. The Description directive is (will be) used
51 during display of the Resource to provide easier human recognition. For
58 Description = "Main Bacula Director"
59 WorkingDirectory = "$HOME/bacula/bin/working"
64 Defines the Director resource with the name "MyDir" and a working directory
65 \$HOME/bacula/bin/working. In general, if you want spaces in a name to the
66 right of the first equal sign (=), you must enclose that name within double
67 quotes. Otherwise quotes are not generally necessary because once defined,
68 quoted strings and unquoted strings are all equal.
71 \subsubsection*{Comments}
72 \index[general]{Comments}
73 \addcontentsline{toc}{subsubsection}{Comments}
75 When reading the configuration file, blank lines are ignored and everything
76 after a hash sign (\#) until the end of the line is taken to be a comment. A
77 semicolon (;) is a logical end of line, and anything after the semicolon is
78 considered as the next statement. If a statement appears on a line by itself,
79 a semicolon is not necessary to terminate it, so generally in the examples in
80 this manual, you will not see many semicolons.
83 \subsubsection*{Upper and Lower Case and Spaces}
84 \index[general]{Spaces!Upper/Lower Case}
85 \index[general]{Upper and Lower Case and Spaces}
86 \addcontentsline{toc}{subsubsection}{Upper and Lower Case and Spaces}
88 Case (upper/lower) and spaces are totally ignored in the resource directive
89 keywords (the part before the equal sign).
91 Within the keyword (i.e. before the equal sign), spaces are not significant.
92 Thus the keywords: {\bf name}, {\bf Name}, and {\bf N a m e} are all
95 Spaces after the equal sign and before the first character of the value are
98 In general, spaces within a value are significant (not ignored), and if the
99 value is a name, you must enclose the name in double quotes for the spaces to
100 be accepted. Names may contain up to 127 characters. Currently, a name may
101 contain any ASCII character. Within a quoted string, any character following a
102 backslash (\textbackslash{}) is taken as itself (handy for inserting
103 blackslashes and double quotes (").
105 Please note, however, that Bacula resource names as well as certain other
106 names (e.g. Volume names) must contain only letters (including ISO accented
107 letters), numbers, and a few special characters (space, underscore, ...).
108 All other characters and punctuation are illegal.
111 \subsubsection*{Including other Configuration Files}
112 \index[general]{Including other Configuration Files }
113 \index[general]{Files!Including other Configuration }
114 \index[general]{Using @ to include other files}
115 \index[general]{@{\bf filename}}
116 \addcontentsline{toc}{subsubsection}{Including other Configuration Files}
118 If you wish to break your configuration file into smaller pieces, you can do
119 so by including other files using the syntax @{\bf filename} where {\bf
120 filename} is the full path and filename of another file. The @filename
121 specification can be given anywhere a primitive token would appear.
124 \subsubsection*{Recognized Primitive Data Types}
125 \index[general]{Types!Recognized Primitive Data }
126 \index[general]{Recognized Primitive Data Types }
127 \addcontentsline{toc}{subsubsection}{Recognized Primitive Data Types}
129 When parsing the resource directives, Bacula classifies the data according to
130 the types listed below. The first time you read this, it may appear a bit
131 overwhelming, but in reality, it is all pretty logical and straightforward.
137 A keyword or name consisting of alphanumeric characters, including the
138 hyphen, underscore, and dollar characters. The first character of a {\bf
139 name} must be a letter. A name has a maximum length currently set to 127
140 bytes. Typically keywords appear on the left side of an equal (i.e. they are
141 Bacula keywords -- i.e. Resource names or directive names). Keywords may not
145 \index[fd]{name-string}
146 A name-string is similar to a name, except that the name may be quoted and
147 can thus contain additional characters including spaces. Name strings are
148 limited to 127 characters in length. Name strings are typically used on the
149 right side of an equal (i.e. they are values to be associated with a keyword.
154 A quoted string containing virtually any character including spaces, or a
155 non-quoted string. A string may be of any length. Strings are typically
156 values that correspond to filenames, directories, or system command names. A
157 backslash (\textbackslash{}) turns the next character into itself, so to
158 include a double quote in a string, you precede the double quote with a
159 backslash. Likewise to include a backslash.
162 \index[dir]{directory}
163 A directory is either a quoted or non-quoted string. A directory will be
164 passed to your standard shell for expansion when it is scanned. Thus
165 constructs such as {\bf \$HOME} are interpreted to be their correct values.
168 \index[dir]{password}
169 This is a Bacula password and it is stored internally in MD5 hashed format.
173 A 32 bit integer value. It may be positive or negative.
175 \item [positive integer]
176 \index[dir]{positive integer }
177 A 32 bit positive integer value.
180 \index[dir]{long integer}
181 A 64 bit integer value. Typically these are values such as bytes that can
182 exceed 4 billion and thus require a 64 bit value.
185 \index[dir]{yes or no }
186 Either a {\bf yes} or a {\bf no}.
191 A size specified as bytes. Typically, this is a floating point scientific
192 input format followed by an optional modifier. The floating point input is
193 stored as a 64 bit integer value. If a modifier is present, it must
194 immediately follow the value with no intervening spaces. The following
195 modifiers are permitted:
205 1,048,576 (megabytes)
208 1,000,000 (megabytes)
211 1,073,741,824 (gigabytes)
214 1,000,000,000 (gigabytes)
220 A time or duration specified in seconds. The time is stored internally as
221 a 64 bit integer value, but it is specified in two parts: a number part and
222 a modifier part. The number can be an integer or a floating point number.
223 If it is entered in floating point notation, it will be rounded to the
224 nearest integer. The modifier is mandatory and follows the number part,
225 either with or without intervening spaces. The following modifiers are
244 days (3600*24 seconds)
248 weeks (3600*24*7 seconds)
252 months (3600*24*30 seconds)
255 \index[dir]{quarters }
256 quarters (3600*24*91 seconds)
260 years (3600*24*365 seconds)
263 Any abbreviation of these modifiers is also permitted (i.e. {\bf seconds}
264 may be specified as {\bf sec} or {\bf s}. A specification of {\bf m} will
267 The specification of a time may have as many number/modifier parts as you
272 1 week 2 days 3 hours 10 mins
273 1 month 2 days 30 sec
278 are valid date specifications.
283 \subsection*{Resource Types}
284 \index[general]{Types!Resource }
285 \index[general]{Resource Types }
286 \addcontentsline{toc}{subsection}{Resource Types}
288 The following table lists all current Bacula resource types. It shows what
289 resources must be defined for each service (daemon). The default configuration
290 files will already contain at least one example of each permitted resource, so
291 you need not worry about creating all these kinds of resources from scratch.
293 \addcontentsline{lot}{table}{Resource Types}
294 \begin{longtable}{|l|l|l|l|l|}
296 \multicolumn{1}{|c| }{\bf Resource } & \multicolumn{1}{c| }{\bf Director } &
297 \multicolumn{1}{c| }{\bf Client } & \multicolumn{1}{c| }{\bf Storage } &
298 \multicolumn{1}{c| }{\bf Console } \\
300 {Autochanger } & {No } & {No } & {Yes } & {No } \\
302 {Catalog } & {Yes } & {No } & {No } & {No } \\
304 {Client } & {Yes } & {Yes } & {No } & {No } \\
306 {Console } & {Yes } & {No } & {No } & {Yes } \\
308 {Device } & {No } & {No } & {Yes } & {No } \\
310 {Director } & {Yes } & {Yes } & {Yes } & {Yes } \\
312 {FileSet } & {Yes } & {No } & {No } & {No } \\
314 {Job } & {Yes } & {No } & {No } & {No } \\
316 {JobDefs } & {Yes } & {No } & {No } & {No } \\
318 {Message } & {Yes } & {Yes } & {Yes } & {No } \\
320 {Pool } & {Yes } & {No } & {No } & {No } \\
322 {Schedule } & {Yes } & {No } & {No } & {No } \\
324 {Storage } & {Yes } & {No } & {Yes } & {No }
329 \subsection*{Names, Passwords and Authorization}
331 \index[general]{Authorization!Names Passwords and }
332 \index[general]{Names, Passwords and Authorization }
333 \index[general]{Passwords}
334 \addcontentsline{toc}{subsection}{Names, Passwords and Authorization}
336 In order for one daemon to contact another daemon, it must authorize itself
337 with a password. In most cases, the password corresponds to a particular name,
338 so both the name and the password must match to be authorized.
340 The default configuration files are automatically defined for correct
341 authorization with random passwords. If you add to or modify these files, you
342 will need to take care to keep them consistent.
344 Here is sort of a picture of what names/passwords in which files/Resources
347 \includegraphics{./Conf-Diagram.eps}
349 In the left column, you will find the Director, Storage, and Client resources,
350 with their names and passwords -- these are all in {\bf bacula-dir.conf}. In
351 the right column are where the corresponding values should be found in the
352 Console, Storage daemon (SD), and File daemon (FD) configuration files.
354 Please note that the Address, {\bf fd-sd}, that appears in the Storage
355 resource of the Director, preceded with and asterisk in the above example, is
356 passed to the File daemon in symbolic form. The File daemon then resolves it
357 to an IP address. For this reason, you must use either an IP address or a
358 fully qualified name. A name such as {\bf localhost}, not being a fully
359 qualified name, will resolve in the File daemon to the localhost of the File
360 daemon, which is most likely not what is desired. The password used for the
361 File daemon to authorize with the Storage daemon is a temporary password
362 unique to each Job created by the daemons and is not specified in any .conf
365 \subsection*{Detailed Information for each Daemon}
366 \index[general]{Detailed Information for each Daemon }
367 \index[general]{Daemon!Detailed Information for each }
368 \addcontentsline{toc}{subsection}{Detailed Information for each Daemon}
370 The details of each Resource and the directives permitted therein are
371 described in the following chapters.
373 The following configuration files must be defined:
377 \ilink{Console}{_ChapterStart36} -- to define the resources for
378 the Console program (user interface to the Director). It defines which
379 Directors are available so that you may interact with them.
381 \ilink{Director}{_ChapterStart40} -- to define the resources
382 necessary for the Director. You define all the Clients and Storage daemons
383 that you use in this configuration file.
385 \ilink{Client}{_ChapterStart25} -- to define the resources for
386 each client to be backed up. That is, you will have a separate Client
387 resource file on each machine that runs a File daemon.
389 \ilink{Storage}{_ChapterStart31} -- to define the resources to
390 be used by each Storage daemon. Normally, you will have a single Storage
391 daemon that controls your tape drive or tape drives. However, if you have
392 tape drives on several machines, you will have at least one Storage daemon