4 \chapter{Configuring the Director}
5 \label{DirectorChapter}
6 \index[general]{Director!Configuring the}
7 \index[general]{Configuring the Director}
9 Of all the configuration files needed to run {\bf Bacula}, the Director's is
10 the most complicated, and the one that you will need to modify the most often
11 as you add clients or modify the FileSets.
13 For a general discussion of configuration files and resources including the
14 data types recognized by {\bf Bacula}. Please see the
15 \ilink{Configuration}{ConfigureChapter} chapter of this manual.
17 \section{Director Resource Types}
18 \index[general]{Types!Director Resource}
19 \index[general]{Director Resource Types}
21 Director resource type may be one of the following:
23 Job, JobDefs, Client, Storage, Catalog, Schedule, FileSet, Pool, Director, or
24 Messages. We present them here in the most logical order for defining them:
26 Note, everything revolves around a job and is tied to a job in one
31 \ilink{Director}{DirectorResource4} -- to define the Director's
32 name and its access password used for authenticating the Console program.
33 Only a single Director resource definition may appear in the Director's
34 configuration file. If you have either {\bf /dev/random} or {\bf bc} on your
35 machine, Bacula will generate a random password during the configuration
36 process, otherwise it will be left blank.
38 \ilink{Job}{JobResource} -- to define the backup/restore Jobs
39 and to tie together the Client, FileSet and Schedule resources to be used
40 for each Job. Normally, you will Jobs of different names corresponding
41 to each client (i.e. one Job per client, but a different one with a different name
44 \ilink{JobDefs}{JobDefsResource} -- optional resource for
45 providing defaults for Job resources.
47 \ilink{Schedule}{ScheduleResource} -- to define when a Job is to
48 be automatically run by {\bf Bacula's} internal scheduler. You
49 may have any number of Schedules, but each job will reference only
52 \ilink{FileSet}{FileSetResource} -- to define the set of files
53 to be backed up for each Client. You may have any number of
54 FileSets but each Job will reference only one.
56 \ilink{Client}{ClientResource2} -- to define what Client is to be
57 backed up. You will generally have multiple Client definitions. Each
58 Job will reference only a single client.
60 \ilink{Storage}{StorageResource2} -- to define on what physical
61 device the Volumes should be mounted. You may have one or
62 more Storage definitions.
64 \ilink{Pool}{PoolResource} -- to define the pool of Volumes
65 that can be used for a particular Job. Most people use a
66 single default Pool. However, if you have a large number
67 of clients or volumes, you may want to have multiple Pools.
68 Pools allow you to restrict a Job (or a Client) to use
69 only a particular set of Volumes.
71 \ilink{Catalog}{CatalogResource} -- to define in what database to
72 keep the list of files and the Volume names where they are backed up.
73 Most people only use a single catalog. However, if you want to
74 scale the Director to many clients, multiple catalogs can be helpful.
75 Multiple catalogs require a bit more management because in general
76 you must know what catalog contains what data. Currently, all
77 Pools are defined in each catalog. This restriction will be removed
80 \ilink{Messages}{MessagesChapter} -- to define where error and
81 information messages are to be sent or logged. You may define
82 multiple different message resources and hence direct particular
83 classes of messages to different users or locations (files, ...).
86 \section{The Director Resource}
87 \label{DirectorResource4}
88 \index[general]{Director Resource}
89 \index[general]{Resource!Director}
91 The Director resource defines the attributes of the Directors running on the
92 network. In the current implementation, there is only a single Director
93 resource, but the final design will contain multiple Directors to maintain
94 index and media database redundancy.
100 Start of the Director resource. One and only one director resource must be
103 \item [Name = \lt{}name\gt{}]
105 \index[dir]{Directive!Name}
106 The director name used by the system administrator. This directive is
109 \item [Description = \lt{}text\gt{}]
110 \index[dir]{Description}
111 \index[dir]{Directive!Description}
112 The text field contains a description of the Director that will be displayed
113 in the graphical user interface. This directive is optional.
115 \item [Password = \lt{}UA-password\gt{}]
116 \index[dir]{Password}
117 \index[dir]{Directive!Password}
118 Specifies the password that must be supplied for the default Bacula
119 Console to be authorized. The same password must appear in the {\bf
120 Director} resource of the Console configuration file. For added
121 security, the password is never passed across the network but instead a
122 challenge response hash code created with the password. This directive
123 is required. If you have either {\bf /dev/random} or {\bf bc} on your
124 machine, Bacula will generate a random password during the configuration
125 process, otherwise it will be left blank and you must manually supply
128 The password is plain text. It is not generated through any special
129 process but as noted above, it is better to use random text for
132 \item [Messages = \lt{}Messages-resource-name\gt{}]
133 \index[dir]{Messages}
134 \index[dir]{Directive!Messages}
135 The messages resource specifies where to deliver Director messages that are
136 not associated with a specific Job. Most messages are specific to a job and
137 will be directed to the Messages resource specified by the job. However,
138 there are a few messages that can occur when no job is running. This
139 directive is required.
141 \item [Working Directory = \lt{}Directory\gt{}]
142 \index[dir]{Working Directory}
143 \index[dir]{Directive!Working Directory}
144 This directive is mandatory and specifies a directory in which the Director
145 may put its status files. This directory should be used only by Bacula but
146 may be shared by other Bacula daemons. However, please note, if this
147 directory is shared with other Bacula daemons (the File daemon and Storage
148 daemon), you must ensure that the {\bf Name} given to each daemon is
149 unique so that the temporary filenames used do not collide. By default
150 the Bacula configure process creates unique daemon names by postfixing them
151 with -dir, -fd, and -sd. Standard shell expansion of the {\bf
152 Directory} is done when the configuration file is read so that values such
153 as {\bf \$HOME} will be properly expanded. This directive is required.
154 The working directory specified must already exist and be
155 readable and writable by the Bacula daemon referencing it.
157 If you have specified a Director user and/or a Director group on your
158 ./configure line with {\bf {-}{-}with-dir-user} and/or
159 {\bf {-}{-}with-dir-group} the Working Directory owner and group will
160 be set to those values.
162 \item [Pid Directory = \lt{}Directory\gt{}]
163 \index[dir]{Pid Directory}
164 \index[dir]{Directive!Pid Directory}
165 This directive is mandatory and specifies a directory in which the Director
166 may put its process Id file. The process Id file is used to shutdown
167 Bacula and to prevent multiple copies of Bacula from running simultaneously.
168 Standard shell expansion of the {\bf Directory} is done when the
169 configuration file is read so that values such as {\bf \$HOME} will be
172 The PID directory specified must already exist and be
173 readable and writable by the Bacula daemon referencing it
175 Typically on Linux systems, you will set this to: {\bf /var/run}. If you are
176 not installing Bacula in the system directories, you can use the {\bf Working
177 Directory} as defined above. This directive is required.
179 \item [Scripts Directory = \lt{}Directory\gt{}]
180 \index[dir]{Scripts Directory}
181 \index[dir]{Directive!Scripts Directory}
182 This directive is optional and, if defined, specifies a directory in
183 which the Director will look for the Python startup script {\bf
184 DirStartup.py}. This directory may be shared by other Bacula daemons.
185 Standard shell expansion of the directory is done when the configuration
186 file is read so that values such as {\bf \$HOME} will be properly
189 \item [QueryFile = \lt{}Path\gt{}]
190 \index[dir]{QueryFile}
191 \index[dir]{Directive!QueryFile}
192 This directive is mandatory and specifies a directory and file in which
193 the Director can find the canned SQL statements for the {\bf Query}
194 command of the Console. Standard shell expansion of the {\bf Path} is
195 done when the configuration file is read so that values such as {\bf
196 \$HOME} will be properly expanded. This directive is required.
198 \item [Heartbeat Interval = \lt{}time-interval\gt{}]
199 \index[dir]{Heartbeat Interval}
200 \index[dir]{Directive!Heartbeat}
201 This directive is optional and if specified will cause the Director to
202 set a keepalive interval (heartbeat) in seconds on each of the sockets
203 it opens for the Client resource. This value will override any
204 specified at the Director level. It is implemented only on systems
205 (Linux, ...) that provide the {\bf setsockopt} TCP\_KEEPIDLE function.
206 The default value is zero, which means no change is made to the socket.
209 \label{DirMaxConJobs}
210 \item [Maximum Concurrent Jobs = \lt{}number\gt{}]
211 \index[dir]{Maximum Concurrent Jobs}
212 \index[dir]{Directive!Maximum Concurrent Jobs}
213 \index[general]{Simultaneous Jobs}
214 \index[general]{Concurrent Jobs}
215 where \lt{}number\gt{} is the maximum number of total Director Jobs that
216 should run concurrently. The default is set to 1, but you may set it to a
219 The Volume format becomes more complicated with
220 multiple simultaneous jobs, consequently, restores may take longer if
221 Bacula must sort through interleaved volume blocks from multiple simultaneous
222 jobs. This can be avoided by having each simultaneous job write to
223 a different volume or by using data spooling, which will first spool the data
224 to disk simultaneously, then write one spool file at a time to the volume
225 thus avoiding excessive interleaving of the different job blocks.
227 \item [FD Connect Timeout = \lt{}time\gt{}]
228 \index[dir]{FD Connect Timeout}
229 \index[dir]{Directive!FD Connect Timeout}
230 where {\bf time} is the time that the Director should continue
231 attempting to contact the File daemon to start a job, and after which
232 the Director will cancel the job. The default is 30 minutes.
234 \item [SD Connect Timeout = \lt{}time\gt{}]
235 \index[dir]{SD Connect Timeout}
236 \index[dir]{Directive!SD Connect Timeout}
237 where {\bf time} is the time that the Director should continue
238 attempting to contact the Storage daemon to start a job, and after which
239 the Director will cancel the job. The default is 30 minutes.
241 \item [DirAddresses = \lt{}IP-address-specification\gt{}]
242 \index[dir]{DirAddresses}
244 \index[general]{Address}
245 \index[dir]{Directive!DirAddresses}
246 Specify the ports and addresses on which the Director daemon will listen
247 for Bacula Console connections. Probably the simplest way to explain
248 this is to show an example:
253 ip = { addr = 1.2.3.4; port = 1205;}
255 addr = 1.2.3.4; port = http;}
264 ip = { addr = 1.2.3.4 }
265 ip = { addr = 201:220:222::2 }
267 addr = bluedot.thun.net
273 where ip, ip4, ip6, addr, and port are all keywords. Note, that the address
274 can be specified as either a dotted quadruple, or IPv6 colon notation, or as
275 a symbolic name (only in the ip specification). Also, port can be specified
276 as a number or as the mnemonic value from the /etc/services file. If a port
277 is not specified, the default will be used. If an ip section is specified,
278 the resolution can be made either by IPv4 or IPv6. If ip4 is specified, then
279 only IPv4 resolutions will be permitted, and likewise with ip6.
281 Please note that if you use the DirAddresses directive, you must
282 not use either a DirPort or a DirAddress directive in the same
285 \item [DirPort = \lt{}port-number\gt{}]
287 \index[dir]{Directive!DirPort}
288 Specify the port (a positive integer) on which the Director daemon will
289 listen for Bacula Console connections. This same port number must be
290 specified in the Director resource of the Console configuration file. The
291 default is 9101, so normally this directive need not be specified. This
292 directive should not be used if you specify DirAddresses (N.B plural)
295 \item [DirAddress = \lt{}IP-Address\gt{}]
296 \index[dir]{DirAddress}
297 \index[dir]{Directive!DirAddress}
298 This directive is optional, but if it is specified, it will cause the
299 Director server (for the Console program) to bind to the specified {\bf
300 IP-Address}, which is either a domain name or an IP address specified as a
301 dotted quadruple in string or quoted string format. If this directive is
302 not specified, the Director will bind to any available address (the
303 default). Note, unlike the DirAddresses specification noted above, this
304 directive only permits a single address to be specified. This directive
305 should not be used if you specify a DirAddresses (N.B. plural) directive.
307 \item [DirSourceAddress = \lt{}IP-Address\gt{}]
308 \index[fd]{DirSourceAddress}
309 \index[fd]{Directive!DirSourceAddress}
310 This record is optional, and if it is specified, it will cause the Director
311 server (when initiating connections to a storage or file daemon) to source
312 its connections from the specified address. Only a single IP address may be
313 specified. If this record is not specified, the Director server will source
314 its outgoing connections according to the system routing table (the default).
316 \item[Statistics Retention = \lt{}time\gt{}]
317 \index[dir]{StatisticsRetention}
318 \index[dir]{Directive!StatisticsRetention}
319 \label{PruneStatistics}
321 The \texttt{Statistics Retention} directive defines the length of time that
322 Bacula will keep statistics job records in the Catalog database after the
323 Job End time. (In \texttt{JobHistory} table) When this time period expires,
324 and if user runs \texttt{prune stats} command, Bacula will prune (remove)
325 Job records that are older than the specified period.
327 Theses statistics records aren't use for restore purpose, but mainly for
328 capacity planning, billings, etc. See \ilink{Statistics chapter} for
329 additional information.
331 See the \ilink{ Configuration chapter}{Time} of this manual for additional
332 details of time specification.
334 The default is 5 years.
336 \item[VerId = \lt{}string\gt{}]
337 \index[dir]{Directive!VerId}
338 where \lt{}string\gt{} is an identifier which can be used for support purpose.
339 This string is displayed using the \texttt{version} command.
341 \item[MaximumConsoleConnections = \lt{}number\gt{}]
342 \index[dir]{MaximumConsoleConnections}
343 \index[dir]{Directive!MaximumConsoleConnections}
345 where \lt{}number\gt{} is the maximum number of Console Connections that
346 could run concurrently. The default is set to 20, but you may set it to a
351 The following is an example of a valid Director resource definition:
357 WorkingDirectory = "$HOME/bacula/bin/working"
358 Password = UA_password
359 PidDirectory = "$HOME/bacula/bin/working"
360 QueryFile = "$HOME/bacula/bin/query.sql"
366 \section{The Job Resource}
368 \index[general]{Resource!Job}
369 \index[general]{Job Resource}
371 The Job resource defines a Job (Backup, Restore, ...) that Bacula must
372 perform. Each Job resource definition contains the name of a Client and
373 a FileSet to backup, the Schedule for the Job, where the data
374 are to be stored, and what media Pool can be used. In effect, each Job
375 resource must specify What, Where, How, and When or FileSet, Storage,
376 Backup/Restore/Level, and Schedule respectively. Note, the FileSet must
377 be specified for a restore job for historical reasons, but it is no longer used.
379 Only a single type ({\bf Backup}, {\bf Restore}, ...) can be specified for any
380 job. If you want to backup multiple FileSets on the same Client or multiple
381 Clients, you must define a Job for each one.
383 Note, you define only a single Job to do the Full, Differential, and
384 Incremental backups since the different backup levels are tied together by
385 a unique Job name. Normally, you will have only one Job per Client, but
386 if a client has a really huge number of files (more than several million),
387 you might want to split it into to Jobs each with a different FileSet
388 covering only part of the total files.
390 Multiple Storage daemons are not currently supported for Jobs, so if
391 you do want to use multiple storage daemons, you will need to create
392 a different Job and ensure that for each Job that the combination of
393 Client and FileSet are unique. The Client and FileSet are what Bacula
394 uses to restore a client, so if there are multiple Jobs with the same
395 Client and FileSet or multiple Storage daemons that are used, the
396 restore will not work. This problem can be resolved by defining multiple
397 FileSet definitions (the names must be different, but the contents of
398 the FileSets may be the same).
405 \index[dir]{Directive!Job}
406 Start of the Job resource. At least one Job resource is required.
408 \item [Name = \lt{}name\gt{}]
410 \index[dir]{Directive!Name}
411 The Job name. This name can be specified on the {\bf Run} command in the
412 console program to start a job. If the name contains spaces, it must be
413 specified between quotes. It is generally a good idea to give your job the
414 same name as the Client that it will backup. This permits easy
415 identification of jobs.
417 When the job actually runs, the unique Job Name will consist of the name you
418 specify here followed by the date and time the job was scheduled for
419 execution. This directive is required.
421 \item [Enabled = \lt{}yes\vb{}no\gt{}]
423 \index[dir]{Directive!Enable}
424 This directive allows you to enable or disable automatic execution
425 via the scheduler of a Job.
427 \item [Type = \lt{}job-type\gt{}]
429 \index[dir]{Directive!Type}
430 The {\bf Type} directive specifies the Job type, which may be one of the
431 following: {\bf Backup}, {\bf Restore}, {\bf Verify}, or {\bf Admin}. This
432 directive is required. Within a particular Job Type, there are also Levels
433 as discussed in the next item.
439 Run a backup Job. Normally you will have at least one Backup job for each
440 client you want to save. Normally, unless you turn off cataloging, most all
441 the important statistics and data concerning files backed up will be placed
446 Run a restore Job. Normally, you will specify only one Restore job
447 which acts as a sort of prototype that you will modify using the console
448 program in order to perform restores. Although certain basic
449 information from a Restore job is saved in the catalog, it is very
450 minimal compared to the information stored for a Backup job -- for
451 example, no File database entries are generated since no Files are
454 {\bf Restore} jobs cannot be
455 automatically started by the scheduler as is the case for Backup, Verify
456 and Admin jobs. To restore files, you must use the {\bf restore} command
462 Run a verify Job. In general, {\bf verify} jobs permit you to compare the
463 contents of the catalog to the file system, or to what was backed up. In
464 addition, to verifying that a tape that was written can be read, you can
465 also use {\bf verify} as a sort of tripwire intrusion detection.
469 Run an admin Job. An {\bf Admin} job can be used to periodically run catalog
470 pruning, if you do not want to do it at the end of each {\bf Backup} Job.
471 Although an Admin job is recorded in the catalog, very little data is saved.
476 \item [Level = \lt{}job-level\gt{}]
478 \index[dir]{Directive!Level}
479 The Level directive specifies the default Job level to be run. Each
480 different Job Type (Backup, Restore, ...) has a different set of Levels
481 that can be specified. The Level is normally overridden by a different
482 value that is specified in the {\bf Schedule} resource. This directive
483 is not required, but must be specified either by a {\bf Level} directive
484 or as an override specified in the {\bf Schedule} resource.
486 For a {\bf Backup} Job, the Level may be one of the following:
492 When the Level is set to Full all files in the FileSet whether or not
493 they have changed will be backed up.
496 \index[dir]{Incremental}
497 When the Level is set to Incremental all files specified in the FileSet
498 that have changed since the last successful backup of the the same Job
499 using the same FileSet and Client, will be backed up. If the Director
500 cannot find a previous valid Full backup then the job will be upgraded
501 into a Full backup. When the Director looks for a valid backup record
502 in the catalog database, it looks for a previous Job with:
505 \item The same Job name.
506 \item The same Client name.
507 \item The same FileSet (any change to the definition of the FileSet such as
508 adding or deleting a file in the Include or Exclude sections constitutes a
510 \item The Job was a Full, Differential, or Incremental backup.
511 \item The Job terminated normally (i.e. did not fail or was not canceled).
512 \item The Job started no longer ago than {\bf Max Full Interval}.
515 If all the above conditions do not hold, the Director will upgrade the
516 Incremental to a Full save. Otherwise, the Incremental backup will be
517 performed as requested.
519 The File daemon (Client) decides which files to backup for an
520 Incremental backup by comparing start time of the prior Job (Full,
521 Differential, or Incremental) against the time each file was last
522 "modified" (st\_mtime) and the time its attributes were last
523 "changed"(st\_ctime). If the file was modified or its attributes
524 changed on or after this start time, it will then be backed up.
526 Some virus scanning software may change st\_ctime while
527 doing the scan. For example, if the virus scanning program attempts to
528 reset the access time (st\_atime), which Bacula does not use, it will
529 cause st\_ctime to change and hence Bacula will backup the file during
530 an Incremental or Differential backup. In the case of Sophos virus
531 scanning, you can prevent it from resetting the access time (st\_atime)
532 and hence changing st\_ctime by using the {\bf \verb:--:no-reset-atime}
533 option. For other software, please see their manual.
535 When Bacula does an Incremental backup, all modified files that are
536 still on the system are backed up. However, any file that has been
537 deleted since the last Full backup remains in the Bacula catalog,
538 which means that if between a Full save and the time you do a
539 restore, some files are deleted, those deleted files will also be
540 restored. The deleted files will no longer appear in the catalog
541 after doing another Full save.
543 In addition, if you move a directory rather than copy it, the files in
544 it do not have their modification time (st\_mtime) or their attribute
545 change time (st\_ctime) changed. As a consequence, those files will
546 probably not be backed up by an Incremental or Differential backup which
547 depend solely on these time stamps. If you move a directory, and wish
548 it to be properly backed up, it is generally preferable to copy it, then
551 However, to manage deleted files or directories changes in the
552 catalog during an Incremental backup you can use \texttt{accurate}
553 mode. This is quite memory consuming process. See \ilink{Accurate
554 mode}{accuratemode} for more details.
557 \index[dir]{Differential}
558 When the Level is set to Differential
559 all files specified in the FileSet that have changed since the last
560 successful Full backup of the same Job will be backed up.
561 If the Director cannot find a
562 valid previous Full backup for the same Job, FileSet, and Client,
563 backup, then the Differential job will be upgraded into a Full backup.
564 When the Director looks for a valid Full backup record in the catalog
565 database, it looks for a previous Job with:
568 \item The same Job name.
569 \item The same Client name.
570 \item The same FileSet (any change to the definition of the FileSet such as
571 adding or deleting a file in the Include or Exclude sections constitutes a
573 \item The Job was a FULL backup.
574 \item The Job terminated normally (i.e. did not fail or was not canceled).
575 \item The Job started no longer ago than {\bf Max Full Interval}.
578 If all the above conditions do not hold, the Director will upgrade the
579 Differential to a Full save. Otherwise, the Differential backup will be
580 performed as requested.
582 The File daemon (Client) decides which files to backup for a
583 differential backup by comparing the start time of the prior Full backup
584 Job against the time each file was last "modified" (st\_mtime) and the
585 time its attributes were last "changed" (st\_ctime). If the file was
586 modified or its attributes were changed on or after this start time, it
587 will then be backed up. The start time used is displayed after the {\bf
588 Since} on the Job report. In rare cases, using the start time of the
589 prior backup may cause some files to be backed up twice, but it ensures
590 that no change is missed. As with the Incremental option, you should
591 ensure that the clocks on your server and client are synchronized or as
592 close as possible to avoid the possibility of a file being skipped.
593 Note, on versions 1.33 or greater Bacula automatically makes the
594 necessary adjustments to the time between the server and the client so
595 that the times Bacula uses are synchronized.
597 When Bacula does a Differential backup, all modified files that are
598 still on the system are backed up. However, any file that has been
599 deleted since the last Full backup remains in the Bacula catalog, which
600 means that if between a Full save and the time you do a restore, some
601 files are deleted, those deleted files will also be restored. The
602 deleted files will no longer appear in the catalog after doing another
603 Full save. However, to remove deleted files from the catalog during a
604 Differential backup is quite a time consuming process and not currently
605 implemented in Bacula. It is, however, a planned future feature.
607 As noted above, if you move a directory rather than copy it, the
608 files in it do not have their modification time (st\_mtime) or
609 their attribute change time (st\_ctime) changed. As a
610 consequence, those files will probably not be backed up by an
611 Incremental or Differential backup which depend solely on these
612 time stamps. If you move a directory, and wish it to be
613 properly backed up, it is generally preferable to copy it, then
614 delete the original. Alternatively, you can move the directory, then
615 use the {\bf touch} program to update the timestamps.
617 %% TODO: merge this with incremental
618 However, to manage deleted files or directories changes in the
619 catalog during an Differential backup you can use \texttt{accurate}
620 mode. This is quite memory consuming process. See \ilink{Accurate
621 mode}{accuratemode} for more details.
623 Every once and a while, someone asks why we need Differential
624 backups as long as Incremental backups pickup all changed files.
625 There are possibly many answers to this question, but the one
626 that is the most important for me is that a Differential backup
628 all the Incremental and Differential backups since the last Full backup
629 into a single Differential backup. This has two effects: 1. It gives
630 some redundancy since the old backups could be used if the merged backup
631 cannot be read. 2. More importantly, it reduces the number of Volumes
632 that are needed to do a restore effectively eliminating the need to read
633 all the volumes on which the preceding Incremental and Differential
634 backups since the last Full are done.
638 For a {\bf Restore} Job, no level needs to be specified.
640 For a {\bf Verify} Job, the Level may be one of the following:
645 \index[dir]{InitCatalog}
646 does a scan of the specified {\bf FileSet} and stores the file
647 attributes in the Catalog database. Since no file data is saved, you
648 might ask why you would want to do this. It turns out to be a very
649 simple and easy way to have a {\bf Tripwire} like feature using {\bf
650 Bacula}. In other words, it allows you to save the state of a set of
651 files defined by the {\bf FileSet} and later check to see if those files
652 have been modified or deleted and if any new files have been added.
653 This can be used to detect system intrusion. Typically you would
654 specify a {\bf FileSet} that contains the set of system files that
655 should not change (e.g. /sbin, /boot, /lib, /bin, ...). Normally, you
656 run the {\bf InitCatalog} level verify one time when your system is
657 first setup, and then once again after each modification (upgrade) to
658 your system. Thereafter, when your want to check the state of your
659 system files, you use a {\bf Verify} {\bf level = Catalog}. This
660 compares the results of your {\bf InitCatalog} with the current state of
665 Compares the current state of the files against the state previously
666 saved during an {\bf InitCatalog}. Any discrepancies are reported. The
667 items reported are determined by the {\bf verify} options specified on
668 the {\bf Include} directive in the specified {\bf FileSet} (see the {\bf
669 FileSet} resource below for more details). Typically this command will
670 be run once a day (or night) to check for any changes to your system
673 Please note! If you run two Verify Catalog jobs on the same client at
674 the same time, the results will certainly be incorrect. This is because
675 Verify Catalog modifies the Catalog database while running in order to
678 \item [VolumeToCatalog]
679 \index[dir]{VolumeToCatalog}
680 This level causes Bacula to read the file attribute data written to the
681 Volume from the last backup Job for the job specified on the {\bf VerifyJob}
682 directive. The file attribute data are compared to the
683 values saved in the Catalog database and any differences are reported.
684 This is similar to the {\bf DiskToCatalog} level except that instead of
685 comparing the disk file attributes to the catalog database, the
686 attribute data written to the Volume is read and compared to the catalog
687 database. Although the attribute data including the signatures (MD5 or
688 SHA1) are compared, the actual file data is not compared (it is not in
691 Please note! If you run two Verify VolumeToCatalog jobs on the same
692 client at the same time, the results will certainly be incorrect. This
693 is because the Verify VolumeToCatalog modifies the Catalog database
696 \item [DiskToCatalog]
697 \index[dir]{DiskToCatalog}
698 This level causes Bacula to read the files as they currently are on
699 disk, and to compare the current file attributes with the attributes
700 saved in the catalog from the last backup for the job specified on the
701 {\bf VerifyJob} directive. This level differs from the {\bf VolumeToCatalog}
702 level described above by the fact that it doesn't compare against a
703 previous Verify job but against a previous backup. When you run this
704 level, you must supply the verify options on your Include statements.
705 Those options determine what attribute fields are compared.
707 This command can be very useful if you have disk problems because it
708 will compare the current state of your disk against the last successful
709 backup, which may be several jobs.
711 Note, the current implementation (1.32c) does not identify files that
715 \item [Accurate = \lt{}yes\vb{}no\gt{}]
716 \index[dir]{Accurate}
717 In accurate mode, the File daemon knowns exactly which files were present
718 after the last backup. So it is able to handle deleted or renamed files.
720 When restoring a FileSet for a specified date (including "most
721 recent"), Bacula is able to restore exactly the files and
722 directories that existed at the time of the last backup prior to
723 that date including ensuring that deleted files are actually deleted,
724 and renamed directories are restored properly.
726 In this mode, the File daemon must keep data concerning all files in
727 memory. So If you do not have sufficient memory, the backup may
728 either be terribly slow or fail.
730 %% $$ memory = \sum_{i=1}^{n}(strlen(path_i + file_i) + sizeof(CurFile))$$
732 For 500.000 files (a typical desktop linux system), it will require
733 approximately 64 Megabytes of RAM on your File daemon to hold the
734 required information.
736 \item [Verify Job = \lt{}Job-Resource-Name\gt{}]
737 \index[dir]{Verify Job}
738 \index[dir]{Directive!Verify Job}
739 If you run a verify job without this directive, the last job run will be
740 compared with the catalog, which means that you must immediately follow
741 a backup by a verify command. If you specify a {\bf Verify Job} Bacula
742 will find the last job with that name that ran. This permits you to run
743 all your backups, then run Verify jobs on those that you wish to be
744 verified (most often a {\bf VolumeToCatalog}) so that the tape just
747 \item [JobDefs = \lt{}JobDefs-Resource-Name\gt{}]
749 \index[dir]{Directive!JobDefs}
750 If a JobDefs-Resource-Name is specified, all the values contained in the
751 named JobDefs resource will be used as the defaults for the current Job.
752 Any value that you explicitly define in the current Job resource, will
753 override any defaults specified in the JobDefs resource. The use of
754 this directive permits writing much more compact Job resources where the
755 bulk of the directives are defined in one or more JobDefs. This is
756 particularly useful if you have many similar Jobs but with minor
757 variations such as different Clients. A simple example of the use of
758 JobDefs is provided in the default bacula-dir.conf file.
760 \item [Bootstrap = \lt{}bootstrap-file\gt{}]
761 \index[dir]{Bootstrap}
762 \index[dir]{Directive!Bootstrap}
763 The Bootstrap directive specifies a bootstrap file that, if provided,
764 will be used during {\bf Restore} Jobs and is ignored in other Job
765 types. The {\bf bootstrap} file contains the list of tapes to be used
766 in a restore Job as well as which files are to be restored.
767 Specification of this directive is optional, and if specified, it is
768 used only for a restore job. In addition, when running a Restore job
769 from the console, this value can be changed.
771 If you use the {\bf Restore} command in the Console program, to start a
772 restore job, the {\bf bootstrap} file will be created automatically from
773 the files you select to be restored.
775 For additional details of the {\bf bootstrap} file, please see
776 \ilink{Restoring Files with the Bootstrap File}{BootstrapChapter} chapter
779 \label{writebootstrap}
780 \item [Write Bootstrap = \lt{}bootstrap-file-specification\gt{}]
781 \index[dir]{Write Bootstrap}
782 \index[dir]{Directive!Write Bootstrap}
783 The {\bf writebootstrap} directive specifies a file name where Bacula
784 will write a {\bf bootstrap} file for each Backup job run. This
785 directive applies only to Backup Jobs. If the Backup job is a Full
786 save, Bacula will erase any current contents of the specified file
787 before writing the bootstrap records. If the Job is an Incremental
789 save, Bacula will append the current bootstrap record to the end of the
792 Using this feature, permits you to constantly have a bootstrap file that
793 can recover the current state of your system. Normally, the file
794 specified should be a mounted drive on another machine, so that if your
795 hard disk is lost, you will immediately have a bootstrap record
796 available. Alternatively, you should copy the bootstrap file to another
797 machine after it is updated. Note, it is a good idea to write a separate
798 bootstrap file for each Job backed up including the job that backs up
799 your catalog database.
801 If the {\bf bootstrap-file-specification} begins with a vertical bar
802 (\verb+|+), Bacula will use the specification as the name of a program to which
803 it will pipe the bootstrap record. It could for example be a shell
804 script that emails you the bootstrap record.
806 On versions 1.39.22 or greater, before opening the file or executing the
807 specified command, Bacula performs
808 \ilink{character substitution}{character substitution} like in RunScript
809 directive. To automatically manage your bootstrap files, you can use
810 this in your {\bf JobDefs} resources:
813 Write Bootstrap = "%c_%n.bsr"
818 For more details on using this file, please see the chapter entitled
819 \ilink{The Bootstrap File}{BootstrapChapter} of this manual.
821 \item [Client = \lt{}client-resource-name\gt{}]
823 \index[dir]{Directive!Client}
824 The Client directive specifies the Client (File daemon) that will be used in
825 the current Job. Only a single Client may be specified in any one Job. The
826 Client runs on the machine to be backed up, and sends the requested files to
827 the Storage daemon for backup, or receives them when restoring. For
828 additional details, see the
829 \ilink{Client Resource section}{ClientResource2} of this chapter.
830 This directive is required.
832 \item [FileSet = \lt{}FileSet-resource-name\gt{}]
834 \index[dir]{Directive!FileSet}
835 The FileSet directive specifies the FileSet that will be used in the
836 current Job. The FileSet specifies which directories (or files) are to
837 be backed up, and what options to use (e.g. compression, ...). Only a
838 single FileSet resource may be specified in any one Job. For additional
839 details, see the \ilink{FileSet Resource section}{FileSetResource} of
840 this chapter. This directive is required.
842 \item [Base = \lt{}job-resource-name, ...\gt{}]
844 \index[dir]{Directive!Base}
845 The Base directive permits to specify the list of jobs that will be used during
846 Full backup as base. This directive is optional. See the \ilink{Base Job
847 chapter}{basejobs} for more information.
849 \item [Messages = \lt{}messages-resource-name\gt{}]
850 \index[dir]{Messages}
851 \index[dir]{Directive!Messages}
852 The Messages directive defines what Messages resource should be used for
853 this job, and thus how and where the various messages are to be
854 delivered. For example, you can direct some messages to a log file, and
855 others can be sent by email. For additional details, see the
856 \ilink{Messages Resource}{MessagesChapter} Chapter of this manual. This
857 directive is required.
859 \item [Pool = \lt{}pool-resource-name\gt{}]
861 \index[dir]{Directive!Pool}
862 The Pool directive defines the pool of Volumes where your data can be
863 backed up. Many Bacula installations will use only the {\bf Default}
864 pool. However, if you want to specify a different set of Volumes for
865 different Clients or different Jobs, you will probably want to use
866 Pools. For additional details, see the \ilink{Pool Resource
867 section}{PoolResource} of this chapter. This directive is required.
869 \item [Full Backup Pool = \lt{}pool-resource-name\gt{}]
870 \index[dir]{Full Backup Pool}
871 \index[dir]{Directive!Full Backup Pool}
872 The {\it Full Backup Pool} specifies a Pool to be used for Full backups.
873 It will override any Pool specification during a Full backup. This
874 directive is optional.
876 \item [Differential Backup Pool = \lt{}pool-resource-name\gt{}]
877 \index[dir]{Differential Backup Pool}
878 \index[dir]{Directive!Differential Backup Pool}
879 The {\it Differential Backup Pool} specifies a Pool to be used for
880 Differential backups. It will override any Pool specification during a
881 Differential backup. This directive is optional.
883 \item [Incremental Backup Pool = \lt{}pool-resource-name\gt{}]
884 \index[dir]{Incremental Backup Pool}
885 \index[dir]{Directive!Incremental Backup Pool}
886 The {\it Incremental Backup Pool} specifies a Pool to be used for
887 Incremental backups. It will override any Pool specification during an
888 Incremental backup. This directive is optional.
890 \item [Schedule = \lt{}schedule-name\gt{}]
891 \index[dir]{Schedule}
892 \index[dir]{Directive!Schedule}
893 The Schedule directive defines what schedule is to be used for the Job.
894 The schedule in turn determines when the Job will be automatically
895 started and what Job level (i.e. Full, Incremental, ...) is to be run.
896 This directive is optional, and if left out, the Job can only be started
897 manually using the Console program. Although you may specify only a
898 single Schedule resource for any one job, the Schedule resource may
899 contain multiple {\bf Run} directives, which allow you to run the Job at
900 many different times, and each {\bf run} directive permits overriding
901 the default Job Level Pool, Storage, and Messages resources. This gives
902 considerable flexibility in what can be done with a single Job. For
903 additional details, see the \ilink{Schedule Resource
904 Chapter}{ScheduleResource} of this manual.
907 \item [Storage = \lt{}storage-resource-name\gt{}]
909 \index[dir]{Directive!Storage}
910 The Storage directive defines the name of the storage services where you
911 want to backup the FileSet data. For additional details, see the
912 \ilink{Storage Resource Chapter}{StorageResource2} of this manual.
913 The Storage resource may also be specified in the Job's Pool resource,
914 in which case the value in the Pool resource overrides any value
915 in the Job. This Storage resource definition is not required by either
916 the Job resource or in the Pool, but it must be specified in
917 one or the other, if not an error will result.
919 \item [Max Start Delay = \lt{}time\gt{}]
920 \index[dir]{Max Start Delay}
921 \index[dir]{Directive!Max Start Delay}
922 The time specifies the maximum delay between the scheduled time and the
923 actual start time for the Job. For example, a job can be scheduled to
924 run at 1:00am, but because other jobs are running, it may wait to run.
925 If the delay is set to 3600 (one hour) and the job has not begun to run
926 by 2:00am, the job will be canceled. This can be useful, for example,
927 to prevent jobs from running during day time hours. The default is 0
928 which indicates no limit.
930 \item [Max Run Time = \lt{}time\gt{}]
931 \index[dir]{Max Run Time}
932 \index[dir]{Directive!Max Run Time}
933 The time specifies the maximum allowed time that a job may run, counted
934 from when the job starts, ({\bf not} necessarily the same as when the
937 By default, the the watchdog thread will kill any Job that has run more
938 than 6 days. The maximum watchdog timeout is independent of MaxRunTime
939 and cannot be changed.
942 \item [Incremental|Differential Max Wait Time = \lt{}time\gt{}]
943 \index[dir]{Incremental Wait Run Time}
944 \index[dir]{Differential Wait Run Time}
945 \index[dir]{Directive!Differential Max Wait Time}
946 Theses directives have been deprecated in favor of
947 \texttt{Incremental|Differential Max Run Time} since bacula 2.3.18.
949 \item [Incremental Max Run Time = \lt{}time\gt{}]
950 \index[dir]{Incremental Max Run Time}
951 \index[dir]{Directive!Incremental Max Run Time}
952 The time specifies the maximum allowed time that an Incremental backup job may
953 run, counted from when the job starts, ({\bf not} necessarily the same as when
954 the job was scheduled).
956 \item [Differential Max Wait Time = \lt{}time\gt{}]
957 \index[dir]{Differential Max Run Time}
958 \index[dir]{Directive!Differential Max Run Time}
959 The time specifies the maximum allowed time that a Differential backup job may
960 run, counted from when the job starts, ({\bf not} necessarily the same as when
961 the job was scheduled).
963 \item [Max Run Sched Time = \lt{}time\gt{}]
964 \index[dir]{Max Run Sched Time}
965 \index[dir]{Directive!Max Run Sched Time}
967 The time specifies the maximum allowed time that a job may run, counted from
968 when the job was scheduled. This can be useful to prevent jobs from running
969 during working hours. We can see it like \texttt{Max Start Delay + Max Run
972 \item [Max Wait Time = \lt{}time\gt{}]
973 \index[dir]{Max Wait Time}
974 \index[dir]{Directive!Max Wait Time}
975 The time specifies the maximum allowed time that a job may block waiting
976 for a resource (such as waiting for a tape to be mounted, or waiting for
977 the storage or file daemons to perform their duties), counted from the
978 when the job starts, ({\bf not} necessarily the same as when the job was
979 scheduled). This directive works as expected since bacula 2.3.18.
983 \includegraphics[width=13cm]{\idir different_time.eps}
984 \caption{Job time control directives}
985 \label{fig:differenttime}
988 \item [Maximum Bandwidth = \lt{}speed\gt{}]
989 \index[dir]{Maximum Bandwidth}
990 \index[dir]{Directive!Maximum Bandwidth}
992 The speed parameter specifies the maximum allowed bandwidth that a job may
993 use. The speed parameter should be specified in k/s, kb/s, m/s or mb/s.
995 \item [Max Full Interval = \lt{}time\gt{}]
996 \index[dir]{Max Full Interval}
997 \index[dir]{Directive!Max Full Interval}
998 The time specifies the maximum allowed age (counting from start time) of
999 the most recent successful Full backup that is required in order to run
1000 Incremental or Differential backup jobs. If the most recent Full backup
1001 is older than this interval, Incremental and Differential backups will be
1002 upgraded to Full backups automatically. If this directive is not present,
1003 or specified as 0, then the age of the previous Full backup is not
1006 \label{PreferMountedVolumes}
1007 \item [Prefer Mounted Volumes = \lt{}yes\vb{}no\gt{}]
1008 \index[dir]{Prefer Mounted Volumes}
1009 \index[dir]{Directive!Prefer Mounted Volumes}
1010 If the Prefer Mounted Volumes directive is set to {\bf yes} (default
1011 yes), the Storage daemon is requested to select either an Autochanger or
1012 a drive with a valid Volume already mounted in preference to a drive
1013 that is not ready. This means that all jobs will attempt to append
1014 to the same Volume (providing the Volume is appropriate -- right Pool,
1015 ... for that job), unless you are using multiple pools.
1016 If no drive with a suitable Volume is available, it
1017 will select the first available drive. Note, any Volume that has
1018 been requested to be mounted, will be considered valid as a mounted
1019 volume by another job. This if multiple jobs start at the same time
1020 and they all prefer mounted volumes, the first job will request the
1021 mount, and the other jobs will use the same volume.
1023 If the directive is set to {\bf no}, the Storage daemon will prefer
1024 finding an unused drive, otherwise, each job started will append to the
1025 same Volume (assuming the Pool is the same for all jobs). Setting
1026 Prefer Mounted Volumes to no can be useful for those sites
1027 with multiple drive autochangers that prefer to maximize backup
1028 throughput at the expense of using additional drives and Volumes.
1029 This means that the job will prefer to use an unused drive rather
1030 than use a drive that is already in use.
1032 Despite the above, we recommend against setting this directive to
1034 it tends to add a lot of swapping of Volumes between the different
1035 drives and can easily lead to deadlock situations in the Storage
1036 daemon. We will accept bug reports against it, but we cannot guarantee
1037 that we will be able to fix the problem in a reasonable time.
1039 A better alternative for using multiple drives is to use multiple
1040 pools so that Bacula will be forced to mount Volumes from those Pools
1041 on different drives.
1043 \item [Prune Jobs = \lt{}yes\vb{}no\gt{}]
1044 \index[dir]{Prune Jobs}
1045 \index[dir]{Directive!Prune Jobs}
1046 Normally, pruning of Jobs from the Catalog is specified on a Client by
1047 Client basis in the Client resource with the {\bf AutoPrune} directive.
1048 If this directive is specified (not normally) and the value is {\bf
1049 yes}, it will override the value specified in the Client resource. The
1050 default is {\bf no}.
1053 \item [Prune Files = \lt{}yes\vb{}no\gt{}]
1054 \index[dir]{Prune Files}
1055 \index[dir]{Directive!Prune Files}
1056 Normally, pruning of Files from the Catalog is specified on a Client by
1057 Client basis in the Client resource with the {\bf AutoPrune} directive.
1058 If this directive is specified (not normally) and the value is {\bf
1059 yes}, it will override the value specified in the Client resource. The
1060 default is {\bf no}.
1062 \item [Prune Volumes = \lt{}yes\vb{}no\gt{}]
1063 \index[dir]{Prune Volumes}
1064 \index[dir]{Directive!Prune Volumes}
1065 Normally, pruning of Volumes from the Catalog is specified on a Pool by
1066 Pool basis in the Pool resource with the {\bf AutoPrune} directive.
1067 Note, this is different from File and Job pruning which is done on a
1068 Client by Client basis. If this directive is specified (not normally)
1069 and the value is {\bf yes}, it will override the value specified in the
1070 Pool resource. The default is {\bf no}.
1072 \item [RunScript \{\lt{}body-of-runscript\gt{}\}]
1073 \index[dir]{RunScript}
1074 \index[dir]{Directive!Run Script}
1076 The RunScript directive behaves like a resource in that it
1077 requires opening and closing braces around a number of directives
1078 that make up the body of the runscript.
1080 The specified {\bf Command} (see below for details) is run as an external
1081 program prior or after the current Job. This is optional. By default, the
1082 program is executed on the Client side like in \texttt{ClientRunXXXJob}.
1084 \textbf{Console} options are special commands that are sent to the director instead
1085 of the OS. At this time, console command ouputs are redirected to log with
1088 You can use following console command : \texttt{delete}, \texttt{disable},
1089 \texttt{enable}, \texttt{estimate}, \texttt{list}, \texttt{llist},
1090 \texttt{memory}, \texttt{prune}, \texttt{purge}, \texttt{reload},
1091 \texttt{status}, \texttt{setdebug}, \texttt{show}, \texttt{time},
1092 \texttt{trace}, \texttt{update}, \texttt{version}, \texttt{.client},
1093 \texttt{.jobs}, \texttt{.pool}, \texttt{.storage}. See console chapter for
1094 more information. You need to specify needed information on command line, nothing
1095 will be prompted. Example :
1098 Console = "prune files client=%c"
1099 Console = "update stats age=3"
1102 You can specify more than one Command/Console option per RunScript.
1104 You can use following options may be specified in the body
1107 \begin{tabular}{|c|c|c|l}
1108 Options & Value & Default & Information \\
1111 Runs On Success & Yes/No & {\it Yes} & Run command if JobStatus is successful\\
1113 Runs On Failure & Yes/No & {\it No} & Run command if JobStatus isn't successful\\
1115 Runs On Client & Yes/No & {\it Yes} & Run command on client\\
1117 Runs When & Before|After|Always|\textsl{AfterVSS} & {\it Never} & When run commands\\
1119 Fail Job On Error & Yes/No & {\it Yes} & Fail job if script returns
1120 something different from 0 \\
1122 Command & & & Path to your script\\
1124 Console & & & Console command\\
1129 Any output sent by the command to standard output will be included in the
1130 Bacula job report. The command string must be a valid program name or name
1133 In addition, the command string is parsed then fed to the OS,
1134 which means that the path will be searched to execute your specified
1135 command, but there is no shell interpretation, as a consequence, if you
1136 invoke complicated commands or want any shell features such as redirection
1137 or piping, you must call a shell script and do it inside that script.
1139 Before submitting the specified command to the operating system, Bacula
1140 performs character substitution of the following characters:
1142 \label{character substitution}
1148 %d = Daemon's name (Such as host-dir or host-fd)
1149 %D = Director's name (Also valid on file daemon)
1150 %e = Job Exit Status
1151 %f = Job FileSet (Only on director side)
1158 %p = Pool name (Only on director side)
1160 %t = Job type (Backup, ...)
1161 %v = Volume name (Only on director side)
1162 %w = Storage name (Only on director side)
1163 %x = Spooling enabled? ("yes" or "no")
1168 Some character substitutions are not available in all situations. The Job Exit
1169 Status code \%e edits the following values:
1171 \index[dir]{Exit Status}
1178 \item Unknown term code
1181 Thus if you edit it on a command line, you will need to enclose
1182 it within some sort of quotes.
1185 You can use these following shortcuts:\\
1187 \begin{tabular}{|c|c|c|c|c|c}
1188 Keyword & RunsOnSuccess & RunsOnFailure & FailJobOnError & Runs On Client & RunsWhen \\
1190 Run Before Job & & & Yes & No & Before \\
1192 Run After Job & Yes & No & & No & After \\
1194 Run After Failed Job & No & Yes & & No & After \\
1196 Client Run Before Job & & & Yes & Yes & Before \\
1198 Client Run After Job & Yes & No & & Yes & After \\
1206 Command = "/etc/init.d/apache stop"
1212 Command = "/etc/init.d/apache start"
1216 {\bf Notes about ClientRunBeforeJob}
1218 For compatibility reasons, with this shortcut, the command is executed
1219 directly when the client recieve it. And if the command is in error, other
1220 remote runscripts will be discarded. To be sure that all commands will be
1221 sent and executed, you have to use RunScript syntax.
1223 {\bf Special Windows Considerations}
1225 You can run scripts just after snapshots initializations with
1226 \textsl{AfterVSS} keyword.
1228 In addition, for a Windows client, please take
1229 note that you must ensure a correct path to your script. The script or
1230 program can be a .com, .exe or a .bat file. If you just put the program
1231 name in then Bacula will search using the same rules that cmd.exe uses
1232 (current directory, Bacula bin directory, and PATH). It will even try the
1233 different extensions in the same order as cmd.exe.
1234 The command can be anything that cmd.exe or command.com will recognize
1235 as an executable file.
1237 However, if you have slashes in the program name then Bacula figures you
1238 are fully specifying the name, so you must also explicitly add the three
1239 character extension.
1241 The command is run in a Win32 environment, so Unix like commands will not
1242 work unless you have installed and properly configured Cygwin in addition
1243 to and separately from Bacula.
1245 The System \%Path\% will be searched for the command. (under the
1246 environment variable dialog you have have both System Environment and
1247 User Environment, we believe that only the System environment will be
1248 available to bacula-fd, if it is running as a service.)
1250 System environment variables can be referenced with \%var\% and
1251 used as either part of the command name or arguments.
1253 So if you have a script in the Bacula\\bin directory then the following lines
1258 Client Run Before Job = systemstate
1260 Client Run Before Job = systemstate.bat
1262 Client Run Before Job = "systemstate"
1264 Client Run Before Job = "systemstate.bat"
1266 ClientRunBeforeJob = "\"C:/Program Files/Bacula/systemstate.bat\""
1270 The outer set of quotes is removed when the configuration file is parsed.
1271 You need to escape the inner quotes so that they are there when the code
1272 that parses the command line for execution runs so it can tell what the
1278 ClientRunBeforeJob = "\"C:/Program Files/Software
1279 Vendor/Executable\" /arg1 /arg2 \"foo bar\""
1283 The special characters
1287 will need to be quoted,
1288 if they are part of a filename or argument.
1290 If someone is logged in, a blank "command" window running the commands
1291 will be present during the execution of the command.
1293 Some Suggestions from Phil Stracchino for running on Win32 machines with
1294 the native Win32 File daemon:
1297 \item You might want the ClientRunBeforeJob directive to specify a .bat
1298 file which runs the actual client-side commands, rather than trying
1299 to run (for example) regedit /e directly.
1300 \item The batch file should explicitly 'exit 0' on successful completion.
1301 \item The path to the batch file should be specified in Unix form:
1303 ClientRunBeforeJob = "c:/bacula/bin/systemstate.bat"
1305 rather than DOS/Windows form:
1307 ClientRunBeforeJob =
1309 "c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}systemstate.bat"
1313 For Win32, please note that there are certain limitations:
1315 ClientRunBeforeJob = "C:/Program Files/Bacula/bin/pre-exec.bat"
1317 Lines like the above do not work because there are limitations of
1318 cmd.exe that is used to execute the command.
1319 Bacula prefixes the string you supply with {\bf cmd.exe /c }. To test that
1320 your command works you should type {\bf cmd /c "C:/Program Files/test.exe"} at a
1321 cmd prompt and see what happens. Once the command is correct insert a
1322 backslash (\textbackslash{}) before each double quote ("), and
1323 then put quotes around the whole thing when putting it in
1324 the director's .conf file. You either need to have only one set of quotes
1325 or else use the short name and don't put quotes around the command path.
1327 Below is the output from cmd's help as it relates to the command line
1328 passed to the /c option.
1331 If /C or /K is specified, then the remainder of the command line after
1332 the switch is processed as a command line, where the following logic is
1333 used to process quote (") characters:
1337 If all of the following conditions are met, then quote characters
1338 on the command line are preserved:
1341 \item exactly two quote characters.
1342 \item no special characters between the two quote characters,
1343 where special is one of:
1347 \item there are one or more whitespace characters between the
1348 the two quote characters.
1349 \item the string between the two quote characters is the name
1350 of an executable file.
1353 \item Otherwise, old behavior is to see if the first character is
1354 a quote character and if so, strip the leading character and
1355 remove the last quote character on the command line, preserving
1356 any text after the last quote character.
1361 The following example of the use of the Client Run Before Job directive was
1362 submitted by a user:\\
1363 You could write a shell script to back up a DB2 database to a FIFO. The shell
1373 db2 BACKUP DATABASE mercuryd TO $DIR/dbpipe WITHOUT PROMPTING &
1378 The following line in the Job resource in the bacula-dir.conf file:
1381 Client Run Before Job = "su - mercuryd -c \"/u01/mercuryd/backupdb.sh '%t'
1386 When the job is run, you will get messages from the output of the script
1387 stating that the backup has started. Even though the command being run is
1388 backgrounded with \&, the job will block until the "db2 BACKUP DATABASE"
1389 command, thus the backup stalls.
1391 To remedy this situation, the "db2 BACKUP DATABASE" line should be changed to
1396 db2 BACKUP DATABASE mercuryd TO $DIR/dbpipe WITHOUT PROMPTING > $DIR/backup.log
1401 It is important to redirect the input and outputs of a backgrounded command to
1402 /dev/null to prevent the script from blocking.
1404 \item [Run Before Job = \lt{}command\gt{}]
1405 \index[dir]{Run Before Job}
1406 \index[dir]{Directive!Run Before Job}
1407 \index[dir]{Directive!Run Before Job}
1408 The specified {\bf command} is run as an external program prior to running the
1409 current Job. This directive is not required, but if it is defined, and if the
1410 exit code of the program run is non-zero, the current Bacula job will be
1414 Run Before Job = "echo test"
1416 it's equivalent to :
1419 Command = "echo test"
1425 Lutz Kittler has pointed out that using the RunBeforeJob directive can be a
1426 simple way to modify your schedules during a holiday. For example, suppose
1427 that you normally do Full backups on Fridays, but Thursday and Friday are
1428 holidays. To avoid having to change tapes between Thursday and Friday when
1429 no one is in the office, you can create a RunBeforeJob that returns a
1430 non-zero status on Thursday and zero on all other days. That way, the
1431 Thursday job will not run, and on Friday the tape you inserted on Wednesday
1432 before leaving will be used.
1434 \item [Run After Job = \lt{}command\gt{}]
1435 \index[dir]{Run After Job}
1436 \index[dir]{Directive!Run After Job}
1437 The specified {\bf command} is run as an external program if the current
1438 job terminates normally (without error or without being canceled). This
1439 directive is not required. If the exit code of the program run is
1440 non-zero, Bacula will print a warning message. Before submitting the
1441 specified command to the operating system, Bacula performs character
1442 substitution as described above for the {\bf RunScript} directive.
1444 An example of the use of this directive is given in the
1445 \ilink{Tips Chapter}{JobNotification} of this manual.
1447 See the {\bf Run After Failed Job} if you
1448 want to run a script after the job has terminated with any
1451 \item [Run After Failed Job = \lt{}command\gt{}]
1452 \index[dir]{Run After Job}
1453 \index[dir]{Directive!Run After Job}
1454 The specified {\bf command} is run as an external program after the current
1455 job terminates with any error status. This directive is not required. The
1456 command string must be a valid program name or name of a shell script. If
1457 the exit code of the program run is non-zero, Bacula will print a
1458 warning message. Before submitting the specified command to the
1459 operating system, Bacula performs character substitution as described above
1460 for the {\bf RunScript} directive. Note, if you wish that your script
1461 will run regardless of the exit status of the Job, you can use this :
1464 Command = "echo test"
1468 RunsOnSuccess = yes # default, you can drop this line
1472 An example of the use of this directive is given in the
1473 \ilink{Tips Chapter}{JobNotification} of this manual.
1476 \item [Client Run Before Job = \lt{}command\gt{}]
1477 \index[dir]{Client Run Before Job}
1478 \index[dir]{Directive!Client Run Before Job}
1479 This directive is the same as {\bf Run Before Job} except that the
1480 program is run on the client machine. The same restrictions apply to
1481 Unix systems as noted above for the {\bf RunScript}.
1483 \item [Client Run After Job = \lt{}command\gt{}]
1484 \index[dir]{Client Run After Job}
1485 \index[dir]{Directive!Client Run After Job}
1486 The specified {\bf command} is run on the client machine as soon
1487 as data spooling is complete in order to allow restarting applications
1488 on the client as soon as possible. .
1490 Note, please see the notes above in {\bf RunScript}
1491 concerning Windows clients.
1493 \item [Rerun Failed Levels = \lt{}yes\vb{}no\gt{}]
1494 \index[dir]{Rerun Failed Levels}
1495 \index[dir]{Directive!Rerun Failed Levels}
1496 If this directive is set to {\bf yes} (default no), and Bacula detects that
1497 a previous job at a higher level (i.e. Full or Differential) has failed,
1498 the current job level will be upgraded to the higher level. This is
1499 particularly useful for Laptops where they may often be unreachable, and if
1500 a prior Full save has failed, you wish the very next backup to be a Full
1501 save rather than whatever level it is started as.
1503 There are several points that must be taken into account when using this
1504 directive: first, a failed job is defined as one that has not terminated
1505 normally, which includes any running job of the same name (you need to
1506 ensure that two jobs of the same name do not run simultaneously);
1507 secondly, the {\bf Ignore FileSet Changes} directive is not considered
1508 when checking for failed levels, which means that any FileSet change will
1511 \item [Spool Data = \lt{}yes\vb{}no\gt{}]
1512 \index[dir]{Spool Data}
1513 \index[dir]{Directive!Spool Data}
1515 If this directive is set to {\bf yes} (default no), the Storage daemon will
1516 be requested to spool the data for this Job to disk rather than write it
1517 directly to the Volume (normally a tape).
1519 Thus the data is written in large blocks to the Volume rather than small
1520 blocks. This directive is particularly useful when running multiple
1521 simultaneous backups to tape. Once all the data arrives or the spool
1522 files' maximum sizes are reached, the data will be despooled and written
1525 Spooling data prevents interleaving date from several job and reduces or
1526 eliminates tape drive stop and start commonly known as "shoe-shine".
1528 We don't recommend using this option if you are writing to a disk file
1529 using this option will probably just slow down the backup jobs.
1531 NOTE: When this directive is set to yes, Spool Attributes is also
1532 automatically set to yes.
1534 \item [Spool Attributes = \lt{}yes\vb{}no\gt{}]
1535 \index[dir]{Spool Attributes}
1536 \index[dir]{Directive!Spool Attributes}
1538 \index[general]{slow}
1539 \index[dir]{Backups!slow}
1540 \index[general]{Backups!slow}
1541 The default is set to {\bf no}, which means that the File attributes are
1542 sent by the Storage daemon to the Director as they are stored on tape.
1543 However, if you want to avoid the possibility that database updates will
1544 slow down writing to the tape, you may want to set the value to {\bf
1545 yes}, in which case the Storage daemon will buffer the File attributes
1546 and Storage coordinates to a temporary file in the Working Directory,
1547 then when writing the Job data to the tape is completed, the attributes
1548 and storage coordinates will be sent to the Director.
1550 NOTE: When Spool Data is set to yes, Spool Attributes is also
1551 automatically set to yes.
1553 \item [SpoolSize={\it bytes}]
1554 \index[dir]{SpoolSize}
1555 \index[dir]{Directive!SpoolSize}
1556 where the bytes specify the maximum spool size for this job.
1557 The default is take from Device Maximum Spool Size limit.
1558 This directive is available only in Bacula version 2.3.5 or
1562 \item [Where = \lt{}directory\gt{}]
1564 \index[dir]{Directive!Where}
1565 This directive applies only to a Restore job and specifies a prefix to
1566 the directory name of all files being restored. This permits files to
1567 be restored in a different location from which they were saved. If {\bf
1568 Where} is not specified or is set to backslash ({\bf /}), the files will
1569 be restored to their original location. By default, we have set {\bf
1570 Where} in the example configuration files to be {\bf
1571 /tmp/bacula-restores}. This is to prevent accidental overwriting of
1574 \item [Add Prefix = \lt{}directory\gt{}]
1575 \label{confaddprefix}
1576 \index[dir]{AddPrefix}
1577 \index[dir]{Directive!AddPrefix}
1578 This directive applies only to a Restore job and specifies a prefix to the
1579 directory name of all files being restored. This will use \ilink{File
1580 Relocation}{filerelocation} feature implemented in Bacula 2.1.8 or later.
1582 \item [Add Suffix = \lt{}extention\gt{}]
1583 \index[dir]{AddSuffix}
1584 \index[dir]{Directive!AddSuffix}
1585 This directive applies only to a Restore job and specifies a suffix to all
1586 files being restored. This will use \ilink{File Relocation}{filerelocation}
1587 feature implemented in Bacula 2.1.8 or later.
1589 Using \texttt{Add Suffix=.old}, \texttt{/etc/passwd} will be restored to
1590 \texttt{/etc/passwsd.old}
1592 \item [Strip Prefix = \lt{}directory\gt{}]
1593 \index[dir]{StripPrefix}
1594 \index[dir]{Directive!StripPrefix}
1595 This directive applies only to a Restore job and specifies a prefix to remove
1596 from the directory name of all files being restored. This will use the
1597 \ilink{File Relocation}{filerelocation} feature implemented in Bacula 2.1.8
1600 Using \texttt{Strip Prefix=/etc}, \texttt{/etc/passwd} will be restored to
1603 Under Windows, if you want to restore \texttt{c:/files} to \texttt{d:/files},
1611 \item [RegexWhere = \lt{}expressions\gt{}]
1612 \index[dir]{RegexWhere}
1613 \index[dir]{Directive!RegexWhere}
1614 This directive applies only to a Restore job and specifies a regex filename
1615 manipulation of all files being restored. This will use \ilink{File
1616 Relocation}{filerelocation} feature implemented in Bacula 2.1.8 or later.
1618 For more informations about how use this option, see
1619 \ilink{this}{useregexwhere}.
1621 \item [Replace = \lt{}replace-option\gt{}]
1622 \index[dir]{Replace}
1623 \index[dir]{Directive!Replace}
1624 This directive applies only to a Restore job and specifies what happens
1625 when Bacula wants to restore a file or directory that already exists.
1626 You have the following options for {\bf replace-option}:
1632 when the file to be restored already exists, it is deleted and then
1633 replaced by the copy that was backed up. This is the default value.
1636 \index[dir]{ifnewer}
1637 if the backed up file (on tape) is newer than the existing file, the
1638 existing file is deleted and replaced by the back up.
1641 \index[dir]{ifolder}
1642 if the backed up file (on tape) is older than the existing file, the
1643 existing file is deleted and replaced by the back up.
1647 if the backed up file already exists, Bacula skips restoring this file.
1650 \item [Prefix Links=\lt{}yes\vb{}no\gt{}]
1651 \index[dir]{Prefix Links}
1652 \index[dir]{Directive!Prefix Links}
1653 If a {\bf Where} path prefix is specified for a recovery job, apply it
1654 to absolute links as well. The default is {\bf No}. When set to {\bf
1655 Yes} then while restoring files to an alternate directory, any absolute
1656 soft links will also be modified to point to the new alternate
1657 directory. Normally this is what is desired -- i.e. everything is self
1658 consistent. However, if you wish to later move the files to their
1659 original locations, all files linked with absolute names will be broken.
1661 \item [Maximum Concurrent Jobs = \lt{}number\gt{}]
1662 \index[dir]{Maximum Concurrent Jobs}
1663 \index[dir]{Directive!Maximum Concurrent Jobs}
1664 where \lt{}number\gt{} is the maximum number of Jobs from the current
1665 Job resource that can run concurrently. Note, this directive limits
1666 only Jobs with the same name as the resource in which it appears. Any
1667 other restrictions on the maximum concurrent jobs such as in the
1668 Director, Client, or Storage resources will also apply in addition to
1669 the limit specified here. The default is set to 1, but you may set it
1670 to a larger number. We strongly recommend that you read the WARNING
1671 documented under \ilink{ Maximum Concurrent Jobs}{DirMaxConJobs} in the
1672 Director's resource.
1674 \item [Reschedule On Error = \lt{}yes\vb{}no\gt{}]
1675 \index[dir]{Reschedule On Error}
1676 \index[dir]{Directive!Reschedule On Error}
1677 If this directive is enabled, and the job terminates in error, the job
1678 will be rescheduled as determined by the {\bf Reschedule Interval} and
1679 {\bf Reschedule Times} directives. If you cancel the job, it will not
1680 be rescheduled. The default is {\bf no} (i.e. the job will not be
1683 This specification can be useful for portables, laptops, or other
1684 machines that are not always connected to the network or switched on.
1686 \item [Reschedule Interval = \lt{}time-specification\gt{}]
1687 \index[dir]{Reschedule Interval}
1688 \index[dir]{Directive!Reschedule Interval}
1689 If you have specified {\bf Reschedule On Error = yes} and the job
1690 terminates in error, it will be rescheduled after the interval of time
1691 specified by {\bf time-specification}. See \ilink{the time
1692 specification formats}{Time} in the Configure chapter for details of
1693 time specifications. If no interval is specified, the job will not be
1694 rescheduled on error.
1696 \item [Reschedule Times = \lt{}count\gt{}]
1697 \index[dir]{Reschedule Times}
1698 \index[dir]{Directive!Reschedule Times}
1699 This directive specifies the maximum number of times to reschedule the
1700 job. If it is set to zero (the default) the job will be rescheduled an
1701 indefinite number of times.
1703 \item [Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}]
1704 \index[general]{Allow Duplicate Jobs}
1706 \begin{figure}[htbp]
1708 \includegraphics[width=13cm]{\idir duplicate-real.eps}
1709 \caption{Allow Duplicate Jobs usage}
1710 \label{fig:allowduplicatejobs}
1713 A duplicate job in the sense we use it here means a second or subsequent job
1714 with the same name starts. This happens most frequently when the first job
1715 runs longer than expected because no tapes are available.
1717 If this directive is enabled duplicate jobs will be run. If
1718 the directive is set to {\bf no} (default) then only one job of a given name
1719 may run at one time, and the action that Bacula takes to ensure only
1720 one job runs is determined by the other directives (see below).
1722 If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs
1723 are present and none of the three directives given below permit
1724 cancelling a job, then the current job (the second one started)
1727 \item [Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}]
1728 \index[general]{Allow Higher Duplicates}
1729 This directive was implemented in version 5.0.0, but does not work
1730 as expected. If used, it should always be set to no. In later versions
1731 of Bacula the directive is disabled (disregarded).
1734 \item [Cancel Lower Level Duplicates = \lt{}yes\vb{}no\gt{}]
1735 \index[general]{Cancel Lower Level Duplicates}
1736 If \textbf{Allow Duplicates Jobs} is set to \textbf{no} and this
1737 directive is set to \textbf{yes}, Bacula will choose between duplicated
1738 jobs the one with the highest level. For example, it will cancel a
1739 previous Incremental to run a Full backup. It works only for Backup
1740 jobs. The default is \texttt{no}. If the levels of the duplicated
1741 jobs are the same, nothing is done and the other
1742 Cancel XXX Duplicate directives will be examined.
1744 \item [Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}]
1745 \index[general]{Cancel Queued Duplicates}
1746 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1747 if this directive is set to {\bf yes} any job that is
1748 already queued to run but not yet running will be canceled.
1749 The default is {\bf no}.
1751 \item[Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}]
1752 \index[general]{Cancel Running Duplicates}
1753 If {\bf Allow Duplicate Jobs} is set to {\bf no} and
1754 if this directive is set to {\bf yes} any job that is already running
1755 will be canceled. The default is {\bf no}.
1758 %%\item[DuplicateJobProximity = \lt{}time-specification\gt{}]
1759 %%\index[general]{Duplicate Job Proximity}
1760 %% This directive permits to determine if two jobs are really duplicated.
1761 %% If the first one is running for long time, this is probably not a good
1762 %% idea to cancel it.
1764 \item [Run = \lt{}job-name\gt{}]
1766 \index[dir]{Directive!Run}
1767 \index[dir]{Clone a Job}
1768 The Run directive (not to be confused with the Run option in a
1769 Schedule) allows you to start other jobs or to clone jobs. By using the
1770 cloning keywords (see below), you can backup
1771 the same data (or almost the same data) to two or more drives
1772 at the same time. The {\bf job-name} is normally the same name
1773 as the current Job resource (thus creating a clone). However, it
1774 may be any Job name, so one job may start other related jobs.
1776 The part after the equal sign must be enclosed in double quotes,
1777 and can contain any string or set of options (overrides) that you
1778 can specify when entering the Run command from the console. For
1779 example {\bf storage=DDS-4 ...}. In addition, there are two special
1780 keywords that permit you to clone the current job. They are {\bf level=\%l}
1781 and {\bf since=\%s}. The \%l in the level keyword permits
1782 entering the actual level of the current job and the \%s in the since
1783 keyword permits putting the same time for comparison as used on the
1784 current job. Note, in the case of the since keyword, the \%s must be
1785 enclosed in double quotes, and thus they must be preceded by a backslash
1786 since they are already inside quotes. For example:
1789 run = "Nightly-backup level=%l since=\"%s\" storage=DDS-4"
1792 A cloned job will not start additional clones, so it is not
1793 possible to recurse.
1795 Please note that all cloned jobs, as specified in the Run directives are
1796 submitted for running before the original job is run (while it is being
1797 initialized). This means that any clone job will actually start before
1798 the original job, and may even block the original job from starting
1799 until the original job finishes unless you allow multiple simultaneous
1800 jobs. Even if you set a lower priority on the clone job, if no other
1801 jobs are running, it will start before the original job.
1803 If you are trying to prioritize jobs by using the clone feature (Run
1804 directive), you will find it much easier to do using a RunScript
1805 resource, or a RunBeforeJob directive.
1808 \item [Priority = \lt{}number\gt{}]
1809 \index[dir]{Priority}
1810 \index[dir]{Directive!Priority}
1811 This directive permits you to control the order in which your jobs will
1812 be run by specifying a positive non-zero number. The higher the number,
1813 the lower the job priority. Assuming you are not running concurrent jobs,
1814 all queued jobs of priority 1 will run before queued jobs of priority 2
1815 and so on, regardless of the original scheduling order.
1817 The priority only affects waiting jobs that are queued to run, not jobs
1818 that are already running. If one or more jobs of priority 2 are already
1819 running, and a new job is scheduled with priority 1, the currently
1820 running priority 2 jobs must complete before the priority 1 job is
1821 run, unless Allow Mixed Priority is set.
1823 The default priority is 10.
1825 If you want to run concurrent jobs you should
1826 keep these points in mind:
1829 \item See \ilink{Running Concurrent Jobs}{ConcurrentJobs} on how to setup
1832 \item Bacula concurrently runs jobs of only one priority at a time. It
1833 will not simultaneously run a priority 1 and a priority 2 job.
1835 \item If Bacula is running a priority 2 job and a new priority 1 job is
1836 scheduled, it will wait until the running priority 2 job terminates even
1837 if the Maximum Concurrent Jobs settings would otherwise allow two jobs
1838 to run simultaneously.
1840 \item Suppose that bacula is running a priority 2 job and a new priority 1
1841 job is scheduled and queued waiting for the running priority 2 job to
1842 terminate. If you then start a second priority 2 job, the waiting
1843 priority 1 job will prevent the new priority 2 job from running
1844 concurrently with the running priority 2 job. That is: as long as there
1845 is a higher priority job waiting to run, no new lower priority jobs will
1846 start even if the Maximum Concurrent Jobs settings would normally allow
1847 them to run. This ensures that higher priority jobs will be run as soon
1851 If you have several jobs of different priority, it may not best to start
1852 them at exactly the same time, because Bacula must examine them one at a
1853 time. If by Bacula starts a lower priority job first, then it will run
1854 before your high priority jobs. If you experience this problem, you may
1855 avoid it by starting any higher priority jobs a few seconds before lower
1856 priority ones. This insures that Bacula will examine the jobs in the
1857 correct order, and that your priority scheme will be respected.
1859 \label{AllowMixedPriority}
1860 \item [Allow Mixed Priority = \lt{}yes\vb{}no\gt{}]
1861 \index[dir]{Allow Mixed Priority}
1862 This directive is only implemented in version 2.5 and later. When
1863 set to {\bf yes} (default {\bf no}), this job may run even if lower
1864 priority jobs are already running. This means a high priority job
1865 will not have to wait for other jobs to finish before starting.
1866 The scheduler will only mix priorities when all running jobs have
1869 Note that only higher priority jobs will start early. Suppose the
1870 director will allow two concurrent jobs, and that two jobs with
1871 priority 10 are running, with two more in the queue. If a job with
1872 priority 5 is added to the queue, it will be run as soon as one of
1873 the running jobs finishes. However, new priority 10 jobs will not
1874 be run until the priority 5 job has finished.
1876 \label{WritePartAfterJob}
1877 \item [Write Part After Job = \lt{}yes\vb{}no\gt{}]
1878 \index[dir]{Write Part After Job}
1879 \index[dir]{Directive!Write Part After Job}
1880 This directive is only implemented in version 1.37 and later.
1881 If this directive is set to {\bf yes} (default {\bf no}), a new part file
1882 will be created after the job is finished.
1884 It should be set to {\bf yes} when writing to devices that require mount
1885 (for example DVD), so you are sure that the current part, containing
1886 this job's data, is written to the device, and that no data is left in
1887 the temporary file on the hard disk. However, on some media, like DVD+R
1888 and DVD-R, a lot of space (about 10Mb) is lost every time a part is
1889 written. So, if you run several jobs each after another, you could set
1890 this directive to {\bf no} for all jobs, except the last one, to avoid
1891 wasting too much space, but to ensure that the data is written to the
1892 medium when all jobs are finished.
1894 This directive is ignored with tape and FIFO devices.
1898 The following is an example of a valid Job resource definition:
1905 Level = Incremental # default
1907 FileSet="Minou Full Set"
1910 Schedule = "MinouWeeklyCycle"
1916 \section{The JobDefs Resource}
1917 \label{JobDefsResource}
1918 \index[general]{JobDefs Resource}
1919 \index[general]{Resource!JobDefs}
1921 The JobDefs resource permits all the same directives that can appear in a Job
1922 resource. However, a JobDefs resource does not create a Job, rather it can be
1923 referenced within a Job to provide defaults for that Job. This permits you to
1924 concisely define several nearly identical Jobs, each one referencing a JobDefs
1925 resource which contains the defaults. Only the changes from the defaults need to
1926 be mentioned in each Job.
1928 \section{The Schedule Resource}
1929 \label{ScheduleResource}
1930 \index[general]{Resource!Schedule}
1931 \index[general]{Schedule Resource}
1933 The Schedule resource provides a means of automatically scheduling a Job as
1934 well as the ability to override the default Level, Pool, Storage and Messages
1935 resources. If a Schedule resource is not referenced in a Job, the Job can only
1936 be run manually. In general, you specify an action to be taken and when.
1941 \index[dir]{Schedule}
1942 \index[dir]{Directive!Schedule}
1943 Start of the Schedule directives. No {\bf Schedule} resource is
1944 required, but you will need at least one if you want Jobs to be
1945 automatically started.
1947 \item [Name = \lt{}name\gt{}]
1949 \index[dir]{Directive!Name}
1950 The name of the schedule being defined. The Name directive is required.
1952 \item [Run = \lt{}Job-overrides\gt{} \lt{}Date-time-specification\gt{}]
1954 \index[dir]{Directive!Run}
1955 The Run directive defines when a Job is to be run, and what overrides if
1956 any to apply. You may specify multiple {\bf run} directives within a
1957 {\bf Schedule} resource. If you do, they will all be applied (i.e.
1958 multiple schedules). If you have two {\bf Run} directives that start at
1959 the same time, two Jobs will start at the same time (well, within one
1960 second of each other).
1962 The {\bf Job-overrides} permit overriding the Level, the Storage, the
1963 Messages, and the Pool specifications provided in the Job resource. In
1964 addition, the FullPool, the IncrementalPool, and the DifferentialPool
1965 specifications permit overriding the Pool specification according to
1966 what backup Job Level is in effect.
1968 By the use of overrides, you may customize a particular Job. For
1969 example, you may specify a Messages override for your Incremental
1970 backups that outputs messages to a log file, but for your weekly or
1971 monthly Full backups, you may send the output by email by using a
1972 different Messages override.
1974 {\bf Job-overrides} are specified as: {\bf keyword=value} where the
1975 keyword is Level, Storage, Messages, Pool, FullPool, DifferentialPool,
1976 or IncrementalPool, and the {\bf value} is as defined on the respective
1977 directive formats for the Job resource. You may specify multiple {\bf
1978 Job-overrides} on one {\bf Run} directive by separating them with one or
1979 more spaces or by separating them with a trailing comma. For example:
1985 \index[dir]{Directive!Level}
1986 is all files in the FileSet whether or not they have changed.
1988 \item [Level=Incremental]
1990 \index[dir]{Directive!Level}
1991 is all files that have changed since the last backup.
1995 \index[dir]{Directive!Pool}
1996 specifies to use the Pool named {\bf Weekly}.
1998 \item [Storage=DLT\_Drive]
1999 \index[dir]{Storage}
2000 \index[dir]{Directive!Storage}
2001 specifies to use {\bf DLT\_Drive} for the storage device.
2003 \item [Messages=Verbose]
2004 \index[dir]{Messages}
2005 \index[dir]{Directive!Messages}
2006 specifies to use the {\bf Verbose} message resource for the Job.
2008 \item [FullPool=Full]
2009 \index[dir]{FullPool}
2010 \index[dir]{Directive!FullPool}
2011 specifies to use the Pool named {\bf Full} if the job is a full backup, or
2013 upgraded from another type to a full backup.
2015 \item [DifferentialPool=Differential]
2016 \index[dir]{DifferentialPool}
2017 \index[dir]{Directive!DifferentialPool}
2018 specifies to use the Pool named {\bf Differential} if the job is a
2019 differential backup.
2021 \item [IncrementalPool=Incremental]
2022 \index[dir]{IncrementalPool}
2023 \index[dir]{Directive!IncrementalPool}
2024 specifies to use the Pool named {\bf Incremental} if the job is an
2028 \item [Accurate=yes\vb{}no]
2029 \index[dir]{Accurate}
2030 \index[dir]{Directive!Accurate}
2031 tells Bacula to use or not the Accurate code for the specific job. It can
2032 allow you to save memory and and CPU resources on the catalog server in some
2036 \item [WritePartAfterJob=yes\vb{}no]
2037 \index[dir]{WritePartAfterJob}
2038 \index[dir]{Directive!WritePartAfterJob}
2039 tells Bacula to request the Storage daemon to write the current part
2040 file to the device when the job is finished (see \ilink{Write Part After
2041 Job directive in the Job resource}{WritePartAfterJob}). Please note,
2042 this directive is implemented only in version 1.37 and later. The
2043 default is yes. We strongly recommend that you keep this set to yes
2044 otherwise, when the last job has finished one part will remain in the
2045 spool file and restore may or may not work.
2049 {\bf Date-time-specification} determines when the Job is to be run. The
2050 specification is a repetition, and as a default Bacula is set to run a job at
2051 the beginning of the hour of every hour of every day of every week of every
2052 month of every year. This is not normally what you want, so you must specify
2053 or limit when you want the job to run. Any specification given is assumed to
2054 be repetitive in nature and will serve to override or limit the default
2055 repetition. This is done by specifying masks or times for the hour, day of the
2056 month, day of the week, week of the month, week of the year, and month when
2057 you want the job to run. By specifying one or more of the above, you can
2058 define a schedule to repeat at almost any frequency you want.
2060 Basically, you must supply a {\bf month}, {\bf day}, {\bf hour}, and {\bf
2061 minute} the Job is to be run. Of these four items to be specified, {\bf day}
2062 is special in that you may either specify a day of the month such as 1, 2,
2063 ... 31, or you may specify a day of the week such as Monday, Tuesday, ...
2064 Sunday. Finally, you may also specify a week qualifier to restrict the
2065 schedule to the first, second, third, fourth, or fifth week of the month.
2067 For example, if you specify only a day of the week, such as {\bf Tuesday} the
2068 Job will be run every hour of every Tuesday of every Month. That is the {\bf
2069 month} and {\bf hour} remain set to the defaults of every month and all
2072 Note, by default with no other specification, your job will run at the
2073 beginning of every hour. If you wish your job to run more than once in any
2074 given hour, you will need to specify multiple {\bf run} specifications each
2075 with a different minute.
2077 The date/time to run the Job can be specified in the following way in
2084 <week-keyword> = 1st | 2nd | 3rd | 4th | 5th | first |
2085 second | third | fourth | fifth
2086 <wday-keyword> = sun | mon | tue | wed | thu | fri | sat |
2087 sunday | monday | tuesday | wednesday |
2088 thursday | friday | saturday
2089 <week-of-year-keyword> = w00 | w01 | ... w52 | w53
2090 <month-keyword> = jan | feb | mar | apr | may | jun | jul |
2091 aug | sep | oct | nov | dec | january |
2092 february | ... | december
2093 <daily-keyword> = daily
2094 <weekly-keyword> = weekly
2095 <monthly-keyword> = monthly
2096 <hourly-keyword> = hourly
2097 <digit> = 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0
2098 <number> = <digit> | <digit><number>
2099 <12hour> = 0 | 1 | 2 | ... 12
2100 <hour> = 0 | 1 | 2 | ... 23
2101 <minute> = 0 | 1 | 2 | ... 59
2102 <day> = 1 | 2 | ... 31
2103 <time> = <hour>:<minute> |
2104 <12hour>:<minute>am |
2106 <time-spec> = <at-keyword> <time> |
2108 <date-keyword> = <void-keyword> <weekly-keyword>
2109 <day-range> = <day>-<day>
2110 <month-range> = <month-keyword>-<month-keyword>
2111 <wday-range> = <wday-keyword>-<wday-keyword>
2112 <range> = <day-range> | <month-range> |
2114 <date> = <date-keyword> | <day> | <range>
2115 <date-spec> = <date> | <date-spec>
2116 <day-spec> = <day> | <wday-keyword> |
2117 <day> | <wday-range> |
2118 <week-keyword> <wday-keyword> |
2119 <week-keyword> <wday-range> |
2121 <month-spec> = <month-keyword> | <month-range> |
2123 <date-time-spec> = <month-spec> <day-spec> <time-spec>
2129 Note, the Week of Year specification wnn follows the ISO standard definition
2130 of the week of the year, where Week 1 is the week in which the first Thursday
2131 of the year occurs, or alternatively, the week which contains the 4th of
2132 January. Weeks are numbered w01 to w53. w00 for Bacula is the week that
2133 precedes the first ISO week (i.e. has the first few days of the year if any
2134 occur before Thursday). w00 is not defined by the ISO specification. A week
2135 starts with Monday and ends with Sunday.
2137 According to the NIST (US National Institute of Standards and Technology),
2138 12am and 12pm are ambiguous and can be defined to anything. However,
2139 12:01am is the same as 00:01 and 12:01pm is the same as 12:01, so Bacula
2140 defines 12am as 00:00 (midnight) and 12pm as 12:00 (noon). You can avoid
2141 this abiguity (confusion) by using 24 hour time specifications (i.e. no
2142 am/pm). This is the definition in Bacula version 2.0.3 and later.
2144 An example schedule resource that is named {\bf WeeklyCycle} and runs a job
2145 with level full each Sunday at 2:05am and an incremental job Monday through
2146 Saturday at 2:05am is:
2151 Name = "WeeklyCycle"
2152 Run = Level=Full sun at 2:05
2153 Run = Level=Incremental mon-sat at 2:05
2158 An example of a possible monthly cycle is as follows:
2163 Name = "MonthlyCycle"
2164 Run = Level=Full Pool=Monthly 1st sun at 2:05
2165 Run = Level=Differential 2nd-5th sun at 2:05
2166 Run = Level=Incremental Pool=Daily mon-sat at 2:05
2171 The first of every month:
2177 Run = Level=Full on 1 at 2:05
2178 Run = Level=Incremental on 2-31 at 2:05
2189 Run = Level=Full hourly at 0:05
2190 Run = Level=Full hourly at 0:15
2191 Run = Level=Full hourly at 0:25
2192 Run = Level=Full hourly at 0:35
2193 Run = Level=Full hourly at 0:45
2194 Run = Level=Full hourly at 0:55
2199 \section{Technical Notes on Schedules}
2200 \index[general]{Schedules!Technical Notes on}
2201 \index[general]{Technical Notes on Schedules}
2203 Internally Bacula keeps a schedule as a bit mask. There are six masks and a
2204 minute field to each schedule. The masks are hour, day of the month (mday),
2205 month, day of the week (wday), week of the month (wom), and week of the year
2206 (woy). The schedule is initialized to have the bits of each of these masks
2207 set, which means that at the beginning of every hour, the job will run. When
2208 you specify a month for the first time, the mask will be cleared and the bit
2209 corresponding to your selected month will be selected. If you specify a second
2210 month, the bit corresponding to it will also be added to the mask. Thus when
2211 Bacula checks the masks to see if the bits are set corresponding to the
2212 current time, your job will run only in the two months you have set. Likewise,
2213 if you set a time (hour), the hour mask will be cleared, and the hour you
2214 specify will be set in the bit mask and the minutes will be stored in the
2217 For any schedule you have defined, you can see how these bits are set by doing
2218 a {\bf show schedules} command in the Console program. Please note that the
2219 bit mask is zero based, and Sunday is the first day of the week (bit zero).
2223 \section{The Client Resource}
2224 \label{ClientResource2}
2225 \index[general]{Resource!Client}
2226 \index[general]{Client Resource}
2228 The Client resource defines the attributes of the Clients that are served by
2229 this Director; that is the machines that are to be backed up. You will need
2230 one Client resource definition for each machine to be backed up.
2234 \item [Client (or FileDaemon)]
2235 \index[dir]{Client (or FileDaemon)}
2236 \index[dir]{Directive!Client (or FileDaemon)}
2237 Start of the Client directives.
2239 \item [Name = \lt{}name\gt{}]
2241 \index[dir]{Directive!Name}
2242 The client name which will be used in the Job resource directive or in the
2243 console run command. This directive is required.
2245 \item [Address = \lt{}address\gt{}]
2246 \index[dir]{Address}
2247 \index[dir]{Directive!FD Address}
2248 \index[dir]{File Daemon Address}
2249 \index[dir]{Client Address}
2250 Where the address is a host name, a fully qualified domain name, or a
2251 network address in dotted quad notation for a Bacula File server daemon.
2252 This directive is required.
2254 \item [FD Port = \lt{}port-number\gt{}]
2255 \index[dir]{FD Port}
2256 \index[dir]{Directive!FD Port}
2257 Where the port is a port number at which the Bacula File server daemon can
2258 be contacted. The default is 9102.
2260 \item [Catalog = \lt{}Catalog-resource-name\gt{}]
2261 \index[dir]{Catalog}
2262 \index[dir]{Directive!Catalog}
2263 This specifies the name of the catalog resource to be used for this Client.
2264 This directive is required.
2266 \item [Password = \lt{}password\gt{}]
2267 \index[dir]{Password}
2268 \index[dir]{Directive!Password}
2269 This is the password to be used when establishing a connection with the File
2270 services, so the Client configuration file on the machine to be backed up
2271 must have the same password defined for this Director. This directive is
2272 required. If you have either {\bf /dev/random} {\bf bc} on your machine,
2273 Bacula will generate a random password during the configuration process,
2274 otherwise it will be left blank.
2276 The password is plain text. It is not generated through any special
2277 process, but it is preferable for security reasons to make the text
2280 \label{FileRetention}
2281 \item [File Retention = \lt{}time-period-specification\gt{}]
2282 \label{FileRetention}
2283 \index[dir]{File Retention}
2284 \index[dir]{Directive!File Retention}
2285 The File Retention directive defines the length of time that Bacula will
2286 keep File records in the Catalog database after the End time of the
2287 Job corresponding to the File records.
2288 When this time period expires, and if
2289 {\bf AutoPrune} is set to {\bf yes} Bacula will prune (remove) File records
2290 that are older than the specified File Retention period. Note, this affects
2291 only records in the catalog database. It does not affect your archive
2294 File records may actually be retained for a shorter period than you specify
2295 on this directive if you specify either a shorter {\bf Job Retention} or a
2296 shorter {\bf Volume Retention} period. The shortest retention period of the
2297 three takes precedence. The time may be expressed in seconds, minutes,
2298 hours, days, weeks, months, quarters, or years. See the
2299 \ilink{ Configuration chapter}{Time} of this manual for
2300 additional details of time specification.
2302 The default is 60 days.
2304 \label{JobRetention}
2305 \item [Job Retention = \lt{}time-period-specification\gt{}]
2306 \label{JobRetention}
2307 \index[dir]{Job Retention}
2308 \index[dir]{Directive!Job Retention}
2309 The Job Retention directive defines the length of time that Bacula will keep
2310 Job records in the Catalog database after the Job End time. When
2311 this time period expires, and if {\bf AutoPrune} is set to {\bf yes}
2312 Bacula will prune (remove) Job records that are older than the specified
2313 File Retention period. As with the other retention periods, this
2314 affects only records in the catalog and not data in your archive backup.
2316 If a Job record is selected for pruning, all associated File and JobMedia
2317 records will also be pruned regardless of the File Retention period set.
2318 As a consequence, you normally will set the File retention period to be
2319 less than the Job retention period. The Job retention period can actually
2320 be less than the value you specify here if you set the {\bf Volume
2321 Retention} directive in the Pool resource to a smaller duration. This is
2322 because the Job retention period and the Volume retention period are
2323 independently applied, so the smaller of the two takes precedence.
2325 The Job retention period is specified as seconds, minutes, hours, days,
2326 weeks, months, quarters, or years. See the
2327 \ilink{ Configuration chapter}{Time} of this manual for
2328 additional details of time specification.
2330 The default is 180 days.
2333 \item [AutoPrune = \lt{}yes\vb{}no\gt{}]
2334 \index[dir]{AutoPrune}
2335 \index[dir]{Directive!AutoPrune}
2336 If AutoPrune is set to {\bf yes} (default), Bacula (version 1.20 or greater)
2337 will automatically apply the File retention period and the Job retention
2338 period for the Client at the end of the Job. If you set {\bf AutoPrune = no},
2339 pruning will not be done, and your Catalog will grow in size each time you
2340 run a Job. Pruning affects only information in the catalog and not data
2341 stored in the backup archives (on Volumes).
2343 \item [Maximum Concurrent Jobs = \lt{}number\gt{}]
2344 \index[dir]{Maximum Concurrent Jobs}
2345 \index[dir]{Directive!Maximum Concurrent Jobs}
2346 where \lt{}number\gt{} is the maximum number of Jobs with the current Client
2347 that can run concurrently. Note, this directive limits only Jobs for Clients
2348 with the same name as the resource in which it appears. Any other
2349 restrictions on the maximum concurrent jobs such as in the Director, Job, or
2350 Storage resources will also apply in addition to any limit specified here.
2351 The default is set to 1, but you may set it to a larger number.
2353 \item [Maximum Bandwidth Per Job = \lt{}speed\gt{}]
2354 \index[dir]{Maximum Bandwidth Per Job}
2355 \index[dir]{Directive!Maximum Bandwidth Per Job}
2357 The speed parameter specifies the maximum allowed bandwidth that a job may use
2358 when started for this Client. The speed parameter should be specified in
2359 k/s, Kb/s, m/s or Mb/s.
2361 \item [Priority = \lt{}number\gt{}]
2362 \index[dir]{Priority}
2363 \index[dir]{Directive!Priority}
2364 The number specifies the priority of this client relative to other clients
2365 that the Director is processing simultaneously. The priority can range from
2366 1 to 1000. The clients are ordered such that the smaller number priorities
2367 are performed first (not currently implemented).
2370 The following is an example of a valid Client resource definition:
2376 FDAddress = minimatou
2378 Password = very_good
2383 \section{The Storage Resource}
2384 \label{StorageResource2}
2385 \index[general]{Resource!Storage}
2386 \index[general]{Storage Resource}
2388 The Storage resource defines which Storage daemons are available for use by
2394 \index[dir]{Storage}
2395 \index[dir]{Directive!Storage}
2396 Start of the Storage resources. At least one storage resource must be
2399 \item [Name = \lt{}name\gt{}]
2401 \index[dir]{Directive!Name}
2402 The name of the storage resource. This name appears on the Storage directive
2403 specified in the Job resource and is required.
2405 \item [Address = \lt{}address\gt{}]
2406 \index[dir]{Address}
2407 \index[dir]{Directive!SD Address}
2408 \index[dir]{Storage daemon Address}
2409 Where the address is a host name, a {\bf fully qualified domain name}, or an
2410 {\bf IP address}. Please note that the \lt{}address\gt{} as specified here
2411 will be transmitted to the File daemon who will then use it to contact the
2412 Storage daemon. Hence, it is {\bf not}, a good idea to use {\bf localhost} as
2413 the name but rather a fully qualified machine name or an IP address. This
2414 directive is required.
2416 \item [SD Port = \lt{}port\gt{}]
2417 \index[dir]{SD Port}
2418 \index[dir]{Directive!SD Port}
2419 Where port is the port to use to contact the storage daemon for information
2420 and to start jobs. This same port number must appear in the Storage resource
2421 of the Storage daemon's configuration file. The default is 9103.
2423 \item [Password = \lt{}password\gt{}]
2424 \index[dir]{Password}
2425 \index[dir]{Directive!Password}
2426 This is the password to be used when establishing a connection with the
2427 Storage services. This same password also must appear in the Director
2428 resource of the Storage daemon's configuration file. This directive is
2429 required. If you have either {\bf /dev/random} {\bf bc} on your machine,
2430 Bacula will generate a random password during the configuration process,
2431 otherwise it will be left blank.
2433 The password is plain text. It is not generated through any special
2434 process, but it is preferable for security reasons to use random text.
2436 \item [Device = \lt{}device-name\gt{}]
2438 \index[dir]{Directive!Device}
2439 This directive specifies the Storage daemon's name of the device
2440 resource to be used for the storage. If you are using an Autochanger,
2441 the name specified here should be the name of the Storage daemon's
2442 Autochanger resource rather than the name of an individual device. This
2443 name is not the physical device name, but the logical device name as
2444 defined on the {\bf Name} directive contained in the {\bf Device} or the
2445 {\bf Autochanger} resource definition of the {\bf Storage daemon}
2446 configuration file. You can specify any name you would like (even the
2447 device name if you prefer) up to a maximum of 127 characters in length.
2448 The physical device name associated with this device is specified in the
2449 {\bf Storage daemon} configuration file (as {\bf Archive Device}).
2450 Please take care not to define two different Storage resource directives
2451 in the Director that point to the same Device in the Storage daemon.
2452 Doing so may cause the Storage daemon to block (or hang) attempting to
2453 open the same device that is already open. This directive is required.
2456 \item [Media Type = \lt{}MediaType\gt{}]
2457 \index[dir]{Media Type}
2458 \index[dir]{Directive!Media Type}
2459 This directive specifies the Media Type to be used to store the data.
2460 This is an arbitrary string of characters up to 127 maximum that you
2461 define. It can be anything you want. However, it is best to make it
2462 descriptive of the storage media (e.g. File, DAT, "HP DLT8000", 8mm,
2463 ...). In addition, it is essential that you make the {\bf Media Type}
2464 specification unique for each storage media type. If you have two DDS-4
2465 drives that have incompatible formats, or if you have a DDS-4 drive and
2466 a DDS-4 autochanger, you almost certainly should specify different {\bf
2467 Media Types}. During a restore, assuming a {\bf DDS-4} Media Type is
2468 associated with the Job, Bacula can decide to use any Storage daemon
2469 that supports Media Type {\bf DDS-4} and on any drive that supports it.
2471 If you are writing to disk Volumes, you must make doubly sure that each
2472 Device resource defined in the Storage daemon (and hence in the
2473 Director's conf file) has a unique media type. Otherwise for Bacula
2474 versions 1.38 and older, your restores may not work because Bacula
2475 will assume that you can mount any Media Type with the same name on
2476 any Device associated with that Media Type. This is possible with
2477 tape drives, but with disk drives, unless you are very clever you
2478 cannot mount a Volume in any directory -- this can be done by creating
2479 an appropriate soft link.
2481 Currently Bacula permits only a single Media Type per Storage
2482 and Device definition. Consequently, if
2483 you have a drive that supports more than one Media Type, you can
2484 give a unique string to Volumes with different intrinsic Media
2485 Type (Media Type = DDS-3-4 for DDS-3 and DDS-4 types), but then
2486 those volumes will only be mounted on drives indicated with the
2487 dual type (DDS-3-4).
2489 If you want to tie Bacula to using a single Storage daemon or drive, you
2490 must specify a unique Media Type for that drive. This is an important
2491 point that should be carefully understood. Note, this applies equally
2492 to Disk Volumes. If you define more than one disk Device resource in
2493 your Storage daemon's conf file, the Volumes on those two devices are in
2494 fact incompatible because one can not be mounted on the other device
2495 since they are found in different directories. For this reason, you
2496 probably should use two different Media Types for your two disk Devices
2497 (even though you might think of them as both being File types). You can
2498 find more on this subject in the \ilink{Basic Volume
2499 Management}{DiskChapter} chapter of this manual.
2501 The {\bf MediaType} specified in the Director's Storage resource, {\bf
2502 must} correspond to the {\bf Media Type} specified in the {\bf Device}
2503 resource of the {\bf Storage daemon} configuration file. This directive
2504 is required, and it is used by the Director and the Storage daemon to
2505 ensure that a Volume automatically selected from the Pool corresponds to
2506 the physical device. If a Storage daemon handles multiple devices (e.g.
2507 will write to various file Volumes on different partitions), this
2508 directive allows you to specify exactly which device.
2510 As mentioned above, the value specified in the Director's Storage
2511 resource must agree with the value specified in the Device resource in
2512 the {\bf Storage daemon's} configuration file. It is also an additional
2513 check so that you don't try to write data for a DLT onto an 8mm device.
2515 \label{Autochanger1}
2516 \item [Autochanger = \lt{}yes\vb{}no\gt{}]
2517 \index[dir]{Autochanger}
2518 \index[dir]{Directive!Autochanger}
2519 If you specify {\bf yes} for this command (the default is {\bf no}),
2520 when you use the {\bf label} command or the {\bf add} command to create
2521 a new Volume, {\bf Bacula} will also request the Autochanger Slot
2522 number. This simplifies creating database entries for Volumes in an
2523 autochanger. If you forget to specify the Slot, the autochanger will
2524 not be used. However, you may modify the Slot associated with a Volume
2525 at any time by using the {\bf update volume} or {\bf update slots}
2526 command in the console program. When {\bf autochanger} is enabled, the
2527 algorithm used by Bacula to search for available volumes will be
2528 modified to consider only Volumes that are known to be in the
2529 autochanger's magazine. If no {\bf in changer} volume is found, Bacula
2530 will attempt recycling, pruning, ..., and if still no volume is found,
2531 Bacula will search for any volume whether or not in the magazine. By
2532 privileging in changer volumes, this procedure minimizes operator
2533 intervention. The default is {\bf no}.
2535 For the autochanger to be used, you must also specify {\bf Autochanger =
2536 yes} in the \ilink{Device Resource}{Autochanger} in the Storage daemon's
2537 configuration file as well as other important Storage daemon
2538 configuration information. Please consult the \ilink{Using
2539 Autochangers}{AutochangersChapter} manual of this chapter for the
2540 details of using autochangers.
2542 \item [Maximum Concurrent Jobs = \lt{}number\gt{}]
2543 \index[dir]{Maximum Concurrent Jobs}
2544 \index[dir]{Directive!Maximum Concurrent Jobs}
2545 where \lt{}number\gt{} is the maximum number of Jobs with the current
2546 Storage resource that can run concurrently. Note, this directive limits
2547 only Jobs for Jobs using this Storage daemon. Any other restrictions on
2548 the maximum concurrent jobs such as in the Director, Job, or Client
2549 resources will also apply in addition to any limit specified here. The
2550 default is set to 1, but you may set it to a larger number. However, if
2551 you set the Storage daemon's number of concurrent jobs greater than one,
2552 we recommend that you read the waring documented under \ilink{Maximum
2553 Concurrent Jobs}{DirMaxConJobs} in the Director's resource or simply
2554 turn data spooling on as documented in the \ilink{Data
2555 Spooling}{SpoolingChapter} chapter of this manual.
2557 \item [AllowCompression = \lt{}yes\vb{}no\gt{}]
2558 \label{AllowCompression}
2559 \index[dir]{AllowCompression}
2560 \index[dir]{Directive!AllowCompression}
2562 This directive is optional, and if you specify {\bf No} (the default is {\bf
2563 Yes}), it will cause backups jobs running on this storage resource to run
2564 without client File Daemon compression. This effectively overrides
2565 compression options in FileSets used by jobs which use this storage
2568 \item [Heartbeat Interval = \lt{}time-interval\gt{}]
2569 \index[dir]{Heartbeat Interval}
2570 \index[dir]{Directive!Heartbeat}
2571 This directive is optional and if specified will cause the Director to
2572 set a keepalive interval (heartbeat) in seconds on each of the sockets
2573 it opens for the Storage resource. This value will override any
2574 specified at the Director level. It is implemented only on systems
2575 (Linux, ...) that provide the {\bf setsockopt} TCP\_KEEPIDLE function.
2576 The default value is zero, which means no change is made to the socket.
2580 The following is an example of a valid Storage resource definition:
2584 # Definition of tape storage device
2588 Password = storage_password # password for Storage daemon
2589 Device = "HP DLT 80" # same as Device in Storage daemon
2590 Media Type = DLT8000 # same as MediaType in Storage daemon
2595 \section{The Pool Resource}
2596 \label{PoolResource}
2597 \index[general]{Resource!Pool}
2598 \index[general]{Pool Resource}
2600 The Pool resource defines the set of storage Volumes (tapes or files) to be
2601 used by Bacula to write the data. By configuring different Pools, you can
2602 determine which set of Volumes (media) receives the backup data. This permits,
2603 for example, to store all full backup data on one set of Volumes and all
2604 incremental backups on another set of Volumes. Alternatively, you could assign
2605 a different set of Volumes to each machine that you backup. This is most
2606 easily done by defining multiple Pools.
2608 Another important aspect of a Pool is that it contains the default attributes
2609 (Maximum Jobs, Retention Period, Recycle flag, ...) that will be given to a
2610 Volume when it is created. This avoids the need for you to answer a large
2611 number of questions when labeling a new Volume. Each of these attributes can
2612 later be changed on a Volume by Volume basis using the {\bf update} command in
2613 the console program. Note that you must explicitly specify which Pool Bacula
2614 is to use with each Job. Bacula will not automatically search for the correct
2617 Most often in Bacula installations all backups for all machines (Clients) go
2618 to a single set of Volumes. In this case, you will probably only use the {\bf
2619 Default} Pool. If your backup strategy calls for you to mount a different tape
2620 each day, you will probably want to define a separate Pool for each day. For
2621 more information on this subject, please see the
2622 \ilink{Backup Strategies}{StrategiesChapter} chapter of this
2626 To use a Pool, there are three distinct steps. First the Pool must be defined
2627 in the Director's configuration file. Then the Pool must be written to the
2628 Catalog database. This is done automatically by the Director each time that it
2629 starts, or alternatively can be done using the {\bf create} command in the
2630 console program. Finally, if you change the Pool definition in the Director's
2631 configuration file and restart Bacula, the pool will be updated alternatively
2632 you can use the {\bf update pool} console command to refresh the database
2633 image. It is this database image rather than the Director's resource image
2634 that is used for the default Volume attributes. Note, for the pool to be
2635 automatically created or updated, it must be explicitly referenced by a Job
2638 Next the physical media must be labeled. The labeling can either be done with
2639 the {\bf label} command in the {\bf console} program or using the {\bf btape}
2640 program. The preferred method is to use the {\bf label} command in the {\bf
2643 Finally, you must add Volume names (and their attributes) to the Pool. For
2644 Volumes to be used by Bacula they must be of the same {\bf Media Type} as the
2645 archive device specified for the job (i.e. if you are going to back up to a
2646 DLT device, the Pool must have DLT volumes defined since 8mm volumes cannot be
2647 mounted on a DLT drive). The {\bf Media Type} has particular importance if you
2648 are backing up to files. When running a Job, you must explicitly specify which
2649 Pool to use. Bacula will then automatically select the next Volume to use from
2650 the Pool, but it will ensure that the {\bf Media Type} of any Volume selected
2651 from the Pool is identical to that required by the Storage resource you have
2652 specified for the Job.
2654 If you use the {\bf label} command in the console program to label the
2655 Volumes, they will automatically be added to the Pool, so this last step is
2656 not normally required.
2658 It is also possible to add Volumes to the database without explicitly labeling
2659 the physical volume. This is done with the {\bf add} console command.
2661 As previously mentioned, each time Bacula starts, it scans all the Pools
2662 associated with each Catalog, and if the database record does not already
2663 exist, it will be created from the Pool Resource definition. {\bf Bacula}
2664 probably should do an {\bf update pool} if you change the Pool definition, but
2665 currently, you must do this manually using the {\bf update pool} command in
2666 the Console program.
2668 The Pool Resource defined in the Director's configuration file
2669 (bacula-dir.conf) may contain the following directives:
2675 \index[dir]{Directive!Pool}
2676 Start of the Pool resource. There must be at least one Pool resource
2680 \item [Name = \lt{}name\gt{}]
2682 \index[dir]{Directive!Name}
2683 The name of the pool. For most applications, you will use the default
2684 pool name {\bf Default}. This directive is required.
2687 \item [Maximum Volumes = \lt{}number\gt{}]
2688 \index[dir]{Maximum Volumes}
2689 \index[dir]{Directive!Maximum Volumes}
2690 This directive specifies the maximum number of volumes (tapes or files)
2691 contained in the pool. This directive is optional, if omitted or set to
2692 zero, any number of volumes will be permitted. In general, this
2693 directive is useful for Autochangers where there is a fixed number of
2694 Volumes, or for File storage where you wish to ensure that the backups
2695 made to disk files do not become too numerous or consume too much space.
2697 \item [Pool Type = \lt{}type\gt{}]
2698 \index[dir]{Pool Type}
2699 \index[dir]{Directive!Pool Type}
2700 This directive defines the pool type, which corresponds to the type of
2701 Job being run. It is required and may be one of the following:
2711 Note, only Backup is current implemented.
2713 \item [Storage = \lt{}storage-resource-name\gt{}]
2714 \index[dir]{Storage}
2715 \index[dir]{Directive!Storage}
2716 The Storage directive defines the name of the storage services where you
2717 want to backup the FileSet data. For additional details, see the
2718 \ilink{Storage Resource Chapter}{StorageResource2} of this manual.
2719 The Storage resource may also be specified in the Job resource,
2720 but the value, if any, in the Pool resource overrides any value
2721 in the Job. This Storage resource definition is not required by either
2722 the Job resource or in the Pool, but it must be specified in
2723 one or the other. If not configuration error will result.
2725 \item [Use Volume Once = \lt{}yes\vb{}no\gt{}]
2726 \index[dir]{Use Volume Once}
2727 \index[dir]{Directive!Use Volume Once}
2728 This directive if set to {\bf yes} specifies that each volume is to be
2729 used only once. This is most useful when the Media is a file and you
2730 want a new file for each backup that is done. The default is {\bf no}
2731 (i.e. use volume any number of times). This directive will most likely
2732 be phased out (deprecated), so you are recommended to use {\bf Maximum
2733 Volume Jobs = 1} instead.
2735 The value defined by this directive in the bacula-dir.conf file is the
2736 default value used when a Volume is created. Once the volume is
2737 created, changing the value in the bacula-dir.conf file will not change
2738 what is stored for the Volume. To change the value for an existing
2739 Volume you must use the {\bf update} command in the Console.
2741 Please see the notes below under {\bf Maximum Volume Jobs} concerning
2742 using this directive with multiple simultaneous jobs.
2744 \item [Maximum Volume Jobs = \lt{}positive-integer\gt{}]
2745 \index[dir]{Maximum Volume Jobs}
2746 \index[dir]{Directive!Maximum Volume Jobs}
2747 This directive specifies the maximum number of Jobs that can be written
2748 to the Volume. If you specify zero (the default), there is no limit.
2749 Otherwise, when the number of Jobs backed up to the Volume equals {\bf
2750 positive-integer} the Volume will be marked {\bf Used}. When the Volume
2751 is marked {\bf Used} it can no longer be used for appending Jobs, much
2752 like the {\bf Full} status but it can be recycled if recycling is
2753 enabled, and thus used again. By setting {\bf MaximumVolumeJobs} to
2754 one, you get the same effect as setting {\bf UseVolumeOnce = yes}.
2756 The value defined by this directive in the bacula-dir.conf
2757 file is the default value used when a Volume is created. Once the volume is
2758 created, changing the value in the bacula-dir.conf file will not change what
2759 is stored for the Volume. To change the value for an existing Volume you
2760 must use the {\bf update} command in the Console.
2762 If you are running multiple simultaneous jobs, this directive may not
2763 work correctly because when a drive is reserved for a job, this
2764 directive is not taken into account, so multiple jobs may try to
2765 start writing to the Volume. At some point, when the Media record is
2766 updated, multiple simultaneous jobs may fail since the Volume can no
2769 \item [Maximum Volume Files = \lt{}positive-integer\gt{}]
2770 \index[dir]{Maximum Volume Files}
2771 \index[dir]{Directive!Maximum Volume Files}
2772 This directive specifies the maximum number of files that can be written
2773 to the Volume. If you specify zero (the default), there is no limit.
2774 Otherwise, when the number of files written to the Volume equals {\bf
2775 positive-integer} the Volume will be marked {\bf Used}. When the Volume
2776 is marked {\bf Used} it can no longer be used for appending Jobs, much
2777 like the {\bf Full} status but it can be recycled if recycling is
2778 enabled and thus used again. This value is checked and the {\bf Used}
2779 status is set only at the end of a job that writes to the particular
2782 The value defined by this directive in the bacula-dir.conf file is the
2783 default value used when a Volume is created. Once the volume is
2784 created, changing the value in the bacula-dir.conf file will not change
2785 what is stored for the Volume. To change the value for an existing
2786 Volume you must use the {\bf update} command in the Console.
2788 \item [Maximum Volume Bytes = \lt{}size\gt{}]
2789 \index[dir]{Maximum Volume Bytes}
2790 \index[dir]{Directive!Maximum Volume Bytes}
2791 This directive specifies the maximum number of bytes that can be written
2792 to the Volume. If you specify zero (the default), there is no limit
2793 except the physical size of the Volume. Otherwise, when the number of
2794 bytes written to the Volume equals {\bf size} the Volume will be marked
2795 {\bf Used}. When the Volume is marked {\bf Used} it can no longer be
2796 used for appending Jobs, much like the {\bf Full} status but it can be
2797 recycled if recycling is enabled, and thus the Volume can be re-used
2798 after recycling. This value is checked and the {\bf Used} status set
2799 while the job is writing to the particular volume.
2801 This directive is particularly useful for restricting the size
2802 of disk volumes, and will work correctly even in the case of
2803 multiple simultaneous jobs writing to the volume.
2805 The value defined by this directive in the bacula-dir.conf file is the
2806 default value used when a Volume is created. Once the volume is
2807 created, changing the value in the bacula-dir.conf file will not change
2808 what is stored for the Volume. To change the value for an existing
2809 Volume you must use the {\bf update} command in the Console.
2811 \item [Volume Use Duration = \lt{}time-period-specification\gt{}]
2812 \index[dir]{Volume Use Duration}
2813 \index[dir]{Directive!Volume Use Duration}
2814 The Volume Use Duration directive defines the time period that the
2815 Volume can be written beginning from the time of first data write to the
2816 Volume. If the time-period specified is zero (the default), the Volume
2817 can be written indefinitely. Otherwise, the next time a job
2818 runs that wants to access this Volume, and the time period from the
2819 first write to the volume (the first Job written) exceeds the
2820 time-period-specification, the Volume will be marked {\bf Used}, which
2821 means that no more Jobs can be appended to the Volume, but it may be
2822 recycled if recycling is enabled. Using the command {\bf
2823 status dir} applies algorithms similar to running jobs, so
2824 during such a command, the Volume status may also be changed.
2826 recycled, it will be available for use again.
2828 You might use this directive, for example, if you have a Volume used for
2829 Incremental backups, and Volumes used for Weekly Full backups. Once the
2830 Full backup is done, you will want to use a different Incremental
2831 Volume. This can be accomplished by setting the Volume Use Duration for
2832 the Incremental Volume to six days. I.e. it will be used for the 6
2833 days following a Full save, then a different Incremental volume will be
2834 used. Be careful about setting the duration to short periods such as 23
2835 hours, or you might experience problems of Bacula waiting for a tape
2836 over the weekend only to complete the backups Monday morning when an
2837 operator mounts a new tape.
2839 The use duration is checked and the {\bf Used} status is set only at the
2840 end of a job that writes to the particular volume, which means that even
2841 though the use duration may have expired, the catalog entry will not be
2842 updated until the next job that uses this volume is run. This
2843 directive is not intended to be used to limit volume sizes
2844 and will not work correctly (i.e. will fail jobs) if the use
2845 duration expires while multiple simultaneous jobs are writing
2848 Please note that the value defined by this directive in the bacula-dir.conf
2849 file is the default value used when a Volume is created. Once the volume is
2850 created, changing the value in the bacula-dir.conf file will not change what
2851 is stored for the Volume. To change the value for an existing Volume you
2853 \ilink{\bf update volume}{UpdateCommand} command in the Console.
2855 \item [Catalog Files = \lt{}yes\vb{}no\gt{}]
2856 \index[dir]{Catalog Files}
2857 \index[dir]{Directive!Catalog Files}
2858 This directive defines whether or not you want the names of the files
2859 that were saved to be put into the catalog. The default is {\bf yes}.
2860 The advantage of specifying {\bf Catalog Files = No} is that you will
2861 have a significantly smaller Catalog database. The disadvantage is that
2862 you will not be able to produce a Catalog listing of the files backed up
2863 for each Job (this is often called Browsing). Also, without the File
2864 entries in the catalog, you will not be able to use the Console {\bf
2865 restore} command nor any other command that references File entries.
2867 \label{PoolAutoPrune}
2868 \item [AutoPrune = \lt{}yes\vb{}no\gt{}]
2869 \index[dir]{AutoPrune}
2870 \index[dir]{Directive!AutoPrune}
2871 If AutoPrune is set to {\bf yes} (default), Bacula (version 1.20 or
2872 greater) will automatically apply the Volume Retention period when new
2873 Volume is needed and no appendable Volumes exist in the Pool. Volume
2874 pruning causes expired Jobs (older than the {\bf Volume Retention}
2875 period) to be deleted from the Catalog and permits possible recycling of
2878 \label{VolRetention}
2879 \item [Volume Retention = \lt{}time-period-specification\gt{}]
2880 \index[dir]{Volume Retention}
2881 \index[dir]{Directive!Volume Retention}
2882 The Volume Retention directive defines the length of time that {\bf
2883 Bacula} will keep records associated with the Volume in
2884 the Catalog database after the End time of each Job written to the
2885 Volume. When this time period expires, and if {\bf AutoPrune} is set to
2886 {\bf yes} Bacula may prune (remove) Job records that are older than the
2887 specified Volume Retention period if it is necessary to free up a
2888 Volume. Recycling will not occur until it is absolutely necessary to
2889 free up a volume (i.e. no other writable volume exists).
2890 All File records associated with pruned Jobs are also
2891 pruned. The time may be specified as seconds, minutes, hours, days,
2892 weeks, months, quarters, or years. The {\bf Volume Retention} is
2893 applied independently of the {\bf Job Retention} and the {\bf File
2894 Retention} periods defined in the Client resource. This means that all
2895 the retentions periods are applied in turn and that the shorter period
2896 is the one that effectively takes precedence. Note, that when the {\bf
2897 Volume Retention} period has been reached, and it is necessary to obtain
2898 a new volume, Bacula will prune both the Job and the File records. This
2899 pruning could also occur during a {\bf status dir} command because it
2900 uses similar algorithms for finding the next available Volume.
2902 It is important to know that when the Volume Retention period expires,
2903 Bacula does not automatically recycle a Volume. It attempts to keep the
2904 Volume data intact as long as possible before over writing the Volume.
2906 By defining multiple Pools with different Volume Retention periods, you
2907 may effectively have a set of tapes that is recycled weekly, another
2908 Pool of tapes that is recycled monthly and so on. However, one must
2909 keep in mind that if your {\bf Volume Retention} period is too short, it
2910 may prune the last valid Full backup, and hence until the next Full
2911 backup is done, you will not have a complete backup of your system, and
2912 in addition, the next Incremental or Differential backup will be
2913 promoted to a Full backup. As a consequence, the minimum {\bf Volume
2914 Retention} period should be at twice the interval of your Full backups.
2915 This means that if you do a Full backup once a month, the minimum Volume
2916 retention period should be two months.
2918 The default Volume retention period is 365 days, and either the default
2919 or the value defined by this directive in the bacula-dir.conf file is
2920 the default value used when a Volume is created. Once the volume is
2921 created, changing the value in the bacula-dir.conf file will not change
2922 what is stored for the Volume. To change the value for an existing
2923 Volume you must use the {\bf update} command in the Console.
2925 \item [Action On Purge = \lt{Truncate}]
2926 \index[dir]{actiononpurge}
2928 This directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate the
2929 volume when it is purged with the \texttt{purge volume action=truncate}
2930 command. It is useful to prevent disk based volumes from consuming too much
2936 Action On Purge = Truncate
2941 You can schedule the truncate operation at the end of your CatalogBackup job
2942 like in this example:
2946 Name = CatalogBackup
2951 Console = "purge volume action=all allpools storage=File"
2956 \label{PoolScratchPool}
2957 \item [ScratchPool = \lt{}pool-resource-name\gt{}]
2958 \index[dir]{ScrachPool}
2959 \index[dir]{Directive!ScrachPool}
2960 This directive permits to specify a dedicate \textsl{Scratch} for the
2961 current pool. This pool will replace the special pool named \textsl{Scrach}
2962 for volume selection. For more information about \textsl{Scratch} see
2963 \ilink{Scratch Pool}{TheScratchPool} section of this manual. This is useful
2964 when using multiple storage sharing the same mediatype or when you want to
2965 dedicate volumes to a particular set of pool.
2967 \label{PoolRecyclePool}
2968 \item [RecyclePool = \lt{}pool-resource-name\gt{}]
2969 \index[dir]{RecyclePool}
2970 \index[dir]{Directive!RecyclePool}
2971 This directive defines to which pool
2972 the Volume will be placed (moved) when it is recycled. Without
2973 this directive, a Volume will remain in the same pool when it is
2974 recycled. With this directive, it can be moved automatically to any
2975 existing pool during a recycle. This directive is probably most
2976 useful when defined in the Scratch pool, so that volumes will
2977 be recycled back into the Scratch pool. For more on the see the
2978 \ilink{Scratch Pool}{TheScratchPool} section of this manual.
2980 Although this directive is called RecyclePool, the Volume in
2981 question is actually moved from its current pool to the one
2982 you specify on this directive when Bacula prunes the Volume and
2983 discovers that there are no records left in the catalog and hence
2984 marks it as {\bf Purged}.
2988 \item [Recycle = \lt{}yes\vb{}no\gt{}]
2989 \index[dir]{Recycle}
2990 \index[dir]{Directive!Recycle}
2991 This directive specifies whether or not Purged Volumes may be recycled.
2992 If it is set to {\bf yes} (default) and Bacula needs a volume but finds
2993 none that are appendable, it will search for and recycle (reuse) Purged
2994 Volumes (i.e. volumes with all the Jobs and Files expired and thus
2995 deleted from the Catalog). If the Volume is recycled, all previous data
2996 written to that Volume will be overwritten. If Recycle is set to {\bf
2997 no}, the Volume will not be recycled, and hence, the data will remain
2998 valid. If you want to reuse (re-write) the Volume, and the recycle flag
2999 is no (0 in the catalog), you may manually set the recycle flag (update
3000 command) for a Volume to be reused.
3002 Please note that the value defined by this directive in the
3003 bacula-dir.conf file is the default value used when a Volume is created.
3004 Once the volume is created, changing the value in the bacula-dir.conf
3005 file will not change what is stored for the Volume. To change the value
3006 for an existing Volume you must use the {\bf update} command in the
3009 When all Job and File records have been pruned or purged from the
3010 catalog for a particular Volume, if that Volume is marked as
3011 Append, Full, Used, or Error, it will then be marked as Purged. Only
3012 Volumes marked as Purged will be considered to be converted to the
3013 Recycled state if the {\bf Recycle} directive is set to {\bf yes}.
3016 \label{RecycleOldest}
3017 \item [Recycle Oldest Volume = \lt{}yes\vb{}no\gt{}]
3018 \index[dir]{Recycle Oldest Volume}
3019 \index[dir]{Directive!Recycle Oldest Volume}
3020 This directive instructs the Director to search for the oldest used
3021 Volume in the Pool when another Volume is requested by the Storage
3022 daemon and none are available. The catalog is then {\bf pruned}
3023 respecting the retention periods of all Files and Jobs written to this
3024 Volume. If all Jobs are pruned (i.e. the volume is Purged), then the
3025 Volume is recycled and will be used as the next Volume to be written.
3026 This directive respects any Job, File, or Volume retention periods that
3027 you may have specified, and as such it is {\bf much} better to use this
3028 directive than the Purge Oldest Volume.
3030 This directive can be useful if you have a fixed number of Volumes in the
3031 Pool and you want to cycle through them and you have specified the correct
3034 However, if you use this directive and have only one
3035 Volume in the Pool, you will immediately recycle your Volume if you fill
3036 it and Bacula needs another one. Thus your backup will be totally invalid.
3037 Please use this directive with care. The default is {\bf no}.
3039 \label{RecycleCurrent}
3041 \item [Recycle Current Volume = \lt{}yes\vb{}no\gt{}]
3042 \index[dir]{Recycle Current Volume}
3043 \index[dir]{Directive!Recycle Current Volume}
3044 If Bacula needs a new Volume, this directive instructs Bacula to Prune
3045 the volume respecting the Job and File retention periods. If all Jobs
3046 are pruned (i.e. the volume is Purged), then the Volume is recycled and
3047 will be used as the next Volume to be written. This directive respects
3048 any Job, File, or Volume retention periods that you may have specified,
3049 and thus it is {\bf much} better to use it rather than the Purge Oldest
3052 This directive can be useful if you have: a fixed number of Volumes in
3053 the Pool, you want to cycle through them, and you have specified
3054 retention periods that prune Volumes before you have cycled through the
3057 However, if you use this directive and have only one Volume in the Pool,
3058 you will immediately recycle your Volume if you fill it and Bacula needs
3059 another one. Thus your backup will be totally invalid. Please use this
3060 directive with care. The default is {\bf no}.
3064 \item [Purge Oldest Volume = \lt{}yes\vb{}no\gt{}]
3065 \index[dir]{Purge Oldest Volume}
3066 \index[dir]{Directive!Purge Oldest Volume}
3067 This directive instructs the Director to search for the oldest used
3068 Volume in the Pool when another Volume is requested by the Storage
3069 daemon and none are available. The catalog is then {\bf purged}
3070 irrespective of retention periods of all Files and Jobs written to this
3071 Volume. The Volume is then recycled and will be used as the next Volume
3072 to be written. This directive overrides any Job, File, or Volume
3073 retention periods that you may have specified.
3075 This directive can be useful if you have a fixed number of Volumes in
3076 the Pool and you want to cycle through them and reusing the oldest one
3077 when all Volumes are full, but you don't want to worry about setting
3078 proper retention periods. However, by using this option you risk losing
3081 Please be aware that {\bf Purge Oldest Volume} disregards all retention
3082 periods. If you have only a single Volume defined and you turn this
3083 variable on, that Volume will always be immediately overwritten when it
3084 fills! So at a minimum, ensure that you have a decent number of Volumes
3085 in your Pool before running any jobs. If you want retention periods to
3086 apply do not use this directive. To specify a retention period, use the
3087 {\bf Volume Retention} directive (see above).
3089 We {\bf highly} recommend against using this directive, because it is
3090 sure that some day, Bacula will recycle a Volume that contains current
3091 data. The default is {\bf no}.
3093 \item [File Retention = \lt{}time-period-specification\gt{}]
3094 \index[dir]{File Retention}
3095 \index[dir]{Directive!File Retention}
3096 The File Retention directive defines the length of time that Bacula will
3097 keep File records in the Catalog database after the End time of the
3098 Job corresponding to the File records.
3100 This directive takes precedence over Client directives of the same name. For
3101 example, you can decide to increase Retention times for Archive or OffSite
3104 Note, this affects only records in the catalog database. It does not affect
3105 your archive backups.
3107 For more information see Client documentation about
3108 \ilink{FileRetention}{FileRetention}
3110 \item [Job Retention = \lt{}time-period-specification\gt{}]
3111 \index[dir]{Job Retention}
3112 \index[dir]{Directive!Job Retention}
3114 The Job Retention directive defines the length of time that Bacula will keep
3115 Job records in the Catalog database after the Job End time. As with the
3116 other retention periods, this affects only records in the catalog and not
3117 data in your archive backup.
3119 This directive takes precedence over Client directives of the same name.
3120 For example, you can decide to increase Retention times for Archive or
3123 For more information see Client side documentation
3124 \ilink{JobRetention}{JobRetention}
3126 \item [Cleaning Prefix = \lt{}string\gt{}]
3127 \index[dir]{Cleaning Prefix}
3128 \index[dir]{Directive!Cleaning Prefix}
3129 This directive defines a prefix string, which if it matches the
3130 beginning of a Volume name during labeling of a Volume, the Volume will
3131 be defined with the VolStatus set to {\bf Cleaning} and thus Bacula will
3132 never attempt to use this tape. This is primarily for use with
3133 autochangers that accept barcodes where the convention is that barcodes
3134 beginning with {\bf CLN} are treated as cleaning tapes.
3137 \item [Label Format = \lt{}format\gt{}]
3138 \index[dir]{Label Format}
3139 \index[dir]{Directive!Label Format}
3140 This directive specifies the format of the labels contained in this
3141 pool. The format directive is used as a sort of template to create new
3142 Volume names during automatic Volume labeling.
3144 The {\bf format} should be specified in double quotes, and consists of
3145 letters, numbers and the special characters hyphen ({\bf -}), underscore
3146 ({\bf \_}), colon ({\bf :}), and period ({\bf .}), which are the legal
3147 characters for a Volume name. The {\bf format} should be enclosed in
3150 In addition, the format may contain a number of variable expansion
3151 characters which will be expanded by a complex algorithm allowing you to
3152 create Volume names of many different formats. In all cases, the
3153 expansion process must resolve to the set of characters noted above that
3154 are legal Volume names. Generally, these variable expansion characters
3155 begin with a dollar sign ({\bf \$}) or a left bracket ({\bf [}). If you
3156 specify variable expansion characters, you should always enclose the
3157 format with double quote characters ({\bf "}). For more details on
3158 variable expansion, please see the \ilink{Variable
3159 Expansion}{VarsChapter} Chapter of this manual.
3161 If no variable expansion characters are found in the string, the Volume
3162 name will be formed from the {\bf format} string appended with the
3163 a unique number that increases. If you do not remove volumes from the
3164 pool, this number should be the number of volumes plus one, but this
3165 is not guaranteed. The unique number will be edited as four
3166 digits with leading zeros. For example, with a {\bf Label Format =
3167 "File-"}, the first volumes will be named {\bf File-0001}, {\bf
3170 With the exception of Job specific variables, you can test your {\bf
3171 LabelFormat} by using the \ilink{ var command}{var} the Console Chapter
3174 In almost all cases, you should enclose the format specification (part
3175 after the equal sign) in double quotes. Please note that this directive
3176 is deprecated and is replaced in version 1.37 and greater with a Python
3177 script for creating volume names.
3181 In order for a Pool to be used during a Backup Job, the Pool must have at
3182 least one Volume associated with it. Volumes are created for a Pool using
3183 the {\bf label} or the {\bf add} commands in the {\bf Bacula Console},
3184 program. In addition to adding Volumes to the Pool (i.e. putting the
3185 Volume names in the Catalog database), the physical Volume must be labeled
3186 with a valid Bacula software volume label before {\bf Bacula} will accept
3187 the Volume. This will be automatically done if you use the {\bf label}
3188 command. Bacula can automatically label Volumes if instructed to do so,
3189 but this feature is not yet fully implemented.
3191 The following is an example of a valid Pool resource definition:
3203 \subsection{The Scratch Pool}
3204 \label{TheScratchPool}
3205 \index[general]{Scratch Pool}
3206 In general, you can give your Pools any name you wish, but there is one
3207 important restriction: the Pool named {\bf Scratch}, if it exists behaves
3208 like a scratch pool of Volumes in that when Bacula needs a new Volume for
3209 writing and it cannot find one, it will look in the Scratch pool, and if
3210 it finds an available Volume, it will move it out of the Scratch pool into
3211 the Pool currently being used by the job.
3214 \section{The Catalog Resource}
3215 \label{CatalogResource}
3216 \index[general]{Resource!Catalog}
3217 \index[general]{Catalog Resource}
3219 The Catalog Resource defines what catalog to use for the current job.
3220 Currently, Bacula can only handle a single database server (SQLite, MySQL,
3221 PostgreSQL) that is defined when configuring {\bf Bacula}. However, there
3222 may be as many Catalogs (databases) defined as you wish. For example, you
3223 may want each Client to have its own Catalog database, or you may want
3224 backup jobs to use one database and verify or restore jobs to use another
3227 Since SQLite is compiled in, it always runs on the same machine
3228 as the Director and the database must be directly accessible (mounted) from
3229 the Director. However, since both MySQL and PostgreSQL are networked
3230 databases, they may reside either on the same machine as the Director
3231 or on a different machine on the network. See below for more details.
3236 \index[dir]{Catalog}
3237 \index[dir]{Directive!Catalog}
3238 Start of the Catalog resource. At least one Catalog resource must be
3242 \item [Name = \lt{}name\gt{}]
3244 \index[dir]{Directive!Name}
3245 The name of the Catalog. No necessary relation to the database server
3246 name. This name will be specified in the Client resource directive
3247 indicating that all catalog data for that Client is maintained in this
3248 Catalog. This directive is required.
3250 \item [password = \lt{}password\gt{}]
3251 \index[dir]{password}
3252 \index[dir]{Directive!password}
3253 This specifies the password to use when logging into the database. This
3254 directive is required.
3256 \item [DB Name = \lt{}name\gt{}]
3257 \index[dir]{DB Name}
3258 \index[dir]{Directive!DB Name}
3259 This specifies the name of the database. If you use multiple catalogs
3260 (databases), you specify which one here. If you are using an external
3261 database server rather than the internal one, you must specify a name
3262 that is known to the server (i.e. you explicitly created the Bacula
3263 tables using this name. This directive is required.
3265 \item [user = \lt{}user\gt{}]
3267 \index[dir]{Directive!user}
3268 This specifies what user name to use to log into the database. This
3269 directive is required.
3271 \item [DB Socket = \lt{}socket-name\gt{}]
3272 \index[dir]{DB Socket}
3273 \index[dir]{Directive!DB Socket}
3274 This is the name of a socket to use on the local host to connect to the
3275 database. This directive is used only by MySQL and is ignored by SQLite.
3276 Normally, if neither {\bf DB Socket} or {\bf DB Address} are specified, MySQL
3277 will use the default socket. If the DB Socket is specified, the
3278 MySQL server must reside on the same machine as the Director.
3280 \item [DB Address = \lt{}address\gt{}]
3281 \index[dir]{DB Address}
3282 \index[dir]{Directive!DB Address}
3283 This is the host address of the database server. Normally, you would specify
3284 this instead of {\bf DB Socket} if the database server is on another machine.
3285 In that case, you will also specify {\bf DB Port}. This directive is used
3286 only by MySQL and PostgreSQL and is ignored by SQLite if provided.
3287 This directive is optional.
3289 \item [DB Port = \lt{}port\gt{}]
3290 \index[dir]{DB Port}
3291 \index[dir]{Directive!DB Port}
3292 This defines the port to be used in conjunction with {\bf DB Address} to
3293 access the database if it is on another machine. This directive is used only
3294 by MySQL and PostgreSQL and is ignored by SQLite if provided. This
3295 directive is optional.
3297 %% \item [Multiple Connections = \lt{}yes\vb{}no\gt{}]
3298 %% \index[dir]{Multiple Connections}
3299 %% \index[dir]{Directive!Multiple Connections}
3300 %% By default, this directive is set to no. In that case, each job that uses
3302 %% same Catalog will use a single connection to the catalog. It will be shared,
3303 %% and Bacula will allow only one Job at a time to communicate. If you set this
3304 %% directive to yes, Bacula will permit multiple connections to the database,
3305 %% and the database must be multi-thread capable. For SQLite and PostgreSQL,
3306 %% this is no problem. For MySQL, you must be *very* careful to have the
3307 %% multi-thread version of the client library loaded on your system. When this
3308 %% directive is set yes, each Job will have a separate connection to the
3309 %% database, and the database will control the interaction between the
3311 %% Jobs. This can significantly speed up the database operations if you are
3312 %% running multiple simultaneous jobs. In addition, for SQLite and PostgreSQL,
3313 %% Bacula will automatically enable transactions. This can significantly speed
3314 %% up insertion of attributes in the database either for a single Job or
3315 %% multiple simultaneous Jobs.
3317 %% This directive has not been tested. Please test carefully before running it
3318 %% in production and report back your results.
3322 The following is an example of a valid Catalog resource definition:
3331 password = "" # no password = no security
3336 or for a Catalog on another machine:
3346 DB Address = remote.acme.com
3352 \section{The Messages Resource}
3353 \label{MessagesResource2}
3354 \index[general]{Resource!Messages}
3355 \index[general]{Messages Resource}
3357 For the details of the Messages Resource, please see the
3358 \ilink{Messages Resource Chapter}{MessagesChapter} of this
3361 \section{The Console Resource}
3362 \label{ConsoleResource1}
3363 \index[general]{Console Resource}
3364 \index[general]{Resource!Console}
3366 As of Bacula version 1.33 and higher, there are three different kinds of
3367 consoles, which the administrator or user can use to interact with the
3368 Director. These three kinds of consoles comprise three different security
3372 \item The first console type is an {\bf anonymous} or {\bf default} console,
3373 which has full privileges. There is no console resource necessary for
3374 this type since the password is specified in the Director's resource and
3375 consequently such consoles do not have a name as defined on a {\bf Name
3376 =} directive. This is the kind of console that was initially
3377 implemented in versions prior to 1.33 and remains valid. Typically you
3378 would use it only for administrators.
3380 \item The second type of console, and new to version 1.33 and higher is a
3381 "named" console defined within a Console resource in both the Director's
3382 configuration file and in the Console's configuration file. Both the
3383 names and the passwords in these two entries must match much as is the
3384 case for Client programs.
3386 This second type of console begins with absolutely no privileges except
3387 those explicitly specified in the Director's Console resource. Thus you
3388 can have multiple Consoles with different names and passwords, sort of
3389 like multiple users, each with different privileges. As a default,
3390 these consoles can do absolutely nothing -- no commands whatsoever. You
3391 give them privileges or rather access to commands and resources by
3392 specifying access control lists in the Director's Console resource. The
3393 ACLs are specified by a directive followed by a list of access names.
3394 Examples of this are shown below.
3396 \item The third type of console is similar to the above mentioned one in that
3397 it requires a Console resource definition in both the Director and the
3398 Console. In addition, if the console name, provided on the {\bf Name =}
3399 directive, is the same as a Client name, that console is permitted to
3400 use the {\bf SetIP} command to change the Address directive in the
3401 Director's client resource to the IP address of the Console. This
3402 permits portables or other machines using DHCP (non-fixed IP addresses)
3403 to "notify" the Director of their current IP address.
3406 The Console resource is optional and need not be specified. The following
3407 directives are permitted within the Director's configuration resource:
3411 \item [Name = \lt{}name\gt{}]
3413 \index[dir]{Directive!Name}
3414 The name of the console. This name must match the name specified in the
3415 Console's configuration resource (much as is the case with Client
3418 \item [Password = \lt{}password\gt{}]
3419 \index[dir]{Password}
3420 \index[dir]{Directive!Password}
3421 Specifies the password that must be supplied for a named Bacula Console
3422 to be authorized. The same password must appear in the {\bf Console}
3423 resource of the Console configuration file. For added security, the
3424 password is never actually passed across the network but rather a
3425 challenge response hash code created with the password. This directive
3426 is required. If you have either {\bf /dev/random} {\bf bc} on your
3427 machine, Bacula will generate a random password during the configuration
3428 process, otherwise it will be left blank.
3430 The password is plain text. It is not generated through any special
3431 process. However, it is preferable for security reasons to choose
3434 \item [JobACL = \lt{}name-list\gt{}]
3436 \index[dir]{Directive!JobACL}
3437 This directive is used to specify a list of Job resource names that can
3438 be accessed by the console. Without this directive, the console cannot
3439 access any of the Director's Job resources. Multiple Job resource names
3440 may be specified by separating them with commas, and/or by specifying
3441 multiple JobACL directives. For example, the directive may be specified
3446 JobACL = kernsave, "Backup client 1", "Backup client 2"
3447 JobACL = "RestoreFiles"
3452 With the above specification, the console can access the Director's resources
3453 for the four jobs named on the JobACL directives, but for no others.
3455 \item [ClientACL = \lt{}name-list\gt{}]
3456 \index[dir]{ClientACL}
3457 \index[dir]{Directive!ClientACL}
3458 This directive is used to specify a list of Client resource names that can
3460 accessed by the console.
3462 \item [StorageACL = \lt{}name-list\gt{}]
3463 \index[dir]{StorageACL}
3464 \index[dir]{Directive!StorageACL}
3465 This directive is used to specify a list of Storage resource names that can
3466 be accessed by the console.
3468 \item [ScheduleACL = \lt{}name-list\gt{}]
3469 \index[dir]{ScheduleACL}
3470 \index[dir]{Directive!ScheduleACL}
3471 This directive is used to specify a list of Schedule resource names that can
3472 be accessed by the console.
3474 \item [PoolACL = \lt{}name-list\gt{}]
3475 \index[dir]{PoolACL}
3476 \index[dir]{Directive!PoolACL}
3477 This directive is used to specify a list of Pool resource names that can be
3478 accessed by the console.
3480 \item [FileSetACL = \lt{}name-list\gt{}]
3481 \index[dir]{FileSetACL}
3482 \index[dir]{Directive!FileSetACL}
3483 This directive is used to specify a list of FileSet resource names that
3484 can be accessed by the console.
3486 \item [CatalogACL = \lt{}name-list\gt{}]
3487 \index[dir]{CatalogACL}
3488 \index[dir]{Directive!CatalogACL}
3489 This directive is used to specify a list of Catalog resource names that
3490 can be accessed by the console.
3492 \item [CommandACL = \lt{}name-list\gt{}]
3493 \index[dir]{CommandACL}
3494 \index[dir]{Directive!CommandACL}
3495 This directive is used to specify a list of of console commands that can
3496 be executed by the console.
3498 \item [WhereACL = \lt{}string\gt{}]
3499 \index[dir]{WhereACL}
3500 \index[dir]{Directive!WhereACL}
3501 This directive permits you to specify where a restricted console
3502 can restore files. If this directive is not specified, only the
3503 default restore location is permitted (normally {\bf
3504 /tmp/bacula-restores}. If {\bf *all*} is specified any path the
3505 user enters will be accepted (not very secure), any other
3506 value specified (there may be multiple WhereACL directives) will
3507 restrict the user to use that path. For example, on a Unix system,
3508 if you specify "/", the file will be restored to the original
3509 location. This directive is untested.
3513 Aside from Director resource names and console command names, the special
3514 keyword {\bf *all*} can be specified in any of the above access control lists.
3515 When this keyword is present, any resource or command name (which ever is
3516 appropriate) will be accepted. For an example configuration file, please see
3518 \ilink{Console Configuration}{ConsoleConfChapter} chapter of this
3521 \section{The Counter Resource}
3522 \label{CounterResource}
3523 \index[general]{Resource!Counter}
3524 \index[general]{Counter Resource}
3526 The Counter Resource defines a counter variable that can be accessed by
3527 variable expansion used for creating Volume labels with the {\bf LabelFormat}
3529 \ilink{LabelFormat}{Label} directive in this chapter for more
3535 \index[dir]{Counter}
3536 \index[dir]{Directive!Counter}
3537 Start of the Counter resource. Counter directives are optional.
3539 \item [Name = \lt{}name\gt{}]
3541 \index[dir]{Directive!Name}
3542 The name of the Counter. This is the name you will use in the variable
3543 expansion to reference the counter value.
3545 \item [Minimum = \lt{}integer\gt{}]
3546 \index[dir]{Minimum}
3547 \index[dir]{Directive!Minimum}
3548 This specifies the minimum value that the counter can have. It also becomes
3549 the default. If not supplied, zero is assumed.
3551 \item [Maximum = \lt{}integer\gt{}]
3552 \index[dir]{Maximum}
3553 \index[dir]{Directive!Maximum}
3554 \index[dir]{Directive!Maximum}
3555 This is the maximum value value that the counter can have. If not specified
3556 or set to zero, the counter can have a maximum value of 2,147,483,648 (2 to
3557 the 31 power). When the counter is incremented past this value, it is reset
3560 \item [*WrapCounter = \lt{}counter-name\gt{}]
3561 \index[dir]{*WrapCounter}
3562 \index[dir]{Directive!*WrapCounter}
3563 If this value is specified, when the counter is incremented past the
3565 and thus reset to the minimum, the counter specified on the {\bf WrapCounter}
3566 is incremented. (This is not currently implemented).
3568 \item [Catalog = \lt{}catalog-name\gt{}]
3569 \index[dir]{Catalog}
3570 \index[dir]{Directive!Catalog}
3571 If this directive is specified, the counter and its values will be saved in
3572 the specified catalog. If this directive is not present, the counter will be
3573 redefined each time that Bacula is started.
3576 \section{Example Director Configuration File}
3577 \label{SampleDirectorConfiguration}
3578 \index[general]{File!Example Director Configuration}
3579 \index[general]{Example Director Configuration File}
3581 An example Director configuration file might be the following:
3586 # Default Bacula Director Configuration file
3588 # The only thing that MUST be changed is to add one or more
3589 # file or directory names in the Include directive of the
3592 # For Bacula release 1.15 (5 March 2002) -- redhat
3594 # You might also want to change the default email address
3595 # from root to your address. See the "mail" and "operator"
3596 # directives in the Messages resource.
3598 Director { # define myself
3600 QueryFile = "/home/kern/bacula/bin/query.sql"
3601 WorkingDirectory = "/home/kern/bacula/bin/working"
3602 PidDirectory = "/home/kern/bacula/bin/working"
3603 Password = "XkSfzu/Cf/wX4L8Zh4G4/yhCbpLcz3YVdmVoQvU3EyF/"
3605 # Define the backup Job
3607 Name = "NightlySave"
3609 Level = Incremental # default
3612 Schedule = "WeeklyCycle"
3622 Where = /tmp/bacula-restores
3628 # List of files to be backed up
3632 Options { signature=SHA1}
3634 # Put your list of files here, one per line or include an
3635 # external list with:
3639 # Note: / backs up everything
3644 # When to do the backups
3646 Name = "WeeklyCycle"
3647 Run = level=Full sun at 2:05
3648 Run = level=Incremental mon-sat at 2:05
3650 # Client (File Services) to backup
3655 Password = "MQk6lVinz4GG2hdIZk1dsKE/LxMZGo6znMHiD7t7vzF+"
3656 File Retention = 60d # sixty day file retention
3657 Job Retention = 1y # 1 year Job retention
3658 AutoPrune = yes # Auto apply retention periods
3660 # Definition of DLT tape storage device
3664 Password = "jMeWZvfikUHvt3kzKVVPpQ0ccmV6emPnF2cPYFdhLApQ"
3665 Device = "HP DLT 80" # same as Device in Storage daemon
3666 Media Type = DLT8000 # same as MediaType in Storage daemon
3668 # Definition for a DLT autochanger device
3672 Password = "jMeWZvfikUHvt3kzKVVPpQ0ccmV6emPnF2cPYFdhLApQ"
3673 Device = "Autochanger" # same as Device in Storage daemon
3674 Media Type = DLT-8000 # Different from DLTDrive
3677 # Definition of DDS tape storage device
3681 Password = "jMeWZvfikUHvt3kzKVVPpQ0ccmV6emPnF2cPYFdhLApQ"
3682 Device = SDT-10000 # same as Device in Storage daemon
3683 Media Type = DDS-4 # same as MediaType in Storage daemon
3685 # Definition of 8mm tape storage device
3689 Password = "jMeWZvfikUHvt3kzKVVPpQ0ccmV6emPnF2cPYFdhLApQ"
3690 Device = "Exabyte 8mm"
3693 # Definition of file storage device
3697 Password = "jMeWZvfikUHvt3kzKVVPpQ0ccmV6emPnF2cPYFdhLApQ"
3698 Device = FileStorage
3701 # Generic catalog service
3704 dbname = bacula; user = bacula; password = ""
3706 # Reasonable message delivery -- send most everything to
3707 # the email address and to the console
3710 mail = root@localhost = all, !skipped, !terminate
3711 operator = root@localhost = mount
3712 console = all, !skipped, !saved
3715 # Default pool definition
3723 # Restricted console used by tray-monitor to get the status of the director
3727 Password = "GN0uRo7PTUmlMbqrJ2Gr1p0fk0HQJTxwnFyE4WSST3MWZseR"
3728 CommandACL = status, .status