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

11 Subvolume-Level and File-Level Replication
By default, RDF provides volume-level protection, wherein changes to all audited files and tables
on each protected primary system data volume are replicated to an associated backup system
data volume.
RDF/IMP, IMPX, and ZLT also support subvolume-level and file-level replication. To use this capability,
you supply INCLUDE and EXCLUDE clauses when configuring updaters to identify specific
subvolumes and files you want either replicated or not replicated.
The ALTER command supports only INCLUDE/EXCLUDE of files and does not support
INCLUDEPURGE or EXCLUDEPURGE. Wild cards in file names and subvolume names are not
supported with this command.
NOTE: The RDF administrator must ensure that the data of the files included or excluded must be
consistent. The ALTER command will neither ensure data consistency of files being included or
excluded nor it will report or correct any data inconsistency that the execution of the ALTER
command. In an emergency, if RDF initialization is not possible, HP recommends that you use the
ALTER command to modify the INCLUDE/EXCLUDE clause while RDF is running. INCLUDE/EXCLUDE
and INCLUDEPURGE/EXCLUDEPURGE are performed best during RDF Initialization.
RDF/IMP, IMPX, and ZLT also enable you to choose what Enscribe files you want purged. For RDF
to replicate Enscribe purger operations, you must configure the global RDF REPLCATEPURGE to
ON. By itself, this means that RDF replicates all Enscribe purge operations. If you want to choose
what purge operations to replicate, you can use INCLUDEPURGE and EXCLUDEPURGE clauses
when you configure the updaters. To use INCLUDEPURGE and EXCLUDEPURGE, the RDF
REPLICATEPURGE attribute must also be set to ON.
NOTE: This chapter specifically addresses the including and excluding of Enscribe and NonStop
SQL/MP database objects. The same principles, however, also apply to NonStop SQL/MX database
objects. INCLUDE and EXCLUDE clauses require the use of Guardian names. If you have an
ANSI-named NonStop SQL/MX object that you want to include or exclude, you must first obtain
the underlying Guardian name by using the MXGNAMES utility or the MXCI SHOWDDL command
as described in Chapter 16 (page 316).
INCLUDE Clauses
INCLUDE clauses explicitly designate those subvolumes, files, and tables residing on a particular
primary system data volume to be replicated. Changes to all other audited files and tables on the
particular volume are ignored.
In this example, only changes to the audited files MYSUBVOL.MYFILE, MMTEST10.FILE1, and
MMTEST10.FILE2 on $DATA01 are replicated:
SET VOLUME CPUS 1:2
SET VOLUME IMAGEVOLUME $IMAGE
SET VOLUME PRIORITY 185
SET VOLUME PROCESS $MM01
SET VOLUME UPDATEVOLUME $DATA01
SET VOLUME INCLUDE MYSUBVOL.MYFILE
SET VOLUME INCLUDE MMTEST10.FILE1
SET VOLUME INCLUDE MMTEST10.FILE2
ADD VOLUME $DATA01
EXCLUDE Clauses
EXCLUDE clauses explicitly designate those subvolumes, files, and tables residing on a particular
primary system data volume that you do not want replicated. All other audited files and tables on
the particular volume are replicated.
INCLUDE Clauses 271