I’ve been working with Symantec’s new VMWare agent for Backup Exec 2010 for the past couple of months. We were excited to have differential backup of VMDK files through vSphere when they announced the new version of the software. In practice however this is a bit more involved than we bargained for.
There are a couple of things that keep us from using this tool to the full extent. First, we have noticed a dramatic decrease in backup speed from the Windows agent to the VMWare agent. The VM agent is about half as fast which impacts our backup windows. Secondly, if you have any VMDK files that are set to ‘independent’ that will cause the VM agent job to fail which hurts your differential backups down the line.
One of the biggest pain points of this agent is that we have regularly been seeing servers fail with the error ‘unable to quiesce’ or some similar variation. Many of the documents out there and support forums have information, but much of it is dated and references VCB which isn’t in use here as Backup Exec 2010 uses the new vSphere API to pull the backups.
I’ve found two quick and dirty ways to try first. First restart the VMTools service on the target Guest to be backed up. Secondly, restart the mgmt-vmware service on the ESX host that the target Guest is living on. More often than not restarting these services fixes the problem, at least temporarily.
I tired setting up a batch file on each of the Guests that would stop and restart the VMTools service. I then put this as a pre-job command in Backup Exec. For the life of me I could not get this to work. I kept getting the error ‘could not find the file’ in the results of the backup job. I believe that the issue is Backup Exec trying to run the command on the ESX server, and not the Windows Guest. Although its not pretty, I’ve scheduled this batch file from within Windows to run every morning. Hopefully this will help keep my backups on track so we can meet our SAS70 objectives.
5 thoughts on “BackupExec 2010 AVVI”
I was wondering if an uninstall/reinstall would work. Has it been stable? (have you had to do that more than once on a server?)
I would be interested to hear the other problems your having and if you have found any solutions yet?
We only use Symantec for OS partitions and backup data volumes using the normal Symantec OS agent. The speed decrease that the AVVI agent has shown makes it not as viable for data volumes. We’re looking really hard at using VMWare Data Recovery instead of the Symantec agent, but that has it’s own set of problems that I detailed in another post!
I’ve been having the same issue. The fix for me has been to remove the vmware tools and BE agent, then reinstall both. This is what symantec suggested, and it actually works.
Having lots of other problems, but that is another post 🙂
Very frustrating indeed. I’m trying to figure out an alternative way of doing backups.
I can’t believe this but I am having the exact same issues that tyou have! Slow AVVI backups, restarting VMware tools (I am using a PowerShell script), snapshot quiesce errors (so I have to shutdown some server to take a snapshot)…