Dealing with routing group master failure

Please let others know how useful this tip is via the rating scale at the end of it. Do you have a useful Exchange or Outlook tip, timesaver or workaround to share? Submit it to our tip contest and you could win a prize.

Bridgehead servers facilitate communications between Exchange Server routing groups by hosting the routing group connectors that tie multiple routing groups together. Although bridgehead servers are definitely important, there is another routing group component that is often overlooked -- the routing group master.

When you create a routing group, Exchange designates the first server in the routing group as the routing group master. Each routing group has its own master, which is responsible for maintaining link state information within that routing group. Technically, the routing group master role can be assigned to a bridgehead server -- but it is typically assigned to a different server.

The routing group master's job is to maintain link state information sent to it by bridgehead servers. Let's say that the WAN connection fails for a routing group connector that exists between two routing groups. Initially, only the bridgehead server is aware of the failure. It contacts the routing group master to inform it of the link state failure. (It will also inform the routing group master if the link comes back up or if a new routing group connector is created.)

Before I go on, you might be wondering why Exchange servers get link state information from a routing group master instead of the bridgehead server. Exchange is designed this way, because multiple servers within a routing group can potentially function as bridgeheads. Rather than r

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Exchange Server Administration Tips Fixing DPM 2007 inconsistent replica errors in Exchange Server Using Mobile Device Manager 2008 server roles in Exchange 2007 An introduction to the DSAccess service in Exchange Server 2007 Exchange Performance Monitor tracks domain controller communication Exchange Server 2007 SP2 reinstates built-in backup capabilities Three Performance Monitors counters to use in Exchange Server 2007 Scheduling multiple Performance Monitor alerts in Exchange Server 2007 Which ActiveSync authentication method is best for your mobile device? Configure Performance Monitor alerts for Exchange Server 2007 Disable ActiveSync in bulk with Exchange Management Shell commands Microsoft Exchange Server Sync and Replication Issues Relocating Outlook email messages on a hosted Exchange 2007 server Pushing a public calendar out from a private Exchange account Synchronized Exchange mobile device showing deleted appointment Working with continuous replication in Exchange Server 2007 Troubleshooting Apple iPhone and Exchange Server integration issues How continuous replication works in Exchange Server 2007 Prevent SSL-related synchronization errors on emulated mobile devices Troubleshoot Windows Mobile device emulator synchronization errors Share and sync calendar data between two Exchange Server sites Troubleshoot Outlook 2007 error 0X8004010F on Exchange Server 2007 Microsoft Exchange Server Sync and Replication Issues Research

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

isk having link state information scattered across multiple servers, Microsoft decided to make the routing group master responsible for storing link state information for the entire routing group.

Since the routing group master is responsible for propagating link state information across the entire routing group, if it fails, any other services (mailboxes, public folders, etc.) running on that server will also fail. So, it's obviously important to get it back online as quickly as possible.

This brings up two more questions though. First, how do you know which server is acting as the routing group master? Second, what do you do if you can't bring the failed server back online?

To determine which server is acting as the routing group master:

This answers the second question too. If you can't revive a dead routing group master, you can simply designate another server in the routing group to act as a routing group master by right clicking on the server and selecting the "Set as Master" command.

About the author: has served as the CIO for a nationwide chain of hospitals and was once in charge of IT security for Fort Knox. As a freelance technical writer he has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies. You can visit Brien's personal Web site at http://www.brienposey.com.

Reference Center: Exchange replication and synchronization tips and resources

---

Rate this Tip To rate tips, you must be a member of SearchExchange.com. Register now to start rating these tips. Log in if you are already a member. Submit a Tip DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.