Best Practices for DFS Replication

Following best practices for DFS Replication can help ensure that replication occurs as expected. Because file replication is triggered by a file version change or last-saved or modified time stamp, a standard file share might generate many replication changes, which 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 as possible:

» Start with empty DFS namespace folders and targets to keep from having to replicate any data at the root level. Also, this can simplify the restore process of a DFS root folder because it contains only folders that are managed by DFS.

» Do not replicate data between DFS namespace shares because the namespace shares will try to replicate the data in the namespace folders as well as the data contained within the folder targets. Replication is not necessary if the folder targets are already replicating. Because the roots will not replicate for redundancy, deploy domain DFS namespaces and add additional namespace servers.

» Back up at least one DFS folder target and configure the backup to not update the archive bit. Changing the archive bit might trigger unnecessary replication.

» Thoroughly test server operating system antivirus programs to ensure that no adverse effects are caused by the scanning of files on a replicated DFS target. Also, configure server antivirus to scan at write operations only and configure clients to scan on read operations to ensure complete antivirus protection for DFS servers and clients.

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

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

Source of Information : Sams - Windows Server 2008 R2 Unleashed (2010)