IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual, Page: 507 / 828

Chapter 14. Advanced operations
477
Because the library is defined to be a manual library, you will need to
manually mount the tapes.
7. Format the database and recovery log using the DSMSERV LOADFORMAT
utility. This utility prepares the existing server database for the DSMSERV
LOADDB utility. For example, issue this command:
dsmserv loadformat 1 c:\tsmdata\rlp\logv_01.dsm 1 c:\tsmdata\dbp\dbv_01.dsm
The command above prepares one recovery log volume
(c:\tsmdata\rlp\logv_01.dsm) and one database volume
(c:\tsmdata\dbp\dbv_01.dsm).
8. Reload the database using the volumes that contain the data from the unload
operation. For example:
dsmserv loaddb devclass=lto2-dc volumenames=DBD001,DBD002
For the volume names, ensure that you do the following operations:
– Enter the volume names in the same order in which they were used for the
dsmserv unloaddb utility.
– Separate the volume names with a comma and no intervening spaces.
9. If you edited your device configuration file in step 3, replace the edited version
of the device configuration file with the original version.
10.Start the server.
Important: Keep track of the order in which the tape volumes are written
when the database is unloaded. You must specify the volume names in the
same order when you reload the database using the DSMSERV LOADDB
utility. For this task you can either:
򐂰
Review the output generated by the DSMSERV UNLOADDB utility and
record the order of the volumes.
򐂰 Manually view the volume history file to identify the tape volumes
containing the unloaded database. The volumes have a volume type of
DUMPDB. (Do
not
restart the server and issue query volhistory at this
step.)