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

Introducing RDF
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
1-23
RDF Control Subvolume
Alternatively, you might have one RDF configuration replicate data on a set of volumes
to one backup system and another RDF configuration replicate data on a different set of
volumes to a different backup system, as follows:
RDF Configuration #1, protecting Volumes $DAT1 through DAT20
\A ---------> \B
RDF Configuration #2, protecting Volumes $DAT21 through
$DAT40
\A ---------> \C
As still another alternative, you might have one RDF configuration replicate data on a
set of volumes to a backup system and a different RDF configuration replicate data on a
different set of volumes to the same backup system as the other RDF configuration, in
this way:
RDF Configuration #1, protecting Volumes $DAT1 through DAT20
\A ---------> \B
RDF Configuration #2, protecting Volumes $DAT21 through
$DAT40
\A ---------> \B
In the preceding examples, each RDF configuration operates entirely independently of
the other RDF configuration primaried on the same node; that is, each RDF
configuration has its own extractor and monitor process. In this way, line failures
affecting one configuration may not necessarily affect the others (depending on the
configuration).
RDF Control Subvolume
The INITIALIZE RDF command includes a control subvolume suffix parameter
(SUFFIX char ), where char is an alphanumeric character. If you include this
parameter, the RDF control subvolume on $SYSTEM will be the local (primary) system
name without the backslash and with the specified character appended to it. If you omit
this parameter, the RDF control subvolume on $SYSTEM will merely be the local
system name without the backslash.
If you want to have several RDF configurations with the same primary system, each
configuration must have its own control subvolume and you must use the SUFFIX char
parameter. Thus, if the name of your primary system is \BOSTON and you assign the
suffix “1”, the control subvolume will be named BOSTON1. If you have two RDF
configurations primaried on \BOSTON, you could initialize one RDF configuration with
the suffix “1” and the other with the suffix “2” so that their control subvolumes would be
named, respectively, “BOSTON1” and “BOSTON2”.
The control subvolume on the primary system contains the following files:
•
$SYSTEM.<control-subvolume>.CONTEXT
•
$SYSTEM.<control-subvolume>.CONFIG
•
$SYSTEM.<control-subvolume>.RDFLOCK