Distributed File System (DFS) is a set of client and server services that allow an organization usingMicrosoft Windows servers to organize many distributedSMB file shares into adistributed file system. DFS has two components to its service: Location transparency (via the namespace component) and Redundancy (via the file replication component). Together, these components enable data availability in the case of failure or heavy load by allowing shares in multiple different locations to be logically grouped under one folder, the "DFS root".
Microsoft's DFS is referred to interchangeably as 'DFS' and 'Dfs' by Microsoft and is unrelated to theDCE Distributed File System, which held the 'DFS' trademark[1] but was discontinued in 2005.
It is also called "MS-DFS" or "MSDFS" in some contexts, e.g. in theSambauser space project.[2]
There is no requirement to use the two components of DFS together; it is perfectly possible to use the logical namespace component without using DFS file replication, and it is perfectly possible to use file replication between servers without combining them into one namespace.
A DFS root can only exist on a server version of Windows (fromWindows NT 4.0 and up) andSolaris[3] (inkernel space) or a computer runningSamba (inuser space.) The Enterprise and Datacenter Editions of Windows Server can host multiple DFS roots on the same server. OpenSolaris intends on supporting multiple DFS roots in "a future project based on Active Directory (AD) domain-based DFS namespaces".[4]
There are two ways of implementing DFS on a server:
\\<domainname>\<dfsroot>or
\\<FQDN>\<dfsroot>The namespace roots can reside on adomain controller or a domain member server. If domain controllers are not used as the namespace root servers, multiple member servers should be used to provide fullfault tolerance.
Traditional file shares, associated with a single server, haveSMB paths of the form
\\<SERVER>\<path>\<subpath>
Domain-based DFS file share paths are distinguished by using the domain name in place of the server name, in the form
\\<DOMAIN.NAME>\<dfsroot>\<path>
When a user accesses such a share, either directly or bymapping a drive, their computer will access one of the available servers associated with that share, following rules which can be configured by the network administrator. For example, the default behaviour is that users will access the closest server to them; but this can be overridden to prefer a particular server.
If a server fails, the client can select a different server transparently to the user. One major caveat regarding this flexibility is that currently-open files will potentially become unusable, as open files cannot befailed-over.
Early versions of DFS used Microsoft'sFile Replication Service (FRS) which provides basic file replication capability between servers. FRS identifies changed or new files, and copies the latest version of the entire file to all servers.
Windows Server 2003 R2 introduced "DFS Replication" (DFSR) which improves on FRS by only copying those parts of files which have changed (remote differential compression), by using data compression to reduce network traffic, and by allowing administrators flexible configuration options for limiting network traffic with a customizable schedule.
The server component of Distributed File System was first introduced as an add-on toWindows NT 4.0 Server, called "DFS 4.1",[5] and was later included as a standard component of all editions ofWindows 2000 Server. Client-side support is included in Windows NT 4.0 and later versions of Windows.
Linux kernels 2.6.14 and later[6] come with an SMB clientVFS called "cifs" that supports DFS.
On Mac OS X DFS is supported natively inMac OS X 10.7 ("Lion") onward.[7]
There are a number of specifications that are relevant to DFS, they are available through the Microsoft Open Specifications program:[8]
