HP Matrix Operating Environment Software User Manual
Page 22
Identical configuration of logical servers between sites
Primary and recovery logical servers must be configured with identical parameters, except for
the logical server name, using the Virtualization Manager. There is a potential for discrepancies,
between the Primary Site and the Recovery Site, in the values of attributes that are not included
in the HP Insight Recovery user interface configuration screens. For example:
•
MAC Address — For VC hosted logical servers, the MAC address is assigned from Virtual
Connect or Virtual Connect Enterprise Manager. Disjoint address ranges must be used at
the Primary and Recovery Sites, hence the MAC address for a primary logical server and
the corresponding recovery logical server will be different.
•
HBA WWN — For a VC hosted logical server, the HBA WWN address is assigned by Virtual
Connect or Virtual Connect Enterprise Manager. Disjoint address ranges must be used at
the Primary and Recovery Sites, hence the WWN for a primary logical server and the
corresponding recovery logical server will be different.
•
BIOS UUID — There is no supported mechanism to preserve the UUID for a VC hosted
logical server as it moves across sites (as there is when it moves within a site).
•
BIOS Serial Number — There is no supported mechanism to preserve the serial number of
a VC hosted logical server as it moves across sites (as there is when it moves within a site).
•
Array LUNs — On a VC hosted 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 VM hosted logical server, the ESX OS on the host must map the presented
LUNs to the VMFS used by the VM hosted 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.
Suggested actions:
Assess the impact of these discrepancies on any licensing arrangements in
use for the operating system and applications running on DR Protected logical servers.
One Raid Manager instance per XP Storage Management Server and One Raid
Manager instance per XP device group
Each Continuous Access XP Storage Management Server configured in HP Insight Recovery will
have one and only one Raid Manager instance managing the XP Device groups. Each Continuous
Access XP Storage Replication Group configured in HP Insight Recovery will be managed by
one Raid Manager instance at each site.
Suggested actions:
There is no workaround for this issue.
CLX/XP software must be installed on a separate Windows system
A separate Windows system other than the Central Management Server (CMS) should be
configured with CLX/XP, and compatible Raid Manager XP software, to manage the various
Continuous Access XP Device groups to be included in an HP Insight Recovery configuration.
Suggested actions:
There is no workaround for this issue.
One Active HP Insight Recovery configuration operation at any point in time
If multiple users attempt to run configuration operations in HP Insight Recovery, only one
operation will succeed. All other configuration operations will receive an error message indicating
that some other configuration operation is in progress.
Suggested actions:
There is no workaround for this issue.
Site delete operation in HP Insight Recovery does not remove SIM tools
If Continuous Access XP Storage Management Servers are configured and if a site delete operation
is performed, the SIM tools used to manage XP storage replication on the local Storage
Management Server will not be deleted.
22
Issues, limitations and suggested actions