5.0

Table Of Contents
Troubleshooting SRM 9
If you have problems with replication, site pairing, or guest customization, you can troubleshoot the problem.
To help identify the cause, you might need to collect SRM server or client log files to review or send to VMware
Support.
Errors encountered during SRM operations appear in error dialog boxes or appear in the Recent Tasks window.
Most errors also generate an entry in an SRM log files. Check the recent tasks and log files for the recovery site
and the protected site.
When searching for the cause of a problem, also check the VMware knowledge base at
http://kb.vmware.com.
This chapter includes the following topics:
n
“Events and Alarms,” on page 93
n
“Collecting SRM Log Files,” on page 102
n
“Features Are Unavailable When Deploying VRMS,” on page 103
n
“OVF Package is Invalid and Cannot be Deployed,” on page 103
n
“Connection Errors Between VRMS and SQL Cannot be Resolved,” on page 103
n
“Configuration of the VRMS Database Fails with DB2 Databases,” on page 104
Events and Alarms
SRM supports logging events and each event includes a corresponding alarm that can be triggered when the
event occurs. This provides a way to track to health and functioning of your system and resolve potential issues
before they impact the protection SRM provides.
Alarms are enabled using the Alarm Manager in the vSphere Client. SRM also includes SNMP traps.
Events can be categorized according to functional areas:
n
Site Status
n
Protection Group Events
n
Recovery Events
n
SNMP Traps
n
Storage and Storage Provider Events
n
Licensing Events
n
Permissions Events
VMware, Inc.
93