INTRODUCING FILE AREA NETWORKS - SNIA
INTRODUCINGFILEAREANETWORKSFIRST EDITIONYour first look at FAN technologyMICHAEL O’CONNOR & JOSH JUDD
Copyright 2007 Brocade All rights reserved.Brocade and the Brocade B-wing symbol are registered trademarks of BrocadeCommunications Systems, Inc., in the United States and other countries. Allother brands, products, or service names are or may be trademarks or servicemarks of, and are used to identify, products or services of their respectiveowners.No part of this book shall be reproduced or transmitted in any form or by anymeans, electronic, mechanical, magnetic, photographic includingphotocopying, recording or by any information storage and retrieval system,without express prior written permission from Brocade. No patent liability isassumed with respect to the use of the information contained herein. Althoughevery precaution has been taken in the preparation of this book, the publisher,the author, and Brocade assume no responsibility for errors or omissions.Neither is any liability assumed for damages resulting from the use of theinformation contained herein. This material is subject to change withoutnotice.Brocade Bookshelf TM Series designed by Josh JuddIntroducing File Area NetworksWritten by Michael O’Connor and Josh JuddEdited by Victoria Thomas, Kent Hanson, and Josh JuddDesign and Production by Victoria ThomasIllustrations by David LehmannPrinting HistoryAdvance Edition in March 2007First Edition in May 2007Published by:1094 New Dehaven St.West Conshohocken, PA hing.comwww.BuyBooksOnTheWeb.comToll-free: (877) BUY-BOOKLocal Phone: (610) 941-9999Fax: (610) 941-9959iiIntroducing File Area Networks
Important NoticeUse of this book constitutes consent to the following conditions. This book issupplied “AS IS” for informational purposes only, without warranty of any kind,expressed or implied, concerning any equipment, equipment feature, orservice offered or to be offered by Brocade. Brocade reserves the right tomake changes to this book at any time, without notice, and assumes noresponsibility for its use. This informational document describes features thatmay not be currently available. Contact a Brocade sales office for informationon feature and product availability. Export of technical data contained in thisbook may require an export license from the United States government.Brocade Corporate HeadquartersSan Jose, CA USAT: (408) 333 8000info@brocade.comBrocade European HeadquartersGeneva, SwitzerlandT: 41 22 799 56 40emea-info@brocade.comBrocade Asia Pacific HeadquartersSingaporeT: 65 6538 4700apac-info@brocade.comAcknowledgementsSpecial thanks are due to Mike Klayko and Tom Buiocchi for executive-levelsupport.Concepts, diagrams, and chunks of text were adapted from slides, manuals,brochures, and white papers prepared by Brocade Education, TechnicalSupport, Professional Services, Engineering, and Marketing. Content was alsoadapted from the books “Principles of SAN Design” and “Multiprotocol Routingfor SANs” by Josh Judd. (Both of these are available from “Buy Books On TheWeb,”www.bbotw.com, and from most other major retail book outlets.) Contentwas adapted from documentation originally produced by the Brocade Houstonteam and other Brocade application product teams. In particular, Rahul Mehtaand his team provided many pages of source content, including diagrams, text,and lists of key concepts.This book would not have been possible without reviews from Kent Hanson,Victoria Thomas, Mike Schmitt, and Martin Skagen.Finally, the authors would like to acknowledge the hard work of the BrocadeEngineering teams, without whom there would be no need for a book on FANtechnology, as there would be no products about which to write.Introducing File Area Networksiii
About the AuthorsMichael O’Connor is a Senior Technical Marketing Engineer in BrocadeTechnical Marketing. In addition to writing about best practices, he works onfuture technologies and proofs-of-concept as well as putting out fires. He alsoworks with SEs and end-users world wide.Before working at Brocade, Mike spent ten years at Sun Microsystems in thenetwork storage group. He also has many technical certifications, and acouple of advanced college degrees. If you ever go to his “cave”, you will seethat he has his own ISP setup right next to the TV.To Mom, Jordan, Croft, Miss B. and TuhanJosh Judd is a Principal Engineer in Brocade Technical Marketing. In additionto writing, he provides support for roadmap activities, develops new productrequirements, and works directly with systems engineers, OEM partners andend users worldwide.When he first went to work for Brocade, Josh was the company’s senior ITtechnical resource, responsible for the architectural design of all network,server, and desktop infrastructure worldwide and escalations. His previousexperience, degree, and certifications are IT-related. He was the first SeniorSAN Architect at Brocade, which means that he was one of the first full-timeprofessional Fibre Channel (FC) SAN designers in the world.About the BookThis book contains information about File Area Networks (FANs) in general,and specific information about FANs built with Brocade products. It is alsodesigned to be useful as a desktop reference for FAN administrators.Information from many white papers, classes, and the authors’ experience hasbeen combined to create this work.This book is appropriate for: Administrators responsible for or deploying FANs Systems Engineers who design and deploy FANs OEM personnel involved in selling or supporting FANs Analysts needing an understanding of the FAN market Network Engineers wishing to expand their skillsWe welcome your comments on this book. Send feedback tobookshelf@brocade.com and include the book title, edition, and publicationdate. If applicable, include the page number and paragraph to which eachcomment applies.ivIntroducing File Area Networks
ContentsChapter 1: FAN Basics .1File Area Networks . 1FAN Drivers . 4FAN vs. SAN . 5FAN Support Products . 6Underlying Network Components . 7RAID Arrays . 8FAN Protocols . 9IP and Ethernet .10Network File Systems .10Chapter Summary .13Chapter 2: FAN Solutions . 15Storage Consolidation .16Namespace Globalization .18Data Migration .22Disaster Recover/Business Continuance .24WAN Performance Optimization .27Chapter Summary .29Chapter 3: Building Blocks . 31Brocade StorageX .31Brocade WAFS .35Brocade FLM .38Brocade MyView .40Brocade UNCUpdate . 41Brocade Unified FAN Strategy .42Customer Case Studies .43StorageX for Data Replication and Protection .43StorageX and WAFS Working Together .45Chapter Summary .46Introducing File Area Networksv
ContentsChapter 4: Design Considerations . 47Compatibility .48Network Topologies .50Topology Names .50Overlay Networks .51Reliability, Availability, and Serviceability .52Reliability .52Availability .54Serviceability .60Performance .61Scalability .62Total Solution Cost .63WAN .63General Distance Considerations .64Data Migration Considerations .65Disaster Recovery Considerations .65Implementation and Beyond .66Rack Locations and Mounting .66Power and UPSs .68Staging and Validation .68Release to Production .69Day-to-Day Management .70Planning for Troubleshooting .70Chapter Summary . 71Chapter 5: Brocade StorageX . 73Deployment Examples .75Single User Drive Mapping Proliferation .75Multi-Department Drive Mapping Inconsistency .77Drive Mapping and Communications .78Infrastructure Changes .79Storage Optimization .79Data Lifecycle Management .81Product Architecture .82Client/Server Design .83GNS Deployment .84Replication Technology .87Data Migration Tasks .98Data Migration Methods .99Migrations Procedures with Unchanging Structures .99Migrations Procedures with Changing Structures .101Migrations Procedures with Server Consolidations . 102StorageX and NetApp Storage Device Integration . 104NetApp Filer in the Physical View tree . 104NetApp vFiler in the Physical View tree . 104viIntroducing File Area Networks
ContentsTroubleshooting . 109Installation Problems . 109Namespace Problems . 110Replication Problems . 110Chapter Summary . 111Chapter 6: Brocade WAFS .113WAFS Business Case . 114Challenges to Centralization . 115WAN Latency and Protocol Design . 115Lack of Bandwidth . 115Lack of Data Integrity . 115Residual Branch Office Servers . 116Summary: Workarounds Don’t Work . 116Brocade WAFS Architecture .117Node Types .117Core Technology . 118Performance Architecture and Benefits . 120Availability and Integrity Benefits . 122End-to-End Security . 122Full CIFS Disconnection Support . 123Other Architectural Benefits . 125Single Instance Storage . 125Transparent Pre-Population . 125Edge Office IT Services . 125Print Services . 126Domain Controller Services . 126Network Services . 127Web Caching Services . 127Management Services . 127Protocol Acceleration . 128TCP Acceleration . 128WAFS Transport Protocol Acceleration .131Data Reduction . 133Data Compression . 134Application-Aware Data Reduction . 135Deploying WAFS .137At the Data Center .137At the Branch Office .137High Availability Deployments . 140Flexible Platform Options .141Platform Hardware . 143Chapter Summary . 144Introducing File Area Networksvii
ContentsChapter 7: Brocade MyView .145System Requirements . 148MyView Server and Client Requirements . 148MyView Database Requirements . 148MyView Disk Space Requirements . 148Namespace Design Considerations . 149Reduce Complexity . 149Consider Reliability . 149Cascaded Namespaces . 149DFS Namespace Sizing .151Namespace Implementation .151Chapter Summary . 152Chapter 8: Brocade FLM .153Effect of Deploying FLM . 155FLM In Action . 155FLM Policies . 158FLM and Backups . 159FLM Deployment Tips and Tricks .161When to Deploy FLM .161General Tips . 162Performance and Scalability Tips . 163Setting the Offline Attribute . 166Auto-Remigration and Auto-Exclusion . 166Security Tips . 167Implementation and Management . 167Data Availability and Recovery .175Communicating with Users Before Rollout . 181Chapter Summary . 182Chapter 9: Brocade UNCUpdate .183System Requirements . 184How It Works . 184Deploying UNCUpdate . 185Command-Line Interface . 185The Desktop . 185Search and Modify Modes . 186The Directives File . 186Templates . 188Reports . 188Important Notes . 189Troubleshooting . 189Chapter Summary . 190viiiIntroducing File Area Networks
ContentsAppendix A: Reference .191Ethernet and IP Network Equipment . 191Ethernet L2 Edge Switches and Hubs . 191IP WAN Routers . 191Storage Equipment . 192RAID Arrays . 192Appendix B: Namespace Requirements .195Appendix C: WAFS Sizing Guidelines .197Supported TPA Connections with WAFS 3.4 .197Core Node .197Edge Node .197WAFS Sizing Guidelines for CIFS . 198Core Node . 198Edge Node . 198WAN Throughput . 198Glossary . 199Introducing File Area Networksix
ContentsxIntroducing File Area Networks
FiguresFigure 1. High-level view of a FAN . 3Figure 2. FAN and SAN architectures in concert . 6Figure 3. White space utilization in a DAS environment .16Figure 4. Network file-system mapping .19Figure 5. Global namespace .20Figure 6. Multi-site GNS Scenario .21Figure 7. DR failover using a FAN overview .25Figure 8. DR failover using a FAN (detailed) .26Figure 9. High-level WAFS architecture .29Figure 10. Brocade WAFS Appliance .35Figure 11. Brocade Unified FAN Strategy .43Figure 12. Acme’s file data replication and protection strategy .44Figure 13. ABC’s enterprise data consolidation and protection strategy .46Figure 14. Horizontal redundant relationships .57Figure 15. Bad rack implementation (airflow problem) .67Figure 16. Too many drive mappings .75Figure 17. Drive mappings consolidated .76Figure 18. Inconsistent mappings .77Figure 19. Inconsistent mappings and communications .78Figure 20. Migrating to higher-capacity storage .79Figure 21. Optimizing capacity utilization with StorageX .80Figure 22. Data lifecycle management concept .81Figure 23. StorageX applications .82Figure 24. Client/server architecture .83Figure 25. Namespace Creation Wizard .85Figure 26. StorageX administration console .86Figure 27. Creating a DFS structure .87Figure 28. Replication technologies .88Figure 29. Replication engine locations .89Figure 30. Data integrity options for replication .90Figure 31. BFDR methodology .91Figure 32. Heterogeneous replication .92Figure 33. Managing replication .93Figure 34. Deleting orphans .97Figure 35. Categories of migration: change or no change .99Introducing File Area Networksix
FiguresFigure 36.Figure 37.Figure 38.Figure 39.Figure 40.Figure 41.Figure 42.Figure 43.Figure 44.Figure 45.Figure 46.Figure 47.Figure 48.Figure 49.Figure 50.Figure 51.Figure 52.Figure 53.Figure 54.Figure 55.Figure 56.Figure 57.Figure 58.Figure 59.Figure 60.Figure 61.Figure 62.Figure 63.Figure 64.xExample of changing structure migration . 101Migration using consolidation root . 103Configuring filer management in StorageX . 105Configuring volumes on a filer . 106Snapshot schedule initiated from StorageX . 107Snapshot scheduling properties and NetApp filer scheduling . 108WAFS product architecture . 117Exemplary WAFS deployment . 119Write-back file locking architecture . 121WAFS security advantages . 123Using WAFS to consolidate services in a branch office . 126TCP performance in a LAN vs. a WAN . 129TCP protocol acceleration impact on applications . 130CIFS over a WAN without acceleration . 132CIFS over a WAN with acceleration . 132Impact of acceleration on file save time . 133Dictionary Compression . 135Mapping Drives with WAFS . 138WAFS plus WCCP Redirection . 139MyView Desktop . 147Inactive vs. active data . 154Impact on file storage utilization of deploying Brocade FLM . 155How FLM works . 156User view of relocated files . 157FLM Policy Engine .
Brocade Corporate Headquarters San Jose, CA USA T: (408) 333 8000 info@brocade.com Brocade European Headquarters Geneva, Switzerland T: 41 22 799 56 40 emea-info@brocade.com Brocade Asia Pacific Headquarters Singapore T: 65 6538 4700 apac-info@brocade.com Acknowledgements Special thanks
Everything You Wanted To Know About Storage (But Were Too Proud To Ask) Part Chartreuse . Your Hosts 2 J Metz SNIA Board of Directors Cisco Chad Hintz SNIA-ESF Board Cisco Fred Knight Standards Technologist NetApp John Kim SNIA-ESF Chair Mellanox . About SNIA 3 . SNIA Legal Notice ! The mate
Jun 02, 2020 · And a new computational storage work area launched in late 2018 All this has led to the evolution of the SNIA Solid State Storage Initiative into the SNIA Compute, Memory, and Storage Initiative Recognizes this fundamental opportunity to combine storage, me
Feb 13, 2020 · The SNIA must be acknowledged as the source of any material used in the body of any document containing material from these presentations. This presentation is a project of the SNIA. Neither the author nor the presenter is an attorney and nothing in this presentation is intended to be, or
Using SPEC SFS with the SNIA Emerald Program for EPA Energy Star Data Center Storage Program Industry Stakeholders Update Verno
Q1 2017. EDSFF group formed. Q4 2017. EDSFF hands off specs to SNIA SFF-TA. SFF-TA-1009 1.0 published
Chad Hintz, Cisco Eric Forgette, Nimble Storage . SNIA Legal Notice ! The material contained in this presentation is copyrighted by the SNIA unless otherwise noted. ! Member companies and individu
Managing Private and Hybrid Clouds for Data Storage 4 2010 STORAGE NETWORKING INDUSTRY ASSOCIATION Improving Private and Hybrid Cloud Storage - CDMI Building on this use of the SNIA Storage Industry Resource Domain Model, the management of private and hybrid clouds (as well as public clouds) is addressed by the SNIA in CDMI. Designed to enable
STM32 and ultra‑low‑power. 4 9 product series – more than 40 product lines . proliferation of hardware IPs and higher‑level programming languages greatly facilitates the work of developers. High‑ performance Cortex‑M STM32 F7 Ultra‑ low‑power Mainstream Cortex‑M3 STM32 F2 STM32 L1 STM32 F1 Cortex‑M STM32 F4 STM32 L4 STM32 F3 Cortex‑M M STM32 L0 STM32 F0 STM32 H7 ST .
