RDF/IMP, IMPX, and ZLT System Management Manual

Entering RDFCOM Commands
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
8-91
Command Overview
receiver is the difference between the “last modified time” of the TMF MAT and the
timestamp that identifies the associated restart point.
The RTD value reported for each updater process is the difference between the “last
modified time” of the TMF master audit trail (MAT) and the timestamp in the most
recent image record seen by the particular updater.
The RTD value reflects, in the most general sense, the amount of time by which the
backup database is lagging behind the primary database. In the example shown under
“Output Displayed” earlier in this command description, the specified RTD time for the
updater $TU04 is 0 minutes and 10 seconds, meaning that the updater is running
approximately 10 seconds behind the MAT.
On a finely tuned RDF backup node, the RTD for an updater can regularly lag 1 to 15
seconds behind TMF processing. However, this 15-second delay does not mean that
15 seconds are needed to catch up; that operation may only a few seconds.
If RDFCOM cannot connect to a particular process, RDFCOM displays dots (...) in the
RTD Time, Sequence, and Rel Byte Addr fields and an appropriate File System error
number in the Error field.
Pri
The fourth column specifies the priority at which each process is running.
Volume and Seqnce
The fifth and sixth columns together specify a file associated with each process, as
follows:
•
The monitor entry reflects the name of the MAT file to which TMF is writing
($AUDIT.ZTMFAT.AA000056 in this example).
•
Each extractor entry reflects the name of the TMF audit trail file from which it is
reading ($AUDIT.ZTMFAT.AA000056 for the master extractor and
$DATA17.ZTMFAT.BB000004 for the auxiliary extractor in this example).
•
The receiver entries reflect the names of the primary image trail files to which each
receiver is writing ($DATA01.RDF04.AA000044 and $DATA02.RDF04.AA000003
in this example).
•
The imagetrail entries reflect the names of the secondary image trail files to which
each receiver is writing ($DATA03.RDF04.AA000022 and
$DATA04.RDF04.AA000003 in this example).
•
Each updater entry reflects the name of the secondary image file from which it is
reading ($DATA03.RDF04.AA000020 for $RU01, $DATA04.RDF04.AA000003 for
$RU02, and so forth, in this example).
If RDFCOM cannot connect to a particular process, RDFCOM displays dots (...) in the
RTD Time, Sequence, and Rel Byte Addr fields and an appropriate File System error
number in the Error field.