WSV 317 R File Server Sprawl File Server

WSV 317 -R

File Server Sprawl File Server Consolidation Investment in File Services Technologies

SMB 2. 1 DFS-R Failover Clustering File Services Role Offline Files CHKDSK Folder Redirection DFS-N Durability Branch. Cache Leasing Robocopy Large MTU Storage Server File Classification Infrastructure (FCI) 8. 3 naming

Limits SMB 1 SMB 2 Number 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 SMB 1 SMB 2 Opcodes >100 19

Windows Vista, Windows Server 2003, and prior operating systems Windows Vista SP 1+ and Windows Server 2008 Windows 7 and Windows Server 2008 R 2 Windows Vista, Windows Server 2003, and prior operating systems SMB 1 Windows Vista SP 1+ and Windows Server 2008 SMB 1 SMB 2 Windows 7 and Windows Server 2008 R 2 SMB 1 SMB 2. 1 If you’re running Windows Server 2003 or Windows XP, you‘re not using SMB 2

CHKDSK time vs. number files per volume 30 Windows Server 2008 R 2 500 Less than 2 hours to CHKDSK a volume with 100 million files 400 New white paper on CHKDSK available! 10 Seconds Hours 15 600 Windows Server 2008 25 20 CHKDSK time vs. volume size (10 million files) 300 5 100 0 0 100 200 300 Files on Volume (Millions) Less than 7 minutes to CHKDSK a 15 TB volume with 10 million files 200 5 10 15 Volume Size (TB) Important note: CHKDSK scales with the number of files in the volume, not the size of the volume.

4000 3573 8 dot 3 enabled 8 dot 3 disabled 3500 250 249 251 8 dot 3 stripped 3000 2500 150 2000 1500 Huge benefits in file creation performance with 8. 3 naming disabling or stripping 1000 500 48 61 0 Create For enumeration, you need 8. 3 naming stripping to see performance benefits 100 50 25 0 Enumerate

2008 Mode Domain Namespace 2, 0 1, 5 Improved performance with Standalone Namespaces 1, 0 WS 2003 WS 2008 R 2 0, 5 0, 0 0 100 200 300 Number of links (thousands) 400 500 Average link creation time (seconds) Standalone Namespace 2, 0 1, 5 WS 2008 1, 0 WS 2008 R 2 0, 5 0, 0 0 200 400 600 800 Number of links (thousands) 1 000 1 200 Even better performance with 2008 -mode Domain Namespaces *http: //www. snia. org/events/storage-developer 2009/presentations/wednesday/Saad. Ansari-Hasegawa_Barreto_DFS-N_Overview-rev. pdf

% of time compared to Explorer drag & drop Note: lower is better 90% 80% 70% 60% file size : # files 50% 256 KB: 20 0 40% 1 MB: 50 30% 20% 10% 0% 1 2 4 8 Number of threads 16 128 Performance increase with multiple threads

WS 2008 R 2 4, 400 users 450 100% 90% 400 WS 2008 3, 200 users 70% 300 Windows 2008 throughput Windows 2008 R 2 throughput Windows 2003 CPU Windows 2008 CPU 60% 250 WS 2003 1, 200 users 50% 200 CPU utilization 40% 150 30% 100 20% Number of users 48 00 46 00 44 00 42 00 40 00 38 00 36 00 34 00 32 00 30 00 28 00 26 00 24 00 22 00 20 00 18 00 00 16 14 00 12 00 80 60 10 00 0% 0 0 0 10% 0 50 40 FSCT Scenario Throughput 350 80% Windows 2003 throughput Windows 2008 R 2 CPU

WS 2008 R 2 800 7500+ Users 700 Scenario Throughput 600 500 400 W 2 K 8 R 2 WS 2008 SP 2 W 2 K 8+SP 2 4500+ Users 300 200 100 0 00 10 00 20 0 0 30 0 0 40 0 0 50 Number of Users 00 00 60 70 00 80 Operating System WS 2008 SP 2 WS 2008 R 2 4, 500 7, 500 11. 22% 28. 40% 44% 58% Disks: 24 RAID-10, HBA: 1 x 8 Gb FC 112 MB/s 167 MB/s Network: 1 x 10 G 121 MB/s 183 MB/s Users CPU: 1 x X 5560 2. 8 GHz Memory: 16 GB

