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

user applications to open backup database files for read access but not for write access while the
updater process has the file open. PROTECTED mode, however, is incompatible with taking online
dumps and RELOAD operations. Therefore, if you want to perform one of these two operations,
you need to change UPDATEROPEN from PROTECTED to SHARED. When you have finished the
operation, you should set UPDATEROPEN back to PROTECTED. Previously you had to stop the
updaters before you could change the UPDATEROPEN mode. You can now do this online, without
stopping the updaters.
PROTECTED OPEN is a special variation of PROTECTED. If you have PROTECTED set, it is possible
for the updater to close a file if that file has had no update activity for five or more minutes. If a
rogue user application then opens the file for write access, it is able to write to the backup database
files. If the updater then wants to apply audit from the primary system to that file, the updater will
encounter an error 2 on its REDO operations, and the file will no longer be in synchronization with
the corresponding file on the primary system. The PROTECTED OPEN mode means that once the
updater has opened the file, it will not close the file even if it encounters a period of idle activity
against the file.
SOFTWARELOC Attribute
The SOFTWARELOC attribute specifies where the RDF software is installed on both the primary
and backup systems. The default is $SYSTEM.RDF.
NETWORK Attribute
The NETWORK attribute specifies whether or not you are configuring an RDF network.
When set to OFF (the default value), an RDF takeover operation provides local database consistency,
but it cannot provide transaction consistency for network transactions that involved several RDF
backup databases.
When set to ON, the RDF subsystem provides database consistency for network transactions that
were replicated to other backup databases by other RDF subsystems.
When set to ON, you must either have the NETWORKMASTER attribute for the same system also
set to ON or have another system configured as the network master.
NETWORKMASTER Attribute
The NETWORKMASTER attribute specifies whether the particular system is the master of the RDF
network.
When set to OFF (the default value), the particular system is not the network master.
When set to ON, the particular system is the network master of the RDF network and this RDF
system coordinates takeover operations across all the RDF subsystems that make up the RDF network.
When this attribute is set to ON, the NETWORK attribute must also be set to ON.
UPDATEREXCEPTION Attribute
The UPDATEREXCEPTION attribute specifies the manner in which exception files are used.
When set to ON (the default value), the updaters log an exception record for each and every audit
record they must undo during a takeover.
When set to OFF, the updaters log exception records only for the first and last audit records that
must be undone (the minimum logging necessary to support Triple Contingency operation).
LOCKSTEPVOL Attribute
The LOCKSTEPVOL attribute specifies the primary system disk volume on which the RDF lockstep
file (control-subvolume.ZRDFLKSP) is to be located. The specified volume must be configured
to the Master Audit Trail (MAT), and either the entire volume or at least the lockstep file must be
protected by the RDF subsystem. For information about the RDF lockstep capability, see Chapter 15
(page 299).
76 Installing and Configuring RDF