TMF Operations and Recovery Guide (G06.26+)

Occasional Operations
HP NonStop TMF Operations and Recovery Guide—522417-003
3-13
Replacing Damaged Data Volumes
If you want to remove a data volume from your TMF configuration permanently, the
proper way to do so is as follows:
1. Issue a DISABLE DATAVOL command to shut the volume down cleanly within the
TMF environment.
2. Issue a DELETE DATAVOL command to delete the volume from the TMF
environment.
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.
Replacing Damaged Data Volumes
If a data volume gets physically damaged and you need to replace it, the proper way to
do so is as follows:
1. Issue a DISABLE DATAVOL command to shut down the damaged volume.
2. Issue a DELETE DATAVOL command to delete the volume from the TMF
configuration.
If you got 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. Replace the damaged disk drive.
4. Use the system restore utility to load any nonaudited files onto the replacement
volume from backup tapes.
5. Specifying the same name as the deleted volume, issue an ADD DATAVOL
command to add the replacement volume to your TMF configuration.
If you get an error message in response to the ADD DATAVOL command,
indicating that one or more of the files on the volume might not be in a consistent
state, you can force the volume to be added by including the
IGNOREPREVIOUSCONFIG option in the ADD DATAVOL command.
Caution. After the data volume has been deleted with the ALLOWINCONSISTENCY option,
volume recovery cannot return it to a consistent state.
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.