XADM: Directory Replication Takes Too Long

Last reviewed: September 23, 1997
Article ID: Q148381

The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SUMMARY

This article explains why, depending on the Directory Replication topology, the time required to replicate directory changes to all parts of a Microsoft Exchange Organization may be several days.

MORE INFORMATION

Consider the following two Directory Replication topologies.

Topology A: Hub

Site X  <------->  Site W   <------> Site Z
                      ^
                      |
                      |
                      V
                    Site Y

Topology B: Cascade

Site W <----> Site X <---> Site Y <-----> Site Z

In each of the above topologies, the arrows indicate a directory replication connector. Assume that each connector is scheduled to replicate at one time during the day.

In Topology A, if a new mailbox is added to Site X, the maximum delay for that directory entry to be propagated to all the other Sites would be 2 days (one day for each directory replication connector hop).

In Topology B, if a new mailbox was added to Site W, the maximum delay for that directory entry to reach all the other sites (specifically Site Z) would be 3 days.

Hence, the time required to propagate directory changes to all sites in an Exchange Organization depends on the replication schedule as well as the number of hops involved and the number of hops depends on the Directory Replication Topology.


Additional query words: faq
Keywords : XADM kbenv
Version : 4.0 5.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.