HP Matrix Operating Environment Software - Manual (Page 11)

NOTE: In the same way that conflict in the configuration of MAC addresses at the Local
and Remote Sites is avoided in “Setting up Networking” (page 9) , conflict must also be
avoided in the configuration of WWNs, if the WWNs are not private to the respective
sites. The same technique using VCEM exclusion ranges is available for array WWN
configuration.
•
Storage Management Server FQDN names and credentials for the Local and Remote
Sites, for example, HP P6000 Command View server name and credentials to access the
Command View server
•
Storage Replication Group name given for the boot and data LUNs of the logical servers
that will be part of the same Recovery Group, for example, the HP P6000 DR Group
name
NOTE:
◦ HP P6000, HP P9000, and User Defined Storage Replication Groups must use the
same Storage Replication Group name at the Local Site and the Remote Site.
◦ HP 3PAR remote copy Storage Replication Groups will have different names at the
Local Site and the Remote Site.
•
Storage port WWN and LUN for the replicated LUN, in the case of raw LUNs used by
DR Protected logical servers
General storage setup notes
•
For information on storage setup of cross-technology logical servers (logical servers capable
of being VC hosted or VM hosted), see:
Dynamic workload movement with CloudSystem
Matrix .
•
For a list of supported storage, see the HP Insight Management 7.1 Support Matrix at http://
www.hp.com/go/matrixoe/docs .
•
Hyper-V virtual machines in clustered environments must be stored on cluster shared volumes.
HP P6000 storage setup notes
•
With HP P6000 Continuous Access Software storage replication, when an asynchronous
replication group is used in a Recovery Group and an unplanned Recovery Group failover
occurs, a full copy of the new source vDisks is automatically duplicated on the new destination
vDisks when the failed site recovers. If a failure occurs in the middle of this full copy operation,
the data on the new destination vDisks could be corrupted. To protect the new destination
vDisks, you must enable the HP P6000 Command View auto-suspend setting to prevent an
automatic full copy operation from occurring. To protect the new destination vDisks, you must
back up the data on them before you manually run a full copy operation.
To prevent a full copy of the new source vDisks to the new destination vDisks after the failover
of asynchronous Storage Replication Groups, Matrix recovery management automatically sets
the mode of all asynchronous Replication Groups to synchronous prior to storage failover and
then resets the mode to asynchronous after the storage failover is completed. The storage link
must be up and both the Local Site and Remote Site arrays must be managed by the same
Command View server for Matrix recovery management to perform this operation.
For the failover of asynchronous Storage Replication Groups to succeed, both the Local Site
and Remote Site arrays must be managed by the same Command View server.
Under rare failure conditions, the mode of a Storage Replication Group can be left in
synchronous mode requiring a manual intervention to reset the mode to asynchronous.
Setting up Storage 11