HP Matrix Operating Environment 7.3 Recovery Management User Guide

Figure 23 Restarting a failed job
NOTE: Restarting the Job retries only Sub Jobs that previously failed; servers associated with
completed Jobs or Sub Jobs are not impacted.
IMPORTANT: If correcting the problem that caused the Job to fail included reconfiguration of
logical servers, before you restart the Job, go to the Recovery Groups tab and delete the Recovery
Groups that contain the reconfigured logical servers. Recovery Groups that have been deleted due
to the reconfiguration of logical servers can be recreated with the reconfigured logical servers 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 that contain 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.
60 Troubleshooting