TMF Operations and Recovery Guide (G06.26+)

Recovery Methods
HP NonStop TMF Operations and Recovery Guide—522417-003
7-25
Responding to Loss of Files on NonStop SMF Disk
Volumes
generated when the file recovery process encounters the file label modification record
in the master audit trail (MAT). To complete the recovery successfully, you must use
the SNOOP utility to locate the file label modification record. To do so, use the
READAUDIT command in SNOOP to scan the MAT with the select criteria specifying
the file name, the file type, and the flags 000021. Once you have located the file label
modification record in this way, you can complete the recovery through either of the
following methods:
•
Use the READAUDIT command in SNOOP to read backward from the relative byte
address of the file label modification record until you find a record that contains a
timestamp. Then, use the RECOVER FILES command with the TOTIMESTAMP
option to recover the file to that point.
•
Use the RECOVER FILES command with the TOMATPOSITION option, specifying
the location of the record just before the file label modification record. To indicate
this location, use the sequence number of the MAT in which file recovery is to stop
and the relative byte address in the MAT where file recovery is to stop, as the
TOMATPOSITION parameters.
SNOOP is best used by persons with substantial TMF expertise, and in some cases
requires assistance from the Global Customer Support Center (CGSC) or your service
provider. The SNOOP utility is provided with the TMF product, and is documented in
the file named $SYSTEM.SYSnn.SNOOPDOC.
Responding to Loss of Files on NonStop SMF Disk Volumes
As noted earlier, the NonStop SMF software enhances the automatic management of
system storage. A file stored on an SMF virtual disk is identified by a logical file name.
A file that is not associated with an SMF virtual disk process, however, is identified by a
direct file name. A file has either a logical or a direct file name, but it never has both.
Logical and direct file names are simply the external file names that applications use to
identify files either managed by the SMF product or not managed by it, respectively.
The DP2 disk process, however, does not use external file names; instead, that
process identifies a file by a physical file name, which is simply an internal file name
that maps to the file’s logical or direct file name. As an example, for a file stored on an
SMF virtual disk, the logical file name might be \$SYS.$L1.SOME.DATA and the
physical file name might be $PHYS27.ZYS00000.A0000K29. For a file that is not
managed by the SMF software, the direct file name and physical file name are both the
same (for instance, \SYS.$P1.MORE.DATA).
For systems using the SMF product, the TMF catalog contains the logical file names of
files managed by SMF and the direct file names of files not managed by SMF. Thus,
when taking dumps of these files, or referring to them in the RECOVER FILES
command, you must refer to these files by their logical or direct file names, not by their
physical file names. Nevertheless, with the TOPHYSVOL option in the RECOVER
FILES command, you can identify the physical target disk volume where you wish TMF