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

set of disks can be replicated to another set of target disks to provide a copy of the live database.
There are two operational considerations unique to this environment:
• The updaters operate in transaction mode, which means you should not stop TMF before
stopping RDF.
• The RDF takeover operation cannot be performed unless you manually stop the monitor and
extractor processes before issuing the TAKEOVER command or include the ! option in the
TAKEOVER command.
Online Product Initialization
You can initialize RDF/IMP, IMPX, or ZLT while your applications continue to run. This is particularly
useful for installing new versions of RDF into existing production environments where you cannot
afford to stop your applications even briefly to generate a TMF shutdown timestamp. It is also
useful if you encounter a problem for which you would like to reinitialize RDF without stopping
your applications.
For information about this capability, see:
• “Initializing RDF Without Stopping TMF (Using INITTIME Option)” (page 69)
• “Online Installation and Initialization Without Stopping RDF” (page 71)
• “INITIALIZE RDF” (page 201)
Online Database Synchronization
With RDF/IMP, IMPX, or ZLT you can synchronize entire databases or selected volumes, files,
tables or even partitions while your applications continue to run. For information about this
capability, see Chapter 7 (page 157).
Online Dumps of the Backup Database
With RDF/IMPX or ZLT, all backup databases are audited by TMF. You can take online dumps of
a backup database at any time, thereby minimizing the amount of time necessary to perform any
subsequent takeover operation. For information about taking dumps while the updaters are running,
see Chapter 5 (page 110).
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/EXCLUDEPURGE. Wild cards in file names and subvolume names are not
supported in this command.
NOTE: The RDF administrator must ensure that the data of the files included or excluded 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.
For information about subvolume-level and file-level replication, For more information, see
Chapter 11 (page 271).
Other RDF Features 45