4 \section*{Autochangers Support}
5 \label{_ChapterStart18}
6 \index[general]{Support!Autochangers }
7 \index[general]{Autochangers Support }
8 \addcontentsline{toc}{section}{Autochangers Support}
10 \subsection*{Autochangers -- General}
11 \index[general]{General!Autochangers -- }
12 \index[general]{Autochangers -- General }
13 \addcontentsline{toc}{subsection}{Autochangers -- General}
15 Bacula provides autochanger support for reading and writing tapes. In
16 order to work with an autochanger, Bacula requires three things, each of
17 which is explained in more detail after this list:
20 \item A script that actually controls the autochanger according to commands
21 sent by Bacula. We furnish such a script that works with {\bf mtx} found in
22 the {\bf depkgs} distribution. This script works only with single drive
24 \item That each Volume (tape) to be used must be defined in the Catalog and
25 have a Slot number assigned to it so that Bacula knows where the Volume is in
26 the autochanger. This is generally done with the {\bf label} command. See
27 below for more details. You must pre-label the tapes manually before
29 \item Modifications to your Storage daemon's Device configuration resource to
30 identify that the device is a changer, as well as a few other parameters.
31 \item You should also modify your Storage resource definition in the
32 Director's configuration file so that you are automatically prompted for the
33 Slot when labeling a Volume.
34 \item You need to ensure that your Storage daemon (if not running as root)
35 has access permissions to both the tape drive and the control device.
38 In version 1.37, there is a new \ilink{Autochanger
39 resource}{AutochangerRes} that permits you to group Device resources thus
40 creating a multi-drive autochanger. If you have a multi-drive autochanger,
41 you must use this new resource. If you have a single drive autochanger,
42 it is recommended, but not required.
44 Bacula uses its own {\bf mtx-changer} script to interface with a program
45 that actually does the tape changing. Thus in principle, {\bf mtx-changer}
46 can be adapted to function with any autochanger program. The current
47 version of {\bf mtx-changer} works with the {\bf mtx} program. However,
48 FreeBSD users have provided a script in the {\bf examples/autochangers}
49 directory that allows Bacula to use the {\bf chio} program.
51 Bacula also supports autochangers with barcode
52 readers. This support includes two Console commands: {\bf label barcodes}
53 and {\bf update slots}. For more details on these commands, see the ``Barcode
54 Support'' section below.
56 Current Bacula autochanger support does not include cleaning, stackers, or
57 silos. However, under certain conditions, you may be able to make Bacula
58 work with stackers (gravity feed and such). Support for multi-drive
59 autochangers requires the \ilink{Autochanger resource}{AutochangerRes}
60 introduced in version 1.37. This resource is also recommended for single
63 In principle, if {\bf mtx} will operate your changer correctly, then it is
64 just a question of adapting the {\bf mtx-changer} script (or selecting one
65 already adapted) for proper interfacing. You can find a list of autochangers
66 supported by {\bf mtx} at the following link:
67 \elink{http://mtx.badtux.net/compatibility.php}
68 {http://mtx.badtux.net/compatibility.php}.
69 The home page for the {\bf mtx} project can be found at:
70 \elink{http://mtx.badtux.net/}{http://mtx.badtux.net/}.
72 If you are having troubles, please use the {\bf auto} command in the {\bf
73 btape} program to test the functioning of your autochanger with Bacula. When
74 Bacula is running, please remember that for many distributions (e.g. FreeBSD,
75 Debian, ...) the Storage daemon runs as {\bf bacula.tape} rather than {\bf
76 root.root}, so you will need to ensure that the Storage daemon has sufficient
77 permissions to access the autochanger.
80 \subsection*{Knowing What SCSI Devices You Have}
81 \index[general]{Have!Knowing What SCSI Devices You }
82 \index[general]{Knowing What SCSI Devices You Have }
83 \index[general]{SCSI devices}
84 \index[general]{devices!SCSI}
85 \addcontentsline{toc}{subsection}{Knowing What SCSI Devices You Have}
95 to see what SCSI devices you have available. You can also:
99 cat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices
103 to find out how to specify their control address ({\bf /dev/sg0} for the
104 first, {\bf /dev/sg1} for the second, ...) on the {\bf Changer Device = }
107 Under FreeBSD, you can use:
115 To list the SCSI devices as well as the {\bf /dev/passn} that you will use on
116 the Bacula {\bf Changer Device = } directive.
118 Please check that your Storage daemon has permission to access this
123 \subsection*{Example Scripts}
124 \index[general]{Scripts!Example }
125 \index[general]{Example Scripts }
126 \addcontentsline{toc}{subsection}{Example Scripts}
128 Please read the sections below so that you understand how autochangers work
129 with Bacula. Although we supply a default {\bf mtx-changer} script, your
130 autochanger may require some additional changes. If you want to see examples
131 of configuration files and scripts, please look in the {\bf
132 \lt{}bacula-src\gt{}/examples/devices} directory where you will find an
133 example {\bf HP-autoloader.conf} Bacula Device resource, and several {\bf
134 mtx-changer} scripts that have been modified to work with different
140 \index[general]{Slots }
141 \addcontentsline{toc}{subsection}{Slots}
143 To properly address autochangers, Bacula must know which Volume is in each
144 {\bf slot} of the autochanger. Slots are where the changer cartridges reside
145 when not loaded into the drive. Bacula numbers these slots from one to the
146 number of cartridges contained in the autochanger.
148 Bacula will not automatically use a Volume in your autochanger unless it is
149 labeled and the slot number is stored in the catalog and the Volume is marked
150 as InChanger. For each Volume in your
151 changer, you will, using the Console program, assign a slot. This information
152 is kept in {\bf Bacula's} catalog database along with the other data for the
153 volume. If no slot is given, or the slot is set to zero, Bacula will not
154 attempt to use the autochanger even if all the necessary configuration records
155 are present. In addition, the console {\bf mount} command does not cause
156 Bacula to operate the autochanger, it only tells Bacula to read any tape that
159 You can check if the Slot number and InChanger flag are set by doing a:
164 in the Console program.
167 \subsection*{Multiple Devices}
168 \index[general]{Devices!Multiple }
169 \index[general]{Multiple Devices }
170 \addcontentsline{toc}{subsection}{Multiple Devices}
172 Some autochangers have more than one read/write device (drive). The
174 \ilink{Autochanger resource}{AutochangerRes} introduced in version
175 1.37 permits you to group Device resources, where each device
176 represents a drive. The Director may still reference the Devices (drives)
177 directly, but doing so, bypasses the proper functioning of the
178 drives together. Instead, the Director (in the Storage resource)
179 should reference the Autochanger resource name. Doing so permits
180 the Storage daemon to ensure that only one drive uses the mtx-changer
181 script at a time, and also that two drives don't reference the
184 Multi-drive requires the use of the {\bf
185 Drive Index} directive in the Device resource of the Storage daemon's
186 configuration file. Drive numbers or the Device Index are numbered beginning
187 at zero, which is the default. To use the second Drive in an autochanger, you
188 need to define a second Device resource and set the Drive Index to 1 for
189 that device. In general, the second device will have the same {\bf Changer
190 Device} (control channel) as the first drive, but a different {\bf Archive
193 \label{ConfigRecords}
194 \subsection*{Device Configuration Records}
195 \index[general]{Records!Device Configuration }
196 \index[general]{Device Configuration Records }
197 \addcontentsline{toc}{subsection}{Device Configuration Records}
199 Configuration of autochangers within Bacula is done in the Device resource of
200 the Storage daemon. Four records: {\bf Autochanger}, {\bf Changer Device},
201 {\bf Changer Command}, and {\bf Maximum Changer Wait} control how Bacula uses
204 These four records, permitted in {\bf Device} resources, are described in
205 detail below. Note, however, that the {\bf Changer Device} and the
206 {\bf Changer Command} directives are not needed in the Device resource
207 if they are present in the {\bf Autochanger} resource.
211 \item [Autochanger = {\it Yes|No} ]
212 \index[sd]{Autochanger }
213 The {\bf Autochanger} record specifies that the current device is or is not
214 an autochanger. The default is {\bf no}.
216 \item [Changer Device = \lt{}device-name\gt{}]
217 \index[sd]{Changer Device }
218 In addition to the Archive Device name, you must specify a {\bf Changer
219 Device} name. This is because most autochangers are controlled through a
220 different device than is used for reading and writing the cartridges. For
221 example, on Linux, one normally uses the generic SCSI interface for
222 controlling the autochanger, but the standard SCSI interface for reading and
223 writing the tapes. On Linux, for the {\bf Archive Device = /dev/nst0}, you
224 would typically have {\bf Changer Device = /dev/sg0}. Note, some of the more
225 advanced autochangers will locate the changer device on {\bf /dev/sg1}. Such
226 devices typically have several drives and a large number of tapes.
228 On FreeBSD systems, the changer device will typically be on {\bf /dev/pass0}
229 through {\bf /dev/passn}.
231 On Solaris, the changer device will typically be some file under {\bf
234 Please ensure that your Storage daemon has permission to access this
237 \item [Changer Command = \lt{}command\gt{}]
238 \index[sd]{Changer Command }
239 This record is used to specify the external program to call and what
240 arguments to pass to it. The command is assumed to be a standard program or
241 shell script that can be executed by the operating system. This command is
242 invoked each time that Bacula wishes to manipulate the autochanger. The
243 following substitutions are made in the {\bf command} before it is sent to
244 the operating system for execution:
249 %a = archive device name
250 %c = changer device name
251 %d = changer drive index base 0
254 %o = command (loaded, load, or unload)
261 An actual example for using {\bf mtx} with the {\bf mtx-changer} script (part
262 of the Bacula distribution) is:
266 Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
270 Where you will need to adapt the {\bf /etc/bacula} to be the actual path on
271 your system where the mtx-changer script resides. Details of the three
272 commands currently used by Bacula (loaded, load, unload) as well as the
273 output expected by Bacula are give in the {\bf Bacula Autochanger Interface}
276 \item [Maximum Changer Wait = \lt{}time\gt{}]
277 \index[sd]{Maximum Changer Wait }
278 This record is used to define the maximum amount of time that Bacula
279 will wait for an autoloader to respond to a command (e.g. load). The
280 default is set to 120 seconds. If you have a slow autoloader you may
281 want to set it longer.
283 If the autoloader program fails to respond in this time, it will be killed
284 and Bacula will request operator intervention.
286 \item [Drive Index = \lt{}number\gt{}]
287 \index[sd]{Drive Index }
288 This record allows you to tell Bacula to use the second or subsequent
289 drive in an autochanger with multiple drives. Since the drives are
290 numbered from zero, the second drive is defined by
299 To use the second drive, you need a second Device resource definition in the
300 Bacula configuration file. See the Multiple Drive section above in this
301 chapter for more information.
304 In addition, for proper functioning of the Autochanger, you must
305 define an Autochanger resource.
306 \input{autochangerres}
309 \subsection*{An Example Configuration File}
310 \index[general]{Example Configuration File }
311 \index[general]{File!Example Configuration }
312 \addcontentsline{toc}{subsection}{Example Configuration File}
314 The following two resources implement an autochanger:
321 Changer Device = /dev/sg0
322 Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
328 Archive Device = /dev/nst0 # Normal archive device
331 AutomaticMount = yes;
333 Mount Anonymous Volumes = no;
338 where you will adapt the {\bf Archive Device}, the {\bf Changer Device}, and
339 the path to the {\bf Changer Command} to correspond to the values used on your
343 \label{SpecifyingSlots}
344 \subsection*{Specifying Slots When Labeling}
345 \index[general]{Specifying Slots When Labeling }
346 \index[general]{Labeling!Specifying Slots When }
347 \addcontentsline{toc}{subsection}{Specifying Slots When Labeling}
349 If you add an {\bf Autochanger = yes} record to the Storage resource in your
350 Director's configuration file, the Bacula Console will automatically prompt
351 you for the slot number when the Volume is in the changer when
352 you {\bf add} or {\bf label} tapes for that Storage device. If your
353 {\bf mtx-changer} script is properly installed, Bacula will automatically
354 load the correct tape during the label command.
357 {\bf Autochanger = yes} in the Storage daemon's Device resource
358 as we have described above in
359 order for the autochanger to be used. Please see the
360 \ilink{Storage Resource}{Autochanger1} in the Director's chapter
362 \ilink{Device Resource}{Autochanger} in the Storage daemon
363 chapter for more details on these records.
365 Thus all stages of dealing with tapes can be totally automated. It is also
366 possible to set or change the Slot using the {\bf update} command in the
367 Console and selecting {\bf Volume Parameters} to update.
369 Even though all the above configuration statements are specified and correct,
370 Bacula will attempt to access the autochanger only if a {\bf slot} is non-zero
371 in the catalog Volume record (with the Volume name).
373 If your autochanger has barcode labels, you can label all the Volumes in
374 your autochanger one after another by using the {\bf label barcodes} command.
375 For each tape in the changer containing a barcode, Bacula will mount the tape
376 and then label it with the same name as the barcode. An appropriate Media
377 record will also be created in the catalog. Any barcode that begins with the
378 same characters as specified on the ``CleaningPrefix=xxx'' command, will be
379 treated as a cleaning tape, and will not be labeled. For example with:
381 Please note that Volumes must be pre-labeled to be automatically used in
382 the autochanger during a backup. If you do not have a barcode reader, this
383 is done manually (or via a script).
389 Cleaning Prefix = "CLN"
394 Any slot containing a barcode of CLNxxxx will be treated as a cleaning tape
395 and will not be mounted.
399 \subsection*{Dealing with Multiple Magazines}
400 \index[general]{Dealing with Multiple Magazines }
401 \index[general]{Magazines!Dealing with Multiple }
402 \addcontentsline{toc}{subsection}{Dealing with Multiple Magazines}
404 If you have several magazines or if you insert or remove cartridges from a
405 magazine, you should notify Bacula of this. By doing so, Bacula will as
406 a preference, use Volumes that it knows to be in the autochanger before
407 accessing Volumes that are not in the autochanger. This prevents unneeded
408 operator intervention.
410 If your autochanger has barcodes (machine readable tape labels), the task of
411 informing Bacula is simple. Every time, you change a magazine, or add or
412 remove a cartridge from the magazine, simply do
420 in the Console program. This will cause Bacula to request the autochanger to
421 return the current Volume names in the magazine. This will be done without
422 actually accessing or reading the Volumes because the barcode reader does this
423 during inventory when the autochanger is first turned on. Bacula will ensure
424 that any Volumes that are currently marked as being in the magazine are marked
425 as no longer in the magazine, and the new list of Volumes will be marked as
426 being in the magazine. In addition, the Slot numbers of the Volumes will be
427 corrected in Bacula's catalog if they are incorrect (added or moved).
429 If you do not have a barcode reader on your autochanger, you have several
433 \item You can manually set the Slot and InChanger flag using the {\bf update
434 volume} command in the Console (quite painful).
435 \item You can issue a
443 command that will cause Bacula to read the label on each of the cartridges in
444 the magazine in turn and update the information (Slot, InChanger flag) in the
445 catalog. This is quite effective but does take time to load each cartridge
446 into the drive in turn and read the Volume label.
447 \item You can modify the mtx-changer script so that it simulates an
448 autochanger with barcodes. See below for more details.
453 \subsection*{Simulating Barcodes in your Autochanger}
454 \index[general]{Autochanger!Simulating Barcodes in your }
455 \index[general]{Simulating Barcodes in your Autochanger }
456 \addcontentsline{toc}{subsection}{Simulating Barcodes in your Autochanger}
458 You can simulate barcodes in your autochanger by making the {\bf mtx-changer}
459 script return the same information that an autochanger with barcodes would do.
460 This is done by commenting out the one and only line in the {\bf list)} case,
465 ${MTX} -f $ctl status | grep " *Storage Element [0-9]*:.*Full" | awk "{print \$3 \$4}" | sed "s/Full *\(:VolumeTag=\)*//"
469 at approximately line 99 by putting a \# in column one of that line, or by
470 simply deleting it. Then in its place add a new line that prints the contents
471 of a file. For example:
475 cat /etc/bacula/changer.volumes
479 Be sure to include a full path to the file, which can have any name. The
480 contents of the file must be of the following format:
491 Where the 1, 2, 3 are the slot numbers and Volume1, Volume2, ... are the
492 Volume names in those slots. You can have multiple files that represent the
493 Volumes in different magazines, and when you change magazines, simply copy the
494 contents of the correct file into your {\bf /etc/bacula/changer.volumes} file.
495 There is no need to stop and start Bacula when you change magazines, simply
496 put the correct data in the file, then run the {\bf update slots} command, and
497 your autochanger will appear to Bacula to be an autochanger with barcodes.
500 \subsection*{The Full Form of the Update Slots Command}
501 \index[general]{Full Form of the Update Slots Command }
502 \index[general]{Command!Full Form of the Update Slots }
503 \addcontentsline{toc}{subsection}{Full Form of the Update Slots Command}
505 If you change only one cartridge in the magazine, you may not want to scan all
506 Volumes, so the {\bf update slots} command (as well as the {\bf update slots
507 scan} command) has the additional form:
511 update slots=n1,n2,n3-n4, ...
515 where the keyword {\bf scan} can be appended or not. The n1,n2, ... represent
516 Slot numbers to be updated and the form n3-n4 represents a range of Slot
517 numbers to be updated (e.g. 4-7 will update Slots 4,5,6, and 7).
519 This form is particularly useful if you want to do a scan (time expensive) and
520 restrict the update to one or two slots.
522 For example, the command:
526 update slots=1,6 scan
530 will cause Bacula to load the Volume in Slot 1, read its Volume label and
531 update the Catalog. It will do the same for the Volume in Slot 6. The command:
540 will read the barcoded Volume names for slots 1,2,3 and 6 and make the
541 appropriate updates in the Catalog. If you don't have a barcode reader or have
542 not modified the mtx-changer script as described above, the above command will
543 not find any Volume names so will do nothing.
546 \subsection*{FreeBSD Issues}
547 \index[general]{Issues!FreeBSD }
548 \index[general]{FreeBSD Issues }
549 \addcontentsline{toc}{subsection}{FreeBSD Issues}
551 If you are having problems on FreeBSD when Bacula tries to select a tape, and
552 the message is {\bf Device not configured}, this is because FreeBSD has made
553 the tape device {\bf /dev/nsa1} disappear when there is no tape mounted in the
554 autochanger slot. As a consequence, Bacula is unable to open the device. The
555 solution to the problem is to make sure that some tape is loaded into the tape
556 drive before starting Bacula. This problem is corrected in Bacula versions
560 \ilink{ Tape Testing}{FreeBSDTapes} chapter of this manual for
561 {\bf important} information concerning your tape drive before doing the
563 \label{AutochangerTesting}
565 \subsection*{Testing the Autochanger and Adapting Your mtx-changer Script}
566 \index[general]{Testing the Autochanger and Adapting Your mtx-changer Script }
567 \index[general]{Script!Testing the Autochanger and Adapting Your mtx-changer }
568 \addcontentsline{toc}{subsection}{Testing the Autochanger and Adapting Your
571 Before attempting to use the autochanger with Bacula, it is preferable to
572 ``hand-test'' that the changer works. To do so, we suggest you do the
573 following commands (assuming that the {\bf mtx-changer} script is installed in
574 {\bf /etc/bacula/mtx-changer}):
578 \item [Make sure Bacula is not running.]
579 \index[sd]{Make sure Bacula is not running. }
581 \item [/etc/bacula/mtx-changer \ /dev/sg0 \ list \ 0 \ /dev/nst0 \ 0]
582 \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ list \ 0 \ /dev/nst0 \ 0
584 This command should print:
596 or one number per line for each slot that is occupied in your changer, and
597 the number should be terminated by a colon ({\bf :}). If your changer has
598 barcodes, the barcode will follow the colon. If an error message is printed,
599 you must resolve the problem (e.g. try a different SCSI control device name
600 if {\bf /dev/sg0} is incorrect. For example, on FreeBSD systems, the
601 autochanger SCSI control device is generally {\bf /dev/pass2}.
603 \item [/etc/bacula/mtx-changer \ /dev/sg0 \ slots \ 0 \ /dev/nst0 \ 0]
604 \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ slots \ 0 \ /dev/nst0 \ 0
606 This command should return the number of slots in your autochanger.
608 \item [/etc/bacula/mtx-changer \ /dev/sg0 \ unload \ ]
609 \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ unload \ }
610 If a tape is loaded, this should cause it to be unloaded.
612 \item [/etc/bacula/mtx-changer \ /dev/sg0 \ load \ 3 \ /dev/nst0 \ 0 ]
613 \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ load \ 3 \ /dev/nst0 \ 0
615 Assuming you have a tape in slot 3, it will be loaded into the read slot (0).
618 \item [/etc/bacula/mtx-changer \ /dev/sg0 \ loaded \ 0 \ /dev/nst0 \ 0]
619 \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ loaded \ 0 \ /dev/nst0 \
621 It should print ``3''
623 \item [/etc/bacula/mtx-changer \ /dev/sg0 \ unload]
624 \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ unload }
627 Once all the above commands work correctly, assuming that you have the right
628 {\bf Changer Command} in your configuration, Bacula should be able to operate
629 the changer. The only remaining area of problems will be if your autoloader
630 needs some time to get the tape loaded after issuing the command. After the
631 {\bf mtx-changer} script returns, Bacula will immediately rewind and read the
632 tape. If Bacula gets rewind I/O errors after a tape change, you will probably
633 need to insert a {\bf sleep 20} after the {\bf mtx} command, but be careful to
634 exit the script with a zero status by adding {\bf exit 0} after any additional
635 commands you add to the script. This is because Bacula checks the return
636 status of the script, which should be zero if all went well.
638 You can test whether or not you need a {\bf sleep} by putting the following
639 commands into a file and running it as a script:
644 /etc/bacula/mtx-changer /dev/sg0 unload
645 /etc/bacula/mtx-changer /dev/sg0 load 3
646 mt -f /dev/st0 rewind
651 If the above script runs, you probably have no timing problems. If it does not
652 run, start by putting a {\bf sleep 30} or possibly a {\bf sleep 60} in the
653 script just after the mtx-changer load command. If that works, then you should
654 move the sleep into the actual {\bf mtx-changer} script so that it will be
655 effective when Bacula runs.
657 A second problem that comes up with a small number of autochangers is that
658 they need to have the cartridge ejected before it can be removed. If this is
659 the case, the {\bf load 3} will never succeed regardless of how long you wait.
660 If this seems to be your problem, you can insert an eject just after the
661 unload so that the script looks like:
666 /etc/bacula/mtx-changer /dev/sg0 unload
667 mt -f /dev/st0 offline
668 /etc/bacula/mtx-changer /dev/sg0 load 3
669 mt -f /dev/st0 rewind
674 Obviously, if you need the {\bf offline} command, you should move it into the
675 mtx-changer script ensuring that you save the status of the {\bf mtx} command
676 or always force an {\bf exit 0} from the script, because Bacula checks the
677 return status of the script.
679 As noted earlier, there are several scripts in {\bf
680 \lt{}bacula-source\gt{}/examples/devices} that implement the above features,
681 so they may be a help to you in getting your script to work.
683 If Bacula complains ``Rewind error on /dev/nst0. ERR=Input/output error.'' you
684 most likely need more sleep time in your {\bf mtx-changer} before returning to
685 Bacula after a load command has been completed.
689 \subsection*{Using the Autochanger}
690 \index[general]{Using the Autochanger }
691 \index[general]{Autochanger!Using the }
692 \addcontentsline{toc}{subsection}{Using the Autochanger}
694 Let's assume that you have properly defined the necessary Storage daemon
695 Device records, and you have added the {\bf Autochanger = yes} record to the
696 Storage resource in your Director's configuration file.
698 Now you fill your autochanger with say six blank tapes.
700 What do you do to make Bacula access those tapes?
702 One strategy is to prelabel each of the tapes. Do so by starting Bacula, then
703 with the Console program, enter the {\bf label} command:
708 Connecting to Director rufus:8101
709 1000 OK: rufus-dir Version: 1.26 (4 October 2002)
714 it will then print something like:
718 Using default Catalog name=BackupDB DB=bacula
719 The defined Storage resources are:
722 Select Storage resource (1-2): 1
726 I select the autochanger (1), and it prints:
730 Enter new Volume name: TestVolume1
731 Enter slot (0 for none): 1
735 where I entered {\bf TestVolume1} for the tape name, and slot {\bf 1} for the
743 Select the Pool (1-2): 1
747 I select the Default pool. This will be automatically done if you only have a
748 single pool, then Bacula will proceed to unload any loaded volume, load the
749 volume in slot 1 and label it. In this example, nothing was in the drive, so
754 Connecting to Storage daemon Autochanger at localhost:9103 ...
755 Sending label command ...
756 3903 Issuing autochanger "load slot 1" command.
757 3000 OK label. Volume=TestVolume1 Device=/dev/nst0
758 Media record for Volume=TestVolume1 successfully created.
759 Requesting mount Autochanger ...
760 3001 Device /dev/nst0 is mounted with Volume TestVolume1
766 You may then proceed to label the other volumes. The messages will change
767 slightly because Bacula will unload the volume (just labeled TestVolume1)
768 before loading the next volume to be labeled.
770 Once all your Volumes are labeled, Bacula will automatically load them as they
773 To ``see'' how you have labeled your Volumes, simply enter the {\bf list
774 volumes} command from the Console program, which should print something like
780 Using default Catalog name=BackupDB DB=bacula
784 Select the Pool (1-2): 1
785 +-------+----------+--------+---------+-------+--------+----------+-------+------+
786 | MedId | VolName | MedTyp | VolStat | Bites | LstWrt | VolReten | Recyc | Slot |
787 +-------+----------+--------+---------+-------+--------+----------+-------+------+
788 | 1 | TestVol1 | DDS-4 | Append | 0 | 0 | 30672000 | 0 | 1 |
789 | 2 | TestVol2 | DDS-4 | Append | 0 | 0 | 30672000 | 0 | 2 |
790 | 3 | TestVol3 | DDS-4 | Append | 0 | 0 | 30672000 | 0 | 3 |
792 +-------+----------+--------+---------+-------+--------+----------+-------+------+
798 \subsection*{Barcode Support}
799 \index[general]{Support!Barcode }
800 \index[general]{Barcode Support }
801 \addcontentsline{toc}{subsection}{Barcode Support}
803 Bacula provides barcode support with two Console commands, {\bf label
804 barcodes} and {\bf update slots}.
806 The {\bf label barcodes} will cause Bacula to read the barcodes of all the
807 cassettes that are currently installed in the magazine (cassette holder) using
808 the {\bf mtx-changer} {\bf list} command. Each cassette is mounted in turn and
809 labeled with the same Volume name as the barcode.
811 The {\bf update slots} command will first obtain the list of cassettes and
812 their barcodes from {\bf mtx-changer}. Then it will find each volume in turn
813 in the catalog database corresponding to the barcodes and set its Slot to
814 correspond to the value just read. If the Volume is not in the catalog, then
815 nothing will be done. This command is useful for synchronizing Bacula with the
816 current magazine in case you have changed magazines or in case you have moved
817 cassettes from one slot to another.
819 The {\bf Cleaning Prefix} statement can be used in the Pool resource to define
820 a Volume name prefix, which if it matches that of the Volume (barcode) will
821 cause that Volume to be marked with a VolStatus of {\bf Cleaning}. This will
822 prevent Bacula from attempting to write on the Volume.
826 \subsection*{Bacula Autochanger Interface}
827 \index[general]{Interface!Bacula Autochanger }
828 \index[general]{Bacula Autochanger Interface }
829 \addcontentsline{toc}{subsection}{Bacula Autochanger Interface}
831 Bacula calls the autochanger script that you specify on the {\bf Changer
832 Device} statement. Normally this script will be the {\bf mtx-changer} script
833 that we can provide, but it can in fact be any program. The only requirements
834 are that the ``commands'' that Bacula uses are {\bf loaded}, {\bf load}, {\bf
835 unload}, {\bf list}, and {\bf slots}. In addition,
836 each of those commands must return the information in the precise format as
841 - Currently the changer commands used are:
842 loaded -- returns number of the slot that is loaded in
843 the drive or 0 if the drive is empty.
844 load -- loads a specified slot (note, some autochangers
845 require a 30 second pause after this command) into
847 unload -- unloads the device (returns cassette to its slot).
848 list -- returns one line for each cassette in the autochanger
849 in the format <slot>:<barcode>. Where
850 the {\bf slot} is the non-zero integer representing
851 the slot number, and {\bf barcode} is the barcode
852 associated with the cassette if it exists and if you
853 autoloader supports barcodes. Otherwise the barcode
855 slots -- returns total number of slots in the autochanger.
859 Bacula checks the exit status of the program called, and if it is zero, the
860 data is accepted. If the exit status is non-zero, Bacula ignores any
861 information returned and treats the drive as if it is not an autochanger.