HP Insight Recovery 1.0 Release Notes

NOTE: Re-running the Job will only re-try sub-jobs that previously failed; servers associated

with successfully completed jobs or sub-jobs are already up and running and will not be impacted.

Wait for the Job to complete. After successful Job completion, the HP Insight Recovery Site tab

will display the updated local site role, as shown below:

If a Recovery Group was deleted due to the re-configuration of a logical server, recreate it now

with the re-configured logical server.

Logical server no longer DR protected by HP Insight Recovery after reconfiguration

Issue: It is possible for users to unmanage a logical server configured in a Recovery Group. In

this situation, the logical server is no longer DR protected by Insight Recovery.

Suggested actions:

1. From the Recovery Group tab, delete the Recovery Group containing the logical server.

2. Import the server blade or virtual machine as a logical server if you have not already done

so.

3. From the Recovery Group tab, add a Recovery Group with the newly imported logical

server.

Unsuccessful failover due to logical server configuration out of synch between Primary

and Recovery Sites

Issue: When a DR protected logical server is modified or re-created, and then reactivated,

Logical Server Management (LSM) modifies the internal state information for that logical server.

This causes the logical server configuration to be out of synch between Primary and Recovery

Sites.

Suggested actions: To keep the Primary and Recovery Sites synchronized, export the HP Insight

Recovery configuration at the Primary Site. At the Recovery Site, re-create the Recovery Group

containing that logical server, using the exported HP Insight Recovery configuration file.

Convert local site to Primary/Recovery operation hangs

Issue: If Logical Server Management (LSM) is not able to complete a task initiated by an Insight

Recovery Convert local site to Primary or Convert local site to Recovery operation due to

underlying stack issues, the Insight Recovery operation will hang.

Suggested actions: Restart LSM services and perform the Insight Recovery operation again.

Insight Recovery Job appears to be in hung state

Issue: In the Jobs tab, if the status of an Insight Recovery Job is displayed as In progress

longer than usual, an environment issue may have caused the back end job process to terminate

ungracefully. This can be verified using the task manager on the central management server

(CMS), by confirming that the hp_lsdt_automation.exe job process is NOT running.

Suggested actions: