HSG80 ACS Solution Software V8.6 for IBM AIM Installation and Configuration Guide
Table Of Contents
- HSG80 ACS Solution Software Version 8.6 for IBM AIX
- Contents
- Figures
- Tables
- About this Guide
- Chapter 1
- Planning a Subsystem
- Chapter 2
- Planning Storage
- Where to Start
- Configuration Rules
- Device PTL Addressing Convention
- Determining Storage Requirements
- Choosing a Container Type
- Creating a Storageset Profile
- Storageset Planning Considerations
- Storageset Expansion Considerations
- Partition Planning Considerations
- Changing Characteristics through Switches
- Storageset and Partition Switches
- Initialization Switches
- Unit Switches
- Storage Maps
- Chapter 3
- Preparing the Host System
- Chapter 4
- Installing and Configuring the HS-Series Agent
- Why Use StorageWorks Command Console (SWCC)?
- Installation and Configuration Overview
- About the Network Connection for the Agent
- Before Installing the Agent
- Installing and Configuring the Agent
- Running the Agent
- Reconfiguring the Agent
- Uninstall Agent, Storageworks Software, and Cambex Driver.
- High Availability Cluster Multi-Processor (HACMP)
- Enabler Software
- General Note on Software Installation
- SWCC Clients
- Running the Agent
- HACMP Implementation for the Agent
- Prerequisites
- Implementation
- Installing the Agent on an HACMP Cluster
- Installing and Configuring the Client on an HACMP cluster
- Operation of the Agent on an HACMP Cluster
- Normal Operation of the Agent on an HACMP Cluster
- Starting, Stopping and Checking for the Agent
- Password and Notification
- Client Functions and Storage Subsystem Options
- Failover with Agent as Part of a Resource Group
- Client IP Address
- Event Scripts
- Notification within HACMP
- Node Isolation Recovery
- Failure of the Agent
- Polling all nodes in cluster for presence of a running Agent
- Restarting the Agent on surviving node
- Notification
- Supporting Tools
- HACMP for AIX Primary Event Scripts
- HACMP for AIX Secondary Event Scripts
- Chapter 5
- Configuration Procedures
- Establishing a Local Connection
- Setting Up a Single Controller
- Setting Up a Controller Pair
- Configuring Devices
- Configuring a Stripeset
- Configuring a Mirrorset
- Configuring a RAIDset
- Configuring a Striped Mirrorset
- Configuring a Single-Disk Unit (JBOD)
- Configuring a Partition
- Assigning Unit Numbers and Unit Qualifiers
- Configuration Options
- Chapter 6
- Verifying Storage Configuration from the Host
- Chapter 7
- Configuration Example Using CLI
- Chapter 8
- Backing Up the Subsystem, Cloning Data for Backup, and Moving Storagesets
- Appendix A
- Subsystem Profile Templates
- Storageset Profile
- Storage Map Template 1 for the BA370 Enclosure
- Storage Map Template 2 for the second BA370 Enclosure
- Storage Map Template 3 for the third BA370 Enclosure
- Storage Map Template 4 for the Model 4214R Disk Enclosure
- Storage Map Template 5 for the Model 4254 Disk Enclosure
- Storage Map Template 6 for the Model 4310R Disk Enclosure
- Storage Map Template 7 for the Model 4350R Disk Enclosure
- Storage Map Template 8 for the Model 4314R Disk Enclosure
- Storage Map Template 9 for the Model 4354R Disk Enclosure
- Appendix B
- Installing, Configuring, and Removing the Client
- Appendix C
- Exploitation of the CLONE and SNAPSHOT Functions of the HSG80 in an AIX Environment
- Glossary
- Index
2–16 HSG80 ACS Solution Software Version 8.6 for IBM AIX Installation and Configuration Guide
■ Striping does not protect against data loss. In fact, because the failure of one member is
equivalent to the failure of the entire stripeset, the likelihood of losing data is higher
for a stripeset than for a single disk drive.
For example, if the mean time between failures (MTBF) for a single disk is l hour, then
the MTBF for a stripeset that comprises N such disks is l/N hours. As another example,
if the MTBF of a a single disk is 150,000 hours (about 17 years), a stripeset
comprising four of these disks would only have an MTBF of slightly more than 4
years.
For this reason, you should avoid using a stripeset to store critical data. Stripesets are
more suitable for storing data that can be reproduced easily or whose loss does not
prevent the system from supporting its critical mission.
■ Evenly distribute the members across the device ports to balance the load and provide
multiple paths.
■ Stripesets may contain between two and 24 members.
■ If you plan to use mirror members to replace failing drives, then create the original
stripeset as a stripeset of 1-member mirrorsets.
■ Stripesets are well-suited for the following applications:
❏ Storing program image libraries or run-time libraries for rapid loading.
❏ Storing large tables or other structures of read-only data for rapid application
access.
❏ Collecting data from external sources at very high data transfer rates.
■ Stripesets are not well-suited for the following applications:
❏ A storage solution for data that cannot be easily reproduced or for data that must be
available for system operation.
❏ Applications that make requests for small amounts of sequentially located data.
❏ Applications that make synchronous random requests for small amounts of data.
Spread the member drives as evenly as possible across the six I/O device ports.
Mirrorset Planning Considerations
Mirrorsets (RAID 1) use redundancy to ensure availability, as illustrated in Figure 2–12.
For each primary disk drive, there is at least one mirror disk drive. Thus, if a primary disk
drive fails, its mirror drive immediately provides an exact copy of the data. Figure 2–13
shows a second example of a Mirrorset.