HP Insight Recovery 1.0 Release Notes
NOTE: HP IR does not support, or install with Microsoft SQL Server 2000 as the database.
Other Requirements
HP Insight Recovery requires that the ESX hosts at the Primary and Recovery sites be managed
by separate instances of VMware Virtual Center server at each site.
Prerequisites
To get to the point where you can install HP Insight Recovery (HP IR) and then complete your
disaster recovery configuration from the HP IR graphical user interface (GUI), you will need to:
• Verify network configuration requirements are met.
• Verify logical server setup requirements are met.
• Verify storage configuration requirements are met.
• Create the recovery logical servers at the Recovery Site.
It is assumed that Networking and Storage Replication links are present between the 2 sites.
Networking Setup
You can use HP Insight Recovery 1.0 in a variety of networking configurations, but it is important
that you take note of the following HP IR 1.0 networking configuration parameters:
• HP IR assumes that the Primary and Recovery Sites operate in an “active-active” mode with
workloads running simultaneously at both sites, but DR Protected workloads only run at
the Primary Site. For this reason, network services such as DNS, DHCP, WINS, and AD,
must be available locally at both sites. If the Primary Site becomes inoperative due to a
disaster, network services will continue to be available at the Recovery Site based on the
native disaster recovery capability in these services, both for the workloads already running
at the Recovery Site and for the workloads that will be failed over from the Primary Site.
HP IR must not be used to failover network services.
NOTE: The HP IR “startup order” feature is intended to start up critical applications first,
not to ensure startup dependencies are met between applications and infrastructure services
such as networking.
• HP IR does not perform DNS updates or update the IP configuration of recovered logical
servers during a failover operation. Your Network Administrator is responsible to make the
necessary modifications to ensure the availability of network services, if you configure the
recovery logical server to use a different IP or subnet than the primary logical server.
• If the logical servers are VC-based, the MAC address used by the recovery logical server is
different from the MAC address used by the primary logical server. If the logical servers
are virtual machines, the MAC address is the same for both the primary and recovery logical
servers. Your Network Administrator needs to plan for this in the networking configuration
for DR Protected logical servers, if you are using DHCP.
• If the Primary Site and corresponding Recovery Site managed servers share a common
subnet, you must ensure that there is no conflict between MAC addresses. For example, if
the default set of 64 address ranges provided by VCEM is used at both sites, conflict can be
avoided by using the VCEM “exclusion ranges” feature. At the Primary Site, exclude ranges
32-63, and at the Recovery Site exclude ranges 0-31.
Prerequisites 11