11-02-2010 06:34 AM
So for 4 Clients we upgraded from SP1 to SP2 and rebooted. All were done prior to the next recovery point set creation. For 2 of the Servers everything went 100%, for the other 2, both have just hung at 94% and the VProSvc.exe is pegged on the CPU taking 25% (1 core pegged). I stopped one servers service manually. Then restarted and reopened the application, it showed in the History as created, I was able to use recovery point browser and verifiy it as well. Although when attempting to run the next incremental it continued from the previous set not the new base???? This is a big issue and I am not sure what to do, would a call to support be worth it?
Solved! Go to Solution.
01-14-2011 09:29 AM
Yes this was solved following an article to clear out job histories and starting from scratch.
11-02-2010 01:51 PM
Yes, definetly. Give Symantec guys a chance to have a look, it might be a bug.
11-11-2010 12:21 AM
Have you had a chance to file a case ?
12-15-2010 12:23 PM
Any updates here ?
01-13-2011 12:47 AM
Any updates here ?
01-14-2011 09:29 AM
Yes this was solved following an article to clear out job histories and starting from scratch.