Manualshelf

TMF Operations and Recovery Guide (G06.24+)

ManualsBrandsHP ManualsServerHP NonStop G-Series
71727374757677787980
Occasional Operations
HP NonStop TMF Operations and Recovery Guide—522417-002
3-15
Renaming Data Volumes
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.
Moving Audited Files to a Different Data Volume
If you need to move protected files to a different data volume, follow these steps:
1. Stop any applications that access the files to be moved.
2. Using the FUP DUP command, move the files to the new data volume.
3. Using the FUP ALTER command, set the audit attribute of the new files so that the
files are audited.
4. If you want to be able to recover the files, make an online dump of the files in the
new location.
5. Set your applications so they access the new files in their new location.
6. Restart the applications that were stopped in Step 1.
Make sure your applications are accessing each new file. If they access and
modify the old data file, the new data file is obsolete. If this happens, repeat the
procedure.
7. When you are satisfied that your applications are accessing the new files, purge
the old files.
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.