TMF Management Programming Manual (H06.06+, J06.03+)
Table Of Contents
- HP NonStop TMF Management Programming Manual
- Legal Notices
- Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to TMF
- 2 Communicating With the TMFSERVE Process
- 3 SPI Programming Considerations for TMF
- 4 Common Definitions
- 5 Commands and Responses
- Command Summary
- Command Descriptions
- ABORT TRANSACTION
- ADD AUDITTRAIL
- ADD DATAVOLS
- ADD DUMPS
- ADD MEDIA
- ADD RESOURCEMANAGER
- ALTER AUDITDUMP
- ALTER AUDITTRAIL
- ALTER BEGINTRANS
- ALTER CATALOG
- ALTER DATAVOLS
- ALTER DUMPS
- ALTER MEDIA
- ALTER PROCESS
- ALTER TMF
- CANCEL OPERATION
- CLOSE RESOURCEMANAGER
- DELETE CATALOG
- DELETE DATAVOLS
- DELETE DUMPS
- DELETE MEDIA
- DELETE RESOURCEMANAGER
- DELETE TMF
- DELETE TRANSACTION
- DISABLE AUDITDUMP
- DISABLE BEGINTRANS
- DISABLE DATAVOLS
- DUMP FILES
- ENABLE AUDITDUMP
- ENABLE BEGINTRANS
- ENABLE DATAVOLS
- INFO ATDUMPDM
- INFO ATVOLUME
- INFO AUDITDUMP
- INFO AUDITTRAIL
- INFO BEGINTRANS
- INFO CATALOG
- INFO DATAVOLS
- INFO DUMPS
- INFO MEDIA
- INFO PROCESS
- INFO RESOURCEMANAGER
- INFO TMF
- LIST AUDITTRAIL
- NEXT AUDITTRAIL
- RECOVER FILES
- RELOCATE DISKDUMPS
- RESOLVE TRANSACTION
- START TMF
- STATUS ATFILE
- STATUS AUDITDUMP
- STATUS AUDITTRAIL
- STATUS BEGINTRANS
- STATUS CATALOG
- STATUS DATAVOLS
- STATUS OPERATION
- STATUS RESOURCEMANAGER
- STATUS RMTRANSBRANCHES
- STATUS TMF
- STATUS TMFSERVER
- STATUS TRANSACTION
- STATUS TRANSACTIONCHILDREN
- STOP TMF
- 6 Event Messages
- 7 Error and Warning Messages
- A TMF Configuration Limits and Defaults
- Index
Commands and Responses
HP NonStop TMF Management Programming Manual—540140-010
5-142
RECOVER FILES
ZToFirstPurge
specifies at what point the recovery operation should end.
ZSPI-VAL-True
File recovery terminates when the first audit record for purging any file in
the specified file sets is encountered; the purge record is not reapplied.
ZSPI-VAL-False
File recovery does not terminate early based on a purge record.
If you omit this field, its default value is ZSPI-VAL-False.
If you include ZToFirstPurge, you must make new online dumps of the
database files recovered; this prevents subsequent file recovery from using the
unwanted audit records generated after the specified time.
ZTimeStamp
directs that file recovery redo all transactions committed before the specified
time. Transactions that began before the specified time but were not yet
committed are backed out. The database is recovered to the time specified,
rather than to the most recent consistent state. Be certain to enter the date and
time for this option completely and accurately.
If the ZFromArchive token is not specified but the ZTimeStamp value is, then
the ZFromArchive token gets a default value of TRUE.
If you include ZTimeStamp, you must make new online dumps of the database
files recovered; this prevents subsequent file recovery from using the
unwanted audit records generated after the specified time.
If you omit ZTimeStamp, the time at which you issue the RECOVER FILES
command is used for the file recovery operation.
ZSystemName
specifies the node on which all tape or disk media used for restoring online
dumps are mounted. The default is the home (local) node. If you specify a
remote node, Guardian labeled-tape processing must be enabled on that node
and must be running on release C30 or later of the NonStop OS. TMF,
however, need not be configured or running on the remote node.
Caution. When you issue a RECOVER FILES command to initiate file recovery to a
timestamp, and the time listed in the TMF catalog is not the time that the online dump actually
took place, you risk destruction of your database because you probably will not recover all the
data you need.