Details

<b>About the Authors.</b> <p><b>Foreword to the Second Edition by Hermann Strass.</b></p> <p><b>Preface by the Authors.</b></p> <p><b>List of Figures and Tables.</b></p> <p><b>1 Introduction.</b></p> <p>1.1 Server-Centric IT Architecture and its Limitations.</p> <p>1.2 Storage-Centric IT Architecture and its Advantages.</p> <p>1.3 Case Study: Replacing a Server with Storage Networks.</p> <p>1.4 <b><i>The Structure of the Book</i></b>.</p> <p><b>PART I Technologies for Storage Networks.</b></p> <p><b>2 Intelligent Disk Subsystems.</b></p> <p>2.1 Architecture of Intelligent Disk Subsystems.</p> <p>2.2 Hard Disks and Internal I/O Channels.</p> <p>2.3 JBOD: Just a Bunch of Disks.</p> <p>2.4 Storage Virtualisation Using RAID.</p> <p>2.5 Different RAID Levels in Detail.</p> <p>2.5.1 RAID 0: block-by-block striping.</p> <p>2.5.2 RAID 1: block-by-block mirroring.</p> <p>2.5.3 RAID 0+1/RAID 10: striping and mirroring combined.</p> <p>2.5.4 RAID 4 and RAID 5: parity instead of mirroring.</p> <p>2.5.5 RAID 6: double parity.</p> <p>2.5.6 RAID 2 and RAID 3.</p> <p>2.5.7 A comparison of the RAID levels.</p> <p>2.6 Caching: Acceleration of Hard Disk Access.</p> <p>2.6.1 Cache on the hard disk.</p> <p>2.6.2 Write cache in the disk subsystem controller.</p> <p>2.6.3 Read cache in the disk subsystem controller.</p> <p>2.7 Intelligent Disk Subsystems.</p> <p>2.7.1 Instant copies.</p> <p>2.7.2 Remote mirroring.</p> <p>2.7.3 Consistency groups.</p> <p>2.7.4 LUN masking.</p> <p>2.8 Availability of Disk Subsystems.</p> <p>2.9 Summary.</p> <p><b>3 I/O Techniques.</b></p> <p>3.1 The Physical I/O Path from the CPU to the Storage System.</p> <p>3.2 SCSI.</p> <p>3.2.1 SCSI basics.</p> <p>3.2.2 SCSI and storage networks.</p> <p>3.3 The Fibre Channel Protocol Stack.</p> <p>3.3.1 Links, ports and topologies.</p> <p>3.3.2 FC-0: cables, plugs and signal encoding.</p> <p>3.3.3 FC-1: 8b/10b encoding, ordered sets and link control protocol.</p> <p>3.3.4 FC-2: data transfer.</p> <p>3.3.5 FC-3: common services.</p> <p>3.3.6 Link services: login and addressing.</p> <p>3.3.7 Fabric services: name server and co.</p> <p>3.3.8 FC-4 and ULPs: application protocols.</p> <p>3.4 Fibre Channel SAN.</p> <p>3.4.1 Point-to-point topology.</p> <p>3.4.2 Fabric topology.</p> <p>3.4.3 Arbitrated loop topology.</p> <p>3.4.4 Hardware components for Fibre Channel SAN.</p> <p>3.4.5 InterSANs.</p> <p>3.4.6 Interoperability of Fibre Channel SAN.</p> <p>3.5 IP Storage.</p> <p>3.5.1 IP storage standards: iSCSI, iFCP, mFCP, FCIP and iSNS.</p> <p>3.5.2 TCP/IP and Ethernet as an I/O technology.</p> <p>3.5.3 Migration from Fibre Channel to IP storage.</p> <p>3.6 Infiniband-based Storage Networks.</p> <p>3.6.1 InfiniBand.</p> <p>3.6.2 Virtual Interface Architecture (VIA).</p> <p>3.6.3 SCSI via InfiniBand and RDMA.</p> <p>3.7 Fibre Channel over Ethernet (FCoE).</p> <p>3.7.1 I/O Consolidation based on Ethernet.</p> <p>3.7.2 FCoE Details.</p> <p>3.7.3 Case studies.</p> <p>3.7.4 Data Center Bridging (DCB).</p> <p>3.7.5 Outlook.</p> <p>3.8 Summary.</p> <p><b>4 File Systems and Network Attached Storage (NAS).</b></p> <p>4.1 Local File Systems.</p> <p>4.1.1 File systems and databases.</p> <p>4.1.2 Journaling.</p> <p>4.1.3 Snapshots.</p> <p>4.1.4 Volume manager.</p> <p>4.2 Network File Systems and File Servers.</p> <p>4.2.1 Basic principle.</p> <p>4.2.2 Network Attached Storage (NAS).</p> <p>4.2.3 Performance bottlenecks in file servers.</p> <p>4.2.4 Acceleration of network file systems.</p> <p>4.2.5 Case study: The Direct Access File System (DAFS).</p> <p>4.3 Shared Disk File Systems.</p> <p>4.3.1 Case study: The General Parallel File System (GPFS).</p> <p>4.4 Comparison: Fibre Channel SAN, FCoE SAN, iSCSI SAN and NAS.</p> <p>4.5 Summary.</p> <p><b>5 Storage Virtualisation.</b></p> <p>5.1 Once Again: Virtualisation in the I/O Path.</p> <p>5.2 Limitations and Requirements.</p> <p>5.2.1 Architecture-related limitations of non-virtualised storage networks.</p> <p>5.2.2 Implementation-related limitations of storage networks.</p> <p>5.2.3 Requirements of the data.</p> <p>5.2.4 Proposed solution: storage virtualisation.</p> <p>5.3 Definition of Storage Virtualisation.</p> <p>5.4 Implementation Considerations.</p> <p>5.4.1 Realisation of the virtualisation entity.</p> <p>5.4.2 Replacement of storage devices.</p> <p>5.4.3 Efficient use of resources by dynamic storage allocation.</p> <p>5.4.4 Efficient use of resources by data migration.</p> <p>5.4.5 Performance increase.</p> <p>5.4.6 Availability due to the introduction of redundancy.</p> <p>5.4.7 Backup and archiving.</p> <p>5.4.8 Data sharing.</p> <p>5.4.9 Privacy protection.</p> <p>5.5 Storage Virtualisation on Block or File Level.</p> <p>5.6 Storage Virtualisation on Various Levels of the Storage Network.</p> <p>5.6.1 Storage virtualisation in the server.</p> <p>5.6.2 Storage virtualisation in storage devices.</p> <p>5.6.3 Storage virtualisation in the network.</p> <p>5.7 Symmetric and Asymmetric Storage Virtualisation in the Network.</p> <p>5.7.1 Symmetric storage virtualisation.</p> <p>5.7.2 Asymmetric storage virtualisation.</p> <p>5.8 Summary.</p> <p><b>PART II Application and Management of Storage Networks.</b></p> <p><b>6 Application of Storage Networks.</b></p> <p>6.1 Definition of the Term ‘Storage Network’.</p> <p>6.1.1 Layering of the transmission techniques and protocols.</p> <p>6.1.2 Networks in the I/O path.</p> <p>6.1.3 Data networks, voice networks and storage networks.</p> <p>6.2 Storage Sharing.</p> <p>6.2.1 Disk storage pooling.</p> <p>6.2.2 Dynamic tape library sharing.</p> <p>6.2.3 Data sharing.</p> <p>6.3 Availability of Data.</p> <p>6.3.1 Failure of an I/O bus.</p> <p>6.3.2 Failure of a server.</p> <p>6.3.3 Failure of a disk subsystem.</p> <p>6.3.4 Failure of virtualisation in the storage network.</p> <p>6.3.5 Failure of a data centre based upon the case study ‘protection of an important database’.</p> <p>6.4 Adaptability and Scalability of IT Systems.</p> <p>6.4.1 Clustering for load distribution.</p> <p>6.4.2 Web architecture.</p> <p>6.4.3 Web applications based upon the case study ‘travel portal’.</p> <p>6.5 Summary.</p> <p><b>7 Network Backup.</b></p> <p>7.1 General Conditions for Backup.</p> <p>7.2 Network Backup Services.</p> <p>7.3 Components of Backup Servers.</p> <p>7.3.1 Job scheduler.</p> <p>7.3.2 Error handler.</p> <p>7.3.3 Metadata database.</p> <p>7.3.4 Media manager.</p> <p>7.4 Backup Clients.</p> <p>7.5 Performance Gains as a Result of Network Backup.</p> <p>7.6 Performance Bottlenecks of Network Backup.</p> <p>7.6.1 Application-specific performance bottlenecks.</p> <p>7.6.2 Performance bottlenecks due to server-centric IT architecture.</p> <p>7.7 Limited Opportunities for Increasing Performance.</p> <p>7.7.1 Separate LAN for network backup.</p> <p>7.7.2 Multiple backup servers.</p> <p>7.7.3 Backup server and application server on the same physical computer.</p> <p>7.8 Next Generation Backup.</p> <p>7.8.1 Server-free backup.</p> <p>7.8.2 LAN-free backup.</p> <p>7.8.3 LAN-free backup with shared disk file systems.</p> <p>7.8.4 Backup using instant copies.</p> <p>7.8.5 Data protection using remote mirroring.</p> <p>7.8.6 Tape library sharing.</p> <p>7.9 Backup of File Systems.</p> <p>7.9.1 Backup of file servers.</p> <p>7.9.2 Backup of file systems.</p> <p>7.9.3 Backup of NAS servers.</p> <p>7.9.4 The Network Data Management Protocol (NDMP).</p> <p>7.10 Backup of Databases.</p> <p>7.10.1 Functioning of database systems.</p> <p>7.10.2 Classical backup of databases.</p> <p>7.10.3 Next generation backup of databases.</p> <p>7.11 Organisational Aspects of Backup.</p> <p>7.12 Summary.</p> <p><b>8 Archiving.</b></p> <p>8.1 Terminology.</p> <p>8.1.1 Differentiating between information and data.</p> <p>8.1.2 Archiving.</p> <p>8.1.3 Digital archiving.</p> <p>8.1.4 Reference architecture for digital archive systems.</p> <p>8.1.5 Differentiating between archiving and backup.</p> <p>8.1.6 Differentiating between archiving and ILM.</p> <p>8.2 Motivation, Conditions and Requirements.</p> <p>8.2.1 Reasons for archiving.</p> <p>8.2.2 Legal requirements.</p> <p>8.2.3 Technical progress.</p> <p>8.2.4 Requirement for stability.</p> <p>8.2.5 Risks from the environment and from society.</p> <p>8.2.6 Requirement for adaptability and scalability.</p> <p>8.2.7 Operational requirements.</p> <p>8.2.8 Cost-related requirements.</p> <p>8.2.9 Conclusion: Archive systems as a strategic investment.</p> <p>8.3 Implementation Considerations.</p> <p>8.3.1 WORM storage technologies.</p> <p>8.3.2 Data security.</p> <p>8.3.3 Data integrity.</p> <p>8.3.4 Proof of regulatory compliance.</p> <p>8.3.5 Deletion of data.</p> <p>8.3.6 Continuous operation.</p> <p>8.3.7 Loss-free operation.</p> <p>8.3.8 Data management: storage hierarchy and migration.</p> <p>8.3.9 Component-neutral archiving.</p> <p>8.3.10 Selection of components and vendors.</p> <p>8.4 Interfaces in Archive Systems.</p> <p>8.4.1 Interface between application and DMS.</p> <p>8.4.2 Java Content Repository (JCR).</p> <p>8.4.3 Interface between DMS and archive storage.</p> <p>8.4.4 eXtensible Access Method (XAM).</p> <p>8.4.5 Management interfaces.</p> <p>8.4.6 Interface between DMS systems.</p> <p>8.4.7 Standardised interfaces for archive systems.</p> <p>8.5 Archive Solutions.</p> <p>8.5.1 Archiving of emails.</p> <p>8.5.2 Archiving of files.</p> <p>8.5.3 Archiving of ERP systems.</p> <p>8.5.4 Archiving in hospitals.</p> <p>8.5.5 Central archives.</p> <p>8.6 Operational and Organisational Aspects.</p> <p>8.7 Summary and Outlook.</p> <p><b>9 Business Continuity.</b></p> <p>9.1 General Conditions.</p> <p>9.1.1 Terminology.</p> <p>9.1.2 Target audience.</p> <p>9.1.3 Classification of risks.</p> <p>9.1.4 Classification of outages.</p> <p>9.1.5 IT failures in the context of business processes.</p> <p>9.1.6 Resumption of business processes.</p> <p>9.1.7 Business continuity for the web architecture.</p> <p>9.1.8 Cost optimisation for business continuity.</p> <p>9.1.9 Risk analysis and risk management.</p> <p>9.1.10 Creation of a business continuity plan.</p> <p>9.2 Strategies of Business Continuity.</p> <p>9.2.1 High availability.</p> <p>9.2.2 Disaster recovery.</p> <p>9.2.3 Continuous business operation.</p> <p>9.3 Parameters of Business Continuity.</p> <p>9.3.1 Availability.</p> <p>9.3.2 Characterisation of availability (MTBF, MTTR and MTTF).</p> <p>9.3.3 Calculation of overall availability.</p> <p>9.3.4 Characterisation of failures (RTO and RPO).</p> <p>9.3.5 Network Recovery Objective (NRO).</p> <p>9.4 Quality of Service for Business Continuity.</p> <p>9.4.1 Service Level Agreements (SLAs).</p> <p>9.4.2 High availability versus disaster recovery.</p> <p>9.4.3 The seven-tier model.</p> <p>9.4.4 Tier 0: no data backup.</p> <p>9.4.5 Tier 1: data backup without a backup data centre.</p> <p>9.4.6 Tier 2: data backup with backup data centre.</p> <p>9.4.7 Tier 3: electronic vaulting.</p> <p>9.4.8 Tier 4: instant copies.</p> <p>9.4.9 Tier 5: software mirroring.</p> <p>9.4.10 Tier 6: disk subsystem-based mirroring.</p> <p>9.4.11 Tier 7: fully automated solutions.</p> <p>9.5 Business Continuity Solutions.</p> <p>9.5.1 Basic techniques.</p> <p>9.5.2 Solution segments of the seven-tier model.</p> <p>9.5.3 Backup and restore.</p> <p>9.5.4 Rapid data recovery using copies.</p> <p>9.5.5 Rapid data recovery using mirrors.</p> <p>9.5.6 Continuous availability.</p> <p>9.6 Switch of Operational Location.</p> <p>9.7 Organisational Aspects.</p> <p>9.8 Summary.</p> <p><b>10. Management of Storage Networks.</b></p> <p>10.1 Requirements.</p> <p>10.1.1 User-related requirements.</p> <p>10.1.2 Component-related requirements.</p> <p>10.1.3 Architectural requirements.</p> <p>10.1.4 One central management system.</p> <p>10.1.5 Five basic services.</p> <p>10.2 Characterisation of Management Interfaces.</p> <p>10.2.1 In-band interfaces.</p> <p>10.2.2 Out-band interfaces.</p> <p>10.2.3 Standardised interfaces.</p> <p>10.2.4 Proprietary interfaces.</p> <p>10.2.5 Conclusion.</p> <p>10.3 In-band Management.</p> <p>10.3.1 In-band management in Fibre Channel SAN.</p> <p>10.4 Out-band Management.</p> <p>10.4.1 The Simple Network Management Protocol (SNMP).</p> <p>10.4.2 CIM and WBEM.</p> <p>10.4.3 Storage Management Initiative Specification (SMI-S).</p> <p>10.4.4 CMIP and DMI.</p> <p>10.5 Operational Aspects of the Management of Storage Networks.</p> <p>10.6 Summary.</p> <p><b>11 Removable Media Management.</b></p> <p>11.1 The Significance of Removable Media.</p> <p>11.2 Removable Media.</p> <p>11.2.1 Tapes.</p> <p>11.2.2 CD, DVD and magneto-optical media.</p> <p>11.2.3 Management features of removable media.</p> <p>11.3 Libraries and Drives.</p> <p>11.3.1 Libraries.</p> <p>11.3.2 Drives.</p> <p>11.3.3 Media changers.</p> <p>11.4 Problems and Requirements in Respect of Removable Media Management.</p> <p>11.4.1 Efficient use of the available resources.</p> <p>11.4.2 Access control.</p> <p>11.4.3 Access synchronisation.</p> <p>11.4.4 Access prioritisation and mount request queuing.</p> <p>11.4.5 Grouping, pooling.</p> <p>11.4.6 Media tracking and vaulting.</p> <p>11.4.7 Cartridge life cycle management.</p> <p>11.4.8 Monitoring.</p> <p>11.4.9 Reporting.</p> <p>11.5 The IEEE 1244 Standard for Removable Media Management.</p> <p>11.5.1 Media management system architecture.</p> <p>11.5.2 Media manager and MMP.</p> <p>11.5.3 Library manager and drive manager.</p> <p>11.6 Summary.</p> <p><b>12 The SNIA Shared Storage Model.</b></p> <p>12.1 The Model.</p> <p>12.1.1 The functional approach.</p> <p>12.1.2 Graphical representations.</p> <p>12.1.3 An elementary overview.</p> <p>12.1.4 The components.</p> <p>12.1.5 The layers.</p> <p>12.1.6 The file/record layer.</p> <p>12.1.7 The block layer.</p> <p>12.1.8 Combination of the block and file/record layers.</p> <p>12.1.9 Access paths.</p> <p>12.1.10 Caching.</p> <p>12.1.11 Access control.</p> <p>12.1.12 Clustering.</p> <p>12.1.13 Storage, data and information.</p> <p>12.1.14 Resource and data sharing.</p> <p>12.1.15 The service subsystem.</p> <p>12.2 Examples of Disk-Based Storage Architectures.</p> <p>12.2.1 Direct attached block storage.</p> <p>12.2.2 Storage network attached block storage.</p> <p>12.2.3 Block storage aggregation in a storage device: SAN appliance.</p> <p>12.2.4 Network attached block storage with metadata server: asymmetric block services.</p> <p>12.2.5 Multi-site block storage.</p> <p>12.2.6 File server.</p> <p>12.2.7 File server controller: NAS heads.</p> <p>12.2.8 Asymmetric file services: NAS/file server metadata manager.</p> <p>12.2.9 Object-based storage device (OSD).</p> <p>12.3 Extension of the SNIA Shared Storage Model to Tape Functions.</p> <p>12.3.1 Logical and physical structure of tapes.</p> <p>12.3.2 Differences between disk and tape.</p> <p>12.3.3 Extension of the model.</p> <p>12.4 Examples of Tape-Based Backup Techniques and Architectures.</p> <p>12.4.1 File backup.</p> <p>12.4.2 File system volume backup.</p> <p>12.4.3 Volume backup.</p> <p>12.4.4 File backup to virtual tape.</p> <p>12.4.5 Direct attached tape.</p> <p>12.4.6 LAN attached tape.</p> <p>12.4.7 Shared tape drive.</p> <p>12.4.8 Partitioned tape library.</p> <p>12.4.9 Virtual tape controller.</p> <p>12.4.10 Virtual tape controller with disk cache.</p> <p>12.4.11 Data mover for tape.</p> <p>12.4.12 File server with tape drive.</p> <p>12.4.13 File server with external tape.</p> <p>12.4.14 File server with data mover.</p> <p>12.5 Summary.</p> <p><b>13 Final Note.</b></p> <p><b>Glossary.</b></p> <p><b>Annotated Bibliography.</b></p> <p><b>Appendix A: Proof of Calculation of the Parity Block of RAID 4 and 5.</b></p> <p><b>Appendix B: Checklist for the Management of Storage Networks.</b></p> <p>B.1 Applications.</p> <p>B.1.1 Monitoring.</p> <p>B.1.2 Availability.</p> <p>B.1.3 Performance.</p> <p>B.1.4 Scalability.</p> <p>B.1.5 Efficient use.</p> <p>B.2 Data.</p> <p>B.2.1 Availability.</p> <p>B.2.2 Performance.</p> <p>B.2.3 Data protection.</p> <p>B.2.4 Archiving.</p> <p>B.2.5 Migration.</p> <p>B.2.6 Data sharing.</p> <p>B.2.7 Security/access control.</p> <p>B.3 Resources.</p> <p>B.3.1 Inventory/asset management and planning.</p> <p>B.3.2 Monitoring.</p> <p>B.3.3 Configuration.</p> <p>B.3.4 Resource use.</p> <p>B.3.5 Capacity.</p> <p>B.3.6 Efficient resource utilisation.</p> <p>B.3.7 Availability.</p> <p>B.3.8 Resource migration.</p> <p>B.3.9 Security.</p> <p>B.4 Network.</p> <p>B.4.1 Topology.</p> <p>B.4.2 Monitoring.</p> <p>B.4.3 Availability.</p> <p>B.4.4 Performance.</p> <p><b>Index</b>.</p>

