RDF System Management Manual for H-Series RVUs (RDF 1.8)

TMF Configuration With Dump Process
When you configure TMF with audit dump on, that subsystem dumps an audit trail to tape or
disk before purging the audit trail. This approach is strongly recommended on the primary
system.
Audit-trail files are pinned by the RDF extractor and TMF cannot purge pinned files until the
extractor has finished processing them. TMF will keep these files pinned on behalf of the RDF
extractor even 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 173).
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
Long ago, the RDF product required that you configure TMF with a dump process that dumps
to tape. RDF no longer imposes this requirement on either the primary or backup systems 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 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 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.
Preparing Databases for RDF Protection
When preparing databases on the primary system for RDF protection, you must consider the
following system aspects:
• Copies of files for the backup database
• DSM catalog and file code 900 replication
• Copies of NonStop SQL/MP and NonStop SQL/MX views on the backup systems
• Placement of partitioned Enscribe files and NonStop SQL/MP and NonStop SQL/MX tables
Audited Backup Database Files
The backup system must have copies of all files that RDF protects. For a successful takeover of
business operations in the event of a primary system failure, the backup system should also have
copies of all the files needed by the primary system applications (including alternate key files
Preparing Software and Database Files for RDF Operations 67