Building Branch Office DFS and FRS Replication using Windows Server 2003 R2 Michael Kleef IT Pro Evangelist Microsoft Corporation SVR309

Agenda AssumptionsOverview 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 FRSv2 FRS is still there! For SYSVOL system functions Bandwidth throttling Scheduling Remote Differential Compression (RDC) Auto Journal Wrap Error Recovery Must have R2 on both ends to fully work!

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

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 16KB for a 3.5MB PPT Install AdminPak onto a 2.6 GB VHD. RDC Sync traffic is 7.6MB, vs 12 MB file size of installer RDC Efficiency (1-RDCBytes/Total compressed Bytes)*100 Connection Type Save full 3.5MB ppt Save only changes 56 kbps modem 10 minutes 3 seconds 500 kbps DSL 70 seconds <1 second

Enabling Technology RDC reduction factors Bandwidth Reduction Factors: RDC vs. Full File Transfer VSD 318 K.DOC 489 K.DOC 2.6 M.MPP241K.PPT594K.XLS2.4M.ZIP348K.HTM425K.PPT3.9M.PST293M

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

Enabling Technology RDC example Original file Updated file The quick fox jumped over the lazy brown dog. the fox jumping over him. “The brown dog was” “so lazy that he …”copy MD4 21 MD4 22 MD4 23 MD4 24 MD4 25 MD4 11 MD4 12 MD4 13 MD4 14 The quick fox jumped over the lazy brown dog. The dog was so lazy that he didn’t notice the fox jumping over him. The quick fox jumped over the lazy brown dog. The brown dog was the fox jumping over him. so lazy that he didn’t notice The quick fox jumped over the lazy brown dog. The brown dog was the fox jumping over him. so lazy that he didn’t notice [use recursion] ClientServer Request file MD4 21 … MD4 25 Fetch new chunks 3, 4

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 ReplicatedFolderRoot\DfsrPrivate\ConflictManifest.xml Conflict is a local directory in DfsrPrivate 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 Staging is to decouple the replicator from the file- system Data is compressed and placed in a staging area from where it is served on the outbound. By default staging under DfsrPrivate\Staging 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 512MB 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 SP1 Management Servers must run R2 All DC’s must run Windows Server 2003 with SP1 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 SP1 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 R2 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 R2DPS 2005 Product goalsGeneral purpose replicatorData Protection (files) DeliveryIn Windows OSApplication ScenariosPublication/distribution Collect data to central server Failover support?YesNo Hub availabilityVia replicated hubs or tape b/uUse tape archive add-on Cross domain?Replicates within forestReplicates within domain TopologiesAnyStar (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 supportFiles replicated on close (note: PST files close after 15m) Files replicated even while open Replication granularityReplicates differences between files when updates occur Replicates write traffic when writes occur

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

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

Resources DFS Home Page: Branch Office Home Page: Windows Server 2003 R2: 3/r2/default.mspx 3/r2/default.mspx Has the Reviewers Guide Beta 2 Signup

We invite you to participate in our online evaluation on CommNet, accessible Friday only If you choose to complete the evaluation online, there is no need to complete the paper evaluation Your Feedback is Important!

© 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 User in LA Branch User in London Branch Server in LA Branch Server in London Branch DFS Namespace Server in New York Hub DFS Replication 3X

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

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