1 / 51

(DEP290) Windows 2003 Server ™ New Storage features

(DEP290) Windows 2003 Server ™ New Storage features. Christophe Dubois Storage Consultant. Didier Lalli Windows Wizard. Hewlett Packard. Agenda. Understanding the Windows 2003 Server Storage Stack Enhanced Driver Model STORport & iSCSI MultiPath Driver Model (MPIO)

vita
Download Presentation

(DEP290) Windows 2003 Server ™ New Storage features

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. (DEP290)Windows 2003 Server™New Storage features Christophe DuboisStorage Consultant Didier LalliWindows Wizard Hewlett Packard

  2. Agenda • Understanding the Windows 2003 Server Storage Stack • Enhanced Driver Model STORport & iSCSI • MultiPath Driver Model (MPIO) • Volume Shadow Copy Service • Backup, Transport, Restore • Virtual Disk Service • And what about Clusters?

  3. File Systems Volume Snapshot Volume Management Windows 2003 storage stack Requestors Volume Shadow Copy Service (Point-in-time copies) Virtual Disk Service (RAID, disk access, Enclosures) Removable Storage Manager (tape and optical media management) Writers Writers User Mode SW Provider SW Provider HW Providers HW Providers Microsoft WMI HP/OEMs Kernel Mode MPIO DSM MPIO DSM DSM Class Disk Tape Changer Port IDEPort iSCSIprt ScsiPort StorPort Miniport Miniport(s) iSCSI Initiator

  4. Enhanced SAN Support STORport • Increases I/O performance: • Removes workarounds for legacy devices • 8-30% improvement in I/O rates, lower CPU utilization • Supports 255 I/Os per LUN • Adds functionality: • Support for LUN Resets (SAN friendly!) • Good for FC nearline storage & Clustering • Support for more Fibre Channel capabilities • Allows boot and tape devices on same data path as shared cluster disks • Support more devices (>2048 LUNs)

  5. Microsoft iSCSI Support • Adds support for native iSCSI toWindows Server 2003, 2000 and XP • Initial iSCSI package will be “OOB” but is still considered part of Windows • Will be inbox for all future OS releases • Initial delivery vehicle will be Windows Download • iSCSI initiator package • iSNS Server package

  6. iSCSI • What is it ? • iSCSI is internet SmallComputer System Interface • Internet Protocol (IP)-based storage networking standard for linking data storage devices • Carries SCSI commands over IP networks • How does it work ? • encapsulate SCSI cmds and data requests into IP packets • commands sent to SCSI/FC controller, and then to the SCSI/FC storage device. Generally via an iSCSI router

  7. iSCSI cont. • What does it mean to me ? • iSCSI can be used to transmit data over • local area networks • wide area networks • or the Internet • can enable location-independent data storage and retrieval

  8. FC & IP Storage Network Hosts with iSCSI drivers Fibre Channel Storage Systems Microsoft and HP deliver this today! FibreChannel EthernetTCP/IP iSCSIRouters

  9. iSCSI vs. NAS? • Cannot really directly compare the two • NAS uses file • iSCSI uses blocks (like fiber channel) • Exchange is supported using iSCSI, NAS is currently not • Complementary – NAS can be a front end for iSCSI • iSCSI does not replace fileservers (or NAS) • Files are natural units of operation for end users • Security and sharing of files is easier

  10. MULTIPATH DRIVER MODEL (MPIO) • What is it? • The ability to use more than one physical path to access a storage device, providing improved system reliability and availability via fault tolerance and/or load balancing of the I/O traffic • Why is Microsoft doing this? • Microsoft's Multi Path I/O delivers a standard and interoperable path for communication between storage products and Windows Servers • Enables multi-vendor storage configurations

  11. MULTIPATH DRIVER MODEL (MPIO) • What does it mean to HP? • HP is working closely with Microsoft to develop an MPIO solution for HP arrays. Secure Path may adopt this technology in future releases.

  12. Vendor ships MPIO Solutions • Solutions available only from vendors • Not part of the operating system • Requires Device Specific Modules (DSMs) • Each storage device has different behaviors and features • Not always possible to identify device down each path • i.e active/passive controller failover • Generic support is not possible without tradeoff

  13. overview. . . Volume Shadow Copy Service

  14. What is a Shadow Copy ? • Known in the industry as Snapshots, split-mirrors or Clones • Appears static, even though the original data is changing • Can be done at the file system level or LUN level in external arrays

  15. F: Volume Map Seconds Copy on Write Snapshot Area Step 2 Retrieve Original and Unchanged data Snapshot E: Volume Map Step 1 Logical Volume the result is an identical logical copy within seconds

  16. Clone: Split Mirror E: Block for Block Copy Logical Volume Cloned Volume Unavailable Step 1 Mirror Link 40-140GB Hour Logical Volume Cloned Volume Step 2 Mirror Link X Seconds Identical Copies Logical Volume Cloned Volume Available Step 3 F:

  17. Clone: SnapClone E: Copy on Write Logical Volume Cloned Volume Step 1 Mirror Link Seconds Background Block for Block Copy Cloned Volume Logical Volume Available Step 2 Mirror Link X F: 40-140GB Hour Identical Copies Logical Volume Cloned Volume Step 3 Starts as a Snapshot and becomes a clone over time

  18. Introduction to VSS • Provides a framework on Windows 2003 Enterprise Edition and Data Center Edition • Simple and consistent method to create a point-in-time copy of a single volume or multiple volumes with control of the applications and stores • Provides unified view for backup applications in a heterogeneous SAN environment

  19. Shadow Copy For BackupWhat problems does VSS solve? • For Backup Applications: • No easy way for applications to describe their data to backup apps • Excessive number of APIs to deal with • For Data: • Some transaction only exist in filesystem OS cache or application memory pages • An application can modify a file while it is being backed-up causing data corruption or a file open error

  20. Current SAN management reality Each array type within a SAN environment requires it’s own management tool/API IBMtool/API HPQtool/API EMCtool/API HDStool/API Heterogeneous SAN

  21. Volume Shadow Copy Service Enables a large heterogeneous SAN to be managed via ONE volume copy management solution Microsoft VSS framework Heterogeneous SAN

  22. VSS Framework • Within VSS there is the concept of a “Framework”. • The Framework can be compared to an air traffic control center - through which all coordination from the various components must travel through

  23. VSS Components • Requestors: Apps that initiate the request to VSS to create a shadow copy of the volume(s) • Ex: Traditional backup application • Writers: Apps that change/manipulate data and respond to VSS signals • Ex: MS SQL Server, MS Exchange 2003 • Providers: Interface to the disk array to create Volume Shadow copies on behalf of the VSS Framework • Ex: Hewlett-Packard EVA VSS Hardware Provider

  24. FilesComponents Settings FilesComponents Settings FilesComponents Settings State Restore Z: Writer Metadata How does it work together ? Backup Application Volume Shadow Copy Service SQL Requestor Exchange IIS • Veritas • Legato • HP • Commvault • Dantz • Ultrabac • Others… Windows ServicesAD, Registry, etc… VSSProviders F: Writer • Win2003 (volsnap.sys) • HP (EVA, VA, XP) • EMC, HDS • Others...

  25. Shadow Copy Transport • Enables you to easily transport data and volumes on your SAN • Create and export a shadow copy of your data volume or database • Import that shadow copy and data on a second server • Requires a provider for the SAN array • HP released compatible VSS hardware providers for EVA, VA, XP arrays

  26. EXC DBs 100 GB EXC DBs ‘ 100 GB EXC Logs 50 GB EXC Logs ‘ 50 GB Shadow Copy Transport Backup Server Exchange Server HP StorageWorks EVA Multiple LUNs shadow copied at single point-in-time with data consistency

  27. Shadow Copy Transport • What are the scenarios? • Make a copy of your database for data mining on another server • Offload backups to another server • Make a copy of your production database for testing purposes • Keep a copy of your data around for fast recovery

  28. Fast Recovery Solutions 2003 • A requestor application focused at the application administrators (Exchange / SQL). • Easy to use with a GUI and a Command Line Interface for scheduling options. • Uses the VSS framework to create VSS LUNs for recovery, however these VSS LUNS could be used for other purposes (backup to tape, Exchange 2003 – Mail Box recovery…etc) • Fast Recovery Solutions is tuned for the HP arrays for performance and features. Currently supports the EVA,XP and VA arrays.

  29. Fast Recovery Solutions 2003 • Fast Recovery Solutions 2003 will be available this fall. EVA and XP beta customer application process will start on August 18, 2003. • For additional details contact Rudy Castillo at rudy.castillo@hp.com

  30. Shadow Copy Restore • New Feature for Windows 2003 Server • Allows users to see network folder contents at points-in-time in the past • Uses system provider included with Windows Server 2003 • Supports Cluster configurations • Reduces users’ dependence on busy administrators • Not a replacement for Archive or Business Recovery! Empower users to undo their own mistakes

  31. introduction. . . Virtual Disk Service

  32. VDS: What is it ? • VDS provides a single interface for managing storage on Windows 2003 • VDS provides a vendor and technology neutral interface for logical volume management • VDS enables management of heterogeneous storage systems. • VDS leverages both client and provider APIs. • Focus is virtualization and innovation in hardware for auto-management

  33. VDS Components

  34. VDS Hardware Provider • Operates on LUNs and drives • The physical hardware associated with a hardware provider is a “subsystem” • A subsystem can be internal or external • Example: hardware provider + PCI controller = internal subsystem • Example: hardware provider + Fiber channel array = external subsystem • HP released providers for EVA, XP, VA disk arrays

  35. VDS Software Provider • Comes with OS • Disk Manager Service in Windows 2003 uses VDS • Operates on LUNs and disks (JBOD) • Only host-based • No associated hardware • Note: VDS does NOT coordinate with applications on file systems like VSS

  36. And what about Clusters? • Cluster setup • AD Integration • Majority Node Set Resources • Generic Script Resource DLL • WMI Support • And many other miscellaneous things I have to tell you…

  37. Cluster Setup • Very different! • Part of the OS install, just need to be configured • All done from CluAdmin.exe • Step1: Add Cluster to turn standalone system into Single Node Cluster • Step2: Add additional nodes • Wizards helps with checking the feasibility. • No reboot required • Node can be evicted as easily and join another cluster

  38. Cluster Setup PM Demo

  39. AD Integration • Virtual Server can be published in AD • Property of the Network Name resource in the virtual server • Also DNS registration can be enforced for IP address of virtual servers

  40. AD Integration PM Demo

  41. Majority Node Set Resource • Quite a big change! • Quorum capable resource stored on each nodes local disk • Use SMB hidden share to count votes • (1 server = 1 vote always!) • Changes “split-brain” logic • now needs (number of node configured / 2) + 1 to survive • Can build a cluster with no shared storage • Good for “stretch cluster” coupled with storage-based data replication across geographically dispersed sites • Can change cluster from Disk Quorum to MNS Quorum

  42. Data Data Dispersed Cluster Example Site 1 Site 2 Site 3 Disaster Disaster Disaster Node2 Node1 Node3 Node4 Node5 Quorum Quorum Quorum Quorum Quorum Controller based Replication

  43. Generic Script Resource DLL • New way to make application “Cluster Aware” • Generic Script resource requires: • Main routine • 7 methods: • Open() • Online() • LooksAlive()  Must return True or False • IsAlive()  Must return True or False • Offline()  Graceful shutdown • Close() • Terminate()  Immediate shutdown • Functions can be empty! • For example in %WinDir%\System32\inetsrv\ • Clusweb.vbs • Clusftp.vbs

  44. FUNCTION LooksAlive( ) DIM objWmiProvider DIM objService DIM strServiceState SET objWmiProvider = GetObject("winmgmts:/root/cimv2") SET objService = objWmiProvider.get("win32_service='w3svc'") strServiceState = objService.state IF ucase(strServiceState) = "RUNNING" THEN LooksAlive = True ELSE LooksAlive = False END IF END FUNCTION Function Open( ) REM put open code here End Function Function Online( ) REM put online code here End Function Function Offline( ) REM put offline code here End Function Function Close( ) REM put close code here End Function Function Terminate( ) REM put terminate code here End Function Function LooksAlive( ) REM put LooksAlive code here LooksAlive = End Function Function IsAlive( ) REM put IsAlive code here IsAlive = End Function REM put main code here Generic Script Resource DLLPM Demo

  45. WMI Support • New WMI Provider • Old Cluster API still exists but is in maintenance mode • The cluster WMI name space is: \\root\MSCluster (e.g: GetObject("winmgmts://./root/MSCluster") • Exposes 36 classes: • 2 super classes • 9 main classes • 17 association classes • 7 event classes • 2 reserved for future use

  46. SET Events = GetObject("winmgmts://./root/MSCluster"). _ ExecNotificationQuery( "Select * from _ MSCluster_EventStateChange" ) DO SET Item = Events.NextEvent WScript.Echo( DATE & " " & TIME & _ " EventNewState=" & Item.EventNewState & _ " EventObjectName=" & Item.EventObjectName & _ " EventObjectPath=" & Item.EventObjectPath & _ " EventObjectType=" & Item.EventObjectType & _ " EventTypeMajor=" & Item.EventTypeMajor & _ " EventTypeMinor=" & Item.EventTypeMinor ) LOOP => Monitor State change of any event wmic /namespace:\\root\mscluster /output:c:\resource.htm path mscluster_resource get name,state /format:htable /every:300 => Maintains a WEB page with resource information in a table format and refreshes every 5 minutes. WMI Support PM Demo

  47. And many other miscellaneous things I have to tell you… • 8 Nodes support • 64-bit support • Mountpoints support • Backup system state support • Volume Shadow Copy support • Improved Clustered Print Queues • Password Change Utility • MSDTC is now a real resource • Multicast support for heartbeat/regroup traffic

  48. Oops, I forgot… • No more IIS, SMTP and NNTP support • Sample Generic Resource VB script for IIS and FTP • No Dynamic Disks support • No real security settings • Still need nodes in same subnet

  49. Community Resources • Community Resources http://www.microsoft.com/communities/default.mspx • Most Valuable Professional (MVP) http://www.mvp.support.microsoft.com/ • Newsgroups Converse online with Microsoft Newsgroups, including Worldwide http://www.microsoft.com/communities/newsgroups/default.mspx • User Groups Meet and learn with your peers http://www.microsoft.com/communities/usergroups/default.mspx

  50. evaluations

More Related