For the past day and a half I’ve been receiving the above error in my Avamar v18.104.22.168 server and in VMware vCentre every time I tried to backup certain virtual machines via the Windows VMware Image plugin. I searched all over the web and couldn’t find anything related to the problems I was experiencing and tried loads of different ideas and looked for similarities between the virtual machines that were failing but found nothing.
As is the case sometimes, once you ask for help you stumble across the solution on your own. As soon as I posted a discussion on the EMC Community Network about my problem and asked for some help/guidance on the problem and then found a posting on the ECN about a problem with the error code I was getting in Avamar Administrator (id 10013). The environment I’m running the backups in hasn’t been upgraded to version 4.1 yet so it did fit the criteria’s for the problem and fourth possible root cause and solution in the list was spot on and fixed the problem for me.
I was planning to write the exact steps I followed but while searching the internet I noticed one of the Varrow bloggers Hugh Griffin had beaten me to it and posted about the error and the same steps I followed(the second workaround).So due to my hating people who repeat my solutions to problems on their blogs with minimal credit I felt it was only fair to give him the credit so here is his blog posting of the solution “Avamar 5.0 VMware Image Backup Error” (Personally I have to put two dashes instead of one like Hugh did for it to work so it only works for me if i do –x22=8192)