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 a Subsystem
1–10 HSG80 ACS Solution Software Version 8.7 for Compaq Tru64 UNIX Installation and
Configuration Guide
Read Caching
When the controller receives a read request from the host, it reads the data from the
disk drives, delivers it to the host, and stores the data in its cache module. Subsequent
reads for the same data will take the data from cache rather than accessing the data
from the disks. This process is called read caching.
Read caching can improve response time to many of the host’s read requests. By
default, read caching is enabled for all units.
Read-Ahead Caching
During read-ahead caching, the controller anticipates subsequent read requests and
begins to prefetch the next blocks of data from the disks as it sends the requested read
data to the host. This is a parallel action. The controller notifies the host of the read
completion, and subsequent sequential read requests are satisfied from the cache
memory. By default, read-ahead caching is enabled for all units.
Write-Back Caching
Write-back caching improves the subsystem’s response time to write requests by
allowing the controller to declare the write operation complete as soon as the data
reaches cache memory. The controller performs the slower operation of writing the
data to the disk drives at a later time.
By default, write-back caching is enabled for all units, but only if there is a backup
power source for the cache modules (either batteries or an uninterruptable power
supply).
Write-Through Caching
Write-through caching is enabled when write-back caching is disabled. When the
controller receives a write request from the host, it places the data in its cache module,
writes the data to the disk drives, then notifies the host when the write operation is
complete. This process is called write-through caching because the data actually
passes through—and is stored in—the cache memory on its way to the disk drives.
Enabling Mirrored Caching
In mirrored caching, half of each controller’s cache mirrors the companion controller’s
cache, as shown in Figure 1–8.