HP Matrix Operating Environment Software - Manual (Page 29)

• Failover job failed because storage failover failed Possible causes include:
— Storage Management Servers were not available at the time of the failover.
• Failover job succeeded but recovery logical servers are not activated. Possible causes include:
— Recovery Groups containing logical servers that are in Maintenance Mode at the
Recovery Site.
• Failover job failed because there are no sufficient licensed physical servers or Virtual machines
to host the logical servers
Possible causes include:
— Physical servers are running other workloads.
• Insight Recovery job failed because of unlocatable logical server in LSM. Possible causes
include:
— A logical server managed by HP Insight Recovery was removed from LSM, before it
was unmanaged in HP Insight Recovery.
• Insight Recovery job failed because an operation failed in LSM for the logical server Possible
causes include:
— Power-up of the logical server may have failed.
Failover job fails because storage failover of Storage Replication Groups
failed Error message
Possible causes include the Storage Management Server not being accessible during the time of
failover, or the status of the Storage Replication Groups does not permit a storage failover. Cause
Ensure that at least the local Storage Management Server is accessible and actively managing one
of the arrays. To further triage the problem, view the {IR_INSTALL_DIR}\storage\EVA\
logs\clxevarun.log
log file on the CMS if you are using EVA disk arrays, or view the
{CLX_INSTALL_DIR}\logs\clxrun.log log file on the local Storage Management Server, if
you are using XP disk arrays. Also look at the lsdt.log file located in the HP Insight Recovery
install directory.
Action
Failover job fails because of unlocatable logical server in LSM Error message
A logical server may have been deleted using the Virtualization Manager without removing the
Recovery Group containing the logical server from HP Insight Recovery. Cause
Remove the logical server from the Recovery Group in HP Insight Recovery and rerun the failover
job. Also look at the lsdt.log file located in the HP Insight Recovery install directory. Action
Failover job succeeds but certain logical servers are not activated Error message
Recovery Groups containing those logical servers may be in Maintenance Mode. Cause
Disable Maintenance Mode on the Recovery Groups and rerun the failover operation. Also look
at the lsdt.log file located in the HP Insight Recovery install directory. Action
Failover job fails because of insufficient servers Error message
There may not be enough licensed physical resources capable of hosting the logical servers. Cause
Ensure that there are enough physical servers licensed for Insight Dynamics available to host the
logical servers managed by HP Insight Recovery. Also look at the lsdt.log file located in the
HP Insight Recovery install directory. Action
HP Insight Recovery log files
See the following log files for useful HP Insight Recovery troubleshooting information:
HP Insight Recovery log files 29