RDF System Management Manual

Managing RDF
HP NonStop RDF System Management Manual—524388-003
5-16
Stopping RDF From the Primary System
•
Issue STATUS RDF commands and wait until all of the RDF Time Delay (RTD)
times are zero.
•
Issue the STOP RDF command.
(For an alternate method of bringing the backup database to a consistent state, see
Access to Backup Databases in a Consistent State later in this section.)
When you issue a STOP RDF command from the primary system, the following events
occur:
1. RDFCOM sends a STOP message to the monitor.
2. The monitor sends stop messages to the extractor(s), the receiver(s), the purger,
the updater(s), and, if there is an RDF network, the RDFNET process.
3. The monitor stops after all RDF processes have stopped.
If the communications lines between the two systems are down when you issue the
STOP RDF command, the monitor tells the extractor to stop and writes an error
message for every process running on the backup system that the monitor could not
access; the monitor then stops itself. If this situation occurs, you must use RDFCOM
on the backup system to stop the remaining RDF processes before you can restart
RDF.
STOP RDF, DRAIN Operations
A STOP RDF, DRAIN command causes the following actions to occur:
•
All TMF audit records up to the time the command is entered, are replicated to the
image trails on the backup node.
•
Each updater shuts down after it has applied all audit records up to the stop point.
•
The purger process reports event 852, indicating all updaters have stopped and
the drain has completed.
Note. Even when no TMF transactions are in progress, TMF periodically writes control points
to the MAT, which means that the MAT continues to fill even when no application activity is
occurring. This can cause RTD times in the status display to fluctuate.