SVR 309 Building Branch Office DFS and FRS

SVR 309 Building Branch Office DFS and FRS Replication using Windows Server 2003 R 2 Michael Kleef IT Pro Evangelist Microsoft Corporation

Agenda Assumptions Overview Process Description Scenarios DFS-R and RDC Internals Configuration and Migration Demo: Configuration Extra bits!

Assumptions You understand all the current DFS/FRS issues Journal Wraps Lack of bandwidth control Etc

DFS Overview DFS is now called DFS Namespaces Virtual tree of folders Failover and redundancy FRS is now called DFS Replication (DFS-R) Was called FRSv 2 FRS is still there! For SYSVOL system functions Bandwidth throttling Scheduling Remote Differential Compression (RDC) Auto Journal Wrap Error Recovery Must have R 2 on both ends to fully work!

DFS Process Description 2 User Server in LA Branch 1 DFS Replication Server in New York Hub 3 DFS Namespace 4 User Server in London Branch

DFS Main Scenarios Data centralisation Elimination of tape backup in branches Client Failover/Failback Data written at the branch replicated to central Note: Requires client hotfix

DFS Main Scenarios Data Distribution Delivery of common data to sites Ideal for software distribution Auto server referral within AD Site Cost based for external sites Prestage of content is supported! Target Priority

DFS Main Scenarios Branch Office Data Replication Users roam from branch to branch Map to a single folder namespace Multiple concurrent changes not a good idea - Last writer wins!

DFS-R and RDC Internals

RDC Efficiency Examples Insert this text into PPT file only requires 16 KB for a 3. 5 MB PPT Connection Type Save full 3. 5 MB ppt Save only changes 56 kbps modem 10 minutes 3 seconds 500 kbps DSL 70 seconds <1 second Install Admin. Pak onto a 2. 6 GB VHD. RDC Sync traffic is 7. 6 MB, vs 12 MB file size of installer RDC Efficiency (1 -RDCBytes/Total compressed Bytes)*100

Enabling Technology RDC reduction factors Bandwidth Reduction Factors: RDC vs. Full File Transfer 450 409 400 350 292 300 250 200 150 92 100 50 3 13 15 31 30 41 . PPT 594 K . XLS 2. 4 M . ZIP 348 K 17 0. VSD 318 K . DOC 489 K . DOC 2. 6 M . MPP 241 K . HTM 425 K . PPT 3. 9 M . PST 293 M

Replication Operation Create / Modify file NTFS Drive FRS learns of file changes from the NTFS “USN Change journal” Filter out unwanted files NTFS Drive Rename file into final location Write entry in DFSR ID table Rebuilds file in pre-install dir Write entry in DFSR ID Table DB notifies Sync with Change in VV, ages 3 s VV exchange, Sends updates Fetches (staging) file Request file Sync Receives update, compare with DB

Enabling Technology RDC example Client Original file MD 411 The quick fox jumped MD 412 over the lazy brown dog. MD 413 The dog was so lazy that he didn’t notice MD 414 the fox jumping over him. Server Updated file copy The quick fox jumped Request file MD 421 … MD 425 Updated file The quick fox jumped MD 421 over the lazy brown dog. [use recursion] over the lazy brown dog. MD 422 The brown dog was Fetch new chunks 3, 4 The brown dog was MD 423 so lazy that he didn’t notice “The brown dog was” so lazy that he didn’t notice MD 424 the fox jumping over him. “so lazy that he …” the fox jumping over him. MD 425

RDC Demo Change a file, monitor the traffic!

Conflict Resolution Uses logical clocks and the USN time Different for files and directories: Last writer for files Earliest Creator for directories Types of Conflicts Name Conflict Update Conflict Replicated. Folder. RootDfsr. PrivateConflict. Manifest. xml Conflict is a local directory in Dfsr. Private Losing content lives only on the machines that handled the conflict. DFS Replication is intended for content that is not modified simultaneously since: It does not support distributed locks. Read only content – single master Loose collaboration with local copies– Read/write content Branch scenarios where WAN reliability and bandwidth are concerns and tight consistency is not.

