Where Issued; Security Restrictions; Rdf State Requirements; Usage Guidelines - HP NonStop RDF J-series RVUs Management Manual

MAPFILE $vol.subvol.fname
specifies the mapfile on the backup system that contains mapping strings that constitute the
mapping rules. The updater will apply these rules to the audit records present in the image
trail files. This parameter is optional.
MAPLOG $vol.subvol.fname
specifies the log file on the backup system into which the updater should log the source and
target filename pairs if a mapping rule is applied. This parameter is optional.

Where Issued

Primary system only.

Security Restrictions

None.

RDF State Requirements

None.

Usage Guidelines

The SET VOLUME command enters the parameter values specified for the updater in this
command into the RDF configuration table in memory. This table serves as an input buffer only,
and so these values do not affect the subsystem until they are applied to the RDF configuration
file with the ADD command.
For ATINDEX values greater than 0, the specified value must match the audit trail number of a
configured auxiliary audit trail. If you specify SET VOLUME ATINDEX 2, for example, there
must be a configured auxiliary audit trail AUX02.
Furthermore, RDF objects with a particular ATINDEX value greater than 0 must together constitute
a complete set:
• If there is an extractor with an ATINDEX value of 1, there must also be a receiver with an
ATINDEX value of 1.
• If there is a receiver with an ATINDEX value of 1, there must also be a secondary image trail
with an ATINDEX of 1.
• An updater with an ATINDEX value of 1 must be protecting a primary system data volume
configured to auxiliary audit trail AUX01, and its secondary image trail must also have an
ATINDEX value of 1.
For a discussion on the use of INCLUDE and EXCLUDE lists, see
Once an updater process has been added to the RDF configuration, you cannot alter its INCLUDE
or EXCLUDE parameters. If you must do so, it is recommended that you STOP RDF, reinitialize
RDF (with the INITTIME option), and reconfigure it with correct INCLUDE and EXCLUDE lists.
See Chapter 3 (page 69)
You can specify a maximum of 100 INCLUDE and EXCLUDE parameters for each volume, in
any combination.
Unlike the behavior of other SET parameters, successive INCLUDE or EXCLUDE parameters
do not supersede preceding ones in the RDF configuration memory table (they merely extend
the include and exclude lists for the particular data volume).
If you want to use the same INCLUDE/EXCLUDE lists for each volume, you only have to use
the SET commands when configuring the first updater. After you ADD that updater, the same
INCLUDE/EXCLUDE lists are retained in memory, and you only need to configure the other
updater attributes. When you ADD the next updater, it inherits the same INCLUDE/EXCLUDE
lists.
238 Entering RDFCOM Commands
for a discussion of how to reinitialize RDF with the INITTIME option.
Chapter 11 (page 279).