When we use Windows NT4.0 to plan and design our enterprise network system, we should design the corresponding domain model according to the specific situation of enterprise construction, such as single domain, multi-master domain or single master domain model. We can use these kinds of domain models to plan the enterprise network environment and realize the organization, management and control of the enterprise network. When we go to implement such network planning, we often have to make planning designs that meet actual needs according to the organizational structure within the enterprise. If it is a large group of companies, we often need to design a department or a department with a relatively large work relationship as a domain to facilitate organization and management. This poses a very difficult problem for our designers. If such a domain is composed of slow connections through computers geographically distributed in different locations, the information synchronization between the PDC and the BDC through the slow connection will be Occupy a large amount of network traffic, affecting the overall performance of the network, in the face of such a problem, we can only do nothing, there is no control method. An engineer once joked: "Whenever he designs a network system, he will first advise the company president to move the departments in each domain model to a building. Many Novell system engineers will have similarities. The troubles of
When I came into contact with Windows 2000, the powerful features and user-friendly design of Active Directory make our future network planning and design more convenient and flexible. The concept of Site in Win2000's Active Directory is proposed. And implementation, to provide a powerful tool for managing and controlling the synchronization of information between DCs, thus effectively solving the problem we have previously proposed that we have been helpless.
The so-called Site, refers to the physical comparison A collection of computers with good line connections that enable faster communication rates, generally referred to as a LAN. Sites typically communicate over a slow connection. It is visible that Site is the actual physical distribution of computers on the network. An objective reflection.
With the concept of Site, we can put computers in a domain According to the geographical distribution, it is distributed among several sites. In a site, Active Directory uses the replication component and KCC to form a two-way ring of replication synchronization between DCs. Each DC has two replication partners. Forming complete information synchronization. When a directory database in a DC changes, it waits for a period of time to send a change notification to its replication partner. After the replication partner receives the change notification, it copies the directory from the changed DC. The change information of the data. The same replication partner also sends the change information to its replication partner to synchronize the DCs in the entire site. Due to the fast and reliable network connection in the Site, the replication data between the DCs in the Site It is not compressed, which increases the bandwidth required for copying information, but reduces the burden of processing data of DC. In general, the information of DC in the site is synchronized by RPC protocol, so that data replication is fast and uniform, so that DC is between Maintains high data consistency.
Between sites is generally through slow connections, only limited availability Wide and unreasonable data transmission. In order not to affect other data communication on the slow connection line and ensure the reliability of directory replication between DCs, the DC replication between the sites does not use the change notification method of DC replication in the site, but The method of copy scheduling is adopted. A schedule and time interval can be set between the sites. The schedule determines when the copy is allowed to occur, and the time interval specifies how often the DC checks the data change within the time allowed for copying. Set the schedule for DC replication synchronization between sites when the network traffic is low (such as midnight). At this time, the network is not crowded and relatively reliable. Moreover, the directory replication of the DC between the sites uses a compression method, and the copy information can be compressed to 10% to 15%, which can effectively optimize the network bandwidth.
It can be seen that by properly planning the Site on Active Directory, we can effectively control the synchronization of DCs in Active Directory, optimize network bandwidth, and improve network performance. Because in Windows 2000 Active Directory, synchronization between DCs involves not only synchronization of large amounts of data between DCs in a domain, but also small amounts of information between DCs in different domains. When we use Site to implement the replication layout between DCs in Active Directory, we can help us to achieve this by means of two settings: Site link and Site link Bridge, thus forming a more reasonable, more efficient and more reliable DC in Active Directory. Copy the layout to maximize our network system.