Backup Exec Become Very slow rate job after Windows Update

Here you can see, the difference between Jobs, the mailbox jobs normally run over 2600/3000 MB/s, now between 500/550 Mb/s

...where is Backup Exec installed? On 1 of the hosts, or a stand-alone server? Does the Exchange server get updated at the same time as the host? are there any restart requirements on the servers after being updated?

Thanks!

Backup Exec is installed in the phisical server that host the Hyper-V servers,  the Exchange Server doesn´t get the windows update at the same time, i configure to do not install update automaticly.

The Phisical server is configure to don´t install automaticly, i acumulated three o four month of updates, and them apply it.

At this moment i update the Exchange Server too, to see if the problem solved but nothing yet.

This morning i Unnistall-Reinstall again Backup Exec, after update TAPE drivers with symantec drivers again, but the problem continue. the tape drive is clean.

I have noticed this issue with BE20110sp3 combined with (backups of) servers with databases (SQL, Exchange) and/or Active Directory, usually in combination with deduplication. After a long analysis, logging and such, I noticed that the BE server had rather long wait periods, in which it would wait for responses from the client. Some further googling led me to the culprit: Microsoft Forefront Endpoint Protection. You would expect them to know how to get the exclusions right on their own anti virus software, but forget it. The on-access scan engine slows backups to a crawl. 

The following article finally put me on the right path:

https://kc.mcafee.com/corporate/index?page=content&id=KB66909&actp=search&viewlocale=en_US&searchid=1318380358919

Solution

Add the following exclusions to your antivirus. I found that it works for FEP, but it might well also work for Sophos, NOD32, Norman, Panda, F-Secure, Kaspersky, Symantec and others. 

Add Low Risk Processes policies and exclusions for Backup Exec.

Step 1 - Add exclusions to AV on your Backup Exec Server

1. Open your antivirus scanner and go to the Exclusions part of the settings.
2. Add exclusions for the following processes:
   
   C:\Program Files\Symantec\Backup Exec\beremote.exe 
   C:\Program Files\Symantec\Backup Exec\beserver.exe 
   C:\Program Files\Symantec\Backup Exec\bengine.exe 
   C:\Program Files\Symantec\Backup Exec\benetns.exe  
   C:\Program Files\Symantec\Backup Exec\pvlsvr.exe 
   C:\Program Files\Symantec\Backup Exec\BkUpexec.exe
   
   NOTE: Change the path as appropriate, depending on which root volume the Media Server or Remote Agent has been installed to.

Step 2 - Exclude Backup Exec paths from scanning

1. Open your antivirus scanner and add the following path to the Exclusions (including subfolders):
   
   C:\Program Files\Symantec\Backup Exec\
   C:\Program Files (x86)\Symantec\Backup Exec\

When configuring your settings, keep your eye open for other settings that could complement the exclusions. For example, McAfee has an option to ignore files that are opened for backup.

Step 3 - Add exclusions based on the used product

Active Directory, Exchange, SQL - they all have their own required exclusions. Configure these exclusions using the following articles:

https://kc.mcafee.com/corporate/index?page=content&id=KB66909&actp=search&viewlocale=en_US&searchid=1318380358919

Once you've set these, there's a good chance things will improve drastically.

Symantec, you would do well to make a dedicated article explaining what exclusions to add - not just for your own products, but also other products that BackupExec has to work with. 

Roger are you backing up exchange data using agent for exchange or are you backing up data using hyper v agent I.e vhds...

...this query is over 5 months old and effectively dead. No response from the OP.

Thanks!

Oh thanks I didnt see that...I am logged on my cell phone so its shows me as post unread in latest one..thanks craig...I would have kept on opening it again again thinking would get a reply...