HP Matrix Operating Environment Software - Manual (Page 12)

Networking setup
It is assumed that networking links are present between the Primary Site and the Recovery Site.
You can use HP Insight Recovery in a variety of networking configurations, but it is important
that you take note of the following HP Insight Recovery networking configuration parameters:
•
HP Insight Recovery assumes that the Primary and Recovery Sites operate in a mode with
workloads running simultaneously at both sites, but with DR Protected workloads running
at the Primary Site only. 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 Insight Recovery must not be used to failover network services.
NOTE: The HP Insight Recovery “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 Insight Recovery 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.
• When running on physical targets (VC hosted) or Hyper-V hosted virtual targets, HP Insight
Recovery does not ensure that the primary logical server uses the same MAC address as the
recovery logical server. When running on VMware ESX hosted virtual targets, HP Insight
Recovery does ensure that the primary logical server uses the same MAC address as the
recovery logical server. Your Network Administrator needs to plan for this in the networking
configuration for DR Protected logical servers, if you are using DHCP.
NOTE: For MAC address details for cross technology logical servers (logical servers that
are capable of running on both VC hosts and VM hosts), refer to Dynamic workload movement
with BladeSystem Matrix: Fluid movement between physical and virtual resources for flexibility and
cost-effective recovery available at: http://www.hp.com/go/insightrecovery
• 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 assigned by VCEM.
For example, if the default address range provided by VCEM is used at both sites, conflict
can be avoided by using the VCEM “exclusion ranges” feature. For example, on the Primary
Site CMS, exclude addresses from 00-21-5A-9B-00-00 to 00-21-5A-9B-FF-FF, and on the
Recovery Site CMS exclude addresses from 00-21-5A-9C-00-00 to 00-21-5A-9C-FF-FF.
Storage setup
HP Insight Recovery depends on storage array replication, for example Continuous Access EVA
Disaster Recovery Groups, to enable failover of logical servers. It is assumed that storage
replication links are present between the Primary Site and the Recovery Site.
To setup HP Insight Recovery Storage Replication Groups, complete the following tasks:
1. Boot and data LUNs for VC or VM hosted logical servers that are to be DR Protected must
be replicated using supported storage replication methods, for example, Continuous Access
EVA or Continuous Access XP.
12 Installing and configuring HP Insight Recovery