HP P2000 HP P2000 G3 MSA System VDS/VSS Hardware Providers Installation Guide - Page 16

Troubleshooting, Troubleshooting the MSA System VSS Hardware Provider

Page 16 highlights

net stop VSS net stop "HP StorageWorks VSS Hardware Provider" Alternately, reboot the server to ensure that all the VSS components have been restarted. Troubleshooting This section contains troubleshooting information for the MSA System VSS Hardware Provider. Table 2 Troubleshooting the MSA System VSS Hardware Provider Issue Description The VSS Provider cannot create a snapshot. The following error is reported: VSS_E_PROVIDER_VETO The shadow copy does not exist on the controller. • The system might not have a license certificate file installed. To enable use of VSS, you must obtain and install a license certificate file for the purchased option. • The maximum number of snapshots allowed by the snapshot license has already been created. • The storage system has failed to execute the commands from the VSS Provider, or the communication between the VSS Provider and the system is broken due to any of the following conditions: • The LUN that will be used to create the snapshot is not a master volume. • The serial number cannot be obtained for the controller owning the master volume partition. • The snapshot cannot be found in the VSS Provider's snapshot list. • The partition is not a snapshot. • The LUN assignment to the newly created snapshot failed. • The snapshot that will be deleted is not a HP snapshot. • The backup utility automatically deletes the shadow copy when the backup is complete. • You might have used the Windows Explorer shadow copy shell extension context menu to create a shadow copy, which is to be used for creating a Windows software shadow copy, not hardware shadow copies. • Make sure you have created the shadow copy using the persistent (-p) attribute. • If you use the Vssadmin tool from Microsoft to create shadow copies, MSA System VSS Hardware Provider is not used. Vssadmin create shadow only works with the Microsoft software shadow copy provider built into Windows. 16

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18

16
net stop VSS
net stop "HP StorageWorks VSS Hardware Provider"
Alternately, reboot the server to ensure that all the VSS components have been restarted.
Troubleshooting
This section contains troubleshooting information for the MSA System VSS Hardware Provider.
Table 2
Troubleshooting the MSA System VSS Hardware Provider
Issue
Description
The
VSS Provider
cannot create a
snapshot.
The following error is reported:
VSS_E_PROVIDER_VETO
The system might not have a license certificate file
installed. To enable use of VSS, you must obtain
and install a license certificate file for the
purchased option.
The maximum number of snapshots allowed by
the snapshot license has already been created.
The storage system has failed to execute the
commands from the
VSS Provider
, or the
communication between the
VSS Provider
and the
system is broken due to any of the following
conditions:
The LUN that will be used to create the
snapshot is not a master volume.
The serial number cannot be obtained for the
controller owning the master volume partition.
The snapshot cannot be found in the VSS
Provider’s snapshot list.
The partition is not a snapshot.
The LUN assignment to the newly created
snapshot failed.
The snapshot that will be deleted is not a
HP snapshot.
The shadow copy does not exist on the
controller.
The backup utility automatically deletes the
shadow copy when the backup is complete.
You might have used the Windows Explorer
shadow copy shell extension context menu to
create a shadow copy, which is to be used for
creating a Windows software shadow copy, not
hardware shadow copies.
Make sure you have created the shadow copy
using the persistent (
-p)
attribute.
If you use the Vssadmin tool from Microsoft to
create shadow copies, MSA System VSS
Hardware Provider is not used. Vssadmin
create
shadow
only works with the Microsoft software
shadow copy provider built into Windows.