To restore or recover a Tivoli Storage Manager V5 database you should follow these basic steps.
- Prepare the files you need to do a restore
- Format the database and logs
- Restore the database
- Sort out any storage pool issues
Obviously, you need a good backup of a TSM database, and you need to know the
device class that was used for the backup. For illustration, we will
assume the latest database backup is on a tape called JK456L5 and used
a devclass called LTO5TAPE.
You also need a list of the database and log file names and sizes. If
you use DRM then the best place to get this from is the latest prepare.
If you don't use DRM, you can get this info when your TSM server is
running with the commands.
query dbvol f=d
query logvol f=d
What if your
database crashes and you don't have a prepare? You can still get the
info with dsmserv commands, use these commands from command prompt if your server is down, go the server directory and run
dsmserv display dbvolumes
dsmserv display logvolumes
Create two text files, one called DB.VOLS that contains the
Database file names, paths and sizes and one called LOG.VOLS for the log
files. The files should look like this, but use your own file names,
paths and sizes. The file sizes are in MB, so this is a 25GB database.
DB.VOLS
"H:\TSMDB\DB01.DSM" 5000
"H:\TSMDB\DB02.DSM" 5000
"H:\TSMDB\DB03.DSM" 5000
"H:\TSMDB\DB04.DSM" 5000
"H:\TSMDB\DB04.DSM" 5000
LOG.VOLS
"H:\TSMRLOG\RLOG01.DSM" 4096
"H:\TSMRLOG\RLOG02.DSM" 4096
DB.VOLS
"H:\TSMDB\DB01.DSM" 5000
"H:\TSMDB\DB02.DSM" 5000
"H:\TSMDB\DB03.DSM" 5000
"H:\TSMDB\DB04.DSM" 5000
"H:\TSMDB\DB04.DSM" 5000
LOG.VOLS
"H:\TSMRLOG\RLOG01.DSM" 4096
"H:\TSMRLOG\RLOG02.DSM" 4096
Place these files in your c:\program files\tivoli\tsm\server\ directory
Formatting or preparing the new TSM Database volumes
Navigate to the c:\program files\tivoli\tsm\server\ directory and run the following command. Note that the logs are described first, then the database, and that you need to say how many of each type of file you are formatting, so 2 log volumes and 4 database volumes.
DSMSERV FORMAT <2 FILE:LOG.VOLS> <4 FILE:DB.VOLS>
When you run a DSMSERV FORMAT on a Windows server, it resets the
registry entry for the TSM server, and this must be put back before you
attempt the restore. Use REGEDIT and navigate to the correct registry
entry for your server.
Also Read: Taking TSM server DB backup when the server is down
If you just have one TSM server on this Windows box, it will be Server1, otherwise Server2-4 depending on which server you are working with. The Server1 key is
HKEY-LOCAL-MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server1 and you need to change the path entry from c:\progam files\tivoli\TSM\Server to Server1.
Also Read: Taking TSM server DB backup when the server is down
If you just have one TSM server on this Windows box, it will be Server1, otherwise Server2-4 depending on which server you are working with. The Server1 key is
HKEY-LOCAL-MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server1 and you need to change the path entry from c:\progam files\tivoli\TSM\Server to Server1.
Restoring the TSM DB
Navigate to the c:\program files\tivoli\tsm\server\ directory and run
the following command. The tape name and devclass are the ones we found
before we started the restore, you substitute your own names.
DSMSERV RESTORE DB VOLUMENAMES= JK456L5 DEVCLASS=LTO5TAPE commit=yes
Auditing Storagepools to syncronize with TSM DB
Before you start TSM, go into the dsmserv.opt file and add the lines, This will stop automatic migration, any schedules and expire interval process as soon as TSM starts.
NOMIGRRECL
DISABLESCHED YES
EXPINT 0
Now start your server in the foreground and
run command DISABLE SESSIONS to stop clients from contacting the server.
Audit your disk storage pools using AUDIT Volume volume_name FIX=YES command, and that will hopefully fix any problems, but you may need to delete
and redefine your disk volumes, discarding faulty data, to get migration
to run clean.
Also Read: Steps to do after successful TSM DB restore
Also Read: Steps to do after successful TSM DB restore
Also audit your tape library, and that will let TSM know the current location of all tapes.
check your latest saved volhist (volhist.out) file in TSM server directory for any tapes that have been deleted or updated since the backup ran. You will need to audit these tapes too. Once you complete the audits, remvove the changes you made to the dsmserv.opt file (NOMIGRRECL, DISABLESCHED, EXPINT), halt the TSM server, then start it normally and enable sessions again.
0 Comment to "How to restore or recover TSM server V5"
Post a Comment