How To Setup Dfs Replication In Windows Server 2012

The Distributed File System on Windows Server 2012 R2 consists of two components, Distributed File System Namespaces and Distributed File System Replication. In this blog postal service we volition review Distributed File System Replication, and and then look at how to install and configure DFS-R on Microsoft Windows Server 2012 R2.

Navigation

1. Distributed File Arrangement Replication (DFS-R)
   1.1 Installing DFS-R
   1.2 Creating a Replication Group
   ane.iii Configuration Options in DFS-R
      i.3.1 Editing Replication Schedules and Bandwidth
      i.iii.2 Managing Connections
      1.3.iii Configuring properties of replication group members
      1.3.iv Configuring properties of replicated folders
      1.iii.5 Replication topologies

.

1. Distributed File System Replication (DFS-R)

DFS Replication is an efficient, multiple-master replication engine that you lot can use to go along folders synchronized between servers. DFS replication tin can occur across multiple sites and servers that live within the same Active Directory wood. DFS Replication uses remote differential pinch (RDC) to locate and replicate simply the inverse information blocks of a file, instead of replicating a file in its entirety. This reduces the amount of network traffic generated past DFS-R.

.

1.i Installing DFS-R

1.1.1 You can install the DFS-R role by using the Add together Roles And Features Magician in Server Manager.
1.1.two Select the Role-Based Or Feature-Based Installation option
1.1.three On the Select Server Roles page, select DFS Replication

one.1.4 Click Add Features to install management tools as well
1.1.five On the Select features page, select Remote Differential Compression

1.1.6 Click Adjacent, and so click on Install

.

ane.ii Creating a Replication Group

A replication grouping enables you to configure folder replication so that folder replicas remain synchronized across servers.

1.2.1 Right-click the Replication node in DFS Direction, select New Replication Group

1.ii.two Select Multipurpose replication group, click Next

Multipurpose replication group is used in most use cases. If you are going to configure replication of folders betwixt ii or more servers, where the same data will reside on all servers that are members of the replication group, then you volition select this selection.

Replication group for data drove is only used if you want to transfer data from a branch server to a hub server, and so use backup software to support the data on the hub server.

1.2.iii Proper name the replication group, click Side by side

1.2.4 Add members to the replication grouping, click Next

1.2.v Select a Topology, click Side by side

1.two.six Select the replication schedule and bandwidth, click Next

1.2.7 Select the primary fellow member, click Next

This will exist the server that will be authoritative during initial replication. Which means that its content volition exist replicated to other members. If there is a conflict, this server will win. Mail the initial replication, in that location is no such matter equally a primary/master member. Simply the first replication will need a primary/master member to ensure that all folders have the same starting indicate.

one.2.eight Select the folders on the primary member, you lot want to exist replicated to the other members of the replication group

You tin likewise edit the name of the replicated folders and NTFS permissions of the replicated folders on this page.

Click Next when you are ready to go on

1.2.9 On the next folio(s) you lot get to define local path and membership status of the replicated folder(s) on the secondary members. Click Edit

1.2.10 You are given following options

Membership status Disabled: The replicated folder will not exist replicated to this member.
Membership status Enabled: The replicated binder volition exist replicated to this fellow member.

Local path of folder: Configure the path the replicated folder will be stored at on this member.
Make the selected replicated folder on this member read-but: This ways that this member will only receive data, and not transmit it, considering information technology will not exist possible for users to manually suspend data to the replicated folder stored on this member.

1.2.11 Dorsum on the previous folio, click Next
one.two.12 Click Create

one.2.thirteen Click Close

.

1.3 Configuration options in DFS-R

.

ane.3.one Editing Replication Schedules and Bandwidth

The replication schedule defines when replication can occur for the replicated folders that are function of the replication group. And how much bandwidth replication tin eat.

ane.3.ane.1 To edit the schedule for an entire grouping right-click the replication group → Edit Replication Group Schedule

i.3.ane.ii To edit the schedule and bandwidth for a specific connexion between 2 members, click on the Connections tab of the Replication Group. So right-click a connection and enter its backdrop sheet. On the Schedule tab of the properties sheet, you can ascertain a custom schedule for this specific connectedness.

