RDF System Management Manual

Installing and Configuring RDF
HP NonStop RDF System Management Manual—524388-003
3-26
Configuring RDF
OWNER Parameter
The OWNER parameter specifies a userid under which all RDF processes will always
run. This global configuration parameter provides functionality whereby any super-
user group userid can start and stop RDF.
To illustrate this functionality, imagine ten users are responsible for managing a
particular RDF configuration and that SUPER.RDF is configured as the OWNER.
Instead of providing all ten users access to the SUPER.RDF userid, each individual
user can be assigned a separate super-user group userid. If one user is assigned
SUPER.FIRST and another SUPER.SECOND, for example, they can both log on with
their userid and be able to start or stop RDF. The RDF processes do not run under
SUPER.FIRST or SUPER.SECOND, however, but under SUPER.RDF (the RDF
OWNER assigned during configuration). The same principal applies to the other eight
users.
The userid associated with OWNER must be a valid Guardian userid and must identify
an existing user account on the RDF primary and backup systems. The OWNER must
also be a member of the super-user group, since that is an existing requirement in
RDF for stopping and starting RDF.
OWNER is an unalterable value. There is no need to change the value, unless you
configured it incorrectly (in which case you must reinitialize RDF with the correct
value).
If the OWNER parameter is omitted, only the userid that initializes RDF can start or
stop RDF (as is true for all versions of RDF prior to 1.7).
Setting Image Trail Parameters
Use SET IMAGETRAIL and ADD IMAGETRAIL commands to configure the following
image trail parameter:
•
ATINDEX
The ATINDEX parameter associates an image trail with a specific audit trail on the
primary system.
The RECEIVER RDFVOLUME parameter specifies the disk volume that contains the
receiver’s master image trail. The receiver process writes all commit/abort records to
this volume. All updaters must be configured to secondary image trails.
To create secondary image trails, use the ADD IMAGETRAIL command. Later, when
you configure your individual updater processes, you assign each of these processes
to a specific image trail. By spreading updaters across secondary image trails, you
reduce the number of updaters contending for a specific trail. ATINDEX specifies which
receiver will write to that trail; 0 is the default.