RDF System Management Manual for H-Series RVUs (RDF 1.8)

3. To proceed with the takeover operation, enter Y or YES.
To abort the takeover operation, enter N or NO.
After you enter your response, RDFCOM returns its prompt. Then you can use the STATUS
RDF command to determine the status of the takeover operation. If the takeover operation
is still in progress, RDF displays the current state as “TAKEOVER IN PROGRESS.”
When the takeover operation finishes, RDF displays a message such as the following in
response to the STATUS RDF command:
STATUS RDF (\RDF04 -> \RDF06) is NOT running
An RDF TAKEOVER has completed
Safe MAT position is SNO 1, RBA 87876660
MAT position for File Recovery: SNO 1, RBA 87876740
By using the TAKEOVER ! version of the TAKEOVER command you eliminate the warning
prompt and response.
For super fast takeover, see “Tips for Executing Fast Business Takeover Operations” (page 39).
Monitoring Takeover Outcome
You can monitor the status of RDF takeovers by issuing a STATUS RDF command on the backup
system or by examining the events in the EMS log.
When all of the updater processes have stopped, the purger logs either a message 724 or 725 and
then stops. Message 724 indicates that the takeover completed successfully. Message 725 indicates
that it did not, and you should reissue the TAKEOVER command. A message 724 is always
followed by a message 735, which indicates the last MAT position seen by the receiver process.
The 735 event is used primarily for triple contingency. These events will be followed by either
an 888 or 858 event. See “Takeover and File Recovery” for more information.
For RDF network takeover considerations, see Chapter 14 (page 275).
For super fast takeover, see “Tips for Executing Fast Business Takeover Operations” (page 39).
Takeover Failure
If a double CPU failure occurs and the receiver process pair or an updater process pair fails
during a takeover operation, you can resume the operation just by entering the TAKEOVER
command through RDFCOM again. You can ascertain that a takeover operation failed by issuing
a STATUS RDF command and getting a response such as the following:
STATUS RDF (\RDF04 -> \RDF05) is NOT running
A partial RDF TAKEOVER has completed
Also, a takeover failure generates a 725 event in the EMS log.
Monitor Considerations
Whether the RDF monitor was started when the initial TAKEOVER command was executed or
not, this process is always started when the TAKEOVER command is reissued.
Updater Considerations
When the purger shuts down at the end of the takeover operation, it examines the context record
of each updater process to determine if that updater has processed all applicable audit data
through the end-of-file in the image trail. If all updaters have processed through the end-of-file,
the purger logs a 724 message to the EMS event log, indicating that the takeover operation
completed successfully. But if it determines that one or more updaters have terminated
prematurely, the purger logs RDF Message 726 for each updater that failed and then logs RDF
Message 725, a general message indicating that the takeover operation did not complete
successfully. If these messages appear in the EMS event log, you must reissue the TAKEOVER
command.
Takeover Operations 137