Book description
This IBM® Redbooks® publication is a detailed technical guide to the IBM System Storage® SAN Volume Controller Version 7.2.
SAN Volume Controller 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 must implement the SAN
Volume Controller at a 7.2 release level with minimal
effort.
Table of contents
- Front cover
- Notices
- Preface
- Summary of changes
- Chapter 1. Introduction to storage virtualization
-
Chapter 2. IBM System Storage 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 via 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 Solid-state drives
- 2.12 Easy Tier
- 2.13 What is new with SAN Volume Controller 7.2
- 2.14 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 Split-cluster system configuration
- 3.3.8 Storage pool configuration
- 3.3.9 Virtual disk 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 SAN Volume Controller 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 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 Windows specific 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 the Windows Server
- 5.5.6 Installing the SDDDSM multipath driver on Windows
- 5.5.7 Attaching SAN Volume Controller volumes to Windows Server 2008 R2 and Windows Server 2012
- 5.5.8 Extending a Windows Server 2008 (R2) volume
- 5.5.9 Removing a disk on Windows
- 5.6 Using the 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.9.12 Operating system versions and maintenance levels
- 5.9.13 SDD dynamic pathing
- 5.10 Hewlett-Packard UNIX configuration information
- 5.11 Using SDDDSM, SDDPCM, and SDD web interface
- 5.12 Calculating the queue depth
- 5.13 For 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 SAN Volume Controller GUI
- 6.5.1 Windows Server 2008 host system connected directly to the LSI 3500
- 6.5.2 Adding SAN Volume Controller between host system and LSI 3500
- 6.5.3 Importing the migrated disks into an online Windows Server 2008 host
- 6.5.4 Adding SAN Volume Controller between the host and LSI 3500 using 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 SAN Volume Controller
- 6.5.8 Mapping the free disks onto the Windows Server 2008
-
6.6 Migrating Linux SAN disks to SAN Volume Controller disks
- 6.6.1 Connecting the SAN Volume Controller to your SAN fabric
- 6.6.2 Preparing your SAN Volume Controller to virtualize disks
- 6.6.3 Moving the LUNs to the SAN Volume Controller
- 6.6.4 Migrating the image mode volumes to managed MDisks
- 6.6.5 Preparing to migrate from the SAN Volume Controller
- 6.6.6 Migrating the volumes to image mode volumes
- 6.6.7 Removing the LUNs from the SAN Volume Controller
-
6.7 Migrating ESX SAN disks to SAN Volume Controller disks
- 6.7.1 Connecting the SAN Volume Controller to your SAN fabric
- 6.7.2 Preparing your SAN Volume Controller to virtualize disks
- 6.7.3 Moving the LUNs to the SAN Volume Controller
- 6.7.4 Migrating the image mode volumes
- 6.7.5 Preparing to migrate from the SAN Volume Controller
- 6.7.6 Migrating the managed volumes to image mode volumes
- 6.7.7 Removing the LUNs from the SAN Volume Controller
-
6.8 Migrating AIX SAN disks to SAN Volume Controller volumes
- 6.8.1 Connecting the SAN Volume Controller to your SAN fabric
- 6.8.2 Preparing your SAN Volume Controller to virtualize disks
- 6.8.3 Moving the LUNs to the SAN Volume Controller
- 6.8.4 Migrating image mode volumes to volumes
- 6.8.5 Preparing to migrate from the SAN Volume Controller
- 6.8.6 Migrating the managed volumes
- 6.8.7 Removing the LUNs from the SAN Volume Controller
- 6.9 Using SAN Volume Controller for storage migration
- 6.10 Using volume mirroring and thin-provisioned volumes together
- Chapter 7. Advanced features for storage efficiency
-
Chapter 8. Advanced Copy Services
- 8.1 FlashCopy
- 8.2 Reverse FlashCopy
- 8.3 FlashCopy functional overview
-
8.4 Implementing 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.6.1 Native IP Replication Technology
- 8.6.2 IP partnership limitations
- 8.6.3 IP partnership and SAN Volume Controller terminology
- 8.6.4 States of IP partnership
- 8.6.5 Remote Copy Groups
- 8.6.6 Supported configurations
- 8.6.7 Setting up SAN Volume Controller system IP partnership by using the SAN Volume Controller GUI
-
8.7 Metro Mirror
- 8.7.1 Metro Mirror overview
- 8.7.2 Remote copy techniques
- 8.7.3 Metro Mirror features
- 8.7.4 Multiple SAN Volume Controller System Mirroring
- 8.7.5 Importance of write ordering
- 8.7.6 Remote copy intercluster communication
- 8.7.7 Metro Mirror attributes
- 8.7.8 Methods of synchronization
- 8.7.9 Metro Mirror states and events
- 8.7.10 Practical use of Metro Mirror
- 8.7.11 Valid combinations of FlashCopy, Metro Mirror, and Global Mirror
- 8.7.12 Metro Mirror configuration limits
-
8.8 Metro Mirror commands
- 8.8.1 Listing available SAN Volume Controller system partners
- 8.8.2 Creating the SAN Volume Controller system partnership
- 8.8.3 Creating a Metro Mirror Consistency Group
- 8.8.4 Creating a Metro Mirror relationship
- 8.8.5 Changing a Metro Mirror relationship
- 8.8.6 Changing a Metro Mirror Consistency Group
- 8.8.7 Starting a Metro Mirror relationship
- 8.8.8 Stopping a Metro Mirror relationship
- 8.8.9 Starting a Metro Mirror Consistency Group
- 8.8.10 Stopping a Metro Mirror Consistency Group
- 8.8.11 Deleting a Metro Mirror relationship
- 8.8.12 Deleting a Metro Mirror Consistency Group
- 8.8.13 Reversing a Metro Mirror relationship
- 8.8.14 Reversing a Metro Mirror Consistency Group
- 8.8.15 Background copy
-
8.9 Global Mirror
- 8.9.1 Intracluster Global Mirror
- 8.9.2 Intercluster Global Mirror
- 8.9.3 Asynchronous remote copy
- 8.9.4 SAN Volume Controller Global Mirror features
- 8.9.5 Global Mirror relationship between master and auxiliary volumes
- 8.9.6 Using Change Volumes with Global Mirror
- 8.9.7 Importance of write ordering
- 8.9.8 Global Mirror Consistency Groups
- 8.9.9 Distribution of work among nodes
- 8.9.10 Background copy performance
- 8.9.11 Thin-provisioned background copy
- 8.10 Global Mirror process
-
8.11 Global Mirror commands
- 8.11.1 Listing the available SAN Volume Controller system partners
- 8.11.2 Creating a SAN Volume Controller system partnership
- 8.11.3 Creating a Global Mirror Consistency Group
- 8.11.4 Creating a Global Mirror relationship
- 8.11.5 Changing a Global Mirror relationship
- 8.11.6 Changing a Global Mirror Consistency Group
- 8.11.7 Starting a Global Mirror relationship
- 8.11.8 Stopping a Global Mirror relationship
- 8.11.9 Starting a Global Mirror Consistency Group
- 8.11.10 Stopping a Global Mirror Consistency Group
- 8.11.11 Deleting a Global Mirror relationship
- 8.11.12 Deleting a Global Mirror Consistency Group
- 8.11.13 Reversing a Global Mirror relationship
- 8.11.14 Reversing a Global Mirror Consistency Group
- 8.12 Troubleshooting remote copy
-
Chapter 9. Perfoming SAN Volume Controller operations by using the command-line interface
- 9.1 Normal operations by using CLI
- 9.2 New commands
-
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 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) 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_SVC1 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 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_SVC1 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 by using the GUI
- 10.1 Normal SAN Volume Controller operations that use the GUI
- 10.2 Working with external disk controllers
- 10.3 Working with storage pools
- 10.4 Working with managed disks
- 10.5 Migration
- 10.6 Working with hosts
-
10.7 Working with volumes
- 10.7.1 Volume information
- 10.7.2 Creating a volume
- 10.7.3 Renaming a volume
- 10.7.4 Modifying a volume
- 10.7.5 Modifying thin-provisioned or compressed volume properties
- 10.7.6 Deleting a volume
- 10.7.7 Creating or modifying the host mapping
- 10.7.8 Deleting a host mapping
- 10.7.9 Deleting all host mappings for a volume
- 10.7.10 Shrinking a volume
- 10.7.11 Expanding a volume
- 10.7.12 Shrinking the real capacity of a thin-provisioned or compressed volume
- 10.7.13 Expanding the real capacity of a thin-provisioned or compressed volume
- 10.7.14 Migrating a volume
- 10.7.15 Adding a mirrored copy to an existing volume
- 10.7.16 Deleting a mirrored copy from a volume mirror
- 10.7.17 Splitting a volume copy
- 10.7.18 Validating volume copies
- 10.7.19 Migrating to a thin-provisioned volume using volume mirroring
- 10.7.20 Creating a volume in image mode
- 10.7.21 Migrating a volume to an image mode volume
- 10.7.22 Creating an image mode mirrored volume
-
10.8 Copy Services and managing FlashCopy
- 10.8.1 Creating a FlashCopy mapping
- 10.8.2 Creating and starting a snapshot preset with a single click
- 10.8.3 Creating and starting a clone preset with a single click
- 10.8.4 Creating and starting a backup preset with a single click
- 10.8.5 Creating a FlashCopy Consistency Group
- 10.8.6 Creating FlashCopy mappings in a Consistency Group
- 10.8.7 Showing related volumes
- 10.8.8 Moving a FlashCopy mapping to a Consistency Group
- 10.8.9 Removing a FlashCopy mapping from a Consistency Group
- 10.8.10 Modifying a FlashCopy mapping
- 10.8.11 Renaming a FlashCopy mapping
- 10.8.12 Renaming a Consistency Group
- 10.8.13 Deleting a FlashCopy mapping
- 10.8.14 Deleting a FlashCopy Consistency Group
- 10.8.15 Starting the FlashCopy copy process
- 10.8.16 Stopping the FlashCopy copy process
- 10.8.17 Starting a FlashCopy Consistency Group copy process
- 10.8.18 Stopping the FlashCopy Consistency Group copy process
- 10.8.19 Migrating between a fully allocated volume and a Space-Efficient volume
- 10.8.20 Reversing and splitting a FlashCopy mapping
-
10.9 Copy Services: Managing remote copy
- 10.9.1 System partnership
- 10.9.2 Creating the Fibre Channel partnership between two remote SAN Volume Controller systems
- 10.9.3 Creating IP partnership between remote SAN Volume Controller systems
- 10.9.4 Creating stand-alone remote copy relationships
- 10.9.5 Creating a Consistency Group
- 10.9.6 Renaming a Consistency Group
- 10.9.7 Renaming a remote copy relationship
- 10.9.8 Moving a stand-alone remote copy relationship to a Consistency Group
- 10.9.9 Removing a remote copy relationship from a Consistency Group
- 10.9.10 Starting a remote copy relationship
- 10.9.11 Starting a remote copy Consistency Group
- 10.9.12 Switching the copy direction for a remote copy relationship
- 10.9.13 Switching the copy direction for a Consistency Group
- 10.9.14 Stopping a remote copy relationship
- 10.9.15 Stopping a Consistency Group
- 10.9.16 Deleting stand-alone remote copy relationships
- 10.9.17 Deleting a Consistency Group
- 10.10 Managing the SAN Volume Controller clustered system by using the GUI
- 10.11 Managing I/O Groups
- 10.12 Managing nodes
- 10.13 Troubleshooting
- 10.14 User Management
-
10.15 Configuration
- 10.15.1 Configuring the network
- 10.15.2 Configuring the service IP addresses
- 10.15.3 Configuring Ethernet ports
- 10.15.4 iSCSI configuration
- 10.15.5 Fibre Channel information
- 10.15.6 Event notifications
- 10.15.7 Email notifications
- 10.15.8 SNMP notifications
- 10.15.9 Using the General panel
- 10.15.10 Date and time
- 10.15.11 Licensing
- 10.15.12 Upgrading software
- 10.15.13 Setting GUI preferences
- 10.16 Upgrading SAN Volume Controller software
-
10.17 Service Assistant Tool with the GUI
- 10.17.1 Placing a SAN Volume Controller node into the service state
- 10.17.2 Exiting the service state
- 10.17.3 Rebooting a SAN Volume Controller node
- 10.17.4 Collect Logs page
- 10.17.5 Manage System page
- 10.17.6 Recover System page
- 10.17.7 Reinstall software
- 10.17.8 Upgrade Manually page
- 10.17.9 Modify WWNN page
- 10.17.10 Change Service IP page
- 10.17.11 Configure CLI Access page
- 10.17.12 Restart Service page
- 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.2
- Author(s):
- Release date: July 2014
- Publisher(s): IBM Redbooks
- ISBN: None
You might also like
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 …
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
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 …