Lesson 6: Troubleshooting Replication

This lesson describes problems you may encounter that relate to replication. Most problems involving poor directory information can be remedied with Active Directory Sites And Services. Problems with directory information might mean that:

  • New directory information is not distributed in a timely fashion
  • Service requests are not handled in a timely fashion

This lesson also describes how to check replication topology.

After this lesson, you will be able to

  • Troubleshoot replication

Estimated lesson time: 5 minutes

Troubleshooting Replication

Ineffective replication can result in declining Active Directory performance, which might include new users not being recognized. Ineffective replication or request handling primarily results in out-of-date directory information or unavailable domain controllers. Each problem or cause has one or more possible solutions. Replication troubleshooting scenarios are discussed in Table 17.4.

Table 17.4 Replication Troubleshooting Scenarios

Symptom: Replication of directory information has stopped
Cause Solution
The sites containing the clients and domain controllers are not connected by site links to domain controllers in other sites in the network. This results in a failure of directory information to be exchanged between sites. Create a site link from the current site to a site that is connected to the rest of the sites in the network.
Symptom: Replication has slowed but not stopped
Cause Solution
Although all sites are connected by site links, your inter-site replication structure is not as complete as it might be. Directory information is replicated to all domain controllers if they are all connected by site links, but this is not optimal. If there are site links but no site link bridges, changes made to domain controllers may take an unacceptably long time to be distributed to other domain controllers that are not closely linked. Make sure Active Directory has been configured properly. To span the multiple site links that need more efficient replication, consider creating a site link bridge or consider bridging all site links.
Symptom: Replication has slowed but not stopped
Cause Solution
The current network resources are insufficient to handle the amount of replication traffic. This can affect services unrelated to Active Directory, because the exchange of directory information is consuming an inordinate amount of network resources. Increase the proportion of available network resources relative to directory traffic. Decrease the frequency of the replication schedule. Configure site link costs. To achieve network connections with more bandwidth, create site links or site link bridges.
Directory information changed at domain controllers in one site is not being updated in domain controllers in other sites in a timely fashion because inter-site replication is scheduled too infrequently. Increase the frequency of replication. If the replication is occurring over a site link bridge, check which site link is restricting replication. Increase the time range during which replication can occur or the frequency of replication within the time frame for that site link.
Clients are having to request authentication, information, and services from a domain controller with a low-bandwidth connection. This may result in clients receiving a slow response for authentication, directory information, or other services. Check if there is a site that will better serve the client's subnet. If a client who is experiencing poor service is isolated from domain controllers, consider creating another site with its own domain controller that will include the client. Install a connection with more bandwidth.

Checking Replication Topology

Active Directory runs a process that considers the cost of inter-site connections, checks if any previously available domain controllers are no longer available, checks if new domain controllers have been added, and then uses this information to add or remove connection objects to create an efficient replication topology. This process does not affect manually created connection objects.

Follow these steps to check the replication topology:

  1. Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Sites And Services.
  2. In the Active Directory Sites And Services console tree, double-click the server that you want to use to check replication topology.
  3. Right-click NTDS Settings, point to All Tasks, and then click Check Replication Topology

Lesson Summary

In this lesson you examined some replication problems you may encounter and possible solutions to these problems.

MCSE Training Kit(c) Microsoft Windows 2000 Accelerated 2000
MCSE Training Kit(c) Microsoft Windows 2000 Accelerated 2000
Year: 2004
Pages: 244

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net