RDF/IMP, IMPX, and ZLT System Management Manual

HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual524388-002
11-1
11
Subvolume- 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- 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.
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 the following 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
Note. All NonStop SQL/MP shared-access DDL operations involve two files – a source file
and a target file. If you are using INCLUDE and EXCLUDE lists to define your RDF
configuration and you plan to execute any such operations on data volumes protected by the
RDF subsystem, you must be certain to define both the source and target files as protected
files; if either the source or target file is not replicated, the updaters will not stop as they are
supposed to and the backup database could be corrupted.