The authors are employed at IBM’s storage competence center in Mainz, Germany. They work at the interface between technology and customers. Their duties cover a wide field of responsibilities. They develop and test new software for storage networks. They present the latest hardware and software products in the field of storage networks to customers and explain their underlying concepts. Last but not least they deploy and support respective hardware and software in customer environments.<br /> <b>Ulf Troppens</b> (centre) studied Computer Science at the University of Karlsruhe. Since 1989 he has been primarily involved in the development and administration of Unix systems, storage systems, data and storage networks and distributed applications.<br /> <b>Rainer Erkens</b> (left) studied Mathematics at the University of Mainz. His experience in the management of computers and distributed applications goes back to 1992. Since 2005 he is a technical support manager in IBM’s European Storage Competence Center.<br /> <b>Wolfgang M¨ uller-Friedt</b> (right) studied Computer Science at the FH Darmstadt. He is a software architect focussing on the software development of management applications for storage networks which support open standards such as SMI-S and IEEE 1244.<br /> <b>Nils Haustein</b> (left front) studied Electrical Engineering at the TU Chemnitz. For several years he is with IBM’s advanced technical sales support in Europe where he is focussing on digital archiving.<br /> <b>Rainer Wolafka</b> (right front) studied Electrical Engineering at the FH Frankfurt and Software Engineering at the Santa Clara University. Since 1997 he is working in the field of storage networks and the software development of management applications for storage networks.

