Académique Documents
Professionnel Documents
Culture Documents
Summary: VM backups complete but show a completion w/ exception in the activity monitor. Analysis of logs report failure to quiesce the VM.
Issue:
Environment:
VMware
Cause:
vCenter fails to quiesce the Virtual Machine when processing for backup.
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.
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:
Product:
Avamar, VMware