NonStop NS-Series Operations Guide (H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Guide
- 1 Introduction to Integrity NonStop NSSeries Operations
- When to Use This Section
- Understanding the Operational Environment
- What Are the Operator Tasks?
- Monitoring the System and Performing Recovery Operations
- Preparing for and Recovering from Power Failures
- Stopping and Powering Off theSystem
- Powering On and Starting the System
- Creating Startup and Shutdown Files
- Performing Preventive Maintenance
- Operating Disk Drives and Tape Drives
- Responding to Spooler Problems
- Updating Firmware
- Determining the Cause of a Problem: A Systematic Approach
- Logging On to an Integrity NonStop Server
- Service Procedures
- 2 Determining Your System Configuration
- 3 Overview of Monitoring and Recovery
- 4 Monitoring EMS Event Messages
- 5 Processes: Monitoring and Recovery
- 6 Communications Subsystems: Monitoring and Recovery
- 7 ServerNet Resources: Monitoring and Recovery
- 8 I/O Adapters and Modules: Monitoring and Recovery
- 9 Processors and Components: Monitoring and Recovery
- When to Use This Section
- Overview of the NonStop Blade Complex
- Monitoring and Maintaining Processors
- Identifying Processor Problems
- Recovery Operations for Processors
- Recovery Operations for a Processor Halt
- Halting One or More Processors
- Reloading a Single Processor on a Running Server
- Recovery Operations for a System Hang
- Enabling/Disabling Processor and System Freeze
- Freezing the System and Freeze-Enabled Processors
- Dumping a Processor to Disk
- Backing Up a Processor Dump to Tape
- Replacing Processor Memory
- Replacing the Processor Board and Processor Entity
- Submitting Information to Your Service Provider
- Related Reading
- 10 Disk Drives: Monitoring and Recovery
- 11 Tape Drives: Monitoring and Recovery
- 12 Printers and Terminals: Monitoring and Recovery
- 13 Applications: Monitoring and Recovery
- 14 Power Failures: Preparation and Recovery
- 15 Starting and Stopping the System
- When to Use This Section
- Powering On a System
- Starting a System
- Minimizing the Frequency of Planned Outages
- Stopping Application, Devices, and Processes
- Stopping the System
- Powering Off a System
- Troubleshooting and Recovery Operations
- Fans Are Not Turning
- System Does Not Appear to Be Powered On
- Green LED Is Not Lit After POSTs Finish
- Amber LED on a Component Remains Lit After the POST Finishes
- Components Fail When Testing the Power
- Recovering From a System Load Failure
- Getting a Corrupt System Configuration File Analyzed
- Recovering From a Reload Failure
- Exiting the OSM Low-Level Link
- Opening Startup Event Stream and Startup TACL Windows
- Related Reading
- 16 Creating Startup and Shutdown Files
- Automating System Startup and Shutdown
- Processes That Represent the System Console
- Example Command Files
- CIIN File
- Writing Efficient Startup and Shutdown Command Files
- How Process Persistence Affects Configuration and Startup
- Tips for Startup Files
- Startup File Examples
- Tips for Shutdown Files
- Shutdown File Examples
- 17 Preventive Maintenance
- A Operational Differences Between Systems Running GSeries and HSeries RVUs
- B Tools and Utilities for Operations
- When to Use This Appendix
- BACKCOPY
- BACKUP
- Disk Compression Program (DCOM)
- Disk Space Analysis Program (DSAP)
- EMSDIST
- Event Management Service Analyzer (EMSA)
- File Utility Program (FUP)
- Measure
- MEDIACOM
- NonStop NET/MASTER
- NSKCOM and the Kernel-Managed Swap Facility (KMSF)
- OSM Package
- PATHCOM
- PEEK
- RESTORE
- SPOOLCOM
- Subsystem Control Facility (SCF)
- HP Tandem Advanced Command Language (TACL)
- TMFCOM
- Web ViewPoint
- ViewPoint
- ViewSys
- C Related Reading
- D Converting Numbers
- Safety and Compliance
- Index
Tape Drives: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
11-8
Recovery Operations for Tape Drives
Recovery Operations for Tape Drives
You can perform recovery operations on tape drives using either the SCF interface to
the storage subsystem or the OSM Service Connection.
Recovery Operations Using the OSM Service Connection
If the recovery operation calls for an OSM Service Connection action, you can perform
an action on one or more tape drive objects.
Performing an OSM Action on a Tape Drive
1. From the OSM Service Connection tree pane (the left-hand pane shown in
Figure 11-1 on page 11-3):
a. Expand the System and Tape Collection objects to locate the tape drive in
need of attention or service.
b. Right-click the tape drive object and select Actions from the menu.
2. In the Actions dialog box:
a. Choose the desired action from the list of available actions.
b. Click Perform action.
c. Check the Action Status window to confirm successful completion of the action,
or click Details for more information if the action fails.
Also, check the Alarms or Attributes tab to make sure the alarm has been
cleared or the degraded attribute value has returned to normal. Using the
example in Figure 11-1, you might use the Start action to bring up the selected
(highlighted) tape drive. If successful, the Device State should change from
Hard Down to Started, and the yellow symbol in both the tree pane and
Attributes tab should disappear.
In many cases, there are OSM and SCF equivalents. For example, you can
select the OSM Start action or the corresponding SCF START command.
Performing an OSM Action on a Multiple Tape Drives
1. From the Display menu, select Multi-Resource Actions.
2. In the Multi-Resource Actions dialog box, select the Tape Drive object to display a
list of all tape drives on the system.
3. From this list, select the tape drives upon which you want to perform the action
(using the Ctrl key to select multiple tape drives).
4. From the Action drop-down menu, select the desired action.
5. Click Perform Action.