While we wait for a VMWARE solution (no laughing) we opted to disable the VM VSS Snapshot Provider service on systems on which it was installed. That was the only non-disruptive solution we could find, since it forces Avamar to instead use the Microsoft VSS provider. This seems to work just fine, though you should definately test your restores.

I have been having the same problem since upgrading to ESX 5.1 - did you ever come to a resolution?  the work around is quite unacceptable.

haha, can't help it. That's what we did too but I was hoping that there was a better solution that I had missed somewhere.  Thanks for the response!

I think you are correct on the quiesce

after the 5.1 upgrade I had to add this to my dataset

[avvcbimage]quiesce_fs=false

that is   a  v  v  c  b  i  m  a  g  e

I would strongly recommend adding the quiesce_fs flag to the dataset as J.H. describes above rather than setting it using the avvcbimage.cmd flag file. The flag files always override the dataset. What if the default behaviour changes in a later release? It's a lot easier to change the dataset than it is to update or re-deploy every proxy.

Also, there is no need to reset or re-register the proxy (or any client) after changing the flag files. Flag files are loaded and processed at backup runtime.

you need login to your avamar proxy

cd /usr/local/avamarclient/var

edit your avvcbimage.cmd

add --quiesce_fs=false

save

then cd ../var-proxy-1

edit your avvcbimage.cmd again

add --quiesce_fs=false

save

then reset proxy and re-register it

Upgrade your grids to 6.1SP1

I am on 6.1.1-87 and still had to use the quiesce.