1. Windows Server 2003 R2 分散式檔案系統 (DFS) 規劃與部署
Slide Title: Title Slide
Keywords:
Key Message: Welcome to this Microsoft TechNet session on Planning and Deploying the Branch Office Technologies in Windows Server 2003 R2.
Slide Builds: 0
Slide Script:
Hello and welcome to this Microsoft TechNet session on Planning and Deploying the Branch Office Technologies in Windows Server 2003 R2. My name is {insert name}.
Slide Transition: Let’s start this session by looking at the topics we will be covering.
Slide Comment:
Additional Information:
曹祖聖 台灣微軟資深講師 MCP, MCP+I, MCSA, MCSE, MCDBA, MCAD, MCSD, MCT, MVP

2. Agenda 為分支機構提供檔案服務 了解 DFS 規劃 DFS 使用 DFS
Slide Title: Agenda: Providing Branch Office File Services
Keywords:
Key Message: Agenda
Slide Builds: 3
Slide Script:
We’ll start by looking at the challenges an administrator faces in providing robust file services to the branch office. For instance, in lightly managed scenarios, it is hard to be sure that backup and recovery processes are working properly.
[BUILD1] Then we will look at the Microsoft solution provided in Windows Server 2003 R2, DFS for namespaces.
[BUILD2] We will get into the details of what it takes to plan for DFS in your environment and what you will need to do before you deploy DFS.
[BUILD3] Finally, we will look at the first steps in using DFS and how it will interact with your users’ files, such as Outlook PSTs and database files.
Slide Transition: How do you provide file services to your branch office?
Slide Comment:
Additional Information:

3. 商業需求: 分支機構的檔案 總公司 分支機構 Slide Title: Business Need: Branch Office Files
Keywords: Branch Office, DFS
Key Message: In the past, administrators had to choose the location of branch office file services.
Slide Builds: 2
Slide Script:
Administrators who deal with branch offices face a quandary: Should they provide file services from the hub or from a server in the branch office?
[BUILD1]
If the file servers are located in the hub, the administrator can have better control and can consolidate servers and backup systems, and manage problems more directly. However, the users at the branch office will have slow response times, and their productivity is reliant on their WAN link. If they can’t connect to the hub office, their file resources are unavailable.
[BUILD2]
If the organization puts file servers in the branch office, the administrator faces the difficulty of managing resources in a remote location or expanding the IT resources at the branch. In a word, it is going to be more expensive. The branch office users will be able to access their files faster and more reliably, but what if they need to collaborate with users at a different office? If complicated situations, such as a recovery from backup, arise, how will you manage it remotely?
Neither option is ideal.
Slide Transition: The solution is Windows Server Distributed File System.
Slide Comment:
Additional Information:
分支機構

4. Distributed File System 概觀台北
虛擬名稱空間
Slide Title: Distributed File System Overview
Keywords:
Key Message: DFS simplifies file access and replication between enterprise branches.
Slide Builds: 4
Slide Script:
DFS is a technology that simplifies file access and data security. DFS uses file replication to keep data available and secure. In this example, a set of specified files is replicated using DFS between servers in New York and London hub offices. DFS replication is highly scalable. It can include hundreds of servers and function across Active Directory domains. This means that no matter how large your organization grows, DFS will continue to support your data replication needs.
New compression technology in Windows Server 2003 R2, which we will cover in a moment, minimizes the network cost of this replication. You can also customize the DFS replication schedule with a granularity of up to 15 minutes, which can help further decrease the impact of file replication on your network infrastructure. The flexible and highly efficient replication offered by DFS can provide an ideal solution for synchronizing files between branch office and hub servers.
[BUILD1]
Windows Server 2003 R2 now also offers support for virtual file namespaces. Administrators can define virtual namespaces for folders that are accessible throughout the enterprise. These namespaces can either work in conjunction with DFS replication or with another replication mechanism of your choice.
Using virtual namespaces, users can connect to a set of files through the configured namespace without needing to know the physical location where those resources are stored. This means that files can be moved between servers without disrupting user access.
In this scenario, a user in the London branch office accesses a set of DFS-replicated files using a virtual namespace.
[BUILD2]
Since DFS supports site-proximity sorting, the user is automatically redirected to the file replica on the closest server—in this case, the London server.
[BUILD3]
DFS also contains built-in failover support. If the lowest-cost source for a requested resource is not available, the user is automatically directed to the next-lowest-cost source server. Here, the London server is offline. Instead of failing, the virtual namespace request is automatically forwarded to the New York server, where another file replica is stored. Automatic failover support means that branch office users can continue to seamlessly access enterprise resources even if local servers are offline.
[BUILD4]
Since the DFS replication algorithm is self-healing, updated files are automatically replicated to servers that have gone offline once access is restored. This means that administrators do not need to manually update files or synchronize resources if a server in either the branch office or the hub office experiences network link fluctuations or a service failure.
Slide Transition: Now that we have seen a high-level view of how DFS works, let’s look at how DFS would be applied to a branch office.
Slide Comment:
Additional Information:
台北的使用者 台中

