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

Installing and Configuring RDF
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
3-27
Configuring RDF
You cannot start RDF until you have configured a purger process.
You can issue ADD PURGER commands only when RDF is stopped.
Updater Processes
Use SET VOLUME and ADD VOLUME commands to configure the following updater
parameters:
•
CPUS primary-CPU : backup-CPU
•
IMAGEVOLUME
•
PRIORITY
•
PROCESS
•
UPDATEVOLUME
You must configure an updater process for each primary system volume to be protected
by RDF.
The CPUS option value specifies the processors in the backup system in which the
updater will run.
The IMAGEVOLUME option value associates this updater process with a specific
image trail you have previously added to the RDF configuration. You cannot add this
updater process, associating it to an image volume, unless you have already added the
image trail with the ADD IMAGETRAIL command.
The PRIORITY option value specifies the priority at which the updater will run. You
should set the updater’s priority higher than that of any application’s process but less
than the priority of the RDF receiver process.
The PROCESS option value, if present, supplies a name for the updater process. If you
choose to name the updater, you should specify a meaningful mnemonic such as $UP01.
The process name can be any unique valid process name up to 5 characters, including
the $ symbol. However, you cannot specify Compaq reserved process names that are of
the form $Xddd, $Yddd, or $Zaaa, in which d is any numeric character and a is any
alphanumeric character.
If you omit the PROCESS option, the operating system selects a name for the updater
process.
The UPDATEVOLUME option value specifies the name of the disk volume on the
backup system that corresponds to a particular volume on the primary system. This
parameter enables you to use different volume names on the backup system than are
being used on the primary system, if you so desire.
The following guidelines are strongly recommended:
•
There should be an identical one-to-one volume relationship between volumes on
the primary system and those on the backup system.
•
Each backup volume should have the same name as the associated primary volume.