Você está na página 1de 5

KNOWLEDGE BASE

Knowledge Base Article: 000190051


VM backups report Completed w/ Exception (000190051)
Version:2

Audience: Level 30 = Customers

Article Type: Break Fix

Last Published: Thu Aug 07 19:08:55 GMT 2014

Validation Status: Technically Approved

Summary: VM backups complete but show a completion w/ exception in the activity monitor. Analysis of logs report failure to quiesce the VM.

Issue:

VM backups complete but show in the activity monitor a completion w/ exception.


In this issue, the VM itself failed to create a 'quiesced snapshot'. Quiescing is a VMware function that attempts to 'quiet'
the VMs OS, application processes in order to create an 'application and file system consistent' state of the VM. This it
to ensures that the VM backup state is clean.
If the VM fails to quiesce, a 'crash-consistent' snapshot is created. This does not prevent a problem with backup or
restore of the VM, however, on the restore of a VM in a 'crash-consistent' state, it does not ensure the integrity of the
OS/Applications or Filesystem hosted on the VM itself. 'Crash-consistent' acts as if the VM was being started up after a
system crash. In essence, the VM backups will be dirty.
NOTE! Permanently disabling quiesce in the Avamar dataset as a workaround will always put your VM backups in a
'Crash-consistent' state. The preferred method to resolve quiesced snapshots issues is to contact VMware support
instead of the workarounds.

Environment:

VMware

Cause:

vCenter fails to quiesce the Virtual Machine when processing for backup.

This is not an Avamar backup


failure, but is a VMware failure where the VM failed to create a quiesced snapshot.
When this occurs, Avamar by default, requests vCenter to try a non-quiesced
snapshot for backup. The reported results is a backup with 'Completed w/
Exception'
Analysis of Log

2014-07-15 03:41:12 avvcbimage Info <9692>: a VM snapshot has been requested


2014-07-15 03:41:12 avvcbimage Info <14627>: Creating snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e', quieceFS=1 < vCenter creating a quiesced
snapshot
2014-07-15 03:41:12 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:14 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:16 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:18 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:20 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:22 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:25 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:27 avvcbimage Info <14631>: Snapshot

'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]


WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:29 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:31 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:33 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:35 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:37 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:39 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:41 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:43 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:45 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:47 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:49 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:51 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:53 avvcbimage Warning <16277>: vSphere Task failed (application quiesce): 'An error occurred while
quiescing the virtual machine. See the virtual machine's event log for details.'. < vCenter failing to create quiesced
snapshot
2014-07-15 03:41:53 avvcbimage Error <17775>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task creation encountered a quiesce problem
2014-07-15 03:41:53 avvcbimage Info <14627>: Creating snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e', quieceFS=0 < Non-quiesced snapshot
requested for backup
2014-07-15 03:41:53 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:55 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:57 avvcbimage Info <14631>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task still in progress, sleep for 2 sec
2014-07-15 03:41:59 avvcbimage Info <14632>: Snapshot
'Avamar-1405395672b3c388f47f8f560c38ec42f8aa3182cd6690ef5e' creation for VM '[CA SFV FarmA VMAX LUN13]
WNP2689/WNP2689.vmx' task completed, moref=snapshot-61231
.
2014-07-15 03:55:30 avtar Info <5163>: Backup complete, wrapping-up session with Server < Backup completed of
VM with non-quesced snapshot
2014-07-15 03:55:30 avtar Info <7238>: Stream complete: 4,972,751,872 bytes read from stream

2014-07-15 03:55:30 avtar Info <5156>: Backup #321 timestamp 2014-07-15


03:55:30, 0 files, 30.14 GB (0 files, 1.409 GB, 4.68% new)
*If the VM guest OS is Windows, there are known issues with Microsoft VSS
causing the VM to fail creating a quiesced snapshot. This can be verified by
checking the 'Windows Event Viewer' and correlating the times of the snapshot
failure to the VSS errors.
Cannot take a quiesced snapshot of Windows 2008 R2 virtual machine (1031298)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031298

Resolution:

Look at the Task and Events of the VM and investigate any reported quiesced snapshot failures and verify VMtools is
also current. Then test creating a manual quiesced snapshot to see if it continues to fail.
Refer to VMware support for further investigation into why the VM failed to quiesce the snapshot.

Testing a manual quiesced snapshot in VMware


First, verify the VM is able to create a quiesced snapshot. If VMware is unable to create a quiesced snapshot of the
host, then follow the steps below to create a dataset that disables the quiesce option.

Disabling Quiesced snapshot requests in Avamar for VMs that fail to quiesce

NOTE! The recommended resolution is to contact VMware to resolve 'quiescing' issues. If the VMs
guest OS cannot create, or support creating a quiesced snapshot, follow these steps to create a
dataset to disable the quiesced request and apply it to a new group with the clients in question.
Non-quiesced snapshots put your VM in a 'crash-consistent' state as described above.

a.
In Avamar Administrator, Select Tools, then Manage Datasets, select the data set related to your VMware image
backups click copy
b.
Rename the new dataset something like VMware image NoQ
c.
Edit this new dataset
d.
Select the options tab, select either Windows VMware Image as the plugin depending on what you are backing up
e.
Select the more button
f.
Put this in Enter Attribute - [avvcbimage]quiesce_fs
g.
Put this in Under Enter Attribute Value - false
h.
Click the + button

i.
Now choose Linux VMware Image as the plugin from the dropdown and repeat steps e-h
j.
Click OK, Then Ok again.
k.
Go to the Policy and double click your VM to Edit it. Select the dataset tab, select the new dataset. Click the
override box below the dataset dropdown to force this vm to use only this dataset.

Start an on-demand backup. Check the logs to confirm the quiescing flag is disabled. In the log, you should see:
quieceFS=0

Notes:

Cannot take a quiesced snapshot of Windows 2008 R2 virtual machine (1031298)


http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031298
Unable to take a quiesced VMware snapshot of a virtual machine (1009073)
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1009073
Snapshot quiescing fails on Linux guests after upgrading to ESXi and VMware Tools 5.1 (2038606)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2038606

Product:

Avamar, VMware

Você também pode gostar