HP Data Protector Operations Guide

Support files
The table below describes the Data Protector log files:
Log File Description
debug.log
Contains unexpected conditions. While some can help you, the information is
mainly used by the support organization.
inet.log
Contains local security-related events for the client, such as denied requests.
On UNIX, it also contains all requests made to the Data Protector Inet service.
enhincr.log
Contains information on enhanced incremental backup activities, for example
detailed error information for problems with the enhanced incremental
backup repository.
Ob2EventLog.txt
Contains Data Protector events and notifications. The Event log represents a
centralized Data Protector event depository.
media.log
Each time a medium is used for backup, initialized, or imported, a new entry
is made to this log. The file can be used when recovering the IDB to find the
medium with the IDB backup and to find out which media were used after the
last backup of the IDB.
omnisv.log
Contains information on when Data Protector services were stopped and
started.
security.log
Contains security-related events on the Cell Manager. Some events may be a
result of normal operation and simply mean that an operation was attempted
that is not allowed by a particular user. On the other hand, events can
indicate that deliberate break-in attempts may be in progress.
purge.log
Contains traces of the background purge of the IDB.
RDS.log
Contains IDB logs. The file resides on the Cell Manager in:
• UNIX systems:
/var/opt/omni/server/db40/datafiles/catalog
• Windows Server 2008:
<Data_Protector_program_data>\db40\datafiles\catalog
• Other Windows systems:
<Data_Protector_home>\db40\datafiles\catalog
sanconf.log
Contains session reports generated by the sanconf command.
sm.log
Contains details on internal errors that occurred during backup and restore
sessions, such as errors in parsing backup specifications.
upgrade.log
Created during upgrade; contains upgrade core part (UCP) and upgrade
detail part (UData Protector) messages.
OB2_Upgrade.log
(UNIX only)
Created during upgrade; contains traces of the upgrade process.
IS_install.log
Contains a trace of remote installation and resides on the Installation Server.
sap.log,
oracle8.log,
informix.log,
sybase.log,
db2.log
Application-specific logs containing traces of integration calls between the
application and Data Protector. The files reside on the application systems.
Database copy
If a copy of the IDB is needed for support, stop the Data Protector services, zip up the
db40
directory and restart the Data Protector services. The required files can be found under the restore
window of the IDB backup. Configuration parameters such as
omnirc and global files, are
part of the IDB backup session. Zip up the entire
db40 folder and the config/server folder.
Note: If no downtime is possible, a backup can be run from the IDB as well, and the tapes can
be exported and sent to HP Support.
56 | Page