HP StorageWorks SAN Virtualization Services Platform 3.0 release notes (5697-0404, April 2010)

• Do not change any back-end logical unit characteristic (for example, number, name, size [by ex-
panding or contracting], and so on) once it has been virtualized (for example, entered into a VSM
storage pool) or is being managed by the VSM. The LUN identification has been written on the
LU by VSM.
• Before starting a migration task, make sure the task does not have any PiTs (such as user PiTs or
mirror PiTs). If PiTs exist, they must be deleted before the task starts, otherwise a future snapshot
created on these PiTs (or a rollback to them) after migration will not be consistent.
• Before installing or uninstalling VSM, you must make sure that all iSCSI connections are disconnec-
ted. You must log out of all existing iSCSI connections.
• After a disruption (perturbation) of VSM connections, wait at least 15 minutes to let the VSM redis-
cover all paths.
• When booting from the SAN, make sure the host only sees that LUN through one path when there
is no multipathing software on the host.
• When rebooting one DPM, wait at least 30 minutes before rebooting the other DPM.
• Before disconnecting a VSM server from the domain, ensure that the other VSM server is running.
There is an increased risk of a Windows fault when disconnecting (even partially) a VSM server
from the domain (for example, to perform maintenance). The lack of an operational second VSM
server can lead to I/O failure.
• When ordering Continuous Access SVSP LTU licenses, you receive an equivalent amount of Business
Copy SVSP LTU licenses. These additional Business Copy licenses are required by the current
replication software and should not be used for local Business Copy processes.
• Before deleting an asynchronous mirror group, detach the task, delete the group, manually rollback
the PiTs on the destination virtual disk, and then delete the destination virtual disk once completed.
If the PiTs of the detached destination virtual disks are stuck in a rollback state, fail over the VSMs
in the destination domain.
• When disconnecting front-end HBAs, the VSM may not display the updated HBA information.
Therefore, check the access paths of the HBAs using the DPM console.
• Before replacing a DPM, you must manually identify all virtual disks and synchronous mirror groups
for which the removed DPM is the active DPM, and change their active DPM.
• When performing remote asynchronous mirror split and merge operations, after the split, and
before the merge operation, you need to perform a VSM failover in the destination domain. After-
wards, you can perform the merge operation. Otherwise, the operation fails.
• Do not set the LUN range for a UDH when only one LUN is assigned to the UDH (for example,
when the same LUN is assigned to both the first and last LU).
Issues and workarounds
This section describes known issues for the SVSP operating systems, Virtualization Service Manager
(VSM), Data Path Module (DPM), and VSM command line interface (CLI) applications. Workarounds
are provided when possible.
Upgrade issues
Upgrading with large back-end disks
You must not upgrade to SVSP 3.0 with a setup that already includes 2 TB or larger back-end virtual
disks.
SAN Virtualization Services Platform 3.0 release notes 11