Building storage networks / Marc Farley.
By: Farley, Marc.Series: Network professional's library. New York : Osborne/McGraw-Hill, c2001Edition: 2nd ed.Description: xxxii, 596 p.,  p. of plates : ill. ; 24 cm.ISBN: 0072130725.Subject(s): Storage area networks (Computer networks) | Database management | File organization (Computer science) | Computer storage devicesDDC classification: 004.6/F22 Other classification: CCS Online resources: Contributor biographical information | Publisher description | Table of contents
|Item type||Current location||Call number||Status||Date due||Barcode|
|Books||College Library General Reference Section||CCS 004.6/F22 (Browse shelf)||Available||62050|
Browsing College Library Shelves , Shelving location: General Reference Section Close shelf browser
|CCS 004.22/F23 Digital logic design and computer organization with computer architecture for security /||CCS 004.22/N91 The essentials of computer organization and architecture /||CCS 004.22/P27 Computer organization and design :||CCS 004.6/F22 Building storage networks /||CCS 004.6/F76 Data communications and networking /||CCS 004.6/F76 Data communications and networking /||CCS 004.6/L95 Networking for dummies /|
Table of Contents Chapter 1: Intro to Storage Networking. Chapter 2: Network Storage I/O Components. Chapter 3: I/O Path Examples. Chapter 4: Mirroring and Replication. Chapter 5: Cacheing and Performance. Chapter 6: RAID. Chapter 7: Network Backup. Chapter 8: Differences Between NAS and SAN. Chapter 9: SAN Architectures and Applications. Chapter 10: Fibre Channel as a SAN Technology. Chapter 11: NEW: Storage Over IP. Chapter 12: NAS Technology. Chapter 13: System-Level NAS Applications. Chapter 14: Mainframe Connections to SANs and NAS. Chapter 15: Infiniband and VI. Chapter 16: Web Site Storage. Chapter 17: Network Storage Management. Chapter 1: The Network Storage Landscape Storig and sharing data over computer networks is hardly a new idea. Most readers of this book are familiar with basic client/server network computing built around the idea of a file server that provides storage services to a group of client workstations. As network computing has evolved over the years to include distributed processing technologies such as message-based middleware and clustering, the requirements for the storage devices and subsystems have also changed. This chapter analyzes some of the primary forces pushing host-oriented storage technologies in the direction of host-independent storage networking technologies. The Changing Role Of Data As A Business Asset A great deal has changed in the computing world over the last 20 years. Inexpensive, powerful computers and networks of computers can do the work that required an expensive mainframe 20 years ago. One thing that has not changed, however, is the importance of the data that computers process and produce. If the data is lost, all the computing power at hand is virtually worthless. So, one of the challenges for the data storage industry has been to provide the type of reliability and protection that is required for 24x7 operations on networks of inexpensive systems. This is easier said than done. Managing storage in a network environment has proven to be generally difficult. A single business location can have several different hardware/software platforms, each with their own systems and storage management utilities. This is an extremely difficult environment for system administrators who have to deal with all this diversity with little or no margin for error. There are two approaches to managing storage in network environments. The first is to manage it through a server-provided interface and the second is to manage it through a storage-specific direct connection. The latter approach is the most common one taken by companies in the storage industry, and it leads to a very interesting conclusion: Data is an independent asset, separate from the computers that access it, and requiring a management system that is independent of host systems management. As data is increasingly thought of as its own free-existing entity, not necessarily belonging to any particular system, it is also being viewed as a corporate asset, similar to capital or intellectual property that needs to be preserved and protected. Likewise, storage networking products and architectures, as platforms for data protection and storage management, are also being elevated as a strategic asset worthy of planning and budget meetings formerly reserved for systems and software. Establishing the Relative Worth of Data Storage networking products contain data that is a corporate asset. Therefore, one might want to know what that data is worth to the organization. Both qualitative and quantitative attributes should be weighed in making this determination. In general, qualitative attributes can't be measured and are rarely agreed upon but quantitative attributes can be measured in detail if one chooses to do so. We'll try to work through aspects of both to help the reader calculate their data's "net" worth. Measuring the Qualitative Value of Data Qualitative measurements are the most fun and the least reliable. Questions like, "So what is going to be the return on our $250,000 investment in this advertising campaign?" illustrate the nature of qualitative worth. Nobody can really say exactly what the qualitative worth is, but it's clearly a lot more than zero. At a minimum, one ought to be able to get into some inspired discussions about qualitative data. The appeal of a company's web site is qualitative; so is the friendliness of its automated voice response system. E-mail systems have both qualitative and quantitative values. If a company loses all its e-mail, there is likely going to be a measurable quantified productivity loss, but there is also going to be a qualitative impact in the way customers, partners and employees perceive the organization. When calculating the value of data, it's important to estimate the impact of parting ways with customers, partners, and employees who lose confidence in a company while its computers are out of commission. Frustrated customers don't necessarily notify their existing vendor to tell them they're done doing business with them and are buying instead from a competitor. The cost of retaining a customer is far less than the cost of winning them back. Table 1-1 lists several qualitative data types along with some suggestions about how the reader might calculate their relative value. The percentages and calculations are based on personal experience with data recovery planning and on pure conjecture. The reader may find it useful as a planning guide. Measuring and Prioritizing Data Measuring the quantitative worth of data requires rigor and persistence. However it is done, at some point a detailed and comprehensive disaster recovery plan should be written. An important result of the disaster recovery planning process is a thorough prioritization of the recovery sequence for applications and systems. This involves meeting with business managers to determine a pecking order for computer services. (It can be somewhat entertaining and flattering for an IT worker to observe business managers who depend on the computer systems arguing over the relative importance of their systems and applications.) From time to time different groups, including professional accounting organizations and the U.S. government, study the results of disasters and downtime on business and employment. The results are never good and are usually fairly chilling... Meet the Author Marc Farley is Vice President of Marketing for SanCastle Technologies, a startup developing Gigabit switches for storage networks. He has worked for 10 years in network storage on backup, subsystems, routers and Internet storage.
Building Storage Networks offers an excellent introduction to the burgeoning field of storage networks. A few years ago, someone pulled me aside, looked me in the eye, and informed me that the future was storage. I felt like young Ben Braddock in The Graduate, being told the future was plastics. While the average IT engineer isn't dealing with Mrs. Robinson, he or she does need to manage a staggering amount of data. Storage devices have been around as long as computers. From cassettes or tape drives to multigigabyte hard drives, the growth of storage has gone hand in hand with the growth of computers, and storage capacity has risen dramatically. Even 10 years ago, industry professionals touted the phrase "disk is cheap," effectively writing off storage as a commodity--and this was when hard drives were 120MB or less. During the last decade, continuing improvements in storage technology coincided with the explosion of the Internet, creating a huge demand for reliable, large-scale storage systems. Most businesses have recognized that data is a critical part of their IT systems, what author Marc Farley calls an "independent asset," equal in stature to applications and other system software. Building Storage Networks gives information professionals the basic skills to understand modern storage technologies. The author argues that the common storage types SAN (Storage Area Network) and NAS (Network Attached Storage) are two different manifestations of a common set of principles, which all professionals should understand no matter which solution they implement. After an in-depth discussion of his three key storage concepts--wiring, storing, and filing--Farley fleshes out the role of storage in today's corporate networks. This includes the details of storage implementation, different cabling and communication options, backup management, and future developments (e.g., InfiniBand). This book is easily accessible to intermediate readers familiar with basic networking topologies and computer terminology. A healthy number of illustrations are used to effectively communicate complex topics. At the end of each chapter is a comprehensive summary, followed by several exercises, allowing the reader to fully grasp various storage concepts before proceeding. Building Storage Networks can be used as an entry point for those wishing to learn about modern storage technologies, or as a reference for IT professionals already knee-deep in storage networks. However, almost all storage issues are considered in the abstract, without explicit reference to a particular vendor's hardware. Although an occasional reference is made to a specific product, the author sets out to educate the reader on storage issues, not to replace the manual for a particular piece of storage hardware. --Pete Ostenson From the Back Cover Plan, design, and implement network storage solutions with help from this definitive guide Develop and design successful storage systems using this in-depth resource, now in a completely revised second edition. Covering everything from basic fundamentals--such as I/O components and file systems to emerging topics such as i-SCSI and DAFS--this complete book delivers the background information and technical know-how to implement large-capacity, high-availability storage networks throughout your enterprise. Filled with diagrams and easy-to-understand explanations, you will be able to identify and apply network storage technology to best meet the needs of your organization. Determine the roles of networks, file systems, databases, and volume managers Get details on data protection techniques including mirroring, replication, and backup Analyze and contrast RAID levels 0, 1, 3, 4, 5, and 0+1 Clarify the options for integrating Ethernet and IP networks with storage networks Measure the impact of InfiniBand, DAFS, and clustering Plan 24 x 7 Internet-based storage including storage service providers (SSPs) Reinforce concepts you've learned through chapter exercises Visit companion Website at: www.buildingstorage.com
College of Engineering and Computer Studies