Procedure describes the steps involved in relocating database and log volumes. Note that the procedure for Tivoli Storage Manager post-5.5 versions is different than that for prior versions.
The server database and recovery log volumes may have been placed during initial setup in a location not desired for long-term administration of the server, or new hardware added and desire exists to relocate the db & log volumes to new disk.
Resolving the problem
Given that great care must be taken when attempting to relocate a Tivoli Storage Manager server database and recovery log volumes, the following procedures walk you through the process step-by-step for Tivoli Storage Manager servers up to version 5.5:
1) Create the new DB and or Log volume in the new location. This can be done by issuing the relevant command on the Tivoli Storage Manager server:
define dbvol <path and filename> formatsize=xxx
define logvol <path and filename> formatsize=xxx
... where xxxx is the size of the volume in megabytes.
2) Extend the DB or log by the size of the newly created db/log:
extend db xxx
extend log xxx
Where xxx is the number in megabytes and should be what was used for the formatsize value in step 1.
* Total size of db/log cannot exceed the maximum size for the Tivoli Storage Manager version you are at. For currently supported versions (up to 5.4 - see your Server Administrator's Guide for any updated values in later versions), those maximums are:
Recovery Log 13.2GB
3) Now you are ready to remove your old db/log volumes. Reduce the db/log by the TOTAL size of the old db/logs you want to remove:
reduce db xxx
reduce log xxx
Where xxx is the total number in megabytes. You can find out the size of the old db/log volumes by running the following command and noting the size:
q logvol f=d
q dbvol f=d
4)You can then delete the old db/log volumes by issuing the following command for each volume:
del dbvol <volname>
del logvol <volname>
** When the delete dbvol/delete logvol command is issued, the Tivoli Storage Manager server checks the database or recovery log volume specified for any valid information and, as it finds that information, it moves it to other database or recovery log volumes before actually deleting the specified database or recovery log volume. These commands may take a while to complete as the database/log information on the volumes being deleted is being moved to the new volumes. Do not continue until the process is complete. To see if the processes are running, run "query process"
5)Now that there is no association between Tivoli Storage Manager and the old db/log volumes, you can simply go out to the operating system and delete those volumes to reclaim the space on your system.
6) To move db and log copy volumes, you will delete them from the original location with the delete
dbvol/delete logvol command, and when the primary db and log volumes are created you can run
the define dbcopy/define logcopy commands to define copy volumes for the db & log volumes in
the new location.
NOTE: When creating the volumes in step 1 they have to be the same size or greater than the original db/log volumes or step 4 will fail.
For Tivoli Storage Manager Server post-5.5 Versions, see the following link: