ByteCafeSupport
asked on
ShadowProtect backups of Exchange server slow over time
We have a Dell PowerEdge T610 with 2x 2.4 Ghz quad core processors and 16 GB of RAM running Exchange 2010 SP1 for about 40 mailboxes on Windows Server 2008 R2. We are using ShadowProtect 3.3.0.16 to back this server up. When server starts up, backups run fine, but initialization time gets longer the longer the server is up. This time since server was rebooted, backup initialization was at 25 minutes after 5 days, 90 minutes after 9 days, and now on day 11, initialization took almost 3 hours on the last backup. The task status on ShadowProtect server shows initializing during this time. Once initialization is done, backups still only take a few seconds like normal. Might this be a VSS issue and is there something I can do besides reboot it regularly?
There was a time where trying to work on server desktop was very slow and system memory usage was at 93%. With information from http://eightwone.com/2011/04/06/limiting-exchange-2010-sp1-database-cache/, set msExchESEParamCacheSizeMin
There are no errors or warnings related to backup in Application or System logs.
There was a time where trying to work on server desktop was very slow and system memory usage was at 93%. With information from http://eightwone.com/2011/04/06/limiting-exchange-2010-sp1-database-cache/, set msExchESEParamCacheSizeMin
There are no errors or warnings related to backup in Application or System logs.
ASKER
Current version of volsnap.sys is 6.1.7600.16385 dated 7/13/2009, which is older than the first hotfix. I'll get hotfixes installed and report back.
Yes, let us know how it goes.
ASKER
While I had the opportunity, I installed Windows Server 2008 R2 SP1 instead. Checked versions of files referenced in hotfixes and all are now newer. Will see how it goes. Also applying Exchange update rollup 3-v3 for Exchange Server 2010 Service Pack 1 (KB2529939).
ASKER
Update - Server up 38 hours, backup initialization time is currently just over 4 minutes.First backup after last boot was about 45 seconds. Will check back on Monday.
ASKER
Update - After almost 6 days, initialization time is up to 28 minutes. After Windows Server 2008 R2 SP1, should I still look at hotfixes posted?
Sorry for delayed response.
These are not required now as you have already updated Windows Server 2008 R2 SP1.
These are not required now as you have already updated Windows Server 2008 R2 SP1.
ASKER
After almost 13 full days, initialization time is up to 3 hours 5 minutes. Anything I can check on the Exchange load for this? In addition to Exchange, it is a DC/GC and is temporarliy hosting Trend Micro Security Server (which uses IIS) until the next server is replaced.
ASKER
Going to work with Microsoft support on this.
ASKER
Update - We are using Trend Micro Worry-Free Business Security Advanced 7 (Security Server is also this server) and after running for 9 days this time and backup times getting longer, I exited Trend Micro agent today and everything came back up to speed. Seems problem is with Trend Micro agent at this point.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It's good that you have found the app causing issue. Lets hope this patch works for you.
ASKER
System has been up 9 days and backup time is now just over 1 minute.
1. High load on Exchange server and it's delayed response to VSS writers to freeze and flush data to disk. When you reboot the server, the load is not that much and response is quicker. Later, as number of days increases, it's getting worse to respond.
2. VSS writers files are old. You can try installing below mentioned hotfixes.
Windows 2008 R2
http://support.microsoft.com/kb/975688
http://support.microsoft.com/kb/975921
http://support.microsoft.com/kb/976099
http://support.microsoft.com/kb/977096
http://support.microsoft.com/kb/980082/EN-US
Note: It is recommended to reboot the server after every patch installation.