A Dfs Folder Can Have a Maximum of Two Targets

Windows Server 2008 R2 : Installing DFS (part two) - Creating a DFS Binder and Replication Grouping & Configuring DFS Read-Only Replication

Creating a DFS Folder and Replication Group

Creating a DFS folder is similar to creating the DFS root. A folder tin can be created to target existing shares or folders beneath shares, or a new share can be created on the desired server or servers. As recommended previously, pre-create the file share on an NTFS folder and properly configure the share and NTFS permissions for each binder target that will be added to the folder.

When a new folder is created with multiple folder targets, a replication group tin can exist created at the same time. To create a folder within an existing namespace, perform the following steps:

1.	Log on to the Windows Server 2008 R2 system with an business relationship with local server administrator privileges.
2.	Pre-create and set NTFS permissions on the servers and shares that volition host the DFS namespace folder.
three.	Click Start, click All Programs, click Administrative Tools, and select DFS Management.
iv.	Select the Namespaces node, so double-click the Namespaces node to expose the existing namespaces.
5.	If the desired namespace does not appear, in the Actions pane, click on the Add Namespaces to Display link and follow the steps to search for and add an existing namespace to the panel view.
vi.	Select the desired existing namespace, and in the Deportment pane, click on the New Folder link.
7.	When the New Folder window opens, type in the proper name of the folder and click the Add button to locate the binder targets.
8.	After all the folder target servers have been added to the New Folder window, click OK to continue, as shown in Effigy four. Figure four. Defining a new folder and folder targets.
nine.	When a new binder is created and multiple targets are specified, a Replication pop-up window opens, asking if a replication grouping should be created. Click Yep to create a new replication grouping for the folder targets.
10.	When the Replication Grouping and Replicate Folder Name window opens, review the name of the proposed replication grouping proper noun and the replicated folder proper noun, and click Adjacent to continue. The prepopulated names will friction match the namespace and folder names.
11.	The Replication Eligibility page will display whether or not each of the binder targets are capable of DFS Replication. If all targets are eligible, click Next to continue.
12.	On the Master Member page, click the Primary Member driblet-downwardly listing pointer and select the folder target server that volition be used to populate the remaining fellow member folder targets. The data that exists in the folder of the primary target fellow member will be replicated to each of the other targets. Later selecting the desired main server, click Next to continue.
13.	On the Topology Selection page, select the desired replication topology. For this instance, select the Hub and Spoke option button, every bit shown in Figure five, and click Next to continue. Effigy v. Selecting the hub and spoke replication topology.
14.	On the Hub Members folio, all servers will initially be listed in the Spoke Member section. Double-click the desired servers to move them to the Hub Member section, if they will exist used as a hub server. Hub servers will replicate with all other servers and spoke servers will only replicate with the hub servers defined on this page. Once all the necessary hub servers are in the Hub Member section, click Next to continue.
15.	On the Hub and Spoke Connections page, each of the spoke servers will exist listed with their required hub fellow member and an optional hub member. Optional hub members will merely be populated if multiple servers are selected as hub members in the previous step. Even though the hub servers are listed as required and optional, the spoke servers will replicate with both and a connection betwixt each hub server and spoke organization will be created. Also, hub servers volition replicate with ane another as well.
16.	On the Replication Group Schedule and Bandwidth page, select the desired bandwidth limitation if desired or fix the hours replication to allowed, and click Next to continue.
17.	On the Review Settings and Create Replication Group folio, review the selections and if everything looks correct, click Create.
xviii.	On the Confirmation folio, if the replication grouping creation tasks were all completed successfully, click Shut. Otherwise, select the Errors tab and review and repair the errors, and rerun the Replication Grouping Creation Wizard.
19.	Once the window is closed, back in the DFS Direction console, double-click on the Replication node to reveal the new replication grouping and select it.
xx.	In the tasks pane, with the new replication group selected in the tree pane, select the Connections tab to review the connections created from the previous steps.

Best Practices for DFS Replication

Following all-time practices for DFS Replication can assistance ensure that replication occurs as expected. Because file replication is triggered by a file version alter or final-saved or modified time stamp, a standard file share might generate many replication changes, which tin can saturate the network bandwidth if no bandwidth constraints are placed within DFS Replication connections. To avoid such scenarios, follow as many of these suggestions every bit possible:

• Offset with empty DFS namespace folders and targets to go on from having to replicate whatsoever data at the root level. Besides, this can simplify the restore process of a DFS root binder because it contains only folders that are managed by DFS.

• Exercise non replicate data between DFS namespace shares because the namespace shares will attempt to replicate the information in the namespace folders equally well as the data contained inside the folder targets. Replication is not necessary if the folder targets are already replicating. Because the roots volition non replicate for redundancy, deploy domain DFS namespaces and add boosted namespace servers.

• Back up at least i DFS binder target and configure the backup to not update the archive bit. Irresolute the archive bit might trigger unnecessary replication.

• Thoroughly exam server operating arrangement antivirus programs to ensure that no agin effects are caused by the scanning of files on a replicated DFS target. Too, configure server antivirus to scan at write operations only and configure clients to browse on read operations to ensure complete antivirus protection for DFS servers and clients.

• Verify that the drive that will comprise the staging folder for a replication connection contains ample space to have the amount of replicated data sent and received by the server.

Having a high number of read-write operations is non desirable because it causes heavy replication, and in a scenario similar this, DFS Replication should be performed during off-meridian hours unless Windows Server 2008 R2 DFS Replication can exist used in conjunction with bandwidth constraints.

Configuring DFS Read-Only Replication

Windows Server 2008 R2 now allows for a replicated folder to exist defined every bit read-only. This can be configured one time a replication group is defined. Equally a best practice, when read-only replicated folders are desired, select the No Topology pick button on the Topology Selection folio when running the Replicate Folder Wizard. Once a replication group is created, select the replication group in the tree pane, and in the tasks pane select the Memberships tab. Correct-click the desired Replicated Folder member and select Make Read-merely, as shown in Effigy six.

Effigy 6. Converting a replicated folder to read-only.

Equally a best practice, when using read-only replicated folders, configure replication connections to be one-way to the read-only binder.

Enabling Access-Based Enumeration on a Domain-Based Namespace in Windows Server 2008 Mode

When a domain-based namespace is created and Windows 2008 mode is enabled, access-based enumeration can exist enabled, just it is not by default. To enable access-based enumeration on a domain-based namespace in Windows Server 2008 fashion, locate the namespace in DFS Management. Correct-click the namespace and select Properties. Select the Advanced tab and check the Enable Access-Based Enumeration for This Namespace check box at the bottom of the window. Click OK to consummate the change. One thing to keep in mind is that this will use to the entire namespace and whatsoever and all folders and folder targets divers in the namespace.

Related -----------------

bennytowernt.blogspot.com

Source: http://tutorial.programming4.us/windows_server/Windows-Server-2008-R2---Installing-DFS-(part-2)---Creating-a-DFS-Folder-and-Replication-Group---Configuring-DFS-Read-Only-Replication.aspx

Share this post