Book description
This IBM® Redbooks® publication is a detailed technical guide to the IBM System Storage® SAN Volume Controller Version 7.4.
The SAN Volume Controller (SVC) is a virtualization appliance solution, which maps virtualized volumes that are visible to hosts and applications to physical volumes on storage devices. Each server within the storage area network (SAN) has its own set of virtual storage addresses that are mapped to physical addresses. If the physical addresses change, the server continues running by using the same virtual addresses that it had before. Therefore, volumes or storage can be added or moved while the server is still running.
The IBM virtualization technology improves the management of information at the “block” level in a network, which enables applications and servers to share storage devices on a network.
This book is intended for readers who want to implement the SVC at a 7.4 release level with minimal effort.
Table of contents
- Front cover
- Notices
- IBM Redbooks promotions
- Preface
- Summary of changes
- Chapter 1. Introduction to storage virtualization
-
Chapter 2. IBM SAN Volume Controller
- 2.1 Brief history of the SAN Volume Controller
- 2.2 SAN Volume Controller architectural overview
- 2.3 SAN Volume Controller terminology
- 2.4 SAN Volume Controller components
- 2.5 Volume overview
- 2.6 iSCSI overview
- 2.7 Advanced Copy Services overview
- 2.8 SAN Volume Controller clustered system overview
-
2.9 User authentication
- 2.9.1 Remote authentication through LDAP
- 2.9.2 SAN Volume Controller user names
- 2.9.3 SAN Volume Controller superuser
- 2.9.4 SAN Volume Controller Service Assistant Tool
- 2.9.5 SAN Volume Controller roles and user groups
- 2.9.6 SAN Volume Controller local authentication
- 2.9.7 SAN Volume Controller remote authentication and single sign-on
- 2.10 SAN Volume Controller hardware overview
- 2.11 Flash drives
- 2.12 What is new with the SAN Volume Controller 7.4
- 2.13 Useful SAN Volume Controller web links
-
Chapter 3. Planning and configuration
- 3.1 General planning rules
- 3.2 Physical planning
-
3.3 Logical planning
- 3.3.1 Management IP addressing plan
- 3.3.2 SAN zoning and SAN connections
- 3.3.3 iSCSI IP addressing plan
- 3.3.4 IP Mirroring
- 3.3.5 Back-end storage subsystem configuration
- 3.3.6 SAN Volume Controller clustered system configuration
- 3.3.7 Stretched cluster system configuration
- 3.3.8 Storage pool configuration
- 3.3.9 Volume configuration
- 3.3.10 Host mapping (LUN masking)
- 3.3.11 Advanced Copy Services
- 3.3.12 SAN boot support
- 3.3.13 Data migration from a non-virtualized storage subsystem
- 3.3.14 SVC configuration backup procedure
- 3.4 Performance considerations
- Chapter 4. SAN Volume Controller initial configuration
-
Chapter 5. Host configuration
- 5.1 Host attachment overview
- 5.2 IBM SAN Volume Controller setup
- 5.3 iSCSI
-
5.4 AIX-specific information
- 5.4.1 Configuring the AIX host
- 5.4.2 Operating system versions and maintenance levels
- 5.4.3 HBAs for IBM System p hosts
- 5.4.4 Configuring fast fail and dynamic tracking
- 5.4.5 Installing the 2145 host attachment support package
- 5.4.6 Subsystem Device Driver Path Control Module
- 5.4.7 Configuring the assigned volume by using SDDPCM
- 5.4.8 Using SDDPCM
- 5.4.9 Creating and preparing volumes for use with AIX V6.1 and SDDPCM
- 5.4.10 Expanding an AIX volume
- 5.4.11 Running SAN Volume Controller commands from an AIX host system
-
5.5 Microsoft Windows information
- 5.5.1 Configuring Windows Server 2008 and 2012 hosts
- 5.5.2 Configuring Windows
- 5.5.3 Hardware lists, device driver, HBAs, and firmware levels
- 5.5.4 Installing and configuring the host adapter
- 5.5.5 Changing the disk timeout on Windows Server
- 5.5.6 Installing the SDDDSM multipath driver on Windows
- 5.5.7 Attaching SVC volumes to Microsoft Windows Server 2008 R2 and to Windows Server 2012
- 5.5.8 Extending a volume
- 5.5.9 Removing a disk on Windows
- 5.6 Using SAN Volume Controller CLI from a Windows host
- 5.7 Microsoft Volume Shadow Copy
- 5.8 Specific Linux (on x86/x86_64) information
-
5.9 VMware configuration information
- 5.9.1 Configuring VMware hosts
- 5.9.2 Operating system versions and maintenance levels
- 5.9.3 HBAs for hosts that are running VMware
- 5.9.4 VMware storage and zoning guidance
- 5.9.5 Setting the HBA timeout for failover in VMware
- 5.9.6 Multipathing in ESX
- 5.9.7 Attaching VMware to volumes
- 5.9.8 Volume naming in VMware
- 5.9.9 Setting the Microsoft guest operating system timeout
- 5.9.10 Extending a VMFS volume
- 5.9.11 Removing a datastore from an ESX host
- 5.10 Sun Solaris hosts
- 5.11 Hewlett-Packard UNIX configuration information
- 5.12 Using the SDDDSM, SDDPCM, and SDD web interface
- 5.13 More information
-
Chapter 6. Data migration
- 6.1 Migration overview
- 6.2 Migration operations
- 6.3 Functional overview of migration
- 6.4 Migrating data from an image mode volume
-
6.5 Data migration for Windows by using the SVC GUI
- 6.5.1 Windows Server 2008 host system connected directly to the DS 3400
- 6.5.2 Adding the SAN Volume Controller between the host system and the DS 3400
- 6.5.3 Importing the migrated disks into an online Windows Server 2008 host
- 6.5.4 Adding IBM SAN Volume Controller between the host and the DS 3400 by using the CLI
- 6.5.5 Migrating a volume from managed mode to image mode
- 6.5.6 Migrating the volume from image mode to image mode
- 6.5.7 Removing image mode data from the IBM SAN Volume Controller
- 6.5.8 Mapping the free disks onto the Windows Server 2008 server
-
6.6 Migrating Linux SAN disks to SVC disks
- 6.6.1 Connecting the IBM SAN Volume Controller to your SAN fabric
- 6.6.2 Preparing your IBM SAN Volume Controller to virtualize disks
- 6.6.3 Moving the LUNs to the IBM SAN Volume Controller
- 6.6.4 Migrating the image mode volumes to managed MDisks
- 6.6.5 Preparing to migrate from the IBM SAN Volume Controller
- 6.6.6 Migrating the volumes to image mode volumes
- 6.6.7 Removing the LUNs from the IBM SAN Volume Controller
-
6.7 Migrating ESX SAN disks to SVC disks
- 6.7.1 Connecting the IBM SAN Volume Controller to your SAN fabric
- 6.7.2 Preparing your IBM SAN Volume Controller to virtualize disks
- 6.7.3 Moving the LUNs to the IBM SAN Volume Controller
- 6.7.4 Migrating the image mode volumes
- 6.7.5 Preparing to migrate from the IBM SAN Volume Controller
- 6.7.6 Migrating the managed volumes to image mode volumes
- 6.7.7 Removing the LUNs from the IBM SAN Volume Controller
-
6.8 Migrating AIX SAN disks to SVC volumes
- 6.8.1 Connecting the IBM SAN Volume Controller to your SAN fabric
- 6.8.2 Preparing your IBM SAN Volume Controller to virtualize disks
- 6.8.3 Moving the LUNs to the IBM SAN Volume Controller
- 6.8.4 Migrating image mode volumes to volumes
- 6.8.5 Preparing to migrate from the IBM SAN Volume Controller
- 6.8.6 Migrating the managed volumes
- 6.8.7 Removing the LUNs from the IBM SAN Volume Controller
- 6.9 Using IBM SAN Volume Controller for storage migration
- 6.10 Using volume mirroring and thin-provisioned volumes together
-
Chapter 7. Advanced features for storage efficiency
- 7.1 Introduction
- 7.2 Easy Tier
- 7.3 Thin provisioning
-
7.4 Real-time Compression Software
- 7.4.1 Common use cases
- 7.4.2 Real-time Compression concepts
- 7.4.3 Random Access Compression Engine
- 7.4.4 Random Access Compression Engine in the SVC software stack
- 7.4.5 Data write flow
- 7.4.6 Data read flow
- 7.4.7 Compression of existing data
- 7.4.8 Configuring compressed volumes
- 7.4.9 SVC 2145-DH8 node software and hardware updates related to Real-time Compression
- 7.4.10 Software enhancements
- 7.4.11 Hardware updates
- 7.4.12 Dual RACE component
-
Chapter 8. Advanced Copy Services
- 8.1 FlashCopy
- 8.2 Reverse FlashCopy
- 8.3 FlashCopy functional overview
-
8.4 Implementing the SAN Volume Controller FlashCopy
- 8.4.1 FlashCopy mappings
- 8.4.2 Multiple Target FlashCopy
- 8.4.3 Consistency Groups
- 8.4.4 FlashCopy indirection layer
- 8.4.5 Grains and the FlashCopy bitmap
- 8.4.6 Interaction and dependency between multiple target FlashCopy mappings
- 8.4.7 Summary of the FlashCopy indirection layer algorithm
- 8.4.8 Interaction with the cache
- 8.4.9 FlashCopy and image mode volumes
- 8.4.10 FlashCopy mapping events
- 8.4.11 FlashCopy mapping states
- 8.4.12 Thin-provisioned FlashCopy
- 8.4.13 Background copy
- 8.4.14 Synthesis
- 8.4.15 Serialization of I/O by FlashCopy
- 8.4.16 Event handling
- 8.4.17 Asynchronous notifications
- 8.4.18 Interoperation with Metro Mirror and Global Mirror
- 8.4.19 FlashCopy presets
- 8.5 Volume mirroring and migration options
- 8.6 Native IP replication
-
8.7 Remote Copy
- 8.7.1 Multiple SVC system mirroring
- 8.7.2 Importance of write ordering
- 8.7.3 Remote copy intercluster communication
- 8.7.4 Metro Mirror overview
- 8.7.5 Synchronous remote copy
- 8.7.6 Metro Mirror features
- 8.7.7 Metro Mirror attributes
- 8.7.8 Global Mirror
- 8.7.9 Asynchronous remote copy
- 8.7.10 SVC Global Mirror features
- 8.7.11 Using Change Volumes with Global Mirror
- 8.7.12 Distribution of work among nodes
- 8.7.13 Background copy performance
- 8.7.14 Thin-provisioned background copy
- 8.7.15 Methods of synchronization
- 8.7.16 Practical use of Metro Mirror
- 8.7.17 Practical use of Global Mirror
- 8.7.18 Valid combinations of FlashCopy, Metro Mirror, and Global Mirror
- 8.7.19 Remote Copy configuration limits
- 8.7.20 Remote Copy states and events
-
8.8 Remote Copy commands
- 8.8.1 Remote Copy process
- 8.8.2 Listing available SVC system partners
- 8.8.3 Changing the system parameters
- 8.8.4 SVC system partnership
- 8.8.5 Creating a Metro Mirror/Global Mirror Consistency Group
- 8.8.6 Creating a Metro Mirror/Global Mirror relationship
- 8.8.7 Changing a Metro Mirror/Global Mirror relationship
- 8.8.8 Changing a Metro Mirror/Global Mirror Consistency Group
- 8.8.9 Starting a Metro Mirror/Global Mirror relationship
- 8.8.10 Stopping a Metro Mirror/Global Mirror relationship
- 8.8.11 Starting a Metro Mirror/Global Mirror Consistency Group
- 8.8.12 Stopping a Metro Mirror/Global Mirror Consistency Group
- 8.8.13 Deleting a Metro Mirror/Global Mirror relationship
- 8.8.14 Deleting a Metro Mirror/Global Mirror Consistency Group
- 8.8.15 Reversing a Metro Mirror/Global Mirror relationship
- 8.8.16 Reversing a Metro Mirror/Global Mirror Consistency Group
- 8.9 Troubleshooting remote copy
-
Chapter 9. SAN Volume Controller operations using the command-line interface
- 9.1 Normal operations by using CLI
- 9.2 New commands and functions
-
9.3 Working with managed disks and disk controller systems
- 9.3.1 Viewing disk controller details
- 9.3.2 Renaming a controller
- 9.3.3 Discovery status
- 9.3.4 Discovering MDisks
- 9.3.5 Viewing MDisk information
- 9.3.6 Renaming an MDisk
- 9.3.7 Including an MDisk
- 9.3.8 Adding MDisks to a storage pool
- 9.3.9 Showing MDisks in a storage pool
- 9.3.10 Working with a storage pool
- 9.3.11 Creating a storage pool
- 9.3.12 Viewing storage pool information
- 9.3.13 Renaming a storage pool
- 9.3.14 Deleting a storage pool
- 9.3.15 Removing MDisks from a storage pool
- 9.4 Working with hosts
- 9.5 Working with the Ethernet port for iSCSI
-
9.6 Working with volumes
- 9.6.1 Creating a volume
- 9.6.2 Volume information
- 9.6.3 Creating a thin-provisioned volume
- 9.6.4 Creating a volume in image mode
- 9.6.5 Adding a mirrored volume copy
- 9.6.6 Splitting a mirrored volume
- 9.6.7 Modifying a volume
- 9.6.8 I/O governing
- 9.6.9 Deleting a volume
- 9.6.10 Expanding a volume
- 9.6.11 Assigning a volume to a host
- 9.6.12 Showing volumes to host mapping
- 9.6.13 Deleting a volume to host mapping
- 9.6.14 Migrating a volume
- 9.6.15 Migrating a fully managed volume to an image mode volume
- 9.6.16 Shrinking a volume
- 9.6.17 Showing a volume on an MDisk
- 9.6.18 Showing which volumes are using a storage pool
- 9.6.19 Showing which MDisks are used by a specific volume
- 9.6.20 Showing from which storage pool a volume has its extents
- 9.6.21 Showing the host to which the volume is mapped
- 9.6.22 Showing the volume to which the host is mapped
- 9.6.23 Tracing a volume from a host back to its physical disk
- 9.7 Scripting under the CLI for SAN Volume Controller task automation
- 9.8 SAN Volume Controller advanced operations by using the CLI
-
9.9 Managing the clustered system by using the CLI
- 9.9.1 Viewing clustered system properties
- 9.9.2 Changing system settings
- 9.9.3 iSCSI configuration
- 9.9.4 Modifying IP addresses
- 9.9.5 Supported IP address formats
- 9.9.6 Setting the clustered system time zone and time
- 9.9.7 Starting statistics collection
- 9.9.8 Determining the status of a copy operation
- 9.9.9 Shutting down a clustered system
- 9.10 Nodes
- 9.11 I/O Groups
- 9.12 Managing authentication
-
9.13 Managing Copy Services
- 9.13.1 FlashCopy operations
- 9.13.2 Setting up FlashCopy
- 9.13.3 Creating a FlashCopy Consistency Group
- 9.13.4 Creating a FlashCopy mapping
- 9.13.5 Preparing (pre-triggering) the FlashCopy mapping
- 9.13.6 Preparing (pre-triggering) the FlashCopy Consistency Group
- 9.13.7 Starting (triggering) FlashCopy mappings
- 9.13.8 Starting (triggering) the FlashCopy Consistency Group
- 9.13.9 Monitoring the FlashCopy progress
- 9.13.10 Stopping the FlashCopy mapping
- 9.13.11 Stopping the FlashCopy Consistency Group
- 9.13.12 Deleting the FlashCopy mapping
- 9.13.13 Deleting the FlashCopy Consistency Group
- 9.13.14 Migrating a volume to a thin-provisioned volume
- 9.13.15 Reverse FlashCopy
- 9.13.16 Split-stopping of FlashCopy maps
-
9.14 Metro Mirror operation
- 9.14.1 Setting up Metro Mirror
- 9.14.2 Creating a SAN Volume Controller partnership between ITSO_SVC2 and ITSO_SVC4
- 9.14.3 Creating a Metro Mirror Consistency Group
- 9.14.4 Creating the Metro Mirror relationships
- 9.14.5 Creating a stand-alone Metro Mirror relationship for MM_App_Pri
- 9.14.6 Starting Metro Mirror
- 9.14.7 Starting a Metro Mirror Consistency Group
- 9.14.8 Monitoring the background copy progress
- 9.14.9 Stopping and restarting Metro Mirror
- 9.14.10 Stopping a stand-alone Metro Mirror relationship
- 9.14.11 Stopping a Metro Mirror Consistency Group
- 9.14.12 Restarting a Metro Mirror relationship in the Idling state
- 9.14.13 Restarting a Metro Mirror Consistency Group in the Idling state
- 9.14.14 Changing the copy direction for Metro Mirror
- 9.14.15 Switching the copy direction for a Metro Mirror relationship
- 9.14.16 Switching the copy direction for a Metro Mirror Consistency Group
- 9.14.17 Creating a SAN Volume Controller partnership among clustered systems
- 9.14.18 Star configuration partnership
-
9.15 Global Mirror operation
- 9.15.1 Setting up Global Mirror
- 9.15.2 Creating a SAN Volume Controller partnership between ITSO_SVC2 and ITSO_SVC4
- 9.15.3 Changing link tolerance and system delay simulation
- 9.15.4 Creating a Global Mirror Consistency Group
- 9.15.5 Creating Global Mirror relationships
- 9.15.6 Creating the stand-alone Global Mirror relationship for GM_App_Pri
- 9.15.7 Starting Global Mirror
- 9.15.8 Starting a stand-alone Global Mirror relationship
- 9.15.9 Starting a Global Mirror Consistency Group
- 9.15.10 Monitoring the background copy progress
- 9.15.11 Stopping and restarting Global Mirror
- 9.15.12 Stopping a stand-alone Global Mirror relationship
- 9.15.13 Stopping a Global Mirror Consistency Group
- 9.15.14 Restarting a Global Mirror relationship in the Idling state
- 9.15.15 Restarting a Global Mirror Consistency Group in the Idling state
- 9.15.16 Changing the direction for Global Mirror
- 9.15.17 Switching the copy direction for a Global Mirror relationship
- 9.15.18 Switching the copy direction for a Global Mirror Consistency Group
- 9.15.19 Changing a Global Mirror relationship to the cycling mode
- 9.15.20 Creating the thin-provisioned Change Volumes
- 9.15.21 Stopping the stand-alone remote copy relationship
- 9.15.22 Setting the cycling mode on the stand-alone remote copy relationship
- 9.15.23 Setting the Change Volume on the master volume
- 9.15.24 Setting the Change Volume on the auxiliary volume
- 9.15.25 Starting the stand-alone relationship in the cycling mode
- 9.15.26 Stopping the Consistency Group to change the cycling mode
- 9.15.27 Setting the cycling mode on the Consistency Group
- 9.15.28 Setting the Change Volume on the master volume relationships of the Consistency Group
- 9.15.29 Setting the Change Volumes on the auxiliary volumes
- 9.15.30 Starting the Consistency Group CG_W2K3_GM in the cycling mode
- 9.16 Service and maintenance
- 9.17 Backing up the SAN Volume Controller system configuration
- 9.18 Restoring the SAN Volume Controller clustered system configuration
- 9.19 Working with the SAN Volume Controller quorum MDisks
- 9.20 Working with the Service Assistant menu
- 9.21 SAN troubleshooting and data collection
- 9.22 T3 recovery process
-
Chapter 10. SAN Volume Controller operations using the GUI
- 10.1 Normal SVC operations using GUI
- 10.2 Monitoring menu
- 10.3 Working with external disk controllers
- 10.4 Working with storage pools
- 10.5 Working with managed disks
- 10.6 Migration
- 10.7 Working with hosts
-
10.8 Working with volumes
- 10.8.1 Volume information
- 10.8.2 Creating a volume
- 10.8.3 Renaming a volume
- 10.8.4 Modifying a volume
- 10.8.5 Modifying thin-provisioned or compressed volume properties
- 10.8.6 Deleting a volume
- 10.8.7 Deleting a host mapping
- 10.8.8 Deleting all host mappings for a volume
- 10.8.9 Shrinking a volume
- 10.8.10 Expanding a volume
- 10.8.11 Shrinking the real capacity of a thin-provisioned or compressed volume
- 10.8.12 Expanding the real capacity of a thin-provisioned or compressed volume
- 10.8.13 Migrating a volume
- 10.8.14 Adding a mirrored copy to an existing volume
- 10.8.15 Deleting a mirrored copy from a volume mirror
- 10.8.16 Splitting a volume copy
- 10.8.17 Validating volume copies
- 10.8.18 Migrating to a thin-provisioned volume by using volume mirroring
- 10.8.19 Creating a volume in image mode
- 10.8.20 Migrating a volume to an image mode volume
- 10.8.21 Creating an image mode mirrored volume
-
10.9 Copy Services and managing FlashCopy
- 10.9.1 Creating a FlashCopy mapping
- 10.9.2 Single-click snapshot
- 10.9.3 Single-click clone
- 10.9.4 Single-click backup
- 10.9.5 Creating a FlashCopy Consistency Group
- 10.9.6 Creating FlashCopy mappings in a Consistency Group
- 10.9.7 Showing related volumes
- 10.9.8 Moving a FlashCopy mapping to a Consistency Group
- 10.9.9 Removing a FlashCopy mapping from a Consistency Group
- 10.9.10 Modifying a FlashCopy mapping
- 10.9.11 Renaming a FlashCopy mapping
- 10.9.12 Renaming a Consistency Group
- 10.9.13 Deleting a FlashCopy mapping
- 10.9.14 Deleting a FlashCopy Consistency Group
- 10.9.15 Starting the FlashCopy copy process
- 10.9.16 Stopping the FlashCopy copy process
-
10.10 Copy Services: Managing remote copy
- 10.10.1 System partnership
- 10.10.2 Creating a Fibre Channel partnership between two remote SVC systems
- 10.10.3 Creating an IP partnership between remote SVC systems
- 10.10.4 Creating stand-alone remote copy relationships
- 10.10.5 Creating a Consistency Group
- 10.10.6 Renaming a Consistency Group
- 10.10.7 Renaming a remote copy relationship
- 10.10.8 Moving a stand-alone remote copy relationship to a Consistency Group
- 10.10.9 Removing a remote copy relationship from a Consistency Group
- 10.10.10 Starting a remote copy relationship
- 10.10.11 Starting a remote copy Consistency Group
- 10.10.12 Switching the copy direction for a remote copy relationship
- 10.10.13 Switching the copy direction for a Consistency Group
- 10.10.14 Stopping a remote copy relationship
- 10.10.15 Stopping a Consistency Group
- 10.10.16 Deleting stand-alone remote copy relationships
- 10.10.17 Deleting a Consistency Group
-
10.11 Managing the SAN Volume Controller clustered system by using the GUI
- 10.11.1 System status information
- 10.11.2 View I/O Groups and their associated nodes
- 10.11.3 View SVC clustered system properties
- 10.11.4 Renaming the SAN Volume Controller clustered system
- 10.11.5 Renaming the site information of the nodes
- 10.11.6 Rename a node
- 10.11.7 Shutting down the SAN Volume Controller clustered system
- 10.11.8 Power off a single node
- 10.12 Upgrading software
- 10.13 Managing I/O Groups
- 10.14 Managing nodes
- 10.15 Troubleshooting
- 10.16 User management
- 10.17 Configuration
- 10.18 Upgrading the SAN Volume Controller software
- Appendix A. Performance data and statistics gathering
- Appendix B. Terminology
- Appendix C. SAN Volume Controller stretched cluster
- 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: Implementing the IBM System Storage SAN Volume Controller V7.4
- Author(s):
- Release date: April 2015
- Publisher(s): IBM Redbooks
- ISBN: 9780738440460
You might also like
book
Implementing the IBM System Storage SAN Volume Controller V7.2
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 …
book
Implementing the IBM System Storage SAN Volume Controller with IBM Spectrum Virtualize V8.1
Abstract This IBM® Redbooks publication is a detailed technical guide to the IBM System Storage® SAN …
book
Implementing the IBM System Storage SAN Volume Controller with IBM Spectrum Virtualize Version 8.4
Continuing its commitment to developing and delivering industry-leading storage technologies, IBM® introduces the IBM FlashSystem® solution …