TMF Operations and Recovery Guide (G06.24+)

Recovery Methods
HP NonStop TMF Operations and Recovery Guide—522417-002
7-26
Restoring the ZTMFCONF Subvolume
•
Create reports including changed records (rows) and compare the output to
expected results. You can do this with an application report generator (if one
exists), with Enform, or with the report writer feature in the SQL conversational
interface.
•
Check the contents of the TMF audit trail to verify the correctness of transaction
after-images. You can do this with a user-written application that invokes the TMF
audit-reading procedures, or with a third-party software package designed to read
and format data from the TMF audit trail. Refer to the TMF Application
Programmer’s Guide for information on the TMF audit-reading procedures.
See Responding to Incorrect Updates to the Database on page 7-21 for information on
recovering the database.
Restoring the ZTMFCONF Subvolume
If the TMF configuration subvolume, ZTMFCONF, becomes damaged or corrupted,
TMF could shut down abruptly and not be able to restart. Particularly significant to the
TMF environment, all audit-trail configuration information is lost. Because the
ZTMFCONF subvolume typically resides on $SYSTEM, it is likely that the $SYSTEM
volume is also damaged or corrupted, which requires a complete system reload.
If your system’s configuration volume is on $SYSTEM, follow the procedure below to
recover the ZTMFCONF subvolume. The ZTMFCONF subvolume can reside on any
volume in the system. If the configuration subvolume on your system is on a volume
other than $SYSTEM, use that volume name in the procedure that follows, and skip
Step 1.
Use the following procedure to recover the ZTMFCONF subvolume:
1. If only one drive of your mirrored system disk ($SYSTEM) is usable, the system
automatically uses that drive.
If neither drive of your mirrored system disk is usable, you must restore your
system disk from the system image tape (SIT) that was created when the system
was installed.
Refer to the recovery procedures established for your system and the appropriate
system operations manual for more information.
2. Rename the existing TMF configuration subvolume.
The existing configuration files are either damaged or, if you introduced a new
$SYSTEM disk, the files represent a new, empty configuration that TMF created
when the system was reloaded. These files need to be moved from the
configuration subvolume so the correct files can be restored.
>FUP RENAME $SYSTEM.ZTMFCONF.*, $SYSTEM.PURGEME.*
3. Restore the ZTMFCONF subvolume from the latest backup on archive media.