HP Insight Recovery 1.0 Release Notes

the HP Insight Recovery 1.0 online help. To view or download a version of this PDF file
with working links, go to: http://www.docs.hp.com/en/vse.html#HP%20Insight%20Recovery
• If HP Insight Recovery is installed from the Insight Software 3.0 DVD, the online help files
associated with the Planned Failovers, Unplanned Failovers, and Authorizing a SIM User to
Administer Insight Recovery modules in the HP Insight Recovery graphical user interface are
missing. In addition, the HP Insight Recovery 1.0 Online Help (Document Format) PDF file
cannot be accessed from the HP IR graphical user interface. These issues are fixed on the
Insight Software 3.1 DVD. The missing files and can also be viewed in an online copy of the
HP Insight Recovery 1.0 Online Help (Document Format) at: http://docs.hp.com/en/
vse.html#HP%20Insight%20Recovery
• The site role reversal procedure for the original Primary Site, after an unplanned failover, is
not accurately documented in the HP IR online help.
You must use the following procedure to change the HP IR site role from primary to recovery
at the original Primary Site, after an unplanned failover:
1. Ensure that the Replication Group disks are read-only at the original Primary Site, by
setting them up as replication targets for the disks at the new Primary Site.
2. Start the ESX hosts on the original Primary Site. VMs that are associated with DR
Protected logical servers will be in an inaccessible state, because the datastores associated
with them will become inaccessible as a result of step 1 (above).
3. Delete Recovery Groups that include VM-based logical servers from the HP IR
configuration at the original Primary Site.
4. Delete the DR Protected VM-based logical servers using the “Recoverable Logical Server
Definition Deletion” option from the ID-VSE user interface.
5. Using VMware Virtual Center, remove all VMs that are associated with DR Protected
logical servers from the inventory of the ESX hosts.
6. Rescan the ESX hosts and discover VM-based logical server resources, as needed, at the
original Primary Site.
7. Run "Change Local Site to Recovery" at the original Primary Site.
8. Follow the instructions in step 2. of “Recovery Site Logical Server Setup” (page 13) to
re-create the VM-based recovery logical servers.
9. Use the HP IR export/import procedure to make the original Primary Site a new Recovery
Site as documented in the HP IR online help.
• The user interface options for UseNonCurrentDataOk when you configure storage do not
match the online help text - “True” in the online help is equivalent to “yes” and “False” in
the online help is equivalent to “no”
• The Jobs screen shows recovery group failover as 0% complete, before a logical server is
activated.
• There is a delay in the site role change when Change Local Site to Primary is run
consecutively.
Limitations
• The Matrix 1.01 update introduces ID-VSE support for VMware ESX 4.0, but HP Insight
Recovery 1.0 does not support failover of VMs created on ESX 4.0 (or any other ESX host),
to an ESX 4.0 host. To avoid unsuccessful failover of HP IR Recovery Groups:
1. Do not assign an ESX 4.0 host to an HP Insight Recovery license.
2. Do not configure a VM-based Logical Server in an HP IR Recovery Group, if the VM
was created in an ESX 4.0 environment.
• With StorageWorks EVA Command View version 9.0, the new Multiple Command View
Server Discovery feature must not be configured to discover the primary and recovery site
Command View server in a single site SIM-S instance. The Discoverer command is used
to add Command View servers to be discovered in a SIM-S instance. Please refer to the
16