RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

where num is once again within the range 2 through 5000. (Before entering this command,
however, you must first stop RDF.)
The COPYAUDIT Command
If the primary system fails, you must execute two takeovers: one on each backup system. Upon
successful completion of both takeovers (signalled by a 724 message in the EMS event log of each
backup system), the databases on the two backup systems will almost assuredly be different: one
of the systems will have been further ahead of the other in its RDF processing when the failure
occurred.
The COPYAUDIT command copies missing audit records from the backup system that was further
ahead in its RDF processing (had the most amount of audit data) to the system that was further
behind (had the least amount of audit data).
Upon successful completion of the two takeovers, examine the EMS event log on both backup
systems for a 735 message. That message, which follows the 724 message in the log, specifies
the last position in the MAT that was seen by the receiver process. Compare the MAT positions in
the two 735 messages and determine which of the two systems was further behind in its RDF
processing when the failure occurred (that is, which system had received the least amount of audit
data from the extractor by the time the primary system was lost). Then issue a COPYAUDIT command
on that system, specifying the name of the other backup system and its RDF control subvolume.
The syntax of the COPYAUDIT command is:
COPYAUDIT, REMOTESYS sys, REMOTECONTROLSUBVOL subvol
where sys is the name of the other system (the backup system that has the most amount of audit
records) and subvol is the name of the RDF control subvolume on that system.
For this discussion, assume that you have established two RDF configurations:
RDF Configuration #1:
\A ------------------> \B
(The RDF control subvolume is A1 on both systems.)
RDF Configuration #2:
\A ------------------> \C
(The RDF control subvolume is A2 on both systems.)
Assume you have lost the original primary system (\A), you have successfully completed a takeover
on both backup systems (\B and \C), and the MAT positions displayed by the respective 735
messages are:
\B: 735 LAST MAT POSITION: Sno 10, RBA 100500000
\C: 735 LAST MAT POSITION: Sno 10, RBA 100000000
500 kilobytes of audit records is missing on \C.
Because \C has the least amount of audit records, you must issue this command on \C:
COPYAUDIT, REMOTESYS \B, REMOTECONTROLSUBVOL A1
For each image trail, RDFCOM on \C reads its own context file to determine the MAT position of
the last audit record in the trail. RDFCOM then searches the corresponding trail on \B to find that
audit record and performs large block transfers to move all audit records beyond that point to the
trail on \C. As it does this, RDFCOM issues messages to let you know which image trail it is
currently processing.
NOTE: When it begins copying missing audit records from one system to the other, RDFCOM
never alters any of the existing image trail files on the local system. Instead, it creates a brand new
image file on the local system even if the starting point of the missing audit records on the other
system is in a file with a different sequence number. This means that, upon completion of the
COPYAUDIT operation, the local system will almost always have more image trail files (one or two
per image trail) than the other system. This is expected behavior.
The COPYAUDIT Command 263