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

Installing and Configuring RDF
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
3-23
Configuring RDF
unique valid process name up to 5 characters, including the $ symbol. However, you
cannot specify HP reserved process names that are of the form $X*, $Y*, or $Z*, in
which * is any alphanumeric string.
The RDFVOLUME parameter applies only to the master receiver. It specifies which
volume on the backup system will contain the receiver’s master image trail. The file
naming convention for image trail files is $volume.control-subvolume.AAnnnnnn,
where n is a digit. For example, the first image file is named $volume.control-
subvolume.AA000001. You cannot specify the subvolume name because that name
is controlled by RDF.
The SLOWMODE option value controls the frequency with which the receiver updates
its context records. With SLOWMODE on, the receiver updates its context records
after processing each extractor message buffer; this enables the updaters to have the
lowest possible RTD value at all times. The SLOWMODE option is intended for use
when customers have implemented their own pseudo-lockstepping environments. The
default is SLOWMODE off. For a complete discussion of SLOWMODE, see the
description of the SET RECEIVER command in section 8.
To configure an RDF receiver process named $RECV to run as a process pair in CPUs
0 and 2 of the backup system at a priority of 185 with SLOWMODE off, and to have the
RDF image trail file (with a primary extent size of 3000 pages and a secondary extent
size of 3000 pages) reside on the volume $IMAGE, issue the following commands:
]SET RECEIVER PROCESS $RECV
]SET RECEIVER CPUS 0:2
]SET RECEIVER PRIORITY 185
]SET RECEIVER RDFVOLUME $IMAGE
]SET RECEIVER EXTENTS (3000,3000)
]SET RECEIVER ATINDEX 0
]ADD RECEIVER
You cannot start RDF until you have configured a master receiver process.
You can issue ADD RECEIVER commands only when RDF is stopped.
Image Trails
As noted earlier, the RECEIVER RDFVOLUME option value specifies the disk volume
that contains the receiver’s master image trail. The receiver process writes all
commit/abort records to this volume. All updaters must be configured to secondary
image trails.
To create secondary image trails, use the ADD IMAGETRAIL command. Later, when
you configure your individual updater processes, you assign each of these processes
to a specific image trail. By spreading updaters across secondary image trails, you
reduce the number of updaters contending for a specific trail. ATINDEX specifies which
receiver will write to that trail; 0 is the default.