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

15
Conclusions
With the omnidlc tool you are able to collect and pack debug information and additional
configuration data from several hosts with only one command.
You do not need to take care of the different installed operating systems on the different hosts in your
Data Protector environment, different OS have different log directories.
Using the omnidlc command will give you the single point for collecting the logs, debugs and
information of your whole environment.
The generated format can be used by every HP Data Protector support engineer, so there is no need
to format or convert the files.
You do not need to grep the data by your own, this will save your time.
Use one command – avoid problems – save time!
Limitations
The omnidlc is a command line only tool. There is no GUI available to collect the debug files.
omnidlc creates his own format, which cannot be unpacked by other packing utilities (WinZip,
WinRAR, 7-Zip, etc.). The unpacking needs to be done by omnidlc –unpack.
The omnidlc command cannot be used to collect the Data Protector installation execution traces.
On how to create and collect these, see the HP Data Protector installation and licensing guide.
The omnidlc command can only be run on Cell Managers.
In a MoM environment, you can only collect data for each Data Protector cell separately by running
the command from the respective Cell Manager.
When a debug and logfile collector is used on HP OpenVMS, the following applies:
The OpenVMS ODS-2 disk structure file name can contain the maximum of 39 characters.
As OpenVMS systems do not have the get_info utility, the get_info.out file is blank and is
not collected.
The omnidlc command run with the -session option does not collect the debug files
produced during specified session, because session names are not part of the OpenVMS debug
filename. Instead, all available logs are collected.
The Data Protector GUI debug files for systems other than Cell Manager can only be gathered using
the -hosts option.
To collect debug files in a cluster, the command must be run using the -hosts option; the cluster
nodes hostnames must be specified as the argument for the option. In a cluster, if the -hosts option is
not specified, the data is collected from the active node.
Absolute Path specified in postfix are not allowed.