Avamar: The VM image level backup is failing with snapshot quiesce error

The VM image backup is failing with snapshot quiesce error as shown below.
 

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.
avvcbimage Warning <43652>: Snapshot 'Avamar-1577539864a83b60c2d81fb0e6234f5e956e1bedb51d697138' creation for VM '[XXYY-XXYY01] testxyz2473_1/testxyz2473_1.vmx' task creation encountered a quiesce problem
avvcbimage Error <43650>: File level consistent snapshot quiesce failure.

When taking a manual snapshot, it is working well. 

There was a resource issue in the VM environment with disk I/O and memory usage. VMware vCenter version 6.5 and later introduced a new Volume Shadow-copy Services (VSS) feature which is called extended snapshots (CreateSnapshotEx_Task) superseding old feature "CreateSnapshot_Task."

A note from the VMware release notes is as below.
The release 6.5 includes support for additional Volume Shadow-copy Service (VSS) backup configurations.

1. The vssBackupType VSS_BT_COPY was previously used as the default for CreateSnapshot_Task but Now VSS_BT_FULL, VSS_BT_INCREMENTAL, VSS_BT_DIFFERENTIAL, and VSS_BT_LOG are available as well.
2. The vssBackupContext is introduced to enforce application or file system quiescing.
3. The timeout (default = 15 minutes) for quiescing VMs can be configured anywhere from 5 minutes to 4 hours.

To support these new features and configurations, the function CreateSnapshotEx_Task was added to the vSphere API, superseding CreateSnapshot_Task.

When the VM team tried for the extended snapshot manually using vCenter Managed Object Browser (MOB), it was failed due to VMware related issues. The backup issue got resolved after the VMware team fixed all VMware related issues including disk I/O issue on that VM and we were able to take snapshot both from MOB and Avamar backup.