5. DFS 部署場景 資料收集 資料發行 寛鬆的協同合作 合併資料 備份資料 分散資料 可靠的存取 本地存取 內容共享
Slide Title: DFS Deployment Scenarios
Keywords:
Key Message: These are the three most common uses for DFS in the branch office.
Slide Builds: 2
Slide Script:
One of the most common applications of DFS in the branch office is for data collection. Most enterprises encounter the need to consolidate content generated by numerous employees in diverse locations into a single data repository. Collecting data into a single repository provides a canonical point of access for enterprise assets and simplifies the process of data backup.
In order to be effective, a data collection system must provide consistent access to a data repository for users, regardless of their location or changes to the underlying network infrastructure. In addition, if a data collection point goes offline for any reason, the data collection system must be able to detect this failure and collect data from the offline system once it becomes available.
[BUILD1]
Most enterprises also need a mechanism for publishing data. Information workers need a way of distributing new enterprise assets to workers at remote locations and making sure that employees have access to the most recent version of materials. Again, in order to be effective, a data publication mechanism must provide consistent access for users across the enterprise and must efficiently replicate information from a central server to remote locations.
[BUILD2]
Finally, enterprises with distributed offices must provide a mechanism for users at different locations to collaborate with each other and share data. Users at each location need fast, local access to shared assets, and must be able to publish assets for other users to view. Users collaborating on projects must also have consistent access to the most recent version of shared materials and resources.
Slide Transition: Let’s take a closer look at DFS namespaces.
Slide Comment:
Additional Information:
資料發行
分散資料
可靠的存取
寛鬆的協同合作
本地存取
內容共享

6. demonstration Demo 排程與頻寬 管理名稱空間 管理名稱伺服器
Slide Title: Demonstration: Scheduling and Bandwidth
Keywords:
Key Message: Demonstration
Slide Builds: 0
Slide Script:
In this demonstration, we will create a namespace in the Contoso network using the DFS Management console. We will see how a user accesses a namespace, and then add additional servers to the namespace, looking at how a namespace can be shared between servers.
Slide Transition: DFS namespaces and replication provide powerful solutions.
Slide Comment:
Additional Information:

7. Agenda 為分支機構提供檔案服務 了解 DFS 規劃 DFS 使用 DFS
Slide Title: Agenda: Providing Branch Office File Services
Keywords:
Key Message: Agenda
Slide Builds: 3
Slide Script:
We’ll start by looking at the challenges an administrator faces in providing robust file services to the branch office. For instance, in lightly managed scenarios, it is hard to be sure that backup and recovery processes are working properly.
[BUILD1] Then we will look at the Microsoft solution provided in Windows Server 2003 R2, DFS for namespaces.
[BUILD2] We will get into the details of what it takes to plan for DFS in your environment and what you will need to do before you deploy DFS.
[BUILD3] Finally, we will look at the first steps in using DFS and how it will interact with your users’ files, such as Outlook PSTs and database files.
Slide Transition: How do you provide file services to your branch office?
Slide Comment:
Additional Information:

8. 排程與頻寬節流 2 Mbps 64 Kbps 台北 高雄 12:00AM ~ 5:00AM 其它時間: 64 Kbps
Slide Title: Schedules and Bandwidth Throttling
Keywords: DFS for Namespaces, Scheduling, Throttling
Key Message: DFS bandwidth usage can be controlled with schedules and bandwidth throttling to prevent network saturation.
Slide Builds: 3
Slide Script:
A high-use DFS namespace could quickly take over many WAN connections. DFS features make it possible to keep the DFS namespaces from consuming all the available bandwidth.
[BUILD1] Since most businesses have the bulk of their network use during business hours, you can utilize the available off-hours bandwidth for DFS updates. Keep in mind that branch offices are often in different time zones. Off-hours for one site may be the middle of the day at another location.
You can create schedules for an entire replication group or create a custom schedule for a single folder as an exception to that schedule. Each schedule can be set in 15-minute increments for a 7-day period.
[BUILD2] In addition, you can define how much of your WAN bandwidth DFS namespaces will utilize. There are several settings, from 16 Kilobits per second to 256 Megabits per second.
Analyze your needs and determine whether your schedule multiplied by bandwidth will replicate all of the data that you need. The throttling feature is flexible—you can even have different settings for different schedules.
[BUILD3] Even if you have your major replication performed overnight, it might be a good idea to keep a small amount of bandwidth, say 64 Kbps, available throughout the day to keep databases and files up to date.
Slide Transition: You can establish more granular control of your file services by putting your DFS folders into replication groups.
Slide Comment: Additional Information: 台北
12:00AM ~ 5:00AM
其它時間: 64 Kbps 高雄

9. 複寫群組 建立複寫群組來做: 不同的複寫拓樸 不同的時間排程 Slide Title: Replication Groups
Keywords: DFS Namespaces, Replication Groups
Key Message: A replication group is a boundary for managing DFS namespaces.
Slide Builds: 2
Slide Script:
The replication group is the basic unit of DFS management. You can create a single or multiple replication groups for your organization. A replication group contains the DFS folders and is a boundary for managing DFS namespaces. We can create multiple groups if we need to divide how our namespaces are configured.
[BUILD1] If we need to deploy DFS for different topologies, such as some for data collection and some for data distribution, we can create a different group for each topology.
[BUILD2] If we need to use different schedules on DFS namespaces, we can create separate replication groups. A single replication group allows you to use the same topology and to simplify management.
For instance, if we wanted to distribute patches to branch offices through a DFS namespace, we might want to trigger replication when a new patch is available. However, we must trigger replication for the entire replication group. Create a replication group just for the Patches folder so that you can trigger it when necessary.
Slide Transition: Let’s look at the Contoso network and see how replication groups will be configured.
Slide Comment:
Additional Information:
不同的複寫拓樸
不同的時間排程

