HP StorageWorks SAN Virtualization Services Platform Administrator Guide (5697-0934, May 2011)

disk is present on a system, these systems can be configured to support shadow copies of all
disk systems mounted on them.
Installing and configuring Microsoft VSS with VSM virtual disks
Use the following checklist to make sure that you implement all of the requirements for running VSS
on the VSM virtual disks presented by the DPMs. The checklist applies to each host that is using
VSS. These hosts include the application hosts and the hosts that back up the data to tapes or disks.
Configuration checklist for VSM deployment with VSS
You are using a Windows server or a Windows virtual machine on a VMware ESX server.
The full-featured DSM has been installed on the Windows server or native multipathing is
being used for the VMware server.
Confirm that the server is defined as a host in the VSM GUI.
On the VSM, create a SAN CLI virtual disk and present it to the host.
On the host, make sure that the SAN CLI virtual disk is recognized on Disk Management.
On the host, install the SVSP VSS hardware provider. See “Installing the SVSP VSS hardware
provider on the host server” (page 67).
On the host, configure the SVSP VSS hardware provider with a user that can access and
manage the SVSP domains.
On the host, install the Microsoft hot fix KB891957, which fixes volume Shadow Copy Service
issues in Windows Server 2003. You can download KB891957 from http://
support.microsoft.com/kb/891957.
Installing the SVSP VSS hardware provider on the host server
NOTE: For VSS to work correctly, you must first install the SVSP full-featured DSM on a Windows
server. Native multipathing is used on a VMware virtual machine.
You can install the SVSP VSS hardware provider using a single installation package. The final step
in the installation process automatically starts the SVSP VSS Hardware Provider Service.
Installing and configuring Microsoft VSS with VSM virtual disks 67