The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
HPE MSA VDS and VSS Hardware Providers enable Virtual Disk Service (VDS) and Volume Shadow Copy Service (VSS) client applications to manage snapshot operations on MSA arrays as well as configure and manage the arrays. VDS and VSS client applications include:
The MSA VDS and VSS Hardware Providers require installation of the HPE CAPI Proxy component and may be installed concurrently with VSS and VDS Providers for other Hewlett Packard Enterprise products.
The HPE MSA CAPI Proxy provides support for MSA VDS and VSS Hardware Providers on Windows Server 2008 and 2012 platforms. It enables VDS and VSS Hardware Providers to access HPE MSA RAID storage subsystems using inband SCSI commands.
For more information about MSA 1040/2040 VDS and VSS Hardware Providers, see the MSA 1040/2040 System VDS and VSS Hardware Providers Installation Guide.
The following features were added or enhanced in 3.5.0.5: | |
|---|---|
| Added support for G22x firmware. | |
| Added support for using non-zero LUN for in-band communication for SAS configurations that require it. | |
| Hewlett Packard Enterprise branding changes. |
Issue: Uninstalling or updating the software fails, and the folders must be manually deleted before the software can be reinstalled. Workaround: The VDS/VSS providers and CAPI Proxy should be installed in a non-default location, each component must be installed in a separate subfolder. |
Issue: If the host is part of a cluster and MSDTC is not running, VSS installation might fail. Workaround: None. |
Issue: MSA 1040/2040 arrays can create a limited number of snapshots at the same time. Workaround: Delete snapshots when they are no longer needed. |
Issue: Adding disk drives to a RAID 0 LUN may appear to hang VDS clients, because it can take a long time to add the drives to the underlying vdisk. Workaround: As a best practice, first add drives to the vdisk that includes the target LUN, and then expand the size of the LUN as desired. |
Issue: If DISKRAID exits abnormally, stop the VDS service with the net stop vds command. The VDS service automatically restarts. Workaround: If the problem persists, it may be necessary to terminate the DLLHOST process which hosts the VDS Provider. If more than one DLLHOST process is running, the Microsoft Sysinternals Process Explorer utility can be used to determine which DLLHOST process is hosting the VDS Provider. |
Issue: The following DISKRAID commands are not supported: add, break, invalidatecache, ipsec, maintenance controller blink, offline, online, recover, remove, replace, reset, and standby. Workaround: None. |
Issue: Changes made to the array configuration by the SMU may not be visible to VDS clients. Workaround: Use the DISKRAID refresh provider command (or equivalent operation in other clients) to refresh the VDS Hardware Provider’s internal database. |
Issue: After a LUN is assigned to the host, you might need to execute a rescan operation in Device Manager to view the paths for the LUN in some commands, such as detail lun. Workaround: None. |
The latest documentation for the MSA 1040 Controller is available at http://www.hpe.com/support/msa1040/manuals.
The latest documentation for the MSA 2040 Controller is available at http://www.hpe.com/support/msa2040/manuals.
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (<docsfeedback@hpe.com>). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.