10. demonstration Demo 資料夾複寫 建立複寫群組 設定複寫排程 設定複寫拓樸
Slide Title: Demonstration: Replicating Folders
Keywords:
Key Message: Demonstration
Slide Builds: 0
Slide Script:
In this demonstration, we will create a replication group. Through the replication group, we can control what servers replicate a DFS namespace and their bandwidth usage. We will create a custom topology so that the London server does not communicate directly with the Seattle server, but both servers replicate with New York. Finally, we will publish the DFS folder to the namespace.
Slide Transition: You will want to plan how to monitor your file system.
Slide Comment:
Additional Information:

11. 監控能力 DFS 內建的報表 Microsoft Operations Manager
很容易實作
少於 50 部伺服器時使用
Slide Title: Monitoring Capabilities
Keywords: DFS Namespace Monitoring
Key Message: Design a monitoring plan based on your needs.
Slide Builds: 3
Slide Script:
It’s important to keep an eye on your DFS namespace. Some problems can occur that will keep your DFS namespace from performing as intended. For instance, you could throttle the bandwidth too much for the amount of data that your namespace contains. In this situation, replication will never completely catch up and data will not be able to update. There are three ways to monitor DFS:
[BUILD1] DFS namespaces contain a built-in diagnostic reporting tool in the DFS Management snap-in. If you have fewer than 50 servers, the built-in DFS monitoring tools will probably work for you. They require little effort to implement and will function for more than 50 servers, but it will not perform very fast.
[BUILD2] As an alternative for larger implementations, particularly if you have already deployed Microsoft Operations Manager in your environment, the DFS Management Pack monitors the performance and health of the DFS service running on Windows® 2000 and later operating systems. In addition to monitoring the health of the DFS service, the Management Pack can also help monitor the availability of DFS shares to clients through client-side monitoring. By detecting, alerting on, and automatically responding to critical events and performance indicators, the Management Pack helps correct and prevent possible DFS service outages. By using embedded expertise, this Management Pack highlights performance, health, and availability conditions that indicate problems. It can, in some cases, even identify issues before they become critical, thus providing you with a level of customer responsiveness that increases the overall availability and performance of your Windows operating systems. As a result, this Management Pack will reduce the cost of ownership by enabling proactive management and reducing resolution times for the issues identified.
[BUILD3] For more customization capabilities, there is a robust DFS Windows Management Interface provider. You can create custom queries, write scripts, or use any tool that can retrieve WMI information, such as WMIC, the WMI command-line provider.
Whatever option you choose, come up with a monitoring plan. Identify what you are looking for and target that information.
Slide Transition: DFS in Windows Server 2003 R2 also includes Remote Differential Compression.
Slide Comment:
Additional Information:
Microsoft Operations Manager
與其它類型的監控整合
用戶端監控
DFS Replication WMI Provider
自訂查詢與監控應用程式
使用 WMIC 或其它事件提供者

12. 使用 RDC 進行複寫 傳送端伺服器 接收端伺服器 File.txt File.txt 要求檔案 更新過的內容 差異雜湊
Slide Title: Replication with RDC
Keywords: RDC, compression, bandwidth
Key Message: RDC saves bandwidth by transferring only the changed portion of files.
Slide Builds: 5
Slide Script:
Here, we have two servers that contain copies of the replicated document, File.txt.
[BUILD1]
In this case, an updated version of the file has been saved to one of the DFS servers. In this example, the word “brown” has been added to the file contents.
[BUILD2]
Next, the second receiving DFS server requests a copy of the new file from the sending server that contains the updated version.
[BUILD3]
DFS replication compares the files by breaking the updated file into discrete chunks and using a hash algorithm to evaluate the contents of each chunk. These hashes are sent to the receiving server, which compares them to the version of the file in the local repository.
[BUILD4]
If the files are identical, only minimal metadata is transferred. If the files are different, the file segments containing changed data are requested by the receiving server.
[BUILD5]
After this comparison, only chunks that have updated contents are transferred between the client and the server, reducing the overall transfer size.
It’s important to remember that for RDC compression to function, both computers need to be running Windows Server 2003 R2.
Slide Transition: By transferring only changed portions of a file, RDC can dramatically improve transfer speeds and decrease bandwidth usage.
Slide Comment:
Additional Information:
The quick fox
jumped over
the lazy dog
who was asleep.
The quick fox
jumped over
the lazy dog
who was asleep.
The quick fox
jumped over
the lazy
brown dog
who was asleep.
要求變更
the lazy
brown dog
傳送變更

