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

Entering RDFCOM Commands
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
8-88
Command Overview
In the STATUS RDF display, the first line gives the name of the primary system
(\RDF04 in this example), the name of the backup system (\RDF05 in this example),
and the timestamp that shows when the STATUS RDF command was issued. The
second line specifies the fully-qualified name of the control subvolume. The third line
specifies the current state of the subsystem; any of the following entries are possible:
•
Normal
•
Normal - Update Stopped
•
Start Update Pending
•
Stop Update Pending
•
Stop Update, Timestamp Pending
•
* STOP RDF In Progress *
•
* TMF STOP In Progress *
•
* TAKEOVER In Progress *
•
WRONG PROGRAM VERSION
•
NSA Stop Update Pending
•
Update NSA Stopped
The rest of the display provides current information about each RDF process
configured.
For extractors, receivers, and image trails, the configured ATINDEX value is displayed
in parentheses following the object name. In the above example, the extractor $RE01
and receiver $RR01 are associated with the MAT, while the extractor $RE02 and
receiver $RR02 are associated with auxiliary audit trail AUX01.
Because of insufficient space, however, ATINDEX values could not be displayed
explicitly for updaters. To determine the ATINDEX value of a particular updater, see the
ATINDEX value of the associated secondary image trail.
In this example, a monitor process and two extractor processes are configured on the
primary system, and two receiver processes and three updater processes are
configured on the backup system. For each process, the following items appear,
indicated by column headings near the top of the display:
RDF Process
The first column of the display identifies the type of process. Notice that each updater
process is identified by the names of both the primary volume the updater process is
protecting and the corresponding volume on the backup system. In this example, each
volume being updated on the backup system has the same name as the corresponding
volume on the primary system (for example, updates to the volume $DATA07 on the
primary system are duplicated by the updater process $RU02 to the volume $DATA07
on the backup system).