HSG80 ACS Solution Software Version 8.7 for Compaq Tru64 UNIX Installation and Configuration Guide
Table Of Contents
- HSG80 ACS Solution Software Version 8.7 for Compaq Tru64 UNIX Installation and Configuration Guide
- About this Guide
- 1- Planning a Subsystem
- Defining Subsystems
- What is Failover Mode?
- Selecting a Cache Mode
- Enabling Mirrored Caching
- What is the Command Console LUN?
- Determining Connections
- Assigning Unit Numbers
- What is Selective Storage Presentation?
- 2- Planning Storage Configurations
- Where to Start
- Determining Storage Requirements
- Configuration Rules for the Controller
- Addressing Conventions for Device PTL
- Choosing a Container Type
- Creating a Storageset Profile
- Planning Considerations for Storageset
- Changing Characteristics through Switches
- Specifying Storageset and Partition Switches
- Specifying Initialization Switches
- Specifying Unit Switches
- Creating Storage Maps
- 3- Preparing the Host System
- Installing RAID Array Storage System
- Making a Physical Connection
- Preparing LUNs for Access by Tru64 UNIX FileSystem
- DECsafe Available Server Environment (ASE)
- HSG80 Units and Tru64 UNIX Utilities
- Solution Software Upgrade Procedures
- New Features, ACS 8.7 for Tru64
- 4- Installing and Configuring HSG Agent
- 5- FC Configuration Procedures
- Establishing a Local Connection
- Setting Up a Single Controller
- Setting Up a Controller Pair
- Configuring Devices
- Configuring Storage Containers
- Assigning Unit Numbers and Unit Qualifiers
- Configuration Options
- Verifying Storage Configuration from Host
- 6- Using CLI for Configuration
- 7- Backing Up, Cloning, and Moving Data
- 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
- B- Installing, Configuring, and Removing the Client
- C- SWCC Agent in TruCluster Environment
- SWCC Overview
- Running the SWCC Agent on a V4.0G Cluster
- Running the SWCC Agent under ASE Services
- Running the SWCC Agent on a V5.x Cluster
- Problems with Running the Agent on Multiple Clusters
- Configure the Controller
- Use Multiple-Bus Failover Mode
- Verify That the HSG80/HSG60 Unit Offsets Are Zero
- Install and Run the Agent on One Cluster Member
- Example of Installing the Agent on a Cluster Member
- Create the CAA Action Script
- Create the CAA Resource
- Glossary
- Index
Planning Storage Configurations
2–20 HSG80 ACS Solution Software Version 8.7 for Compaq Tru64 UNIX 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.