RDF System Management Manual

Entering RDFCOM Commands
HP NonStop RDF System Management Manual—524388-003
8-75
Command Overview
RDFVOLUME $volume
specifies which disk volume on the backup system is to be used for the receiver’s
master image trail (the image trail to which the receiver writes all commit/abort
records). The default is $SYSTEM.
Note that this attribute applies only to the master receiver (the receiver process
configured with an ATINDEX value of 0). It is ignored for auxiliary receivers.
For best performance, do not use $SYSTEM as the RDFVOLUME.
If the backup system will run with updating disabled, be sure to specify an
RDFVOLUME disk that has an adequate amount of available space.
If the RDFVOLUME disk becomes filled, the receiver process will receive error
43 messages (Unable to obtain disk space for extent) from the file system until the
situation is corrected.
PRIORITY priority
identifies the execution priority for the receiver process; priority is the execution
priority, from 10 through 199. The default is 165.
PROCESS process-name
specifies the process name for the receiver process; process-name is any
unique, valid process name of up to 5 characters; the first character must be a
dollar sign ($). You cannot specify any of the reserved process names listed in
Appendix B of the Guardian Procedure Calls Reference Manual. Names longer
than 5 characters, including the $ sign, are invalid.
This parameter is not optional. You must explicitly name the receiver process.
SLOWMODE {ON | OFF}
During normal processing, the updaters’ RTD values are typically 4 to 20 seconds
behind the extractor’s RTD value. This is expected and normal behavior, although
it does not necessarily mean that the updaters are in fact running 4 to 20 seconds
behind the extractor. The updaters cannot read past what the receiver deems
safe, and that is determined by the frequency with which the receiver updates its
context records. The receiver normally updates its context records every 5 to 15
seconds, and the updaters’ RTD values reflect that interval.
Some customers would prefer the updaters to have the lowest possible RTD value
at all times. This can be accomplished by setting SLOWMODE ON.
With SLOWMODE ON, the receiver updates its context records after processing
each extractor message buffer. This enables the updaters to read and apply
image records much faster. It also, however, slows the extractor-to-receiver
throughput rate. You should only specify SLOWMODE ON if your throughput rate
is typically low to moderate. In environments with high extractor-to-receiver
throughput, specifying SLOWMODE ON will cause the extractor to fall behind TMF
audit generation.