HP StorageWorks SAN Virtualization Services Platform 2.1.1 release notes (5697-0066, July 2009)

Message when failing over a VSM server after refreshing access paths
When failing over a VSM server after refreshing the access paths, the VSM displays a warning
message that the back-end LUs are not accessible in the passive VSM server. This may be a false
warning, so attempt to fail over despite the message.
VSS with synchronous mirror LUNs
At this time, the use of Microsoft Volume Shadow Copy Service (VSS) on a LUN that is part of a
synchronous mirror within the same domain is not supported. HP is working to remove this limitation.
SAN API virtual disk required for each DPM group
A separate SAN API (also called SAN CLI) virtual disk must be created from each DPM group to each
host that requires a SAN API virtual disk.
Out of memory error when importing a LUN
When importing a LUN using the VSM GUI, you may experience an error 33; out of memory. This
issue was noticed when the installation of Windows did not come from the CDs supplied with the
SVSP product. If you receive this error, HP recommends that you allow Microsoft Windows to determine
the virtual memory size using memory management, and reboot the VSM server.
Setting the host personality to ALUA changes host OS type to “unknown”
After changing the host type, the personality is set to “unknown.” The personality must be manually
changed to the correct setting.
Changing virtual disk or group DPM selection from two to one DPM is not allowed
VSM does not allow changing the virtual disk or virtual disk group DPM’s selection from two to one
DPM. Reducing the DPM selection to a single DPM must be done by removing permissions and
reassigning the permissions through a single DPM.
Computer name of single VSM server in SAN must not be changed
When a single VSM server is connected to the SAN, its computer name must not be changed. Changing
the VSM server computer name is allowed if two VSM servers are connected to the SAN. However,
changing the names must be done by a specific procedure, and to one VSM server at a time.
Letter t in long PiT or snapshot names
If a PiT or snapshot is created with a long name containing 31 characters, the next to last (30th)
character must not be a "t." For example, the name dManual_Prod_Backup_mirror_PIT3 must
not be used for a PiT or snapshot name.
Secure session between VSM client and VSM not possible
Secure sessions (https) between the VSM client and VSM application cannot be used at this time.
12