RDF System Management Manual

Entering RDFCOM Commands
HP NonStop RDF System Management Manual—524388-003
8-10
Command Overview
[VOLUME] $volume
applies configuration parameters for an updater process, implicitly identifying the
updater process by the name of the volume on the primary system for which this
process is responsible. The updater volume must be audited by TMF.
TRIGGER trigger-type
applies configuration parameters for a trigger entity. trigger-type is either
REVERSE or TAKEOVER.
Where Issued
Primary system only.
Security Restrictions
You can issue the ADD command if you are a member of the super-user group.
RDF State Requirement
Except for the ADD VOLUME and ADD TRIGGER commands, you can issue any ADD
command only after initializing RDF but before entering the first START RDF
command. After RDF is initialized, you can issue an ADD VOLUME or ADD TRIGGER
command anytime RDF is stopped.
Usage Guidelines
With the ADD command, all configuration parameter settings that you previously
supplied in SET commands for the particular process or other object are applied from
the RDF memory table to the RDF configuration file. Any parameter settings that you
did not supply are set to their default values.
Each volume on the primary system protected by RDF requires a corresponding
updater process on the backup system. You must issue one ADD VOLUME command
for every primary system volume to be protected by RDF.
Although more than one primary volume can be protected by a single disk volume on
the backup system, HP strongly recommends that you configure your environment so
that each updater process writes to its own volume (that is, that there is a one-to-one
mapping of primary volumes to backup volumes).
If you add an updater process after you stop RDF, the context record of the new
updater process is set to that of the receiver’s context for particular image trail of the
updater. So, after the next START RDF command, the newly added updater process