13. Staging Folder 本地端 Staging Folder 虛擬名稱空間 遠端 成員伺服器 本地端成員伺服器
Slide Title: Staging Folder
Keywords: DFS Namespace Staging Folder
Key Message: Know where the staging folder is and make it large enough for efficient replication.
Slide Builds: 3
Slide Script:
DFS replication uses staging folders that act as caches for new and changed files to be replicated from sending members to receiving members. It’s important to determine each staging folder quota as you plan DFS. The staging folder is a hidden folder that is, by default, at the root of the replicated folder. Each staging folder’s quota can be configured separately. It should be carefully set based on the folder’s replication activity and space available on the drive.
You should size the staging folder quota so that it is large enough to store the amount of data that will be replicated during the replication window. For example, if you plan to drop 2 gigabytes of files into the replicated folder, and you want that data to replicate within the replication window (assuming the window is long enough), set the staging quota size to at least 2 gigabytes. That way, the full 2 gigabytes of data will still be in the staging folder when the next replication window opens on the staggered schedule. However, since DFS replication compresses the staging files, a 2-gigabyte quota might not be necessary.
[BUILD1] A larger staging folder will increase performance by preventing files from being staged twice. For instance, if a folder is replicated to two branch offices in a DFS replication system and the branches are in different replication schedules, a too-small staging folder will have purged the file after the first replication.
[BUILD2] The file will have to be restaged. More CPU and disk I/O will be required to copy the file again. The default size of each staging folder is 4,096 MB. This is not a hard limit, however. It is only a quota that is used to govern cleanup and excessive usage based on high and low watermarks (90 percent and 60 percent of staging folder size, respectively). For example, when the staging folder reaches 90 percent of the configured quota, the oldest staged files are purged until the staging folder reaches 60 percent of the configured quota.
It is important to note that the staging folder quota does not determine the largest file that can be replicated. In other words, it is possible to replicate a file that is larger than the configured quota of a staging folder. The large file is placed in the staging folder, and the staging folder cleanup process is triggered when the file is finished staging and space usage is at or above the high watermark. If the cleanup fails because the large file is still in the process of being replicated to receiving members, the cleanup process will be retried later, and eventually the large file will be purged from the staging folder.
[BUILD3] If the staging folder is large enough, the file will stay in the folder for the second branch office replication. For one file, the difference is insignificant; however, consider that a small staging folder could double all of our DFS-related disk I/O. Compared with relatively inexpensive hard disk space, appropriately sized staging folders are a cheap way of improving performance.
Slide Transition: Increasing the staging folder size will also improve the performance of RDC.
Slide Comment:
Additional Information:
虛擬名稱空間
遠端 成員伺服器
本地端成員伺服器

14. 使用 Staging Folder 改善 RDC 效率
Checksum
檔案的部份變更時，該部份的 checksum 就會改變
RDC 會維護檔案的每一個部份的 checksum 值
Checksum 4 4 5
Slide Title: Staging Folder Improves RDC
Keywords: DFS Namespace Staging Folder, Remote Differential Compression, RDC
Key Message: RDC checksums are maintained in the staging folder.
Slide Builds: 2
Slide Script:
RDC also uses the staging folder.
[BUILD1] When a file is changed and subsequently staged in the staging folder, RDC logically "breaks" the file into portions and uses an algorithm to generate a checksum value for each portion.
[BUILD2] By comparing the checksums on the sending and receiving members, RDC identifies the mismatched checksums, which indicate that the portion has changed, and then replicates only the changed portions.
These checksums are stored as an alternate data stream on the staging file. As long as the file is kept in the staging folder, the checksums do not need to be regenerated if the file is replicated again. Generating the checksum value does require CPU overhead, which is why it is good to minimize checksum regeneration by keeping staged files. A larger staging folder will reduce CPU overhead by cutting down on the checksums that must be created.
Slide Transition: Let’s see a demonstration of this.
Slide Comment:
Additional Information:
虛擬名稱空間
Staging Folder
Staging Folder

15. demonstration Demo 控制 DFS 使用檔案類型來過濾 變更 Staging Folder
DFS Replication WMI Provider
Slide Title: Demonstration: Controlling DFS
Keywords:
Key Message: Demonstration
Slide Builds: 0
Slide Script:
In this demonstration, we will control how DFS works in the environment. First, we will prevent certain files or subfolders from replicating. Then, we will move the staging folder and increase its quota to increase DFS performance.
Slide Transition: Now that you have seen DFS in action, let’s move on to the next agenda item.
Slide Comment:
Additional Information:

16. Agenda 為分支機構提供檔案服務 了解 DFS 規劃 DFS 使用 DFS
Slide Title: Agenda: Providing Branch Office File Services
Keywords:
Key Message: Agenda
Slide Builds: 3
Slide Script:
We’ll start by looking at the challenges an administrator faces in providing robust file services to the branch office. For instance, in lightly managed scenarios, it is hard to be sure that backup and recovery processes are working properly.
[BUILD1] Then we will look at the Microsoft solution provided in Windows Server 2003 R2, DFS for namespaces.
[BUILD2] We will get into the details of what it takes to plan for DFS in your environment and what you will need to do before you deploy DFS.
[BUILD3] Finally, we will look at the first steps in using DFS and how it will interact with your users’ files, such as Outlook PSTs and database files.
Slide Transition: How do you provide file services to your branch office?
Slide Comment:
Additional Information:

