Avamar: Error occurs when saving snapshots for VMware Virtual Machine backups
Summary: Avamar image-level backups for VMware virtual machines (VM) fail with a snapshot creation error. The failure occurs during snapshot creation even when using non-quiesced backups and can also prevent manual snapshots and Storage vMotion. ...
Symptoms
During VMware virtual machine (VM) image-level backups, the jobs fail and the following symptoms may be observed:
-
Avamar backup logs contain snapshot errors, such as:
avvcbimage Info <0000>: Snapshot 'Avamar-xxxxxxxxxxxxxxxxxx' creation for VM '[<Datastore_Name>] VM_Name/VM_Name.vmx' task still in progress, sleep for 3 sec
avvcbimage Error <16279>: vSphere Task failed (snapshot error=45): 'fault.GenericVmConfigFault.summary'.
avvcbimage Error <14635>: Snapshot 'Avamar-xxxxxxxxxxxxxxxxxx' creation for VM '[<Datastore_Name>] VM_Name/VM_Name.vmx' task creation encountered a problem.
-
vCenter displays the following task error for the VM:
An error occurred while taking a snapshot:msg.snapshot.error-QUIESCINGERROR - The issue persists when running non-quiesced backups using the
--quiesce_fs=falseflag. - Manual snapshot creation in vCenter fails for the affected VM.
- Storage vMotion operations fail for the same VM.
- The VM's
vmware.logfile records datastore free-space errors, for example:vcpu-0| I120: DISKLIB-VMFS : "/vmfs/volumes/xxxxxxxxxxxxxxxx/VM_Name/VM_Name-flat.vmdk" : closed. | vcpu-0| W110: File_GetFreeSpace: Couldn't statfs /vmfs/volumes/xxxxxxxxxxxxxxxx/VM_Name | vcpu-0| I120: SNAPSHOT: SnapshotCheckSpaceAndSnapshotNum: Error getting the free space on the storage disk -
The datastore shows sufficient free space when verified through vCenter and the storage array.
Cause
This issue occurs when vCenter Server or the ESXi host incorrectly reports datastore free-space information for a specific datastore. As a result, snapshot creation fails despite sufficient available storage.
Resolution
Rescan Storage on the ESXi Host or Datacenter
Rescan the storage to refresh datastore information and correct the reported free-space values.
-
Follow the VMware documentation that corresponds to the deployed VMware vSphere version:
Performing a rescan of the storage on an ESXi host (External Link) -
After the rescan completes:
- Retry creating a snapshot manually in vCenter.
- Re-run the Avamar image-level backup.
- vMotion operations may not be available.
- Certain datastore operations may be temporarily restricted.
- Always consult the VMware administrator before performing a storage rescan in a production environment.