HP StorageWorks SAN Virtualization Services Platform 3.0.1 Release Notes (5697 - 0405, May 2010)

• 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.x with a setup that already includes 2 TB or larger back-end virtual
disks.
Upgrade order
When upgrading from SVSP 2.x, the VSM servers must be upgraded first, and then the Data Path
Modules may be upgraded. Each is done one-at-a-time, making the upgrade process a rolling upgrade.
Operating system issues
Miscellaneous Windows issues
The following are currently issues with Microsoft Windows:
• A LUN after an Import-in-Place operation can be accessed (read/write) as a normal disk from the
VSM server. The process of Windows mounting the device on the VSM server can result in corrup-
tion if the device is still mounted when the VSM server is rebooted. Windows Server 2008 on the
VSM server will run the Check Disk utility on that LUN and cause applications that may be accessing
this volume through SVSP to question its integrity. An HP engineering advisory was written for this
issue.
To disable Windows 2008 Auto Mount (after the VSM software is installed on both VSM servers,
after the setup volumes are created, and after performing one test of VSM failover and failback),
enter these commands from the command line: Diskpart, Automount disable, and exit.
SAN Virtualization Services Platform 3.0.1 Release Notes 11