HP Insight Recovery 6.2 User Guide

If a Recovery Group was deleted due to the re-configuration of a logical server, recreate it now
with the re-configured logical server.
The following troubleshooting issues are addressed in this section:
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.
Hypervisor management software (for example, VMware vCenter Server) is not running
on the Recovery Site.
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 clxevarun.log in STORAGE/EVA/log
located where HP Insight Recovery is installed on the system, or view the clxrun.log in the
logs directory where CLX or XP are installed on the local storage management server.
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 logs directory where HP Insight Recovery is
installed.
Action
HP Insight Recovery troubleshooting 31