Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 2.0 Major Updated and revised the technical content. 7/12/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Major Updated and revised the technical content. 11/14/2013 4.0 Updated and revised the technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the
second part is an interface to monitor Distributed File (DFS-R) on a server and to collect various statistics about the DFS Replication operation. Distributed File System Replication Protocol This protocol is used to replicate files between file servers. It is a multimaster replication, which enables files to be changed by any member that participates in replicating shared files. Because it uses an optimistic replication strategy, files can be updated without any prior consensus or serialization. DFS-R uses the Remote Differential Compression (RDC) algorithm. DFS-R supersedes the older FRS replication protocol. File Replication Service Protocol This protocol is an RPC protocol that is used on file servers to replicate files and folders among file servers on the network. This protocol enables
Dependencies on Other Systems/Components The File Management Services system depends on the following external systems and components: Object store: Used to store files and metadata. Active Directory system: Used to store Distributed File System (DFS) namespace metadata. If an Active Directory system is unavailable, an administrator cannot create a domain-based Distributed File System (DFS) namespace and cannot use the Distributed File System Replication (DFS-R) Services. Authentication Services system: Used to authenticate admin clients and the admin server. The Authentication services are described in the Authentication Services Protocols Overview . Assumptions and Preconditions The following assumptions and preconditions for the File Services Management system to operate successfully: System availability: The File Services Management system must be installed on all computers involved. Domain configuration: In a domain configuration, file clients and file services have access to that are provided by the domain. Authentication services: Authentication services, as described in , are available to all file clients and file services. RPC: Components of the file client and file services that use remote procedure call (RPC) interfaces have all prerequisites satisfied, as described in section 1.5. Network configuration: For system components that are running on different computers to communicate, the network services and infrastructure are functional and configured in such a way that required protocols, ports, and so on are remotely accessible. Domain functionality: For system functionality that requires a domain and directory services, as described in , at one domain controller is configured and accessible. Some functionality could require an Active Directory domain as noted in individual technical documents. Use Cases Share Management Use Cases Share Management use cases describe the management activities that the administrator performs to control a shared resource by using the admin tool. The share management activity includes the following share tasks: Creation Enumeration Getting and setting information Deletion The following diagram shows the Share Management use cases that are described in detail in the following sections.
Stakeholders Administrator The administrator is the person who administers the file server. The administrator's has administrative rights and uses the File Services Management system to provide SMB File Services. Main Success Scenario Trigger: The admin tool receives a request from the administrator to get the health report for the DFS-R Service. The tool establishes a communication channel to the DFS-R Service, as described in section 2.1. The DFS Service authenticates the administrator through the mechanisms of the Authentication Services Protocols Overview, as described in . The admin tool contacts the DFS-R Service to get the health report by using either the IServerHealthReport or the IServerHealthReport2 interface, as described in [MS-DFSRH] sections 3.1.5.4 and 3.1.5.5. The DFS-R Service generates the report and returns it to the admin client. Post-Condition The health report is generated and returned to the administrator. Extensions If the communication channel for the DFS Replication Helper Protocol, as described in cannot be established, or it becomes disconnected: The admin tool can attempt to establish connection multiple times; ultimately, the use case ends with failure. Depending on when the connection failed, the namespace could or could not have been created. Create a Directory Object for a DFS Replication Group Using Server Credentials Goal To create an Active Directory object that is used by the DFS-R Service. Context of Use The administrator creates Active Directory objects that have configuration information for DFS replication. Actors Admin tool The admin tool is the primary actor that triggers this use case. The admin tool is a program that offers management functionality to the administrator through the admin client. Typical admin tools are command-line tools and graphical shells, management utilities, and graphical management programs. The purpose of the admin tool is to correctly interpret, execute, and display the results of the commands that are issued by the administrator. DFS-R Service
Index A 55 15 9 17 C 54 75 71 55 17 17 17 17 9 Considerations 55 55 67 60 64 66 69 57 D 58 17 17 17 18 24 31 36 40 18 48 Dfs use cases 24 Dfs-r configuration and monitoring use cases 31 E 17 54 Examples 71 67 60 64 66 69 57 58 Extensibility ( 54, 73) 73 17 F 9 9 G 5 H 54 I 73 55 7 17 5 M 60 73 O Overview 15 9 P 17 73 R 7 Requirements 55 54 9 17 Resource management use cases 36 S 55 Server management use 40 Share management use cases 18 Smb redirector use cases 48 9 17 17