4 \chapter{Volume Utility Tools}
5 \label{_UtilityChapter}
6 \index[general]{Volume Utility Tools}
7 \index[general]{Tools!Volume Utility}
9 This document describes the utility programs written to aid Bacula users and
10 developers in dealing with Volumes external to Bacula.
12 \section{Specifying the Configuration File}
13 \index[general]{Specifying the Configuration File}
15 Starting with version 1.27, each of the following programs requires a valid
16 Storage daemon configuration file (actually, the only part of the
17 configuration file that these programs need is the {\bf Device} resource
18 definitions). This permits the programs to find the configuration parameters
19 for your archive device (generally a tape drive). By default, they read {\bf
20 bacula-sd.conf} in the current directory, but you may specify a different
21 configuration file using the {\bf -c} option.
24 \section{Specifying a Device Name For a Tape}
25 \index[general]{Tape!Specifying a Device Name For a}
26 \index[general]{Specifying a Device Name For a Tape}
28 Each of these programs require a {\bf device-name} where the Volume can be
29 found. In the case of a tape, this is the physical device name such as {\bf
30 /dev/nst0} or {\bf /dev/rmt/0ubn} depending on your system. For the program to
31 work, it must find the identical name in the Device resource of the
32 configuration file. See below for specifying Volume names.
34 Please note that if you have Bacula running and you ant to use
35 one of these programs, you will either need to stop the Storage daemon, or
36 {\bf unmount} any tape drive you want to use, otherwise the drive
37 will {\bf busy} because Bacula is using it.
40 \section{Specifying a Device Name For a File}
41 \index[general]{File!Specifying a Device Name For a}
42 \index[general]{Specifying a Device Name For a File}
44 If you are attempting to read or write an archive file rather than a tape, the
45 {\bf device-name} should be the full path to the archive location including
46 the filename. The filename (last part of the specification) will be stripped
47 and used as the Volume name, and the path (first part before the filename)
48 must have the same entry in the configuration file. So, the path is equivalent
49 to the archive device name, and the filename is equivalent to the volume name.
52 \section{Specifying Volumes}
53 \index[general]{Volumes!Specifying}
54 \index[general]{Specifying Volumes}
56 In general, you must specify the Volume name to each of the programs below
57 (with the exception of {\bf btape}). The best method to do so is to specify a
58 {\bf bootstrap} file on the command line with the {\bf -b} option. As part of
59 the bootstrap file, you will then specify the Volume name or Volume names if
60 more than one volume is needed. For example, suppose you want to read tapes
61 {\bf tape1} and {\bf tape2}. First construct a {\bf bootstrap} file named say,
62 {\bf list.bsr} which contains:
70 where each Volume is separated by a vertical bar. Then simply use:
74 ./bls -b list.bsr /dev/nst0
78 In the case of Bacula Volumes that are on files, you may simply append volumes
83 ./bls /tmp/test1\|test2
87 where the backslash (\textbackslash{}) was necessary as a shell escape to
88 permit entering the vertical bar (|).
90 And finally, if you feel that specifying a Volume name is a bit complicated
91 with a bootstrap file, you can use the {\bf -V} option (on all programs except
92 {\bf bcopy}) to specify one or more Volume names separated by the vertical bar
97 ./bls -V Vol001 /dev/nst0
101 You may also specify an asterisk (*) to indicate that the program should
102 accept any volume. For example:
113 \index[general]{program!bls}
115 {\bf bls} can be used to do an {\bf ls} type listing of a {\bf Bacula} tape or
120 Usage: bls [options] <device-name>
121 -b <file> specify a bootstrap file
122 -c <file> specify a config file
123 -d <level> specify debug level
124 -e <file> exclude list
125 -i <file> include list
128 (no j or k option) list saved files
130 -p proceed inspite of errors
132 -V specify Volume names (separated by |)
133 -? print this message
137 For example, to list the contents of a tape:
141 ./bls -V Volume-name /dev/nst0
145 Or to list the contents of a file:
149 ./bls /tmp/Volume-name
151 ./bls -V Volume-name /tmp
155 Note that, in the case of a file, the Volume name becomes the filename, so in
156 the above example, you will replace the {\bf Volume-name} with the name of the volume
159 Normally if no options are specified, {\bf bls} will produce the equivalent
160 output to the {\bf ls -l} command for each file on the tape. Using other
161 options listed above, it is possible to display only the Job records, only the
162 tape blocks, etc. For example:
168 bls: butil.c:148 Using device: /tmp
169 drwxrwxr-x 3 k k 4096 02-10-19 21:08 /home/kern/bacula/k/src/dird/
170 drwxrwxr-x 2 k k 4096 02-10-10 18:59 /home/kern/bacula/k/src/dird/CVS/
171 -rw-rw-r-- 1 k k 54 02-07-06 18:02 /home/kern/bacula/k/src/dird/CVS/Root
172 -rw-rw-r-- 1 k k 16 02-07-06 18:02 /home/kern/bacula/k/src/dird/CVS/Repository
173 -rw-rw-r-- 1 k k 1783 02-10-10 18:59 /home/kern/bacula/k/src/dird/CVS/Entries
174 -rw-rw-r-- 1 k k 97506 02-10-18 21:07 /home/kern/bacula/k/src/dird/Makefile
175 -rw-r--r-- 1 k k 3513 02-10-18 21:02 /home/kern/bacula/k/src/dird/Makefile.in
176 -rw-rw-r-- 1 k k 4669 02-07-06 18:02 /home/kern/bacula/k/src/dird/README-config
177 -rw-r--r-- 1 k k 4391 02-09-14 16:51 /home/kern/bacula/k/src/dird/authenticate.c
178 -rw-r--r-- 1 k k 3609 02-07-07 16:41 /home/kern/bacula/k/src/dird/autoprune.c
179 -rw-rw-r-- 1 k k 4418 02-10-18 21:03 /home/kern/bacula/k/src/dird/bacula-dir.conf
181 -rw-rw-r-- 1 k k 83 02-08-31 19:19 /home/kern/bacula/k/src/dird/.cvsignore
182 bls: Got EOF on device /tmp
187 \subsection{Listing Jobs}
188 \index[general]{Listing Jobs with bls}
189 \index[general]{bls!Listing Jobs}
191 If you are listing a Volume to determine what Jobs to restore, normally the
192 {\bf -j} option provides you with most of what you will need as long as you
193 don't have multiple clients. For example,
197 ./bls -j -V Test1 -c stored.conf DDS-4
198 bls: butil.c:258 Using device: "DDS-4" for reading.
199 11-Jul 11:54 bls: Ready to read from volume "Test1" on device "DDS-4" (/dev/nst0).
200 Volume Record: File:blk=0:1 SessId=4 SessTime=1121074625 JobId=0 DataLen=165
201 Begin Job Session Record: File:blk=0:2 SessId=4 SessTime=1121074625 JobId=1 Level=F Type=B
202 Begin Job Session Record: File:blk=0:3 SessId=5 SessTime=1121074625 JobId=5 Level=F Type=B
203 Begin Job Session Record: File:blk=0:6 SessId=3 SessTime=1121074625 JobId=2 Level=F Type=B
204 Begin Job Session Record: File:blk=0:13 SessId=2 SessTime=1121074625 JobId=4 Level=F Type=B
205 End Job Session Record: File:blk=0:99 SessId=3 SessTime=1121074625 JobId=2 Level=F Type=B
206 Files=168 Bytes=1,732,978 Errors=0 Status=T
207 End Job Session Record: File:blk=0:101 SessId=2 SessTime=1121074625 JobId=4 Level=F Type=B
208 Files=168 Bytes=1,732,978 Errors=0 Status=T
209 End Job Session Record: File:blk=0:108 SessId=5 SessTime=1121074625 JobId=5 Level=F Type=B
210 Files=168 Bytes=1,732,978 Errors=0 Status=T
211 End Job Session Record: File:blk=0:109 SessId=4 SessTime=1121074625 JobId=1 Level=F Type=B
212 Files=168 Bytes=1,732,978 Errors=0 Status=T
213 11-Jul 11:54 bls: End of Volume at file 1 on device "DDS-4" (/dev/nst0), Volume "Test1"
214 11-Jul 11:54 bls: End of all volumes.
218 shows a full save followed by two incremental saves.
220 Adding the {\bf -v} option will display virtually all information that is
221 available for each record:
223 \subsection{Listing Blocks}
224 \index[general]{Listing Blocks with bls}
225 \index[general]{bls!Listing Blocks}
227 Normally, except for debugging purposes, you will not need to list Bacula
228 blocks (the "primitive" unit of Bacula data on the Volume). However, you can
233 ./bls -k /tmp/File002
234 bls: butil.c:148 Using device: /tmp
240 bls: Got EOF on device /tmp
241 End of File on device
245 By adding the {\bf -v} option, you can get more information, which can be
246 useful in knowing what sessions were written to the volume:
250 ./bls -k -v /tmp/File002
252 Id : Bacula 0.9 mortal
257 LabelType : VOL_LABEL
263 Date label written: 2002-10-19 at 21:16
264 Block: 1 blen=64512 First rec FI=VOL_LABEL SessId=1 SessTim=1035062102 Strm=0 rlen=147
265 Block: 2 blen=64512 First rec FI=6 SessId=1 SessTim=1035062102 Strm=DATA rlen=4087
266 Block: 3 blen=64512 First rec FI=12 SessId=1 SessTim=1035062102 Strm=DATA rlen=5902
267 Block: 4 blen=64512 First rec FI=19 SessId=1 SessTim=1035062102 Strm=DATA rlen=28382
269 Block: 65 blen=64512 First rec FI=83 SessId=1 SessTim=1035062102 Strm=DATA rlen=1873
270 Block: 66 blen=19195 First rec FI=83 SessId=1 SessTim=1035062102 Strm=DATA rlen=2973
271 bls: Got EOF on device /tmp
272 End of File on device
276 Armed with the SessionId and the SessionTime, you can extract just about
279 If you want to know even more, add a second {\bf -v} to the command line to
280 get a dump of every record in every block.
284 ./bls -k -v -v /tmp/File002
285 bls: block.c:79 Dump block 80f8ad0: size=64512 BlkNum=1
286 Hdrcksum=b1bdfd6d cksum=b1bdfd6d
287 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=VOL_LABEL Strm=0 len=147 p=80f8b40
288 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=SOS_LABEL Strm=-7 len=122 p=80f8be7
289 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=1 Strm=UATTR len=86 p=80f8c75
290 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=2 Strm=UATTR len=90 p=80f8cdf
291 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=3 Strm=UATTR len=92 p=80f8d4d
292 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=3 Strm=DATA len=54 p=80f8dbd
293 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=3 Strm=MD5 len=16 p=80f8e07
294 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=4 Strm=UATTR len=98 p=80f8e2b
295 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=4 Strm=DATA len=16 p=80f8ea1
296 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=4 Strm=MD5 len=16 p=80f8ec5
297 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=5 Strm=UATTR len=96 p=80f8ee9
298 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=5 Strm=DATA len=1783 p=80f8f5d
299 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=5 Strm=MD5 len=16 p=80f9668
300 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=6 Strm=UATTR len=95 p=80f968c
301 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=6 Strm=DATA len=32768 p=80f96ff
302 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=6 Strm=DATA len=32768 p=8101713
303 bls: block.c:79 Dump block 80f8ad0: size=64512 BlkNum=2
304 Hdrcksum=9acc1e7f cksum=9acc1e7f
305 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=6 Strm=contDATA len=4087 p=80f8b40
306 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=6 Strm=DATA len=31970 p=80f9b4b
307 bls: block.c:92 Rec: VId=1 VT=1035062102 FI=6 Strm=MD5 len=16 p=8101841
314 \index[general]{Bextract}
315 \index[general]{program!bextract}
317 If you find yourself using {\bf bextract}, you probably have done
318 something wrong. For example, if you are trying to recover a file
319 but are having problems, please see the \ilink {Restoring When Things Go
320 Wrong}{database_restore} section of the Restore chapter of this manual.
322 Normally, you will restore files by running a {\bf Restore} Job from the {\bf
323 Console} program. However, {\bf bextract} can be used to extract a single file
324 or a list of files from a Bacula tape or file. In fact, {\bf bextract} can be
325 a useful tool to restore files to an empty system assuming you are able to
326 boot, you have statically linked {\bf bextract} and you have an appropriate
327 {\bf bootstrap} file.
329 Please note that some of the current limitations of bextract are:
332 \item It cannot restore access control lists (ACL) that have been
333 backed up along with the file data.
334 \item It cannot restore encrypted files.
335 \item The command line length is relatively limited,
336 which means that you cannot enter a huge number of volumes. If you need to
337 enter more volumes than the command line supports, please use a bootstrap
347 Usage: bextract [-d debug_level] <device-name> <directory-to-store-files>
348 -b <file> specify a bootstrap file
349 -dnn set debug level to nn
350 -e <file> exclude list
351 -i <file> include list
352 -p proceed inspite of I/O errors
353 -V specify Volume names (separated by |)
354 -? print this message
358 where {\bf device-name} is the Archive Device (raw device name or full
359 filename) of the device to be read, and {\bf directory-to-store-files} is a
360 path prefix to prepend to all the files restored.
362 NOTE: On Windows systems, if you specify a prefix of say d:/tmp, any file that
363 would have been restored to {\bf c:/My Documents} will be restored to {\bf
364 d:/tmp/My Documents}. That is, the original drive specification will be
365 stripped. If no prefix is specified, the file will be restored to the original
368 \subsection{Extracting with Include or Exclude Lists}
369 \index[general]{Lists!Extracting with Include or Exclude}
370 \index[general]{Extracting with Include or Exclude Lists}
372 Using the {\bf -e} option, you can specify a file containing a list of files
373 to be excluded. Wildcards can be used in the exclusion list. This option will
374 normally be used in conjunction with the {\bf -i} option (see below). Both the
375 {\bf -e} and the {\bf -i} options may be specified at the same time as the
376 {\bf -b} option. The bootstrap filters will be applied first, then the include
377 list, then the exclude list.
379 Likewise, and probably more importantly, with the {\bf -i} option, you can
380 specify a file that contains a list (one file per line) of files and
381 directories to include to be restored. The list must contain the full filename
382 with the path. If you specify a path name only, all files and subdirectories
383 of that path will be restored. If you specify a line containing only the
384 filename (e.g. {\bf my-file.txt}) it probably will not be extracted because
385 you have not specified the full path.
387 For example, if the file {\bf include-list} contains:
400 ./bextract -i include-list -V Volume /dev/nst0 /tmp
404 will restore from the Bacula archive {\bf /dev/nst0} all files and directories
405 in the backup from {\bf /home/kern/bacula} and from {\bf /usr/local/bin}. The
406 restored files will be placed in a file of the original name under the
407 directory {\bf /tmp} (i.e. /tmp/home/kern/bacula/... and
408 /tmp/usr/local/bin/...).
410 \subsection{Extracting With a Bootstrap File}
411 \index[general]{File!Extracting With a Bootstrap}
412 \index[general]{Extracting With a Bootstrap File}
414 The {\bf -b} option is used to specify a {\bf bootstrap} file containing the
415 information needed to restore precisely the files you want. Specifying a {\bf
416 bootstrap} file is optional but recommended because it gives you the most
417 control over which files will be restored. For more details on the {\bf
418 bootstrap} file, please see
419 \ilink{Restoring Files with the Bootstrap File}{BootstrapChapter}
420 chapter of this document. Note, you may also use a bootstrap file produced by
421 the {\bf restore} command. For example:
425 ./bextract -b bootstrap-file /dev/nst0 /tmp
429 The bootstrap file allows detailed specification of what files you want
430 restored (extracted). You may specify a bootstrap file and include and/or
431 exclude files at the same time. The bootstrap conditions will first be
432 applied, and then each file record seen will be compared to the include and
435 \subsection{Extracting From Multiple Volumes}
436 \index[general]{Volumes!Extracting From Multiple}
437 \index[general]{Extracting From Multiple Volumes}
439 If you wish to extract files that span several Volumes, you can specify the
440 Volume names in the bootstrap file or you may specify the Volume names on the
441 command line by separating them with a vertical bar. See the section above
442 under the {\bf bls} program entitled {\bf Listing Multiple Volumes} for more
443 information. The same techniques apply equally well to the {\bf bextract}
444 program or read the \ilink{Bootstrap}{BootstrapChapter}
445 chapter of this document.
449 \index[general]{bscan}
450 \index[general]{program!bscan}
452 If you find yourself using this program, you have probably done something
453 wrong. For example, the best way to recover a lost or damaged Bacula
454 database is to reload the database by using the bootstrap file that
455 was written when you saved it (default bacula-dir.conf file).
457 The {\bf bscan} program can be used to re-create a database (catalog)
458 records from the backup information written to one or more Volumes. This
459 is normally needed only if one or more Volumes have been pruned or purged
460 from your catalog so that the records on the Volume are no longer in the
461 catalog, or for Volumes that you have archived. Note, if you scan in
462 Volumes that were previously purged, you will be able to do restores from
463 those Volumes. However, unless you modify the Job and File retention times
464 for the Jobs that were added by scanning, the next time you run any backup Job
465 with the same name, the records will be pruned again. Since it takes a
466 long time to scan Volumes this can be very frustrating.
468 With some care, {\bf bscan} can also be used to synchronize your existing
469 catalog with a Volume. Although we have never seen a case of bscan
470 damaging a catalog, since bscan modifies your catalog, we recommend that
471 you do a simple ASCII backup of your database before running {\bf bscan}
472 just to be sure. See \ilink{Compacting Your Database}{CompactingMySQL} for
473 the details of making a copy of your database.
475 {\bf bscan} can also be useful in a disaster recovery situation, after the
476 loss of a hard disk, if you do not have a valid {\bf bootstrap} file for
477 reloading your system, or if a Volume has been recycled but not overwritten,
478 you can use {\bf bscan} to re-create your database, which can then be used to
479 {\bf restore} your system or a file to its previous state.
486 Usage: bscan [options] <bacula-archive>
487 -b bootstrap specify a bootstrap file
488 -c <file> specify configuration file
489 -d <nn> set debug level to nn
490 -m update media info in database
491 -n <name> specify the database name (default bacula)
492 -u <user> specify database user name (default bacula)
493 -P <password> specify database password (default none)
494 -h <host> specify database host (default NULL)
495 -p proceed inspite of I/O errors
497 -s synchronize or store in database
499 -V <Volumes> specify Volume names (separated by |)
500 -w <dir> specify working directory (default from conf file)
501 -? print this message
505 If you are using MySQL or PostgreSQL, there is no need to supply a working
506 directory since in that case, bscan knows where the databases are. However, if
507 you have provided security on your database, you may need to supply either the
508 database name ({\bf -b} option), the user name ({\bf -u} option), and/or the
509 password ({\bf -p}) options.
511 NOTE: before {\bf bscan} can work, it needs at least a bare bones valid
512 database. If your database exists but some records are missing because
513 they were pruned, then you are all set. If your database was lost or
514 destroyed, then you must first ensure that you have the SQL program running
515 (MySQL or PostgreSQL), then you must create the Bacula database (normally
516 named bacula), and you must create the Bacula tables using the scripts in
517 the {\bf cats} directory. This is explained in the
518 \ilink{Installation}{CreateDatabase} chapter of the manual. Finally, before
519 scanning into an empty database, you must start and stop the Director with
520 the appropriate bacula-dir.conf file so that it can create the Client and
521 Storage records which are not stored on the Volumes. Without these
522 records, scanning is unable to connect the Job records to the proper
525 Forgetting for the moment the extra complications of a full rebuild of
526 your catalog, let's suppose that you did a backup to Volumes "Vol001"
527 and "Vol002", then sometime later all records of one or both those
528 Volumes were pruned or purged from the
529 database. By using {\bf bscan} you can recreate the catalog entries for
530 those Volumes and then use the {\bf restore} command in the Console to restore
531 whatever you want. A command something like:
535 bscan -c bacula-sd.conf -v -V Vol001\|Vol002 /dev/nst0
539 will give you an idea of what is going to happen without changing
540 your catalog. Of course, you may need to change the path to the Storage
541 daemon's conf file, the Volume name, and your tape (or disk) device name. This
542 command must read the entire tape, so if it has a lot of data, it may take a
543 long time, and thus you might want to immediately use the command listed
544 below. Note, if you are writing to a disk file, replace the device name with
545 the path to the directory that contains the Volumes. This must correspond to
546 the Archive Device in the conf file.
548 Then to actually write or store the records in the catalog, add the {\bf -s}
553 bscan -s -m -c bacula-sd.conf -v -V Vol001\|Vol002 /dev/nst0
557 When writing to the database, if bscan finds existing records, it will
558 generally either update them if something is wrong or leave them alone. Thus
559 if the Volumes you are scanning are all or partially in the catalog already, no
560 harm will be done to that existing data. Any missing data will simply be
563 If you have multiple tapes, you should scan them with:
567 bscan -s -m -c bacula-sd.conf -v -V Vol001\|Vol002\|Vol003 /dev/nst0
571 Since there is a limit on the command line length (511 bytes) accepted
572 by {\bf bscan}, if you have too many Volumes, you will need to manually
573 create a bootstrap file. See the \ilink{Bootstrap}{BootstrapChapter}
574 chapter of this manual for more details, in particular the section
575 entitled \ilink{Bootstrap for bscan}{bscanBootstrap}. Basically, the
576 .bsr file for the above example might look like:
586 You should, always try to specify the tapes in the order they are written.
587 If you do not, any Jobs that span a volume may not be fully or properly
588 restored. However, bscan can handle scanning tapes that are not sequential. Any
589 incomplete records at the end of the tape will simply be ignored in that
590 case. If you are simply repairing an existing catalog, this may be OK, but
591 if you are creating a new catalog from scratch, it will leave your database
592 in an incorrect state. If you do not specify all necessary Volumes on a
593 single bscan command, bscan will not be able to correctly restore the
594 records that span two volumes. In other words, it is much better to
595 specify two or three volumes on a single bscan command (or in a .bsr file)
596 rather than run bscan two or three times, each with a single volume.
599 Note, the restoration process using bscan is not identical to the original
600 creation of the catalog data. This is because certain data such as Client
601 records and other non-essential data such
602 as volume reads, volume mounts, etc is not stored on the Volume, and thus is
603 not restored by bscan. The results of bscanning are, however, perfectly valid,
604 and will permit restoration of any or all the files in the catalog using the
605 normal Bacula console commands. If you are starting with an empty catalog
606 and expecting bscan to reconstruct it, you may be a bit disappointed, but
607 at a minimum, you must ensure that your bacula-dir.conf file is the same
608 as what it previously was -- that is, it must contain all the appropriate
609 Client resources so that they will be recreated in your new database {\bf
610 before} running bscan. Normally when the Director starts, it will recreate
611 any missing Client records in the catalog. Another problem you will have
612 is that even if the Volumes (Media records) are recreated in the database,
613 they will not have their autochanger status and slots properly set. As a
614 result, you will need to repair that by using the {\bf update slots}
615 command. There may be other considerations as well. Rather than
616 bscanning, you should always attempt to recover you previous catalog
620 \subsection{Using bscan to Compare a Volume to an existing Catalog}
621 \index[general]{Catalog!Using bscan to Compare a Volume to an existing}
622 \index[general]{Using bscan to Compare a Volume to an existing Catalog}
624 If you wish to compare the contents of a Volume to an existing catalog without
625 changing the catalog, you can safely do so if and only if you do {\bf not}
626 specify either the {\bf -m} or the {\bf -s} options. However, at this time
627 (Bacula version 1.26), the comparison routines are not as good or as thorough
628 as they should be, so we don't particularly recommend this mode other than for
631 \subsection{Using bscan to Recreate a Catalog from a Volume}
632 \index[general]{Volume!Using bscan to Recreate a Catalog from a Volume}
633 \index[general]{Using bscan to Recreate a Catalog from a Volume}
635 This is the mode for which {\bf bscan} is most useful. You can either {\bf
636 bscan} into a freshly created catalog, or directly into your existing catalog
637 (after having made an ASCII copy as described above). Normally, you should
638 start with a freshly created catalog that contains no data.
640 Starting with a single Volume named {\bf TestVolume1}, you run a command such
645 ./bscan -V TestVolume1 -v -s -m -c bacula-sd.conf /dev/nst0
649 If there is more than one volume, simply append it to the first one separating
650 it with a vertical bar. You may need to precede the vertical bar with a
651 forward slash escape the shell -- e.g. {\bf
652 TestVolume1\textbackslash{}|TestVolume2}. The {\bf -v} option was added for
653 verbose output (this can be omitted if desired). The {\bf -s} option that
654 tells {\bf bscan} to store information in the database. The physical device
655 name {\bf /dev/nst0} is specified after all the options.
657 {\bf} For example, after having done a full backup of a directory, then two
658 incrementals, I reinitialized the SQLite database as described above, and
659 using the bootstrap.bsr file noted above, I entered the following command:
663 ./bscan -b bootstrap.bsr -v -s -c bacula-sd.conf /dev/nst0
667 which produced the following output:
671 bscan: bscan.c:182 Using Database: bacula, User: bacula
672 bscan: bscan.c:673 Created Pool record for Pool: Default
673 bscan: bscan.c:271 Pool type "Backup" is OK.
674 bscan: bscan.c:632 Created Media record for Volume: TestVolume1
675 bscan: bscan.c:298 Media type "DDS-4" is OK.
676 bscan: bscan.c:307 VOL_LABEL: OK for Volume: TestVolume1
677 bscan: bscan.c:693 Created Client record for Client: Rufus
678 bscan: bscan.c:769 Created new JobId=1 record for original JobId=2
679 bscan: bscan.c:717 Created FileSet record "Kerns Files"
680 bscan: bscan.c:819 Updated Job termination record for new JobId=1
681 bscan: bscan.c:905 Created JobMedia record JobId 1, MediaId 1
682 bscan: Got EOF on device /dev/nst0
683 bscan: bscan.c:693 Created Client record for Client: Rufus
684 bscan: bscan.c:769 Created new JobId=2 record for original JobId=3
685 bscan: bscan.c:708 Fileset "Kerns Files" already exists.
686 bscan: bscan.c:819 Updated Job termination record for new JobId=2
687 bscan: bscan.c:905 Created JobMedia record JobId 2, MediaId 1
688 bscan: Got EOF on device /dev/nst0
689 bscan: bscan.c:693 Created Client record for Client: Rufus
690 bscan: bscan.c:769 Created new JobId=3 record for original JobId=4
691 bscan: bscan.c:708 Fileset "Kerns Files" already exists.
692 bscan: bscan.c:819 Updated Job termination record for new JobId=3
693 bscan: bscan.c:905 Created JobMedia record JobId 3, MediaId 1
694 bscan: Got EOF on device /dev/nst0
695 bscan: bscan.c:652 Updated Media record at end of Volume: TestVolume1
696 bscan: bscan.c:428 End of Volume. VolFiles=3 VolBlocks=57 VolBytes=10,027,437
700 The key points to note are that {\bf bscan} prints a line when each major
701 record is created. Due to the volume of output, it does not print a line for
702 each file record unless you supply the {\bf -v} option twice or more on the
705 In the case of a Job record, the new JobId will not normally be the same as
706 the original Jobid. For example, for the first JobId above, the new JobId is
707 1, but the original JobId is 2. This is nothing to be concerned about as it is
708 the normal nature of databases. {\bf bscan} will keep everything straight.
710 Although {\bf bscan} claims that it created a Client record for Client: Rufus
711 three times, it was actually only created the first time. This is normal.
713 You will also notice that it read an end of file after each Job (Got EOF on
714 device ...). Finally the last line gives the total statistics for the bscan.
716 If you had added a second {\bf -v} option to the command line, Bacula would
717 have been even more verbose, dumping virtually all the details of each Job
718 record it encountered.
720 Now if you start Bacula and enter a {\bf list jobs} command to the console
721 program, you will get:
725 +-------+----------+------------------+------+-----+----------+----------+---------+
726 | JobId | Name | StartTime | Type | Lvl | JobFiles | JobBytes | JobStat |
727 +-------+----------+------------------+------+-----+----------+----------+---------+
728 | 1 | kernsave | 2002-10-07 14:59 | B | F | 84 | 4180207 | T |
729 | 2 | kernsave | 2002-10-07 15:00 | B | I | 15 | 2170314 | T |
730 | 3 | kernsave | 2002-10-07 15:01 | B | I | 33 | 3662184 | T |
731 +-------+----------+------------------+------+-----+----------+----------+---------+
735 which corresponds virtually identically with what the database contained
736 before it was re-initialized and restored with bscan. All the Jobs and Files
737 found on the tape are restored including most of the Media record. The Volume
738 (Media) records restored will be marked as {\bf Full} so that they cannot be
739 rewritten without operator intervention.
741 It should be noted that {\bf bscan} cannot restore a database to the exact
742 condition it was in previously because a lot of the less important information
743 contained in the database is not saved to the tape. Nevertheless, the
744 reconstruction is sufficiently complete, that you can run {\bf restore}
745 against it and get valid results.
747 An interesting aspect of restoring a catalog backup using {\bf bscan} is
748 that the backup was made while Bacula was running and writing to a tape. At
749 the point the backup of the catalog is made, the tape Bacula is writing to
750 will have say 10 files on it, but after the catalog backup is made, there
751 will be 11 files on the tape Bacula is writing. This there is a difference
752 between what is contained in the backed up catalog and what is actually on
753 the tape. If after restoring a catalog, you attempt to write on the same
754 tape that was used to backup the catalog, Bacula will detect the difference
755 in the number of files registered in the catalog compared to what is on the
756 tape, and will mark the tape in error.
758 There are two solutions to this problem. The first is possibly the simplest
759 and is to mark the volume as Used before doing any backups. The second is
760 to manually correct the number of files listed in the Media record of the
761 catalog. This procedure is documented elsewhere in the manual and involves
762 using the {\bf update volume} command in {\bf bconsole}.
764 \subsection{Using bscan to Correct the Volume File Count}
765 \index[general]{Using bscan to Correct the Volume File Count}
766 \index[general]{Count!Using bscan to Correct the Volume File Count}
768 If the Storage daemon crashes during a backup Job, the catalog will not be
769 properly updated for the Volume being used at the time of the crash. This
770 means that the Storage daemon will have written say 20 files on the tape, but
771 the catalog record for the Volume indicates only 19 files.
773 Bacula refuses to write on a tape that contains a different number of files
774 from what is in the catalog. To correct this situation, you may run a {\bf
775 bscan} with the {\bf -m} option (but {\bf without} the {\bf -s} option) to
776 update only the final Media record for the Volumes read.
778 \subsection{After bscan}
779 \index[general]{After bscan}
780 \index[general]{Bscan!After}
782 If you use {\bf bscan} to enter the contents of the Volume into an existing
783 catalog, you should be aware that the records you entered may be immediately
784 pruned during the next job, particularly if the Volume is very old or had been
785 previously purged. To avoid this, after running {\bf bscan}, you can manually
786 set the volume status (VolStatus) to {\bf Read-Only} by using the {\bf update}
787 command in the catalog. This will allow you to restore from the volume without
788 having it immediately purged. When you have restored and backed up the data,
789 you can reset the VolStatus to {\bf Used} and the Volume will be purged from
794 \index[general]{Bcopy}
795 \index[general]{program!bcopy}
797 The {\bf bcopy} program can be used to copy one {\bf Bacula} archive file to
798 another. For example, you may copy a tape to a file, a file to a tape, a file
799 to a file, or a tape to a tape. For tape to tape, you will need two tape
800 drives. (a later version is planned that will buffer it to disk). In the
801 process of making the copy, no record of the information written to the new
802 Volume is stored in the catalog. This means that the new Volume, though it
803 contains valid backup data, cannot be accessed directly from existing catalog
804 entries. If you wish to be able to use the Volume with the Console restore
805 command, for example, you must first bscan the new Volume into the catalog.
807 \subsection{bcopy Command Options}
808 \index[general]{Options!bcopy Command}
809 \index[general]{Bcopy Command Options}
813 Usage: bcopy [-d debug_level] <input-archive> <output-archive>
814 -b bootstrap specify a bootstrap file
815 -c <file> specify configuration file
816 -dnn set debug level to nn
817 -i specify input Volume names (separated by |)
818 -o specify output Volume names (separated by |)
819 -p proceed inspite of I/O errors
821 -w dir specify working directory (default /tmp)
822 -? print this message
826 By using a {\bf bootstrap} file, you can copy parts of a Bacula archive file
829 One of the objectives of this program is to be able to recover as much data as
830 possible from a damaged tape. However, the current version does not yet have
833 As this is a new program, any feedback on its use would be appreciated. In
834 addition, I only have a single tape drive, so I have never been able to test
835 this program with two tape drives.
839 \index[general]{Btape}
840 \index[general]{program!btape}
842 This program permits a number of elementary tape operations via a tty command
843 interface. It works only with tapes and not with other kinds of Bacula
844 storage media (DVD, File, ...). The {\bf test} command, described below,
845 can be very useful for testing older tape drive compatibility problems.
846 Aside from initial testing of tape drive compatibility with {\bf Bacula},
847 {\bf btape} will be mostly used by developers writing new tape drivers.
849 {\bf btape} can be dangerous to use with existing {\bf Bacula} tapes because
850 it will relabel a tape or write on the tape if so requested regardless that
851 the tape may contain valuable data, so please be careful and use it only on
854 To work properly, {\bf btape} needs to read the Storage daemon's configuration
855 file. As a default, it will look for {\bf bacula-sd.conf} in the current
856 directory. If your configuration file is elsewhere, please use the {\bf -c}
857 option to specify where.
859 The physical device name must be specified on the command line, and this
860 same device name must be present in the Storage daemon's configuration file
865 Usage: btape <options> <device_name>
866 -b <file> specify bootstrap file
867 -c <file> set configuration file to file
868 -d <nn> set debug level to nn
869 -p proceed inspite of I/O errors
872 -? print this message.
876 \subsection{Using btape to Verify your Tape Drive}
877 \index[general]{Using btape to Verify your Tape Drive}
878 \index[general]{Drive!Using btape to Verify your Tape}
880 An important reason for this program is to ensure that a Storage daemon
881 configuration file is defined so that Bacula will correctly read and write
884 It is highly recommended that you run the {\bf test} command before running
885 your first Bacula job to ensure that the parameters you have defined for your
886 storage device (tape drive) will permit {\bf Bacula} to function properly. You
887 only need to mount a blank tape, enter the command, and the output should be
888 reasonably self explanatory. Please see the
889 \ilink{Tape Testing}{TapeTestingChapter} Chapter of this manual for
892 \subsection{btape Commands}
893 \index[general]{Btape Commands}
894 \index[general]{Commands!btape}
896 The full list of commands are:
902 autochanger test autochanger
905 cap list device capabilities
906 clear clear tape errors
907 eod go to end of Bacula data for append
908 eom go to the physical end of medium
909 fill fill tape, write onto second volume
910 unfill read filled tape
911 fsf forward space a file
912 fsr forward space a record
913 help print this command
914 label write a Bacula label to the tape
917 rawfill use write() to fill tape
918 readlabel read and print the Bacula tape label
919 rectest test record handling functions
920 rewind rewind the tape
921 scan read() tape block by block to EOT and report
922 scanblocks Bacula read block by block to EOT and report
923 speed report drive speed
924 status print tape status
925 test General test Bacula tape functions
926 weof write an EOF on the tape
927 wr write a single Bacula block
928 rr read a single record
929 qfill quick fill command
933 The most useful commands are:
936 \item test -- test writing records and EOF marks and reading them back.
937 \item fill -- completely fill a volume with records, then write a few records
938 on a second volume, and finally, both volumes will be read back.
939 This command writes blocks containing random data, so your drive will
940 not be able to compress the data, and thus it is a good test of
941 the real physical capacity of your tapes.
942 \item readlabel -- read and dump the label on a Bacula tape.
943 \item cap -- list the device capabilities as defined in the configuration
944 file and as perceived by the Storage daemon.
947 The {\bf readlabel} command can be used to display the details of a Bacula
948 tape label. This can be useful if the physical tape label was lost or damaged.
951 In the event that you want to relabel a {\bf Bacula}, you can simply use the
952 {\bf label} command which will write over any existing label. However, please
953 note for labeling tapes, we recommend that you use the {\bf label} command in
954 the {\bf Console} program since it will never overwrite a valid Bacula tape.
956 \subsubsection*{Testing your Tape Drive}
957 \label{sec:btapespeed}
959 To determine the best configuration of your tape drive, you can run the new
960 \texttt{speed} command available in the \texttt{btape} program.
962 This command can have the following arguments:
964 \item[\texttt{file\_size=n}] Specify the Maximum File Size for this test
965 (between 1 and 5GB). This counter is in GB.
966 \item[\texttt{nb\_file=n}] Specify the number of file to be written. The amount
967 of data should be greater than your memory ($file\_size*nb\_file$).
968 \item[\texttt{skip\_zero}] This flag permits to skip tests with constant
970 \item[\texttt{skip\_random}] This flag permits to skip tests with random
972 \item[\texttt{skip\_raw}] This flag permits to skip tests with raw access.
973 \item[\texttt{skip\_block}] This flag permits to skip tests with Bacula block
978 *speed file_size=3 skip_raw
979 btape.c:1078 Test with zero data and bacula block structure.
980 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
981 ++++++++++++++++++++++++++++++++++++++++++
982 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
983 btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 MB/s
985 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 MB/s
987 btape.c:1090 Test with random data, should give the minimum throughput.
988 btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
989 +++++++++++++++++++++++++++++++++++++++++++
990 btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
991 btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 MB/s
992 +++++++++++++++++++++++++++++++++++++++++++
994 btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s
998 When using compression, the random test will give your the minimum throughput
999 of your drive . The test using constant string will give you the maximum speed
1000 of your hardware chain. (cpu, memory, scsi card, cable, drive, tape).
1002 You can change the block size in the Storage Daemon configuration file.
1004 \section{Other Programs}
1005 \index[general]{Programs!Other}
1006 \index[general]{Other Programs}
1008 The following programs are general utility programs and in general do not need
1009 a configuration file nor a device name.
1013 \index[general]{Bsmtp}
1014 \index[general]{program!bsmtp}
1016 {\bf bsmtp} is a simple mail transport program that permits more flexibility
1017 than the standard mail programs typically found on Unix systems. It can even
1018 be used on Windows machines.
1024 Usage: bsmtp [-f from] [-h mailhost] [-s subject] [-c copy] [recipient ...]
1025 -c set the Cc: field
1026 -dnn set debug level to nn
1027 -f set the From: field
1028 -h use mailhost:port as the bsmtp server
1029 -l limit the lines accepted to nn
1030 -s set the Subject: field
1031 -? print this message.
1035 If the {\bf -f} option is not specified, {\bf bsmtp} will use your userid. If
1036 the option {\bf -h} is not specified {\bf bsmtp} will use the value in the environment
1037 variable {\bf bsmtpSERVER} or if there is none {\bf localhost}. By default
1040 If a line count limit is set with the {\bf -l} option, {\bf bsmtp} will
1041 not send an email with a body text exceeding that number of lines. This
1042 is especially useful for large restore job reports where the list of
1043 files restored might produce very long mails your mail-server would
1044 refuse or crash. However, be aware that you will probably suppress the
1045 job report and any error messages unless you check the log file written
1046 by the Director (see the messages resource in this manual for details).
1049 {\bf recipients} is a space separated list of email recipients.
1051 The body of the email message is read from standard input.
1053 An example of the use of {\bf bsmtp} would be to put the following statement
1054 in the {\bf Messages} resource of your {\bf bacula-dir.conf} file. Note, these
1055 commands should appear on a single line each.
1059 mailcommand = "/home/bacula/bin/bsmtp -h mail.domain.com -f \"\(Bacula\) %r\"
1060 -s \"Bacula: %t %e of %c %l\" %r"
1061 operatorcommand = "/home/bacula/bin/bsmtp -h mail.domain.com -f \"\(Bacula\) %r\"
1062 -s \"Bacula: Intervention needed for %j\" %r"
1066 Where you replace {\bf /home/bacula/bin} with the path to your {\bf Bacula}
1067 binary directory, and you replace {\bf mail.domain.com} with the fully
1068 qualified name of your bsmtp (email) server, which normally listens on port
1069 25. For more details on the substitution characters (e.g. \%r) used in the
1070 above line, please see the documentation of the
1071 \ilink{ MailCommand in the Messages Resource}{mailcommand}
1072 chapter of this manual.
1074 It is HIGHLY recommended that you test one or two cases by hand to make sure
1075 that the {\bf mailhost} that you specified is correct and that it will accept
1076 your email requests. Since {\bf bsmtp} always uses a TCP connection rather
1077 than writing in the spool file, you may find that your {\bf from} address is
1078 being rejected because it does not contain a valid domain, or because your
1079 message is caught in your spam filtering rules. Generally, you should specify
1080 a fully qualified domain name in the {\bf from} field, and depending on
1081 whether your bsmtp gateway is Exim or Sendmail, you may need to modify the
1082 syntax of the from part of the message. Please test.
1084 When running {\bf bsmtp} by hand, you will need to terminate the message by
1085 entering a ctl-d in column 1 of the last line.
1086 % TODO: is "column" the correct terminology for this?
1088 If you are getting incorrect dates (e.g. 1970) and you are
1089 running with a non-English language setting, you might try adding
1090 a LANG=''en\_US'' immediately before the bsmtp call.
1092 In general, {\bf bsmtp} attempts to cleanup email addresses that you
1093 specify in the from, copy, mailhost, and recipient fields, by adding
1094 the necessary \lt{} and \gt{} characters around the address part. However,
1095 if you include a {\bf display-name} (see RFC 5332), some SMTP servers
1096 such as Exchange may not accept the message if the {\bf display-name} is
1097 also included in \lt{} and \gt{}. As mentioned above, you must test, and
1098 if you run into this situation, you may manually add the \lt{} and \gt{}
1099 to the Bacula {\bf mailcommand} or {\bf operatorcommand} and when
1100 {\bf bsmtp} is formatting an address if it already contains a \lt{} or
1101 \gt{} character, it will leave the address unchanged.
1105 \index[general]{Dbcheck}
1106 \index[general]{program!dbcheck}
1107 {\bf dbcheck} is a simple program that will search for logical
1108 inconsistencies in the Bacula tables in your database, and optionally fix them.
1109 It is a database maintenance routine, in the sense that it can
1110 detect and remove unused rows, but it is not a database repair
1111 routine. To repair a database, see the tools furnished by the
1112 database vendor. Normally dbcheck should never need to be run,
1113 but if Bacula has crashed or you have a lot of Clients, Pools, or
1114 Jobs that you have removed, it could be useful.
1116 The {\bf dbcheck} program can be found in
1117 the {\bf \lt{}bacula-source\gt{}/src/tools} directory of the source
1118 distribution. Though it is built with the make process, it is not normally
1125 Usage: dbcheck [-c config ] [-B] [-C catalog name] [-d debug_level]
1126 <working-directory> <bacula-database> <user> <password> [<dbhost>] [<dbport>]
1128 -C catalog name in the director conf file
1129 -c Director conf filename
1130 -B print catalog configuration and exit
1131 -d <nn> set debug level to <nn>
1132 -dt print timestamp in debug output
1133 -f fix inconsistencies
1135 -? print this message
1139 If the \textbf{-B} option is specified, dbcheck will print out catalog
1140 information in a simple text based format. This is useful to backup it in a
1156 If the {\bf -c} option is given with the Director's conf file, there is no
1157 need to enter any of the command line arguments, in particular the working
1158 directory as dbcheck will read them from the file.
1160 If the {\bf -f} option is specified, {\bf dbcheck} will repair ({\bf fix}) the
1161 inconsistencies it finds. Otherwise, it will report only.
1163 If the {\bf -b} option is specified, {\bf dbcheck} will run in batch mode, and
1164 it will proceed to examine and fix (if -f is set) all programmed inconsistency
1165 checks. If the {\bf -b} option is not specified, {\bf dbcheck} will enter
1166 interactive mode and prompt with the following:
1170 Hello, this is the database check/correct program.
1171 Please select the function you want to perform.
1172 1) Toggle modify database flag
1173 2) Toggle verbose flag
1174 3) Repair bad Filename records
1175 4) Repair bad Path records
1176 5) Eliminate duplicate Filename records
1177 6) Eliminate duplicate Path records
1178 7) Eliminate orphaned Jobmedia records
1179 8) Eliminate orphaned File records
1180 9) Eliminate orphaned Path records
1181 10) Eliminate orphaned Filename records
1182 11) Eliminate orphaned FileSet records
1183 12) Eliminate orphaned Client records
1184 13) Eliminate orphaned Job records
1185 14) Eliminate all Admin records
1186 15) Eliminate all Restore records
1189 Select function number:
1193 By entering 1 or 2, you can toggle the modify database flag (-f option) and
1194 the verbose flag (-v). It can be helpful and reassuring to turn off the modify
1195 database flag, then select one or more of the consistency checks (items 3
1196 through 9) to see what will be done, then toggle the modify flag on and re-run
1199 The inconsistencies examined are the following:
1202 \item Duplicate filename records. This can happen if you accidentally run two
1203 copies of Bacula at the same time, and they are both adding filenames
1204 simultaneously. It is a rare occurrence, but will create an inconsistent
1205 database. If this is the case, you will receive error messages during Jobs
1206 warning of duplicate database records. If you are not getting these error
1207 messages, there is no reason to run this check.
1208 \item Repair bad Filename records. This checks and corrects filenames that
1209 have a trailing slash. They should not.
1210 \item Repair bad Path records. This checks and corrects path names that do
1211 not have a trailing slash. They should.
1212 \item Duplicate path records. This can happen if you accidentally run two
1213 copies of Bacula at the same time, and they are both adding filenames
1214 simultaneously. It is a rare occurrence, but will create an inconsistent
1215 database. See the item above for why this occurs and how you know it is
1217 \item Orphaned JobMedia records. This happens when a Job record is deleted
1218 (perhaps by a user issued SQL statement), but the corresponding JobMedia
1219 record (one for each Volume used in the Job) was not deleted. Normally, this
1220 should not happen, and even if it does, these records generally do not take
1221 much space in your database. However, by running this check, you can
1222 eliminate any such orphans.
1223 \item Orphaned File records. This happens when a Job record is deleted
1224 (perhaps by a user issued SQL statement), but the corresponding File record
1225 (one for each Volume used in the Job) was not deleted. Note, searching for
1226 these records can be {\bf very} time consuming (i.e. it may take hours) for a
1227 large database. Normally this should not happen as Bacula takes care to
1228 prevent it. Just the same, this check can remove any orphaned File records.
1229 It is recommended that you run this once a year since orphaned File records
1230 can take a large amount of space in your database. You might
1231 want to ensure that you have indexes on JobId, FilenameId, and
1232 PathId for the File table in your catalog before running this
1234 \item Orphaned Path records. This condition happens any time a directory is
1235 deleted from your system and all associated Job records have been purged.
1236 During standard purging (or pruning) of Job records, Bacula does not check
1237 for orphaned Path records. As a consequence, over a period of time, old
1238 unused Path records will tend to accumulate and use space in your database.
1239 This check will eliminate them. It is recommended that you run this
1240 check at least once a year.
1241 \item Orphaned Filename records. This condition happens any time a file is
1242 deleted from your system and all associated Job records have been purged.
1243 This can happen quite frequently as there are quite a large number of files
1244 that are created and then deleted. In addition, if you do a system update or
1245 delete an entire directory, there can be a very large number of Filename
1246 records that remain in the catalog but are no longer used.
1248 During standard purging (or pruning) of Job records, Bacula does not check
1249 for orphaned Filename records. As a consequence, over a period of time, old
1250 unused Filename records will accumulate and use space in your database. This
1251 check will eliminate them. It is strongly recommended that you run this check
1252 at least once a year, and for large database (more than 200 Megabytes), it is
1253 probably better to run this once every 6 months.
1254 \item Orphaned Client records. These records can remain in the database long
1255 after you have removed a client.
1256 \item Orphaned Job records. If no client is defined for a job or you do not
1257 run a job for a long time, you can accumulate old job records. This option
1258 allow you to remove jobs that are not attached to any client (and thus
1260 \item All Admin records. This command will remove all Admin records,
1261 regardless of their age.
1262 \item All Restore records. This command will remove all Restore records,
1263 regardless of their age.
1267 If you are using Mysql, dbcheck will ask you if you want to create temporary
1268 indexes to speed up orphaned Path and Filename elimination.
1270 Mostly for PostgreSQL users, we provide a pure SQL script dbcheck replacement
1271 in \url{examples/database/dbcheck.sql} that works with global queries instead
1272 of many small queries like dbcheck. Execution instructions are at the top of
1273 the script and you will need to type \texttt{COMMIT} at the end to validate
1276 If you are using bweb or brestore, don't eliminate orphaned Path, else you will
1277 have to rebuild \texttt{brestore\_pathvisibility} and
1278 \texttt{brestore\_pathhierarchy} indexes.
1280 By the way, I personally run dbcheck only where I have messed up
1281 my database due to a bug in developing Bacula code, so normally
1282 you should never need to run dbcheck in spite of the
1283 recommendations given above, which are given so that users don't
1284 waste their time running dbcheck too often.
1288 \index[general]{bregex}
1289 \index[general]{program!bregex}
1291 {\bf bregex} is a simple program that will allow you to test
1292 regular expressions against a file of data. This can be useful
1293 because the regex libraries on most systems differ, and in
1294 addition, regex expressions can be complicated.
1296 {\bf bregex} is found in the src/tools directory and it is
1297 normally installed with your system binaries. To run it, use:
1300 Usage: bregex [-d debug_level] -f <data-file>
1301 -f specify file of data to be matched
1302 -l suppress line numbers
1303 -n print lines that do not match
1304 -? print this message.
1307 The \lt{}data-file\gt{} is a filename that contains lines
1308 of data to be matched (or not) against one or more patterns.
1309 When the program is run, it will prompt you for a regular
1310 expression pattern, then apply it one line at a time against
1311 the data in the file. Each line that matches will be printed
1312 preceded by its line number. You will then be prompted again
1313 for another pattern.
1315 Enter an empty line for a pattern to terminate the program. You
1316 can print only lines that do not match by using the -n option,
1317 and you can suppress printing of line numbers with the -l option.
1319 This program can be useful for testing regex expressions to be
1320 applied against a list of filenames.
1324 \index[general]{bwild}
1325 \index[general]{program!bwild}
1327 {\bf bwild} is a simple program that will allow you to test
1328 wild-card expressions against a file of data.
1330 {\bf bwild} is found in the src/tools directory and it is
1331 normally installed with your system binaries. To run it, use:
1334 Usage: bwild [-d debug_level] -f <data-file>
1335 -f specify file of data to be matched
1336 -l suppress line numbers
1337 -n print lines that do not match
1338 -? print this message.
1341 The \lt{}data-file\gt{} is a filename that contains lines
1342 of data to be matched (or not) against one or more patterns.
1343 When the program is run, it will prompt you for a wild-card
1344 pattern, then apply it one line at a time against
1345 the data in the file. Each line that matches will be printed
1346 preceded by its line number. You will then be prompted again
1347 for another pattern.
1349 Enter an empty line for a pattern to terminate the program. You
1350 can print only lines that do not match by using the -n option,
1351 and you can suppress printing of line numbers with the -l option.
1353 This program can be useful for testing wild expressions to be
1354 applied against a list of filenames.
1358 \index[general]{Testfind}
1359 \index[general]{program!testfind}
1361 {\bf testfind} permits listing of files using the same search engine that is
1362 used for the {\bf Include} resource in Job resources. Note, much of the
1363 functionality of this program (listing of files to be included) is present in
1365 \ilink{estimate command}{estimate} in the Console program.
1367 The original use of testfind was to ensure that Bacula's file search engine
1368 was correct and to print some statistics on file name and path length.
1369 However, you may find it useful to see what bacula would do with a given {\bf
1370 Include} resource. The {\bf testfind} program can be found in the {\bf
1371 \lt{}bacula-source\gt{}/src/tools} directory of the source distribution.
1372 Though it is built with the make process, it is not normally "installed".
1378 Usage: testfind [-d debug_level] [-] [pattern1 ...]
1379 -a print extended attributes (Win32 debug)
1380 -dnn set debug level to nn
1381 - read pattern(s) from stdin
1382 -? print this message.
1383 Patterns are used for file inclusion -- normally directories.
1384 Debug level>= 1 prints each file found.
1385 Debug level>= 10 prints path/file for catalog.
1386 Errors are always printed.
1387 Files/paths truncated is a number with len> 255.
1388 Truncation is only in the catalog.
1392 Where a pattern is any filename specification that is valid within an {\bf
1393 Include} resource definition. If none is specified, {\bf /} (the root
1394 directory) is assumed. For example:
1402 Would print the following:
1408 Lnk: /bin/bash2 -> bash
1409 Lnk: /bin/sh -> bash
1417 Reg: /bin/aumix-minimal
1419 Lnka: /bin/gawk-3.1.0 -> /bin/gawk
1429 Even though {\bf testfind} uses the same search engine as {\bf Bacula}, each
1430 directory to be listed, must be entered as a separate command line entry or
1431 entered one line at a time to standard input if the {\bf -} option was
1434 Specifying a debug level of one (i.e. {\bf -d1}) on the command line will
1435 cause {\bf testfind} to print the raw filenames without showing the Bacula
1436 internal file type, or the link (if any). Debug levels of 10 or greater cause
1437 the filename and the path to be separated using the same algorithm that is
1438 used when putting filenames into the Catalog database.