windows server 2008 r2 sp1 file services consolidation
DESCRIPTION
SESSION CODE: SVR311. Jeff Alexander IT Pro Evangelist Microsoft Australia http://blogs.technet.com/jeffa36 . Windows server 2008 r2 sp1 File services Consolidation. Session Objectives. Session Objective(s): - PowerPoint PPT PresentationTRANSCRIPT
WINDOWS SERVER 2008 R2 SP1 FILE SERVICES CONSOLIDATION
Jeff AlexanderIT Pro EvangelistMicrosoft Australiahttp://blogs.technet.com/jeffa36
SESSION CODE: SVR311
Session Objectives► Session Objective(s):
– Describe the technical improvements in Windows Server 2008 R2 file services, including performance, scalability and availability.
– Outline different strategies to implement name consolidation, network fault tolerance and higher availability in your file services.
– Compare a few recommended Windows Server 2008 R2 consolidated file services configurations.
Agenda
Scenario Overview
File Server Scalability and Performance
File Server Name Consolidation
File Server Advanced Networking
File Server High Availability
Summary and Questions
Scenario Overview► File Servers are being consolidated
(as are many other services out there) ► Consolidation will lead you to more
shares running in fewer servers► More shares and users per server calls
for higher scalability and performance
► Users want assurances that:– Servers can deliver on scalability and
performance– Path to files do not change with consolidation– Networks can scale and be fault tolerant– File Service is highly available
File ServerSprawl
File ServerConsolidation
Investmentin File ServicesTechnologies
File Server Scalability and Performance► Improvements since Windows Server 2003► Sample Configuration – 24 Spindles► Sample Configuration – 96 Spindles► Sample Configuration – 192 Spindles
Improvements since Windows Server 2003
► 8 years of innovation in File Services:– Performance – more throughput, more
users/server– Scalability – more shares, more files and more
users– WAN Efficiency – faster over high latency– Metrics – Using the File Server Capacity Tool
(FSCT)– Better together with Windows 7
► What do you need to know about moving to Windows Server 2008 R2?
SMB 2.1
File Classification Infrastructure (FCI)
DFS-N
File Services Role
DFS-R
Offline Files
Folder RedirectionCHKDSK
Storage Server
BranchCache
Failover Clustering
Robocopy
Durability
8.3 naming
Large MTU
Leasing
SMB2 and SMB 2.1 Improvements► Increased file sharing scalability
► Improved performance– Request compounding reduces “chattiness”– Asynchronous operations allow filling high latency pipelines– Larger reads/writes can fill the pipe even with significant link latency
► More secure and robust– Small command set allows quicker innovation– Stronger and more efficient signing (HMAC SHA-256 replaces MD5)– Network fault tolerance with SMB2 durability
► SMB 2.1 improvements– Large MTU support– Leasing improvements
Limits SMB1 SMB2Number of users Max 2^16 Max 2^64
Number of open files Max 2^16 Max 2^64
Number of shares Max 2^16 Max 2^32
Total SMB1 SMB2Opcodes >100 19
Make sure you’re running the right version…
Windows Vista,
Windows Server 2003, and prior operating systems
Windows Vista SP1+ andWindows Server 2008
Windows 7 andWindows Server 2008 R2
Windows Vista, Windows Server 2003, and
prior operating systemsSMB 1 SMB 1 SMB 1
Windows Vista SP1+ and Windows Server 2008 SMB 1 SMB 2 SMB 2
Windows 7 and Windows Server 2008 R2 SMB 1 SMB 2 SMB 2.1
If you’re running Windows Server 2003 or Windows XP, you‘re not using SMB2
CHKDSK ImprovementsHo
urs
Files on Volume (Millions)
100 200 3000
5
10
15
20
25
30 Windows Server 2008Windows Server 2008 R2
5 10 150
100
200
300
400
500
600
Seco
nds
Volume Size (TB)
Less than 7 minutes to CHKDSK a 15 TB volume with
10 million files
CHKDSK time vs. number files per volume CHKDSK time vs. volume size (10 million files)
New white paper on CHKDSK available!
Less than 2 hours to CHKDSK a volume
with 100 million files
Important note: CHKDSK scales with the number of files in the volume, not the size of the volume.
8.3 naming disabling and stripping
Create0
500
1000
1500
2000
2500
3000
3500
40003573
48 61
8dot3 enabled8dot3 disabled8dot3 stripped
seco
nds
Creating 100K files in a 1M files directory
Enumerate0
50
100
150
200
250
300
249 251
25
seco
nds
Directory enumeration with 1M files directory
Huge benefits in file creation performance with 8.3 naming
disabling or stripping
For enumeration, you need 8.3 naming stripping to see performance benefits
DFS Namespace Scalability
► Dramatic improvement in WS 2008 compared to WS 2003 (standalone namespaces)► Additional performance for very large namespaces (300,000+ links) (both modes)► Windows Server 2008 R2 test run with up to 1.3 million (!) links per namespace
0 100,000 200,000 300,000 400,000 500,0000.0
0.5
1.0
1.5
2.0
Standalone Namespace
WS2003WS2008WS2008 R2
Number of links (thousands)Aver
age
link
crea
tion
time
(sec
onds
)
0
200,000
400,000
600,000
800,000
1,000,000
1,200,0000.00.51.01.52.0
2008 Mode Domain Namespace
WS2008WS2008 R2
Number of links (thousands)Aver
age
link
crea
tion
time
(sec
onds
)*http://www.snia.org/events/storage-developer2009/presentations/wednesday/SaadAnsari-Hasegawa_Barreto_DFS-N_Overview-rev.pdf
Improved performance with Standalone
Namespaces
Even better performance with
2008-mode Domain Namespaces
Multi-threaded ROBOCOPY
► With multiple threads, ROBOCOPY is much faster on WAN connections► Syntax: robocopy /mt:128 /log:nul
1 2 4 8 16 1280%
10%20%30%40%50%60%70%80%90%
256KB:200
Number of threads
% o
f tim
e co
mpa
red
to E
xplo
rer
drag
& d
rop file size : # files
Not
e: low
er is
bett
er
Performance increase with multiple threads
Scalability Improvement Over Time
Running on server hardware “typical” of release date (~$3,000 configuration with 12 disks on RAID-0)
400
800
1200
1600
2000
2400
2800
3200
3600
4000
4400
4800
0
50100
150
200
250
300
350
400450
0%10%20%30%40%50%60%70%80%90%100%
Windows 2003 throughputWindows 2008 throughputWindows 2008 R2 throughputWindows 2003 CPUWindows 2008 CPU
Number of users
FSCT
Sce
nario
Thr
ough
put
CPU
util
izati
on
WS2008 3,200 users
WS2003 1,200 users
WS2008 R24,400 users
Bottlenecked on disk I/O
Sample Configuration – 24 spindles
10002000
30004000
50006000
70008000
0
100
200
300
400
500
600
700
800
W2K8R2
W2K8+SP2
Number of Users
Scen
ario
Thr
ough
put
WS 2008 R2
7500+ Users
WS 2008 SP2
4500+ Users
Bottlenecked on disk I/O
Operating System WS 2008 SP2 WS 2008 R2
Users 4,500 7,500
CPU: 1 x X5560 2.8GHz 11.22% 28.40%
Memory: 16GB 44% 58%
Disks: 24 RAID-10, HBA: 1 x 8Gb FC 112 MB/s 167 MB/s
Network: 1 x 10G 121 MB/s 183 MB/s
Sample Configuration – 96 spindles
10002000
30004000
50006000
70008000
900010000
1100012000
1300014000
1500016000
1700018000
0
200
400
600
800
1000
1200
1400
1600
1800
W2K8R2W2K8+SP2
Number of Users
Scen
ario
Thr
ough
put
WS 2008 SP2
7500+ Users
WS 2008 R2
16500+ Users
Bottlenecked on controller I/O
Operating System WS 2008 SP2 WS 2008 R2
Users 7,500 16,500
CPU: 2 x X5560 2.8GHz 12.90% 48.30%
Memory: 72GB 17% 17%
Disks: 96 RAID-10, HBA: 2 x 8Gb FC 179 MB/s 419 MB/s
Network: 1 x 10G 197 MB/s 457 MB/s
Sample Configuration – 192 spindles!
New White Paper with these FSCT results available!
1500016000
1700018000
1900020000
2100022000
2300024000
2500026000
2700028000
0
500
1000
1500
2000
2500
0
10
20
30
40
50
60
70
80
Number of Users
Scen
ario
Thr
ough
put
CPU
Utiliz
ation
WS 2008 R2
23,000 users (!)
Bottleneck on ?
Operating System WS 2008 R2
Users 23,000
CPU: 2 x X5560 2.8GHz 63.10%
Memory: 72GB 23%
Disks: 192 RAID-10, HBA: 4 x 8Gb FC 601 MB/s
Network: 2 x 10G 650 MB/s
File Server Name Consolidation► The name problem► Static DNS Entries► Alternate Computer Names and Dynamic DNS► DFS Consolidation Roots► Virtual Machines► Failover Clusters
The Name Consolidation ProblemFILE1
Orders
Sales
FILE2
Training
Software
FILE3
Engineering
Sales
CFILE
Orders
Sales
Training
Software
Engineering
Sales2
\\FILE1\Orders\\FILE1\Sales
\\FILE2\Training\\FILE2\Software
\\FILE3\Engineering\\FILE3\Sales
\\CFILE\Orders\\CFILE\Sales
\\CFILE\Training\\CFILE\Software
\\CFILE\Engineering\\CFILE\Sales2
The goal is to consolidate the file servers and keep the same UNC path
Static DNS Entries► Create A record (or CNAME
record if using DHCP) in DNS for each consolidate file server
► All shares will show under any of the names or IP addresses
DNSCMD dc1.contoso.local /RecordAdd contoso.local File1 A 192.168.1.11DNSCMD dc1.contoso.local /RecordAdd contoso.local File2 A 192.168.1.11DNSCMD dc1.contoso.local /RecordAdd contoso.local File3 A 192.168.1.11
Each consolidated file server shows as an A record in DNS
Alternate Computer Names and Dynamic DNS
NETDOM COMPUTERNAME cfile /ADD file1.contoso.localNETDOM COMPUTERNAME cfile /ADD file2.contoso.localNETDOM COMPUTERNAME cfile /ADD file2.contoso.localIPCONFIG /registerdns
► Create alternate computer names for each of the consolidated file server
► All shares will show under any of the names or IP addresses
Each consolidated file server shows as an alternate
computer name
DFS Consolidation Roots
DFSUTIL ROOT ADDSTD \\cfile\#file1DFSUTIL ROOT ADDSTD \\cfile\#file2DFSUTIL ROOT ADDSTD \\cfile\#file3
► Create a consolidated DFS Namespace Root for each of the consolidated file server
► Create links to the old shares in each DFS Namespace
► Each share shows only under the specific namespace
► Automate the process using FSMT► http://support.microsoft.com/kb/829885
Each consolidated file server is mapped to a new
DFS namespace root
DFS Consolidation Roots Wizard Start
Configure DFS
DFS root folder?
Old server names? Wizard Finish
DFS Server name?
File Server Migration Toolkit 1.2
File Server Migration Toolkit
demo
Virtual Machines► Create one VM per
consolidated file server► Use a matching
computer name and even a matching IP address
► Leverage Physical to Virtual (P2V) tools
Each consolidated file server shows as virtual machine
Failover Clusters► Create one clustered file
service (cluster group) per consolidated file server
► Use a matching name and even a matching IP address
Each consolidated file server shows as cluster file service
File Server Advanced Networking► DNS Round Robin► SMB2 Durability► Multiple IP addresses per cluster name► NIC Teaming► Sample Multi-NIC File Server Configurations
DNS Round Robin• Multiple NICs in the file server• File server IP addresses are registered with
the DNS server • When a client queries the name, it gets an
ordered list of IP addresses that is reordered by the DNS server with every request
• File server clients favor the first IP address in the list received from the DNS server
• If several clients access the file server by that DNS name, they tend to be distributed across the multiple IP addresses evenly
FILE1192.168.1.1/24
192.168.2.1/24
192.168.3.1/24
DNS
Router
FILE1192.168.1.1192.168.2.1192.168.3.1
CLIENT1
CLIENT2
CLIENT3
FILE1192.168.1.1
192.168.2.1192.168.3.1
FILE1192.168.3.1
192.168.1.1192.168.2.1
FILE1192.168.2.1
192.168.3.1192.168.1.1
SMB2 Durability• Multiple NICs in the file server• SMB client receive a list of IP addresses from the DNS server• SMB client connects to one of them• Upon network failure, handles survive• SMB2 client will try to reconnect, maybe using another NIC
• Requires SMB2 (durable handles are default)• Opportunistic in nature (no guarantees)• Oplocks (opportunistic locks) are required for reconnection• Other SMB clients can break oplocks
Server
SMB
Network Interfaces
Potential NetworkFailure
SMB2 Durability
Copy starts, Network1 is used
Network1 disconnected, SMB2 uses etwork3
Network3 disconnected, SMB2 uses Network2
DNS reports multiple IP addresses for the file server
Multiple IP addresses per cluster nameMultiple cluster networks
enabled for public access
Multiple IP addresses for each cluster name defined
Multiple NICs DNS Round RobinSMB2 Durability
demo
NIC Teaming• Several Physical NICs grouped into one
Logical NIC• Also known as “Link Aggregation” or
“Load Balancing and Fail-Over” (LBFO)• Available from most NIC vendors
including Intel, Broadcom and HP
• Support is provided by the NIC vendor(See Microsoft KB 254101 and 968703)
Server
SMB
Network Interfaces
Potential NetworkFailure
NIC Teaming
Make sure you have the latest versions of the vendor’s drivers
Sample Multi-NIC File Server Configurations
a) Standalone, single switch, single client NIC – 2nd NIC disabledb) Standalone, single switch, single client NIC – NIC teamingc) Standalone, single switch, single client NIC – same subnetd) Standalone, multiple switches, single client NICe) Standalone, router, single client NICf) Standalone, multiple switches, multiple client NICsg) Cluster, router, single client NICh) Cluster, multiple switches, multiple client NICs
Switch
File Server
Client 1
192.168.1.21/24
192.168.1.1/24
DisabledClient 2
192.168.1.22/24
4.5a. Standalone, single switch, single client NIC – 2nd NIC disabled
Second NIC on the file server is wasted :-(
Switch
File Server
Client 1
192.168.1.21/24
Client 2
192.168.1.22/24
4.5b. Standalone, single switch, single client NIC – NIC teaming
NIC Teaming192.168.1.1/24
NIC Teaming requires a third-party solution (from NIC vendor)
Switch
File Server
Client 1
192.168.1.21/24
192.168.1.1/24
192.168.1.2/24Client 2
192.168.1.22/24
4.5c. Standalone, single switch, single client NIC – same subnet
Multiple NICs on the same computer on the same subnet is not a supported configuration.See http://support.microsoft.com/kb/175767
File Server
4.5d. Standalone, multiple switches, single client NIC
Switch 1 192.168.1.1/24
192.168.2.1/24Switch 2
Client 1
192.168.1.21/24
Client 2
192.168.2.21/24
Each NIC on the server supports a different set of clients.Load is not balanced between NICs.
File Server
4.5e. Standalone, router, single client NIC
192.168.1.1/24
192.168.2.1/24
Client 1
10.1.1.21/24
Client 2
10.1.2.21/24
Switch 1
Switch 2Rout
erSwitch 3
Switch 4
Ideal for standalone multi-NIC file server with single-NIC file clients.Could be combined with NIC teaming on the file server side.
File Server
4.5f. Standalone, multiple switches, multiple client NICs
192.168.1.1/24
192.168.2.1/24
Server 1
Server 2
192.168.1.21/24
192.168.2.21/24
192.168.1.22/24
192.168.2.22/24
Switch 1
Switch 2
Router
To client networks…
Ideal for standalone multi-NIC file server with multi-NIC file clientsTypical scenario is an application server (like SQL Server) using SMB2Could be combined with NIC teaming on both sides
File Server 1
4.5g. Cluster, router, single client NIC192.168.1.1/24
192.168.2.1/24
File Server 2
192.168.1.2/24
192.168.2.2/24
File
Ser
vice
A
192.168.1.11192.168.2.11
File
Ser
vice
B192.168.1.12
192.168.2.12
Client 1
10.1.1.21/24
Client 2
10.1.2.21/24
Switch 1
Switch 2Rout
erSwitch 3
Switch 4
Ideal for clustered multi-NIC file server with single-NIC file clientsCould be combined with NIC teaming on the file server side.
Router
File Server 1
4.5h. Cluster, multiple switches, multiple client NICs
Switch 1
192.168.1.1/24
192.168.2.1/24
Switch 2
Server 1
Server 2
192.168.1.21/24
192.168.2.21/24
192.168.1.22/24
192.168.2.22/24
File Server 2
192.168.1.2/24
192.168.2.2/24
File
Ser
vice
A
192.168.1.11192.168.2.11
File
Ser
vice
B
192.168.1.12192.168.2.12
To client networks…
Ideal for clustered multi-NIC file server with multi-NIC file clientsTypical scenario is an application server like SQL Server using SMB2Could be combined with NIC teaming on both sides
File Server High Availability► Multi-Site DFS and Offline Files► Single-Site DFS► Cluster – Active/Passive vs. Multi-Active► File Server Cluster – FC SAN► File Server Cluster – SAS Array► File Server Cluster – iSCSI SAN► Virtual File Server with DFS► Virtual File Server – Host Cluster► Virtual File Server – Guest Cluster
Multi-site DFS and Offline Files► Two File Servers (1 in HQ, 1 in branch)► Distributed File System Namespaces
(DFS-N)► Distributed File System Replication (DFS-
R)► Client-side Caching (CSC), a.k.a. Offline
Files
► No open file replication► Potential replication delay between sites► Potential replication conflicts► Does not replace regular backups
ServerHQ
SMB DFS-NDFS-R
DAS
ServerBO
SMB DFS-NDFS-RDAS
Client
CSC
Potential HostFailure
Potential HostFailure
Potential ClientFailure
Single-site DFS► Two File Servers► Directly Attached Storage (DAS)► Distributed File System Namespaces (DFS-N)► Distributed File System Replication (DFS-R)► Single-site with high/low priority targets
(use DFS-N Target Prioritization)► Low priority shares defined as read-only
(make read/write manually upon failure)
► No open file replication► Non-replicated data lost if main file server fails► Does not replace regular backups
Server1 Server2
SMB DFS-N
DFS-RDFS-R
Network Interfaces
SMB DFS-N
DASDAS
DASDAS
Read-Only
Potential HostFailure
File Servers plus DFS
DFS Server:Target priority
is defined
DFS Client: Prioritized Target
is used
Cluster - Active/Passive vs. Multi-ActiveClient
Switch
FS1 = 10.1.1.1
Shared Storage
FS2 = 10.1.1.2
Name=FSAIP=10.1.1.3
Active
Share1Share2
1 service, 1 nameActive/Passive
2 volumes, 4 shares
\\FSA\Share1\\FSA\Share2\\FSA\Share3\\FSA\Share4
No overload on failureEasier to manage
Single name
Passive
Share3Share4
Client
Switch
Shared Storage
Name=FSAIP=10.1.1.3
Share1Share2
2 services, 2 namesDual Active2 volumes, 4 shares
\\FSA\Share1\\FSA\Share2\\FSB\Share3\\FSB\Share4
No idle nodes
Share3Share4
Name=FSBIP=10.1.1.4
FS1 = 10.1.1.1 FS2 = 10.1.1.2
File Server Cluster – FC SAN• Two Nodes with Windows
Server Failover Clustering (WSFC)
• Shared Storage• FC Array with dual
controllersController 1
Node1 Node2
Controller 2
FC Switch FC Switch
FC Array
FC HBAFC HBA
WSFC SMBWSFC SMB
Network InterfacesPotential Host
Failure
File Server Cluster – SAS Array• Two Nodes with
Windows Server Failover Clustering (WSFC)
• Shared Storage• SAS Array with dual
controllersController 1
Node1 Node2
Controller 2
SAS Array
SAS HBASAS HBA
WSFC SMBWSFC SMB
Network InterfacesPotential Host
Failure
File Server Cluster – iSCSI SAN• Two Nodes with
Windows Server Failover Clustering (WSFC)
• Shared Storage• iSCSI Array with dual
controllers Controller 1
Node1 Node2
Controller2
Switch Switch
iSCSI Array
WSFC SMBWSFC SMB
Network Interfaces
iSCSI NetworkInterfaces
iSCSI Initiator iSCSI Initiator
Potential HostFailure
File Server Cluster – iSCSI SAN
Running now on CONTOSO-S4
File Serviceis Highly Available
File share iscalled Reviews
Using Cluster Disk 2 as Shared
Storage
Access path is\\CONTOSO-FS\Reviews
Two potential
nodes
Virtual File Server – DFS ► Two Virtual File Servers► Directly Attached Storage (DAS)► DFS Namespaces (DFS-N)► DFS Replication (DFS-R)► Single-site with high/low priority targets
(use DFS-N Target Prioritization)► Low priority shares defined as read-only
(make read/write manually upon failure)
► No open file replication► Non-replicated data lost if main file server
fails► Does not replace regular backups
Hyper-V 1 Hyper-V 2
VM1 with File Server
VM2 with File Server
SMB DFS-N
DFS-RDFS-R
Network Interfaces
SMB DFS-N
Read-Only
Potential HostFailure
Shared Storage
Virtual File Server, Host Cluster► File Server in a Virtual
Machine► Two Hyper-V Nodes with
Failover Clustering► Various Options for Shared
Storage
VM withFile Server
WSFC SMB
Network Interfaces
Hyper-V 1 Hyper-V 2
WSFC
Potential HostFailure
Virtual File Server, Host ClusterVirtual Machine is Highly
Available
File Service and File Shares in the VM
(not visible here)
Virtual File Server, Guest Cluster► Two VMs in different Hyper-V
nodes► File Servers in the VMs in a
Failover Cluster► Shared Storage► iSCSI Array with dual
controllers
► Not available for FC Array
iSCSI NetworkInterfaces
Hyper-V 1 Hyper-V 2
Controller 1
Node1 Node2
Controller 2
Switch Switch
iSCSI Array
WSFC SMBWSFC SMB
iSCSI Initiator iSCSI Initiator
Network Interfaces
Potential HostFailure
Virtual File ServersGuest ClusteriSCSI SAN
demo
Related FeaturesOffline Files, Folder Redirection, Roaming user profiles
BranchCache
File Classification Infrastructure
Heterogeneity (NFS) improvements
Windows Server power optimizations
File Server Resource Management toolkit
In Review: Session Objectives► Session Objective(s):
– Describe the technical improvements in Windows Server 2008 R2 file services, including performance, scalability and availability.
– Outline different strategies to implement name consolidation, network fault tolerance and higher availability in your file services.
– Compare a few recommended Windows Server 2008 R2 consolidated file services configurations.
Resources► Blogs► http://blogs.technet.com/b/josebda/► http://blogs.technet.com/b/filecab/
Enrol in Microsoft Virtual Academy TodayWhy Enroll, other than it being free?The MVA helps improve your IT skill set and advance your career with a free, easy to access training portal that allows you to learn at your own pace, focusing on Microsoft technologies.What Do I get for enrolment?► Free training to make you become the Cloud-Hero in my Organization► Help mastering your Training Path and get the recognition► Connect with other IT Pros and discuss The Cloud
Where do I Enrol?www.microsoftvirtualacademy.com Then tell us what you think. [email protected]
