HP LeftHand SAN Solutions Support Document - Service Notes - VSA 7.0 for VMware ESX

Workaround

1 Convert the volume back to a remote volume.

2 Convert it to a primary, but with full provisioning.

3 Edit the volume and make it thin provisioned.

MS Cluster Failovers When Migrating A Large Number Of Volumes

Concurrently (7485)

Scenario

You may experience delayed write failures and cluster failovers. The client

servers become unresponsive.

When migrating volumes from one cluster to another, multiple disk groups

fail. The iSCSI session is overloaded and write failures and cluster failovers

by accessing the iSCSI initiator UI and Cluster Admin UI during the process.

The application log is noted with a hungapp error.

Workaround

When migrating volumes, stagger the migrations. Do not start all at the

same time.

Volumes With Degraded Replication Are Not Apparent (7363)

Scenario

There are two scenarios for this issue:

• You change a volume from 0-way replication to 2-way replication, and the

software displays a message at the start of this transition that the volume

is now 2-way replicated. However, during the transition period from 0-way

to 2-way replication, if you lose a storage module or perform an upgrade,

the changed volume goes offline. This scenario often transgresses to the

next one.

• A storage module is down, and 2-way replicated volumes are really not

fully replicated anymore. The Console shows these volumes as Normal.

There is no indication that the volume has a lower reliability level than

the replication goal that is set on the volume.