Table of Contents
Advertisement
03/01/2006 11:44:32 ANR1238I Restore of primary storage pool DISKDATA has
Alternatively, you can use the recovery script as a guide and manually run each
step.
If you wish to view the output of the commands run during the server restoration
process, the results are logged in the following files:
LOGANDDB.VOLUMES.INSTALL.LOG
LICENSE.REGISTRATION.LOG
COPYSTGPOOL.VOLUMES.AVAILABLE.LOG
PRIMARY.VOLUMES.DESTROYED.LOG
COPYSTGPOOL.VOLUMES.DESTROYED.LOG
PRIMARY.VOLUMES.REPLACEMENT.CREATE.LOG
PRIMARY.VOLUMES.REPLACEMENT.LOG
STGPOOLS.RESTORE.LOG
19.5.6 Summary of example disaster recovery plan
Using Tivoli Storage Manager Disaster Recovery Manager, we were able to
quickly restore our Tivoli Storage Manager server named LOCHNESS_Server1
on a replacement set of hardware. The off-site backup of the Tivoli Storage
Manager database and the copy storage pool volumes provided the necessary
data.
Once your replacement server is up and running, you should use DRM
procedures to return the retrieved vault recovery volumes so they are available in
the event of another disaster. You can now resume normal backup and disaster
protection operations.
19.6 Summary
As we mentioned on the first page of this chapter, our example and the
associated explanations are not sufficient to supply the reader with enough
understanding of disaster recovery to properly design and implement a solution.
There are some excellent books on disaster recovery available. However, the
IBM Redbook Disaster Recovery Strategies with Tivoli Storage Management,
SG24-6844, is certainly one of the "must read" choices.
Implementing the Disaster Recovery Manager without a full understanding of the
product, and a business commitment to its ongoing care and feeding, may lead
to misconfiguration or undesirable results at a point when it is most needed.
ended. Files Restored: 5427, Bytes Restored: 376963072,
Unreadable Files: 0, Unreadable Bytes: 0.
Chapter 19. Disaster Recovery Manager
627
Advertisement
Table of Contents
