490 likes | 1.04k Views
Module 11: Managing Active Directory Replication. Overview. Introduction to Active Directory Replication Replication Components and Processes Replication Topology Using Sites to Optimize Active Directory Replication Implementing Sites to Manage Active Directory Replication
E N D
Overview • Introduction to Active Directory Replication • Replication Components and Processes • Replication Topology • Using Sites to Optimize Active Directory Replication • Implementing Sites to Manage Active Directory Replication • Monitoring Replication Traffic • Adjusting Replication • Troubleshooting Active Directory Replication • Best Practices
Multimaster Replication with a Loose Convergence DomainController B Replication Domain Controller A DomainController C Introduction to Active Directory Replication
Replication Components and Processes • How Replication Works • Replication Latency • Resolving Replication Conflicts • Optimizing Replication
DomainController B Replicated Update Replication Originating Update Domain Controller A Replicated Update DomainController C How Replication Works • Add • Modify • Move • Delete Active Directory Update
Default Replication Latency (Change Notification) = 5 minutes • When No Changes, Scheduled Replication = One Hour • Urgent Replication = Immediate Change Notification Replicated Update Change Notification DomainController B Replication Originating Update Domain Controller A Change Notification Replicated Update Domain Controller C Replication Latency
Domain Controller A Domain Controller B Originating Update Originating Update Stamp Stamp Conflict Conflict Version Number Timestamp Server GUID Stamp ConflictsCanBeDueto: • Attribute Value • Adding/Moving Under a Deleted Container Object or the Deletion of a Container Object • Sibling Name Resolving Replication Conflicts
DomainController B GUID USN GUID USN Up-To-Dateness Vector Update Replicated Update Originating Update Domain Controller A Update GUID USN DomainController C Replicated Update Optimizing Replication
Replication Topology • Directory Partitions • What Is Replication Topology? • Global Catalog and Replication of Partitions • Automatic Replication Topology Generation • Using Connection Objects
Directory Partitions Schema Contains definitions and rules for creating and manipulating all objects and attributes Forest Configuration Contains information about Active Directory structure contoso.msft Holds information about all domain-specific objects created in Active Directory Domain Active Directory Database Directory Partitions
A2 A4 A2 A4 A1 A3 A1 A3 B2 B3 B1 Domain Controllers from the Same Domains Domain Controllers from Different Domains Domain A Topology Schema/Configuration Topology Domain A Topology Domain B Topology Schema/Configuration Topology What Is Replication Topology?
A2 A4 Partial Directory Partition Replica A1 A3 B2 B3 Schema Configuration B1 contoso.msft Holds read only copy of all domain directory partitions namerica.contoso.msft Global Catalog Server Domain A Topology Domain B Topology Schema/Configuration Topology Global Catalog and Replication of Partitions
KCC KCC KCC KCC A2 A2 KCC KCC A1 A1 A3 A3 Automatic Replication Topology Generation KCC KCC KCC KCC A4 A4 A8 A8 A6 A7 A5 A7 A5 A6 KCC KCC KCC KCC KCC KCC Domain Topology Schema/Configuration Topology Automatic Replication Topology Generation
Using Connection Objects • Connection Objects Are Created: Automatically or Manually • Connection Objects Are Created on Each Domain Controller • Use Active Directory Sites and Services to Manually Create, Delete, and Adjust Connection Objects • Use the Replicate Now Option to Manually Initiate Replication Connection Object Connection Object Domain Controller A1 Domain Controller A2
Using Sites to Optimize Active Directory Replication • What Are Sites? • Replication Within Sites • Replication Between Sites • Replication Protocols
AD Sites and Services Console Window Help Active View Name Type Tree Default-First-Site-Name Inter-Site Transports Redmond-Site Subnets Site Inter-Site Transport Container Site Subnets Container Active Directory Sites and Services Sites Default-First-Site-Name Servers DENVER NTDS Settings Inter-Site Transports Redmond-Site Subnets What Are Sites? • The First Site Is Set Up Automatically, and Is Called Default-First-Site-Name • Sites Can Consist of Zero, One, or More Subnets • Sites Are Used to Control Replication Traffic and Logon Traffic • Sites Contain Server Objects and Are Associated with IP Subnet Objects
DomainController A Site IP Subnet Replication IP Subnet Domain Controller B Replication Within Sites Replication Within Sites: • Occurs Between Domain Controllers in the Same Site • Assumes Fast and Highly Reliable Network Links • Does Not Compress Replication Traffic • Uses a Change Notification Mechanism
Replication Between Sites ISTG Bridgehead Server Replication Between Sites: • Occurs on a Manually Defined Schedule • Is Designed to Optimize Bandwidth • One or More Replicas in Each Site Act As Bridgeheads Replication IP Subnet IP Subnet Site Replication Replication Bridgehead Server, ISTG IP Subnet IP Subnet Site
Domain Controller A Domain Controller B Replication Protocols RPC or SMTP • RPC for Replication Within and Between Sites • SMTP for Replication Between Sites Replication Protocols
Implementing Sites to Manage Active Directory Replication • Creating Sites and Subnets • Creating and Configuring Site Links • Creating a Site Link Bridge
AD Sites and Services Console Window Help Active View Name Type Tree Default-First-Site-Name Inter-Site Transports Redmond-Site Subnets Site Inter-Site Transport Container Site Subnets Container Active Directory Sites and Services Sites Default-First-Site-Name Servers DENVER NTDS Settings IP Subnet Inter-Site Transports Redmond-Site Subnets IP Subnet IP Subnet Redmond-Site Domain Controller B Default-First-Site-Name Domain Controller A Creating Sites and Subnets
Domain Controller A IP Subnet IP Subnet Site Site Link Domain Controller B IP Subnet IP Subnet Site Creating and Configuring Site Links Site Links Are Defined by: • Transport • Member sites • Cost • Schedule • Replication Interval
Site Y IP Subnet IP Subnet Site Link XY, Cost 3 Site Link YZ, Cost 4 Site Link Bridge XYZ, Cost 7 IP Subnet IP Subnet IP Subnet IP Subnet Site X Site Z Creating a Site Link Bridge
Monitoring Replication Traffic • What Is Replication Monitor? • Using Replication Monitor to Monitor Replication Traffic • Using Repadmin to Monitor Replication Traffic
With Replication Monitor You Can: What Is Replication Monitor? • Display the Replicating Partner • Display Each USN Value, the Number of Failed Attempts, Reason, and Flags • Poll the Server at an Administrator-Defined Interval • Monitor the Count of Failed Replication Attempts • Show Which Objects Have Not Yet Replicated • Synchronize Between Just Two Domain Controllers • Trigger the KCC into Recalculating the Replication Topology
Active Directory Replication Monitor File Edit Action View Help Update Automatically Monitored Servers: Monitored Servers Log C:\Documents and Settings\Administrator.LONDON2154\My Documents\lond... Default-First-Site-Name Status as of: 12/13/1999 6:00:41 PM london2154 CN=Schema,CN=Conf CN=Schema,CN=Conf >>Direct Replication Partner Data<< Server is current through Property Update USN: 2803 The last replication attempt was successful. This took place at: 12/13/1999 5:49:17 PM (local) Default-First-Site-N CN=Configuration,DC= Default-First-Site-Na DC=nwtraders2154,DC Default-First-Site-Na Status as of: 12/14/1999 8:15:59 AM atlanta2154 CN=Schema,CN=Conf >>Direct Replication Partner Data<< Server is current through Property Update USN: 2955 Replication Failure: Changes have not been successfully replicated from ATLANTA2154 for 12 attempt(s). Replication Failure: The reason is: The RPC server is unavailable. Replication Failure: The last replication attempt was 12/14/1999 7:50:22 AM (local). Default-First-Site-Na CN=Configuration,DC= Default-First-Site-Na DC=nwtraders2154,DC Default-First-Site-Na 12/14/1999 8:18 AM Using Replication Monitor to Monitor Replication Traffic
C:\WINNT\System32\cmd.exe C:\>repadmin /showreps denver.domain2.nwtraders.msft Using Repadmin to Monitor Replication Traffic
Modify the Replication Behavior by: Adjusting Replication • Creating Additional Connection Objects to: • Reduce the number of hops between domain controllers • Bypass the failed server or servers • Configuring Preferred Bridgehead Servers
Error Error Error Error Error Replication Does Not Finish Replication Is Slow Replication Increases Network Traffic Replication Clients Are Receiving a Slow Response KCC Was Unable to Complete the Topology Troubleshooting Active Directory Replication
Place At Least One DNS Server in Each Site Schedule Site Links for Times When Network Traffic Is Slow Place at Least One Domain Controller in Every Site Best Practices
Review • Introduction to Active Directory Replication • Replication Components and Processes • Replication Topology • Using Sites to Optimize Active Directory Replication • Implementing Sites to Manage Active Directory Replication • Monitoring Replication Traffic • Adjusting Replication • Troubleshooting Active Directory Replication • Best Practices