TMF Operations and Recovery Guide (G06.26+)

Recovery Methods
HP NonStop TMF Operations and Recovery Guide—522417-003
7-20
Retaining Audit Files Restored from Tape on
Restore-Audit Volumes
The following RECOVER FILES command uses the MAP NAMES option to recover
the file T32, originally stored on $TMF.TMF01, to $DATA.TMF01.T32:
TMF 92> RECOVER FILES $TMF.TMF01.T32, &
>>>MAP NAMES ($TMF.*.* TO $DATA1.*.*)
.
.
.
By using wild-card characters in the MAP NAMES option, you can gain great efficiency
and flexibility in specifying source files and target files. For more information about
wild-card characters and examples of their use, see TMF Reference Manual.
Retaining Audit Files Restored from Tape on
Restore-Audit Volumes
During volume recovery or file recovery, if TMF requires an audit-trail file that is no
longer available on the system but is archived on tape, TMF copies that file from an
audit dump on the tape to a restore-audit volume on disk. When the recovery process
is finished, TMF purges this file and all other unneeded files from the restore-audit
Caution. The MAP NAMES option does not correct interdependencies between files. In
particular, the following restrictions apply:
•
MAP NAMES does not add SQL objects into a SQL catalog; instead, you must manually
add the new tables to the SQL catalog you wish before you perform the recovery.
•
MAP NAMES treats file partitions as distinct files; thus, recovered file partitions must be
manually updated to reflect any changes.
•
MAP NAMES does not update file labels for alternate key files.
•
TMF does not apply SQL file-label modification records encountered in an audit trail for an
object being recovered to a new location. Thus, the file label in an online dump must
match the file label of the newly created target and the target’s file label must match the
final form of the source file label to ensure a successful recovery.
For full guidelines and restrictions on the recovery of SQL objects, see the discussion
“Recovering Files to New Volumes, Subvolumes, or File IDs” in the SQL/MP Installation and
Management Guide and the discussion “Recovering Files to New Locations” in the SQL/MX
Installation and Management Guide.
If you use the MAP NAMES option of the RECOVER FILES command to recover files to a new
location, you must immediately make new online dumps of the target data files recovered.
Without these new dumps, you will not have file-recovery protection for those files, and
subsequent file-recovery operations can fail. In particular, if you later try to use old online
dumps of the target files to recover the target files to a point beyond the time that the last
RECOVER FILES command was issued, the file-recovery process fails during the redo phase
and transmits EMS message 175:
Encountered a File Hiatus record for audit file filename at
audit trail Index #index, SNO #sno, RBA #rba.