Exchange 2010 Multiple HT servers no Edge Server
We are looking at a situation where we will have 3 Exchange 2010 servers in a DAG. Each server will have multiple databases live on it. Each server is a HT.
All servers on a single domain. Multiple physicial locations. A single internet connection shared by all physical locations. The internet entry/exit also has one of the Exchange servers.
Do we need an edge server. If not where and how is the incoming/outgoing email routed.
We use Postini for email filtering. Where do i point this.
All servers on a single domain. Multiple physicial locations. A single internet connection shared by all physical locations. The internet entry/exit also has one of the Exchange servers.
Do we need an edge server. If not where and how is the incoming/outgoing email routed.
We use Postini for email filtering. Where do i point this.
ASKER
just to clarify
3 Exchange Servers each with different live databases, but all 3 have all the databases replicated as part of the DAG. So do i just choose on of the servers to act as the receiver for the entire organization. We have about 25 domain names that we collect email for. Around 200,000 incoming emails per month.
3 Exchange Servers each with different live databases, but all 3 have all the databases replicated as part of the DAG. So do i just choose on of the servers to act as the receiver for the entire organization. We have about 25 domain names that we collect email for. Around 200,000 incoming emails per month.
How is the current set up for inbound?
What i meant is if one of the datacenter or member server [where MX is pointed currently] goes down completely then you need to point the MX to another server.
if you have such a huge inbound emails per month - then definitely use multiple hub servers on each site. Hub servers will automatically balance the load among themselves.
Edge server can be subscribed on site basis.
What i meant is if one of the datacenter or member server [where MX is pointed currently] goes down completely then you need to point the MX to another server.
if you have such a huge inbound emails per month - then definitely use multiple hub servers on each site. Hub servers will automatically balance the load among themselves.
Edge server can be subscribed on site basis.
ASKER
Current setup does not have a single entry point as all domains are separate.
So you are saying that it doesn't matter if all the email hits the first HT server, it will just redirect email to the other relevant HT servers for delivery, just as Exchange 2003 did.
For example Server A receives all the email, but doesn't have the database which contains user B which is stored on Server B in a different location, it will simply forward the email to Server B for delivery.
Is that correct?
So you are saying that it doesn't matter if all the email hits the first HT server, it will just redirect email to the other relevant HT servers for delivery, just as Exchange 2003 did.
For example Server A receives all the email, but doesn't have the database which contains user B which is stored on Server B in a different location, it will simply forward the email to Server B for delivery.
Is that correct?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1. For inbound, you will have to point the MX record /or firewall rule to point to the server where you failover the database.
2. Make sure on receive connector Anonymous users are checked. on all HUB servers
3. There is no need for Edge server unless you need them.
4. Multiple Hubs on each site / or dedicated Hub server is much preferred.