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

To perform DDL operations on Enscribe files that RDF does not replicate, there are two methods to
coordinate the operation:
The STOP TMF Method
1. Stop application processing on the primary system.
2. Stop TMF on the primary system; wait for RDF to read the STOP TMF message in the audit
trail and stop itself.
3. Start TMF on the primary system so the operations on audited Enscribe files can be performed.
4. Start RDF so that no audit trails are lost, but do not resume application processing.
5. Perform each operation on Enscribe files on the backup system and the corresponding operation
on the primary system.
6. Finally, resume application processing.
The STOP RDF DRAIN Method
1. Stop application processing on the primary system.
2. When all applications have terminated, issue the STOP RDF, DRAIN command.
3. Perform the DDL operation on the primary system.
4. When the purger has logged RDF event 852, perform the same DDL operation on the backup
system.
5. START RDF on the primary system.
6. Start application processing on the primary system.
Resynchronizing Databases
There are two ways of resynchronizing your primary and backup databases: offline and online.
With offline resynchronization you must first stop your applications and TMF on the primary system.
With online resynchronization, however, you can resynchronize entire databases, selected volumes,
a single volume, or individual tables and files while your applications continue to run on the primary
system.
The remainder of this chapter describes how to do offline resynchronization. For information about
online resynchronization, see Chapter 7 (page 158).
To resynchronize the primary and backup databases, you need to make all backup database files
or tables logically identical to the primary database files or tables when there is no audit data to
be processed for the files or tables. If you know which files or tables are not synchronized,
resynchronize the databases only on the volumes that contain those files or tables.
There is no audit data to be processed for a volume at the following times:
• Immediately after TMF has been started for the very first time and no applications have been
started yet
• When the RTD time is zero for the volume’s updater process, and no audit data is being
generated by any application while the files or tables are being duplicated
• When TMF is stopped (without the ABRUPT option)
Make sure the primary and backup databases are synchronized if any of the following should
occur:
• A TMF file recovery operation to a timestamp or to first purge occurs, after which only the
affected database tables or files need to be resynchronized.
• Asterisks (****) appear in the final column of the STATUS RDF display, indicating that an
updater process has experienced an unexpected file-system error.
Resynchronizing Databases 155