When Avamar 7.1 backs up a VMware guest at an image level, by default the Avamar software asks VMware to create a quiesced snapshot. If VMware Tools are installed on the guest, VMware will attempt to create a VSS snapshot on the guest before creating the VMware snapshot. The exact process used to create a quiesced snapshot is independent of Avamar.

I don't believe the VMware tools will truncate SQL logs by default when taking a VSS snapshot but a quick Google search tells me that there are third party tools that will do this. I would recommend checking with the system administrators to see if any of these tools have been installed on the guest.

Alternatively, you could work with VMware support to determine why this may be happening.

If all else fails, you could disable quiesced snapshots as described in the following thread:

Error 10007 when backing up VMs

Please be aware that disabling quiescing will make your VM backups crash-consistent rather than application consistent.

I have to go with Ian On this.

I have a LOT of vm's with sql on them, but we do NOT use the Avamar SQL plug in to back them up.

the DBA dose the native SQL backup to local disk or to DataDomain.

I have NOT had any issues with the users telling me that the logs are being truncated

Ian hi, just like Symm snapshots and freezing the lun for writes, do you recommend a method as below for SQL data protection inside VMs (if not production, at the lease for QA/dev/staging environments)

1) run a script to fludh DB transactions to disk

2) after 5-10 minutes run the snapshot backups of VMs

I can't give you any specific recommendation but an approach like that seems reasonable. I've heard it's possible to create scripts for VM Tools to run during snapshots but I don't have any experience with this.

One thing to note is with Avamar 7.4 and vSphere 6.5 you can truncate logs from a VMWare image backup.  In vSphere 6.5 VMware added a lot of VSS improvements and Avamar 7.4 takes advantage of it.