WS 2008 R 2 1800 16500+ Users 1600 Scenario Throughput 1400 1200 WS 2008 SP 2 1000 7500+ Users 800 600 W 2 K 8 R 2 400 200 W 2 K 8+SP 2 0 00 10 20 00 00 30 40 00 00 50 0 0 60 0 0 70 0 0 80 0 0 90 00 0 10 Number of Users 00 0 11 0 00 12 0 00 13 0 00 14 0 00 15 0 00 16 0 00 17 Operating System 0 00 18 WS 2008 SP 2 WS 2008 R 2 7, 500 16, 500 12. 90% 48. 30% 17% Disks: 96 RAID-10, HBA: 2 x 8 Gb FC 179 MB/s 419 MB/s Network: 1 x 10 G 197 MB/s 457 MB/s Users CPU: 2 x X 5560 2. 8 GHz Memory: 72 GB

WS 2008 R 2 00 25 80 23, 000 users (!) 70 20 00 50 CPU Utilization Scenario Throughput 60 0 0 15 40 10 00 30 20 50 0 10 Operating System 0 00 15 0 00 16 0 00 17 18 0 00 19 0 00 00 20 0 0 00 21 Number of Users 00 0 22 00 0 23 00 0 24 00 0 25 00 0 26 00 0 27 00 0 28 Users CPU: 2 x X 5560 2. 8 GHz Memory: 72 GB WS 2008 R 2 23, 000 63. 10% 23% Disks: 192 RAID-10, HBA: 4 x 8 Gb FC 601 MB/s Network: 2 x 10 G 650 MB/s

FILE 1 CFILE Orders Sales FILE 2 Training Software FILE 3 Engineering Sales 2 The goal is to consolidate the file servers and keep the same UNC path

Each consolidated file server shows as an A record in DNS

Each consolidated file server shows as an alternate computer name

http: //support. microsoft. com/kb/829885 Each consolidated file server is mapped to a new DFS namespace root

Wizard Start DFS Server name? Old server names? Configure DFS root folder? Wizard Finish File Server Migration Toolkit 1. 2

Each consolidated file server shows as virtual machine

Each consolidated file server shows as cluster file service

DNS • Multiple NICs in the file server • File server IP addresses are registered with the DNS server (dynamically or manually) • 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 CLIENT 1 FILE 1 192. 168. 1. 1 192. 168. 2. 1 192. 168. 3. 1 CLIENT 2 FILE 1 192. 168. 3. 1 192. 168. 1. 1 192. 168. 2. 1 FILE 1 192. 168. 1. 1/24 Router 192. 168. 2. 1/24 192. 168. 3. 1/24 CLIENT 3 FILE 1 192. 168. 2. 1 192. 168. 3. 1 192. 168. 1. 1

• 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 • SMB 2 client will try to reconnect, maybe using another NIC • Requires SMB 2 (durable handles are default) • Opportunistic in nature (no guarantees) • Oplocks (opportunistic locks) are required for reconnection • Other SMB clients can break oplocks Potential Network Failure Network Interfaces Server SMB

Network 1 disconnected, SMB 2 uses etwork 3 Copy starts, Network 1 is used DNS reports multiple IP addresses for the file server Network 3 disconnected, SMB 2 uses Network 2

Multiple cluster networks enabled for public access Multiple IP addresses for each cluster name defined

demo

• 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 Potential Network Failure • Support is provided by the NIC vendor (See Microsoft KB 254101 and 968703) Network Interfaces Server SMB

Make sure you have the latest versions of the vendor’s drivers

