HP Insight Recovery 1.0 Release Notes

BIOS Serial Number - There is no supported mechanism to preserve the Serial Number
for a physical logical server as it moves across sites (as there is when it moves within a
site).
Array LUN Numbers - On a physical logical server, the Windows or Linux OS is
responsible for mapping the LUNs presented to them correctly to the volumes and file
systems configured for the OS. For a virtual logical server, the ESX OS on the host must
map the presented LUNs to the VMFS used by the virtual logical server. Although the
operating systems have built-in mechanisms to do this, HP recommends as a best
practice that you keep LUN numbers the same for corresponding disks across sites (if
possible).
If an incorrect site name is entered during site creation, instead of entering the correct site
name in the page with the error message, you must go back to the Sites tab and enter correct
site name there.
The HP IR installer will install HP IR 1.0 even if it is already installed.
HP IR 1.0 includes a bundled light version of CLX for EVA. Installation of a licensed version
of CLX for EVA on a CMS node is not supported.
HP IR 1.0 requires upper case letters to be used in the EVA Storage WWN
Related Information
Extensive Online Help and Tool Tips are included in the HP Insight Recovery GUI.
The HP Insight Recovery Version 1.0 Release Notes (this document) are included on the HP
Insight Software DVD and in the HP Insight Recovery section at: http://www.docs.hp.com/en/
vse.html
The HP Insight Recovery White Paper is also available in the HP Insight Recovery section at:
http://www.docs.hp.com/en/vse.html
Troubleshooting
To troubleshoot a problem encountered in HP Insight Recovery, it is typically necessary to
examine the subsystems to identify the source of the issue.
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 button. A site failover job 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. as shown in the Jobs screen below:
18