17. 確定您的需求 資料收集與備份 資料分散 鬆散的協同合作 嚴格的協同合作 系統狀態備份 DFS 名稱空間 SharePoint 系統狀態
Slide Title: Determining Your Requirements
Keywords: DFS, SharePoint, failure protection, data protection
Key Message: DFS is helpful for a lot of scenarios, but it does not work as well for strict collaboration or operating system backup.
Slide Builds: 2
Slide Script:
DFS can fulfill the needs for the branch office that we pointed out earlier in this session. It can help you with data distribution from your hub to branch offices. It can also help in data collection from the branch, which you can then back up centrally.
[BUILD1] You can utilize DFS for collaboration; however, it does not have any additional conflict resolution. It is a multimaster environment in which any node can write to the namespace. As a result, in a strict collaborative environment, there are no good protections to prevent a file from being opened by multiple people or written over. For strict collaboration, consider using SharePoint. SharePoint includes file checkout procedures to prevent conflicts between collaborators.
[BUILD2] In addition, DFS cannot be used alone to back up operating system data. For disaster preparedness, put in place an operating system backup and recovery system apart from DFS, such as Microsoft System Center Data Protection Manager 2006.
The DFS replication service supports configuring a volume root, such as C:\, as the local path of a replicated folder, but this configuration is not recommended. DFS replication replicates metadata (including ACLs and attributes) that are set on the local path of the replicated folder. Volume roots are special because they always implicitly have both the hidden and system attribute bits set. If replication partners are configured to have the corresponding local path of the replicated folder to be some place other than a volume root, that replicated folder will have system attributes and hidden attributes set. System folders are typically placed in the volume root. DFS replication is designed to ignore these folders, but there might be interoperability issues with third-party applications.
Slide Transition: What are the requirements for DFS?Slide Comment:
Additional Information:
嚴格的協同合作
使用檔案 checkout 機制來避免衝突
SharePoint
系統狀態備份
作業系統復原
系統狀態

18. DFS 複寫需求 變更 Active Directory schema 不能跨樹系 跨檔案 RDC DFS 類別與屬性
Windows 2000 或 2003 網域控制站
Slide Title: DFS Replication Requirements
Keywords: DFS for namespaces, replication, Windows Server 2003 R2
Key Message: Prepare Active Directory for DFS.
Slide Builds: 2
Slide Script:
Before you implement DFS, you must first update the Active Directory schema to include the Active Directory classes and attributes used by DFS replication. In addition to Windows Server 2003 R2, you can apply the schema to Active Directory domain controllers running Windows Server 2003 or Windows 2000 Server. Windows 2000 and 2003 servers may be present in the organization and may be domain controllers, but all DFS member servers that participate in the replication must run Windows Server 2003 R2.
[BUILD1] DFS cannot occur between forests, even with cross-forest trusts established. However, DFS replication can occur between servers in different domains. Design the DFS system with member servers that are all in the same forest.
[BUILD2] As mentioned earlier, cross-file RDC is only available when one of the servers is running Windows Server 2003 R2 Enterprise or Datacenter. Generally, in a branch office scenario, that means the main office runs the Enterprise or Data Center edition and the branch offices can run the Standard edition.
Slide Transition: Now we can start designing our Distributed File System.
Slide Comment:
Additional Information:
不能跨樹系
可以跨同一樹系下的不同網域
跨檔案 RDC
需要 Enterprise 或 Data Center 版

19. DFS 設計流程 初始決定 基礎架構分析 重覆檢視效能與參考最佳化準則 決定那些資料要複寫 決定名稱空間 設計複寫拓樸
Slide Title: DFS Design Process
Keywords: DFS, Design, MOF
Key Message: The design process from the resource kit will guide you through implementation.
Slide Builds: 3
Slide Script:
This is the design process that will be the guideline for the rest of this session.
[BUILD1] Before you deploy DFS, make some preliminary decisions. Identify what data you want to replicate. How much data will be changing daily? What types of files are you going to put in the namespace? Different file types make better use of RDC than others, so you will have to scope your capacity for your user’s needs. For more information about RDC compression, see the TechNet session ADD-54 “Branch Office Solutions in Windows Server 2003 R2.”
Also, make initial decisions about the namespace. This will involve deciding whether your namespace should be stand-alone or linked to your domain, whether it will reside on a cluster, and whether you will use multiple servers for distributed file services.
Design the topology based on your needs and your network capabilities. DFS can be flexible in helping you make sure that users access the namespace from the member that is closest to them, so identify which servers will provide for which sites.
[BUILD2] Next, perform some analysis of your infrastructure. How will implementing DFS affect your network’s high availability and business continuity? This is a good time to identify the effect the DFS rollout will have on the organization.
Who will be responsible for the DFS namespaces? Identify who is the manager of namespaces and delegate administrative rights.
At this time, you should also create replication schedules and specify DFS bandwidth allowance. With these two tools, you can limit the impact of DFS on your other network operations by limiting the amount of DFS traffic and the time of DFS traffic.
For a Microsoft Excel spreadsheet to assist you in documenting your DFS namespace design decisions, see the "DFS Configuration Worksheet" on the Microsoft® Windows® Server 2003 Deployment Kit companion CD. It is also available on the Web at
[BUILD3] Finally, review your performance and optimization guidelines. Later in this session you will see how increasing the size of your staging folder is a simple and cheap way to increase the performance of your DFS namespace.
Slide Transition: What are the initial namespace decisions?
Slide Comment:
Additional Information:
基礎架構分析
規劃高可用性與持續的商業運作能力
決定管理權限的委派
建立複寫排程與頻寬節流
重覆檢視效能與參考最佳化準則

