AZ-800 Administering Windows Server Hybrid Core Infrastructure Exam

Manage Intersite Replication Topology and Scheduling

Intersite replication is a core part of AD DS that keeps directory data consistent across multiple locations. Intersite replication uses the network to copy changes between domain controllers in different sites. By managing replication properly, you can reduce network traffic and make sure updates happen on time. Effective replication planning also enhances disaster recovery and load balancing. Ultimately, this ensures that users and applications always see the latest directory information.

To set up replication, start by configuring site links and link bridges. Site links define the network paths between sites, while link bridges connect separate site links to allow indirect replication routes. You also need to set replication intervals to control how often changes travel across these links. Key steps include:

• Defining site link costs to choose the fastest or most reliable path
• Creating link bridges to connect multiple site links
• Scheduling replication intervals based on bandwidth and business hours

Optimizing replication involves fine-tuning these settings to match your network environment. Adjust replication intervals to balance between timely updates and bandwidth usage. Use site link cost values so that critical links get priority over slower ones. Implement link bridges when direct connections aren’t available, ensuring consistent routing. These steps help you maintain a healthy replication topology that adapts to changing network conditions.

Validating replication health is essential to catch issues early. Tools like repadmin give you detailed status reports on pending changes and replication failures. Checking AD DS event logs helps you spot errors or warnings that need attention. Regular validation tasks include:

• Running repadmin /showrepl to view replication partners and failures
• Reviewing Directory Service logs in Event Viewer for error codes
• Confirming that changes replicate within your targeted intervals

Common replication problems include latency, USN rollback, and lingering objects. High latency means updates take too long to propagate, so you may need to increase replication frequency or lower site link costs. A USN rollback can occur if a domain controller is restored incorrectly; remediating it often requires rejoining the domain controller. Lingering objects are stale directory entries that persist when replication breaks down; running repadmin /removelingeringobjects can clean them up. By monitoring and fixing these issues, you ensure reliable directory consistency across all sites.

Conclusion

In summary, managing intersite replication topology and scheduling involves defining site links, link bridges, and replication intervals to optimize AD DS traffic. You use tools like repadmin and AD DS event logs to validate replication health and catch problems early. Common issues such as latency, USN rollback, and lingering objects require targeted remediation steps. By applying these practices, you’ll maintain consistent and efficient replication across on-premises and Azure-hosted domain controllers, ensuring your directory remains up to date and reliable.