Monitored Log Files; Data Protector Default Log Files; Omnisv.log - HP Data Protector A.06.11 Integration Manual

Use the Operations Manager Policy Editor on the Operations Manager Server to
adjust how often each monitor is started. If you change any Operations Manager
policy, it must be redistributed to the assigned systems before it becomes active.

Monitored log files

You can use Operations Manager to monitor applications by observing their log
files. You can suppress log file entries or forward them to Operations Manager as
messages. You can also restructure these messages or configure them with Operations
Manager-specific attributes. For details, see the Operations Manager documentation
(see http://www.hp.com/support/manuals) and online help.
Four Data Protector log files are monitored for warning and error patterns. Basic
information is provided in the HP Data Protector troubleshooting guide.

Data Protector default log files

There are two default log files on every system where the Data Protector core is
installed:
•

omnisv.log

•
inet.log
omnisv.log
Generated when omnisv -start or omnisv -stop is executed. The date/time
format is fixed and not language dependant. The format is:
Format: YYYY-[M]M-[D]D [H]H:MM:SS - {START|STOP}
Parameters for messages for the default log files are:
Message Group
Applications
Note
Severity
Service Name
Object
70 Using the Data Protector Integration
DP_Misc
Data Protector
name_system on which log file resides
omnisv.log: NORMALinet.log: WARNING
Services.Data Protector.cell name
logfile name