• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TSM DB Restore


Apr 17, 2018
Reaction score
Hi all

I have a question about a DB Restore i need to do. it has been years since i performed this and have a general understanding of what i need to do

basically i am backing up the DB, reconfiguring the disk that the DB and Logs are on (running out of dbspace, disk was configured mirrored, going to change it to raid-5 - no available storage to extend DB..)

so steps are as i remember and from searching the forums
TSM 7.1.7 on windows
  • Record the DB and activelog/archive/failover archive directory names/files
  • Issue q dbspace f=d and record the output, issue q db f=d and record the output, issue q log f=d and record the output
  • Cancel all processes and sessions – issue "disable sess all" to keep any new sessions from starting
  • Perform a full database backup to a file device class – backupdb type=full devc=filedevc
  • Once DB backup is complete – issue backup volhist – take note of the volhistory file location
  • Issue backup devconfig – take note of the devconfig file location
  • Once complete – issue HALT
  • Open the dsmserv.opt file and remove the * or # from the lines at the bottom that say NOMIGRRECL EXPINTERVAL 0 and DISABLESCHEDS YES
  • Make a copy of the volhist, devconfig, dsmserv.opt and store somewhere where it can be retrieved if necessary
  • Remove the database instance – dsmserv remove db (any other parameter needed here?)
  • Perform the reconfiguration of the drives that the DB and Actlog was on
  • Once reconfigured, recreate the directories for the DB and active logs
  • Create a file that lists out the location of the DB directory/ actlog /?
  • Issue DSMSERV RESTORE DB on =dbdirs.txt
These are the steps in bold i am fuzzy on. Only the DB and Active Log are affected by the disk change configuration.
the archive log and failover archive log are not being touched, so i am not sure if my dbdirs.txt needs the existing directories listed in there too.


Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 19 18.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 61 59.8%
  • Let's be formal and just say Spectrum Protect

    Votes: 13 12.7%
  • Other (please comement)

    Votes: 9 8.8%

Forum statistics

Latest member