TMF Operations and Recovery Guide (G06.26+)

Recovery Methods
HP NonStop TMF Operations and Recovery Guide—522417-003
7-33
Recovering Your TMF Environment to a New System
Following Disaster
state exist, TMF startup is not affected. Nevertheless, these exported transactions
must be completed to clean up data structures for the transaction.
Integrating Multiple Configurations
After recovering the database to the remote node, you can manually integrate data
volumes from the remote node’s configuration into the primary node’s configuration.
Use the ADD DATAVOLS command with the IGNOREPREVIOUSCONFIG option to do
this.
TMF starts protecting the data volumes when you add them to the primary node’s
configuration. Because the existing online dumps of these data volumes are unusable,
you need to take new online dumps if you want to be able to perform file recovery after
adding the data volumes to the new configuration.
When you are ready to move the primary node’s configuration back to the primary
node, you can remove the remote node’s data volumes using the TMFCOM DELETE
DATAVOLS command.
For instructions on changing the data volume configuration, refer to Section 3,
Occasional Operations.
Recovering Your TMF Environment to a New System Following
Disaster
If a disaster affects the physical condition of your NonStop system, the TMF system (as
well as other software, and in fact, your entire system) could become totally inoperable.
Such disasters can range from local damage (fire or electrical damage in the computer
room) to far greater catastrophes (floods, earthquakes, or tornados). In the face of
such calamity, you can recover your TMF environment (a tape containing the TMF
configuration files and the associated online and audit dumps) to another system. TMF
does not require the target system to have the same node name or node number as
the source system from which the TMF environment came, eliminating the need to
revise node-identifier instances in the old environment.
This disaster-recovery operation is not performed through the TMFCOM or SPI
interface. Instead, it is selected by setting a flag through the SNOOP command
interface. Complete details and directions appear in Support Note S02073A, NonStop
TMF Disaster Recovery with A-T Backup/Restore. SNOOP itself is provided with the
TMF product and is documented in the file $SYSTEM.SYSnn.SNOOPDOC.