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

Introducing RDF
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
1-30
Triple Contingency
•
$IMAGE.<control-subvolume>.ZRDFNMTX (master image trail only)
•
$IMAGE.<control-subvolume>.ZRDFNMT2 (master image trail only)
•
$IMAGE.<control-subvolume>.ZRDFNMT3 (master image trail only)
Triple Contingency
If you are replicating your database to multiple backup systems, you can perform an
RDF takeover to any of the backup systems upon loss of the primary system and
continue application processing on the new system within minutes. To proceed with full
RDF protection, however, you must:
1. Initiate a takeover on two of the backup systems.
2. Synchronize the two databases.
3. Configure the two systems as a primary-backup pair.
4. Initialize and start RDF on the system that you want to be the new primary system.
Depending upon the size of your database, the second step listed, database
synchronization, could take days to accomplish without the RDF triple contingency
feature. Triple contingency, however, streamlines this step, enabling you to achieve
rapid database synchronization after a takeover operation. Triple contingency allows
your applications to resume, with full RDF protection, within minutes after the loss of
your primary system, provided that the two systems are not too far behind.
The triple contingency feature builds upon the ability to replicate to multiple backup
systems. To use this feature, you establish two essentially identical RDF
configurations, as follows:
RDF Configuration #1
\A ---------> \B
RDF Configuration #2
\A ---------> \C
With both RDF configurations in operation, your data is replicated to the two backup
systems (\B and \C). Because the two configurations operate independently of one
another, if the primary system fails, it is unlikely that the databases on the two backup
systems will be logically identical to each other after RDF takeover operations. The
extractor in one RDF configuration may have just read and sent new audit to its backup
system, but the primary system might have failed before the other extractor could send
the same audit to its backup system. To bring the two backup databases into rapid
synchronization, you must perform the following steps:
1. Check the EMS event log on both remote systems after the takeover operations
have finished, and exam each 735 event. This event lists the MAT position of the
last record received by the receiver from its extractor. By comparing this message
in each EMS event log, you can easily identify which backup system received the
most audit.