<b>All you need to know about Storage Area Networks</b> <p>The amount of data of an average company doubles every year. Thus, companies who own 1TB of data today will own 32TB in five years. Storage networks help to tame such data quantities and to manage this data growth efficiently. Since stored data and information are the biggest asset of any company, anyone who is involved in the planning or the operation of IT systems requires a basic knowledge of the principle and the use of storage networks.</p> <p><i>Storage Networks Explained</i>   covers the fundaments, techniques and functions of storage networks such as disk subsystems, Fibre Channel SAN, Internet SCSI (iSCSI), Fibre Channel over Ethernet (FCoE), Network Attached Storage (NAS), file systems, and storage virtualization. Furthermore the authors describe the use of these techniques and how they are designed to achieve high-availability, flexibility, and scalability of data and applications. Additional attention is given to network backup and the management of storage networks. Written by leading experts in the field, this book on storage area networks is updated and fully revised.</p> <p><i>This book provides system administrators and system architects, as well as students and decision makers, with the tools needed for optimal selection and cost-effective use of storage networks.</i></p> <p><i><b>The Linux Journal awarded the first edition with the “Editor’s Choice Award 2005” in the category “System Administration Book.”</b></i></p> <p><i>Key features:</i></p> <ul> <li>Presents the basic concepts of storage networks, such as I/O techniques, disk subsystems, virtualization, NAS and SAN file systems</li> <li>Covers the design of storage networks which provide flexible, highly-available, and scaleable IT systems</li> <li>Explains the use of storage networks for data sharing, data protection, and digital archiving</li> <li>Discusses management of storage networks using SNMP, SMI-S, and IEEE 1244</li> </ul>

GB