11.0 HP StoreVirtual Storage Application-Aware Snapshot Manager Deployment Guide (AX696-96318, September 2013)

Table 1 Application Aware Snapshot Manager Issues and solutions (continued)
SolutionIssue
(and active on the other node). The snapshot is taken
successfully. You can ignore this message.
If an application-managed snapshot is created while a NIC
failover is in progress on an application server, the
following error may display in the Windows event log:
An error occurs when an application-managed snapshot
is created during NIC failover on an application server.
App-Managed SS Failed: Could not get list
of volumes on server
Wait until the NIC failover has completed.
Application-managed snapshots should then resume
successfully.
When taking application managed snapshots via the CMC
or the CLI on a volume that contains a large number of
Snapshots fail with the following error:
Cannot create a quiesced snapshot because
the snapshot operation exceeded the time
virtual machines, some virtual machines may fail due a
failure to quiesce. The culprit could either be the VMware
limit for holding off I/O in the frozen
virtual machine.
tools synch driver or MS VSS. The failure is not reported
in the CMC as the CMC is not currently logging VM
quiesce failures. For more information, see the VMware
KB article:
http://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1018194
The process of creating an application-managed snapshot
on a VMware volume consist of the following steps:
After creating an application-managed snapshot on a
VMware volume, the event log may include an error
message such as:
1. Snapshots of all virtual machine volumes on the VMware
volume are created.
Failed to create application managed
snapshot.
or
2. The application-managed snapshot is created.
3. The intermediate virtual machine snapshots (in step 1)
are deleted.
Failed to create snapshot for one or more
VMs.
If a virtual machine is busy when the virtual machine
snapshots are being created, the VMware API may time
out. The application-managed snapshot is still created, but
the intermediate virtual machine snapshots are not deleted.
The virtual machine snapshot manager will indicate that
the virtual machine snapshots were created, but will not
display an indication that they were deleted. To resolve
this issue, you must manually delete the intermediate virtual
machine snapshots.
This message can be ignored. The snapshot was take
successfully on the cluster server where the volume resides.
If you have a failover cluster configuration using Windows
Server 2012 servers and an application-managed snapshot
is taken on a volume, the following error message may
display in the Windows Application log on the cluster
server that does not own the volume:
Volume Shadow Copy Service error:
Unexpected error querying for the
IVssWriterCallback interface. hr =
0x80070005, Access is denied.
With Windows Server 2012, SQL Server is not quiesced
when an application-managed snapshot is taken on an
Application-managed snapshots do not work on SMB file
shares presented by a Windows Failover Cluster.
SMB file share that is presented by a Windows Failover
Cluster. The snapshot appears as if it is a managed
snapshot, but because SQL Server was not quiesced, it is
not a true managed snapshot.
To resolve this issue, ensure that scheduled snapshots are
set to times where there is less activity on the application
server.
It is possible for scheduled application-managed snapshots
to fail if the application server is overloaded and unable
to quiesce the application.
Creating application-managed snapshots of volumes that
are attached to VMware virtual machines (VM) as a Raw
RDM volumes and application-managed snapshot support.
14 Using the Application Aware Snapshot Manager