RDF/IMP, IMPX, and ZLT System Management Manual

Installing and Configuring RDF
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
3-31
Starting RDF
ENABLE BEGINTRANS. For details about these TMFCOM commands, see the HP
NonStop Transaction Management Facility (TMF) Reference Manual.
Starting RDF
There are two ways to start RDF: with updating enabled and with updating disabled. If
updating is enabled, the updaters begin updating the backup database immediately. If
updating is disabled, they do not (but the extractor and receiver continue to work
normally). The default is to start RDF with updating enabled.
To start RDF, issue the RDFCOM command START RDF, as follows:
]START RDF
Notice that to issue this command, you must have an RDFCOM session running on the
primary system and meet all of the following requirements:
•
Be logged on as a member of the super-user group
•
Have the same super ID that was used to initialize RDF
•
Have remote passwords on both the primary and backup systems
•
Ensure that the RDF configuration file contains all necessary parameters
•
Ensure that all updater volumes on the backup system are enabled for transaction
processing
When RDF starts execution, it automatically performs a validation check on the
configuration file; if the check succeeds, RDF copies the configuration file
$SYSTEM.control-subvolume.CONFIG to the backup system.
If the RDF configuration file does not exist, or if there are any missing or invalid
parameters, RDFCOM displays an error message and aborts the start operation.
If you did not start TMF on the backup system, or if you did not add an updater volume
to the TMF configuration on the backup system and enable it for transaction
processing, the corresponding updater logs an RDF error and terminates immediately.
If you started TMF on the backup system and added the updater volume to the TMF
configuration but did not enable that volume for transaction processing, the updater
issues an error message and then stops.
If TMF BEGINTRANS is disabled, RDF issues an error message.
Unless you explicitly specify otherwise, RDF always starts with updating enabled: all
updater processes immediately begin updating their volumes by reading audit images
from the RDF image files and applying the appropriate changes to the backup
database files.