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-26
Configuring RDF
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 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.
If the backup volume names are not identical to the corresponding primary volume
names, then you will have to update every partitioned file and every file that has
alternate keys on the backup system so that each points to the correct volume name.
You can use INCLUDE and EXCLUDE lists to specify which files are to be, or are not
to be, protected by RDF. For a description of INCLUDE and EXCLUDE lists, see
Section 11, Subvolume- and File-Level Replication.
The following RDFCOM commands configure an updater named $UP01 to run as a
process pair in CPUs 2 and 4 at a priority of 180. The updater will be associated with
an secondary image trail on the volume $IMAGA1. The name of the backup volume
and the primary volume being protected is $DATA01.
]SET VOLUME PROCESS $UP01
]SET VOLUME CPUS 2:4
]SET VOLUME IMAGEVOLUME $IMAGA1
]SET VOLUME PRIORITY 180
]SET VOLUME UPDATEVOLUME $DATA01
]SET VOLUME ATINDEX 0
]ADD VOLUME $DATA01
Note that the mapping between the configured updater process and a particular
primary volume is accomplished by the ADD VOLUME command.
You can issue ADD VOLUME commands only when RDF is stopped.
You must configure all updaters to use secondary image trails, thereby leaving the
RDFVOLUME (master image trail) exclusively for use by the master receiver (at index
0).