TMF Reference Manual (G06.24+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-002
3-212
RECOVER FILES
Because the MAP NAMES option restores files only to the same instance of TMF, you
cannot use this option to restore these files to another system.
When you use the MAP NAMES option, the files in the new locations have the same
user IDs and attributes as those in the old locations.
When you use the MAP NAMES option, the FROMARCHIVE option is also used in all
cases, even if you do not explicitly select it. For recovery to a new location, Enscribe
files are purged and restored before recovery is started. However, you should create
SQL objects before recovery is started to keep the catalog consistent.
The MAP NAMES option does not correct interdependencies between files. It does not
add SQL objects into a SQL catalog; instead, you must manually add the new tables to
the SQL catalog you wish. File partitions are treated as distinct files; thus, recovered
file partitions must be manually updated to reflect any changes.
Options for the SMF Product
The TOPHYSVOL and WHEREPHYSVOLIS parameters allow you to refer to physical
disk volumes managed by the NonStop Storage Management Foundation (SMF)
product. The 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,
Note. If you specify the MAP NAMES option, you cannot use the RECOVERVDPPHASE1
option.
Caution. 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.