Activation or deactivation job hangs – HP Matrix Operating Environment Software User Manual
Page 42
Suggested actions:
•
For ESX3.X hosts, set Lvm.DisallowSnapshotLun to 0 using Virtual Center
→ Configuration
→ Advanced Settings.
•
For ESX4.X hosts, to mount the Local Site datastore with an existing signature, refer to the
chapter titled Mount a VMFS Datastore with an Existing Signature in the ESX Configuration
Guide Update 1, ESX 4.0, vCenter Server 4.0 available at:
For additional information, refer to the
VMware Knowledge Base at:
Activation or deactivation job hangs
If Matrix OE logical server management is not able to complete a task initiated by a Matrix recovery
management Acitvate... or Deactivate... operation due to underlying stack issues, the Matrix recovery
management operation will hang.
Suggested actions:
Restart the HP Logical Server Automation service from the CMS (Windows Administrative Tools –>
Services and Applications –> Services) and perform the Matrix recovery management operation
again.
Identical configuration of logical servers between sites
Local and recovery logical servers must be configured with identical parameters, except for the
logical server name, using Matrix OE visualization. There is a potential for discrepancies, between
the Local Site and the Remote Site, in the values of attributes that are not included in the Matrix
recovery management 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
Local and Remote 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
Local and Remote 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 HP P9000 Storage Management Server and One
RAID Manager instance per HP P9000 device group
Each HP P9000 Continuous Access Software Storage Management Server configured in Matrix
recovery management will have one and only one HP P9000 RAID Manager Software instance
42
Issues, limitations and suggested actions