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

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 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.
If the LUN is already imported and mounted to the VSM: Use the MountVol D:\ /P command
(where D is the drive letter assigned to the mounted, imported LUN) for every LUN receiving an
Import-in-Place. This unmount the LUN and prevents Windows Server 2008 from remounting it
after a reboot.
• For a Windows HyperV environment, the only supported guest operating systems are the Windows
operating systems—Windows Server 2003 SP2, Windows Server 2008 SP1/SP2, and Windows
Server 2008 R2. HP DSM is not expected to support any non-Windows guest operating system
in a HyperV environment.
• When a file system from the HyperV manager is on the SCSI controllers, they show up as Msft on
the SLES10 SP2 guest host.
• Virtual Connect (VC) is supported on Windows.
• Pass-through or imported virtual disks are not supported in HyperV.
• Windows only recognizes 254 LUNs with the HP DSM driver though the Windows operating
system supports 255 LUNs (maximum).
• Automatic failback of Microsoft Cluster Service resource groups does not occur when both the
HBA cables of one node are pulled out and reinserted.
OpenVMS support without async mirrors
OpenVMS 8.3 is supported with the exception of asynchronous mirrors.
SMI-S provider can delete some setup virtual disks
SVSP normally uses three setup virtual disks that are a part of a synchronous mirror group. It is possible
while using the SMI-S provider to delete two of these setup virtual disks, but not the third. This can
cause system availability issues, so ensure that care is taken to not delete any setup virtual disks.
12