DFS Management
The Distributed File System (DFS) solution in Windows Unified Data
Storage Server 2003 provides simplified, fault-tolerant access to files and wide
area network (WAN) friendly replication. DFS consists of two technologies:
•
DFS Namespaces — DFS namespaces allows administrators to group shared
folders located on different servers and present them to users as a virtual
tree of folders known as a namespace. A namespace provides benefits such
as increased availability of data, load sharing, and simplified data migration.
•
DFS Replication — The successor to file replication service (FRS), DFS
replication is a state-based, multimaster replication engine that supports
scheduling and bandwidth throttling. DFS replication uses a compression
algorithm known as Remote Differential Compression (RDC). RDC is a
protocol that updates files over a limited-bandwidth network. RDC
detects insertions, removals, and rearrangement of data in files enabling
DFS replication to replicate only the changes when the files are updated.
Microsoft Services for NFS
Microsoft Services for NFS is a component of Windows Unified Data Storage
Server 2003 that provides a file sharing solution for enterprise systems
running both Windows and UNIX
Services for NFS, you can configure storage services that enable users to store
and access files on the Windows Unified Data Storage Server 2003 based
storage server. You can also transfer files between the storage server and
systems running the UNIX operating system using the NFS protocol.
In Windows Unified Data Storage Server 2003, the initial configuration of
Microsoft Services for NFS can be completed using the Microsoft Services for
NFS Configuration Guide. This document includes instructions on how to
use the Identity Mapping Setup wizard. After completing the initial
configuration of Microsoft Services for NFS, you can use the Microsoft
Services for NFS console for maintenance and administration.
For more information about Microsoft Services for NFS, see the Microsoft
website.
®
operating systems. Using Microsoft
Deployment Guide
13
Print Page