TMF Planning and Configuration Guide (G06.26+)

Concepts and Capabilities

HP NonStop TMF Planning and Configuration Guide—522416-005

1-2

Where Configuration Information Is Stored

All TMF configuration information is stored in the ZTMFCONF subvolume of the

configuration volume (which is $SYSTEM by default). This subvolume includes all

configuration parameter settings and the files for the TMF catalog, a database that

specifies where all dumped files (from audit dumps and online dumps) reside and

which dump media are available for reuse. Therefore, it is extremely important that the

ZTMFCONF subvolume be backed up after every configuration change (or group of

changes) from which you might need to recover, and that the backup media be readily

available.

A Typical TMF Environment

There is no single typical TMF environment. Typical TMF usage encompasses three

types of environments: light TMF usage, heavy TMF usage, and extremely heavy TMF

usage.

A light TMF-usage environment has a single volume configured to the master audit trail

(MAT), is configured solely to protect the integrity of transactions, and does not use the

audit dump, online dump, and file-recovery features of TMF. The transaction rate for

this environment causes one to two rollovers each day.

A heavy TMF-usage environment has multiple volumes configured to the MAT and

uses audit dumping and weekly online dumps to support file recovery. The transaction

rate for this environment causes a rollover about once each hour.

An extremely heavy TMF-usage environment has multiple volumes configured to the

MAT, multiple volumes configured to one or two auxiliary audit trails, and uses audit

dumping and weekly online dumps to support file recovery. The transaction rate for

this environment causes a rollover about once each hour on each audit trail.

The Configuration Volume

For a database to be protected by the Nomadic Disk Subsystem, TMF configuration

and TMF catalog information must be available at the remote site as well as the local

site. This information, which was stored in the $SYSTEM volume in previous releases,

can now reside on another volume that you specify as the configuration volume. With

this flexibility, you can use the Nomadic Disk Subsystem with the NonStop CLX and

NonStop Cyclone/R systems, which require that the $SYSTEM disk and its mirror

reside within the system cabinet.

This capability is not restricted to use with the Nomadic Disk Subsystem. You might,

for example, want to move TMF catalog and configuration files as part of disk space

management on $SYSTEM.

When you specify a configuration volume other than $SYSTEM, a new file called

CONFVOL is created in the $SYSTEM.ZTMFCONF subvolume. CONFVOL stores the

current configuration volume name; TMF uses the configuration volume specified in