The following RDFCOM commands configure an updater named $UP01 to run as a process pair
in CPUs 2 and 4 at a priority of 180. The updater will be associated with an secondary image
trail on the volume $IMAGA1. The name of the backup volume and the primary volume being
protected is $DATA01.
]SET VOLUME ATINDEX 0
]SET VOLUME PROCESS $UP01
]SET VOLUME CPUS 2:4
]SET VOLUME IMAGEVOLUME $IMAGA1
]SET VOLUME PRIORITY 180
]SET VOLUME UPDATEVOLUME $DATA01
]ADD VOLUME $DATA01
The mapping between the configured updater process and a particular primary volume is
accomplished by the ADD VOLUME command.
You can issue ADD VOLUME commands only when RDF is stopped.
You must configure all updaters to use secondary image trails, thereby leaving the RDFVOLUME
(master image trail) exclusively for use by the master receiver (at index 0).
Creating a Configuration Command File
You can use the INFO * command with the OBEYFORM attribute to create a configuration
command file quickly and easily from an existing RDF configuration:
1.
Redirect the output of the RDFCOM session from your terminal to the configuration
command file by issuing an appropriate OUT command. For example, to direct subsequent
session output to the configuration command file named RDF.INIT, enter the following
command:
]OUT RDF.INIT
2.
Issue an INFO * command with the OBEYFORM attribute:
]INFO *,OBEYFORM
RDFCOM lists the current attributes in the RDF configuration file to RDF.INIT in OBEY
command file format.
3.
Issue another OUT command to redirect subsequent session output back to your terminal:
]OUT
For further information about configuration command files, see the example file in
Appendix B
(page 359)
.
Configuration File Compatibility
Before running certain commands, RDFCOM compares its own version against the version of
the RDF configuration file to ensure that the configuration file is compatible with the current
version of the RDF software. If RDFCOM detects a difference, it prints the following message to
the home terminal and aborts the command:
RDFCOM version (version1) does not match the config file version (version2)
If that happens, you should make sure you are using the correct RDFCOM. If you are using the
correct version and you get this message, then you must reinitialize RDF.
If RDFCOM cannot determine the configuration file version, it prints the following message to
the home terminal and aborts the command:
RDFCOM version (version) does not match the config file version unknown
If that happens, you should make sure you are using the correct RDFCOM. If you are using the
correct version and you get this message, then you must reinitialize RDF.
96
Installing and Configuring RDF
Summary of Contents for NonStop RDF
Page 68: ...68 ...
Page 186: ...186 ...
Page 260: ...260 ...
Page 278: ...278 ...
Page 284: ...284 ...
Page 290: ...290 ...
Page 308: ...308 ...
Page 322: ...322 ...
Page 336: ...336 ...
Page 348: ...348 ...
Page 464: ...464 ...
Page 478: ......