HP XP Cluster Extension Software Administrator Guide

7 Troubleshooting
To troubleshoot problems with XP Cluster Extension, you must understand Continuous Access
environments. Many issues can be attributed to incompatible disk pair states. See the Continuous
Access and RAID Manager documentation before assuming that a problem has been caused by
XP Cluster Extension.
CAUTION:
XP Cluster Extension cannot handle device/copy group states automatically and correctly when
they result from manual manipulations. XP Cluster Extension will try to automatically recover
suspended RAID Manager device/copy group states if the AutoRecover object is set to YES.
However, if the recovery procedure experiences a problem, XP Cluster Extension will not stop
unless fence level DATA is used or the ApplicationStartup object is set to RESYNCWAIT. Therefore,
ensure that the device/copy group PAIR state has been recovered before the next failure occurs.
Always disable automatic application service failover when resynchronizing disk pairs. A failure
of the resynchronization source while resynchronizing can lead to unrecoverable data on the
resynchronization target. The resynchronization process does not copy data in transactional order.
For more information, see “Implementing rolling disaster protection” (page 59).
XP Cluster Extension log files
XP Cluster Extension provides log messages to the cluster software as well as to the XP Cluster
Extension log file. The XP Cluster Extension log file includes disk status information.
• The XP Cluster Extension log file is located in
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\
• For the configuration tool, the clxXPcfg.log file resides in:
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\
If the log file needs to be cleared and reset, for example, to reduce disk space usage, archive the
log file and then delete it. A new log file is generated automatically.
For information about log levels, see “LogLevel” (page 49).
Start errors
Start errors can occur when the path to the RAID Manager binaries has not been set in the PATH
environment variable. If a user configuration file is not found in the correct directory location, XP
Cluster Extension returns a local error.
Failover error handling
XP Cluster Extension automatically fails over if the system on which the application is running
becomes unavailable. This also means that if a problem with the disk array state occurs, an
application startup process will be stopped. The behavior of XP Cluster Extension is highly
configurable.
Depending on the customer setting, XP Cluster Extension is used to prevent applications from starting
automatically under the wrong conditions. Therefore, XP Cluster Extension will return local, data
center-wide, or even cluster-wide errors to prevent accidental access to the disk array disk set.
XP Cluster Extension log files 65