Copyaudit; Where Issued; Security Restrictions; Rdf State Requirement - HP NonStop RDF J-series RVUs Management Manual

The following command changes the execution priority of the auxiliary extractor process
associated with the auxiliary audit trail AUX02 to 170:
]ALTER EXTRACTOR ATINDEX 2 PRIORITY 170
To change the primary and backup CPUs for the master receiver process to CPUs 3 and 4
respectively, enter an ALTER RECEIVER CPUS command:
]ALTER RECEIVER CPUS 3:4
Remember you cannot do this particular alter operation while RDF is running.
To change the primary and alternate CPUs of a reverse trigger to CPUs 3 and 4, enter an ALTER
TRIGGER CPU command:
]ALTER TRIGGER REVERSE CPUS 3:4

COPYAUDIT

This command is only for use with the triple contingency feature.
If the primary system fails, you must execute two takeovers: one on each backup system involved
in the triple contingency protocol. Upon successful completion of both takeovers, the databases
on the two backup systems will almost assuredly not be identical: one of the extractors 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).
COPYAUDIT , REMOTESYS name , REMOTECONTROLSUBVOL subvol
REMOTESYS name
specifies the name of the backup system that has the most audit records (that was further
ahead in its RDF processing).
REMOTECONTROLSUBVOL subvol
specifies the name of the RDF control subvolume on the remote system.

Where Issued

Backup system only (the backup system that has the least amount of audit records).

Security Restrictions

You can issue the COPYAUDIT command only if you are a member of the super-user group and
have remote passwords on both systems.

RDF State Requirement

After an RDF takeover operation has completed successfully on both backup systems, you must
issue the COPYAUDIT command while RDF is stopped.

Usage Guidelines

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 the system that is behind, specifying the name of the other backup system and its
RDF control subvolume.
For the following discussion, assume that you have established these two RDF configurations:
RDF Configuration #1:
\A ------------------> \B
RDFCOM Commands 197