Setting up storage – HP Matrix Operating Environment Software User Manual
Page 10
For information on PINT, see the Portable Images Network Tool (PINT) Linux readme version
1.0.0 available at
•
If the Local Site and corresponding Remote Site managed servers share a common subnet,
you must ensure that there is no conflict between MAC addresses assigned by HP Virtual
Connect Enterprise Manager (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 Local Site CMS, exclude addresses from 00-21-5A-9B-00-00 to
00-21-5A-9B-FF-FF, and on the Remote Site CMS, exclude addresses from 00-21-5A-9C-00-00
to 00-21-5A-9C-FF-FF.
•
For DR protected logical servers and IO services, ESX port group names and Hyper-V virtual
network names must be identical at the Local Site and the Remote Site.
Setting up Storage
Matrix recovery management depends on storage array replication to enable failover of logical
servers. It is assumed that storage replication links are present between the Local Site and the
Remote Site. HP P6000 Continuous Access Software Disaster Recovery Groups are a good example
of this concept.
To set up Matrix recovery management Storage Replication Groups:
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, HP P6000 Continuous
Access, HP P9000 Continuous Access, HP 3PAR, or a User Defined storage replication method.
User Defined storage replication is supported when you create and install a storage adapter
in your Matrix recovery management configuration for a storage type other than HP P6000,
P9000, or HP 3PAR. For example, if you create and install a storage adapter named EMC,
the Storage server type drop-down menu for configuring a
includes EMC as a storage server type. For more information see
User Defined storage adapter” (page 13)
•
If a DR Protected logical server at the Local Site is VC hosted, the replicated boot and
data LUNs on the array at the Remote Site must be presented to the corresponding recovery
logical server.
•
If a DR Protected logical server at the Local Site is VM hosted, the replicated boot and
data LUNs on the array at the Remote Site must be presented to the VM host (for example,
ESX) at the Remote Site that is targeted to run the recovery logical server (for example,
ESX guest).
NOTE:
•
Each Recovery Group has a single Storage Replication Group that is used by the logical
servers in that Recovery Group only. All boot and data LUNs used by these logical servers
must be included in the same Storage Replication Group.
•
A Storage Replication Group is a set of storage LUNs on a particular disk array that are
replicated with write order preserved. This corresponds to the HP P6000 Continuous
Access DR Group concept as well as the HP P9000 Continuous Access
concept.
2.
Create one Storage Replication Group for each set of logical servers that will be included in
a Recovery Group.
3.
Record the following details about the Storage Replication Group configuration. This information
is required when you configure Matrix recovery management for replicated storage:
•
Local and Remote Site storage identifiers, for example, an HP P6000 storage array WWN
or an HP P9000 array serial number
10
Installing and configuring Matrix recovery management