20. 決定名稱空間 Stand-alone 名稱空間 一部主機的網域名稱空間 多部主機的網域名稱空間 可以使用叢集來估容錯 適合大量的資料夾
Slide Title: Initial Namespace Decisions
Keywords: Namespace, Windows R2
Key Message: The underlying structure of namespaces has not changed significantly from the Windows Server 2003 version.
Slide Builds: 0
Slide Script:
In the initial namespace decision, determine which flavor of namespace is best suited for your needs. You can determine what type of namespace is best by asking these questions:
Will you have more than 5,000 folders in a namespace?
Does the namespace need to be fault-tolerant?
Do you have Active Directory deployed in your organization?
Based on the answers to these questions, you can build a stand-alone namespace or a domain-based namespace, and you can plan for clustering or DFS.
These criteria are unchanged in R2, so the information at is still relevant.
Slide Transition: You will also need to plan for backup and disaster recovery.
Slide Comment:
Additional Information:
一部主機的網域名稱空間
使用 Active Directory 做存取控制
多部主機的網域名稱空間
容錯機制
資料分散

21. 規劃備份策略 總公司 虛擬名稱空間 Slide Title: Plan for Backups
Keywords: DFS namespaces, Windows Server 2003 R2, backup
Key Message: Prepare for potential disaster-recovery situations by designing a backup plan.
Slide Builds: 3
Slide Script:
Backups are essential to a highly available distributed file system, because any total recovery strategy in a collection or distribution DFS namespace is a recovery from backup.
[BUILD1] Therefore, regularly back up the namespace data at the main office.
[BUILD2] You will also want to back up the namespace itself. Its configuration data can be restored from backup. If you export the configuration data, you would not have to re-create it if you experience a total loss of the server. Instead, use the Windows Support Tool “DFSutil.exe” to export the DFS settings from the member server. DFSutil.exe can be used to import the settings back to the recovered server.
Before making any dramatic changes to your DFS namespaces, back up both the files and the DFS configuration.
[BUILD3] In addition, important DFS replication information is stored in Active Directory. Therefore, this information should be backed up as part of your regular Active Directory backup process. For more information, see the “Administering Active Directory Backup and Restore” heading in the “Active Directory Operations Guide.”
Another disaster preparedness task is to inventory the DFS replication settings. You can use the DFSRadmin.exe command-line tool to generate a list of replication folders, replication groups, and their respective attributes. If you must re-create your replication groups from scratch, this document will be all the information that you need.
For more information about DFSRadmin, see the TechNet session ADD-54, “Branch Office Solutions in Windows Server 2003 R2.”
Slide Transition: If your organization is spread out, you may need some help administering DFS.Slide Comment:
Additional Information:
總公司

22. 規劃委派策略 建立 stand-alone 名稱空間 建立以網域為基礎的名稱空間 管理名稱空間與複寫群組 建立複寫群組 啟用複寫 管理者
Slide Title: Plan for Delegation
Keywords: DFS, administration, delegation
Key Message: Most, but not all, DFS tasks can be delegated.
Slide Builds: 1
Slide Script:
Almost every DFS-replication administrative task can be delegated to other users.
[BUILD1] Determine who will need to perform these tasks. A member of the Domain Admins group can delegate the creation of stand-alone or domain-based namespaces, as well as the management of existing namespaces and replication groups. Creating replication groups and enabling replication on folder targets in a namespace can also be delegated.
This can be useful when a low-management branch office has no administrator, but a local user handles some of the day-to-day IT operations for the branch servers. Without granting complete administrative rights, you can selectively allow a local user to control some aspects of DFS.
It’s a good idea to review “Best Practices for Delegating Active Directory Administration,” available on when you are planning administration delegation.
Slide Transition: Now we will plan and create a lab environment to test DFS.
Slide Comment:
Additional Information:
分支機構使用者

23. 建立測試計劃 DFSRadmin RG Export FSUTIL USN DeleteJournal /d C: DFS 測試環境
資料庫與應用程式
Slide Title: Building a Test Plan
Keywords: DFS, namespace, testing, lab
Key Message: Build a test lab that closely simulates your working environment.
Slide Builds: 4
Slide Script:
Like any implementation, you should test DFS namespaces in a test lab. Start by setting up a lab that is similar to your actual environment.
[BUILD1] Put in place any third-party applications, such as databases, that will interact with DFS namespaces in your actual network. Put in the namespace similar file types and data types as in your network.
[BUILD2] Be sure to re-create any firewalls that your DFS system will have to pass through. Confirm that the ports necessary for DFS are allowed between the necessary member servers.
[BUILD3] We should test our backup and disaster recovery plan in the lab as well. Restore replicated folders from your backup application. Test your disaster recovery scenarios as well. Use DFSRadmin to import and export the DFS settings.
[BUILD4] Another great disaster recovery test is to delete the USN journal using FSUtil. DFS is reliant on the NTFS USN journal for file change information. If the journal is deleted, it will take some time for it to be re-created. In your test lab, use FSUtil with the “deletejournal” switch to delete the USN journal on a member server to get an idea of how long it will take for the USN journal to be re-created.
Slide Transition: We have now planned for DFS for namespaces, from determining your requirements to testing DFS for namespaces in a lab.
Slide Comment:
Additional Information:
“DFS Operations Guide: Using the DFSRAdmin Command-line Tool “
防火牆
測試備份計劃
DFSRadmin RG Export
FSUTIL USN DeleteJournal /d C:

