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

• If you plan to include the TIMESTAMP option in the INITIALIZE RDF command, make sure that
the primary system database is backed up after the TMF shutdown so that the backup database
can be restored at this point in the audit trail. Consider the following example:
1. TMF and RDF subsystems are running.
2. TMF subsystem is stopped, and RDF subsystem subsequently stops.
3. TMF subsystem is started and application processing resumed.
4. TMF subsystem is stopped.
If you initialize RDF at the shutdown point at Step 1, you should restore on the backup system
a copy of the primary system database taken at Step 1. The databases would not be
synchronized if the database at Step 2 was restored to the backup system.
If you initialize RDF to the timestamp corresponding to Step 2, you should restore on the
backup system a copy of the primary system database taken at Step 2.
• If you are using the TIMESTAMP option, it is a good idea to initialize RDF to the latest TMF
shutdown point. In the example immediately above, if you were to initialize RDF to Point 2,
then, after you have initialized and started RDF, it will shutdown when it reaches the audit
trail location of the next TMF shutdown at Point 4. In this case, you must initialize RDF at the
most recent TMF shutdown point. If you initialize RDF at an earlier shutdown point, RDF
operations will start at that point but will shut down when the next TMF shutdown point is
reached. In this case, you must restart RDF quickly so that operations on the backup system
do not fall too far behind those on the primary system. If you choose to initialize RDF at a TMF
shutdown point that is not the most recent, watch the RDF event messages for the RDF shutdown
message and then restart RDF immediately.
• If you include the TIMESTAMP option in the INITIALIZE RDF command, use the following
guidelines to determine when you must restore the backup database:
◦ If you are going to start RDF with UPDATE ON, restore the database to the backup system
before you start RDF.
◦ If you are going to start RDF with UPDATE OFF, you do not have to restore the database.
However, if the need for an RDF takeover arises, you must then restore the database on
the backup system before you issue the TAKEOVER command.
• In any event, if you plan to enable updating on the backup system as part of the new
configuration, ensure that the primary and backup databases are logically identical before
entering the INITIALIZE RDF command. For more information about database synchronization,
see “Understanding Database States” (page 148).
Examples
The following INITIALIZE RDF command, issued on the primary system, \LON, initializes the
subsystem to 2:30 pm, January 12, 2004:
]INITIALIZE RDF, BACKUPSYSTEM \CHI, TIMESTAMP 12JAN2004 14:30
Do you wish to proceed? [Y/N] Y
Please wait while RDF searches for the specified timestamp.
TMF shutdown at 12JAN2004 14:30 has been found. RDF will
start at RBA: 376275 MAT file: $AUDIT.ZTMFAT.AA000414
Do you still wish to start at this point? [Y/N] Y
The following INITIALIZE RDF command, issued on the primary system \LON after TMF was stopped,
deleted, and reconfigured, initializes RDF at once, without prompting you to confirm your request:
]INITIALIZE RDF, BACKUPSYSTEM \CHI, SUFFIX 2 !
In the first example, the RDF control subvolume is implicitly named LON while in the second example
it is explicitly named LON2.
RDFCOM Commands 205