.

ane.3.2 Managing Connections

1.3.2.1 On the Connections tab of the replication group, you will find all transport and receive connections between all members of the replication group. Past right-clicking a connection, y'all will have these options on the context menu,

Disable lets you disable replication for this specific connectedness.
Replicate Now starts replication for the connectedness. The receiving member will start receiving data.
Properties volition allow y'all enter the backdrop sail, where you can enable/disable replication and remote differential compression for the connectedness.

i.3.ii.2 If you lot want to create a new connection between members of the replication group, then right-click the replication group and select New Connection. This will bring up the new connectedness dialog box, where you lot can define sending and receiving members. You lot tin too create a custom schedule for the connectedness, and create a second connexion in the contrary direction automatically.

.

1.3.3 Configuring properties of replication group members

1.three.3.i On the Memberships tab of the replication grouping, you lot will observe the different folders that are being replicated between members. Past correct-clicking a binder, you will have these options on the context menu,

Delete Fellow member deletes the member from that replicated binder
Make read-only makes the folder read-only on that item member. Meaning no files tin can be written on it by users, and the replication will in practice be one-fashion, as this member volition simply receive data from the other members considering data on it volition never be changed by users.

Disable lets you disable replication for this particular folder on a specific member. Afterwards a disabled member is enabled, the member must consummate an initial replication of the replicated folder. Initial replication will cause about one KB of data to exist transferred for each file or folder in the replicated folder, and any updated or new files present on the fellow member will be moved to the DfsrPrivate\PreExisting folder on the member and will be replaced with authoritative files from another member. If all members are disabled, then the offset fellow member enabled becomes the principal/authoritative member.

Backdrop will allow you lot enter the properties canvass,

⇒ Full general tab gives information only,

⇒ Replicated folder tab too simply gives information,

⇒ Staging tab lets you lot ascertain the path and size of the staging folder.

By default the staging folder is located under the local path of the replicated folder. The staging folder is used to shop files before sending and receiving them. When remote differential compression is enabled, calculations are performed on files in the staging binder to decide which blocks need to exist replicated. The receiving folder uses its own staging folder to build the modified file.

You can better performance and reduce the likelihood of replication declining past optimizing the size of the staging folder. Microsoft recommends that at a minimum the staging binder quota should be at least the size of the 32 largest files in the replicated folder, and for all-time possible functioning on the file server, the size of the staging folder quota should be set as close equally possible to the size of the replicated folder and it should be located on a different physical deejay than the replicated binder.

The disk space allocated to the staging folder will not be reserved, but merely be consumed when needed.

⇒ Advanced tab

On this tab you can ascertain the size of the Disharmonize and Deleted folder. You can too enable/disable moving deleted files to this folder. When the same file is edited on different replicas, the user who performs the most recent save operation has the changes saved and replicated beyond servers. If files with the same proper noun and path are created on 2 different replicas, earlier replication occurs, so the file that was created first is kept and replicated across servers. The losing files are moved to the conflict and deleted folder.

.

1.3.4 Configuring properties of replicated folders

1.3.4.ane On the Replicated Folders tab of the replication group, you volition notice the dissimilar folders that are being replicated between members. By right-clicking a binder, y'all will take these options on the context menu,

Share and Publish in Namespace option lets you share the replicated folder, or share and publish it in a namespace.

Properties will let you lot enter the properties sheet,

File filter lets you lot ascertain which files will not be replicated. Past default the following file types will not be replicated,

~*, Microsoft Part temporary files
*.bak, fill-in files
*.tmp, temporary files

Subfolder filter lets you ascertain which folders will not exist replicated.

.

one.3.five Replication topologies

Replication topology determines how members of a replication group replicate with each other. At that place are two different replication topologies yous tin can choose between.

Hub And Spoke

This topology requires iii or more members. Key servers are designated every bit hub servers, while branch servers are designated as spoke servers. Spoke servers replicate with hub servers, only practise not replicate straight with other spoke servers.

Full Mesh

All servers replicate directly with each other.

Source: https://shabaztech.com/installing-and-configuring-dfs-r-on-windows-server-2012-r2/

Posted by: davisdogried.blogspot.com

Share this post