4 \chapter{Bacula Console}
5 \label{_ConsoleChapter}
6 \index[general]{Console!Bacula}
7 \index[general]{Bacula Console}
8 \index[console]{Console!Bacula}
9 \index[console]{Bacula Console}
11 The {\bf Bacula Console} (sometimes called the User Agent) is a program that
12 allows the user or the System Administrator, to interact with the Bacula
13 Director daemon while the daemon is running.
15 The current Bacula Console comes in two versions: a shell interface (TTY
16 style), and a GNOME GUI interface. Both permit the administrator or authorized
17 users to interact with Bacula. You can determine the status of a particular
18 job, examine the contents of the Catalog as well as perform certain tape
19 manipulations with the Console program.
21 In addition, there is a bwx-console built with wxWidgets that allows a graphic
22 restore of files. As of version 1.34.1 it is in an early stage of development,
23 but it already is quite useful. Unfortunately, it has not been enhanced for
26 Since the Console program interacts with the Director through the network, your
27 Console and Director programs do not necessarily need to run on the same
30 In fact, a certain minimal knowledge of the Console program is needed in order
31 for Bacula to be able to write on more than one tape, because when Bacula
32 requests a new tape, it waits until the user, via the Console program,
33 indicates that the new tape is mounted.
35 \section{Console Configuration}
36 \index[general]{Console Configuration}
37 \index[general]{Configuration!Console}
38 \index[console]{Console Configuration}
39 \index[console]{Configuration!Console}
41 When the Console starts, it reads a standard Bacula configuration file named
42 {\bf bconsole.conf} or {\bf bgnome-console.conf} in the case of the GNOME
43 Console version. This file allows default configuration of the Console, and at
44 the current time, the only Resource Record defined is the Director resource,
45 which gives the Console the name and address of the Director. For more
46 information on configuration of the Console program, please see the
47 \ilink{Console Configuration File}{ConsoleConfChapter} Chapter of
50 \section{Running the Console Program}
51 \index[general]{Running the Console Program}
52 \index[general]{Program!Running the Console}
53 \index[console]{Running the Console Program}
54 \index[console]{Program!Running the Console}
56 The console program can be run with the following options:
59 Usage: bconsole [-s] [-c config_file] [-d debug_level]
60 -c <file> set configuration file to file
61 -dnn set debug level to nn
64 -t test - read configuration and exit
65 -? print this message.
70 After launching the Console program (bconsole), it will prompt you for the
71 next command with an asterisk (*). (Note, in the GNOME version, the prompt is
72 not present; you simply enter the commands you want in the command text box at
73 the bottom of the screen.) Generally, for all commands, you can simply enter
74 the command name and the Console program will prompt you for the necessary
75 arguments. Alternatively, in most cases, you may enter the command followed by
76 arguments. The general format is:
80 <command> <keyword1>[=<argument1>] <keyword2>[=<argument2>] ...
84 where {\bf command} is one of the commands listed below; {\bf keyword} is one
85 of the keywords listed below (usually followed by an argument); and {\bf
86 argument} is the value. The command may be abbreviated to the shortest unique
87 form. If two commands have the same starting letters, the one that will be
88 selected is the one that appears first in the {\bf help} listing. If you want
89 the second command, simply spell out the full command. None of the keywords
90 following the command may be abbreviated.
100 will list all files saved for JobId 23. Or:
108 will display all the Pool resource records.
110 The maximum command line length is limited to 511 characters, so if you
111 are scripting the console, you may need to take some care to limit the
114 \section{Stopping the Console Program}
115 \index[general]{Program!Stopping the Console}
116 \index[general]{Stopping the Console Program}
117 \index[console]{Program!Stopping the Console}
118 \index[console]{Stopping the Console Program}
120 Normally, you simply enter {\bf quit} or {\bf exit} and the Console program
121 will terminate. However, it waits until the Director acknowledges the command.
122 If the Director is already doing a lengthy command (e.g. prune), it may take
123 some time. If you want to immediately terminate the Console program, enter the
126 There is currently no way to interrupt a Console command once issued (i.e.
127 Ctrl-C does not work). However, if you are at a prompt that is asking you to
128 select one of several possibilities and you would like to abort the command,
129 you can enter a period ({\bf .}), and in most cases, you will either be
130 returned to the main command prompt or if appropriate the previous prompt (in
131 the case of nested prompts). In a few places such as where it is asking for a
132 Volume name, the period will be taken to be the Volume name. In that case, you
133 will most likely be able to cancel at the next prompt.
136 \section{Alphabetic List of Console Keywords}
137 \index[general]{Keywords!Alphabetic List of Console}
138 \index[general]{Alphabetic List of Console Keywords}
139 \index[console]{Keywords!Alphabetic List of Console}
140 \index[console]{Alphabetic List of Console Keywords}
141 Unless otherwise specified, each of the following keywords
142 takes an argument, which is specified after the keyword following
143 an equal sign. For example:
149 Please note, this list is incomplete as it is currently in
150 the process of being created and is not currently totally in
156 Permitted on the python command, and causes the Python
157 interpreter to be restarted. Takes no argument.
159 Permitted on the status and show commands to specify all components or
160 resources respectively.
162 Permitted on the update command to specify that all Volumes in the
163 pool (specified on the command line) should be updated.
165 Used in the restore command.
167 Used in the restore command.
169 Allowed in the use command to specify the catalog name
172 Used in the show command. Takes no arguments.
175 Used in the show, list, and llist commands. Takes no arguments.
177 Used in the show command. Takes no arguments.
179 Used in the restore command. Takes no argument.
181 Used to define the number of days the "list nextvol" command
182 should consider when looking for jobs to be run. The days keyword
183 can also be used on the "status dir" command so that it will display
184 jobs scheduled for the number of days you want.
186 Used in the show command. Takes no arguments.
187 \item [dir | director]
189 Used in the show command. Takes no arguments.
191 Used in the restore command. Its argument specifies the directory
194 This keyword can appear on the {\bf update volume} as well
195 as the {\bf update slots} commands, and can
196 allows one of the following arguments: yes, true, no, false, archived,
197 0, 1, 2. Where 0 corresponds to no or false, 1 corresponds to yes or true, and
198 2 corresponds to archived. Archived volumes will not be used, nor will
199 the Media record in the catalog be pruned. Volumes that are not enabled,
200 will not be used for backup or restore.
202 Used in the restore command. Takes no argument.
204 Used in the restore command.
206 Used in the list and llist commands. Takes no arguments.
209 Used in the show command. Takes no arguments.
211 Used in the show command. Takes no arguments.
213 Used in the show, list and llist commands. Takes no arguments.
215 Used in the list and llist commands. Takes no arguments.
217 Used in the list and llist commands. Takes no arguments.
219 The JobId is the numeric jobid that is printed in the Job
220 Report output. It is the index of the database record for the
221 given job. While it is unique for all the existing Job records
222 in the catalog database, the same JobId can be reused once a
223 Job is removed from the catalog. Probably you will refer
224 specific Jobs that ran using their numeric JobId.
225 \item [job | jobname]
226 The Job or Jobname keyword refers to the name you specified
227 in the Job resource, and hence it refers to any number of
228 Jobs that ran. It is typically useful if you want to list
229 all jobs of a particular name.
232 Permitted on the estimate command. Takes no argument.
235 Used in the show command. Takes no arguments.
237 Used in the list and llist commands. Takes no arguments.
238 \item [nextvol | nextvolume]
239 Used in the list and llist commands. Takes no arguments.
246 Used in the show, list, and llist commands. Takes no arguments.
248 Used in the restore command. Takes no argument.
250 Used in the show command. Takes no arguments.
252 Used in the show command. Takes no arguments.
253 \item [sd | store | storage]
255 The ujobid is a unique job identification that is printed
256 in the Job Report output. At the current time, it consists
257 of the Job name (from the Name directive for the job) appended
258 with the date and time the job was run. This keyword is useful
259 if you want to completely identify the Job instance run.
262 Used in the list and llist commands. Takes no arguments.
264 Used in the restore command.
266 Used in the restore command. Takes no argument.
270 \section{Alphabetic List of Console Commands}
271 \index[general]{Commands!Alphabetic List of Console}
272 \index[general]{Alphabetic List of Console Commands}
273 \index[console]{Commands!Alphabetic List of Console}
274 \index[console]{Alphabetic List of Console Commands}
276 The following commands are currently implemented:
279 \item [{add [pool=\lt{}pool-name\gt{} storage=\lt{}storage\gt{}
280 jobid=\lt{}JobId\gt{}]} ]
282 This command is used to add Volumes to an existing Pool. That is,
283 it creates the Volume name in the catalog and inserts into the Pool
284 in the catalog, but does not attempt to access the physical Volume.
286 added, Bacula expects that Volume to exist and to be labeled.
287 This command is not normally used since Bacula will
288 automatically do the equivalent when Volumes are labeled. However,
289 there may be times when you have removed a Volume from the catalog
290 and want to later add it back.
292 Normally, the {\bf label} command is used rather than this command
293 because the {\bf label} command labels the physical media (tape, disk,
294 DVD, ...) and does the equivalent of the {\bf add} command. The {\bf
295 add} command affects only the Catalog and not the physical media (data
296 on Volumes). The physical media must exist and be labeled before use
297 (usually with the {\bf label} command). This command can, however, be
298 useful if you wish to add a number of Volumes to the Pool that will be
299 physically labeled at a later time. It can also be useful if you are
300 importing a tape from another site. Please see the {\bf label} command
301 below for the list of legal characters in a Volume name.
303 \item [autodisplay on/off]
304 \index[console]{autodisplay on/off}
305 This command accepts {\bf on} or {\bf off} as an argument, and turns
306 auto-display of messages on or off respectively. The default for the
307 console program is {\bf off}, which means that you will be notified when
308 there are console messages pending, but they will not automatically be
309 displayed. The default for the bgnome-console program is {\bf on}, which
310 means that messages will be displayed when they are received (usually
311 within five seconds of them being generated).
313 When autodisplay is turned off, you must explicitly retrieve the
314 messages with the {\bf messages} command. When autodisplay is turned
315 on, the messages will be displayed on the console as they are received.
317 \item [automount on/off]
318 \index[console]{automount on/off}
319 This command accepts {\bf on} or {\bf off} as the argument, and turns
320 auto-mounting of the Volume after a {\bf label} command on or off
321 respectively. The default is {\bf on}. If {\bf automount} is turned
322 off, you must explicitly {\bf mount} tape Volumes after a label command to
325 \item [{cancel [jobid=\lt{}number\gt{} job=\lt{}job-name\gt{} ujobid=\lt{}unique-jobid\gt{}]}]
326 \index[console]{cancel jobid}
327 This command is used to cancel a job and accepts {\bf jobid=nnn} or {\bf
328 job=xxx} as an argument where nnn is replaced by the JobId and xxx is
329 replaced by the job name. If you do not specify a keyword, the Console
330 program will prompt you with the names of all the active jobs allowing
333 Once a Job is marked to be canceled, it may take a bit of time
334 (generally within a minute) before it actually terminates, depending on
335 what operations it is doing.
337 \item [{create [pool=\lt{}pool-name\gt{}]}]
338 \index[console]{create pool}
339 This command is not normally used as the Pool records are automatically
340 created by the Director when it starts based on what it finds in
341 the conf file. If needed, this command can be
342 to create a Pool record in the database using the
343 Pool resource record defined in the Director's configuration file. So
344 in a sense, this command simply transfers the information from the Pool
345 resource in the configuration file into the Catalog. Normally this
346 command is done automatically for you when the Director starts providing
347 the Pool is referenced within a Job resource. If you use this command
348 on an existing Pool, it will automatically update the Catalog to have
349 the same information as the Pool resource. After creating a Pool, you
350 will most likely use the {\bf label} command to label one or more
351 volumes and add their names to the Media database.
353 When starting a Job, if Bacula determines that there is no Pool record
354 in the database, but there is a Pool resource of the appropriate name,
355 it will create it for you. If you want the Pool record to appear in the
356 database immediately, simply use this command to force it to be created.
358 \item [{delete [volume=\lt{}vol-name\gt{} pool=\lt{}pool-name\gt{} job
359 jobid=\lt{}id\gt{}]}]
360 \index[console]{delete}
361 The delete command is used to delete a Volume, Pool or Job record from
362 the Catalog as well as all associated catalog Volume records that were
363 created. This command operates only on the Catalog database and has no
364 effect on the actual data written to a Volume. This command can be
365 dangerous and we strongly recommend that you do not use it unless you
366 know what you are doing.
368 If the keyword {\bf Volume} appears on the command line, the named
369 Volume will be deleted from the catalog, if the keyword {\bf Pool}
370 appears on the command line, a Pool will be deleted, and if the keyword
371 {\bf Job} appears on the command line, a Job and all its associated
372 records (File and JobMedia) will be deleted from the catalog. The full
373 form of this command is:
376 delete pool=<pool-name>
382 delete volume=>volume-name> pool=>pool-name> or
386 delete JobId=>job-id> JobId=>job-id2> ... or
390 delete Job JobId=n,m,o-r,t ...
393 The first form deletes a Pool record from the catalog database. The
394 second form deletes a Volume record from the specified pool in the
395 catalog database. The third form deletes the specified Job record from
396 the catalog database. The last form deletes JobId records for JobIds
397 n, m, o, p, q, r, and t. Where each one of the n,m,... is, of course, a
398 number. That is a "delete jobid" accepts lists and ranges of
401 \item [disable job\lt{}job-name\gt{}]
402 \index[console]{enable}
403 This command permits you to disable a Job for automatic scheduling.
404 The job may have been previously enabled with the Job resource
405 {\bf Enabled} directive or using the console {\bf enable} command.
406 The next time the Director is restarted or the conf file is reloaded,
407 the Enable/Disable state will be set to the value in the Job resource
408 (default enabled) as defined in the bacula-dir.conf file.
410 \item [enable job\lt{}job-name\gt{}]
411 \index[console]{enable}
412 This command permits you to enable a Job for automatic scheduling.
413 The job may have been previously disabled with the Job resource
414 {\bf Enabled} directive or using the console {\bf disable} command.
415 The next time the Director is restarted or the conf file is reloaded,
416 the Enable/Disable state will be set to the value in the Job resource
417 (default enabled) as defined in the bacula-dir.conf file.
421 \index[console]{estimate}
422 Using this command, you can get an idea how many files will be backed
423 up, or if you are unsure about your Include statements in your FileSet,
424 you can test them without doing an actual backup. The default is to
425 assume a Full backup. However, you can override this by specifying a
426 {\bf level=Incremental} or {\bf level=Differential} on the command line.
427 A Job name must be specified or you will be prompted for one, and
428 optionally a Client and FileSet may be specified on the command line.
429 It then contacts the client which computes the number of files and bytes
430 that would be backed up. Please note that this is an estimate
431 calculated from the number of blocks in the file rather than by reading
432 the actual bytes. As such, the estimated backup size will generally be
433 larger than an actual backup.
435 Optionally you may specify the keyword {\bf listing} in which case, all the
436 files to be backed up will be listed. Note, it could take quite some time to
437 display them if the backup is large. The full form is:
441 estimate job=<job-name> listing client=<client-name>
442 fileset=<fileset-name> level=<level-name>
445 Specification of the {\bf job} is sufficient, but you can also override
446 the client, fileset and/or level by specifying them on the estimate
450 As an example, you might do:
455 estimate job=NightlySave listing level=Incremental
460 which will do a full listing of all files to be backed up for the Job {\bf
461 NightlySave} during an Incremental save and put it in the file {\bf
462 /tmp/listing}. Note, the byte estimate provided by this command is
463 based on the file size contained in the directory item. This can give
464 wildly incorrect estimates of the actual storage used if there are
465 sparse files on your systems. Sparse files are often found on 64 bit
466 systems for certain system files. The size that is returned is the size
467 Bacula will backup if the sparse option is not specified in the FileSet.
468 There is currently no way to get an estimate of the real file size that
469 would be found should the sparse option be enabled.
473 \index[console]{help}
474 This command displays the list of commands available.
477 \index[console]{label}
478 \index[console]{relabel}
479 \index[general]{label}
480 \index[general]{relabel}
481 This command is used to label physical volumes. The full form of this command
485 label storage=>storage-name> volume=>volume-name>
489 If you leave out any part, you will be prompted for it. The media type
490 is automatically taken from the Storage resource definition that you
491 supply. Once the necessary information is obtained, the Console program
492 contacts the specified Storage daemon and requests that the Volume be
493 labeled. If the Volume labeling is successful, the Console program will
494 create a Volume record in the appropriate Pool.
496 The Volume name is restricted to letters, numbers, and the special
497 characters hyphen ({\bf -}), underscore ({\bf \_}), colon ({\bf :}), and
498 period ({\bf .}). All other characters including a space are invalid.
499 This restriction is to ensure good readability of Volume names to reduce
502 Please note, when labeling a blank tape, Bacula will get {\bf read I/O
503 error} when it attempts to ensure that the tape is not already labeled. If
504 you wish to avoid getting these messages, please write an EOF mark on
505 your tape before attempting to label it:
515 The label command can fail for a number of reasons:
518 \item The Volume name you specify is already in the Volume database.
520 \item The Storage daemon has a tape or other Volume already mounted on the
521 device, in which case you must {\bf unmount} the device, insert a blank
522 tape, then do the {\bf label} command.
524 \item The Volume in the device is already a Bacula labeled Volume. (Bacula will
525 never relabel a Bacula labeled Volume unless it is recycled and you use the
526 {\bf relabel} command).
528 \item There is no Volume in the drive.
531 There are two ways to relabel a volume that already has a Bacula label. The
532 brute force method is to write an end of file mark on the tape using the
533 system {\bf mt} program, something like the following:
537 mt -f /dev/st0 rewind
542 For a disk volume, you would manually delete the Volume.
544 Then you use the {\bf label} command to add a new label. However, this could
545 leave traces of the old volume in the catalog.
547 The preferable method to relabel a Volume is to first {\bf purge} the volume,
548 either automatically, or explicitly with the {\bf purge} command, then use
549 the {\bf relabel} command described below.
551 If your autochanger has barcode labels, you can label all the Volumes in
552 your autochanger one after another by using the {\bf label barcodes}
553 command. For each tape in the changer containing a barcode, Bacula will
554 mount the tape and then label it with the same name as the barcode. An
555 appropriate Media record will also be created in the catalog. Any barcode
556 that begins with the same characters as specified on the
557 "CleaningPrefix=xxx" directive in the Director's Pool resource, will be
558 treated as a cleaning tape, and will not be labeled. However, an entry for
559 the cleaning tape will be created in the catalog. For example with:
565 Cleaning Prefix = "CLN"
571 Any slot containing a barcode of CLNxxxx will be treated as a cleaning tape
572 and will not be mounted. Note, the full form of the command is:
576 update storage=xxx pool=yyy slots=1-5,10 barcodes
581 \index[console]{list}
582 The list command lists the requested contents of the Catalog. The
583 various fields of each record are listed on a single line. The various
584 forms of the list command are:
589 list jobid=<id> (list jobid id)
591 list ujobid<unique job name> (list job with unique name)
593 list job=<job-name> (list all jobs with "job-name")
595 list jobname=<job-name> (same as above)
597 In the above, you can add "limit=nn" to limit the output to
602 list jobmedia jobid=<id>
604 list jobmedia job=<job-name>
606 list files jobid=<id>
608 list files job=<job-name>
618 list volumes jobid=<id>
620 list volumes pool=<pool-name>
622 list volumes job=<job-name>
624 list volume=<volume-name>
626 list nextvolume job=<job-name>
628 list nextvol job=<job-name>
630 list nextvol job=<job-name> days=nnn
635 What most of the above commands do should be more or less obvious. In
636 general if you do not specify all the command line arguments, the
637 command will prompt you for what is needed.
639 The {\bf list nextvol} command will print the Volume name to be used by
640 the specified job. You should be aware that exactly what Volume will be
641 used depends on a lot of factors including the time and what a prior job
642 will do. It may fill a tape that is not full when you issue this
643 command. As a consequence, this command will give you a good estimate
644 of what Volume will be used but not a definitive answer. In addition,
645 this command may have certain side effect because it runs through the
646 same algorithm as a job, which means it may automatically purge or
647 recycle a Volume. By default, the job specified must run within the
648 next two days or no volume will be found. You can, however, use the
649 {\bf days=nnn} specification to specify up to 50 days. For example,
650 if on Friday, you want to see what Volume will be needed on Monday,
651 for job MyJob, you would use {\bf list nextvol job=MyJob days=3}.
653 If you wish to add specialized commands that list the contents of the
654 catalog, you can do so by adding them to the {\bf query.sql} file.
655 However, this takes some knowledge of programming SQL. Please see the
656 {\bf query} command below for additional information. See below for
657 listing the full contents of a catalog record with the {\bf llist}
660 As an example, the command {\bf list pools} might produce the following
665 +------+---------+---------+---------+----------+-------------+
666 | PoId | Name | NumVols | MaxVols | PoolType | LabelFormat |
667 +------+---------+---------+---------+----------+-------------+
668 | 1 | Default | 0 | 0 | Backup | * |
669 | 2 | Recycle | 0 | 8 | Backup | File |
670 +------+---------+---------+---------+----------+-------------+
674 As mentioned above, the {\bf list} command lists what is in the
675 database. Some things are put into the database immediately when Bacula
676 starts up, but in general, most things are put in only when they are
677 first used, which is the case for a Client as with Job records, etc.
679 Bacula should create a client record in the database the first time you
680 run a job for that client. Doing a {\bf status} will not cause a
681 database record to be created. The client database record will be
682 created whether or not the job fails, but it must at least start. When
683 the Client is actually contacted, additional info from the client will
684 be added to the client record (a "uname -a" output).
686 If you want to see what Client resources you have available in your conf
687 file, you use the Console command {\bf show clients}.
690 \index[console]{llist}
691 The llist or "long list" command takes all the same arguments that the
692 list command described above does. The difference is that the llist
693 command list the full contents of each database record selected. It
694 does so by listing the various fields of the record vertically, with one
695 field per line. It is possible to produce a very large number of output
696 lines with this command.
698 If instead of the {\bf list pools} as in the example above, you enter
699 {\bf llist pools} you might get the following output:
710 VolRetention: 1,296,000
711 VolUseDuration: 86,400
727 VolUseDuration: 3,600
739 \index[console]{messages}
740 This command causes any pending console messages to be immediately displayed.
744 \index[console]{mount}
745 The mount command is used to get Bacula to read a volume on a physical
746 device. It is a way to tell Bacula that you have mounted a tape and
747 that Bacula should examine the tape. This command is normally
748 used only after there was no Volume in a drive and Bacula requests you to mount a new
749 Volume or when you have specifically unmounted a Volume with the {\bf
750 unmount} console command, which causes Bacula to close the drive. If
751 you have an autoloader, the mount command will not cause Bacula to
752 operate the autoloader unless you specify a {\bf slot} and possibly a
753 {\bf drive}. The various forms of the mount command are:
755 mount storage=\lt{}storage-name\gt{} [ slot=\lt{}num\gt{} ] [
756 drive=\lt{}num\gt{} ]
758 mount [ jobid=\lt{}id\gt{} | job=\lt{}job-name\gt{} ]
760 If you have specified {\bf Automatic Mount = yes} in the Storage daemon's
761 Device resource, under most circumstances, Bacula will automatically access
762 the Volume unless you have explicitly {\bf unmount}ed it in the Console
766 \index[console]{python}
767 The python command takes a single argument {\bf restart}:
771 This causes the Python interpreter in the Director to be reinitialized.
772 This can be helpful for testing because once the Director starts and the
773 Python interpreter is initialized, there is no other way to make it
774 accept any changes to the startup script {\bf DirStartUp.py}. For more
775 details on Python scripting, please see the \ilink{Python
776 Scripting}{PythonChapter} chapter of this manual.
778 \label{ManualPruning}
780 \index[console]{prune}
781 The Prune command allows you to safely remove expired database records
782 from Jobs and Volumes. This command works only on the Catalog database
783 and does not affect data written to Volumes. In all cases, the Prune
784 command applies a retention period to the specified records. You can
785 Prune expired File entries from Job records; you can Prune expired Job
786 records from the database, and you can Prune both expired Job and File
787 records from specified Volumes.
789 prune files|jobs|volume client=\lt{}client-name\gt{}
790 volume=\lt{}volume-name\gt{}
792 For a Volume to be pruned, the {\bf VolStatus} must be Full, Used, or
793 Append, otherwise the pruning will not take place.
796 \index[console]{purge}
797 The Purge command will delete associated Catalog database records from
798 Jobs and Volumes without considering the retention period. {\bf Purge}
799 works only on the Catalog database and does not affect data written to
800 Volumes. This command can be dangerous because you can delete catalog
801 records associated with current backups of files, and we recommend that
802 you do not use it unless you know what you are doing. The permitted
803 forms of {\bf purge} are:
805 purge files jobid=\lt{}jobid\gt{}|job=\lt{}job-name\gt{}|client=\lt{}client-name\gt{}
807 purge jobs client=\lt{}client-name\gt{} (of all jobs)
809 purge volume|volume=\lt{}vol-name\gt{} (of all jobs)
811 For the {\bf purge} command to work on Volume Catalog database records the
812 {\bf VolStatus} must be Append, Full, Used, or Error.
814 The actual data written to the Volume will be unaffected by this command.
817 \index[console]{relabel}
818 \index[general]{relabel}
819 This command is used to label physical volumes. The full form of this
822 relabel storage=\lt{}storage-name\gt{} oldvolume=\lt{}old-volume-name\gt{}
823 volume=\lt{}newvolume-name\gt{}
825 If you leave out any part, you will be prompted for it. In order for
826 the Volume (old-volume-name) to be relabeled, it must be in the catalog,
827 and the volume status must be marked {\bf Purged} or {\bf Recycle}.
828 This happens automatically as a result of applying retention periods, or
829 you may explicitly purge the volume using the {\bf purge} command.
831 Once the volume is physically relabeled, the old data previously written
832 on the Volume is lost and cannot be recovered.
835 \index[console]{release}
836 This command is used to cause the Storage daemon to rewind (release) the
837 current tape in the drive, and to re-read the Volume label the next time
840 release storage=\lt{}storage-name\gt{}
842 After a release command, the device is still kept open by Bacula (unless
843 Always Open is set to No in the Storage Daemon's configuration) so it
844 cannot be used by another program. However, with some tape drives, the
845 operator can remove the current tape and to insert a different one, and
846 when the next Job starts, Bacula will know to re-read the tape label to
847 find out what tape is mounted. If you want to be able to use the drive
848 with another program (e.g. {\bf mt}), you must use the {\bf unmount}
849 command to cause Bacula to completely release (close) the device.
852 \index[console]{reload}
853 The reload command causes the Director to re-read its configuration
854 file and apply the new values. The new values will take effect
855 immediately for all new jobs. However, if you change schedules,
856 be aware that the scheduler pre-schedules jobs up to two hours in
857 advance, so any changes that are to take place during the next two
858 hours may be delayed. Jobs that have already been scheduled to run
859 (i.e. surpassed their requested start time) will continue with the
860 old values. New jobs will use the new values. Each time you issue
861 a reload command while jobs are running, the prior config values
862 will queued until all jobs that were running before issuing
863 the reload terminate, at which time the old config values will
864 be released from memory. The Directory permits keeping up to
865 ten prior set of configurations before it will refuse a reload
866 command. Once at least one old set of config values has been
867 released it will again accept new reload commands.
869 While it is possible to reload the Director's configuration on the fly,
870 even while jobs are executing, this is a complex operation and not
871 without side effects. Accordingly, if you have to reload the Director's
872 configuration while Bacula is running, it is advisable to restart the
873 Director at the next convenient opportunity.
875 \label{restore_command}
877 \index[console]{restore}
878 The restore command allows you to select one or more Jobs (JobIds) to be
879 restored using various methods. Once the JobIds are selected, the File
880 records for those Jobs are placed in an internal Bacula directory tree,
881 and the restore enters a file selection mode that allows you to
882 interactively walk up and down the file tree selecting individual files
883 to be restored. This mode is somewhat similar to the standard Unix {\bf
884 restore} program's interactive file selection mode.
886 restore storage=\lt{}storage-name\gt{} client=\lt{}backup-client-name\gt{}
887 where=\lt{}path\gt{} pool=\lt{}pool-name\gt{} fileset=\lt{}fileset-name\gt{}
888 restoreclient=\lt{}restore-client-name\gt{}
889 select current all done
891 Where {\bf current}, if specified, tells the restore command to
892 automatically select a restore to the most current backup. If not
893 specified, you will be prompted. The {\bf all} specification tells the
894 restore command to restore all files. If it is not specified, you will
895 be prompted for the files to restore. For details of the {\bf restore}
896 command, please see the \ilink{Restore Chapter}{RestoreChapter} of this
899 The client keyword initially specifies the client from which the backup
900 was made and the client to which the restore will be make. However,
901 if the restoreclient keyword is specified, then the restore is written
906 This command allows you to schedule jobs to be run immediately. The full form
909 run job=\lt{}job-name\gt{} client=\lt{}client-name\gt{}
910 fileset=\lt{}FileSet-name\gt{} level=\lt{}level-keyword\gt{}
911 storage=\lt{}storage-name\gt{} where=\lt{}directory-prefix\gt{}
912 when=\lt{}universal-time-specification\gt{} yes
914 Any information that is needed but not specified will be listed for
915 selection, and before starting the job, you will be prompted to accept,
916 reject, or modify the parameters of the job to be run, unless you have
917 specified {\bf yes}, in which case the job will be immediately sent to
920 On my system, when I enter a run command, I get the following prompt:
924 A job name must be specified.
925 The defined Job resources are:
935 Select Job resource (1-9):
940 If I then select number 5, I am prompted with:
946 FileSet: Minou Full Set
951 When: 2003-04-23 17:08:18
952 OK to run? (yes/mod/no):
957 If I now enter {\bf yes}, the Job will be run. If I enter {\bf mod}, I will
958 be presented with the following prompt.
962 Parameters to modify:
970 Select parameter to modify (1-7):
975 If you wish to start a job at a later time, you can do so by setting the When
976 time. Use the {\bf mod} option and select {\bf When} (no. 6). Then enter the
977 desired start time in YYYY-MM-DD HH:MM:SS format.
980 \index[console]{setdebug}
981 \index[dir]{setdebug}
982 \index[dir]{debugging}
983 \index[dir]{debugging Win32}
984 \index[dir]{Windows!debugging}
985 This command is used to set the debug level in each daemon. The form of this
988 setdebug level=nn [trace=0/1 client=\lt{}client-name\gt{} | dir | director |
989 storage=\lt{}storage-name\gt{} | all]
991 If trace=1 is set, then tracing will be enabled, and the daemon will be
992 placed in trace mode, which means that all debug output as set by the
993 debug level will be directed to the file {\bf bacula.trace} in the
994 current directory of the daemon. Normally, tracing is needed only for
995 Win32 clients where the debug output cannot be written to a terminal or
996 redirected to a file. When tracing, each debug output message is
997 appended to the trace file. You must explicitly delete the file when
1001 \index[console]{show}
1003 The show command will list the Director's resource records as defined in
1004 the Director's configuration file (normally {\bf bacula-dir.conf}).
1005 This command is used mainly for debugging purposes by developers.
1006 The following keywords are accepted on the
1007 show command line: catalogs, clients, counters, devices, directors,
1008 filesets, jobs, messages, pools, schedules, storages, all, help.
1009 Please don't confuse this command
1010 with the {\bf list}, which displays the contents of the catalog.
1013 \index[console]{sqlquery}
1014 The sqlquery command puts the Console program into SQL query mode where
1015 each line you enter is concatenated to the previous line until a
1016 semicolon (;) is seen. The semicolon terminates the command, which is
1017 then passed directly to the SQL database engine. When the output from
1018 the SQL engine is displayed, the formation of a new SQL command begins.
1019 To terminate SQL query mode and return to the Console command prompt,
1020 you enter a period (.) in column 1.
1022 Using this command, you can query the SQL catalog database directly.
1023 Note you should really know what you are doing otherwise you could
1024 damage the catalog database. See the {\bf query} command below for
1025 simpler and safer way of entering SQL queries.
1027 Depending on what database engine you are using (MySQL, PostgreSQL or
1028 SQLite), you will have somewhat different SQL commands available. For
1029 more detailed information, please refer to the MySQL, PostgreSQL or
1030 SQLite documentation.
1034 This command will display the status of the next jobs that are scheduled
1035 during the next 24 hours as well as the status of currently
1036 running jobs. The full form of this command is:
1038 status [all | dir=\lt{}dir-name\gt{} | director |
1039 client=\lt{}client-name\gt{} | storage=\lt{}storage-name\gt{} |
1042 If you do a {\bf status dir}, the console will list any currently
1043 running jobs, a summary of all jobs scheduled to be run in the next 24
1044 hours, and a listing of the last ten terminated jobs with their statuses.
1045 The scheduled jobs summary will include the Volume name to be used. You
1046 should be aware of two things: 1. to obtain the volume name, the code
1047 % TODO: use bullets here or be consistent with numbering items
1048 goes through the same code that will be used when the job runs, which
1049 means that it may prune or recycle a Volume; 2. The Volume listed is
1050 only a best guess. The Volume actually used may be different because of
1051 the time difference (more durations may expire when the job runs) and
1052 another job could completely fill the Volume requiring a new one.
1054 In the Running Jobs listing, you may find the following types of
1060 2507 Catalog MatouVerify.2004-03-13_05.05.02 is waiting execution
1061 5349 Full CatalogBackup.2004-03-13_01.10.00 is waiting for higher
1062 priority jobs to finish
1063 5348 Differe Minou.2004-03-13_01.05.09 is waiting on max Storage jobs
1064 5343 Full Rufus.2004-03-13_01.05.04 is running
1068 Looking at the above listing from bottom to top, obviously JobId 5343
1069 (Rufus) is running. JobId 5348 (Minou) is waiting for JobId 5343 to
1070 finish because it is using the Storage resource, hence the "waiting on
1071 max Storage jobs". JobId 5349 has a lower priority than all the other
1072 jobs so it is waiting for higher priority jobs to finish, and finally,
1073 JobId 2508 (MatouVerify) is waiting because only one job can run at a
1074 time, hence it is simply "waiting execution"
1076 If you do a {\bf status dir}, it will by default list the first
1077 occurrence of all jobs that are scheduled today and tomorrow. If you
1078 wish to see the jobs that are scheduled in the next three days (e.g. on
1079 Friday you want to see the first occurrence of what tapes are scheduled
1080 to be used on Friday, the weekend, and Monday), you can add the {\bf
1081 days=3} option. Note, a {\bf days=0} shows the first occurrence of jobs
1082 scheduled today only. If you have multiple run statements, the first
1083 occurrence of each run statement for the job will be displayed for the
1086 If your job seems to be blocked, you can get a general idea of the
1087 problem by doing a {\bf status dir}, but you can most often get a
1088 much more specific indication of the problem by doing a
1089 {\bf status storage=xxx}. For example, on an idle test system, when
1090 I do {\bf status storage=File}, I get:
1094 Connecting to Storage daemon File at 192.168.68.112:8103
1096 rufus-sd Version: 1.39.6 (24 March 2006) i686-pc-linux-gnu redhat (Stentz)
1097 Daemon started 26-Mar-06 11:06, 0 Jobs run since started.
1103 Jobs waiting to reserve a drive:
1107 JobId Level Files Bytes Status Finished Name
1108 ======================================================================
1109 59 Full 234 4,417,599 OK 15-Jan-06 11:54 kernsave
1113 utochanger "DDS-4-changer" with devices:
1115 Device "DDS-4" (/dev/nst0) is mounted with Volume="TestVolume002"
1117 Slot 2 is loaded in drive 0.
1118 Total Bytes Read=0 Blocks Read=0 Bytes/block=0
1119 Positioned at File=0 Block=0
1120 Device "Dummy" is not open or does not exist.
1121 No DEVICE structure.
1123 Device "DVD-Writer" (/dev/hdc) is not open.
1124 Device "File" (/tmp) is not open.
1127 In Use Volume status:
1132 Now, what this tells me is that no jobs are running and that none of
1133 the devices are in use. Now, if I {\bf unmount} the autochanger, which
1134 will not be used in this example, and then start a Job that uses the
1135 File device, the job will block. When I re-issue the status storage
1136 command, I get for the Device status:
1143 Autochanger "DDS-4-changer" with devices:
1145 Device "DDS-4" (/dev/nst0) is not open.
1146 Device is BLOCKED. User unmounted.
1147 Drive 0 is not loaded.
1148 Device "Dummy" is not open or does not exist.
1149 No DEVICE structure.
1151 Device "DVD-Writer" (/dev/hdc) is not open.
1152 Device "File" (/tmp) is not open.
1153 Device is BLOCKED waiting for media.
1159 Now, here it should be clear that if a job were running that wanted
1160 to use the Autochanger (with two devices), it would block because
1161 the user unmounted the device. The real problem for the Job I started
1162 using the "File" device is that the device is blocked waiting for
1163 media -- that is Bacula needs you to label a Volume.
1166 \index[console]{unmount}
1167 This command causes the indicated Bacula Storage daemon to unmount the
1168 specified device. The forms of the command are the same as the mount command:
1171 unmount storage=<storage-name> [ drive=<num> ]
1173 unmount [ jobid=<id> | job=<job-name> ]
1177 Once you unmount a storage device, Bacula will no longer be able to use
1178 it until you issue a mount command for that device. If Bacula needs to
1179 access that device, it will block and issue mount requests periodically
1182 If the device you are unmounting is an autochanger, it will unload
1183 the drive you have specified on the command line. If no drive is
1184 specified, it will assume drive 1.
1186 \label{UpdateCommand}
1188 \index[console]{update}
1189 This command will update the catalog for either a specific Pool record, a Volume
1190 record, or the Slots in an autochanger with barcode capability. In the case
1191 of updating a Pool record, the new information will be automatically taken
1192 from the corresponding Director's configuration resource record. It can be
1193 used to increase the maximum number of volumes permitted or to set a maximum
1194 number of volumes. The following main keywords may be specified:
1197 media, volume, pool, slots
1201 In the case of updating a Volume, you will be prompted for which value you
1202 wish to change. The following Volume parameters may be changed:
1208 Volume Retention Period
1211 Maximum Volume Files
1212 Maximum Volume Bytes
1220 All Volumes from Pool
1225 For slots {\bf update slots}, Bacula will obtain a list of slots and
1226 their barcodes from the Storage daemon, and for each barcode found, it
1227 will automatically update the slot in the catalog Media record to
1228 correspond to the new value. This is very useful if you have moved
1229 cassettes in the magazine, or if you have removed the magazine and
1230 inserted a different one. As the slot of each Volume is updated, the
1231 InChanger flag for that Volume will also be set, and any other Volumes
1232 in the Pool that were last mounted on the same Storage device
1233 will have their InChanger flag turned off. This permits
1234 Bacula to know what magazine (tape holder) is currently in the
1237 If you do not have barcodes, you can accomplish the same thing in
1238 version 1.33 and later by using the {\bf update slots scan} command.
1239 The {\bf scan} keyword tells Bacula to physically mount each tape and to
1240 read its VolumeName.
1242 For Pool {\bf update pool}, Bacula will move the Volume record from its
1243 existing pool to the pool specified.
1245 For {\bf Volume from Pool} and {\bf All Volumes from Pool}, the
1246 following values are updated from the Pool record: Recycle, RecyclePool,
1247 VolRetention, VolUseDuration, MaxVolJobs, MaxVolFiles, and MaxVolBytes.
1248 (RecyclePool feature is available with bacula 2.1.4 or higher.)
1250 The full form of the update command with all command line arguments is:
1254 update volume=xxx pool=yyy slots volstatus=xxx VolRetention=ddd
1255 VolUse=ddd MaxVolJobs=nnn MaxVolBytes=nnn Recycle=yes|no
1256 slot=nnn enabled=n recyclepool=zzz
1262 \index[console]{use}
1263 This command allows you to specify which Catalog database to use. Normally,
1264 you will be using only one database so this will be done automatically. In
1265 the case that you are using more than one database, you can use this command
1266 to switch from one to another.
1268 use \lt{}database-name\gt{}
1272 \index[console]{var name}
1273 This command takes a string or quoted string and does variable expansion on
1274 it the same way variable expansion is done on the {\bf LabelFormat} string.
1275 Thus, for the most part, you can test your LabelFormat strings. The
1276 difference between the {\bf var} command and the actual LabelFormat process
1277 is that during the var command, no job is running so "dummy" values are
1278 used in place of Job specific variables. Generally, however, you will get a
1279 good idea of what is going to happen in the real case.
1282 \index[console]{version}
1283 The command prints the Director's version.
1286 \index[console]{quit}
1287 This command terminates the console program. The console program sends the
1288 {\bf quit} request to the Director and waits for acknowledgment. If the
1289 Director is busy doing a previous command for you that has not terminated, it
1290 may take some time. You may quit immediately by issuing the {\bf .quit}
1291 command (i.e. quit preceded by a period).
1294 \index[console]{query}
1295 This command reads a predefined SQL query from the query file (the name and
1296 location of the query file is defined with the QueryFile resource record in
1297 the Director's configuration file). You are prompted to select a query from
1298 the file, and possibly enter one or more parameters, then the command is
1299 submitted to the Catalog database SQL engine.
1301 The following queries are currently available (version 1.24):
1307 2: List where a file is saved:
1308 3: List where the most recent copies of a file are saved:
1309 4: List total files/bytes by Job:
1310 5: List total files/bytes by Volume:
1311 6: List last 20 Full Backups for a Client:
1312 7: List Volumes used by selected JobId:
1313 8: List Volumes to Restore All Files:
1314 9: List where a File is saved:
1315 Choose a query (1-9):
1321 \index[console]{exit}
1322 This command terminates the console program.
1325 \index[console]{wait}
1326 The wait command causes the Director to pause until there are no jobs
1327 running. This command is useful in a batch situation such as regression
1328 testing where you wish to start a job and wait until that job completes
1329 before continuing. This command now has the following options:
1332 wait [jobid=nn] [jobuid=unique id] [job=job name]
1335 If specified with a specific JobId, ... the wait command will wait
1336 for that particular job to terminate before continuing.
1341 \section{Special dot Commands}
1342 \index[general]{Commands!Special dot}
1343 \index[general]{Special dot Commands}
1345 There is a list of commands that are prefixed with a period (.). These
1346 commands are intended to be used either by batch programs or graphical user
1347 interface front-ends. They are not normally used by interactive users. Once
1348 GUI development begins, this list will be considerably expanded. The following
1349 is the list of dot commands:
1353 .backups job=xxx list backups for specified job
1354 .clients list all client names
1355 .defaults client=xxx fileset=yyy list defaults for specified client
1356 .die cause the Director to segment fault (for debugging)
1357 .dir when in tree mode prints the equivalent to the dir command,
1358 but with fields separated by commas rather than spaces.
1360 .filesets list all fileset names
1361 .help help command output
1362 .jobs list all job names
1363 .levels list all levels
1364 .messages get quick messages
1365 .msgs return any queued messages
1366 .pools list all pool names
1368 .status get status output
1369 .storage return storage resource names
1370 .types list job types
1376 \section{Special At (@) Commands}
1377 \index[general]{Commands!Special At @}
1378 \index[general]{Special At (@) Commands}
1380 Normally, all commands entered to the Console program are immediately
1381 forwarded to the Director, which may be on another machine, to be executed.
1382 However, there is a small list of {\bf at} commands, all beginning with an at
1383 character (@), that will not be sent to the Director, but rather interpreted
1384 by the Console program directly. Note, these commands are implemented only in
1385 the tty console program and not in the GNOME Console. These commands are:
1389 \item [@input \lt{}filename\gt{}]
1390 \index[console]{@input \lt{}filename\gt{}}
1391 Read and execute the commands contained in the file specified.
1393 \item [@output \lt{}filename\gt{} w/a]
1394 \index[console]{@output \lt{}filename\gt{} w/a}
1395 Send all following output to the filename specified either overwriting the
1396 file (w) or appending to the file (a). To redirect the output to the
1397 terminal, simply enter {\bf @output} without a filename specification.
1398 WARNING: be careful not to overwrite a valid file. A typical example during a
1399 regression test might be:
1410 \item [@tee \lt{}filename\gt{} w/a]
1411 \index[console]{@tee \lt{}filename\gt{} w/a}
1412 Send all subsequent output to both the specified file and the terminal. It is
1413 turned off by specifying {\bf @tee} or {\bf @output} without a filename.
1415 \item [@sleep \lt{}seconds\gt{}]
1416 \index[console]{@sleep \lt{}seconds\gt{}}
1417 Sleep the specified number of seconds.
1420 \index[console]{@time}
1421 Print the current time and date.
1424 \index[console]{@version}
1425 Print the console's version.
1428 \index[console]{@quit}
1432 \index[console]{@exit}
1435 \item [@\# anything]
1436 \index[console]{anything}
1442 \section{Running the Console from a Shell Script}
1443 \index[general]{Script!Running the Console Program from a Shell}
1444 \index[general]{Running the Console Program from a Shell Script}
1446 You can automate many Console tasks by running the console program from a
1447 shell script. For example, if you have created a file containing the following
1452 ./bconsole -c ./bconsole.conf <<END_OF_DATA
1453 unmount storage=DDS-4
1459 when that file is executed, it will unmount the current DDS-4 storage device.
1460 You might want to run this command during a Job by using the {\bf
1461 RunBeforeJob} or {\bf RunAfterJob} records.
1463 It is also possible to run the Console program from file input where the file
1464 contains the commands as follows:
1468 ./bconsole -c ./bconsole.conf <filename
1472 where the file named {\bf filename} contains any set of console commands.
1474 As a real example, the following script is part of the Bacula regression
1475 tests. It labels a volume (a disk volume), runs a backup, then does a restore
1480 bin/bconsole -c bin/bconsole.conf <<END_OF_DATA
1483 @output /tmp/log1.out
1484 label volume=TestVolume001
1491 @output /tmp/log2.out
1502 The output from the backup is directed to /tmp/log1.out and the output from
1503 the restore is directed to /tmp/log2.out. To ensure that the backup and
1504 restore ran correctly, the output files are checked with:
1508 grep "^Termination: *Backup OK" /tmp/log1.out
1510 grep "^Termination: *Restore OK" /tmp/log2.out
1515 \section{Adding Volumes to a Pool}
1516 \index[general]{Adding Volumes to a Pool}
1517 \index[general]{Pool!Adding Volumes to a}
1519 If you have used the {\bf label} command to label a Volume, it will be
1520 automatically added to the Pool, and you will not need to add any media to the
1523 Alternatively, you may choose to add a number of Volumes to the pool without
1524 labeling them. At a later time when the Volume is requested by {\bf Bacula}
1525 you will need to label it.
1527 Before adding a volume, you must know the following information:
1530 \item The name of the Pool (normally "Default")
1531 \item The Media Type as specified in the Storage Resource in the Director's
1532 configuration file (e.g. "DLT8000")
1533 \item The number and names of the Volumes you wish to create.
1536 For example, to add media to a Pool, you would issue the following commands to
1537 the console program:
1542 Enter name of Pool to add Volumes to: Default
1543 Enter the Media Type: DLT8000
1544 Enter number of Media volumes to create. Max=1000: 10
1545 Enter base volume name: Save
1546 Enter the starting number: 1
1547 10 Volumes created in pool Default
1552 To see what you have added, enter:
1556 *list media pool=Default
1557 +-------+----------+---------+---------+-------+------------------+
1558 | MedId | VolumeNa | MediaTyp| VolStat | Bytes | LastWritten |
1559 +-------+----------+---------+---------+-------+------------------+
1560 | 11 | Save0001 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1561 | 12 | Save0002 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1562 | 13 | Save0003 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1563 | 14 | Save0004 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1564 | 15 | Save0005 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1565 | 16 | Save0006 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1566 | 17 | Save0007 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1567 | 18 | Save0008 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1568 | 19 | Save0009 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1569 | 20 | Save0010 | DLT8000 | Append | 0 | 0000-00-00 00:00 |
1570 +-------+----------+---------+---------+-------+------------------+
1575 Notice that the console program automatically appended a number to the base
1576 Volume name that you specify (Save in this case). If you don't want it to
1577 append a number, you can simply answer 0 (zero) to the question "Enter number
1578 of Media volumes to create. Max=1000:", and in this case, it will create a
1579 single Volume with the exact name you specify.