§ Windows and DFS Replication support folder paths with up to 32 thousand characters.
§ DFS Replication is not limited to folder paths of 260 characters.
§ Replication groups can span across domains within a single forest
§ VSS with DFS is supported.
§ Size of all replicated files on a server: 100 terabytes.
§ Number of replicated files on a volume: 70 million.
§ Maximum file size: 250 gigabytes.
§ File can be staged ranging 16KB to 1MB. Default is 64KB when RDC is enabled. When RDC is disabled 256KB from sending member.
§ Up to 5000 folders with target. Maximum 50000 folders with targets.
§ Size of all replicated files on a server: 10 terabytes.
§ Number of replicated files on a volume: 11 million.
§ Maximum file size: 64 gigabytes.
§ Cross forests replication is unsupported
§ NTBackup for remotely backup DFS folder.
§ DFS in a workgroup environment
. This option causes the receiving member to treat the schedule as an absolute clock. For example, a schedule that begins at 0800 UTC is the same for any location, regardless of time zone or whether daylight savings time is in effect for a receiving member. For example, assume that you set replication to begin at 0800 UTC. A receiving member in Eastern Standard Time would begin replicating at 3:00 A.M. local time (UTC – 5), and a receiving member in Rome would begin replicating at 9:00 A.M. local time (UTC + 1). Note that the UTC offset shifts when daylight savings time is in effect for a particular location.
. This option causes the receiving member to use its local time to start and stop replication. Local time is determined by the time zone and daylight savings time status of the receiving member. For example, a schedule that begins at 8:00 A.M. will cause every receiving member to begin replicating when the local time is 8:00 A.M. Note that daylight savings time does not cause the schedule to shift. If replication starts at 9 A.M. before daylight savings time, replication will still start at 9 A.M. when daylight savings time is in effect.
§ The forest uses the Windows Server 2003 or higher forest functional level.
§ The domain uses the Windows Server 2008 or higher domain functional level.
§ All namespace servers are running Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008.
Remote differential compression (RDC) is a client-server protocol that can be used to efficiently update files over a limited-bandwidth network. RDC detects insertions, removals, and rearrangements of data in files, enabling DFS Replication to replicate only the changes when files are updated. RDC is used only for files that are 64 KB or larger by default. RDC can use an older version of a file with the same name in the replicated folder or in the DfsrPrivate\ConflictandDeleted folder (located under the local path of the replicated folder).
RDC is used when the file exceeds a minimum size threshold. This size threshold is 64 KB by default. After a file exceeding that threshold has been replicated, updated versions of the file always use RDC, unless a large portion of the file is changed or RDC is disabled.
§ RDC is available Windows Server 2008 R2 Enterrprise and Datacenter Edition.
§ RDC is available Windows Server 2012/R2 Standard and Datacenter Edition.
A referral is an ordered list of targets, transparent to the user that a client receives from a domain controller or namespace server when the user accesses the namespace root or a folder with targets in the namespace. The client caches the referral for a configurable period of time.
Targets in the client’s Active Directory site are listed first in a referral. (Targets given the target priority “first among all targets” will be listed before targets in the client’s site.) The order in which targets outside of the client’s site appear in a referral is determined by one of the following referral ordering methods:
Lowest cost, Random order, Exclude targets outside of the client’s site
To publish data, you will likely use a hub-and-spoke topology, where one or more hub servers are located in data centers, and servers in branch offices will connect to one or more hub servers. To prevent the hub servers from becoming overloaded, we recommend that fewer than 100 spoke members replicate with the hub server at any given time. If you need more than 100 spoke members to replicate with a hub server, set up a staggered replication schedule to balance the replication load of the hub server.
The lowest cost ordering method works properly for all targets only if the Bridge all site links option in Active Directory is enabled. (This option, as well as site link costs, are available in the Active Directory Sites and Services snap-in.) An Inter-site Topology Generator that is running Windows Server 2003 relies on the Bridge all site links option being enabled to generate the inter-site cost matrix that the Distributed File System service requires for its site-costing functionality. If the Bridge all site links option is enabled, the servers in a referral are listed in the following order:
1. The server in the branch site.
2. The server in regional data center site 1. (Cost = 10)
3. The server in regional data center site 2. (Cost = 30)
4. The server in regional data center site 3. (Cost = 50)
A domain-based namespace can be hosted by multiple namespace servers to increase the availability of the namespace. Putting a namespace server in remote or branch offices also allows clients to contact a namespace server and receive referrals without having to cross expensive WAN connections.
. A namespace server hosts a namespace. The namespace server can be a member server or a domain controller.
. The namespace root is the starting point of the namespace. In the previous figure, the name of the root is Public, and the namespace path is \\Contoso\Public. This type of namespace is a domain-based namespace because it begins with a domain name (for example, Contoso) and its metadata is stored in Active Directory Domain Services (AD DS). Although a single namespace server is shown in the previous figure, a domain-based namespace can be hosted on multiple namespace servers to increase the availability of the namespace.
. Folders without folder targets add structure and hierarchy to the namespace, and folders with folder targets provide users with actual content. When users browse a folder that has folder targets in the namespace, the client computer receives a referral that transparently redirects the client computer to one of the folder targets.
. A folder target is the UNC path of a shared folder or another namespace that is associated with a folder in a namespace. The folder target is where data and content is stored. In the previous figure, the folder named Tools has two folder targets, one in London and one in New York, and the folder named Training Guides has a single folder target in New York. A user who browses to \\domain.com\Public\Software\Tools is transparently redirected to the shared folder \\server1\Tools or \\server2\Tools, depending on which site the user is currently located in.
By default, DFS replication between two members is bidirectional. Bidirectional connections occur in both directions and include two one-way connections. If you desire only a one-way connection, you can disable one of the connections or use share permissions to prevent the replication process from updating files on certain member servers.
Before setting up replication between servers, the DFS Replication roles need to be installed on each server that is going to participate in the replication group. Open Server Manger by clicking on the Server Manager icon on the task bar
1. On the Welcome Tile, under Quick Start, click on Add roles and features to start the Add Roles and Features Wizard. If there’s no Welcome Tile, it might be hidden. Click View on the menu bar and click Show Welcome Tile.
2. Click Next.
3. Select Roll-based or feature-based installation and click Next.
4. Select a server from the server pool and select the server on which you want to install DFS Replication. Click Next.
5. Under Roles, expand File and Storage Services, expand File and iSCSI Services, select DFS Replication and click Next.
6. If you have not already installed the features required for DFS Replication, the following box will pop up explaining which features and roles will be installed along with DFS Replication.
7. Click Add Features.
8. Back to the Select server roles dialog. It should now show DFS Replication as checked along with the other roles required for DFS Replication.
9. Click Next.
10. The Select features dialog shows the features that will be added along with the DFS Replication role.
11. Click Next.
12. Click Install.
13. Click Close when the installation completes.
14. You will notice a new DFS management icon.
1. Double click on this icon to open the DFS Management MMC.
2. In the DFS Management console, right click on Namespaces and select new namespace. In the New Namespace Wizard, select the server that will host the namespace (the DFS server) and click next to continue.
3. Give your DFS and easy to understand namespace and click next.
4. The next step asks whether you want to use a domain based namespace or a stand alone namespace. Select domain-name based DFS namespace and click next, then create.
5. Once finished, you will see the newly created namespace in the namespace section of the DFS Manager along with its UNC path. This is the path you will use to access the DFS share.
6. Now that we have create the namespace, it’s time to add some folders. In DFS, you can access multiple shared folders using a single drive letter. Add the required folders to the DFS namespace.
7. Right click on the DFS namespace and select new folder.
8. In the new folder window, create a folder named X, then click on the add button and locate the folder on the required server. When finished, click OK.
9. Repeat the process to add the other shared folders.
10. To test – Open a browser and type the UNC path of your DFS namespace. All folders appear in a single share.
1. In the DFS Management console, double click on the folder to view its path.
2. Log in to server 2 and create a folder named admin as well.
3. Right click on the folder and select add folder target.
4. Enter the UNC path of the folder located on the second server and click OK.
5. You will be prompted to create a replication group. Click yes.
6. Follow the wizard to configure the replication parameters.
§ Primary Member: This is the server that has the initial copy of the files you want to replicate.
§ Topology: This dictates in what fashion the replication will occur.
§ Bandwidth and Schedule: How much bandwidth to allocate and when to synchronize.
7. Once you have finished, click create. Any file that you create, modify or delete when using the namespace UNC path will be almost immediately copied to both replicating folders.
1. In the console tree of the DFS Management snap-in, right-click the node, and then click .
2. Follow the steps in the New Replication Group Wizard and supply the information in the following table.
3. Select >Type the name of the replication group> Click to select at least two servers that will participate in replication. The servers must have the DFS Replication Service installed.
4. Select Full Mesh> Select .> Select the member that has the most up-to-date content that you want to replicate to the other member.
5. Click to enter the local path of the Data folder you created earlier on the first server. Use the name for the replicated folder name.
6. On this page, you specify the location of the Data folder on the other members of the replication group. To specify the path, click , and then in the dialog box, click , and then type the local path of the Data folder.
7. On this page, you specify the location of the Antivirus Signatures folder on the other members of the replication group. To specify the path, click , and then in the dialog box, click , and then type the local path of the Antivirus Signatures folder.
8. Click to create the replication group.
9. Click to close the wizard. Click to close the dialog box that warns you about the delay in initial replication.