Book description
This IBM® Redbooks® publication captures several of the preferred practices that are based on field experience and describes the performance gains that can be achieved by implementing the IBM System Storage® SAN Volume Controller and Storwize® V7000 V7.2.
This book begins with a look at the latest developments with SAN Volume Controller and Storwize V7000 and reviews the changes in the previous versions of the product. It highlights configuration guidelines and preferred practices for the storage area network (SAN) topology, clustered system, back-end storage, storage pools and managed disks, volumes, remote copy services, and hosts. Then, this book provides performance guidelines for SAN Volume Controller, back-end storage, and applications. It explains how you can optimize disk performance with the IBM System Storage Easy Tier® function. Next, it provides preferred practices for monitoring, maintaining, and troubleshooting SAN Volume Controller and Storwize V7000. Finally, this book highlights several scenarios that demonstrate the preferred practices and performance guidelines.
Table of contents
- Front cover
- Notices
- Preface
- Summary of changes
-
Part 1 Configuration guidelines and preferred practices
-
Chapter 1. Updates in IBM System Storage SAN Volume Controller
- 1.1 Enhancements and changes in SAN Volume Controller V5.1
- 1.2 Enhancements and changes in SAN Volume Controller V6.1
- 1.3 Enhancements and changes in SAN Volume Controller V6.2
- 1.4 Enhancements and changes in SAN Volume Controller V6.3
- 1.5 Enhancements and changes in SAN Volume Controller V6.4
- 1.6 Enhancements and changes in SAN Volume Controller V7.1
- 1.7 Enhancements and changes in SAN Volume Controller V7.2
-
Chapter 2. SAN topology
- 2.1 SAN topology of the SAN Volume Controller/Storwize
-
2.2 SAN switches
- 2.2.1 Selecting SAN switch models
- 2.2.2 Switch port layout for large SAN edge switches
- 2.2.3 Switch port layout for director-class SAN switches
- 2.2.4 Virtual channels
- 2.2.5 IBM System Storage and IBM b-type SANs
- 2.2.6 IBM System Storage and Cisco SANs
- 2.2.7 SAN routing and duplicate worldwide node names
-
2.3 Zoning
- 2.3.1 Types of zoning
- 2.3.2 Prezoning tips and shortcuts
- 2.3.3 SAN Volume Controller internode communications zone
- 2.3.4 SAN Volume Controller/Storwize storage zones
- 2.3.5 SAN Volume Controller/Storwize host zones
- 2.3.6 Standard SAN Volume Controller/Storwize zoning configuration
- 2.3.7 Zoning with multiple SAN Volume Controller/Storwize clustered systems
- 2.3.8 Split storage subsystem configurations
- 2.4 Switch domain IDs
- 2.5 Distance extension for remote copy services
- 2.6 Tape and disk traffic that share the SAN
- 2.7 Switch interoperability
- 2.8 IBM Tivoli Storage Productivity Center
- 2.9 iSCSI support
- 2.10 SAS support
- Chapter 3. SAN Volume Controller and Storwize V7000 Cluster
-
Chapter 4. Back-end storage
- 4.1 Controller affinity and preferred path
- 4.2 Round Robin Path Selection
-
4.3 Considerations for DS4000 and DS5000 series
- 4.3.1 Setting the DS4000 and DS5000 series so that both controllers have the same worldwide node name
- 4.3.2 Balancing workload across DS4000 and DS5000 series controllers
- 4.3.3 Ensuring path balance before MDisk discovery
- 4.3.4 Auto-Logical Drive Transfer for the DS4000 and DS5000 series (firmware version before 7.83.x)
- 4.3.5 Asymmetric Logical Unit Access for the DS4000 and DS5000 series (firmware 7.83.x and later)
- 4.3.6 Selecting array and cache parameters
- 4.3.7 Logical drive mapping
- 4.4 Considerations for DS8000 series
- 4.5 Considerations for IBM XIV Storage System
- 4.6 Considerations for IBM Storwize V7000/V5000/V3700
- 4.7 Considerations for IBM FlashSystem
- 4.8 Considerations for third-party storage with EMC Symmetrix DMX and Hitachi Data Systems
- 4.9 Medium error logging
- 4.10 Mapping physical LBAs to volume extents
- 4.11 Identifying storage controller boundaries by using the IBM Tivoli Storage Productivity Center
-
Chapter 5. Storage pools and managed disks
- 5.1 Availability considerations for storage pools
- 5.2 Selecting storage subsystems
- 5.3 Selecting the storage pool
- 5.4 Quorum disk considerations
- 5.5 Tiered storage
- 5.6 Adding MDisks to existing storage pools
- 5.7 Rebalancing extents across a storage pool
- 5.8 Removing MDisks from existing storage pools
- 5.9 Remapping managed MDisks
- 5.10 Controlling extent allocation order for volume creation
- 5.11 Moving an MDisk between SAN Volume Controller clusters
- 5.12 MDisk group considerations when Real-time Compression is used
-
Chapter 6. Volumes
- 6.1 Overview of volumes
- 6.2 Volume mirroring
- 6.3 Creating volumes
- 6.4 Volume migration
- 6.5 Preferred paths to a volume
- 6.6 Cache mode and cache-disabled volumes
- 6.7 Effect of a load on storage controllers
-
6.8 Setting up FlashCopy services
- 6.8.1 Making a FlashCopy volume with application data integrity
- 6.8.2 Making multiple related FlashCopy volumes with data integrity
- 6.8.3 Creating multiple identical copies of a volume
- 6.8.4 Creating a FlashCopy mapping with the incremental flag
- 6.8.5 Using thin-provisioned FlashCopy
- 6.8.6 Using FlashCopy with your backup application
- 6.8.7 Migrating data by using FlashCopy
- 6.8.8 Summary of FlashCopy rules
- 6.8.9 IBM Tivoli Storage FlashCopy Manager
- 6.8.10 IBM System Storage Support for Microsoft Volume Shadow Copy Service
-
Chapter 7. Remote copy services
- 7.1 Introduction to remote copy services
- 7.2 SAN Volume Controller remote copy functions by release
-
7.3 Terminology and functional concepts
- 7.3.1 Remote copy partnerships and relationships
- 7.3.2 Global Mirror control parameters
- 7.3.3 Global Mirror partnerships and relationships
- 7.3.4 Asynchronous remote copy
- 7.3.5 Understanding remote copy write operations
- 7.3.6 Asynchronous remote copy
- 7.3.7 Global Mirror write sequence
- 7.3.8 Write ordering
- 7.3.9 Colliding writes
- 7.3.10 Link speed, latency, and bandwidth
- 7.3.11 Choosing a link cable of supporting Global Mirror applications
- 7.3.12 Remote copy volumes: Copy directions and default roles
-
7.4 Intercluster link
- 7.4.1 SAN configuration overview
- 7.4.2 Switches and ISL oversubscription
- 7.4.3 Zoning
- 7.4.4 Distance extensions for the intercluster link
- 7.4.5 Optical multiplexors
- 7.4.6 Long-distance SFPs and XFPs
- 7.4.7 Fibre Channel IP conversion
- 7.4.8 Configuration of intercluster links
- 7.4.9 Link quality
- 7.4.10 Hops
- 7.4.11 Buffer credits
- 7.5 Global Mirror design points
- 7.6 Global Mirror planning
-
7.7 Global Mirror use cases
- 7.7.1 Synchronizing a remote copy relationship
- 7.7.2 Global Mirror relationships, saving bandwidth, and resizing volumes
- 7.7.3 Master and auxiliary volumes and switching their roles
- 7.7.4 Migrating a Metro Mirror relationship to Global Mirror
- 7.7.5 Multicluster mirroring
- 7.7.6 Performing three-way copy service functions
- 7.7.7 When to use storage controller Advanced Copy Services functions
- 7.7.8 Using Metro Mirror or Global Mirror with FlashCopy
- 7.7.9 Global Mirror upgrade scenarios
- 7.8 Intercluster Metro Mirror and Global Mirror source as an FC target
- 7.9 States and steps in the Global Mirror relationship
- 7.10 1920 errors
- 7.11 Monitoring remote copy relationships
- Chapter 8. Hosts
-
Chapter 1. Updates in IBM System Storage SAN Volume Controller
-
Part 2 Performance preferred practices
- Chapter 9. Performance highlights for SAN Volume Controller V7.2
-
Chapter 10. Back-end storage performance considerations
- 10.1 Workload considerations
- 10.2 Tiering
- 10.3 Storage controller considerations
- 10.4 Array considerations
- 10.5 I/O ports, cache, and throughput considerations
- 10.6 SAN Volume Controller extent size
- 10.7 SAN Volume Controller cache partitioning
- 10.8 IBM DS8000 series considerations
- 10.9 IBM XIV considerations
- 10.10 Storwize V7000 considerations
- 10.11 DS5000 series considerations
- Chapter 11. IBM System Storage Easy Tier function
- Chapter 12. Applications
-
Part 3 Management, monitoring, and troubleshooting
-
Chapter 13. Monitoring
- 13.1 Analyzing the SAN Volume Controller and Storwize Family Storage Systems by using Tivoli Storage Productivity Center
- 13.2 Considerations for performance analysis
-
13.3 Top 10 reports for SAN Volume Controller and Storwize V7000
- 13.3.1 I/O Group Performance for SAN Volume Controller and Storwize V7000
- 13.3.2 Node Cache Performance for SAN Volume Controller and Storwize V7000
- 13.3.3 Viewing the Managed Disk Group Performance report for SAN Volume Controller by using the stand-alone GUI
- 13.3.4 Top Volume Performance reports
- 13.3.5 Port Performance reports for SAN Volume Controller and Storwize V7000
- 13.4 Reports for fabric and switches
-
13.5 Case studies
- 13.5.1 Server performance problem
- 13.5.2 Disk performance problem in a Storwize V7000 subsystem
- 13.5.3 Top volumes response time and I/O rate performance reports
- 13.5.4 Performance constraint alerts
- 13.5.5 Monitoring and diagnosing performance problems for a fabric Viewing
- 13.5.6 Verifying the SAN Volume Controller and Fabric configuration by using Topology Viewer
- 13.5.7 Verifying the SAN Volume Controller and Fabric configuration by using the Tivoli Storage Productivity Center 5.2 web-based GUI Data Path tools
- 13.6 Monitoring in real time by using the SAN Volume Controller or Storwize V7000 GUI
- 13.7 Manually gathering SAN Volume Controller statistics
-
Chapter 14. Maintenance
-
14.1 Automating the documentation for SAN Volume Controller/Storwize and SAN environment
- 14.1.1 Naming conventions
- 14.1.2 SAN fabrics documentation
- 14.1.3 SAN Volume Controller and Storwize family products
- 14.1.4 Storage
- 14.1.5 Technical Support information
- 14.1.6 Tracking incident and change tickets
- 14.1.7 Automated support data collection
- 14.1.8 Subscribing to SAN Volume Controller/Storwize support
- 14.2 Storage management IDs
- 14.3 Standard operating procedures
-
14.4 SAN Volume Controller/Storwize code upgrade
- 14.4.1 Preparing for the upgrade
- 14.4.2 SAN Volume Controller upgrade from V5.1 to V6.2
- 14.4.3 Upgrading SAN Volume Controller clusters/Storwize systems that are participating in Metro Mirror or Global Mirror
- 14.4.4 SAN Volume Controller/Storwize upgrade
- 14.4.5 Storwize family systems disk drive upgrade
- 14.5 SAN modifications
- 14.6 Hardware upgrades for SAN Volume Controller
- 14.7 Adding expansion enclosures to Storwize family systems
- 14.8 More information
-
14.1 Automating the documentation for SAN Volume Controller/Storwize and SAN environment
- Chapter 15. Troubleshooting and diagnostics
-
Chapter 13. Monitoring
-
Part 4 Practical examples
-
Chapter 16. SAN Volume Controller scenarios
- 16.1 SAN Volume Controller upgrade with CF8 nodes and internal solid-state drives
- 16.2 Handling Stuck SAN Volume Controller Code Upgrades
- 16.3 Moving an AIX server
- 16.4 Migrating to a new SAN Volume Controller by using Copy Services
- 16.5 SAN Volume Controller scripting
- 16.6 Migrating AIX cluster volumes off DS4700
- 16.7 Easy Tier and FlashSystem planned outages
- 16.8 Changing LUN ID presented to a VMware ESXi host
-
Chapter 17. IBM Real-time Compression
- 17.1 Overview
- 17.2 What is new in version 7.2
- 17.3 Evaluate data types for estimated compression savings by using the Comprestimator utility
- 17.4 Evaluate workload by using Disk Magic sizing tool
- 17.5 Configure a balanced system
- 17.6 Verify available CPU resources
- 17.7 Compressed and non-compressed volumes in the same MDisk group
- 17.8 Application benchmark results
- 17.9 Standard benchmark tools
- 17.10 Compression with FlashCopy
- 17.11 Compression with Easy Tier
- 17.12 Compression on SAN Volume Controller with Storwize V700
- 17.13 Related Publications
-
Chapter 16. SAN Volume Controller scenarios
-
Appendix A. IBM i considerations
- IBM i Storage management
- Planning for IBM i capacity
- Connecting SAN Volume Controller or Storwize to IBM i
- Preparing SAN Volume Controller or Storwize storage for IBM i
- Solid-state drives
- Sizing Fibre Channel adapters in IBM i and VIOS
- Zoning SAN switches
- Boot from SAN
- IBM i mirroring
- IBM i Multipath
- Copy services considerations
- Related publications
- Back cover
-
IBM System x Reference Architecture for Hadoop: IBM InfoSphere BigInsights Reference Architecture
- Introduction
- Business problem and business value
- Reference architecture use
- Requirements
- InfoSphere BigInsights predefined configuration
- InfoSphere BigInsights HBase predefined configuration
- Deployment considerations
- Customizing the predefined configurations
- Predefined configuration bill of materials
- References
- The team who wrote this paper
- Now you can become a published author, too!
- Stay connected to IBM Redbooks
- Notices
Product information
- Title: IBM System Storage SAN Volume Controller and Storwize V7000 Best Practices and Performance Guidelines
- Author(s):
- Release date: October 2014
- Publisher(s): IBM Redbooks
- ISBN: None
You might also like
book
IBM System Storage SAN Volume Controller and Storwize V7000 Best Practices and Performance Guidelines
Abstract This IBM® Redbooks® publication captures several of the preferred practices and describes the performance gains …
book
IBM System Storage SAN Volume Controller Best Practices and Performance Guidelines
This IBM® Redbooks® publication captures several of the best practices based on field experience and describes …
book
Implementing the IBM System Storage SAN Volume Controller V7.4
This IBM® Redbooks® publication is a detailed technical guide to the IBM System Storage® SAN Volume …
book
Implementing the IBM System Storage SAN Volume Controller V5.1
This IBM® Redbooks® publication is a detailed technical guide to the IBM System Storage™ SAN Volume …