TMF Operations and Recovery Guide (G06.26+)

Recovery Methods
HP NonStop TMF Operations and Recovery Guide—522417-003
7-17
Performing File Recovery
than one renaming pattern in this option and there is a conflict, TMF uses the first
applicable pattern. Within the context of MAP NAMES, the following syntax
restrictions apply:
Wild-card Characters in old-fileset-list
In old-fileset-list, you can use wild-card characters in the volume,
subvolume, file ID fields as follows:
* An asterisk matches from 0 through 8 letters, digits, or a combination of
these, in the position where it appears.
? A question mark matches exactly one letter or digit, in the position where it
appears.
Wild-card Characters in new-fileset
In new-fileset, you cannot use the question mark as a wild-card character.
However, you can use the asterisk in this way:
* An asterisk can be used in place of a volume name, subvolume name, or
file ID. The asterisk indicates “all.” For example, $data1.*.filea refers
to all files named filea on the volume named $data1. Using a wild-card in
partial names, such as $data1.sub*.filea, is not allowed.
You can cancel a RECOVER FILES operation by using the CANCEL OPERATIONS
command. For more information on using the CANCEL OPERATIONS command,
refer to the TMF Reference Manual. Also see the TMF Reference Manual for complete
syntax rules and instructions for using the RECOVER FILES command.
Performing File Recovery
To recover files by using the TMF file recovery process, follow these steps:
1. Make sure TMF is started.
Transaction processing can be enabled, but files that need file recovery cannot be
accessed. Transactions involving undamaged or recovered audited files can be
processed while the damaged files are being recovered. It might be advisable,
however, to restrict transaction processing until all files have been recovered.
2. Determine which files to recover.
You can use a FUP INFO command or a DSAP command to identify the files
marked for file recovery. These files are marked redo-needed or undo-needed.
You determine which files to recover based on the type of failure that occurred.
You do not have to recover your entire database at one time. Sometimes it is
better to recover only those audited files crucial to an application that must be
online as soon as possible; later, you can recover the rest of the database. For
example, if you have an online order-entry system and an electronic mail system,
you can choose to recover the order entry system first, and recover the electronic
mail system later.