4 \chapter{Storage Daemon Configuration}
5 \label{StoredConfChapter}
6 \index[general]{Storage Daemon Configuration}
7 \index[general]{Configuration!Storage Daemon}
9 The Storage Daemon configuration file has relatively few resource definitions.
10 However, due to the great variation in backup media and system capabilities,
11 the storage daemon must be highly configurable. As a consequence, there are
12 quite a large number of directives in the Device Resource definition that
13 allow you to define all the characteristics of your Storage device (normally a
14 tape drive). Fortunately, with modern storage devices, the defaults are
15 sufficient, and very few directives are actually needed.
17 Examples of {\bf Device} resource directives that are known to work for a
18 number of common tape drives can be found in the {\bf
19 \lt{}bacula-src\gt{}/examples/devices} directory, and most will also be listed
22 For a general discussion of configuration file and resources including the
23 data types recognized by {\bf Bacula}, please see the
24 \ilink{Configuration}{ConfigureChapter} chapter of this manual. The
25 following Storage Resource definitions must be defined:
29 \ilink{Storage}{StorageResource} -- to define the name of the
32 \ilink{Director}{DirectorResource1} -- to define the Director's
33 name and his access password.
35 \ilink{Device}{DeviceResource} -- to define the
36 characteristics of your storage device (tape drive).
38 \ilink{Messages}{MessagesChapter} -- to define where error and
39 information messages are to be sent.
42 \section{Storage Resource}
43 \label{StorageResource}
44 \index[general]{Resource!Storage}
45 \index[general]{Storage Resource}
47 In general, the properties specified under the Storage resource define global
48 properties of the Storage daemon. Each Storage daemon configuration file must
49 have one and only one Storage resource definition.
53 \item [Name = \lt{}Storage-Daemon-Name\gt{}]
55 \index[sd]{Directive!Name}
56 Specifies the Name of the Storage daemon. This directive is required.
58 \item [Working Directory = \lt{}Directory\gt{}]
59 \index[sd]{Working Directory}
60 \index[sd]{Directive!Working Directory}
61 This directive is mandatory and specifies a directory in which the Storage
62 daemon may put its status files. This directory should be used only by {\bf
63 Bacula}, but may be shared by other Bacula daemons provided the names
64 given to each daemon are unique. This directive is
67 \item [Pid Directory = \lt{}Directory\gt{}]
68 \index[sd]{Pid Directory}
69 \index[sd]{Directive!Pid Directory}
70 This directive is mandatory and specifies a directory in which the Director
71 may put its process Id file files. The process Id file is used to shutdown
72 Bacula and to prevent multiple copies of Bacula from running simultaneously.
73 This directive is required. Standard shell expansion of the {\bf Directory}
74 is done when the configuration file is read so that values such as {\bf
75 \$HOME} will be properly expanded.
77 Typically on Linux systems, you will set this to: {\bf /var/run}. If you are
78 not installing Bacula in the system directories, you can use the {\bf Working
79 Directory} as defined above.
81 \item [Heartbeat Interval = \lt{}time-interval\gt{}]
82 \index[sd]{Heartbeat Interval}
83 \index[sd]{Directive!Heartbeat Interval}
84 \index[general]{Heartbeat Interval}
85 \index[general]{Broken pipe}
86 This directive defines an interval of time in seconds. When
87 the Storage daemon is waiting for the operator to mount a
88 tape, each time interval, it will send a heartbeat signal to
89 the File daemon. The default interval is zero which disables
90 the heartbeat. This feature is particularly useful if you
91 have a router such as 3Com that does not follow Internet
92 standards and times out an valid connection after a short
93 duration despite the fact that keepalive is set. This usually
94 results in a broken pipe error message.
96 \item [Client Connect Wait = \lt{}time-interval\gt{}]
97 \index[sd]{Connect Wait}
98 \index[sd]{Directive!Connect Wait}
99 \index[general]{Client Connect Wait}
100 This directive defines an interval of time in seconds that
101 the Storage daemon will wait for a Client (the File daemon)
102 to connect. The default is 30 minutes. Be aware that the
103 longer the Storage daemon waits for a Client, the more
104 resources will be tied up.
106 \item [Maximum Concurrent Jobs = \lt{}number\gt{}]
107 \index[sd]{Maximum Concurrent Jobs}
108 \index[sd]{Directive!Maximum Concurrent Jobs}
109 where \lt{}number\gt{} is the maximum number of Jobs that may run
110 concurrently. The default is set to 10, but you may set it to a larger
111 number. Each contact from the Director (e.g. status request, job start
112 request) is considered as a Job, so if you want to be able to do a {\bf
113 status} request in the console at the same time as a Job is running, you
114 will need to set this value greater than 1. To run simultaneous Jobs,
115 you will need to set a number of other directives in the Director's
116 configuration file. Which ones you set depend on what you want, but you
117 will almost certainly need to set the {\bf Maximum Concurrent Jobs} in
118 the Storage resource in the Director's configuration file and possibly
119 those in the Job and Client resources.
121 \item [SDAddresses = \lt{}IP-address-specification\gt{}]
122 \index[sd]{SDAddresses}
123 \index[sd]{Directive!SDAddresses}
124 Specify the ports and addresses on which the Storage daemon will listen
125 for Director connections. Normally, the default is sufficient and you
126 do not need to specify this directive. Probably the simplest way to
127 explain how this directive works is to show an example:
131 SDAddresses = { ip = {
132 addr = 1.2.3.4; port = 1205; }
134 addr = 1.2.3.4; port = http; }
147 addr = 201:220:222::2
150 addr = bluedot.thun.net
156 where ip, ip4, ip6, addr, and port are all keywords. Note, that the address
157 can be specified as either a dotted quadruple, or IPv6 colon notation, or as
158 a symbolic name (only in the ip specification). Also, port can be specified
159 as a number or as the mnemonic value from the /etc/services file. If a port
160 is not specified, the default will be used. If an ip section is specified,
161 the resolution can be made either by IPv4 or IPv6. If ip4 is specified, then
162 only IPv4 resolutions will be permitted, and likewise with ip6.
164 Using this directive, you can replace both the SDPort and SDAddress
165 directives shown below.
167 \item [SDPort = \lt{}port-number\gt{}]
169 \index[sd]{Directive!SDPort}
170 Specifies port number on which the Storage daemon listens for Director
171 connections. The default is 9103.
173 \item [SDAddress = \lt{}IP-Address\gt{}]
174 \index[sd]{SDAddress}
175 \index[sd]{Directive!SDAddress}
176 This directive is optional, and if it is specified, it will cause the
177 Storage daemon server (for Director and File daemon connections) to bind
178 to the specified {\bf IP-Address}, which is either a domain name or an
179 IP address specified as a dotted quadruple. If this directive is not
180 specified, the Storage daemon will bind to any available address (the
185 The following is a typical Storage daemon Storage definition.
190 # "Global" Storage daemon configuration specifications appear
191 # under the Storage resource.
194 Name = "Storage daemon"
196 WorkingDirectory = "~/bacula/working"
197 Pid Directory = "~/bacula/working"
202 \section{Director Resource}
203 \label{DirectorResource1}
204 \index[general]{Director Resource}
205 \index[general]{Resource!Director}
207 The Director resource specifies the Name of the Director which is permitted
208 to use the services of the Storage daemon. There may be multiple Director
209 resources. The Director Name and Password must match the corresponding
210 values in the Director's configuration file.
214 \item [Name = \lt{}Director-Name\gt{}]
216 \index[sd]{Directive!Name}
217 Specifies the Name of the Director allowed to connect to the Storage daemon.
218 This directive is required.
220 \item [Password = \lt{}Director-password\gt{}]
222 \index[sd]{Directive!Password}
223 Specifies the password that must be supplied by the above named Director.
224 This directive is required.
226 \item [Monitor = \lt{}yes\vb{}no\gt{}]
228 \index[sd]{Directive!Monitor}
229 If Monitor is set to {\bf no} (default), this director will have full
230 access to this Storage daemon. If Monitor is set to {\bf yes}, this
231 director will only be able to fetch the current status of this Storage
234 Please note that if this director is being used by a Monitor, we highly
235 recommend to set this directive to {\bf yes} to avoid serious security
240 The following is an example of a valid Director resource definition:
246 Password = my_secret_password
251 \label{DeviceResource}
252 \section{Device Resource}
253 \index[general]{Resource!Device}
254 \index[general]{Device Resource}
256 The Device Resource specifies the details of each device (normally a tape
257 drive) that can be used by the Storage daemon. There may be multiple
258 Device resources for a single Storage daemon. In general, the properties
259 specified within the Device resource are specific to the Device.
263 \item [Name = {\it Device-Name}]
265 \index[sd]{Directive!Name}
266 Specifies the Name that the Director will use when asking to backup or
267 restore to or from to this device. This is the logical Device name, and may
268 be any string up to 127 characters in length. It is generally a good idea to
269 make it correspond to the English name of the backup device. The physical
270 name of the device is specified on the {\bf Archive Device} directive
271 described below. The name you specify here is also used in your Director's
273 \ilink{Device directive}{StorageResource2} in its Storage
276 \item [Archive Device = {\it name-string}]
277 \index[sd]{Archive Device}
278 \index[sd]{Directive!Archive Device}
279 The specified {\bf name-string} gives the system file name of the storage
280 device managed by this storage daemon. This will usually be the device file
281 name of a removable storage device (tape drive), for example "{\bf
282 /dev/nst0}" or "{\bf /dev/rmt/0mbn}". It may also be a directory name
283 if you are archiving to disk storage. In this case, you must supply the
284 full absolute path to the directory. When specifying a tape device, it
285 is preferable that the "non-rewind" variant of the device file name be
286 given. In addition, on systems such as Sun, which have multiple tape
287 access methods, you must be sure to specify to use Berkeley I/O
288 conventions with the device. The {\bf b} in the Solaris (Sun) archive
289 specification {\bf /dev/rmt/0mbn} is what is needed in this case.
290 Bacula does not support SysV tape drive behavior.
292 As noted above, normally the Archive Device is the name of a tape drive, but
293 you may also specify an absolute path to an existing directory. If the
294 Device is a directory Bacula will write to file storage in the specified
295 directory, and the filename used will be the Volume name as specified in the
296 Catalog. If you want to write into more than one directory (i.e. to spread
297 the load to different disk drives), you will need to define two Device
298 resources, each containing an Archive Device with a different directory.
300 In addition to a tape device name or a directory name, Bacula will accept the
301 name of a FIFO. A FIFO is a special kind of file that connects two programs
302 via kernel memory. If a FIFO device is specified for a backup operation, you
303 must have a program that reads what Bacula writes into the FIFO. When the
304 Storage daemon starts the job, it will wait for {\bf MaximumOpenWait} seconds
305 for the read program to start reading, and then time it out and terminate
306 the job. As a consequence, it is best to start the read program at the
307 beginning of the job perhaps with the {\bf RunBeforeJob} directive. For this
308 kind of device, you never want to specify {\bf AlwaysOpen}, because you want
309 the Storage daemon to open it only when a job starts, so you must explicitly
310 set it to {\bf No}. Since a FIFO is a one way device, Bacula will not attempt
311 to read a label of a FIFO device, but will simply write on it. To create a
312 FIFO Volume in the catalog, use the {\bf add} command rather than the {\bf
313 label} command to avoid attempting to write a label.
321 Archive Device = /tmp/fifo
332 During a restore operation, if the Archive Device is a FIFO, Bacula will
333 attempt to read from the FIFO, so you must have an external program that
334 writes into the FIFO. Bacula will wait {\bf MaximumOpenWait} seconds for the
335 program to begin writing and will then time it out and terminate the job. As
336 noted above, you may use the {\bf RunBeforeJob} to start the writer program
337 at the beginning of the job.
339 The Archive Device directive is required.
341 \item [Device Type = {\it type-specification}]
342 \index[sd]{Device Type}
343 \index[sd]{Directive!Device Type}
344 The Device Type specification allows you to explicitly tell Bacula
345 what kind of device you are defining. It the {\it type-specification}
346 may be one of the following:
349 Tells Bacula that the device is a file. It may either be a
350 file defined on fixed medium or a removable filesystem such as
351 USB. All files must be random access devices.
353 The device is a tape device and thus is sequential access. Tape devices
354 are controlled using ioctl() calls.
356 The device is a first-in-first out sequential access read-only
357 or write-only device.
360 The Device Type directive is not required, and if not specified, Bacula
361 will attempt to guess what kind of device has been specified using the
362 Archive Device specification supplied. There are several advantages to
363 explicitly specifying the Device Type. First, on some systems, block and
364 character devices have the same type.
365 Secondly, if you explicitly specify the Device Type, the mount point
366 need not be defined until the device is opened. This is the case with
367 most removable devices such as USB that are mounted by the HAL daemon.
368 If the Device Type is not explicitly specified, then the mount point
369 must exist when the Storage daemon starts.
371 This directive was implemented in Bacula version 1.38.6.
374 \item [Media Type = {\it name-string}]
375 \index[sd]{Media Type}
376 \index[sd]{Directive!Media Type}
377 The specified {\bf name-string} names the type of media supported by this
378 device, for example, "DLT7000". Media type names are arbitrary in that you
379 set them to anything you want, but they must be known to the volume
380 database to keep track of which storage daemons can read which volumes. In
381 general, each different storage type should have a unique Media Type
382 associated with it. The same {\bf name-string} must appear in the
383 appropriate Storage resource definition in the Director's configuration
386 Even though the names you assign are arbitrary (i.e. you choose the name
387 you want), you should take care in specifying them because the Media Type
388 is used to determine which storage device Bacula will select during
389 restore. Thus you should probably use the same Media Type specification
390 for all drives where the Media can be freely interchanged. This is not
391 generally an issue if you have a single Storage daemon, but it is with
392 multiple Storage daemons, especially if they have incompatible media.
394 For example, if you specify a Media Type of "DDS-4" then during the
395 restore, Bacula will be able to choose any Storage Daemon that handles
396 "DDS-4". If you have an autochanger, you might want to name the Media Type
397 in a way that is unique to the autochanger, unless you wish to possibly use
398 the Volumes in other drives. You should also ensure to have unique Media
399 Type names if the Media is not compatible between drives. This
400 specification is required for all devices.
402 In addition, if you are using disk storage, each Device resource will
403 generally have a different mount point or directory. In order for
404 Bacula to select the correct Device resource, each one must have a
408 \item [Autochanger = {\it yes\vb{}no}]
409 \index[sd]{Autochanger}
410 \index[sd]{Directive!Autochanger}
411 If {\bf Yes}, this device belongs to an automatic tape changer, and you
412 must specify an {\bf Autochanger} resource that points to the {\bf
413 Device} resources. You must also specify a
414 {\bf Changer Device}. If the Autochanger directive is set to {\bf
415 No} (default), the volume must be manually changed. You should also
416 have an identical directive to the
417 \ilink{Storage resource}{Autochanger1} in the Director's
418 configuration file so that when labeling tapes you are prompted for the slot.
420 \item [Changer Device = {\it name-string}]
421 \index[sd]{Changer Device}
422 \index[sd]{Directive!Changer Device}
423 The specified {\bf name-string} must be the {\bf generic SCSI} device
424 name of the autochanger that corresponds to the normal read/write
425 {\bf Archive Device} specified in the Device resource. This
426 generic SCSI device name should be specified if you have an autochanger
427 or if you have a standard tape drive and want to use the
428 {\bf Alert Command} (see below). For example, on Linux systems, for
429 an Archive Device name of {\bf /dev/nst0}, you would specify {\bf
430 /dev/sg0} for the Changer Device name. Depending on your exact
431 configuration, and the number of autochangers or the type of
432 autochanger, what you specify here can vary. This directive is
433 optional. See the \ilink{Using Autochangers}{AutochangersChapter} chapter
434 of this manual for more details of using this and the following
435 autochanger directives.
437 \item [Changer Command = {\it name-string}]
438 \index[sd]{Changer Command}
439 \index[sd]{Directive!Changer Command}
440 The {\bf name-string} specifies an external program to be called that will
441 automatically change volumes as required by {\bf Bacula}. Normally,
442 this directive will be specified only in the {\bf AutoChanger} resource,
443 which is then used for all devices. However, you may also specify
444 the different {\bf Changer Command} in each Device resource.
446 you will specify the Bacula supplied {\bf mtx-changer} script as follows:
450 Changer Command = "/path/mtx-changer %c %o %S %a %d"
454 and you will install the {\bf mtx} on your system (found in the {\bf depkgs}
455 release). An example of this command is in the default bacula-sd.conf file.
456 For more details on the substitution characters that may be specified to
457 configure your autochanger please see the
458 \ilink{Autochangers}{AutochangersChapter} chapter of this manual.
459 For FreeBSD users, you might want to see one of the several {\bf chio}
460 scripts in {\bf examples/autochangers}.
462 \item [Alert Command = {\it name-string}]
463 \index[sd]{Alert Command}
464 The {\bf name-string} specifies an external program to be called at the
465 completion of each Job after the device is released. The purpose of this
466 command is to check for Tape Alerts, which are present when something is
467 wrong with your tape drive (at least for most modern tape drives). The same
468 substitution characters that may be specified in the Changer Command may
469 also be used in this string. For more information, please see the
470 \ilink{Autochangers}{AutochangersChapter} chapter of this manual.
473 Note, it is not necessary to have an autochanger to use this command. The
474 example below uses the {\bf tapeinfo} program that comes with the {\bf mtx}
475 package, but it can be used on any tape drive. However, you will need to
476 specify a {\bf Changer Device} directive in your Device resource (see above)
477 so that the generic SCSI device name can be edited into the command (with
480 An example of the use of this command to print Tape Alerts in the Job report
485 Alert Command = "sh -c 'tapeinfo -f %c | grep TapeAlert'"
490 and an example output when there is a problem could be:
494 bacula-sd Alert: TapeAlert[32]: Interface: Problem with SCSI interface
495 between tape drive and initiator.
500 \item [Drive Index = {\it number}]
501 \index[sd]{Drive Index}
502 \index[sd]{Directive!Drive Index}
503 The {\bf Drive Index} that you specify is passed to the {\bf
504 mtx-changer} script and is thus passed to the {\bf mtx} program. By
505 default, the Drive Index is zero, so if you have only one drive in your
506 autochanger, everything will work normally. However, if you have
507 multiple drives, you must specify multiple Bacula Device resources (one
508 for each drive). The first Device should have the Drive Index set to 0,
509 and the second Device Resource should contain a Drive Index set to 1,
510 and so on. This will then permit you to use two or more drives in your
511 autochanger. As of Bacula version 1.38.0, using the {\bf Autochanger}
512 resource, Bacula will automatically ensure that only one drive at a time
513 uses the autochanger script, so you no longer need locking scripts as in
514 the past -- the default mtx-changer script works for any number of
517 \item [Autoselect = {\it yes\vb{}no}]
518 \index[sd]{Autoselect}
519 \index[sd]{Directive!Autoselect}
520 If this directive is set to {\bf yes} (default), and the Device
521 belongs to an autochanger, then when the Autochanger is referenced
522 by the Director, this device can automatically be selected. If this
523 directive is set to {\bf no}, then the Device can only be referenced
524 by directly using the Device name in the Director. This is useful
525 for reserving a drive for something special such as a high priority
526 backup or restore operations.
528 \item[Maximum Concurrent Jobs = {\it num}]
529 \index[sd]{MaximumConcurrentJobs}
531 {\bf Maximum Concurrent Jobs} is a directive that permits setting the maximum
532 number of Jobs that can run concurrently on a specified Device. Using this
533 directive, it is possible to have different Jobs using multiple drives, because
534 when the Maximum Concurrent Jobs limit is reached, the Storage Daemon will
535 start new Jobs on any other available compatible drive. This facilitates
536 writing to multiple drives with multiple Jobs that all use the same Pool.
538 \item [Maximum Changer Wait = {\it time}]
539 \index[sd]{Maximum Changer Wait}
540 \index[sd]{Directive!Maximum Changer Wait}
541 This directive specifies the maximum time in seconds for Bacula to wait
542 for an autochanger to change the volume. If this time is exceeded,
543 Bacula will invalidate the Volume slot number stored in the catalog and
544 try again. If no additional changer volumes exist, Bacula will ask the
545 operator to intervene. The default is 5 minutes.
546 % TODO: if this is the format, then maybe "5 minutes" should be in
547 % TODO: quotes? define style. see others.
549 \item [Maximum Rewind Wait = {\it time}]
550 \index[sd]{Maximum Rewind Wait}
551 \index[sd]{Directive!Maximum Rewind Wait}
552 This directive specifies the maximum time in seconds for Bacula to wait
553 for a rewind before timing out. If this time is exceeded,
554 Bacula will cancel the job. The default is 5 minutes.
556 \item [Maximum Open Wait = {\it time}]
557 \index[sd]{Maximum Open Wait}
558 \index[sd]{Directive!Maximum Open Wait}
559 This directive specifies the maximum time in seconds that
560 Bacula will wait for a device that is busy. The default is 5 minutes.
561 If the device cannot be obtained, the current Job will be terminated in
562 error. Bacula will re-attempt to open the drive the next time a Job
563 starts that needs the the drive.
565 \item [Always Open = {\it yes\vb{}no}]
566 \index[sd]{Always Open}
567 \index[sd]{Directive!Always Open}
568 If {\bf Yes} (default), Bacula will always keep the device open unless
569 specifically {\bf unmounted} by the Console program. This permits
570 Bacula to ensure that the tape drive is always available, and properly
571 positioned. If you set
572 {\bf AlwaysOpen} to {\bf no}, {\bf Bacula} will only open the
573 drive when necessary, and at the end of the Job if no other Jobs are
574 using the drive, it will be freed. The next time Bacula wants to append
575 to a tape on a drive that was freed, Bacula will rewind the tape and
576 position it to the end. To avoid unnecessary tape positioning and to
577 minimize unnecessary operator intervention, it is highly recommended
578 that {\bf Always Open = yes}. This also ensures that the drive is
579 available when Bacula needs it.
581 If you have {\bf Always Open = yes} (recommended) and you want to use the
582 drive for something else, simply use the {\bf unmount} command in the
583 Console program to release the drive. However, don't forget to remount the
584 drive with {\bf mount} when the drive is available or the next Bacula job
587 For File storage, this directive is ignored. For a FIFO storage device, you
588 must set this to {\bf No}.
590 Please note that if you set this directive to {\bf No} Bacula will release
591 the tape drive between each job, and thus the next job will rewind the tape
592 and position it to the end of the data. This can be a very time consuming
593 operation. In addition, with this directive set to no, certain multiple
594 drive autochanger operations will fail. We strongly recommend to keep
595 {\bf Always Open} set to {\bf Yes}
597 \item [Volume Poll Interval = {\it time}]
598 \index[sd]{Volume Poll Interval}
599 \index[sd]{Directive!Volume Poll Interval}
600 If the time specified on this directive is non-zero, after asking the
601 operator to mount a new volume Bacula will periodically poll (or read) the
602 drive at the specified interval to see if a new volume has been mounted. If
603 the time interval is zero (the default), no polling will occur. This
604 directive can be useful if you want to avoid operator intervention via the
605 console. Instead, the operator can simply remove the old volume and insert
606 the requested one, and Bacula on the next poll will recognize the new tape
607 and continue. Please be aware that if you set this interval too small, you
608 may excessively wear your tape drive if the old tape remains in the drive,
609 since Bacula will read it on each poll. This can be avoided by ejecting the
610 tape using the {\bf Offline On Unmount} and the {\bf Close on Poll}
612 However, if you are using a Linux 2.6 kernel or other OSes
613 such as FreeBSD or Solaris, the Offline On Unmount will leave the drive
614 with no tape, and Bacula will not be able to properly open the drive and
615 may fail the job. For more information on this problem, please see the
616 \borgxrlink{description of Offline On Unmount}{NoTapeInDrive}{problems}{subsection}
617 in the \borgxrlink{Tape Testing}{TapeTestingChapter}{problems}{chapter} of the \problemsman{}.
619 \item [Close on Poll= {\it yes\vb{}no}]
620 \index[sd]{Close on Poll}
621 \index[sd]{Directive!Close on Poll}
622 If {\bf Yes}, Bacula close the device (equivalent to an unmount except no
623 mount is required) and reopen it at each poll. Normally this is not too
624 useful unless you have the {\bf Offline on Unmount} directive set, in which
625 case the drive will be taken offline preventing wear on the tape during any
626 future polling. Once the operator inserts a new tape, Bacula will recognize
627 the drive on the next poll and automatically continue with the backup.
628 Please see above more more details.
630 \label{removablemedia}
631 \item [Removable media = {\it yes\vb{}no}]
632 \index[sd]{Removable media}
633 \index[sd]{Directive!Removable media}
634 If {\bf Yes}, this device supports removable media (for example, tapes
635 or CDs). If {\bf No}, media cannot be removed (for example, an
636 intermediate backup area on a hard disk). If {\bf Removable media} is
637 enabled on a File device (as opposed to a tape) the Storage daemon will
638 assume that device may be something like a USB device that can be
639 removed or a simply a removable harddisk. When attempting to open
640 such a device, if the Volume is not found (for File devices, the Volume
641 name is the same as the Filename), then the Storage daemon will search
642 the entire device looking for likely Volume names, and for each one
643 found, it will ask the Director if the Volume can be used. If so,
644 the Storage daemon will use the first such Volume found. Thus it
645 acts somewhat like a tape drive -- if the correct Volume is not found,
646 it looks at what actually is found, and if it is an appendable Volume,
649 If the removable medium is not automatically mounted (e.g. udev), then
650 you might consider using additional Storage daemon device directives
651 such as {\bf Requires Mount}, {\bf Mount Point}, {\bf Mount Command},
652 and {\bf Unmount Command}, all of which can be used in conjunction with
653 {\bf Removable Media}.
656 \item [Random access = {\it yes\vb{}no}]
657 \index[sd]{Random access}
658 \index[sd]{Directive!Random access}
659 If {\bf Yes}, the archive device is assumed to be a random access medium
660 which supports the {\bf lseek} (or {\bf lseek64} if Largefile is enabled
661 during configuration) facility. This should be set to {\bf Yes} for all
662 file systems such as USB, and fixed files. It should be set to
663 {\bf No} for non-random access devices such as tapes and named pipes.
666 \item [Requires Mount = {\it yes\vb{}no}]
667 \index[sd]{Requires Mount }
668 When this directive is enabled, the Storage daemon will submit
669 a {\bf Mount Command} before attempting to open the device.
670 You must set this directive to {\bf yes} for removable
671 file systems such as USB devices that are not automatically mounted
672 by the operating system when plugged in or opened by Bacula.
673 It should be set to {\bf no} for
674 all other devices such as tapes and fixed filesystems. It should also
675 be set to {\bf no} for any removable device that is automatically
676 mounted by the operating system when opened (e.g. USB devices mounted
677 by udev or hotplug). This directive
678 indicates if the device requires to be mounted using the {\bf Mount
679 Command}. To be able to write devices need a mount, the following
680 directives must also be defined: {\bf Mount Point}, {\bf Mount Command},
681 and {\bf Unmount Command}.
683 \item [Mount Point = {\it directory}]
684 \index[sd]{Mount Point}
685 Directory where the device can be mounted.
686 This directive is used only
687 for devices that have {\bf Requires Mount} enabled such as
690 \item [Mount Command = {\it name-string}]
691 \index[sd]{Mount Command}
692 This directive specifies the command that must be executed to mount
693 devices such as many USB devices. Before the command is
694 executed, \%a is replaced with the Archive Device, and \%m with the Mount
697 See the \ilink{Edit Codes}{mountcodes} section below for more details of
698 the editing codes that can be used in this directive.
700 If you need to specify multiple commands, create a shell script.
702 \item [Unmount Command = {\it name-string}]
703 \index[sd]{Unmount Command}
704 This directive specifies the command that must be executed to unmount
705 devices such as many USB devices. Before the command is
706 executed, \%a is replaced with the Archive Device, and \%m with the Mount
709 Most frequently, you will define it as follows:
713 Unmount Command = "/bin/umount %m"
717 See the \ilink{Edit Codes}{mountcodes} section below for more details of
718 the editing codes that can be used in this directive.
720 If you need to specify multiple commands, create a shell script.
722 \item[Block Checksum = {\it yes/no}]
724 You may turn off the Block Checksum (CRC32) code that Bacula uses when
725 writing blocks to a Volume. Doing so can reduce the Storage daemon CPU usage
726 slightly. It will also permit Bacula to read a Volume that has corrupted
729 The default is {\bf yes} -- i.e. the checksum is computed on write and
732 \textbf{We do not recommend to turn this off} particularly on older tape
733 drives or for disk Volumes where doing so may allow corrupted data to go
736 \item [Minimum block size = {\it size-in-bytes}]
737 \index[sd]{Minimum block size}
738 \index[sd]{Directive!Minimum block size}
739 On most modern tape drives, you will not need or want to specify this
740 directive, and if you do so, it will be to make Bacula use fixed block
741 sizes. This statement applies only to non-random access devices (e.g.
742 tape drives). Blocks written by the storage daemon to a non-random
743 archive device will never be smaller than the given {\bf size-in-bytes}.
744 The Storage daemon will attempt to efficiently fill blocks with data
745 received from active sessions but will, if necessary, add padding to a
746 block to achieve the required minimum size.
748 To force the block size to be fixed, as is the case for some non-random
749 access devices (tape drives), set the {\bf Minimum block size} and the
750 {\bf Maximum block size} to the same value (zero included). The default
751 is that both the minimum and maximum block size are zero and the default
752 block size is 64,512 bytes.
754 For example, suppose you want a fixed block size of 100K bytes, then you
760 Minimum block size = 100K
761 Maximum block size = 100K
766 Please note that if you specify a fixed block size as shown above, the tape
767 drive must either be in variable block size mode, or if it is in fixed block
768 size mode, the block size (generally defined by {\bf mt}) {\bf must} be
769 identical to the size specified in Bacula -- otherwise when you attempt to
770 re-read your Volumes, you will get an error.
772 If you want the block size to be variable but with a 64K minimum and 200K
773 maximum (and default as well), you would specify:
778 Minimum block size = 64K
779 Maximum blocksize = 200K
784 \item [Maximum block size = {\it size-in-bytes}]
785 \index[sd]{Maximum block size}
786 \index[sd]{Directive!Maximum block size}
787 On most modern tape drives, you will not need to specify this directive.
788 If you do so, it will most likely be to use fixed block sizes (see
789 Minimum block size above). The Storage daemon will always attempt to
790 write blocks of the specified {\bf size-in-bytes} to the archive device.
791 As a consequence, this statement specifies both the default block size
792 and the maximum block size. The size written never exceed the given
793 {\bf size-in-bytes}. If adding data to a block would cause it to exceed
794 the given maximum size, the block will be written to the archive device,
795 and the new data will begin a new block.
797 If no value is specified or zero is specified, the Storage daemon will
798 use a default block size of 64,512 bytes (126 * 512).
800 The maximum {\bf size-in-bytes} possible is 2,000,000.
802 \item [Hardware End of Medium = {\it yes\vb{}no}]
803 \index[sd]{Hardware End of Medium}
804 \index[sd]{Directive!Hardware End of Medium}
805 If {\bf No}, the archive device is not required to support end of medium
806 ioctl request, and the storage daemon will use the forward space file
807 function to find the end of the recorded data. If {\bf Yes}, the archive
808 device must support the {\tt ioctl} {\tt MTEOM} call, which will position
809 the tape to the end of the recorded data. In addition, your SCSI driver must
810 keep track of the file number on the tape and report it back correctly by
811 the {\bf MTIOCGET} ioctl. Note, some SCSI drivers will correctly forward
812 space to the end of the recorded data, but they do not keep track of the
813 file number. On Linux machines, the SCSI driver has a {\bf fast-eod}
814 option, which if set will cause the driver to lose track of the file
815 number. You should ensure that this option is always turned off using the
818 Default setting for Hardware End of Medium is {\bf Yes}. This function is
819 used before appending to a tape to ensure that no previously written data is
820 lost. We recommend if you have a non-standard or unusual tape drive that you
821 use the {\bf btape} program to test your drive to see whether or not it
822 supports this function. All modern (after 1998) tape drives support this
825 \item [Fast Forward Space File = {\it yes\vb{}no}]
826 \index[sd]{Fast Forward Space File}
827 \index[sd]{Directive!Fast Forward Space File}
828 If {\bf No}, the archive device is not required to support keeping track of
829 the file number ({\bf MTIOCGET} ioctl) during forward space file. If {\bf
830 Yes}, the archive device must support the {\tt ioctl} {\tt MTFSF} call, which
831 virtually all drivers support, but in addition, your SCSI driver must keep
832 track of the file number on the tape and report it back correctly by the
833 {\bf MTIOCGET} ioctl. Note, some SCSI drivers will correctly forward space,
834 but they do not keep track of the file number or more seriously, they do not
835 report end of medium.
837 Default setting for Fast Forward Space File is {\bf Yes}.
839 \item [Use MTIOCGET = {\it yes\vb{}no}]
840 \index[sd]{Use MTIOCGET}
841 \index[sd]{Directive!Use MTIOCGET}
842 If {\bf No}, the operating system is not required to support keeping track of
843 the file number and reporting it in the ({\bf MTIOCGET} ioctl). The default
844 is {\bf Yes}. If you must set this to No, Bacula will do the proper file
845 position determination, but it is very unfortunate because it means that
846 tape movement is very inefficient.
847 Fortunately, this operation system deficiency seems to be the case only
848 on a few *BSD systems. Operating systems known to work correctly are
849 Solaris, Linux and FreeBSD.
851 \item [BSF at EOM = {\it yes\vb{}no}]
852 \index[sd]{BSF at EOM}
853 \index[sd]{Directive!BSF at EOM}
854 If {\bf No}, the default, no special action is taken by Bacula with the End
855 of Medium (end of tape) is reached because the tape will be positioned after
856 the last EOF tape mark, and Bacula can append to the tape as desired.
857 However, on some systems, such as FreeBSD, when Bacula reads the End of
858 Medium (end of tape), the tape will be positioned after the second EOF tape
859 mark (two successive EOF marks indicated End of Medium). If Bacula appends
860 from that point, all the appended data will be lost. The solution for such
861 systems is to specify {\bf BSF at EOM} which causes Bacula to backspace over
862 the second EOF mark. Determination of whether or not you need this directive
863 is done using the {\bf test} command in the {\bf btape} program.
865 \item [TWO EOF = {\it yes\vb{}no}]
867 \index[sd]{Directive!TWO EOF}
868 If {\bf Yes}, Bacula will write two end of file marks when terminating a
869 tape -- i.e. after the last job or at the end of the medium. If {\bf No},
870 the default, Bacula will only write one end of file to terminate the tape.
872 \item [Backward Space Record = {\it yes\vb{}no}]
873 \index[sd]{Backward Space Record}
874 \index[sd]{Directive!Backward Space Record}
875 If {\it Yes}, the archive device supports the {\tt MTBSR ioctl} to backspace
876 records. If {\it No}, this call is not used and the device must be rewound
877 and advanced forward to the desired position. Default is {\bf Yes} for non
878 random-access devices. This function if enabled is used at the end of a
879 Volume after writing the end of file and any ANSI/IBM labels to determine
880 whether or not the last block was written correctly. If you turn this
881 function off, the test will not be done. This causes no harm as the re-read
882 process is precautionary rather than required.
884 \item [Backward Space File = {\it yes\vb{}no}]
885 \index[sd]{Backward Space File}
886 \index[sd]{Directive!Backward Space File}
887 If {\it Yes}, the archive device supports the {\bf MTBSF} and {\bf MTBSF
888 ioctl}s to backspace over an end of file mark and to the start of a file. If
889 {\it No}, these calls are not used and the device must be rewound and
890 advanced forward to the desired position. Default is {\bf Yes} for non
891 random-access devices.
893 \item [Forward Space Record = {\it yes\vb{}no}]
894 \index[sd]{Forward Space Record}
895 \index[sd]{Directive!Forward Space Record}
896 If {\it Yes}, the archive device must support the {\bf MTFSR ioctl} to
897 forward space over records. If {\bf No}, data must be read in order to
898 advance the position on the device. Default is {\bf Yes} for non
899 random-access devices.
901 \item [Forward Space File = {\it yes\vb{}no}]
902 \index[sd]{Forward Space File}
903 \index[sd]{Directive!Forward Space File}
904 If {\bf Yes}, the archive device must support the {\tt MTFSF ioctl} to
905 forward space by file marks. If {\it No}, data must be read to advance the
906 position on the device. Default is {\bf Yes} for non random-access devices.
908 \item [Offline On Unmount = {\it yes\vb{}no}]
909 \index[sd]{Offline On Unmount}
910 \index[sd]{Directive!Offline On Unmount}
911 The default for this directive is {\bf No}. If {\bf Yes} the archive device
912 must support the {\tt MTOFFL ioctl} to rewind and take the volume offline. In
913 this case, Bacula will issue the offline (eject) request before closing the
914 device during the {\bf unmount} command. If {\bf No} Bacula will not attempt
915 to offline the device before unmounting it. After an offline is issued, the
916 cassette will be ejected thus {\bf requiring operator intervention} to
917 continue, and on some systems require an explicit load command to be issued
918 ({\bf mt -f /dev/xxx load}) before the system will recognize the tape. If you
919 are using an autochanger, some devices require an offline to be issued prior
920 to changing the volume. However, most devices do not and may get very
923 If you are using a Linux 2.6 kernel or other OSes
924 such as FreeBSD or Solaris, the Offline On Unmount will leave the drive
925 with no tape, and Bacula will not be able to properly open the drive and
926 may fail the job. For more information on this problem, please see the
927 \borgxrlink{description of Offline On Unmount}{NoTapeInDrive}{problems}{subsection}
928 in the \borgxrlink{Tape Testing}{TapeTestingChapter}{problems}{chapter} of the \problemsman{}.
930 \item [Maximum Concurrent Jobs = \lt{}number\gt{}]
931 \index[sd]{Device Maximum Concurrent Jobs}
932 \index[sd]{Directive!Device Maximum Concurrent Jobs}
933 \index[sd]{Directive!New in 3.0.3}
934 where \lt{}number\gt{} is the maximum number of Jobs that can run
935 concurrently on a specified Device. Using this directive, it is possible
936 to have different Jobs using multiple drives, because when
937 the Maximum Concurrent Jobs limit is
938 reached, the Storage Daemon will start new Jobs on any other available
939 compatible drive. This facilitates writing to multiple drives with
940 multiple Jobs that all use the same Pool.
942 \item [Maximum Volume Size = {\it size}]
943 \index[sd]{Maximum Volume Size}
944 \index[sd]{Directive!Maximum Volume Size}
945 No more than {\bf size} bytes will be written onto a given volume on the
946 archive device. This directive is used mainly in testing Bacula to
947 simulate a small Volume. It can also be useful if you wish to limit the
948 size of a File Volume to say less than 2GB of data. In some rare cases
949 of really antiquated tape drives that do not properly indicate when the
950 end of a tape is reached during writing (though I have read about such
951 drives, I have never personally encountered one). Please note, this
952 directive is deprecated (being phased out) in favor of the {\bf Maximum
953 Volume Bytes} defined in the Director's configuration file.
955 \item [Maximum File Size = {\it size}]
956 \index[sd]{Maximum File Size}
957 \index[sd]{Directive!Maximum File Size}
958 No more than {\bf size} bytes will be written into a given logical file
959 on the volume. Once this size is reached, an end of file mark is
960 written on the volume and subsequent data are written into the next
961 file. Breaking long sequences of data blocks with file marks permits
962 quicker positioning to the start of a given stream of data and can
963 improve recovery from read errors on the volume. The default is one
964 Gigabyte. This directive creates EOF marks only on tape media.
965 However, regardless of the medium type (tape, disk, USB ...) each time
966 a the Maximum File Size is exceeded, a record is put into the catalog
967 database that permits seeking to that position on the medium for
968 restore operations. If you set this to a small value (e.g. 1MB),
969 you will generate lots of database records (JobMedia) and may
970 significantly increase CPU/disk overhead.
972 If you are configuring an LTO-3 or LTO-4 tape, you probably will
973 want to set the {\bf Maximum File Size} to 2GB to avoid making
974 the drive stop to write an EOF mark.
976 Note, this directive does not limit the size of Volumes that Bacula
977 will create regardless of whether they are tape or disk volumes. It
978 changes only the number of EOF marks on a tape and the number of
979 block positioning records (see below) that are generated. If you
980 want to limit the size of all Volumes for a particular device, use
981 the {\bf Maximum Volume Size} directive (above), or use the
982 {\bf Maximum Volume Bytes} directive in the Director's Pool resource,
983 which does the same thing but on a Pool (Volume) basis.
985 \item [Block Positioning = {\it yes\vb{}no}]
986 \index[sd]{Block Positioning}
987 \index[sd]{Directive!Block Positioning}
988 This directive tells Bacula not to use block positioning when doing restores.
989 Turning this directive off can cause Bacula to be {\bf extremely} slow
990 when restoring files. You might use this directive if you wrote your
991 tapes with Bacula in variable block mode (the default), but your drive
992 was in fixed block mode. The default is {\bf yes}.
994 \item [Maximum Network Buffer Size = {\it bytes}]
995 \index[sd]{Maximum Network Buffer Size}
996 \index[sd]{Directive!Maximum Network Buffer Size}
997 where {\it bytes} specifies the initial network buffer size to use with the
998 File daemon. This size will be adjusted down if it is too large until
999 it is accepted by the OS. Please use care in setting this value since if
1000 it is too large, it will be trimmed by 512 bytes until the OS is happy,
1001 which may require a large number of system calls. The default value is
1004 The default size was chosen to be relatively large but not too big in
1005 the case that you are transmitting data over Internet. It is clear that
1006 on a high speed local network, you can increase this number and improve
1007 performance. For example, some users have found that if you use a value
1008 of 65,536 bytes they get five to ten times the throughput. Larger values for
1009 most users don't seem to improve performance. If you are interested
1010 in improving your backup speeds, this is definitely a place to
1011 experiment. You will probably also want to make the corresponding change
1012 in each of your File daemons conf files.
1015 \item [Maximum Spool Size = {\it bytes}]
1016 \index[sd]{Maximum Spool Size}
1017 \index[sd]{Directive!Maximum Spool Size}
1018 where the bytes specify the maximum spool size for all jobs that are
1019 running. The default is no limit.
1021 \item [Maximum Job Spool Size = {\it bytes}]
1022 \index[sd]{Maximum Job Spool Size}
1023 \index[sd]{Directive!Maximum Job Spool Size}
1024 where the bytes specify the maximum spool size for any one job that is
1025 running. The default is no limit.
1026 This directive is implemented only in version 1.37 and later.
1028 \item [Spool Directory = {\it directory}]
1029 \index[sd]{Spool Directory}
1030 \index[sd]{Directive!Spool Directory}
1031 specifies the name of the directory to be used to store the spool files for
1032 this device. This directory is also used to store temporary part files when
1033 writing to a device that requires mount (USB). The default is to use the
1039 \section{Edit Codes for Mount and Unmount Directives}
1040 \index[general]{Directives!Edit Codes}
1041 \index[general]{Edit Codes for Mount and Unmount Directives }
1043 Before submitting the {\bf Mount Command}, {\bf Unmount Command},
1044 or {\bf Free Space Command} directives
1045 to the operating system, Bacula performs character substitution of the
1046 following characters:
1051 %a = Archive device name
1052 %e = erase (set if cannot mount and first part)
1059 \section{Devices that require a mount (USB)}
1060 \index[general]{Devices that require a mount (USB)}
1062 All the directives in this section are implemented only in
1063 Bacula version 1.37 and later and hence are available in version 1.38.6.
1066 "Requires Mount", "Mount Point", "Mount Command", and "Unmount Command"
1067 apply to removable filesystems such as USB.
1071 \item [Requires Mount = {\it yes\vb{}no}]
1072 \index[sd]{Requires Mount}
1073 \index[sd]{Directive!Requires Mount}
1074 You must set this directive to {\bf yes} for removable devices such as
1075 USB unless they are automounted, and to {\bf no} for all other devices
1076 (tapes/files). This directive indicates if the device requires to be
1077 mounted to be read, and if it must be written in a special way. If it
1078 set, {\bf Mount Point}, {\bf Mount Command}, and {\bf Unmount Command}
1079 directives must also be defined.
1081 \item [Mount Point = {\it directory}]
1082 \index[sd]{Mount Point}
1083 \index[sd]{Directive!Mount Point}
1084 Directory where the device can be mounted.
1086 \item [Mount Command = {\it name-string}]
1087 \index[sd]{Mount Command}
1088 \index[sd]{Directive!Mount Command}
1089 Command that must be executed to mount the device. Before the command is
1090 executed, \%a is replaced with the Archive Device, and \%m with the Mount
1093 Most frequently, you will define it as follows:
1097 Mount Command = "/bin/mount -t iso9660 -o ro %a %m"
1101 For some media, you may need multiple commands. If so, it is recommended
1102 that you use a shell script instead of putting them all into the Mount
1103 Command. For example, instead of this:
1107 Mount Command = "/usr/local/bin/mymount"
1111 Where that script contains:
1116 ndasadmin enable -s 1 -o w
1118 mount /dev/ndas-00323794-0p1 /backup
1122 Similar consideration should be given to all other Command parameters.
1124 \item [Unmount Command = {\it name-string}]
1125 \index[sd]{Unmount Command}
1126 \index[sd]{Directive!Unmount Command}
1127 Command that must be executed to unmount the device. Before the command is
1128 executed, \%a is replaced with the Archive Device, and \%m with the Mount
1131 Most frequently, you will define it as follows:
1135 Unmount Command = "/bin/umount %m"
1139 If you need to specify multiple commands, create a shell script.
1143 %% This pulls in the Autochanger resource from another file.
1144 \label{AutochangerRes}
1145 \label{AutochangerResource1}
1146 \input{autochangerres}
1148 \section{Capabilities}
1149 \index[general]{Capabilities}
1153 \item [Label Media = {\it yes\vb{}no}]
1154 \index[general]{Label Media}
1155 \index[sd]{Label Media}
1156 \index[sd]{Directive!Label Media}
1157 If {\bf Yes}, permits this device to automatically label blank media
1158 without an explicit operator command. It does so by using an internal
1159 algorithm as defined on the \ilink{Label Format}{Label} record in each
1160 Pool resource. If this is {\bf No} as by default, Bacula will label
1161 tapes only by specific operator command ({\bf label} in the Console) or
1162 when the tape has been recycled. The automatic labeling feature is most
1163 useful when writing to disk rather than tape volumes.
1165 \item [Automatic mount = {\it yes\vb{}no}]
1166 \index[sd]{Automatic mount}
1167 \index[sd]{Directive!Automatic mount}
1168 If {\bf Yes} (the default), permits the daemon to examine the device to
1169 determine if it contains a Bacula labeled volume. This is done
1170 initially when the daemon is started, and then at the beginning of each
1171 job. This directive is particularly important if you have set
1172 {\bf Always Open = no} because it permits Bacula to attempt to read the
1173 device before asking the system operator to mount a tape. However,
1174 please note that the tape must be mounted before the job begins.
1178 \section{Messages Resource}
1179 \label{MessagesResource1}
1180 \index[general]{Resource!Messages}
1181 \index[general]{Messages Resource}
1183 For a description of the Messages Resource, please see the
1184 \ilink{Messages Resource}{MessagesChapter} Chapter of this
1187 \section{Sample Storage Daemon Configuration File}
1188 \label{SampleConfiguration}
1189 \index[general]{File!Sample Storage Daemon Configuration}
1190 \index[general]{Sample Storage Daemon Configuration File}
1192 A example Storage Daemon configuration file might be the following:
1197 # Default Bacula Storage Daemon Configuration file
1199 # For Bacula release 1.37.2 (07 July 2005) -- gentoo 1.4.16
1201 # You may need to change the name of your tape drive
1202 # on the "Archive Device" directive in the Device
1203 # resource. If you change the Name and/or the
1204 # "Media Type" in the Device resource, please ensure
1205 # that bacula-dir.conf has corresponding changes.
1207 Storage { # definition of myself
1210 WorkingDirectory = "$HOME/bacula/bin/working"
1211 Pid Directory = "$HOME/bacula/bin/working"
1212 Maximum Concurrent Jobs = 20
1215 # List Directors who are permitted to contact Storage daemon
1219 Password = "ZF9Ctf5PQoWCPkmR3s4atCB0usUPg+vWWyIo2VS5ti6k"
1222 # Restricted Director, used by tray-monitor to get the
1223 # status of the storage daemon
1227 Password = "9usxgc307dMbe7jbD16v0PXlhD64UVasIDD0DH2WAujcDsc6"
1231 # Devices supported by this Storage daemon
1232 # To connect, the Director's bacula-dir.conf must have the
1233 # same Name and MediaType.
1239 Changer Command = "/home/kern/bacula/bin/mtx-changer %c %o %S %a %d"
1240 Changer Device = /dev/sg0
1246 Media Type = DLT-8000
1247 Archive Device = /dev/nst0
1248 AutomaticMount = yes; # when device opened, read it
1250 RemovableMedia = yes;
1253 Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
1259 Media Type = DLT-8000
1260 Archive Device = /dev/nst1
1261 AutomaticMount = yes; # when device opened, read it
1263 RemovableMedia = yes;
1266 Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
1271 Media Type = DLT8000
1272 Archive Device = /dev/nst0
1273 AutomaticMount = yes; # when device opened, read it
1275 RemovableMedia = yes;
1279 # Media Type = DDS-2
1280 # Archive Device = /dev/nst0
1281 # AutomaticMount = yes; # when device opened, read it
1283 # RemovableMedia = yes;
1287 # Media Type = Floppy
1288 # Archive Device = /mnt/floppy
1289 # RemovableMedia = yes;
1290 # Random Access = Yes;
1291 # AutomaticMount = yes; # when device opened, read it
1295 # Name = FileStorage
1297 # Archive Device = /tmp
1298 # LabelMedia = yes; # lets Bacula label unlabeled media
1299 # Random Access = Yes;
1300 # AutomaticMount = yes; # when device opened, read it
1301 # RemovableMedia = no;
1305 # A very old Exabyte with no end of media detection
1308 # Name = "Exabyte 8mm"
1309 # Media Type = "8mm"
1310 # Archive Device = /dev/nst0
1311 # Hardware end of medium = No;
1312 # AutomaticMount = yes; # when device opened, read it
1314 # RemovableMedia = yes;
1317 # Send all messages to the Director,
1318 # mount messages also are sent to the email address
1322 director = rufus-dir = all
1323 operator = root = mount