TMF Operations and Recovery Guide (G06.26+)

Occasional Operations
HP NonStop TMF Operations and Recovery Guide—522417-003
3-15
Associating a Data Volume with a Different Audit
Trail
Associating a Data Volume with a Different Audit Trail
Most applications, even very large ones, use only a master audit trail. If you have
configured one or more auxiliary audit trails, however, and you need to associate a
configured data volume with a different audit trail, the proper way to do so is as follows:
1. Issue a DISABLE DATAVOL command to shut the volume down cleanly.
2. Issue a DELETE DATAVOL command to delete the volume from the TMF
configuration.
If you received an error message in Step 1, indicating that the volume did not shut
down cleanly, you can force the volume to be deleted by including the
ALLOWINCONSISTENCY option in the DELETE DATAVOL command.
3. Issue an ADD DATAVOL command to add the volume back into the TMF
configuration, specifying the desired audit trail.
If the volume did not shut down cleanly in Step 1, you can force the volume to be
added by including the IGNOREPREVIOUSCONFIG option in the ADD DATAVOL
command.
4. Make online dumps of all the audited tables and files on the data volume that you
want protected by the TMF file recovery feature.
Renaming Data Volumes
You cannot rename a data volume while TMF is running without risking data
inconsistency on the volume. A data volume is protected by TMF based on its name
when it is added to the TMF configuration. To rename a volume and continue to have
it protected by TMF, you must first delete it from the TMF configuration while it is in a
consistent state, rename it, and then re-add it to the TMF configuration, using its new
name. If you rename a data volume without taking these steps, TMF will not recognize
the volume.
After renaming a data volume, you cannot use existing TMF online dumps to recover
files residing on this data volume. You must now take new online dumps to support file
recovery for this volume.
Caution. After the data volume has been deleted with the ALLOWINCONSISTENCY option,
volume recovery cannot return it to a consistent state.
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.