Using HP Data Protector Debug Log Collector Tool "Best Practices"

– U is the Unicode flag. If it is specified, the debug files on Windows are written in the

Unicode format.

 XYZ is the debug postfix, for example DBG_01.txt.

 host is a list of clients where debugging is turned on. Use this option to run the debugging only on

the clients specified. Delimit multiple clients by spaces. Enclose the list in quotes, for example:

"computer1.company.com computer2.company.com".

Names and locations of debug files

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

Windows Vista, Windows Server 2008: Data_Protector_program_data\tmp

Other Windows systems: Data_Protector_home\tmp

UNIX systems: /tmp

Novell NetWare: 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 is the ID of the debugging session and is used by all further processes.

 Program is the code name of the Data Protector program writing the debug file.

 Host is the client where the debug file is created.

 pid is the process ID.

 XYZ is the postfix as specified in the -debug parameter.

Once the backup or restore session ID sid is determined, it is added to the file name:

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.

Using Debug Log Collector (omnidlc)

After Data Protector debug data has been generated, the omnidlc command can be used to collect

Data Protector debug, log, and getinfo files from the Data Protector cell (by default, from every client).

The command transfers the data from selected clients to the Cell Manager where it is then packed.

The command can also selectively collect the data, for example, only log files from a certain client, or

only debug files that were created during a particular Data Protector session.

A Data Protector debug session will create debug files in the Data Protector tmp directory on every

client which has been participating in the Data Protector session in debug mode.

This can be a bunch of data and when you run several sessions hard to identify which are the needed

files. All the collection can be automatically done by the omnidlc command.

Let’s have an example. When debugging a Data Protector backup session running on three hosts

where Disk Agent is used, one additional host used as Media Agent, you have in total 5 systems

involved in this example backup session.

 1 x Cell Manager (CM)

 1 x Media Agent (MA)

 3 x Disk Agent (DA)