• 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.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    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.

Build a New TSM Server with Database backup.

Shiv0202s

ADSM.ORG Member
#1
Hi All,

Actual Setup - We have a TSM server.. Replication & Deduplication is running
C Drive- O/S
D,E,F,G Drives- TSM Database
H,I,J,K Drives- Active log,Archive log etc

M,N,O,P,Q,R,S Drives- Storage pools for TSM ( Each of 2TB)

C,D,E - - - K are from a Different datastore and the remaining drives are from a Different Datastore.

This TSM server is replicating to another TSM Server.. So we have copy of volhist,devconfig etc in the other TSM Server....

SAN team has phased out the drives from C,D to K.. so all the o/s, database, active logs are gone.

We have database backup in L; Drive

We have build a windows machine and mounted the L;Drive Lun to the windows machine.

Now i need to build a new tsm server with the database backups.

Let me know if i can follow the below steps-

1. Install TSM then create database,log volumes with the actual size or more
2.then format database and log volumes
3.Restore database


Can Some one tell me the steps to be followed..
 

moon-buddy

ADSM.ORG Moderator
#2
If you have built a new TSM server which has a similar setup as the old one, just do a restore of the TSM DB from the L: drive. Once the new TSM server is up, delete and redefine the disk and other pools.
 

Shiv0202s

ADSM.ORG Member
#3
Hi Moon-buddy,

I am getting the below error while restoring the database
Help me

C:\Program Files\Tivoli\TSM\server>dsmserv restore db
ANR7800I DSMSERV generated at 02:08:06 on Jul 26 2012.
Tivoli Storage Manager for Windows
Version 6, Release 3, Level 2.000
Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 2011.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR0900I Processing options file c:\program files\tivoli\tsm\server1\dsmserv.opt.
ANR4726I The ICC support module has been loaded.
ANR1636W The server machine GUID changed: old value (), new value (c8.b2.9a.31.c9.8c.11.e4.be.a9.00.50.56.95.2e.0b).
ANR7808W Sun Microsystems Library Attach module libacs.dll is not available from the system.

ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1500.
ANR0152I Database manager successfully started.
ANR4636I Starting roll-forward database restore.
ANR4591I Selected backup series 758 from 03/12/2015 and 08:00:27 as best candidate available for restore database processing.

ANR4592I Restore database backup series 758 includes eligible operation 0 with volume L:\TSM\BACKUP01\26143608.DBV having sequence 10001 and using device class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143649.DBV having sequence 10002 and using device class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143649.DBV having sequence 10002 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143684.DBV having sequence 10003 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143722.DBV having sequence 10004 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143757.DBV having sequence 10005 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143792.DBV having sequence 10006 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143830.DBV having sequence 10007 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143866.DBV having sequence 10008 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143903.DBV having sequence 10009 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143939.DBV having sequence 10010 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26143975.DBV having sequence 10011 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26144012.DBV having sequence 10012 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26144055.DBV having sequence 10013 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26144101.DBV having sequence 10014 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26144148.DBV having sequence 10015 and using device

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26144200.DBV having sequence 10016 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26144244.DBV having sequence 10017 and using device

class FILEDEV1.

ANR4592I Restore database backup series 758 includes eligible operation 0 with

volume L:\TSM\BACKUP01\26144294.DBV having sequence 10018 and using device

class FILEDEV1.

ANR4598I Validating database backup information for selected backup series 758

and operation 0 using volume L:\TSM\BACKUP01\26144294.DBV.

ANR8340I FILE volume L:\TSM\BACKUP01\26144294.DBV mounted.

ANR1363I Input volume L:\TSM\BACKUP01\26144294.DBV opened (sequence number 18).A

NR1364I Input volume L:\TSM\BACKUP01\26144294.DBV closed.

ANR3008I Database backup was written using client API: 6.3.0.0.

ANR4638I Restore of backup series 758 operation 0 in progress.

ANR4897I Database restore of operation 0 will use device class FILEDEV1 and

attempt to use 1 streams.

ANR2969E Database restore terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 40.

ANR2032E RESTORE DB: Command failed - internal server error detected.

ANR9999D Thread<0> issued message 2032 from:

ANR9999D Thread<0> 000007FEF29EE3DE outMsgf()+3e

ANR9999D Thread<0> 000007FEF2287355 AdmRestoreDb()+12f5

ANR9999D Thread<0> 000007FEF221C857 admRestoreDatabase()+187

ANR9999D Thread<0> 000007FEF2201322 psPostCleanup()+272

ANR9999D Thread<0> 000007FEF22034E1 adsmMain()+ef1

ANR9999D Thread<0> 000000013F5C111B main()+9b dsmserv.c:241

ANR9999D Thread<0> 000000013F5C28DA __tmainCRTStartup()+11a crtexe.c:555

ANR9999D Thread<0> 00000000771A652D BaseThreadInitThunk()+d

ANR9999D Thread<0> 00000000772DC521 RtlUserThreadStart()+21

ANR1794W TSM SAN discovery is disabled by options.
 

moon-buddy

ADSM.ORG Moderator
#4
1. What kind of TSM DB backup do you have? FULL or INCREMENTAL?
2. Is the new system setup the way the old one was? Same (or bigger) DB and LOG volume sizes, and drive mappings?
3. Configuration files copied over?
4. Same TSM server version installed on the new system?

If you don't have the same drive mappings for the DB and LOG volumes, specify the new locations when you do the restore.
 

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: 17 19.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 53 60.9%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 11.5%
  • Other (please comement)

    Votes: 7 8.0%

Forum statistics

Threads
31,472
Messages
134,143
Members
21,569
Latest member
srinathkodela
Top