11-06-2010 05:08 PM
I'm working with a Symantec rep to give them extended logging for my AVVI backups, but since I changed the debug log level in the registry my backups have all gotten stuck "updating catalogs".
Because of this, for whatever reason the AVVI agent isn't letting go of the vmdk via the vSphere API, because my VM's are stuck with a "reload managed entity" message in my vSphere client, the machines "appear" powered off and nothing can be edited/rebooted/etc.
Normally my VMWare backup job runs about 5 hours, so far I'm 12+ hours in.. most of it being "updating catalogs". GRT is enabled for Exchange and SQL Server.
11-06-2010 09:13 PM
This should work - http://www.symantec.com/docs/TECH129826
11-07-2010 07:09 AM
Sorry how does that help? I'm not moving my BE server. I'm trying to figure out why it's running a 19+ hour catalog update after a backup job.
11-07-2010 07:39 AM
My apologies, I pasted the wrong link.
Here is the correct one - http://www.symantec.com/docs/TECH128144
11-07-2010 08:20 AM
I'm not sure how that'll work. Once I remove the VMWare tools I'll no longer have a network card to re-install the Symantec Agent. So if it's suggesting the Agent needs to get loaded before VMWare tools I have no way to do that.
11-07-2010 06:26 PM
The document is asking you to uninstall and re-install both the Vmware tools and the BE remote agent. Which one gets installed first is not important.
11-07-2010 06:57 PM
Alright, as long as order isn't specific I guess I can do it.
Though this is a new problem, my first few VMWare backups worked with the exception of a GRT issue I am trying to work out with the Symantec support folks.