Home > Articles > Operating Systems, Server > Microsoft Servers

  • Print
  • + Share This
This chapter is from the book

Maximizing Redundancy and Flexibility with Distributed File System

One method for creating low-cost failover and redundancy of file shares is leveraging Microsoft's Distributed File System (DFS). A feature introduced in Windows NT 4, DFS improves file share availability by providing a single unified namespace to access shared folders hosted across different servers. Because the same data can be synchronized through replication across multiple servers, there is no single point of failure for the access of the data.

Further, because a DFS root can support multiple targets physically distributed across a network, the network load for accessing particular file shares can be load-balanced rather than taxing a single server.

DFS also improves the users' experience for accessing files because the user needs to remember only a single server or domain name and share name to connect to a DFS-shared folder. Because domain-based DFS, available from Windows 2000, is published in Active Directory, the DFS namespace is always visible to users in the domain. Moreover, if a server hosting a particular share becomes unavailable, DFS will use the site and costing information in Active Directory to route the user to the next closest server.

Finally, because DFS uses NTFS and file sharing permissions, administrators can improve security of data by ensuring only authorized users have access to DFS shares.

The next section explains new DFS features available in Windows Server 2003 and provides best practices for deploying DFS in a Windows Server 2003 network environment.

New DFS Features in Windows Server 2003

Administrators deploying DFS in Windows NT 4, or even in a Windows 2000 Active Directory, often found that the technology promised more than it could deliver. With Windows Server 2003, such problems have been worked out, startup and configuration times have been reduced, memory usage has been improved, and new features have been added.

Closest Site Selection

One such enhancement deals with site costing, which exists in both Windows 2000 and Windows Server 2003. When a client accesses a DFS namespace, DFS will connect the client to a DFS root target in the client's site. In Windows 2000, if there are no available root targets in the client's site, the client will randomly connect to another DFS root target in any site.

With Windows Server 2003, if a root target is not available in the client's site, it will randomly look for a target in the next closest site, and so on. This feature, called Closest Site Selection, improves upon site costing by automatically connecting the client to the closest possible DFS target.

Intersite Topology Generator (ISTG) Must Be Running

For Closest Site Selection to work on link targets, Intersite Topology Generator (ISTG) must be running on Windows Server 2003. All domain controllers in a domain must be running Windows Server 2003 for Closest Site Selection to work on domain root targets.

To enable Closest Site Selection, use the DFSutil.exe command-line tool that is installed with the Windows Server 2003 support tools. The syntax for the command is as follows:

Dfsutil /root:\\servername>\dfsrootname /sitecosting /enable

Multiple Roots per Server

With Windows 2000 DFS, administrators were limited to creating a single DFS root per server. With Windows Server 2003, a server can contain multiple DFS roots. This new feature provides an immediate server and namespace consolidation opportunity for existing Windows 2000 DFS deployments.

More importantly, Windows Server 2003 provides an opportunity to set up different DFS roots on a single server that each have unique security settings. For companies that want to delegate administration of different DFS roots to particular organizational groups, this can now be accomplished from a single server.

With Windows Server 2003 Enterprise or Datacenter Edition, server clusters can support the multiple DFS roots. Multiple DFS roots can exist in multiple resource groups and each group can be hosted on a different node in the cluster. Microsoft Cluster Service (MSCS) is discussed in a later section of this chapter.

Administration Improvements

Windows Server 2003 provides a new DFS Microsoft Management Console (MMC) snap-in that eases the administration of the File Replication Service (FRS). Replication of DFS targets can now be configured via a wizard that includes a built-in topology generator as shown in Figure 22.2.

Figure 22.2Figure 22.2 Configuring DFS Replication topology.

Setting Up DFS

DFS is included with a default installation of Windows Server 2003. Setup begins with defining the DFS namespace. The namespace starts with a root that maps to one or more root targets. Below the root are links that map to their own targets, which refer to shared folders on separate servers.

DFS roots can be server-based or domain-based, but they must exist on NTFS volumes. A domain-based DFS root has the following format: \\domainname\rootname, as shown in Figure 22.3.

Figure 22.3Figure 22.3 Setting up the DFS root.

In Active Directory environments, use the domain-based DFS namespace. This type of namespace can include approximately 5,000 links. Multiple DFS targets can be created in the same domain to ensure availability.

For a single namespace that includes more than 5,000 links, use a standalone server-based DFS namespace. A single, standalone DFS namespace can support as many as 50,000 links. Configuration information for a server-based DFS is stored in the local Registry instead of Active Directory.

Domain-based DFS leverages Active Directory for fault tolerance. For a single server implementation of DFS, high availability is achieved by using Microsoft Cluster Service (MSCS).

Many client types can access targets in a DFS namespace by default. These include Windows Server 2003 family, Windows XP Professional, Windows 2000 family, and Windows NT 4 with Service Pack 6a. Windows 95/98 will need to have the DFS client installed.

DFS Replication

The 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. To avoid such scenarios, follow as many of these suggestions as possible:

  • Start with an empty DFS root folder 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 links that are managed by DFS.

  • Do not replicate DFS roots because the roots will try to replicate the data in the root folders plus the data contained within the link targets. Replication is not necessary if the links are already replicating. Because the roots will not replicate for redundancy, deploy domain DFS roots and add additional root targets.

  • If possible, use DFS for read-only data. When data is being replicated, FRS always chooses the last-saved version of a file. If a group share is provided through a replicated DFS link and two employees are working on the same file, each on different replica targets, the last user who closes and saves the file will have his change(s) saved and replicated over the changes of other previous saved edits.

  • Schedule replication to occur during nonpeak hours to reduce network congestion. For replicating links that contain frequently changing data, this might not be possible, so to provide data redundancy in the unified namespace, create only a single target for that link and deploy it on a cluster file share. This provides server-level redundancy for your file share data.

  • Back up at least one DFS link 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.

  • Verify that the drive that will contain the staging folder for a replication connection contains ample space to accept the amount of replicated data inbound and outbound to this server.

DFS and Security

Although DFS in Windows Server 2003 enables delegation of administration for assigning permissions to DFS roots and links, it does not provide any additional security to the actual DFS root or link targets. What this means for administrators is that the permissions will need to be set on the NTFS shares manually to provide proper access to files and folders within DFS targets.

Moreover, when multiple targets are involved, it is important for administrators to duplicate the NTFS permissions exactly for each additional target. Otherwise, administrators might inadvertently grant users elevated privileges or deny users access completely. To prevent this problem, administrators should create the target file share and configure the share and NTFS permissions manually at the shared folder level before defining the share as a DFS target.

Combining the Functionality of DFS with Software Distribution Via Active Directory Group Policies

When combining the functionality of DFS with software distribution via Active Directory Group Policies, it is important to appropriate NTFS permissions on those shares that contain the software installation packages. If Group Policies are used to push software to computer accounts from DFS shares, make sure those computer accounts have NTFS permission to the file shares.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020