TMF Operations and Recovery Guide (G06.26+)

Recovery Methods
HP NonStop TMF Operations and Recovery Guide—522417-003
7-29
Responding to a TMF Crash
6. If you altered the TMF PROCESS configuration in Step 5 for any of the TMFMON,
TMFMON2, or TMP processes, issue another STOP TMF, ABRUPT command.
7. Issue the START TMF command.
8. Redo any changes you made to TMF DUMPS or TAPEMEDIA, and reenter any
ALTER AUDITTRAIL, AUDITDUMP OFF commands issued after the last backup of
ZTMFCONF.
9. Use the ADD DUMPS command to replace online dump and audit dump
information from dumps made after the most recent backup of ZTMFCONF; use
output from an INFO DUMPS, OBEYFORM command, as described previously in
Keeping Current System Information on page 2-30.
10. Back up the ZTMFCONF subvolume.
11. Issue the INFO DUMPS, OBEYFORM command to obtain a command file
containing ADD DUMPS commands for re-creating the current TMF catalog.
Responding to a TMF Crash
A TMF crash occurs in any of the following conditions:
•
The STOP TMF, ABRUPT command is issued.
•
Both TMP processes abend due to an internal error.
•
Both processors controlling the TMP fail.
A TMF crash may occur in these conditions:
•
Both processors controlling the disk process for an audit-trail volume fail.
•
An audit-trail volume suffers a hardware or media failure and stops.
A TMF crash causes TMF to stop functioning. All transaction activity in the system
ceases. Any transactions active at the time of the crash are aborted when the system
restarts. TMF enters the stopped state as soon as the TMP can restart.
Unless the TMF crash was due to a STOP TMF, ABRUPT command, you should
evaluate the cause and eliminate it. Left uncorrected, the problem may recur,
lengthening the current outage or causing a future outage. Examine the EMS
messages generated by TMF: they should indicate that a TMF crash occurred, and list
the primary reason for it.