RDF/IMP and IMPX System Management Manual (RDF 1.4+)

Managing RDF
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
5-16
Reciprocal Configurations
At this point, the RDF subsystem is stopped, the business applications from
system \A are running on system \B, and all audit information is being queued in
TMF audit trails on system \B.
5. When system \A is ready to resume its normal operations, restart TMF on \A.
6. On system \B, issue an INITIALIZE RDF command using the INITTIME option and
specifying the local system time you noted in step 3.
This action initializes the RDF extractor on \B so that it cannot miss any relevant
audit information.
7. On system \B, configure the RDF subsystem to run from \B to \A.
8. On system \B, start the RDF subsystem. The RDF subsystem begins replicating
database changes from \B to \A.
When the extractor on \B starts sending current audit information to \A (and at a
convenient time with respect to your processing environment), stop the applications on
\B and carry out a planned switchover from \B to \A.
The planned switchover repeats the procedure described above, except that you
reverse the roles of systems \A and \B. After doing so, RDF replication once again
occurs from \A to \B.
Reciprocal Configurations
In a reciprocal RDF configuration, two systems act both as a primary and as the
backup to the other.
With reciprocal configurations it is imperative that you use INCLUDE and EXCLUDE
lists specifying which database files each configuration will (and will not) protect. See
Reciprocal and Chain Replication in section 1 for more detailed information about this.
System \A System \B
Backup
Primary
Backup
Primary
RDF Subsystem #1 RDF Subsystem #1
RDF Subsystem #2RDF Subsystem #2
Applications #1
Applications #2