RDF System Management Manual

Installing and Configuring RDF
HP NonStop RDF System Management Manual—524388-003
3-27
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:
]SET IMAGETRAIL ATINDEX 0
]ADD IMAGETRAIL $IMAGA1
]SET IMAGETRAIL ATINDEX 1
]ADD IMAGETRAIL $IMAGA2
Setting Trigger Parameters
Use SET TRIGGER and ADD TRIGGER commands to configure the following trigger
parameters:
•
PROGRAM
•
INFILE
•
OUTFILE
•
CPUS
•
PRIORITY
•
WAIT or NOWAIT
The PROGRAM parameter specifies the name of a Guardian object file that is
executed once RDF has reached a particular state, either after a STOP RDF,
REVERSE, or TAKEOVER operation.
The INFILE parameter specifies the name of an edit file that will be passed as the IN
file to the trigger process when it is created.
The OUTFILE parameter specifies the name of a file or process that will be passed as
the OUT file to the trigger process when it is created.
The CPUS parameter specifies the number of the primary and alternate CPUs in which
the trigger process is to run.
The PRIORITY parameter specifies the priority at which the trigger process will run.
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.