Operating Environment Software Manual

1. Refresh the server resources to reflect any environment configuration changes. In the
Virtualization Manager screen, select Tools→Logical Servers→Refresh. Select Virtual
Connect Resources and Virtual Machine Resources, then click the Refresh button.
2. Retry the HP Insight Recovery Job.
If the job fails again, proceed with troubleshooting by examining the appropriate subsystem.
To identify the subsystem where the failure occurred, review the remainder of this section
for information on which log files you need to look at and what action you need to take. For
additional information, you can view the lsdt.log log files in the logs directory where
HP Insight Recovery is installed on the system.
The concept of a "Job" in HP Insight Recovery is a multi-step automated process, for example, a
site failover. A site failover Job is initiated by clicking on the Sites tab, then clicking on the
Change local site to Primary Site button, or the Change local site to Recover y Site button.
For example, the Job with a Job Id of 8 shown in the screen capture below is a Change local
site to Primary Site site failover job. It has an Entity of type Site and an Operation of type
recovery → primary to denote that the original Recovery Site will become the Primary Site upon
completion of the failover. You will also notice in the Status column that Job 8 has failed.
NOTE: The corresponding Job to change the original Primary Site to become the Recovery Site
is initiated by clicking on the Change local site to Recovery Site button.
NOTE: The role of a site in HP Insight Recovery is not changed until a site Job has completed.
For a failed Job, click on the associated Job Id to get detailed information about the associated
Sub Jobs.
A Site Job contains a Sub Job for each Recovery Group. Similarly, each Recovery Group has Sub
Jobs for its Storage Replication Group and logical server, respectively.
To trouble shoot a Site Job and identify the source of the error, drill down to each of the associated
failed Sub Jobs to determine what operation failed and the reason for the failure, as shown in
the following screen capture:
HP Insight Recovery troubleshooting 29