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

if you stop RDF. Audit trail pinning is lost if you stop TMF. See also the description of the
UNPINAUDIT command in Chapter 8 (page 176).
You can control when TMF dumps an audit trail by configuring TMF for dump to tape. For example,
when configured with a tape dump process, TMF issues a prompt for the operator to mount a tape
when TMF is ready to dump and purge an old audit trail file. Because TMF cannot execute the
dump and purge of the audit trail file until a tape is mounted, the operator can wait until the RDF
extractor finishes that file before mounting the tape.
For more information on configuring TMF, see the TMF Planning and Configuration Guide.
TMF Configuration Without Dump Process on the Primary System
Long ago, the RDF product required that you configure TMF with a dump process that dumps to
tape. RDF no longer imposes this requirement for the following reasons:
• On the primary system, the RDF extractor explicitly pins the audit trail it is currently processing,
thereby preventing TMF from purging it. This explicit pinning remains in effect even if the
extractor process fails or RDF is shut down.
If you must unpin one or more audit trail files, you can do so by issuing an RDFCOM
UNPINAUDIT command. Later, when RDF is restarted, you can restore the necessary audit
trail files from tape.
• TMF includes the functional capability of audit overflow volumes. You should always configure
them with at least one overflow audit volume.
CAUTION: Although RDF no longer requires you to configure TMF with a dump process that
dumps to tape, you should nevertheless configure TMF for dumping to tape or disk if you want
to achieve full TMF protection for your primary database. In addition, if the RDF extractor is
running behind and you stop the TMF and RDF subsystems before RDF has caught up to the
TMF shutdown point, when you subsequently restart TMF, the TMP might roll over the files
before the RDF extractor can process them.
If you are required to do a takeover, it is recommended that you take online dumps of the backup
database before restarting the applications that will use it.
Configuring TMF for RDF Operations on the Backup System
As is indicated in Chapter 5 (page 113), you are strongly urged to configure TMF on your RDF
backup system with audit dumping and you are urged to take frequent online dumps of your backup
database. Performing both of these operations helps ensure fast switching of your application from
the primary to the backup system. Online dumps of your backup database can also be used to
recover a volume on the backup system from a complete media failure, but these online dumps
are not useful for any other type of TMF File Recovery operation on your backup system (for
example, Recover to First Purge). When you want to take an online dump of your backup database,
you must change the RDF UPDATEROPEN parameter from Protected (the default value) to Shared.
When the online dump has completed, you can set the RDF UPDATEROPEN parameter back to
Protected. Please note that if you take online dumps of your backup database, you must also take
audit dumps too. For more information see, “SET RDF” command in Chapter 8 (page 176).
Preparing Databases for RDF Protection
When preparing databases on the primary system for RDF protection, you must consider the
following system aspects:
• Maximum Number of Audited Files Per Volume on Primary System
• Copies of files for the backup database
• DSM catalog and file code 900 replication
56 Preparing the RDF Environment