Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

trying to create redundancy for email servers

Status
Not open for further replies.

jlh1

MIS
Mar 26, 2001
65
US
I’m trying to create redundancy for email servers.

We have 2 exchange 2010 servers, one in the corporate office and one offsite.

We have created a DAG to fail over the database and this works fine.

We use an internal email server as our smart host that exchange sends and receives email through.

I have created a duplicate smart host that I have installed in the offsite environment.

My next step is to create a second MX record with a higher weight then the primary MX record so that there is a second path for the email server to receive email.

The next step I have question on.

I will add the second smart host IP to the Network tab, Smart host on the organization send connector.

Also I will add the second smart host IP number to the receive connectors on the two exchange servers.

I think this will give redundant paths to send and receive emails.

In the event that of the internet connection goes down at the corporate site how would I ensure that the send connector will only use the offsite smart host.

Both smart hosts will be in the DMZ of the network. The exchange servers will still be able to see them but won’t know that one of them has lost it internet connection.

Would I have to create second send connectors with the offsite smart host IP and manually enable them when needed?


Thanks
jlh1
 
You shouldn't really need to use smart hosts for that. For one, smart hosts make it more difficult to troubleshoot mail delivery to external recipients.

One MX record should point to the receive connector on one server, and the other MX record should point to the receive connector on the other server. Make sure your messaging hygiene is identical on both sides. Use two send connectors and DNS delivery for outbound delivery. Problem solved.

Stop by the new Tek-Tips group at LinkedIn. Come say hi, look for a job, have some fun.
Pat Richard MVP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top