Described below are the set of procedures which can be used to configure reproducing of data on the Active Directory Domain on servers, which have Windows Server of 2016.
For the purpose of configuring the replication, DFS Namespaces and DFS Replication will be installed on the dual servers enabled with Windows Server 2016.
SELECTION OF SERVER ROLES
DFS namespace will then be created by using the DFS management console. It is up to your need that, either you use stand-alone namespace or domain-based namespace.
Afterwards, a new folder will be made in the new namespace. It should be ensured that the new directory is reachable along the network by the UNC path ‘whateverthenameyouchose’.
Between 2 Servers: Configuration of DFS Replication
At this stage it is possible for you to configure the DFS replication. With the help of DFS replication, synchronization of directories with copied folders between the 2 servers is possible. 2 servers which are the component of DFS replication group. Both servers are connected via DFS linkage.
Remote Differential Compression Algorithm RDC is used to replicate the changes. Those components of the files are copied which are altered by you. Asynchronous DFS replication is performed, in colloquial terms at a certain point in time due to which sources may be inconsistent.
It is of paramount nature that difference should be maintained in FRS- File Replication Service and DFSR- Distributed File System Replication. DFSR was featured in Windows Server 2008, which assisted in altering the while in a way that differential compression was used in the process and transferred over the network as it didn’t assist in transferring the entire file. Unlikely, in FRS the whole file is replicated.
DFS brings advantage when WAN link is relied upon while using remote folders among remote branches for the copying. It automatically resumes the copying of data when the connection between the replication partners are reestablished after in a state of stagnation.
A group of servers forming a linkage to enable replications is called a replication group.
Following are the DFS replication system requirements :
- All the servers of the replication group must have DFS replication installed.
- Replication group servers should be present in the in a single AD Forest.
- At least Windows Server 2003 R2 for Active Directory Forest Schema version and simultaneously, for domain functional level at least Windows Server 2008.
- Location of replicated directories must be alongside the volumes with NTFS file system. FAT, Cluster Shared Volumes and ReFS are not compatible.
- Either the replicated directories should be exempted from the antivirus exemptions or snure the compatibility of the antivirus with DFS mechanism.
Prior to configuring replication, a network shared folder will be created in the 2nd DFS server. For which, DFS Management console will be opened, then select the desire namespace and from the context menu select the Add Folder Target.
Enter the name of the shared folder and then click OK button.
Afterwards, click ‘Yes’ when you are prompted for the replication group.
In the next phase you will be required to verify the name of the replication group and the directory which is to be replicated.
To avoid any nuisance paths to the shared folders on the servers should be checked.
Primary member node will be selected which will be used for both, initial storage and replication of data.
Full mesh is opted as a replication technology by default, through which all changes on a single node are automatically and with immediate effect are copied to all others.
It remains to adjust the schedule and bandwidth which will then be used to replicate data. Check the settings and hit Create.
A message will appear as:
Now at this stage the configuration of DFS and data replication on it is completed.
For pilot testing, try creating a new file in the shared folder on any one of the member server. Replication time lag will depend on the type of bandwidth of the communication bridge.