Client 1 192. 168. 1. 21/24 File Server Switch Client 2 192. 168. 1. 22/24 Second NIC on the file server is wasted : -( 192. 168. 1. 1/24 Disabled

Client 1 192. 168. 1. 21/24 File Server Switch Client 2 NIC Teaming 192. 168. 1. 1/24 192. 168. 1. 22/24 NIC Teaming requires a third-party solution (from NIC vendor)

Client 1 192. 168. 1. 21/24 File Server 192. 168. 1. 1/24 Switch Client 2 192. 168. 1. 2/24 192. 168. 1. 22/24 Multiple NICs on the same computer on the same subnet is not a supported configuration. See http: //support. microsoft. com/kb/175767

Client 1 192. 168. 1. 21/24 File Server Client 2 Switch 1 192. 168. 1. 1/24 Switch 2 192. 168. 2. 1/24 192. 168. 2. 21/24 Load is not balanced between NICs.

Client 1 10. 1. 1. 21/24 Switch 3 Switch 4 Client 2 10. 1. 2. 21/24 Router File Server Switch 1 192. 168. 1. 1/24 Switch 2 192. 168. 2. 1/24

To client networks… Server 1 192. 168. 1. 21/24 Router File Server 192. 168. 2. 21/24 Server 2 192. 168. 1. 22/24 192. 168. 2. 22/24 Switch 1 192. 168. 1. 1/24 Switch 2 192. 168. 2. 1/24

Switch 4 Client 2 10. 1. 2. 21/24 192. 168. 1. 11 192. 168. 2. 1/24 192. 168. 2. 11 Switch 2 192. 168. 1. 2/24 192. 168. 1. 12 192. 168. 2. 2/24 192. 168. 2. 12 File Server 2 File Service B Switch 3 Router 10. 1. 1. 21/24 File Service A File Server 1 Client 1

192. 168. 1. 21/24 192. 168. 2. 21/24 Router File Server 1 192. 168. 1. 1/24 192. 168. 1. 11 192. 168. 2. 1/24 192. 168. 2. 11 File Service A To client networks… Server 1 Switch 1 192. 168. 1. 22/24 192. 168. 2. 22/24 192. 168. 1. 12 192. 168. 2. 2/24 192. 168. 2. 12 File Server 2 File Service B Switch 2 Server 2

• 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 Potential Client Failure CSC • No open file replication • Potential replication delay between sites • Potential replication conflicts • Does not replace regular backups Client DAS DFS-R SMB DFS-N Server. BO Potential Host Failure Server. HQ Potential Host Failure DAS DFS-R SMB DFS-N

• 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) Network Interfaces Server 1 Server 2 Read-Only • No open file replication • Non-replicated data lost if main file server fails • Does not replace regular backups SMB DFS-N DFS-R DAS Potential Host Failure SMB DFS-N DFS-R DAS

DFS Client: Prioritized Target is used DFS Server: Target priority is defined

1 service, 1 name Active/Passive 2 volumes, 4 shares Client Switch FS 1 = 10. 1. 1. 1 FS 2 = 10. 1. 1. 2 Share 1 Share 2 \FSAShare 1 \FSAShare 2 \FSAShare 3 \FSAShare 4 \FSAShare 1 \FSAShare 2 \FSBShare 3 \FSBShare 4 No overload on failure Easier to manage Single name No idle nodes Client Switch FS 1 = 10. 1. 1. 1 FS 2 = 10. 1. 1. 2 Name=FSA IP=10. 1. 1. 3 Active 2 services, 2 names Dual Active 2 volumes, 4 shares Name=FSB IP=10. 1. 1. 4 Passive Share 3 Share 4 Share 1 Share 2 Shared Storage Share 3 Share 4

Network Interfaces Potential Host Failure Node 1 WSFC Node 2 SMB FC HBA FC Switch Controller 1 FC Array WSFC SMB FC HBA FC Switch Controller 2

Network Interfaces Potential Host Failure Node 1 WSFC Node 2 SMB SAS HBA Controller 1 SAS Array WSFC SMB SAS HBA Controller 2

Potential Host Failure Network Interfaces Node 1 WSFC Node 2 SMB i. SCSI Initiator WSFC SMB i. SCSI Initiator i. SCSI Network Interfaces Switch Controller 1 i. SCSI Array Switch Controller 2

File Service is Highly Available Running now on CONTOSO-S 4 Two potential nodes Using Cluster Disk 2 as Shared Storage File share is called Reviews Access path is \CONTOSO-FSReviews

Network Interfaces VM 1 with File Server VM 2 with File Server Read-Only SMB DFS-N DFS-R Hyper-V 1 • • • No open file replication Non-replicated data lost if main file server fails Does not replace regular backups SMB DFS-N DFS-R Hyper-V 2 Potential Host Failure

Network Interfaces Hyper-V 1 WSFC Potential Host Failure VM with File Server SMB Shared Storage Hyper-V 2 WSFC

Virtual Machine is Highly Available File Service and File Shares in the VM (not visible here)

Network Interfaces Potential Host Failure Hyper-V 1 Hyper-V 2 Node 1 WSFC Node 2 SMB i. SCSI Initiator WSFC SMB i. SCSI Initiator i. SCSI Network Interfaces Switch Controller 1 i. SCSI Array Switch Controller 2

demo

WSV 317 -R WSV 318 WSV 313 WSV 323 May

http: //blogs. technet. com/josebda http: //twitter. com/josebarreto

Connect. Share. Discuss. http: //northamerica. msteched. com Sessions On-Demand & Community Microsoft Certification & Training Resources www. microsoft. com/teched www. microsoft. com/learning Resources for IT Professionals Resources for Developers http: //microsoft. com/technet http: //microsoft. com/msdn

Scan the Tag to evaluate this session now on my. Tech • Ed Mobile