Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 592
  • Last Modified:

How to make RUS fault tolerant in a single Exchange Server 2003 environment? and dns....

I noticed that "Recipient Update Services" (RUS) is only configured to use 1 of my Domain Controllers. If that DC goes down, Exchange will not automatically connect to another DC in the domain(will it?). I see that in http://support.microsoft.com/default.aspx?scid=kb;en-us;319065 I can add and configure another Domain Controller here.  WOULD IT HURT MY DOMAIN, MY AD REPLICATION, OR ANYTHING ELSE, if I configure my only 2 DC's to both be Recipient Update servers? I'm assuming that if one went down Exchange knows to continue using the next avaiable server and use it (so the domain stays fully operational)  - is this correct? PLEASE ELABORATE AND/OR GIVE TECH REFERENCES ON THE WEB.

See info below for what I already have know. IS THERE ANYTHING ELSE I can do to make a single Exchange server more resilient in the event of a DC or DNS server being powered down/taken offline/crash? I'm currently reviewing MS's "Exchange 2003 Disaster Recovery Planning Guide." http://www.microsoft.com/downloads/details.aspx?FamilyId=784BBEA2-28DD-409A-8368-F9914E993B28&displaylang=en
_____________________________

Redundacy for Recipient Update Services in Exchange: How to Add a New Recipient Update Service

To add a new Recipient Update Service: 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Expand the Recipients object, and then click the Recipient Update Services container.
3. Right-click Recipient Update Services, point to New, and then click Recipient Update Service.  
4. Click Browse next to "Domain" to display a list of domains in your forest.
5. Click the domain that you want this Recipient Update Service to update, and then click OK.  
6. Confirm that the domain that you selected is displayed in the New Object - Recipient Update Service dialog box, and then click Next.
7. Click Browse, click the Exchange server on which you want this instance of the Recipient Update Service to run, and then click OK.
8. Click Next.
9. Click Finish.
10. Right-click the new Recipient Update Service object that you created, click Properties, configure the Update interval setting, and then click OK.

Note When you are creating a Recipient Update Service, you cannot select the domain controller. You can only select the domain that you want the new Recipient Update Service to be associated with. After you have finished creating the Recipient Update Service, you can edit the properties of the Recipient Update Service and select the domain controller that you want.



Redundancy for DNS in Exchange 2003:
When I took down one of my DC's for maintenance the other day and my Exchange server stopped functioning correctly - couldn't resolve external DNS to send mail. I thought since the server NIC had two internal DNS servers listed (the one taken down plus another DC/DNS server) it would automatically forward all requests to the secondary DNS server listed in the NIC config.

I then found about the setting (in Exchange) that lets you tell Exchange directly) what DNS servers to use. See below

Directly setting DNS Servers in Exchange System Manager
1. Start Exchange System Manager.
2. Expand Your_Organization (where Your_Organization is the name of your Exchange organization).
3. Expand Servers, and then expand Your_Server (where Your_Server is the name of your server).
4. Expand Protocols, and then expand SMTP.
5. Right-click Your_SMTP_Virtual_Server (where Your_SMTP_Virtual_Server is the name of your SMTP virtual server), and then click Properties.
6. Click the Delivery tab, and then click Advanced.
7. Click Configure next to Configure external DNS Servers.
8. Click Add, type the IP address of your internal\external DNS servers, and then click OK
 
0
mrmmills
Asked:
mrmmills
  • 2
1 Solution
 
bakerm00Commented:
many large environments will use multiple RUS for a single domain within a forest should the domains own replication topology have excessive time delay.

therefore configuring both as RUS is possible..  however you only have two DC's?? of which one is only a GC because you know of infrastructure master requirement.
so this brings up DSAccess and exchange requirements for a GC.  exchange gets config info from a DC but The RUS communicates with a global catalog server via the GC LDAP Port 3268 for GAL and is services.

I would recommend that you review the following KB on how to trouble shoot the RUS with the app log. http://support.microsoft.com/?kbid=822794.

as for redundancy - my view is how much money do you have to fulfil all possible avenues.
however - for your immediate needs you can reference:
http://support.microsoft.com/?kbid=322856 - How to configure DNS to use with Exchange Server

and the Exchange High Availability Guide - Making exchange fault tolerant.
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3HighAvGuide/6115570d-9f61-47a0-bd73-419a89380fe3.mspx
0
 
mrmmillsAuthor Commented:
Your correct in that I forgot to explain our topology - kinda essential to get a correct answer for my question.

less than 50 user environment.
2 DC's (one holding all FSMO roles),
each DC is an internal DNS server
Exchange 2003 server is not acting as a DNS server
I have an SMTP gateway (in front of the Exch server) blocking spam at the perimeter.

From your answer all I can gather is that you believe that I could configure my other DC to be a secondary RUS server and it should not have an impact on my tiny domain. But for the second DC to be able to be a RUS server I must configure it to also be a Global Catalog server. In short your saying to make both my DC's Global Catalog servers and have my single Exchange server configured to use both of the,

KB272552 makes it sound like anyone who set up Exchange 2003 and did not append it's default settings for the RUS server (and set up multiple GC's) is in jeopardy of not having any Exchange redundancy measures in place in the event of a GC DC failure.
0
 
mrmmillsAuthor Commented:
Looks like I have found the answer per a single MS KB Article.

http://support.microsoft.com/default.aspx?scid=kb;en-us;875427

Titled:  " Global catalog server placement and ratios in an Exchange 2000 Server organization or in an Exchange Server 2003 organization."

 “For scalability and for fault tolerance, we recommend that you configure at least two global catalog servers in each Active Directory site. If a site spans multiple domains, we recommend that you configure a global catalog for each domain where Exchange 2000 Server computers or Exchange Server 2003 computers and clients reside.”

From this I gather we need two GC's and for the (Recipient Udpate Service) RUS service to have soem fault tolerance.
0

Featured Post

Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now