Ripro Server/ Ripro Archiver/ Ripro Backup

BOM – Support Document

Lev Weissman
May 30, 1999

This document is for Integrity distributors only – not for clients!

1. The BOM.INI File

   The BOM.INI file contains the following parameters:

   SERVER_NAME	Name of backup server.
   BOM_HOME	Directory in which BOM was installed.
   BOM_EXE_DIR	Directory in which all BOM executable files sit. Default: [BOM_HOME]\exe.
   BOM_TEMP_DIR	Directory in which all BOM temporary files sit. Default: [BOM_ HOME]\temp.
   BOM_OUTPUT_DIR	Directory in which all BOM output files sit. Default: [BOM_ HOME]\output.
   BOM_FILES_DIR	Configuration files directory. Default: [BOM_HOME]\files.
   BOM_LOG_DIR	BOM internal logs directory. Default: [BOM_HOME]\log.
   BOM_MAIN_LOG	BOM main internal log file name. Default: [BOM_HOME]\log\bom_main.log.
   BOM_DB_DIR	BOM database directory. Default: [BOM_HOME]\db.
   BOM_REFRESH_INTERVAL	Automatic refresh interval of Device information and Pending Messages in BOM main screen in seconds. Minimum interval is 10
   BOM_SOCKET	The TCP port through which BOM and BOM-Server communicate.
   LEGATO_BIN	The location of NetWorker’s bins directory.
   TRACE_LEVEL	For tracing purposes. Use only with instructions from tech support.
   TRACE_REFRESH_LEVEL	For tracing purposes. Use only with instructions from tech support.
   BOM_TRACE_FILE	BOM main trace file. Use only with instructions from tech support

2. Troubleshooting

   ERROR MESSAGES	Problem Suggested Solution
   When starting BOM you get a message: "BOM server is not up!!!Aborting."	Windows: Stop the BOM Server Service using the Service dialog box from the Control Panel. Start the server again. Unix: Stop BOM daemon with the following file: [BOM_HOME]\bin\rc.bom stop. Then to start the BOM daemon, use the following file: [BOM_HOME]\bin\rc.bom start.
   Number of Mail slots displayed is not correct or message "Unknown number of mail slots"appears.	Please see section 2.1
   BOM does not accurately reflect NetWorker configuration (e.g., number of pools do not correspond)	Run File/Update System Configuration from the BOM main menu.

   2.1  Unknown number of mail slots.

   This might occur if your jukebox model is not recognized by BOM. You can find your jukebox model and add it to BOM jukebox models list by :

   1. Enter nsradmin:

      nsradmin -s <backup server>
      nsradmin > print type:nsr jukebox

   2. Take the value in the line "model:<jukebox model>" (i.e model: ATL).
   3. Edit the file <BOM_HOME>/files/jb_spec.ini (in the same place as jukebox.cfg).
      Enter a line for your jukebox model identifying the jukebox model and the number of mail slots
      (i.e. ATL;4)

      Note: if a line like this already exists but has the wrong number of mail slots, update this line.

   4. Exit BOM and start it again.
   5. This will build a new <BOM_HOME>/files/jukebox.cfg with the correct values.

3. The trace file

   The trace file, defined in BOM.INI (under BOM_TRACE_FILE), contains information about BOM modules that are being executed.

   Trace levels (defined in by the parameter TRACE_LEVEL=n):

   1	Routines entry/exit points, so one can track if a routine did not complete, or a routine was not called.
   8	Legato commands being executed, as well as messages from lower trace levels.
   16	Parameters to routines, as well as messages from lower trace levels.

   To enable the trace, you need to define BOM_TRACE_FILE and TRACE_LEVEL in the bom.ini

   The default TRACE_LEVEL is 0, which means no tracing.

   The parameter TRACE_REFRESH_LEVEL affects tracing from the program that handles the screen refresh. Usually, it should not be changed. Change it only after instructions from Integrity Systems.

   Note: Using trace can produce huge files, so make sure you change the trace level back to 0 after completing the diagnostics.

4. The temp directory

   The BOM_TEMP_DIR directory, defined in BOM_INI, contains all the temporary files used by BOM.

   In general, legato commands executed from BOM write their output to files in this directory, and this output (in case of an error) is displayed by BOM.

   Files names:
   unload.out    - output file of the withdraw command.
   load.tape.out - output file of the deposit command.

5. The log file

   The log file, specified in BOM.INI (BOM_MAIN_LOG), usually contains internal errors that are not reported to the screen.

   In case an operation failed, please check this file for error messages.

6. The clone process

   The clone process is done in the background, so if an error occurs it is not displayed on the screen.  If the clone process did not succeed, you can check the following files for more information:

   run_clone.tmp - contains the save sets list to be cloned (including ssid, name, flags).
   ssid_list.tmp - contains the save sets list to be cloned (only ssid – this is the list that will be pass to the clone process).
   run_clone.err - contains the error messages of the clone process.
   clone_label.err - contains the error messages of labeling the destination clone tape (done before the cloning is started).
   clone_label.out - contains the output messages of labeling the destination clone tape (done before the cloning is started).

   Notes:

1. Those files reflect the LAST clone process started.
2. More errors can be found in the BOM log file.