We have a 2 node DAG/CAS setup that uses loadbalancers for client access. We did a test shutdown of our primary site the other day and everything went well apart from the outbound SMTP.
What I did was setup 2 send connectors, connector A and connector B. These 2 send connectors both go to our smarthost at Messagelabs. Connector A has a cost of 1 and is assigned to server A. Connector B has a cost of 100 and is assigned to server B. My thinking was that should server A fail it will automatically failover to connector B. Unfortunately it seems that Exchange has no way of doing this. Obviously if I manually disable connector A it all starts working on connector B. So how do I achieve automatic failover on SMTP outbound? Surely people don't all do this manually?
Are you in the migration process of your Exchange to Exchange Online?
Be aware of customized solutions developed on the transport role on your old Exchange server. They might not be convertible to Exchange Online!
This article involves a discussion about issues people have when it comes to Client Access in relating to Load Balancing in an Exchange environment which we had ourselves, along with a solution I found to the problem.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment.
The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online)
The email signat…