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
Disk Drives: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
10-15
Recovery Operations for a Nearly Full Database File
Recovery Operations for a Nearly Full Database File
When a database file is 90 percent full or more, you can modify the file extents
dynamically with FUP or perform other procedures according to your system policies.
To allocate additional extents to the file MEMOS:
> FUP
- ALTER MEMOS, MAXEXTENTS 20
- INFO MEMOS, DETAIL
A report such as this one is sent to your home terminal:
This report shows that the maximum extents allocated to this file have been increased
to 20 and that the file MEMOS is now only 78.5% full.
Related Reading
Note. Allocating additional extents to any file causes that file to take up more disk space.
Before you change the maximum allowable extents for any file, as shown in the next example,
check your local procedures to determine whether this is the appropriate action for you to take.
$DATA.DATA1.MEMOS 12 Jul 1993, 14:05
ENSCRIBE
TYPE U
CODE 101
EXT ( 2 PAGES, 2 PAGES )
ODDUNSTR
MAXEXTENTS 20
BUFFERSIZE 4096
OWNER 8,255
SECURITY (RWEP): NUNU
DATA MODIF: 12 Jul 1993, 14:04
CREATION DATE: 12 Jan 1993, 14:04
LAST OPEN: 12 Jul 1993, 14:24
EOF 567022 (78.5% USED)
FILE LABEL: 649 (22.8% USED)
EXTENTS ALLOCATED: 10
For information about See
Complete syntax, examples, and considerations for the
SCF commands used in this section
SCF Reference Manual for the
Storage Subsystem
Utilities such as:
•
DCOM
•
DSAP
•
BACKUP
•
RESTORE
Guardian Disk and Tape Utilities
Reference Manual
Other operations procedures involving disk drives Guardian User’s Guide