In this video, we explore how send/receive connectors take advantage of redundancy in other Exchange services to create reliable sites to build a resilient organization.
- [Instructor] One of the goals across all of IT is to keep our network services as reliable as possible. Earlier in the course, we talked about service level agreements and the target of zero downtime, and while that may not always be possible, we're going to want to get as close as we can. The first step in achieving a high-availability environment is to make each each Active Directory site as reliable as possible. In many environments, the administrator may have never renamed the first site created by Active Directory.
But if your organization is larger, or destined to become larger, you're going to want to assign more helpful names to the sites as you create them. And, once again, because this can't be overemphasized, don't rename a site after you've installed things like a Microsoft Exchange organization or other environments in your domain and in your Active Directory site that use this name. The key to high-availability within a site is redundancy.
In the courses on Exchange mailbox databases and Client Access services, there is a lot of talk about having multiple servers and how they can cover for each other during an outage. This redundancy also improves fault tolerance of Transport services. This is the Exchange admin center where we saw the connectors that were created when we configured the Edge Transport Subscription. Notice the names of these Send connectors. Let me go ahead and expand this a little bit, so that we can see the entire name.
And you'll notice that each of these connectors are named for an Active Directory site to the internet or the internet to the Active Directory site. There is no mention of a specific Exchange server. I could select either one of these and look at the properties and scroll through all of the information shown, and I will never see reference to a specific mailbox database server. This means that the Transport services can take advantage of the clustering feature of database availability groups and the failover features of client proxy and redirection, all with no additional configuration.
This Edge Transport server is configured to interact with any existing mailbox database servers in this Active Directory site. If one mailbox server goes down, due to a failed power supply or planned server maintenance, the message can still be delivered to other mailbox database servers in the site. The Send connector is sending the request to all available mailbox servers anyway. If the mailbox servers were the only possible redundancy, we would still have a single point of failure in the Edge Transport server.
That limitation doesn't exist, however. You can install multiple servers as Edge Transport servers and create separate subscriptions for each server, just as we did earlier in the course. Once an Edge Transport server has been added to your Exchange organization, you can even add that subscription to the same EdgeSync Send connector. Using the same connector helps avoid sending the same email twice. Once you have two or more servers configured to send email, you can decide whether your network needs redundancy as well.
The separate Edge servers could have different paths to you border router or, in more extreme situations, connect to the internet through different internet providers. How much redundancy you need will vary based on your availability needs and the reliability of your network connections. Multiple Transport servers on a single connector will give you that fault tolerance at the Transport level.
- Planning and configuring transport and routing
- Understanding Safety Net
- Sending and receiving connectors
- Creating partner connectors
- High availability and site resilience
- Troubleshooting transport services
- Message security
- Filtering connections and recipients
- Spam confidence level thresholds
- Antivirus solutions