KB ID 0000763 Dtd 08/02/13
ProblemYesterday morning, I walked into the office, the boss told me a client’s Exchange was running slowly and they had had a Veeam backup fail. I know this client well enough to know if it was something simple he would have fixed it himself, so while my laptop booted I armed myself with a coffee. By the time I got on remotely, Ben on the help desk had also got online and was giving me the heads up on what the NAble proactive system had flagged up during the night, one drive was practically full, and it had filled up quickly. I rang the client who told me the drive in question was the transaction log volume for Exchange, (which with failing backups would make sense). Also he had added 1500 iPad clients to the network in the last few weeks, and the transaction logs were going up by about 20GB a day. Without a good backup to flush the logs things had steadily got worse. I connected to the Veeam backup server and this was the error.
Solution1. OK thatâ€™s a huge error, but essentially it’s complaining about the VSS writer on the Exchange server. Log onto the Exchange server, drop to command line and issue the following command;
3. Check again to make sure you are back up.
4. Note: We are backing up using Veeam, make sure there is no instance of the Symantec Backup Exec Remote Agent for Exchange, if it’s there remove it.
5. Finally, Iâ€™ve got over 120GB of transaction logs to contend with, for the problem mail store, Iâ€™m going to enable circular logging to free up some room. (Note: You can disable this again once you have a decent backup if you wish).
6. At this point I rebooted both the Exchange server and the Veeam Backup server it then performed a backup of the Exchange server without error.
We had an issue with this again this week and the above resolution did not work. In the end we had to do the following;
1. Exchange shouldn’t be more than 20 sec. So please kindly inspect closely the following article:Â http://www.veeam.com/kb1680
2. Please make sure that Exchange server isn’t running on a snapshot.
3. Troubleshoot the VSS service. i.e.
Related Articles, References, Credits, or External Links
Thanks to Steve Morrison and Dimitri from Veeam