HP StorageWorks SAN Virtualization Services Platform 3.0.
Legal and notice information © Copyright 2008-2010 Hewlett-Packard Development Company, L.P.
Description HP StorageWorks SAN Virtualization Services Platform (SVSP) is a hardware and software solution that enhances the storage capabilities of approved storage arrays. Using Virtualization Service Manager (VSM) software, redundant VSM servers and Data Path Modules (DPMs) map application server I/O to locations on storage systems. Versions HP SAN Virtualization Services Platform 3.0.1, which includes: • Virtualization Services Manager software version 1.2.530 supported by LSI HBA driver version 9.1.
Fixes The following issue was fixed in the HP StorageWorks SAN Virtualization Services Platform from version 3.0 to version 3.0.1: With synchronous mirrored virtual disks, certain error conditions may require an I/O timeout and retry by the host to detect. In these cases, the mirror leg would not be marked failed (and the mirror transitioned to Journal mode) until that timeout and retry has occurred, which may take a minute or more. In that interval, I/O to that synchronous mirror may hang.
OS Version Supported Not supported Comments HP-UX Support for existing customers only, as Secure Path is not available for this version any longer. 11.23 11.31 Linux RHEL 4.7 RHEL 4.8 RHEL 5.1 RHEL 5 U2 RHEL 5 U3 RHEL 5 U4 RHEL 6.0 SLES 9 SLES 10 SP2 SLES 10 SP3 SLES 11 Mac OS X NetWare 6.5 OpenVMS 8.3 Solaris 9 No clusters SAN Virtualization Services Platform 3.0.
OS Version 10 Supported Not supported Comments No clusters VMware ESX 3.5 ESX 4.0 Windows 2003, R2, SP2 2008 SP1, SP2 2008 R2 HyperV HyperV v2 Xen (Citrix) 5 5.5 (RHEL 5.3 kernel) Xen (RHEL) 5.2 5.3 To obtain the HP MPIO Full Feature DSM and DSM Manager: 1. Go to http://www.hp.com and click Support & Drivers. 2. In the Step 1 area, select the Download drivers and software (and firmware) option. The Step 2 field becomes available. 3.
Devices supported See the HP Single Point of Connectivity Knowledge (SPOCK) website at http://www.hp.com/storage/ spock for approved driver and firmware versions for host bus adapters used with AIX, HP-UX, Linux, Microsoft Windows Server, Sun Solaris, and VMware operating systems. Site registration is required. SVSP-supported storage arrays See the HP Single Point of Connectivity Knowledge (SPOCK) website at http://www.hp.com/storage/ spock for a list of SVSP-approved storage arrays.
• Maximum number of virtual disks (including snapshots, snapclones, 4 paths): 4093 + 3 setup virtual disks per DPM pair. • Maximum number of virtual disks per host: 255 (LUNs 1–255)—depending on operating system • Maximum size of virtual disk: 16 TB • Minimum size of virtual disk: 1 GB • Maximum number of PiTs per virtual disk: 32 at 10–minute intervals or 64 at 60–minute intervals • The minimum interval between point in time (PiT) copies is 10 minutes.
• Using the VSM client requires a JRE version of 1.5.0.06 or greater. • The VSM client is approved for use only with Internet Explorer version 7 and higher, or Mozilla Firefox version 2.0 and higher. • Before the initial launching of the VSM client, ensure you know which VSM server is active so you target the correct (active) VSM server of the system. • Before connecting an upgraded or replacement VSM server to the SAN, you should install all the license keys on the server.
1. A virtual disk is created from a pool. 2. The virtual disk is presented to a host. 3. The first I/O stream is initiated to the virtual disk. 4. A PiT is created from the virtual disk. 5. A snapshot is created from the PiT. 6. The snapshot is presented to a host. 7. The second I/O stream is initiated to the snapshot. If you decide to delete the virtual disk, you should remove or halt all the operations that were performed from the time the virtual disk was created, by working backwards.
• 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 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. Be sure you do not unmount the setup virtual disk.
Restoring a VSM setup from a backup cannot have PiTs Restoring a VSM setup from a backup can be safely performed only if there are no PiTs in the system. If PiTs exist (either created directly or by Business Copy or Continuous Access applications), their metadata in the setup backup may be invalid and may result in data loss/corruption if restored. Error 1618 during VSM installation During a VSM installation, you may receive an error 1618 and the procedure aborts.
Issue when exceeding 180 async mirror tasks When the number of asynchronous mirror data mover tasks on a single VSM server exceeds 180, a situation may arise under specific conditions where the existing asynchronous mirror PiTs do not progress and new PiTs are not created. A workaround is: 1. Stop and start the VSM service on the passive server using the VSM Monitor. 2. From the active VSM server, failover to the passive server.
Long boot time with large configurations In a configuration with large numbers of devices, configured with large number of paths, the host system takes more time to boot up. This is normal Windows behavior, which takes awhile to detect devices and load drivers.
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. Windows fault when array unresponsive There is a Windows limitation that when an array is overloaded, it may return the command unprocessed with a SCSI BUSY or QUEUE FULL status.
LUNs must have a preferred path/controller VSM does not support EVA or MSA LUNs that are configured in No Preference mode. They must be preferred to Path A or B. If No Preference LUNs are presented to the VSM server, they will not display in the GUI, and are therefore not manageable by the VSM. To resolve this issue: 1. Using HP Command View EVA or MSA management interface, unpresent the No Preference LUNs. 2. Perform a rescan of the hardware with the VSM GUI. a.
NOTE: All the above communications are confined to the SVSP domains. External communications (for example, the GUI and other SOAP clients connected to the web server) are done according to the site configuration (either through IPv4 or IPv6 addresses). • If an IPv6 address is added or deleted while VSM is running, the VSM Monitor cannot detect this change without restarting the VSM application.
DPM group. The newly added DPM will not join the old DPM group. To recover from this issue, perform the following steps: 1. Manually delete the old (partial) DPM group. 2. Verify the front-end HBA list is the same for both DPMs, their rank is the opposite, and they have the same WWNN. 3. Manually create a new DPM group consisting of the two DPMs. 4. Verify the correct exposure of the virtual disks in both DPMs. 5.
Rescan is required after deleting or unpresenting virtual disks Hosts may not automatically detect that a virtual disk has been deleted or unpresented. A rescan should be performed on the host after any virtual disks to that host have been deleted or unpresented. This is required before any new virtual disks, especially any with the same LUN as a deleted/unpresented virtual disk, are presented to the host.
DPM reboot when unpresenting/re-presenting back-end virtual disks Under certain circumstances, if permissions to a back-end virtual disk are removed from the SVSP system (DPM and VSM), and then permissions are restored, or a new back-end virtual disk is created with the same LUN number, the DPM may unexpectedly reboot. HP recommends that such operations be scheduled for off-hours or during a maintenance window.
DSM has been installed and the personality selected for the UDH has been changed to ‘HP-EVA VS-ALUA’. An alterative workaround would be to reboot both DPMs after FF-DSM has been installed and the personality for the UDH has been changed. VSM CLI issues Some VSM CLI commands cause the CLI application to stop The ExpandPartition, ExpandPartitionEX, and GetBackEndLUPartitionNumbers commands have been found to stop CLI processing. Do not use these command with a Windows 2008 R2 server.
Incorrect error message when creating 65th PiT on a virtual disk When creating the 65th PiT on a virtual disk using the VSM CLI, you receive an error message indicating A SCSI error in I/O to the switch. The correct error message should be the Virtual disk has too many PiTs. HP is working to resolve this issue. The ListSnapshots command fails to return data with too many PiTs The ListSnapshots command with a –PiT argument does not return data with 2048 PiTs.
The CreateSnapcloneGroupEx command fails with HP-UX if the group is still building The CreateSnapcloneGroupEx command should run the first time. However, with HP-UX, if the command is run again while the snapclone operation is still building the copy, the command fails. You should increase the timeout argument to as long as you believe the building operation should last. HP is working to resolve this issue.
