Simplifying SAN Deployments on Windows

1. Simplifying SAN Deploymentson Windows Patrick Stirrat Lead Program Manager, Storage Partners Windows Server Division pstirrat @ microsoft.com Microsoft Corporation

2. Session Outline • Market trends • SAN deployment inhibitors • Windows Simple SAN Partner program • Goals • Structure • Benefits • Simple SAN program bottom line • Call to Action • Questions

3. Session Goals • Attendees should leave this session with the following understanding: • Windows Storage market trends • SAN deployment blockers • Windows Simple SAN program • Goals & Objectives • Program Structure • Requirements • Windows Simple SAN Call to Action

4. Windows Storage Market Trends • Movement from direct tofabric attached storage • Declining disk prices • Higher capacity drives • Lower cost consumer drivetechnologies • Emergence of low cost switches, HBAs • Maturity of iSCSI • According to IDC 2004, Windows is the number one platform for storage for all metrics (total storage, external and RAID) • The forecast (IDC) is for Windows to overtake Unix as the leader in hosting Fibre Channel SAN storage in 2005

5. SAN Growth Inhibitors • In 2002, IDC survey respondents predicted an adoption rate that was much higher than subsequently occurred • Why have potential SAN buyers not followed through? Source: Networked Storage Opportunities—Fibre Channel, iSCSI and Converged SANs. IDC, 2004

6. Customers are Ready for SAN Benefits… • Many IT administrators are at a “tipping” point with respect to the SAN purchase • Overwhelmed by trying to manage storage • Need the flexibility and benefits of SAN solutions • Want to start small and migrate storage • Want lower costs

7. ...But Aren’t Ready for SAN Complexity • What SAN capabilities do customers want from vendors? Among business with 10-19 servers: (N=54) Source: Networked Storage Opportunities—Fibre Channel, iSCSI and Converged SANs. IDC, 2004

8. Windows Simple SAN Partner Program • Program Goals • Program Structure • Benefits

9. Program Goals • Help provide Windows customers withsimplified SAN solutions that are: • Easy to deploy • Serviceable • Robust • Provide the programmatic framework tohelp meet customer needs by: • Helping drive partnerships among SAN vendors • Providing a Simple SAN program that guides the development of simpler SAN components and solutions • Supports both FC and iSCSI SANs

10. Program Structure • Designation: “Compatible with Windows Simple SAN” • Not administered by WHQL • Partners can leverage existing WHQL (Designed For Windows) qualifications • “Hard” Requirements • Can be explicitly evaluated and validatedvia specific metrics • “Soft” Requirements • Includes Out Of Box Experience, quality of documentation, other non-“Designed for Windows” logo tests • Some metrics • Evaluation by Microsoft’s technical andbusiness management

11. Program Structure (cont) • Component submissions • Individual SAN components can earn “Compatible with Windows Simple SAN” designation: HBA, Switch, Array, etc. • Solution submissions • Complete solutions are a superset of components that meet the “Compatible with Windows Simple SAN” requirements, and have additional requirements • Online Submission Tool • Partners apply online for Components and Solutions • Evaluation & approval by Microsoft’s technical andbusiness management • Solution showcase for approved components and solutions

12. Simple SAN Categories Solution Components Storage Array HBA (FC & iSCSI) FC Switch Storage Provisioning Backup/Quick Restore Tape Drive/Library Multipath Solution Clustering Security Complete Solution Out-of-Box Experience Documentation Serviceability Interoperability

13. Component: Storage Array “Hard” Supports either Fibre Channel or iSCSI protocols Must include VDS provider (recommend VDS v 1.1; required 9 months after ships) Must support LUN reset Must pass SCSI compliance tests Solution must not depend on filter drivers Drivers must be upgradeable to future versions of the Windows Server OS If a multipathing solution is implemented, it must use Microsoft MPIO “Soft” VSS provider implemented Supports Shadow Copy transport for some scenarios Indicate when multipathing solutions are appropriate (using scenarios, for example)

14. Component: FC HBA “Hard” Supports either Fibre Channel or iSCSI protocols Solutions must not depend on filter drivers Drivers must not compromise upgrading to future versions of the Windows Server OS Fibre Channel Must use Storport miniport drivers (with WMI support for HBA API) Default configuration must be fabric (auto topology okay as long as fabric is used) Must support LUN reset “Soft” Simplified configuration Automatic configuration preferred

15. Component: iSCSI HBA “Hard” Supports either Fibre Channel or iSCSI protocols Solutions must not depend on filter drivers Drivers must not compromise upgrading to future versions of the Windows Server OS iSCSI Must use Storport miniport drivers Must support LUN reset iSCSI software initiator must use the Microsoft iSCSI software initiator “Soft” Simplified configuration Automatic configuration preferred

16. Component: FC Switch “Hard” Must support fabrics only (no FC-AL solutions) Must support FC-GS-3 or later Switch must operate in “open mode” (that is, must be interoperable, not proprietary) “Soft” Installation scheme should be easy Include configuration poster Use a single HBA per zone If serial port configuration is required, include cabling

17. Component: Storage Provisioning “Hard” Must use VDS provider “Soft” Need simple (max half-dozen steps) setup process Can use in-box UI (Storage Manager for SANs)

18. Component: Backup/Quick Restore “Hard”If snapshot capability is implemented: Must be based on VSS Must support Shadow Copy transport Exchange restore solution must be compatible with KB article 822896 “Soft” Should work in cluster configurations

19. Component: Tape Drive or Library “Hard” Tape/library driver must comply with HCT v12.1 or later Drivers must follow Microsoft driver model for tape and changers (must be implemented as mini-drivers, as per Windows DDK) Must support Storport driver “Soft” None

20. Component: Security “Hard”If implementing iSCSI: Must support CHAP “Soft” None

21. Complete Solution Requirements:

22. Simple SAN Requirements: Bottom Line • Microsoft will promote and feature Simple SAN solutions that consist of components that are Simple SAN Approved • Partners submit their products through a partner web site: http://www.microsoftstoragepartners.com/SolutionShowcase/default.asp

23. Call to Action • Obtain “Designed for Windows” Logo for products • Submit component for “Compatible with Windows Simple SAN” designation • Submit solution for “Compatible with Windows Simple SAN” designation • http://www.microsoftstoragepartners.com/SolutionShowcase/default.asp

24. Community Resources • Windows Hardware & Driver Central (WHDC) • www.microsoft.com/whdc/default.mspx • Technical Communities • www.microsoft.com/communities/products/default.mspx • Non-Microsoft Community Sites • www.microsoft.com/communities/related/default.mspx • Microsoft Public Newsgroups • www.microsoft.com/communities/newsgroups • Technical Chats and Webcasts • www.microsoft.com/communities/chats/default.mspx • www.microsoft.com/webcasts • Microsoft Blogs • www.microsoft.com/communities/blogs