high processor usage backing up w2008 r2 virtual machines Backup Exec 12.5

You're not by any chance using software encryption or compression as part of the job, are you?
Those can really suck up CPU cycles.

No, i haven´t any encription or compression, it happens when i try to explore the remote machine. My virtual machine is an hyper-v machine.  

I have finally access to the remote server, but i can only see shared folders, i can´t see all the resources to backup (drive c:, SQL, sharepoint), meanwhile i can see al this resources in the other remoter servers in my domain. I am connecting with an administrator account. Why this could be happening?.

Thanks.

 

I´ve seen that this high cpu usage begins when i start backup exec remote agent, if this is stopped i can access to the remote server, but it only shows shared resources.

First of all, if you applied SP4, are you sure you have pushed out the remote agent to this remote server again. It's not enough to apply SP4 on the Media server, the agent needs SP4 as well, by pushing it out.

As you can see from the Symantec article that was linked in the link you sent, Windows 2008 R2 has very limited support on Backup Exec 12.5. http://www.symantec.com/docs/TECH74523 says: "File System, System State, Shadow Copy Components Only" and "All other Backup Exec Options such as SQL, ADBO, IDR and Exchange ... are not supported".
There is only full support for SQL and Sharepoint on W2K8 R2 in Backup Exec 2010.
Additionally, if you have SP1 on W2K8R2, Symantec would have never tested or certified that SP, so even normal file and  system state backups may not work and possibly cause the symptoms you see.

Also the SharePoint 2010 is not supported by BE 12.5. So trying to launch a Remote Agent on a system with Sharepoint 2010 will also give non-certified and possibly non-expected results.

Your only option at this time seems Backup Exec 2010.

I´m quite stranged because this only happens on virtual servers, not in hardware servers. The symantec article is an very old article, it talks about sp2, and it´s date is "2009-01-31" so it´s highly outdated. I am copying the whole virtual machine with no problem, but it´s a great waste of resources.
My apologices for the delay, i´m now on holydays, so i don´t review so much this thread.  

The article is not outdated. 12.5 is just an old version of Backup Exec, therefore the articles for it are old.
BE 12.5, even with the lastest SP does not support 2008 R2 or SharePoint 2010. Not supported means things have not been coded, tested and certified with those softwares in mind. So you may find that some things work and others don't. Is Sharepoint 2010 for example installed on the physical machine where things work? If not, then Sharepoint may be causing the problems for Backup Exec.

I´ll test that when i return to work and I´ll keep you informed about the progress. Thanks for your help.

I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

I´m trying to test if the new version of symantec backup also have this problem, I´ll note here whats the result of my test as soon as i could test it.

Thanks.

Thanks for your help.