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-24
Configuring RDF
Each secondary image trail contains the audit records needed by the associated
updater processes. Image trail files in secondary image trails have the same extent
sizes as image trail files on the volume specified by RDFVOLUME.
To add one secondary image trail to the volume named $IMAGA1 and another to the
volume named $IMAGA2, issue the following commands:
]ADD IMAGETRAIL $IMAGA1
]ADD IMAGETRAIL $IMAGA2
Purger Process
Use SET PURGER and ADD PURGER commands to configure the following purger
parameters:
•
CPUS primary-CPU : backup-CPU
•
PRIORITY
•
PROCESS
•
RETAINCOUNT
•
PURGETIME
The CPUS option value specifies the processors in the backup system in which the
purger is to run.
The PRIORITY option value specifies the priority at which the purger will run. You
should set the purger’s priority higher than that of any application’s process and higher
than that of any RDF updater process.
The PROCESS option value supplies a name for the purger process. You should
specify a meaningful mnemonic such as $PURG. The process name can be any
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 RETAINCOUNT option value specifies how many of the most recent image trail
files will be retained on disk for each image trail. The default value is 2. For details
about the RETAINCOUNT parameter and triple contingency, see Section 10, Triple
Contingency.
The PURGETIME option value specifies the number of minutes the purger process
waits between attempts to purge redundant image trail files. The default value is 60.
Note. To have secondary image trails, you must add them after initialization and before RDF
has been started for the first time. Also you cannot add secondary image trails until you have
configured the receiver, as described in the previous paragraphs. The secondary image trail
files have the same extents as the master image trail files. To delete a secondary image trail,
you must stop RDF, delete any updaters associated with the particular trail, and then delete
the trail. Normally, you should never delete a secondary image trail until RDF has completely
caught up with TMF.