TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-24
ADD DATAVOLS
The NonStop Remote Database Facility (RDF), which relies on TMF for many of its
functions, uses only the master audit trail for its audit records.
RECOVERYMODE {ONLINE|ARCHIVE}
determines whether audit-trail files are held on disk until they are no longer
required for volume recovery.
ONLINE retains sufficient audit-trail files on disk so that volume recovery does not
need to restore audit information from an archived audit dump. Retaining audit-
trail files on disk can affect audit trail management and transaction processing;
transaction processing, for example, is disabled if it causes the audit trail to exceed
a capacity threshold.
ARCHIVE releases audit-trail files so that they are not retained on disk solely for
the purpose of volume recovery. If volume recovery becomes necessary, one or
more audit dumps might need to be restored. ARCHIVE is allowed only if audit
dumping is configured for the associated audit trail.
The default is ONLINE.
You can change the RECOVERYMODE attribute later by using the ALTER
DATAVOLS command.
IGNOREPREVIOUSCONFIG
specifies that a data volume is to be added to the configuration regardless of
whether it was associated with a previous TMF configuration and thus might be
inconsistent.
If you omit IGNOREPREVIOUSCONFIG and TMF encounters either of the
following conditions, the ADD DATAVOLS command fails:
•
Any volume designated for the current TMF configuration was part of a
previous TMF configuration and was not deleted from that configuration.
•
Any volume designated for the current TMF configuration contains files that
might have been in an inconsistent state when the volume was deleted.
Specifying IGNOREPREVIOUSCONFIG overrides this protective mechanism and
allows TMF to add the volume despite possible inconsistencies.
Security Restrictions
You can issue the ADD DATAVOLS command only if you are a member of the super
user group.
Caution. Volume recovery cannot repair any inconsistencies that exist when a data volume is
added with IGNOREPREVIOUSCONFIG specified, even if the data volume is returned to its
previous configuration environment.