HP StoreVirtual 4000 Release Note page 19

1. Open the service property page.
2. Select logon type.
3. Change the logon type from Local Service to the account that has administrative
credentials.
An error occurs when an application-managed snapshot is created during NIC failover on an
application server
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:
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.
Intermediate VMware snapshots are not deleted when a timeout error occurs
The process of creating an application-managed snapshot for a VMware volume involves creating
snapshots for all virtual machines on the volume, creating the SAN/iQ snapshot, and deleting
the intermediate virtual machine snapshots. If a timeout error occurs when the snapshot is being
created (this can occur if a virtual machine is busy), the snapshot will still be created, but the
intermediate virtual machine snapshots will not be deleted.
You can determine if this issue occurred by reviewing the event log. Error messages such as
Failed to create application-managed snapshotor Failed to create
snapshots for one or more VMs will appear. Also, the Application Aware Snapshot
Manager will not indicate that snapshots were deleted. To resolve the issue, you must delete the
intermediate snapshots manually.
When creating an application-managed snapshot of a cluster shared volume, an error message
displays on the passive server
If you have a Hyper-V configuration with cluster shared volumes, you may see the following error
when an application aware managed snapshot is taken on one of the cluster shared volumes.
Cluster Shared Volume 'Volume3' ('CSV3') is no longer directly
accessible from this cluster node. I/O access will be redirected to
the storage device over the network through the node that owns the
volume. This may result in degraded performance. If redirected access
is turned on for this volume, please turn it off. If redirected access
is turned off, please troubleshoot this node's connectivity to the
storage device and I/O will resume to a healthy state once connectivity
to the storage device is reestablished.
The error indicates that the volume is no longer accessible, but the volume is in a passive state
on that particular node (and active on the other node). The snapshot is taken successfully. You
can ignore this message.
The CLI command GETSERVERCAPABILITIES fails on Windows Server Core
Microsoft does not support .NET on Windows Server Core. With the release of version 9.5, which
included .NET, the Application Aware Snapshot Manager is no longer supported on Windows
2008 Server Core or Windows 2008 Server R2 Core. The Application Aware Snapshot Manager
documentation (online help and deployment guide) incorrectly list support and installation
instructions for Server Core. This information will be removed in a future release.
The Application Aware Snapshot Manager is causing VSS error messages on the Windows cluster
server that does not own the volume
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:
Workarounds 19