Building Branch Office DFS Building Branch Office DFS and FRS Replication using and FRS Replication using Windows Server 2003 R2 Windows Server 2003 R2
Michael KleefMichael KleefIT Pro EvangelistIT Pro EvangelistMicrosoft CorporationMicrosoft Corporation
SVR309
AgendaAgenda
AssumptionsAssumptions
OverviewOverview
Process DescriptionProcess Description
ScenariosScenarios
DFS-R and RDC InternalsDFS-R and RDC Internals
Configuration and MigrationConfiguration and Migration
Demo: ConfigurationDemo: Configuration
Extra bits!Extra bits!
AssumptionsAssumptions
You understand all the current You understand all the current DFS/FRS issuesDFS/FRS issues
Journal WrapsJournal Wraps
Lack of bandwidth controlLack of bandwidth control
EtcEtc
DFS DFS OverviewOverview
DFS is now called DFS NamespacesDFS is now called DFS NamespacesVirtual tree of foldersVirtual tree of foldersFailover and redundancyFailover and redundancy
FRS is now called DFS Replication (DFS-R)FRS is now called DFS Replication (DFS-R)Was called FRSv2Was called FRSv2FRS is still there! For SYSVOL system FRS is still there! For SYSVOL system functionsfunctionsBandwidth throttlingBandwidth throttlingSchedulingSchedulingRemote Differential Compression (RDC)Remote Differential Compression (RDC)Auto Journal Wrap Error RecoveryAuto Journal Wrap Error Recovery
Must have R2 on both ends to fully work!Must have R2 on both ends to fully work!
DFS DFS Process DescriptionProcess Description
UserUser Server inServer inLA BranchLA Branch
Server inServer inLondon BranchLondon Branch
DFS NamespaceDFS Namespace
22
44
UserUser
11
33
Server in Server in New York HubNew York Hub
DFS ReplicationDFS Replication
DFSDFSMain ScenariosMain Scenarios
Data centralisationData centralisationElimination of tape backup in branchesElimination of tape backup in branches
Client Failover/FailbackClient Failover/Failback
Data written at the branch replicated to Data written at the branch replicated to centralcentral
Note: Requires client hotfixNote: Requires client hotfix
DFSDFSMain ScenariosMain Scenarios
Data DistributionData DistributionDelivery of common data to sitesDelivery of common data to sites
Ideal for software distributionIdeal for software distribution
Auto server referral within AD SiteAuto server referral within AD Site
Cost based for external sitesCost based for external sites
Prestage of content is supported!Prestage of content is supported!
Target PriorityTarget Priority
DFSDFSMain ScenariosMain Scenarios
Branch Office Data ReplicationBranch Office Data ReplicationUsers roam from branch to branchUsers roam from branch to branch
Map to a single folder namespaceMap to a single folder namespace
Multiple concurrent changes not a good Multiple concurrent changes not a good idea - Last writer wins!idea - Last writer wins!
DFS-R and RDC InternalsDFS-R and RDC Internals
RDC EfficiencyRDC EfficiencyExamplesExamples
Insert Insert this textthis text into PPT file only requires into PPT file only requires 16KB for a 3.5MB PPT16KB for a 3.5MB PPT
Install AdminPak onto a 2.6 GB VHD.Install AdminPak onto a 2.6 GB VHD.RDC Sync traffic is 7.6MB, vs 12 MB file size of RDC Sync traffic is 7.6MB, vs 12 MB file size of installerinstaller
RDC Efficiency (1-RDCBytes/Total RDC Efficiency (1-RDCBytes/Total compressed Bytes)*100compressed Bytes)*100
Connection TypeConnection Type Save full 3.5MB pptSave full 3.5MB ppt Save only changesSave only changes
56 kbps modem56 kbps modem 10 minutes10 minutes 3 seconds3 seconds
500 kbps DSL500 kbps DSL 70 seconds70 seconds <1 second<1 second
Enabling TechnologyEnabling TechnologyRDC reduction factorsRDC reduction factors
Bandwidth Reduction Factors: RDC vs. Full File Transfer
409409
400400
350350
300300
250250
200200
150150
100100
5050
00
292292
9292
41413030313117171515131333
450450
.VSD.VSD318 K318 K
.DOC.DOC489 K489 K
.DOC.DOC2.6 M2.6 M
.MPP.MPP241K241K
.PPT.PPT594K594K
.XLS.XLS2.4M2.4M
.ZIP.ZIP348K348K
.HTM.HTM425K425K
.PPT.PPT3.9M3.9M
.PST.PST293M293M
Replication OperationReplication Operation
Create / Modify file
NTFS Drive
Request file Sync Receives update, compare with DB
Filter out unwanted files
Write entry in DFSR ID TableFetches (staging) file
Rebuilds file in pre-install dir
Rename file into final locationWrite entry in DFSR ID table
DB notifies Sync with Change in VV, ages 3 sVV exchange, Sends updates
NTFS Drive FRS learns of file changes from
the NTFS “USN Change journal”
Enabling TechnologyEnabling TechnologyRDC exampleRDC example
Original fileOriginal file Updated fileUpdated fileUpdated fileUpdated file
The quick fox The quick fox jumpedjumped
over the lazy over the lazy brown dog.brown dog.
the fox the fox jumping over jumping over
him.him.
“The brown dog was”
“so lazy that he …”
copycopy
MD4MD42121
MD4MD42222
MD4MD42323
MD4MD42424
MD4MD42525
MD4MD41111
MD4MD41212
MD4MD41313
MD4MD41414
The quick fox The quick fox jumpedjumped
over the lazy over the lazy brown dog.brown dog.
The dog wasThe dog wasso lazy that he so lazy that he didn’t noticedidn’t notice
the fox the fox jumping over jumping over
him.him.
The quick fox The quick fox jumpedjumped
over the lazy over the lazy brown dog.brown dog.
The The brownbrown dog wasdog was
the fox the fox jumping over jumping over
him.him.
so lazy that he so lazy that he didn’t noticedidn’t notice
The quick fox The quick fox jumpedjumped
over the lazy over the lazy brown dog.brown dog.
The The brownbrown dog wasdog was
the fox the fox jumping over jumping over
him.him.
so lazy that he so lazy that he didn’t noticedidn’t notice
[use recursion]
Client Server
Request file
MD421 … MD425
Fetch new chunks 3, 4
RDC DemoRDC DemoChange a file, monitor the traffic!Change a file, monitor the traffic!
Conflict ResolutionConflict ResolutionUses logical clocks and the USN time Uses logical clocks and the USN time Different for files and directories:Different for files and directories:
Last writer for filesLast writer for filesEarliest Creator for directories Earliest Creator for directories
Types of ConflictsTypes of ConflictsName Conflict Name Conflict Update Conflict Update Conflict
ReplicatedFolderRoot\DfsrPrivate\ConflictManifest.xmlReplicatedFolderRoot\DfsrPrivate\ConflictManifest.xmlConflict is a local directory in DfsrPrivateConflict is a local directory in DfsrPrivate
Losing content lives only on the machines that handled the Losing content lives only on the machines that handled the conflict.conflict.
DFS Replication is intended for content that is not modified DFS Replication is intended for content that is not modified simultaneously since: simultaneously since:
It does not support distributed locks.It does not support distributed locks.Read only content – single masterRead only content – single masterLoose collaboration with local copies– Read/write content Loose collaboration with local copies– Read/write content Branch scenarios where WAN reliability and bandwidth Branch scenarios where WAN reliability and bandwidth are concerns and tight consistency is not.are concerns and tight consistency is not.
StagingStagingStaging is to decouple the replicator from the file-Staging is to decouple the replicator from the file-system system
Data is compressed and placed in a staging area Data is compressed and placed in a staging area from where it is served on the outbound. By default from where it is served on the outbound. By default staging under DfsrPrivate\Stagingstaging under DfsrPrivate\Staging
RDC hashes are computed on the staged data RDC hashes are computed on the staged data
Staging is cleaned up lazily by an age heuristic when Staging is cleaned up lazily by an age heuristic when the high watermark is reachedthe high watermark is reached
Staging limit is not a hard quota, files will continue Staging limit is not a hard quota, files will continue to be staged over the limit if space on the staging to be staged over the limit if space on the staging volume is availablevolume is available
With large data best to keep staging on a separate With large data best to keep staging on a separate volume from datavolume from data
Self HealingSelf Healing
NTFS journal can wrap if changes happening rapidly NTFS journal can wrap if changes happening rapidly and replication cannot keep up. Default size is and replication cannot keep up. Default size is 512MB512MB
Replication will automatically recover from journal Replication will automatically recover from journal wrapwrap
Replication will also automatically recover from Replication will also automatically recover from database loss or corruption by recreating DB database loss or corruption by recreating DB
Alternate pair-wise sync algorithm also exists to Alternate pair-wise sync algorithm also exists to fixup issues with respect to normal sync fixup issues with respect to normal sync
Configuration and MigrationConfiguration and Migration
DFS ConfigurationDFS ConfigurationDFS NamespacesDFS Namespaces
All servers must be running Windows Server 2003 All servers must be running Windows Server 2003 SP1SP1Management Servers must run R2Management Servers must run R2All DC’s must run Windows Server 2003 with SP1All DC’s must run Windows Server 2003 with SP1Namespaces must be created on NTFS volumesNamespaces must be created on NTFS volumesAll clients that support namespaces workAll clients that support namespaces workCaveat: Only clients running the following client Caveat: Only clients running the following client failback hotfix can be configured for client failback:failback hotfix can be configured for client failback:
Windows® XP with Service Pack 2 and the Windows XP Windows® XP with Service Pack 2 and the Windows XP Client Failback hotfix. Client Failback hotfix. Windows Server 2003 SP1 and the Windows Server 2003 Windows Server 2003 SP1 and the Windows Server 2003 Client Failback hotfix. (This hotfix does not yet have a Client Failback hotfix. (This hotfix does not yet have a release date.)release date.)
DFS ConfigurationDFS ConfigurationDFS–RDFS–R
Extend Active Directory schema Extend Active Directory schema Windows Server 2003 R2 requiredWindows Server 2003 R2 requiredInstall DFS Replication Service on each Install DFS Replication Service on each server that will take part in replicationserver that will take part in replicationInstall the DFS Management snap-in on one Install the DFS Management snap-in on one server server Antivirus software must be compatible with Antivirus software must be compatible with DFS ReplicationDFS ReplicationServers in a replication group must be in the Servers in a replication group must be in the same forestsame forestReplicated folders must be stored on NTFS Replicated folders must be stored on NTFS volumes.volumes.NOTE: DFS-R is not for SYSVOL – do not NOTE: DFS-R is not for SYSVOL – do not disable FRS for DC’s.disable FRS for DC’s.
DFS Configuration DFS Configuration DFS–RDFS–R
Prestage content if necessary!Prestage content if necessary!
Make a Replication groupMake a Replication group
Add membersAdd members
Apply Schedule/Bandwidth controlsApply Schedule/Bandwidth controls
Choose foldersChoose folders
Apply filtersApply filters
Publish to DFS Namespace (if exists)Publish to DFS Namespace (if exists)
DFS ConfigurationDFS ConfigurationNamespace and DFS-RNamespace and DFS-R
Extra bits!Extra bits!
What do I use?What do I use?DFS Replication or SC Data Protection Server?DFS Replication or SC Data Protection Server?
DFS Replication in R2 DPS 2005
Product goals General purpose replicator Data Protection (files)
Delivery In Windows OS Application
Scenarios Publication/distributionCollect data to central server
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
LANWAN (even poor WANs)
LAN WAN (better WANs…)
Open file support Files replicated on close(note: PST files close after 15m)
Files replicated even while open
Replication granularity
Replicates differences between files when updates occur
Replicates write traffic when writes occur
Monitoring DFS in R2Monitoring DFS in R2Microsoft Operations Manager (MOM)Microsoft Operations Manager (MOM)
DFS Namespace management pack DFS Namespace management pack releasedreleased
DFS Replication management in BetaDFS Replication management in BetaEvent based management packEvent based management pack
20042004
20052005
20062006
20072007
►Windows Server 2003 for 64-Bit Extended Systems Windows Server 2003 for 64-Bit Extended Systems ►Windows Server 2003 Service Pack 1Windows Server 2003 Service Pack 1►Additional Feature Packs (e.g. Windows Update Services)Additional Feature Packs (e.g. Windows Update Services)
►Windows Server: Codename “Longhorn” Windows Server: Codename “Longhorn” Beta 1Beta 1
►Windows Server 2003 Update: Codename “R2” with Windows Server 2003 Update: Codename “R2” with DFS Replication DFS Replication
►Windows Server “Longhorn” Windows Server “Longhorn” Beta 2Beta 2
►Windows Server “Longhorn” with DFS Replication for Windows Server “Longhorn” with DFS Replication for SYSVOL and DFS replicasSYSVOL and DFS replicas
Release Roadmap
DFS Replication RoadmapDFS Replication RoadmapDFS Replication RoadmapDFS Replication Roadmap
ResourcesResources
DFS Home Page: http://www.microsoft.com/dfs
Branch Office Home Page: http://www.microsoft.com/branchoffice
Windows Server 2003 R2: http://www.microsoft.com/windowsserver2003/r2/default.mspx
•Has the Reviewers Guide
•Beta 2 Signup
We invite you to participate in ourWe invite you to participate in our online evaluationonline evaluation on CommNet,on CommNet,
accessible Friday onlyaccessible Friday only
If you choose to complete the evaluation online, If you choose to complete the evaluation online, there isthere is no need to complete the paper evaluationno 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: PublicationDFS Scenario: Publication
User inUser inLA BranchLA Branch
User inUser inLondon BranchLondon Branch
Server inServer inLA BranchLA Branch
Server inServer inLondon BranchLondon Branch
DFS NamespaceDFS Namespace
22
22
11
11
Server in Server in New York HubNew York Hub
DFS ReplicationDFS Replication
33
XX
DFS Scenario: Data DFS Scenario: Data CollectionCollection
User inUser inLondon BranchLondon Branch
Collection Server Collection Server In HubIn Hub
DFS NamespaceDFS Namespace DFS ReplicationDFS Replication
Server inServer inLondon BranchLondon Branch
11
22
33
XX44BackupBackup
ApplicationApplication
BackupBackupApplicationApplication
DFS Scenario: Roaming DFS Scenario: Roaming User DocumentsUser Documents
UserUser Server inServer inLA BranchLA Branch
Server inServer inLondon BranchLondon Branch
DFS NamespaceDFS Namespace
22
44
UserUser
11
33
Server in Server in New York HubNew York Hub
DFS ReplicationDFS Replication