7 Dec 10 12:47
We have recently had our Brightstor database become corrupt (i know... what a surprise), and were not able to get any backups to even start. I went through and performed a dbdefrag, dbfix, and keybuild on all of the databases. Now, it is able to log into the DB, find the media, and perform the backup. However, when it gets to backing up Exchange, we receive a lot of errors even though it backs everything up.
Upon starting the Exchange backup portion, we receive this error in the Job Log:
Failed to send data to the client agent. (EC=-1)
dbaexchis Version 11.1 Build 3200 12-13-2003 Microsoft Exchange Server 2K/up
Converting connection protocol to named pipes due to connection error
At the same time, these are the errors that appear in the Universal Agent log file on the Exchange Server:
12/06/10 9:46:55 Set Stop Event.
12/06/10 9:46:55 [UDP] Failed to initialize communication object. RC = 1d012740, Error = 10048
12/06/10 9:46:56 Universal Agent awaiting connection.
12/06/10 9:47:21 Set Stop Event.
12/06/10 9:47:21 Unmap Done.
12/06/10 9:47:24 Set Stop Event.
12/06/10 9:47:24 [UDP] Failed to initialize communication object. RC = 1d012740, Error = 10048
12/06/10 9:47:25 Universal Agent awaiting connection.
A quick search for these errors gave me some information on increasing the send/receive timeout values to 3600, which i did complete. However, the problem still remains.
I have noticed that the Backup Agent Admin console on the Exchange server has a list of 10 connections that never get cleared out. Some of them completed 100%, and some didn't. I'm not sure if this has anything to do with the problem. I have included a screenshot of this also, as i want to provide as much information as possible. This thing is driving me insane! :)
Also, the version we are using is r11.1 (Build 3200).
Thanks in advance for any feedback,