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-18
Command Overview
unknown at the time of the original takeover. Because RDFCOM added more audit
information to the image trail, there is a chance that the outcome of some of these
transactions is now known. Therefore, RDFCOM repositions the updater’s restart
location back to the first record that it could not previously apply. (If there were no
exception records, then RDFCOM leaves the updater’s restart location unchanged.)
Finally, RDFCOM turns off the receiver’s takeover completed flag and issues a
message telling you that the COPYAUDIT operation has completed successfully and
you must initiate another takeover on \C. Issue a TAKEOVER command on \C. If the
takeover completes successfully (the receiver logs an RDF message 724 followed by a
735 message containing the same detail as in the 735 message associated with the
takeover on \B), the two databases are logically identical.
At that point you can initialize, configure, and start RDF on both systems, and then
resume application processing on the new primary system with full RDF protection.
COPYAUDIT Restartability
The COPYAUDIT command is restartable.
If an error condition aborts execution of a COPYAUDIT command, you merely correct
the condition and then reissue the command. Upon restart, RDFCOM quickly checks
the local system image files it had previously created to be sure they are still correct,
deletes the file it was working on at the time of the error condition, and then resumes
copying. Because it keeps track of where it was in the COPYAUDIT operation,
RDFCOM does not have to recopy the previously copied image files.
RDFCOM abends if it encounters network problems while searching the remote image
trails for missing audit information. If that happens, RDFCOM logs a message to the
EMS event log, but not to the home terminal.
If RDFCOM encounters network problems during any other phase of COPYAUDIT
execution, it does not abend. Instead, it logs a message to the home terminal and
aborts the COPYAUDIT command.
Example
Assume you have established two RDF configurations to provide triple contingency
protection (\A to \B and \A to \C) and that the RDF control subvolume of the \A to \B
configuration is A1 and the RDF control subvolume of the \A to \C configuration is A2.
Assume further that, after failure of the primary system (\A), you do a takeover on both
\B and \C and determine that \B was further ahead in its RDF processing.
To copy the missing audit information from \B to \C, issue the following command on
\C:
]COPYAUDIT , REMOTESYS \B, REMOTECONTROLSUBVOL A1