windows server 2003 r2 vladimír wojnar microsoft solutions centre@hp prague

Windows Server 2003 R2

Vladimír WojnarMicrosoft Solutions Centre@HPPrague

Agenda

Release CycleWindows Server™ 2003 R2

Principal ScenariosSimplified Branch Server ManagementIdentity and Access ManagementEfficient Storage Management

Windows server release cycle

UNIX UNIX

InteropInteropSP1 & x64SP1 & x64

Windows Windows SharePoint SharePoint ServicesServices

.NET .NET Framework Framework

2.02.0

Web Single Sign-on B2B/B2C Commerce and Collaboration Decentralized application directories UNIX identity management

Centralized Backup & Management of File and Print High Availability Efficient Publishing & Collaboration

Simple SAN Management for the IT Generalist File Server Resource Manager UNIX NFS Connectivity

Simplified Branch Server Management

Identity and Access Management

Efficient Storage Management

Microsoft Branch OfficeAgenda

The Branch StoryThe Branch StoryOverview - Consolidations - Challenges

Microsoft’s VisionBranch Model - Roadmap

Enabling TechnologiesRDC – Distributed File System - PMC

Usage ScenariosSummary

The Branch Story: OVERVIEW

Branch Story…Branch Story…30% of businesses have remote sites55% of LORG headcount in branch sites

(↑7% in ’03)Branches consume nearly 33% of IT budgetsLORGs spent $25B US on WANs in 2003

Achieving TCO Gains…Achieving TCO Gains…Consolidation: Do we need branch servers?Productivity vs. Performance?

Source: Microsoft ResearchSource: Microsoft Research

“The WAN is the largestrecurring cost other than

people in IS organizations.”Gartner

CONSOLIDATIONMost companies have consolidated their central serversMost companies have consolidated their central servers

Consolidation paths are clear – Windows Server 2003 scalabilityFocus shifting to branch server consolidationFocus shifting to branch server consolidation

Path is less obvious. TCO gains come with trade-offs.

Servers in branch sites?Servers in branch sites?Servers in central sites?Servers in central sites?

Low Server Management CostsLow Server Management Costs WANs Decrease Branch ProductivityWANs Decrease Branch Productivity

Bandwidth, Latency, Availability

or

Increases Branch Productivity/AutonomyIncreases Branch Productivity/Autonomy High Server Management CostsHigh Server Management Costs

Backup, recovery, repair, etc.

WAN CHALLENGES

Low bandwidth and high latencyLow bandwidth and high latencyHinders branch performance → productivityIP tuning helps, limiting round trips is vital

WAN-optimized client/server protocolsWAN-optimized client/server protocolsLAN speeds mask inefficient protocols

File (CIFS and NFS), Print, AuthenticationProtocols are evolving (R2 Extends)

HTTP, BITS, Cached Exchange Mode are WAN-ready

Branch servers mitigate WAN limitations but……Branch servers mitigate WAN limitations but……Difficult to manage, create “Mini Data-Centers”

“If the WAN was like a LAN, there would

be no problem!”

MANAGEMENT CHALLENGES

At the Branch OfficeAt the Branch OfficeOn-site “admins” scarce

Remedies pricey: “Flying Doctors” ~$140/hrData protection expensive/unreliableConsolidating multiple server roles

Difficult to maintain delegation boundaries, e.g., DCs

From Central SitesFrom Central SitesAdmins central, managing branch remotely

Offshore admins for large sites, “Follow-the-Sun” 24/7Management Tools

Lack scalability for large number of sites (Policy, Delegation)Need one-to-many tools for multi-role “cookie cutter” servers

“Branch servers are a necessary evil.”

Agenda

The Branch StoryOverview - Consolidations - Challenges

Microsoft’s VisionMicrosoft’s VisionBranch Model - Roadmap



OptionalOptionalDisposableDisposableReplaceableReplaceable

Continuity ofContinuity ofServicesServices

ServiceServiceAcceleratorAccelerator

A SERVER MANAGED AS A CACHE

Clients fail-over to a central serverClients fail-over to a central serverService cache: No unique stateService cache: No unique stateEasy to re-provision replacementsEasy to re-provision replacements

State-of-the-art compressionState-of-the-art compressionCache: Limits bandwidth usageCache: Limits bandwidth usageCache: Mitigates WAN latencyCache: Mitigates WAN latency

Cache: Local request handlingCache: Local request handlingStore-and-forward to central serverStore-and-forward to central server

A simple, self-healing, self diagnosing, “admin-free” serverA simple, self-healing, self diagnosing, “admin-free” server

ACHIEVING THE VISION: ROADMAP

WAN-Friendly File ReplicationWAN-Friendly File Replication Scalable MonitoringScalable Monitoring Centralized Printer ManagementCentralized Printer Management

R2R2

LonghorLonghornn

Workload ProvisioningWorkload Provisioning Cached AuthenticationCached Authentication Staged PatchingStaged Patching Branch SharePointBranch SharePoint Streaming MediaStreaming Media

Making Key Server Roles Branch-FriendlyMaking Key Server Roles Branch-Friendly

2006 2007

Agenda



Enabling TechnologiesEnabling TechnologiesRDC – Distributed File System - PMC


WINDOWS SERVER 2003 R2

Branch Office Features in R2Branch Office Features in R2File Server Workload

Remote Differential Compression (RDC)Distributed File System

Replication (File Replication Services 2 – FRS2)Namespace improvements Management Console

Print Server WorkloadPrint Management Console

RDC OVERVIEWBrand new “Brand new “deltadelta”-based compression algorithm”-based compression algorithm

Existing objects: Efficiently detects insertions, removals, re-arrangements of data

