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 xxx} 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 Win32 non-portable streams (typically default).
335 \item It cannot restore encrypted files.
336 \item The command line length is relatively limited,
337 which means that you cannot enter a huge number of volumes. If you need to
338 enter more volumes than the command line supports, please use a bootstrap
348 Usage: bextract [-d debug_level] <device-name> <directory-to-store-files>
349 -b <file> specify a bootstrap file
350 -dnn set debug level to nn
351 -e <file> exclude list
352 -i <file> include list
353 -p proceed inspite of I/O errors
354 -V specify Volume names (separated by |)
355 -? print this message
359 where {\bf device-name} is the Archive Device (raw device name or full
360 filename) of the device to be read, and {\bf directory-to-store-files} is a
361 path prefix to prepend to all the files restored.
363 NOTE: On Windows systems, if you specify a prefix of say d:/tmp, any file that
364 would have been restored to {\bf c:/My Documents} will be restored to {\bf
365 d:/tmp/My Documents}. That is, the original drive specification will be
366 stripped. If no prefix is specified, the file will be restored to the original
369 \subsection{Extracting with Include or Exclude Lists}
370 \index[general]{Lists!Extracting with Include or Exclude}
371 \index[general]{Extracting with Include or Exclude Lists}
373 Using the {\bf -e} option, you can specify a file containing a list of files
374 to be excluded. Wildcards can be used in the exclusion list. This option will
375 normally be used in conjunction with the {\bf -i} option (see below). Both the
376 {\bf -e} and the {\bf -i} options may be specified at the same time as the
377 {\bf -b} option. The bootstrap filters will be applied first, then the include
378 list, then the exclude list.
380 Likewise, and probably more importantly, with the {\bf -i} option, you can
381 specify a file that contains a list (one file per line) of files and
382 directories to include to be restored. The list must contain the full filename
383 with the path. If you specify a path name only, all files and subdirectories
384 of that path will be restored. If you specify a line containing only the
385 filename (e.g. {\bf my-file.txt}) it probably will not be extracted because
386 you have not specified the full path.
388 For example, if the file {\bf include-list} contains:
401 ./bextract -i include-list -V Volume /dev/nst0 /tmp
405 will restore from the Bacula archive {\bf /dev/nst0} all files and directories
406 in the backup from {\bf /home/kern/bacula} and from {\bf /usr/local/bin}. The
407 restored files will be placed in a file of the original name under the
408 directory {\bf /tmp} (i.e. /tmp/home/kern/bacula/... and
409 /tmp/usr/local/bin/...).
411 \subsection{Extracting With a Bootstrap File}
412 \index[general]{File!Extracting With a Bootstrap}
413 \index[general]{Extracting With a Bootstrap File}
415 The {\bf -b} option is used to specify a {\bf bootstrap} file containing the
416 information needed to restore precisely the files you want. Specifying a {\bf
417 bootstrap} file is optional but recommended because it gives you the most
418 control over which files will be restored. For more details on the {\bf
419 bootstrap} file, please see
420 \ilink{Restoring Files with the Bootstrap File}{BootstrapChapter}
421 chapter of this document. Note, you may also use a bootstrap file produced by
422 the {\bf restore} command. For example:
426 ./bextract -b bootstrap-file /dev/nst0 /tmp
430 The bootstrap file allows detailed specification of what files you want
431 restored (extracted). You may specify a bootstrap file and include and/or
432 exclude files at the same time. The bootstrap conditions will first be
433 applied, and then each file record seen will be compared to the include and
436 \subsection{Extracting From Multiple Volumes}
437 \index[general]{Volumes!Extracting From Multiple}
438 \index[general]{Extracting From Multiple Volumes}
440 If you wish to extract files that span several Volumes, you can specify the
441 Volume names in the bootstrap file or you may specify the Volume names on the
442 command line by separating them with a vertical bar. See the section above
443 under the {\bf bls} program entitled {\bf Listing Multiple Volumes} for more
444 information. The same techniques apply equally well to the {\bf bextract}
445 program or read the \ilink{Bootstrap}{BootstrapChapter}
446 chapter of this document.
450 \index[general]{bscan}
451 \index[general]{program!bscan}
453 If you find yourself using this program, you have probably done something
454 wrong. For example, the best way to recover a lost or damaged Bacula
455 database is to reload the database by using the bootstrap file that
456 was written when you saved it (default bacula-dir.conf file).
458 The {\bf bscan} program can be used to re-create a database (catalog)
459 records from the backup information written to one or more Volumes.
461 needed only if one or more Volumes have been pruned or purged from your
462 catalog so that the records on the Volume are no longer in the catalog, or
463 for Volumes that you have archived.
465 With some care, it can also be used to synchronize your existing catalog with
466 a Volume. Although we have never seen a case of bscan damaging a
467 catalog, since bscan modifies your catalog, we recommend that
468 you do a simple ASCII backup of your database before running {\bf bscan} just
469 to be sure. See \ilink{Compacting Your Database}{CompactingMySQL} for
470 the details of making a copy of your database.
472 {\bf bscan} can also be useful in a disaster recovery situation, after the
473 loss of a hard disk, if you do not have a valid {\bf bootstrap} file for
474 reloading your system, or if a Volume has been recycled but not overwritten,
475 you can use {\bf bscan} to re-create your database, which can then be used to
476 {\bf restore} your system or a file to its previous state.
483 Usage: bscan [options] <bacula-archive>
484 -b bootstrap specify a bootstrap file
485 -c <file> specify configuration file
486 -d <nn> set debug level to nn
487 -m update media info in database
488 -n <name> specify the database name (default bacula)
489 -u <user> specify database user name (default bacula)
490 -P <password> specify database password (default none)
491 -h <host> specify database host (default NULL)
492 -p proceed inspite of I/O errors
494 -s synchronize or store in database
496 -V <Volumes> specify Volume names (separated by |)
497 -w <dir> specify working directory (default from conf file)
498 -? print this message
502 If you are using MySQL or PostgreSQL, there is no need to supply a working
503 directory since in that case, bscan knows where the databases are. However, if
504 you have provided security on your database, you may need to supply either the
505 database name ({\bf -b} option), the user name ({\bf -u} option), and/or the
506 password ({\bf -p}) options.
508 NOTE: before {\bf bscan} can work, it needs at least a bare bones valid
509 database. If your database exists but some records are missing because
510 they were pruned, then you are all set. If your database was lost or
511 destroyed, then you must first ensure that you have the SQL program running
512 (MySQL or PostgreSQL), then you must create the Bacula database (normally
513 named bacula), and you must create the Bacula tables using the scripts in
514 the {\bf cats} directory. This is explained in the
515 \ilink{Installation}{CreateDatabase} chapter of the manual. Finally, before
516 scanning into an empty database, you must start and stop the Director with
517 the appropriate bacula-dir.conf file so that it can create the Client and
518 Storage records which are not stored on the Volumes. Without these
519 records, scanning is unable to connect the Job records to the proper
522 Forgetting for the moment the extra complications of a full rebuild of
523 your catalog, let's suppose that you did a backup to Volumes "Vol001"
524 and "Vol002", then sometime later all records of one or both those
525 Volumes were pruned or purged from the
526 database. By using {\bf bscan} you can recreate the catalog entries for
527 those Volumes and then use the {\bf restore} command in the Console to restore
528 whatever you want. A command something like:
532 bscan -c bacula-sd.conf -v -V Vol001\|Vol002 /dev/nst0
536 will give you an idea of what is going to happen without changing
537 your catalog. Of course, you may need to change the path to the Storage
538 daemon's conf file, the Volume name, and your tape (or disk) device name. This
539 command must read the entire tape, so if it has a lot of data, it may take a
540 long time, and thus you might want to immediately use the command listed
541 below. Note, if you are writing to a disk file, replace the device name with
542 the path to the directory that contains the Volumes. This must correspond to
543 the Archive Device in the conf file.
545 Then to actually write or store the records in the catalog, add the {\bf -s}
550 bscan -s -m -c bacula-sd.conf -v -V Vol001\|Vol002 /dev/nst0
554 When writing to the database, if bscan finds existing records, it will
555 generally either update them if something is wrong or leave them alone. Thus
556 if the Volumes you are scanning are all or partially in the catalog already, no
557 harm will be done to that existing data. Any missing data will simply be
560 If you have multiple tapes, you should scan them with:
564 bscan -s -m -c bacula-sd.conf -v -V Vol001\|Vol002\|Vol003 /dev/nst0
568 Since there is a limit on the command line length (511 bytes) accepted
569 by {\bf bscan}, if you have too many Volumes, you will need to manually
570 create a bootstrap file. See the \ilink{Bootstrap}{BootstrapChapter}
571 chapter of this manual for more details, in particular the section
572 entitled \ilink{Bootstrap for bscan}{bscanBootstrap}.
574 You should, always try to specify the tapes in the order they are written.
575 However, bscan can handle scanning tapes that are not sequential. Any
576 incomplete records at the end of the tape will simply be ignored in that
577 case. If you are simply repairing an existing catalog, this may be OK, but
578 if you are creating a new catalog from scratch, it will leave your database
579 in an incorrect state. If you do not specify all necessary Volumes on a
580 single bscan command, bscan will not be able to correctly restore the
581 records that span two volumes. In other words, it is much better to
582 specify two or three volumes on a single bscan command rather than run
583 bscan two or three times, each with a single volume.
586 Note, the restoration process using bscan is not identical to the original
587 creation of the catalog data. This is because certain data such as Client
588 records and other non-essential data such
589 as volume reads, volume mounts, etc is not stored on the Volume, and thus is
590 not restored by bscan. The results of bscanning are, however, perfectly valid,
591 and will permit restoration of any or all the files in the catalog using the
592 normal Bacula console commands. If you are starting with an empty catalog
593 and expecting bscan to reconstruct it, you may be a bit disappointed, but
594 at a minimum, you must ensure that your bacula-dir.conf file is the same
595 as what it previously was -- that is, it must contain all the appropriate
596 Client resources so that they will be recreated in your new database {\bf
597 before} running bscan. Normally when the Director starts, it will recreate
598 any missing Client records in the catalog. Another problem you will have
599 is that even if the Volumes (Media records) are recreated in the database,
600 they will not have their autochanger status and slots properly set. As a
601 result, you will need to repair that by using the {\bf update slots}
602 command. There may be other considerations as well. Rather than
603 bscanning, you should always attempt to recover you previous catalog
607 \subsection{Using bscan to Compare a Volume to an existing Catalog}
608 \index[general]{Catalog!Using bscan to Compare a Volume to an existing}
609 \index[general]{Using bscan to Compare a Volume to an existing Catalog}
611 If you wish to compare the contents of a Volume to an existing catalog without
612 changing the catalog, you can safely do so if and only if you do {\bf not}
613 specify either the {\bf -m} or the {\bf -s} options. However, at this time
614 (Bacula version 1.26), the comparison routines are not as good or as thorough
615 as they should be, so we don't particularly recommend this mode other than for
618 \subsection{Using bscan to Recreate a Catalog from a Volume}
619 \index[general]{Volume!Using bscan to Recreate a Catalog from a Volume}
620 \index[general]{Using bscan to Recreate a Catalog from a Volume}
622 This is the mode for which {\bf bscan} is most useful. You can either {\bf
623 bscan} into a freshly created catalog, or directly into your existing catalog
624 (after having made an ASCII copy as described above). Normally, you should
625 start with a freshly created catalog that contains no data.
627 Starting with a single Volume named {\bf TestVolume1}, you run a command such
632 ./bscan -V TestVolume1 -v -s -m -c bacula-sd.conf /dev/nst0
636 If there is more than one volume, simply append it to the first one separating
637 it with a vertical bar. You may need to precede the vertical bar with a
638 forward slash escape the shell -- e.g. {\bf
639 TestVolume1\textbackslash{}|TestVolume2}. The {\bf -v} option was added for
640 verbose output (this can be omitted if desired). The {\bf -s} option that
641 tells {\bf bscan} to store information in the database. The physical device
642 name {\bf /dev/nst0} is specified after all the options.
644 {\bf} For example, after having done a full backup of a directory, then two
645 incrementals, I reinitialized the SQLite database as described above, and
646 using the bootstrap.bsr file noted above, I entered the following command:
650 ./bscan -b bootstrap.bsr -v -s -c bacula-sd.conf /dev/nst0
654 which produced the following output:
658 bscan: bscan.c:182 Using Database: bacula, User: bacula
659 bscan: bscan.c:673 Created Pool record for Pool: Default
660 bscan: bscan.c:271 Pool type "Backup" is OK.
661 bscan: bscan.c:632 Created Media record for Volume: TestVolume1
662 bscan: bscan.c:298 Media type "DDS-4" is OK.
663 bscan: bscan.c:307 VOL_LABEL: OK for Volume: TestVolume1
664 bscan: bscan.c:693 Created Client record for Client: Rufus
665 bscan: bscan.c:769 Created new JobId=1 record for original JobId=2
666 bscan: bscan.c:717 Created FileSet record "Kerns Files"
667 bscan: bscan.c:819 Updated Job termination record for new JobId=1
668 bscan: bscan.c:905 Created JobMedia record JobId 1, MediaId 1
669 bscan: Got EOF on device /dev/nst0
670 bscan: bscan.c:693 Created Client record for Client: Rufus
671 bscan: bscan.c:769 Created new JobId=2 record for original JobId=3
672 bscan: bscan.c:708 Fileset "Kerns Files" already exists.
673 bscan: bscan.c:819 Updated Job termination record for new JobId=2
674 bscan: bscan.c:905 Created JobMedia record JobId 2, MediaId 1
675 bscan: Got EOF on device /dev/nst0
676 bscan: bscan.c:693 Created Client record for Client: Rufus
677 bscan: bscan.c:769 Created new JobId=3 record for original JobId=4
678 bscan: bscan.c:708 Fileset "Kerns Files" already exists.
679 bscan: bscan.c:819 Updated Job termination record for new JobId=3
680 bscan: bscan.c:905 Created JobMedia record JobId 3, MediaId 1
681 bscan: Got EOF on device /dev/nst0
682 bscan: bscan.c:652 Updated Media record at end of Volume: TestVolume1
683 bscan: bscan.c:428 End of Volume. VolFiles=3 VolBlocks=57 VolBytes=10,027,437
687 The key points to note are that {\bf bscan} prints a line when each major
688 record is created. Due to the volume of output, it does not print a line for
689 each file record unless you supply the {\bf -v} option twice or more on the
692 In the case of a Job record, the new JobId will not normally be the same as
693 the original Jobid. For example, for the first JobId above, the new JobId is
694 1, but the original JobId is 2. This is nothing to be concerned about as it is
695 the normal nature of databases. {\bf bscan} will keep everything straight.
697 Although {\bf bscan} claims that it created a Client record for Client: Rufus
698 three times, it was actually only created the first time. This is normal.
700 You will also notice that it read an end of file after each Job (Got EOF on
701 device ...). Finally the last line gives the total statistics for the bscan.
703 If you had added a second {\bf -v} option to the command line, Bacula would
704 have been even more verbose, dumping virtually all the details of each Job
705 record it encountered.
707 Now if you start Bacula and enter a {\bf list jobs} command to the console
708 program, you will get:
712 +-------+----------+------------------+------+-----+----------+----------+---------+
713 | JobId | Name | StartTime | Type | Lvl | JobFiles | JobBytes | JobStat |
714 +-------+----------+------------------+------+-----+----------+----------+---------+
715 | 1 | kernsave | 2002-10-07 14:59 | B | F | 84 | 4180207 | T |
716 | 2 | kernsave | 2002-10-07 15:00 | B | I | 15 | 2170314 | T |
717 | 3 | kernsave | 2002-10-07 15:01 | B | I | 33 | 3662184 | T |
718 +-------+----------+------------------+------+-----+----------+----------+---------+
722 which corresponds virtually identically with what the database contained
723 before it was re-initialized and restored with bscan. All the Jobs and Files
724 found on the tape are restored including most of the Media record. The Volume
725 (Media) records restored will be marked as {\bf Full} so that they cannot be
726 rewritten without operator intervention.
728 It should be noted that {\bf bscan} cannot restore a database to the exact
729 condition it was in previously because a lot of the less important information
730 contained in the database is not saved to the tape. Nevertheless, the
731 reconstruction is sufficiently complete, that you can run {\bf restore}
732 against it and get valid results.
734 An interesting aspect of restoring a catalog backup using {\bf bscan} is
735 that the backup was made while Bacula was running and writing to a tape. At
736 the point the backup of the catalog is made, the tape Bacula is writing to
737 will have say 10 files on it, but after the catalog backup is made, there
738 will be 11 files on the tape Bacula is writing. This there is a difference
739 between what is contained in the backed up catalog and what is actually on
740 the tape. If after restoring a catalog, you attempt to write on the same
741 tape that was used to backup the catalog, Bacula will detect the difference
742 in the number of files registered in the catalog compared to what is on the
743 tape, and will mark the tape in error.
745 There are two solutions to this problem. The first is possibly the simplest
746 and is to mark the volume as Used before doing any backups. The second is
747 to manually correct the number of files listed in the Media record of the
748 catalog. This procedure is documented elsewhere in the manual and involves
749 using the {\bf update volume} command in {\bf bconsole}.
751 \subsection{Using bscan to Correct the Volume File Count}
752 \index[general]{Using bscan to Correct the Volume File Count}
753 \index[general]{Count!Using bscan to Correct the Volume File Count}
755 If the Storage daemon crashes during a backup Job, the catalog will not be
756 properly updated for the Volume being used at the time of the crash. This
757 means that the Storage daemon will have written say 20 files on the tape, but
758 the catalog record for the Volume indicates only 19 files.
760 Bacula refuses to write on a tape that contains a different number of files
761 from what is in the catalog. To correct this situation, you may run a {\bf
762 bscan} with the {\bf -m} option (but {\bf without} the {\bf -s} option) to
763 update only the final Media record for the Volumes read.
765 \subsection{After bscan}
766 \index[general]{After bscan}
767 \index[general]{Bscan!After}
769 If you use {\bf bscan} to enter the contents of the Volume into an existing
770 catalog, you should be aware that the records you entered may be immediately
771 pruned during the next job, particularly if the Volume is very old or had been
772 previously purged. To avoid this, after running {\bf bscan}, you can manually
773 set the volume status (VolStatus) to {\bf Read-Only} by using the {\bf update}
774 command in the catalog. This will allow you to restore from the volume without
775 having it immediately purged. When you have restored and backed up the data,
776 you can reset the VolStatus to {\bf Used} and the Volume will be purged from
781 \index[general]{Bcopy}
782 \index[general]{program!bcopy}
784 The {\bf bcopy} program can be used to copy one {\bf Bacula} archive file to
785 another. For example, you may copy a tape to a file, a file to a tape, a file
786 to a file, or a tape to a tape. For tape to tape, you will need two tape
787 drives. (a later version is planned that will buffer it to disk). In the
788 process of making the copy, no record of the information written to the new
789 Volume is stored in the catalog. This means that the new Volume, though it
790 contains valid backup data, cannot be accessed directly from existing catalog
791 entries. If you wish to be able to use the Volume with the Console restore
792 command, for example, you must first bscan the new Volume into the catalog.
794 \subsection{bcopy Command Options}
795 \index[general]{Options!bcopy Command}
796 \index[general]{Bcopy Command Options}
800 Usage: bcopy [-d debug_level] <input-archive> <output-archive>
801 -b bootstrap specify a bootstrap file
802 -c <file> specify configuration file
803 -dnn set debug level to nn
804 -i specify input Volume names (separated by |)
805 -o specify output Volume names (separated by |)
806 -p proceed inspite of I/O errors
808 -w dir specify working directory (default /tmp)
809 -? print this message
813 By using a {\bf bootstrap} file, you can copy parts of a Bacula archive file
816 One of the objectives of this program is to be able to recover as much data as
817 possible from a damaged tape. However, the current version does not yet have
820 As this is a new program, any feedback on its use would be appreciated. In
821 addition, I only have a single tape drive, so I have never been able to test
822 this program with two tape drives.
826 \index[general]{Btape}
827 \index[general]{program!btape}
829 This program permits a number of elementary tape operations via a tty command
830 interface. It works only with tapes and not with other kinds of Bacula
831 storage media (DVD, File, ...). The {\bf test} command, described below,
832 can be very useful for testing older tape drive compatibility problems.
833 Aside from initial testing of tape drive compatibility with {\bf Bacula},
834 {\bf btape} will be mostly used by developers writing new tape drivers.
836 {\bf btape} can be dangerous to use with existing {\bf Bacula} tapes because
837 it will relabel a tape or write on the tape if so requested regardless that
838 the tape may contain valuable data, so please be careful and use it only on
841 To work properly, {\bf btape} needs to read the Storage daemon's configuration
842 file. As a default, it will look for {\bf bacula-sd.conf} in the current
843 directory. If your configuration file is elsewhere, please use the {\bf -c}
844 option to specify where.
846 The physical device name must be specified on the command line, and this
847 same device name must be present in the Storage daemon's configuration file
852 Usage: btape <options> <device_name>
853 -b <file> specify bootstrap file
854 -c <file> set configuration file to file
855 -d <nn> set debug level to nn
856 -p proceed inspite of I/O errors
859 -? print this message.
863 \subsection{Using btape to Verify your Tape Drive}
864 \index[general]{Using btape to Verify your Tape Drive}
865 \index[general]{Drive!Using btape to Verify your Tape}
867 An important reason for this program is to ensure that a Storage daemon
868 configuration file is defined so that Bacula will correctly read and write
871 It is highly recommended that you run the {\bf test} command before running
872 your first Bacula job to ensure that the parameters you have defined for your
873 storage device (tape drive) will permit {\bf Bacula} to function properly. You
874 only need to mount a blank tape, enter the command, and the output should be
875 reasonably self explanatory. Please see the
876 \ilink{Tape Testing}{TapeTestingChapter} Chapter of this manual for
879 \subsection{btape Commands}
880 \index[general]{Btape Commands}
881 \index[general]{Commands!btape}
883 The full list of commands are:
889 autochanger test autochanger
892 cap list device capabilities
893 clear clear tape errors
894 eod go to end of Bacula data for append
895 eom go to the physical end of medium
896 fill fill tape, write onto second volume
897 unfill read filled tape
898 fsf forward space a file
899 fsr forward space a record
900 help print this command
901 label write a Bacula label to the tape
904 rawfill use write() to fill tape
905 readlabel read and print the Bacula tape label
906 rectest test record handling functions
907 rewind rewind the tape
908 scan read() tape block by block to EOT and report
909 scanblocks Bacula read block by block to EOT and report
910 status print tape status
911 test General test Bacula tape functions
912 weof write an EOF on the tape
913 wr write a single Bacula block
914 rr read a single record
915 qfill quick fill command
919 The most useful commands are:
922 \item test -- test writing records and EOF marks and reading them back.
923 \item fill -- completely fill a volume with records, then write a few records
924 on a second volume, and finally, both volumes will be read back.
925 This command writes blocks containing random data, so your drive will
926 not be able to compress the data, and thus it is a good test of
927 the real physical capacity of your tapes.
928 \item readlabel -- read and dump the label on a Bacula tape.
929 \item cap -- list the device capabilities as defined in the configuration
930 file and as perceived by the Storage daemon.
933 The {\bf readlabel} command can be used to display the details of a Bacula
934 tape label. This can be useful if the physical tape label was lost or damaged.
937 In the event that you want to relabel a {\bf Bacula}, you can simply use the
938 {\bf label} command which will write over any existing label. However, please
939 note for labeling tapes, we recommend that you use the {\bf label} command in
940 the {\bf Console} program since it will never overwrite a valid Bacula tape.
942 \section{Other Programs}
943 \index[general]{Programs!Other}
944 \index[general]{Other Programs}
946 The following programs are general utility programs and in general do not need
947 a configuration file nor a device name.
951 \index[general]{Bsmtp}
952 \index[general]{program!bsmtp}
954 {\bf bsmtp} is a simple mail transport program that permits more flexibility
955 than the standard mail programs typically found on Unix systems. It can even
956 be used on Windows machines.
962 Usage: bsmtp [-f from] [-h mailhost] [-s subject] [-c copy] [recipient ...]
964 -dnn set debug level to nn
965 -f set the From: field
966 -h use mailhost:port as the bsmtp server
967 -l limit the lines accepted to nn
968 -s set the Subject: field
969 -? print this message.
973 If the {\bf -f} option is not specified, {\bf bsmtp} will use your userid. If
974 the option {\bf -h} is not specified {\bf bsmtp} will use the value in the environment
975 variable {\bf bsmtpSERVER} or if there is none {\bf localhost}. By default
978 If a line count limit is set with the {\bf -l} option, {\bf bsmtp} will
979 not send an email with a body text exceeding that number of lines. This
980 is especially useful for large restore job reports where the list of
981 files restored might produce very long mails your mail-server would
982 refuse or crash. However, be aware that you will probably suppress the
983 job report and any error messages unless you check the log file written
984 by the Director (see the messages resource in this manual for details).
987 {\bf recipients} is a space separated list of email recipients.
989 The body of the email message is read from standard input.
991 An example of the use of {\bf bsmtp} would be to put the following statement
992 in the {\bf Messages} resource of your {\bf bacula-dir.conf} file. Note, these
993 commands should appear on a single line each.
997 mailcommand = "/home/bacula/bin/bsmtp -h mail.domain.com -f \"\(Bacula\) %r\"
998 -s \"Bacula: %t %e of %c %l\" %r"
999 operatorcommand = "/home/bacula/bin/bsmtp -h mail.domain.com -f \"\(Bacula\) %r\"
1000 -s \"Bacula: Intervention needed for %j\" %r"
1004 Where you replace {\bf /home/bacula/bin} with the path to your {\bf Bacula}
1005 binary directory, and you replace {\bf mail.domain.com} with the fully
1006 qualified name of your bsmtp (email) server, which normally listens on port
1007 25. For more details on the substitution characters (e.g. \%r) used in the
1008 above line, please see the documentation of the
1009 \ilink{ MailCommand in the Messages Resource}{mailcommand}
1010 chapter of this manual.
1012 It is HIGHLY recommended that you test one or two cases by hand to make sure
1013 that the {\bf mailhost} that you specified is correct and that it will accept
1014 your email requests. Since {\bf bsmtp} always uses a TCP connection rather
1015 than writing in the spool file, you may find that your {\bf from} address is
1016 being rejected because it does not contain a valid domain, or because your
1017 message is caught in your spam filtering rules. Generally, you should specify
1018 a fully qualified domain name in the {\bf from} field, and depending on
1019 whether your bsmtp gateway is Exim or Sendmail, you may need to modify the
1020 syntax of the from part of the message. Please test.
1022 When running {\bf bsmtp} by hand, you will need to terminate the message by
1023 entering a ctl-d in column 1 of the last line.
1024 % TODO: is "column" the correct terminology for this?
1026 If you are getting incorrect dates (e.g. 1970) and you are
1027 running with a non-English language setting, you might try adding
1028 a LANG=''en\_US'' immediately before the bsmtp call.
1032 \index[general]{Dbcheck}
1033 \index[general]{program!dbcheck}
1034 {\bf dbcheck} is a simple program that will search for logical
1035 inconsistencies in the Bacula tables in your database, and optionally fix them.
1036 It is a database maintenance routine, in the sense that it can
1037 detect and remove unused rows, but it is not a database repair
1038 routine. To repair a database, see the tools furnished by the
1039 database vendor. Normally dbcheck should never need to be run,
1040 but if Bacula has crashed or you have a lot of Clients, Pools, or
1041 Jobs that you have removed, it could be useful.
1043 The {\bf dbcheck} program can be found in
1044 the {\bf \lt{}bacula-source\gt{}/src/tools} directory of the source
1045 distribution. Though it is built with the make process, it is not normally
1052 Usage: dbcheck [-c config] [-C catalog name] [-d debug_level]
1053 <working-directory> <bacula-database> <user> <password> [<dbhost>]
1055 -C catalog name in the director conf file
1056 -c director conf filename
1057 -dnn set debug level to nn
1058 -f fix inconsistencies
1060 -? print this message
1064 If the {\bf -c} option is given with the Director's conf file, there is no
1065 need to enter any of the command line arguments, in particular the working
1066 directory as dbcheck will read them from the file.
1068 If the {\bf -f} option is specified, {\bf dbcheck} will repair ({\bf fix}) the
1069 inconsistencies it finds. Otherwise, it will report only.
1071 If the {\bf -b} option is specified, {\bf dbcheck} will run in batch mode, and
1072 it will proceed to examine and fix (if -f is set) all programmed inconsistency
1073 checks. If the {\bf -b} option is not specified, {\bf dbcheck} will enter
1074 interactive mode and prompt with the following:
1078 Hello, this is the database check/correct program.
1079 Please select the function you want to perform.
1080 1) Toggle modify database flag
1081 2) Toggle verbose flag
1082 3) Repair bad Filename records
1083 4) Repair bad Path records
1084 5) Eliminate duplicate Filename records
1085 6) Eliminate duplicate Path records
1086 7) Eliminate orphaned Jobmedia records
1087 8) Eliminate orphaned File records
1088 9) Eliminate orphaned Path records
1089 10) Eliminate orphaned Filename records
1090 11) Eliminate orphaned FileSet records
1091 12) Eliminate orphaned Client records
1092 13) Eliminate orphaned Job records
1093 14) Eliminate all Admin records
1094 15) Eliminate all Restore records
1097 Select function number:
1101 By entering 1 or 2, you can toggle the modify database flag (-f option) and
1102 the verbose flag (-v). It can be helpful and reassuring to turn off the modify
1103 database flag, then select one or more of the consistency checks (items 3
1104 through 9) to see what will be done, then toggle the modify flag on and re-run
1107 The inconsistencies examined are the following:
1110 \item Duplicate filename records. This can happen if you accidentally run two
1111 copies of Bacula at the same time, and they are both adding filenames
1112 simultaneously. It is a rare occurrence, but will create an inconsistent
1113 database. If this is the case, you will receive error messages during Jobs
1114 warning of duplicate database records. If you are not getting these error
1115 messages, there is no reason to run this check.
1116 \item Repair bad Filename records. This checks and corrects filenames that
1117 have a trailing slash. They should not.
1118 \item Repair bad Path records. This checks and corrects path names that do
1119 not have a trailing slash. They should.
1120 \item Duplicate path records. This can happen if you accidentally run two
1121 copies of Bacula at the same time, and they are both adding filenames
1122 simultaneously. It is a rare occurrence, but will create an inconsistent
1123 database. See the item above for why this occurs and how you know it is
1125 \item Orphaned JobMedia records. This happens when a Job record is deleted
1126 (perhaps by a user issued SQL statement), but the corresponding JobMedia
1127 record (one for each Volume used in the Job) was not deleted. Normally, this
1128 should not happen, and even if it does, these records generally do not take
1129 much space in your database. However, by running this check, you can
1130 eliminate any such orphans.
1131 \item Orphaned File records. This happens when a Job record is deleted
1132 (perhaps by a user issued SQL statement), but the corresponding File record
1133 (one for each Volume used in the Job) was not deleted. Note, searching for
1134 these records can be {\bf very} time consuming (i.e. it may take hours) for a
1135 large database. Normally this should not happen as Bacula takes care to
1136 prevent it. Just the same, this check can remove any orphaned File records.
1137 It is recommended that you run this once a year since orphaned File records
1138 can take a large amount of space in your database. You might
1139 want to ensure that you have indexes on JobId, FilenameId, and
1140 PathId for the File table in your catalog before running this
1142 \item Orphaned Path records. This condition happens any time a directory is
1143 deleted from your system and all associated Job records have been purged.
1144 During standard purging (or pruning) of Job records, Bacula does not check
1145 for orphaned Path records. As a consequence, over a period of time, old
1146 unused Path records will tend to accumulate and use space in your database.
1147 This check will eliminate them. It is recommended that you run this
1148 check at least once a year.
1149 \item Orphaned Filename records. This condition happens any time a file is
1150 deleted from your system and all associated Job records have been purged.
1151 This can happen quite frequently as there are quite a large number of files
1152 that are created and then deleted. In addition, if you do a system update or
1153 delete an entire directory, there can be a very large number of Filename
1154 records that remain in the catalog but are no longer used.
1156 During standard purging (or pruning) of Job records, Bacula does not check
1157 for orphaned Filename records. As a consequence, over a period of time, old
1158 unused Filename records will accumulate and use space in your database. This
1159 check will eliminate them. It is strongly recommended that you run this check
1160 at least once a year, and for large database (more than 200 Megabytes), it is
1161 probably better to run this once every 6 months.
1162 \item Orphaned Client records. These records can remain in the database long
1163 after you have removed a client.
1164 \item Orphaned Job records. If no client is defined for a job or you do not
1165 run a job for a long time, you can accumulate old job records. This option
1166 allow you to remove jobs that are not attached to any client (and thus
1168 \item All Admin records. This command will remove all Admin records,
1169 regardless of their age.
1170 \item All Restore records. This command will remove all Restore records,
1171 regardless of their age.
1174 By the way, I personally run dbcheck only where I have messed up
1175 my database due to a bug in developing Bacula code, so normally
1176 you should never need to run dbcheck in spite of the
1177 recommendations given above, which are given so that users don't
1178 waste their time running dbcheck too often.
1182 \index[general]{bregex}
1183 \index[general]{program!bregex}
1185 {\bf bregex} is a simple program that will allow you to test
1186 regular expressions against a file of data. This can be useful
1187 because the regex libraries on most systems differ, and in
1188 addition, regex expressions can be complicated.
1190 {\bf bregex} is found in the src/tools directory and it is
1191 normally installed with your system binaries. To run it, use:
1194 Usage: bregex [-d debug_level] -f <data-file>
1195 -f specify file of data to be matched
1196 -l suppress line numbers
1197 -n print lines that do not match
1198 -? print this message.
1201 The \lt{}data-file\gt{} is a filename that contains lines
1202 of data to be matched (or not) against one or more patterns.
1203 When the program is run, it will prompt you for a regular
1204 expression pattern, then apply it one line at a time against
1205 the data in the file. Each line that matches will be printed
1206 preceded by its line number. You will then be prompted again
1207 for another pattern.
1209 Enter an empty line for a pattern to terminate the program. You
1210 can print only lines that do not match by using the -n option,
1211 and you can suppress printing of line numbers with the -l option.
1213 This program can be useful for testing regex expressions to be
1214 applied against a list of filenames.
1218 \index[general]{bwild}
1219 \index[general]{program!bwild}
1221 {\bf bwild} is a simple program that will allow you to test
1222 wild-card expressions against a file of data.
1224 {\bf bwild} is found in the src/tools directory and it is
1225 normally installed with your system binaries. To run it, use:
1228 Usage: bwild [-d debug_level] -f <data-file>
1229 -f specify file of data to be matched
1230 -l suppress line numbers
1231 -n print lines that do not match
1232 -? print this message.
1235 The \lt{}data-file\gt{} is a filename that contains lines
1236 of data to be matched (or not) against one or more patterns.
1237 When the program is run, it will prompt you for a wild-card
1238 pattern, then apply it one line at a time against
1239 the data in the file. Each line that matches will be printed
1240 preceded by its line number. You will then be prompted again
1241 for another pattern.
1243 Enter an empty line for a pattern to terminate the program. You
1244 can print only lines that do not match by using the -n option,
1245 and you can suppress printing of line numbers with the -l option.
1247 This program can be useful for testing wild expressions to be
1248 applied against a list of filenames.
1252 \index[general]{Testfind}
1253 \index[general]{program!testfind}
1255 {\bf testfind} permits listing of files using the same search engine that is
1256 used for the {\bf Include} resource in Job resources. Note, much of the
1257 functionality of this program (listing of files to be included) is present in
1259 \ilink{estimate command}{estimate} in the Console program.
1261 The original use of testfind was to ensure that Bacula's file search engine
1262 was correct and to print some statistics on file name and path length.
1263 However, you may find it useful to see what bacula would do with a given {\bf
1264 Include} resource. The {\bf testfind} program can be found in the {\bf
1265 \lt{}bacula-source\gt{}/src/tools} directory of the source distribution.
1266 Though it is built with the make process, it is not normally "installed".
1272 Usage: testfind [-d debug_level] [-] [pattern1 ...]
1273 -a print extended attributes (Win32 debug)
1274 -dnn set debug level to nn
1275 - read pattern(s) from stdin
1276 -? print this message.
1277 Patterns are used for file inclusion -- normally directories.
1278 Debug level>= 1 prints each file found.
1279 Debug level>= 10 prints path/file for catalog.
1280 Errors are always printed.
1281 Files/paths truncated is a number with len> 255.
1282 Truncation is only in the catalog.
1286 Where a pattern is any filename specification that is valid within an {\bf
1287 Include} resource definition. If none is specified, {\bf /} (the root
1288 directory) is assumed. For example:
1296 Would print the following:
1302 Lnk: /bin/bash2 -> bash
1303 Lnk: /bin/sh -> bash
1311 Reg: /bin/aumix-minimal
1313 Lnka: /bin/gawk-3.1.0 -> /bin/gawk
1323 Even though {\bf testfind} uses the same search engine as {\bf Bacula}, each
1324 directory to be listed, must be entered as a separate command line entry or
1325 entered one line at a time to standard input if the {\bf -} option was
1328 Specifying a debug level of one (i.e. {\bf -d1}) on the command line will
1329 cause {\bf testfind} to print the raw filenames without showing the Bacula
1330 internal file type, or the link (if any). Debug levels of 10 or greater cause
1331 the filename and the path to be separated using the same algorithm that is
1332 used when putting filenames into the Catalog database.