Unable to connect to Exchange 2007 mailbox following full backup

Currently we are having an issue where after a Full backup we have some, but not all, Outlook clients who are unable to  connect to our Exchange 2007 environment.  They will receive an "Unable to connect to Exchange Server" error message or some clients will be forced to work offline.

To allow them to reconnect to Exchange 2007 I have to Stop and then Start the Clustered Mailbox Server using the Clustered Mailbox Server wizard in Exchange 2007.  After that Exchange works fine until the next Full backup when the issue occurs all over again.  

The issue does not affect any one storage group or database.  The issue does not affect the same clients every time and has no affect on OWA access at all.

The following is our Exchange Environment:

      -Two CCR clustered Mailbox servers running Exchange 2007 SP1
      -One CAS/Hub Transport server running Exchange 2007 SP1
      -Our clients are Outlook 2000, Outlook 2003, and Outlook 2007 and all three are affected
      -We've used both NTbackup and BackupExec 12 to backup the databases and both cause the issue.
      -Full backups are the only backups that are causing the issues, Incremental or Differential backups have no issues.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Whenever I see weird behaviour like this it often is down to antivirus software. Try uninstalling it.

I assume this is running on Windows 2003. Apply the latest VSS rollup package if you haven't already. http://support.microsoft.com/kb/940349. VSS is used extensively in backups of Exchange.

Check http://www.experts-exchange.com/Software/Internet_Email/Email/Email_Clients/Q_22613416.html


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
i would do a integrity check on the database.

PaulRKruegerAuthor Commented:
Thanks. We'll give them a shot and let you know.
PaulRKruegerAuthor Commented:
We made two changes (sorry, I know that doesn't help) and our problem has been solved.
We disabled the TCP Chimney feature on the server using the Netsh.exe tool (http://support.microsoft.com/?id=945977) as linked from http://www.experts-exchange.com/Software/Internet_Email/Email/Email_Clients/Q_22613416.html.
We also started backing up from the passive node.
As a result, we have improved our network backup speed by 4 hours (a 30% reduction) and did not have any issues this morning. I'm guessing this is primarily due to disabling the TCP Chimney feature.
Thanks a bunch!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.