HP StoreVirtual 4000 Release Note page 20

Volume Shadow Copy Service error: Unexpected error querying for the
IVssWriterCallback interface. hr = 0x80070005, Access is denied.
This message can be ignored. The snapshot was take successfully on the cluster server where the
volume resides.
Scheduled application-managed snapshots fail intermittently if volumes have active I/O
This issue occurs if there are cluster shared volumes in the configuration and the I/O load is set
to 8K OLTP. The failures generate error messages indicating that the application-managed snapshot
has failed due to a connection timing out or due to some other conflict. The error messages include
the following examples:
◦
The snapshot schedule 'xxxx' status in cluster 'xxxx' is 'Failed': 'App-Managed SS Completed
with Warning: VSS Provider: Point in time snapshot is created. The system could not quiesce.'
◦
The snapshot schedule 'xxxx' status in cluster 'xxxx' is 'Failed': 'App-Managed SS Failed:
Another app-managed snapshot is in progress.'
◦
The snapshot schedule 'xxxx' status in cluster 'xxxx' is 'Failed': 'App-Managed SS Failed:
VSS operation timed out.'
◦
The snapshot schedule 'xxxx' status in cluster 'xxxx' is 'Failed': 'App-Managed SS Failed:
Cannot get application server information: connection timed out'.
SQL Server is not quiesced when taking application-managed snapshots on an SMB cluster volume
With Windows Server 2012, SQL Server is not quiesced when an application-managed snapshot
is taken on an SMB cluster volume. The snapshot appears as if it is a managed snapshot, but
because SQL Server was not quiesced, it is not a true managed snapshot.
Unable to take application-managed snapshots of Fibre Channel Hyper-V volumes
Version 10.0 requirements for using a Controlling Server IP address have expanded. If you are
using application-managed snapshots, you must assign a controlling server IP address to each
server you create in the CMC. The information below is available by clicking on the link What
IP address do I use? in the New Server and Edit Server windows.
"The IP address to use depends on your application type and environment. For Windows Failover Clusters, there will
typically be more than one LeftHand OS server object associated with the cluster. For this environment, enter a
controlling IP address for each of the LeftHand OS server objects in the Windows Failover Cluster. The table below
describes which IP address should be entered in the controlling server IP address field for the LeftHand OS server
object."
20 Workarounds