24. Agenda 為分支機構提供檔案服務 了解 DFS 規劃 DFS 使用 DFS
Slide Title: Agenda: Providing Branch Office File Services
Keywords:
Key Message: Agenda
Slide Builds: 3
Slide Script:
We’ll start by looking at the challenges an administrator faces in providing robust file services to the branch office. For instance, in lightly managed scenarios, it is hard to be sure that backup and recovery processes are working properly.
[BUILD1] Then we will look at the Microsoft solution provided in Windows Server 2003 R2, DFS for namespaces.
[BUILD2] We will get into the details of what it takes to plan for DFS in your environment and what you will need to do before you deploy DFS.
[BUILD3] Finally, we will look at the first steps in using DFS and how it will interact with your users’ files, such as Outlook PSTs and database files.
Slide Transition: How do you provide file services to your branch office?
Slide Comment:
Additional Information:

25. 已開啟檔案與 Outlook PSTs 檔 虛擬名稱空間 本地 Staging Folder 共享違規 檔案類型過濾 本地成員伺服器
Slide Title: Open Files and Outlook PSTs
Keywords: DFS, Outlook, PST
Key Message: Open files are not synchronized by DFS.
Slide Builds: 2
Slide Script:
DFS does not replicate open files.
[BUILD1] The DFS service will perform a sharing violation if it encounters an open file and tries to stage it. The first 100 files that result in a sharing violation will be included in a report available to DFS built-in reporting.
DFS will wait until a file is closed before copying it to the staging area. This will affect many types of database files, including the PST file that Outlook uses for data storage. Recent regulations, such as Sarbanes-Oxley, have required organizations to save all s. You can use DFS to collect PSTs from the branch office, but you will need to configure Outlook to close them on a regular basis.
[BUILD2] If you are having this experience with files that you do not want to replicate, you can set up replication filters that prevent DFS from attempting replication of certain file types. You can use this feature to prevent problems with databases that you do not want to replicate.
Slide Transition: Here is a recommended procedure for using DFS with Outlook PST files.
Slide Comment:
Additional Information:
Microsoft Knowledge Base articles and
共享違規
檔案類型過濾
本地成員伺服器

26. PST 建議的作法 Outlook 2000: Outlook 2003
HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Outlook\PST\PSTDisconnectDelay
Microsoft Knowledge Base #222328
Slide Title: PST Recommended Procedure
Keywords: DFS, PST, Outlook
Key Message: Configure Outlook to release the PST file every 15 minutes.
Slide Builds: 2
Slide Script:
Some versions of Outlook do not, by default, ever release their PST files. If the files that you want to replicate include PST files, you should configure Outlook clients to release their PST files every 15 minutes.
[BUILD1]
By default, Outlook only releases a PST file after 30 minutes of inactivity. We can configure it to automatically release the file on a scheduled interval by editing the workstation registry. In the local registry, create the “PSTDisconnectDelay” DWord value, and assign it a decimal value of 900 seconds, or 15 minutes. Refer to Microsoft Knowledge Base article for instructions on how to change the timeout period in Outlook 2000.
[BUILD2]
For Outlook 2003, you must first install Office Service Pack 2. Then, follow the same procedure as Outlook 2000, except edit the registry key “PST Key,” which is in a different location.
Slide Transition: As you initialize the DFS namespace, you will have to designate a primary member.
Slide Comment:
Additional Information:
Microsoft Knowledge Base articles and
Outlook 2003
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\PST\PST Key
Microsoft Office 2003 SP2:

27. 指定主要成員伺服器 Foo.txt 一般的狀況: 所有成員都相同 以主要成員伺服器的為主 主要成員伺服器 DFS 名稱空間 遠端 成員伺服器
Slide Title: Designate Primary Member
Keywords: DFS Namespace, Primary Member, Initial Synchronization
Key Message: Designate the authoritative file server as the primary master for the initial DFS synchronization. Make the file server that has the authoritative versions of files the primary member.
Slide Builds: 3
Slide Script:
When in operation, DFS follows the multimaster model similar to Active Directory. That is, a change made to any node will replicate to all other nodes.
[BUILD1] However, the initial synchronization requires one member to be the source for the namespace. Designate the member that has the most current version of files as the primary member.
[BUILD2] The primary member status means that this member’s files will win any conflict resolution, regardless if the other member’s versions of the file are older or newer. Take care to audit the receiving folders. It’s a good idea to back up the receiving folders before triggering initial synchronization. Unique files on the receiving member will be preserved and replicated once initial synchronization is completed.
[BUILD3] Once the initial synchronization is completed, the primary member designation is removed and the DFS namespace functions as a multimaster environment. All members are equal partners in replication.
Slide Transition: Now we should be prepared to initiate DFS. Let’s look at how that process works.
Slide Comment:
Additional Information:
DFS 名稱空間
遠端 成員伺服器
Foo.txt
Foo.txt
Foo.txt

28. 開始 DFS 1. 網域控制站複寫 2. DFS 成員伺服器查詢 AD 3. 複寫 DFS 名稱空間 主要成員伺服器
Slide Title: Starting DFS
Keywords: DFS, Initial Synchronization, Active Directory
Key Message: DFS will not start replicating until all domain controllers have synchronized.
Slide Builds: 3
Slide Script:
Once you trigger initial synchronization, you may be surprised that synchronization does not begin immediately. A couple of things must happen before files start to move.
[BUILD1] Since DFS configuration is stored in Active Directory, DFS synchronization will not occur until all domain controllers have received the DFS settings. All domain controllers must replicate before DFS can commence.
[BUILD2] Next, each DFS member server must poll its closest domain controller to obtain these settings. The amount of time this takes will depend on your network’s Active Directory replication latency and polling interval. To move things along, you might want to trigger Active Directory synchronization through Active Directory Sites and Services.
[BUILD3] Replication proceeds outward from the primary member. Initial replication first occurs between the primary member and its receiving partners. After a member has received all files from the primary member, that member server will start replicating files to its receiving partners. For conflict resolution, any member that has completed replication is considered authoritative over one that has not.
Slide Transition: This conflict resolution is handled on each server by the Conflict and Deleted folder.
Slide Comment:
Additional Information:
3. 複寫
DFS 名稱空間
主要成員伺服器

