RDF/IMP and IMPX System Management Manual (RDF 1.3+)

Operating and Monitoring RDF
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
4-20
Displaying Current Configuration Parameters and
Operating Statistics
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 5 to
50 seconds behind TMF processing. However, this 50-second delay does not mean
that 50 seconds are needed to catch up; that operation may only a few seconds.
•
Pri specifies the priority at which each process is running.
•
Volume and Seqnce 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).
•
Rbyte Addr specifies where in the specified file the particular process is
currently reading.
•
Cpus specifies the CPUs in which each process pair is running.
•
Error lets you know if a process has experienced a critical error. If the column is
blank, no error has occurred. If the column contains asterisks (*****), the process
has experienced a critical error. The occurrence of a critical error could mean that
the backup database is no longer synchronized with the primary database because of
data loss. If asterisks appear in the Error column for any RDF process, you should
examine the messages in the RDF log file or on the RDF log device to determine
what is happening and what corrective action to take.
Asterisks in the Error column continue to appear in every STATUS RDF display
until the error condition has been corrected.
The asterisks will also disappear when updating is restarted after execution of any of
the following commands:
Note. RTD times are approximations. They are not necessarily precise..