11.0 HP StoreVirtual Storage User Guide (AX696-96275, December 2013)

Troubleshooting snapshots
Table 58 Troubleshooting snapshot issues
DescriptionIssue
When taking managed snapshots via the CMC or the CLI on a volume that contains
a large number of virtual machines, some virtual machines may fail due a failure to
Snapshots fail with error
“Cannot create a
quiesce. The culprit could either be the VMware tools synch driver or MS VSS. The
quiesced snapshot
failure is not reported in the CMC as the CMC is not currently logging VM quiesce
because the snapshot
failures. For more information, see the VMware KB article: http://kb.vmware.com/
operation exceeded the
selfservice/microsites/search.do?language=en_US&cmd=displayKC&
externalId=1018194
time limit for holding
off I/O in the frozen
virtual machine.”
Virtual machines that are converted from a template to a virtual machine still may
have information in the configuration file indicating that it was once a template. This
Snapshots fail with error "An
attempt was made to
is a known issue highlighted in the VMware KB article: http://kb.vmware.com/
write to a read-only
selfservice/microsites/search.do?language=en_US&cmd=displayKC&
externalId=1004538
file.
vim.fault.FileNotWritable.”
If VMware vCenter is running in
a non-domain environment, the
• Scenario 1—If vCenter is not joined to a domain, that CIM server service account
must be changed to an account with administrative privileges.
CIM server account must be
modified.
• Scenario 2—If vCenter is not joined to a domain, and is configured as in Scenario
1, and is then later joined to a domain, the CIM server account changes must be
undone. Otherwise you will see an error such as the following:
A general error occurred that is not covered by a more
specific error code. "Error retrieving volume list from
application server at 10.31.100.100: ILED: An exception of
type Exception with message InitializeSecurityContext()
failed!!! VCENTER5\VCENTER5$, -2146893042 occurred while
performing InitializeClient operation."
To create a point-in-time snapshot, click Continue.
To cancel the process without creating new snapshots, click
Cancel.
The following workarounds apply to all supported versions of Microsoft Windows.
The Windows server computer name and full computer name must be the same for
the workarounds to work. Do one of the following:
• Create a domain and join the management computer to the domain
• Change the Pegasus server service logon:
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.
The error is expected because the suspended VM has not changed since the last
snapshot. These situations can arise when either a snapshot of a suspended VM is
There are situations where a
snapshot of a suspended virtual
taken via vCenter prior to a LeftHand OS managed snapshot, or if a LeftHand OSmachine already exists in
snapshot of a volume holding the suspended virtual machine is mounted and another
snapshot is taken.
vCenter, when a managed
snapshot of the volume is taken.
In such situations, the following
error message appears on the
volume status page and in
vCenter, "Snapshot not
taken since the state
of the virtual machine
has not changed since
the last snapshot
operation."
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
An error occurs when an
application-managed snapshot
178 Using snapshots