New objects: Efficiently discovers and reconstructs using relevant pieces of object on receiving machine

Works on any “file” type, applicable to any client/server

Generalized TechniqueGeneralized TechniqueRequires no “change tracking”Superior to RSYNC in most cases (up to 3X)

RDC – IN DEPTHOriginal file Updated file

SHA21 … SHA25

Fetch new chunks 3, 4

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

Client

SHA21

SHA22

SHA23

SHA24

SHA25

SHA11

SHA12

SHA13

SHA14

Request file The quick fox

jumped


The dog wasso lazy that he

didn’t notice




The brown dog was


so lazy that he didn’t notice



The brown dog was


so lazy that he didn’t notice

[use recursion]

The updated & original files are divided into variable-length chunks based on their The updated & original files are divided into variable-length chunks based on their contentscontents..

For each chunk on the client and server, RDC computes a strong hash (SHA).For each chunk on the client and server, RDC computes a strong hash (SHA). The server transmits the list of strong hashes to the client.The server transmits the list of strong hashes to the client.

For large files, the algorithm is applied recursively at this point.For large files, the algorithm is applied recursively at this point.

The client compares the server hashes to its own, and requests the server send only the data for hashes that don’t match.The client compares the server hashes to its own, and requests the server send only the data for hashes that don’t match.

Client assembles updated file by combining:Client assembles updated file by combining: Its own chunks whose hashes match those on the server.Its own chunks whose hashes match those on the server. The missing chunks it received from the server.The missing chunks it received from the server.

RDC EFFICIENCIESRDC speeds up network transfers by orders of RDC speeds up network transfers by orders of

magnitudemagnitudeSuperior to rsync 2.6.2 for larger filesSuperior to rsync 2.6.2 for larger files

Large File Transfers

.VHD (11.28GB)* - One day of changes to a DC

.BKF (9.0GB) - Exchange Daily Backup

.VHD (2.6GB)* - Install 12 MB admin pack on WS03 - Only 7.6 MB diff (existing DLLs)

.VHD (2.5GB)* - Add user to a Windows Server 2003 DC

* VHD’s are Virtual Server system images3 5 13 17 15 16 17

31 2435 30 38 41 34

92 87

292

151

409

141

0

50

100

150

200

250

300

350

400

450

.VSD318K

.DOC498K

.DOC2.6MB

.MPP241K

.PPT594K

.XLS2.4MB

.ZIP348K

.HTM425K

.PPT3.9MB

.PST293MB

RDC Bandwidth Reduction Factors

Microsoft RDC

rsync 2.6.2

96.07 139.1

349.66

1555.05

0

200

400

600

800

1000

1200

1400

1600

.VHD 112GB .BKF 9GB .VHD 2.6GB .VHD 2.5GB

Large Files Bandwidth Reduction Factors

DFS – OVERVIEW Capabilities

Replication: Efficient sync between servers Namespace: Virtualizes file servers Scale: Thousands of servers, cross-domain

Manageability New MMC2.1 console for DFS * Supports all topologies In-the-box HTML reports and diagnostics * MOM Management Pack *

WAN efficiency Replicate only changed parts of files (RDC) * 15 min. granularity scheduling and throttling * Route client to closest Server via DFSN Prevent branch-to-branch fail-over *

Availability Self-healing file replication algorithm * Multi-level Fail-over and Fail-back Works with Shadow Copy for Shared Folders Offline working for disconnected sites Highly available configuration store (AD) Define link target priorities within sites * Robustness and Monitoring super-important

* = New in R2

Single system – many scenarios Distribution of hub files to branches

Applications, Documents, patches, etc. Collection of files from branches to hubs

Eradicate tape backup in branch Last-writer-wins distributed file sharing

Efficiently transfer files between sites

User in New York

Server in New York

User in London

Server in London

DFS Replication

Namespace

DFS Process Description

DFS REPLICATION

Robust multi-master file replication systemRewrite from the ground upSignificantly more efficient, scalable and robust than predecessor

(File Replication Services) Key new features

Core ServiceEfficient and simple state-based synchronizationLeverages RDCBandwidth ThrottlingAutomatic DB rebuild on USN journal wrap or DB loss

New management console

DFS REPLICATION

DFS NamespaceBrand new management UI

Hierarchical view of namespaceNew features: rename links, drag n’ drop Incorporates functionality that was previously only available via

CLI

New features added to DFS Namespace Service in Server SP1Fail-backPrioritization of Target Server referrals

Set high/low priority servers

DFS NAMESPACE

Printers Node

Servers Node

Printer Management ConsoleWith PMC, branch servers can easily be print servers because they are With PMC, branch servers can easily be print servers because they are

remotely manageable on a 1-to-many basisremotely manageable on a 1-to-many basis

Agenda




Usage ScenariosUsage ScenariosSummary

DATA COLLECTION

Goal: Consolidate branch data for centralized redundancy and backup through replication

Key Requirements Branch data efficiently replicated to hub Fail-over to hub if branch server unavailable Easy recovery of branch server cache Fail-back to branch server, once it recovers

CONTENT PUBLICATION Goal: Distribute file content to a number of branch (and

hub) sites

Key RequirementsBranch data can act as caches for centrally authored dataFail-over to hubFail-back to branch server, once it recovers

Agenda




Usage ScenariosSummarySummary

SUMMARY Windows optimizing for branches and WANs R2 release provides first wave:

File and Print roles are the focusDFS Replication and RDC are key enabling technologies, used with

DFS Namespace Longhorn broadens Branch vision to more server roles

windows server 2003 r2 vladimír wojnar microsoft solutions centre@hp prague

Documents

branch sites

branch productivity

branch productivity

wanready branch servers

management challenges

microsoft branch office

clear windows server

gartner slide