beautypg.com

4 issues, limitations and suggested actions, Limitations, Minor issues – HP Matrix Operating Environment Software User Manual

Page 21

background image

4 Issues, limitations and suggested actions

Issues and limitations of this release are listed below. The following categories are used:
Limitations

Limitations of the implemented functions and features of this release.

Major issues

Issues that may significantly affect functionality and usability in this release.

Minor issues

Issues that may be noticeable but do not have a significant impact on
functionality or usability.

Limitations

No automatic synchronization of configuration between sites

The configuration of HP Insight Recovery 6.0 at two separate sites is not automatically
synchronized, but HP Insight Recovery provides a configuration export and import facility that
simplifies this task.

Suggested actions:

The HP Insight Recovery online help will guide you through the export

and import operations.

Minor issues

ESX configuration setting required for VMFS datastores of HP Insight Recovery
managed logical servers to be visible at Recovery Site

If you have asymmetric Continuous Access EVA array models at the Primary and Recovery Site,
or if you are using Continuous Access XP storage arrays at both sites, HP Insight Recovery
requires a specific ESX configuration setting to retain the signature of a VMFS datastore so it will
be visible at the remote site.

Suggested actions:

For ESX3.X hosts, set Lvm.DisallowSnapshotLun to 0 using Virtual Center

Configuration

Advanced Settings.

For ESX4.X hosts, to mount the Primary 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:

http://www.vmware.com/pdf/

vsphere4/r40_u1/vsp_40_u1_esx_server_config.pdf

For additional information, refer to the

VMware Knowledge Base at:

http://kb.vmware.com/kb/1015986

Convert local site to Primary or Recovery Site operation hangs

If Logical Server Management (LSM) is not able to complete a task initiated by an HP Insight
Recovery Change local site to Primary Site or Change local site to Recovery Site operation
due to underlying stack issues, the HP Insight Recovery operation will hang.

Suggested actions:

Restart LSM services and perform the HP Insight Recovery operation again.

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

Limitations

21