29. Conflict and Deleted 資料夾
解決衝突
最後寫入的為主
另一份會放在 Conflict and Deleted 資料夾
Slide Title: Conflict and Deleted Folder
Keywords: DFS, Windows R2
Key Message: Conflict resolution is managed on each server in the Conflict and Deleted folder.
Slide Builds: 0
Slide Script:
DFS replication uses a "last-writer wins" method for determining which version of a file to keep when a file is modified on two or more members. The losing file is stored in the Conflict and Deleted folder on the member that resolves the conflict. This member might not be the member where the changes originated.
[BUILD1] You can also configure the service to move deleted files to the Conflict and Deleted folder for retrieval should the file or folder be deleted. This is an added protective measure that could preserve a folder or file that one user deletes but that another wants to recover.
[BUILD2]
File conflicts can occur if write permissions are set on the hub and branch servers. In this case, the quota size of the Conflict and Deleted folder should be chosen according to how much data you anticipate having to retrieve due to conflicts.
Each replicated folder has its own Conflict and Deleted folder, which is located under the local path of the replicated folder in the DfsrPrivate\ConflictandDeleted folder. The quota size of the Conflict and Deleted folder is 660 MB by default. Like the staging folder, the Conflict and Deleted folder has high and low watermarks—90 percent of the folder quota is the high and 60 percent is low—that govern cleanup and excessive usage of the folder.
The files in the Conflict and Deleted folder are renamed and are accessible only by members of the local Administrators group. The access control lists (ACLs) on the conflict files are preserved to help ensure security. You can view a log of conflict files, as well as their original file names, by viewing the ConflictandDeletedManifest.xml file in the DfsrPrivate folder.
Slide Transition: Let’s see how this works on our network.
Slide Comment: Additional Information:
保護刪除的檔案
避免意外刪除
\..\DfsrPrivate\ConflictAndDeleted
設定配額 (預設 660 MB)
本機管理者可以還原這些檔案

30. demonstration Demo 使用 DFS 建立目標資料夾 複寫目標資料夾
Slide Title: Demonstration: Using DFS
Keywords:
Key Message: Demonstration
Slide Builds: 0
Slide Script:
Now we will use DFS in our environment. We will manage folders in the DFS namespace, and then introduce targets to those folders. We will then enable replication on those folders.
Slide Transition: Here is what we have covered today.
Slide Comment:
Additional Information:

31. 總結 依據需求來設計 DFS 架構 在分支機構中使用 DFS 來為檔案服務的基礎 特別注意資料庫檔案或其它已開啟檔案的複寫問題
Slide Title: Summary
Keywords:
Key Message: Summary
Slide Builds: 2
Slide Script:
With the use of DFS Namespaces and DFS Replication you can provide consistent data across your organization including branch locations. The namespace stores the data and DFS replication makes sure that all namespace servers hosting the namespace have the same data as the data is updated.
[BUILD1]
Windows Server 2003 R2 provides the DFS Management Snap-In which allows you to manage and monitor DFS Namespaces and DFS Replication using the graphical tools. The command line tools are still available but most of the functions can be administered using the graphical interface of the snap-in.
[BUILD2]
Finally, there are several monitoring and diagnostic tools available for DFS Namespace and DFS Replication so you can make sure that they are running efficiently. Health reports and diagnostic reporting are available through the DFS Management Snap-In and Windows Server 2003 R2 adds a DFS replication management pack for MOM Additionally, by monitoring the levels of the conflict and deleted folders and the staging folders you can make sure that the data is being processed efficiently and data is being updated as necessary.
Slide Transition: To get more information on the products and technologies we have covered today, we have some online resources available that can help
Slide Comment:
Additional Information:

32. 參考資訊
Windows Server 2003 R2 分散式檔案系統 (DFS) 管理
Windows Server 2003 R2 分散式檔案系統 (DFS) 問題處理與除錯
KEY MESSAGE: For more information on this session see these web sites.
SLIDE BUILDS:
SLIDE SCRIPT:
For more information on this session see the main TechNet Web site at
Additional resources to support this Session page can be found at
SLIDE TRANSITION: For additional information on the technologies used, see these links.

33. 參考資訊 TechNet http://www.microsoft.com/taiwan/technet/default.mspx
聖哥的資訊站 teacher.allok.com.tw
KEY MESSAGE: For more information on this session see these web sites.
SLIDE BUILDS:
SLIDE SCRIPT:
For more information on this session see the main TechNet Web site at
Additional resources to support this Session page can be found at
SLIDE TRANSITION: For additional information on the technologies used, see these links.

34. Questions and Answers 請不要忘了填一下問卷 接下來即將舉行的線上課程:
/webcast/online.mspx