HP Matrix Operating Environment 7.3 Recovery Management User Guide

ESX configuration setting required for VMFS datastores of Matrix recovery
management managed logical servers to be visible at Remote Site
Under the following conditions, Matrix recovery management requires a specific ESX configuration
setting to retain the signature of a VMFS datastore so it will be visible at the Remote Site:
• You have asymmetric HP P6000 Continuous Access Software array models at the Local and
Remote Site.
• You are using HP P9000 Continuous Access Software storage arrays at the Local and Remote
Site.
• You are using HP 3PAR storage systems.
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, see “Mount a
VMFS Datastore with an Existing Signature” in the ESX Configuration Guide Update 1, ESX
4.0, vCenter Server 4.0 available at http://www.vmware.com/pdf/vsphere4/r40_u1/
vsp_40_u1_esx_server_config.pdf. For additional information, see the VMware Knowledge
Base at http://kb.vmware.com/kb/1015986.
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 hangs.
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. Because disjointed address ranges must be
used at the Local and Remote Sites, the MAC address for a Local Site logical server and it’s
corresponding Recovery Site logical server are different.
• HBA WWN—For a VC-hosted logical server, the HBA WWN address is assigned by Virtual
Connect or Virtual Connect Enterprise Manager. Because disjointed address ranges must be
used at the Local and Remote Sites, the HBA WWN address for a Local Site logical server
and it’s corresponding Recovery Site logical server are 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 must map presented
LUNs 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
50 Issues, limitations, and suggested actions