RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

• EXCLUDEPURGE
• INCLUDEPURGE
You must configure an updater process for each primary system volume to be protected by RDF.
The ATINDEX attribute specifies an integer value from 0 through 15 specifying the audit trail on
the primary system to which the data volume being protected is mapped. 0 specifies the MAT. 1
through 15 specifies auxiliary audit trails AUX01 through AUX15, respectively. The default is 0.
The CPUS attribute specifies the processors in the backup system in which the updater will run.
The PRIORITY attribute specifies the priority at which the updater will run. You should set the
updater’s priority higher than that of any application’s process but less than the priority of the RDF
receiver process.
The PROCESS attribute supplies a name for the updater process. You should specify a meaningful
mnemonic such as $UP01. The process name can be any unique valid process name up to
six characters, including the $ symbol. However, you cannot specify HP reserved process names
that are of the form $X*, $Y*, or $Z*, in which * is any alphanumeric string.
The IMAGEVOLUME attribute associates this updater process with a specific image trail you have
previously added to the RDF configuration. You cannot add this updater process, associating it to
an image volume, unless you have already added the image trail with the ADD IMAGETRAIL
command. Also, the ATINDEX of this updater must match the ATINDEX of the associated image
trail.
The UPDATEVOLUME attribute specifies the name of the disk volume on the backup system that
corresponds to a particular volume on the primary system. This attribute enables you to use different
volume names on the backup system than are being used on the primary system, if you so desire.
The following guidelines are strongly recommended:
• There should be an identical one-to-one volume relationship between volumes on the primary
system and those on the backup system.
• Each backup volume should have the same name as the associated primary volume.
If the backup volume names are not identical to the corresponding primary volume names, then
you will have to update every partitioned file and every file that has alternate keys on the backup
system so that each points to the correct volume name.
You can use INCLUDE and EXCLUDE lists to specify which files are to be, or are not to be, protected
by RDF. For a description of INCLUDE and EXCLUDE lists, see Chapter 11 (page 266).
If you want Enscribe purge operations replicated, but you want to be selective and have some
purges replicated and others not, then you use INCLUDEPURGE and EXCLUDEPURGE to specify
what purges you want replicated. Please note that you must also have the RDF REPLICATEPURGE
attribute set to ON. For more details, see Chapter 11 (page 266).
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.
88 Installing and Configuring RDF