Troubleshooting

Debugging

Trace File Name

The debug postfix option is used for creating the trace files in the following directory:

• On UNIX systems: /tmp

• On Windows systems: <Data_Protector_home>\tmp

• On Novell NetWare systems: SYS:\USR\OMNI\TMP The files are named OB2DBG_<did>__<Program>_<Host>_<pid>_<XYZ> where:

<did> (debugging ID) is the process ID of the first process that accepts the debugging parameters. This ID is used as an ID for the debugging session. All further processes will use this ID.

<Program> is the code name of the Data Protector program writing the trace.

<Host> is the name where the trace file is created. <pid> is the process ID.

<XYZ> is the postfix as specified in the -debugparameter.

 

Once the backup or restore session ID(<sid>) is determined, it will be

 

added to the filename:

 

OB2DBG_<did>_<sid>_<Program>_<Host>_<pid>_<XYZ>

 

Processes that add the <sid> are BMA/RMA, xBDA/xRDA, and other

 

processes started by the session, but not by the BSM/RSM itself.

 

 

NOTE

The session ID is intended to help you identify sets of debug files. Other

 

debug files may belong to the same session and you may have to provide

 

them as well.

 

 

trace.log

A trace.log file is generated on the Cell Manager, containing

 

information where (on which hosts) debug files are generated and which

 

debugging prefixes are being used. Note that this file does not contain a

 

complete list of all generated files.

556

Chapter 12

Page 586
Image 586
HP B6960-90078 manual Trace File Name, 556