RDF/IMP, IMPX, and ZLT System Management Manual

Preparing the RDF Environment

HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002

2-6

Configuring TMF for RDF Operations

TMF attempts to purge old audit trails each time it rolls over to a new one. The purge

operation is successful only if the audit trail is not pinned on behalf of RDF.

If audit dumping is disabled and TMF were to purge an audit trail before it has been

pinned, you must reinitialize RDF and resynchronize the databases.

You can, however, configure TMF with a dump process to dump audit trail files to tape

or disk. If TMF dumps audit trail files, the extractor waits until that audit trail is restored

from tape and then resumes. In that case, you do not need to reinitialize RDF or

resynchronize the databases.

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.

Note that 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 section 8.

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 HP NonStop Transaction

Management Facility (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, however, for the following reasons:

1. 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.