10.5 HP StoreVirtual Storage User Guide (AX696-96269, March 2013)

Troubleshooting snapshots
Table 56 Troubleshooting snapshot issues
DescriptionIssue
When taking managed snapshots via the CMC or the CLI
on a volume that contains a large number of virtual
Snapshots fail with error “Cannot create a quiesced
snapshot because the snapshot operation
machines, some virtual machines may fail due a failure to
exceeded the time limit for holding off
I/O in the frozen virtual machine.”
quiesce. The culprit could either be the VMware 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
Virtual machines that are converted from a template to a
virtual machine still may have information in the
Snapshots fail with error "An attempt was made to
write to a read-only file.
vim.fault.FileNotWritable.”
configuration file indicating that it was once a template.
This is a known issue highlighted in the VMware KB article:
http://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1004538
If VMware vCenter is running in a non-domain environment,
the CIM server account must be modified.
• Scenario 1—If vCenter is not joined to a domain, that
CIM server service account must be changed to an
account with administrative privileges.
• 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
There are situations where a snapshot of a suspended
virtual machine already exists in vCenter, when a managed
when either a snapshot of a suspended VM is taken viasnapshot of the volume is taken. In such situations, the
vCenter prior to a LeftHand OS managed snapshot, or iffollowing error message appears on the volume status page
a LeftHand OS snapshot of a volume holding the suspended
virtual machine is mounted and another snapshot is taken.
and in vCenter, "Snapshot not taken since the
state of the virtual machine has not
changed since the last snapshot operation."
Troubleshooting snapshots 181