Staging is to decouple the replicator from the filesystem Data is compressed and placed in a staging area from where it is served on the outbound. By default staging under Dfsr. PrivateStaging RDC hashes are computed on the staged data Staging is cleaned up lazily by an age heuristic when the high watermark is reached Staging limit is not a hard quota, files will continue to be staged over the limit if space on the staging volume is available With large data best to keep staging on a separate volume from data

Self Healing NTFS journal can wrap if changes happening rapidly and replication cannot keep up. Default size is 512 MB Replication will automatically recover from journal wrap Replication will also automatically recover from database loss or corruption by recreating DB Alternate pair-wise sync algorithm also exists to fixup issues with respect to normal sync

Configuration and Migration

DFS Configuration DFS Namespaces All servers must be running Windows Server 2003 SP 1 Management Servers must run R 2 All DC’s must run Windows Server 2003 with SP 1 Namespaces must be created on NTFS volumes All clients that support namespaces work Caveat: Only clients running the following client failback hotfix can be configured for client failback: Windows® XP with Service Pack 2 and the Windows XP Client Failback hotfix. Windows Server 2003 SP 1 and the Windows Server 2003 Client Failback hotfix. (This hotfix does not yet have a release date. )

DFS Configuration DFS–R Extend Active Directory schema Windows Server 2003 R 2 required Install DFS Replication Service on each server that will take part in replication Install the DFS Management snap-in on one server Antivirus software must be compatible with DFS Replication Servers in a replication group must be in the same forest Replicated folders must be stored on NTFS volumes. NOTE: DFS-R is not for SYSVOL – do not disable FRS for DC’s.

DFS Configuration DFS–R Prestage content if necessary! Make a Replication group Add members Apply Schedule/Bandwidth controls Choose folders Apply filters Publish to DFS Namespace (if exists)

DFS Configuration Namespace and DFS-R

Extra bits!

What do I use? DFS Replication or SC Data Protection Server? DFS Replication in R 2 DPS 2005 Product goals General purpose replicator Data Protection (files) Delivery In Windows OS Application Scenarios Publication/distribution Collect data to central server Failover support? Yes No Hub availability Via replicated hubs or tape b/u Use tape archive add-on Cross domain? Replicates within forest Replicates within domain Topologies Any Star (production server to DPS) Shadow copy integration Compatible with Shadow Copy Restore Extends Shadow Copy restore Network types supported LAN WAN (even poor WANs) LAN WAN (better WANs…) Open file support Files replicated on close (note: PST files close after 15 m) Files replicated even while open Replication granularity Replicates differences between files when updates occur Replicates write traffic when writes occur

Monitoring DFS in R 2 Microsoft Operations Manager (MOM) DFS Namespace management pack released DFS Replication management in Beta Event based management pack

DFS Replication Roadmap Release Roadmap 2007 2006 ►Windows Server “Longhorn” with DFS Replication for SYSVOL and DFS replicas ►Windows Server “Longhorn” Beta 2 2005 2004 ►Windows Server: Codename “Longhorn” Beta 1 ►Windows Server 2003 Update: Codename “R 2” with DFS Replication ►Windows Server 2003 for 64 -Bit Extended Systems ►Windows Server 2003 Service Pack 1 ►Additional Feature Packs (e. g. Windows Update Services)

Resources DFS Home Page: http: //www. microsoft. com/dfs Branch Office Home Page: http: //www. microsoft. com/branchoffice Windows Server 2003 R 2: http: //www. microsoft. com/windowsserver 200 3/r 2/default. mspx • Has the Reviewers Guide • Beta 2 Signup

We invite you to participate in our online evaluation on Comm. Net, accessible Friday only If you choose to complete the evaluation online, there is no need to complete the paper evaluation

© 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

DFS Scenario: Publication 2 User in LA Branch Server in LA Branch 1 DFS Replication Server in New York Hub 1 DFS Namespace 2 User in London Branch 3 X Server in London Branch

DFS Scenario: Data Collection Backup Application Collection Server In Hub DFS Namespace 3 DFS Replication 1 4 2 User in London Branch X Server in London Branch Backup Application

DFS Scenario: Roaming User Documents 2 User Server in LA Branch 1 DFS Replication Server in New York Hub 3 DFS Namespace 4 User Server in London Branch