SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

HP NonStop SQL/MX Installation and Management Guide—523723-004
12-1
12
Performing Recovery Operations
The success of recovery operations depends on the effectiveness and consistency of
the plan you develop for handling recovery situations. (See Planning Database
Recovery on page 5-6.) Before beginning a recovery operation, you should thoroughly
evaluate the tools available (RDF, TMF online dumps, backup tapes, and so forth) and
appropriate for the type of failure.
This section addresses these topics:
•
Recovering Databases After Disk or Node Failures on page 12-1
•
Recovering Disk Volumes on page 12-2
•
Recovering Files on page 12-2
•
Recovering Metadata on page 12-6
•
Recovering Database Objects on page 12-7
•
Restoring Objects With BRCOM RESTORE on page 12-21
•
Repairing Damaged SQL/MX Metadata and Objects on page 12-24
•
Using GOAWAY to Delete Damaged Objects on page 12-35
•
Recovering From SCF Commands on page 12-35
This section generally contains information specific to recovering SQL/MX database
objects. For information about recovering SQL/MP objects, see the SQL/MP
Installation and Management Guide and the Backup and Restore 2 Manual.
Recovering Databases After Disk or Node
Failures
When a disk or node (system) fails, SQL/MX tables and database files on the disk or
node are often left in a crash-open state. To recover the database, both the catalogs
and the files must be recovered to a consistent state.
Normally, TMF volume recovery automatically recovers the database after a disk or
node failure. See Recovering Disk Volumes on page 12-2. However, if one or more
disks have media failures and cannot be recovered by volume recovery, use TMF file
recovery. See Recovering Files on page 12-2. You have these options:
•
Use the file recovery method to recover the database, starting with online dumps,
which include files containing copies of consistent catalogs and objects saved by
the TMF DUMP FILES command. The file recovery function starts with saved files
and updates transactions to the last consistent point in the audit trails.