In the previous section, we monitored the output produced by the -v option on the screen. The -v option also allows you to generate log files that contain this information. If you want to keep a record of how a particular tape archive was created and what files it contains, you can redirect the output of one of the verbose options to a log file. This command line sends the information produced by the -v option to the screen:
bru -cv file1 file2 file3
but this command line sends the log information to logfile and any error messages to a different file, errfile:
bru -cv file1 file2 file3 > logfile 2> errfile
If you want both error and log information to go to the same file, you can use a command line similar to this under the Bourne shell:
bru -c -v file1 file2 file3 > logfile 2>&1
If you want BRU to read the list of files to be archived from a file instead of from the command line, you can use something like:
bru -c -vvvv < filelist > logfile
where filelist is a file containing the list of files, one to a line.
The amount of information you collect in your log files can be varied by using different levels of verbosity.
All error messages and warnings are also recorded in the BRU execution log, /var/log/bruexeclog. The bruexeclog file is described in Appendix F, “BRU’s Execution Log.”
BRU offers an additional verbosity level that is designed to allow for easier parsing within a script or interface. By setting the verbosity level to 10 v’s, the output from BRU will appear as:
In this output, the interesting fields are the 3rd and 12th fields separated by the pipe (|) symbol. The 3rd field tells you what volume (if it is a multi-volume backup), while the 12th field tells you the logical block address within the volume. In the example above, the /etc/mtab file is located on the first volume at the 0x70 (HEX value) block.