HP Matrix Operating Environment 7.0 Recovery Management User Guide

NOTE: Restarting the Job will only retry Sub Jobs that previously failed; servers associated with
completed Jobs or Sub Jobs are already up and running and will not be impacted.
IMPORTANT: If correcting the problem that caused the Job to fail included re-configuration of
logical server(s), before you restart the Job, go to the Recovery Groups tab and delete the Recovery
Group(s) that contain the re-configured logical server(s). Recovery Group(s) that have been deleted
due to the re-configuration of logical server(s) can be recreated with the re-configured logical
server(s) after the Job is successfully completed.
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 Remote
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 Remote Site.
Matrix recovery management troubleshooting 51