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

Moving TSM Server To New Hardware and OS

jayp2200

ADSM.ORG Member
#1
Our company has recently purchased a new HP server and new disk storage for it so I would like to know the best method and steps needed for moving/migrating our current TSM server setup to it.

Our current system is an IBM x3650 M3 which is running Windows Server 2008 R2 Standard and TSM version 7.1.6.0. The new HP server will be running Windows Server 2012 R2 but will keep the same TSM 7.1.6.0 version. The existing IBM TS3310 tape library will need to be moved to the new server as well.

Any help would be greatly appreciated!
 

moon-buddy

ADSM.ORG Moderator
#2
Simple answer:

Build the new TSM server on Windows 2012
Install TSM 7.1.6.0 and configure exactly as you have on the current TSM server - tape library, diskpool, etc.
Backup the TSM DB from the old TSM server
Move the Library connections from the old to the new TSM server
Shutdown the TSM server
Restore the DB to the New TSM server.
Start the new TSM server
 

manofmilk

ADSM.ORG Member
#4
Can I just chuck an additional question on here, save starting a new thread - we're about to do a very similar thing. Can you confirm that we need to create a TSM instance on the new server and then overwrite it with the restore please?
I.e. its not enough just to install TSM, we must run dsmicfgx and create a new instance first? And we don't need to drop the new instance we created - we can just 'overwrite' it with the database restore?
 

jayp2200

ADSM.ORG Member
#5
Can I just chuck an additional question on here, save starting a new thread - we're about to do a very similar thing. Can you confirm that we need to create a TSM instance on the new server and then overwrite it with the restore please?
I.e. its not enough just to install TSM, we must run dsmicfgx and create a new instance first? And we don't need to drop the new instance we created - we can just 'overwrite' it with the database restore?
Yes, good question! In addition, I'm wondering if we need to copy the existing data over to the new server as well before or after the db is restored?
 

moon-buddy

ADSM.ORG Moderator
#6
Yes, good question! In addition, I'm wondering if we need to copy the existing data over to the new server as well before or after the db is restored?
No need - create the new instance with the same name as the old one - with same settings - and when you do a restore, all of the so called 'data' will show up.

This procedure is similar to a DR scenario except you don't make all of the tapes read only. The server BIOS name and IP address does not have to be the same. However, the instance name - the TSM server name - must be the same as the old one and that ALL nodes must be accessing the TSM via a DNS name and NOT by IP address.
 

joshmo

ADSM.ORG Member
#7
Has anyone tried this by just installing the instance and moving all the db, instance, log ,volumes, drives etc to the new server? I'm trying to reduce the downtime required and that would save me a couple of hours.
 

rcdelaw

ADSM.ORG Member
#9
Will NOT work - a DB restore from the old to the new is the way to go.
You are going from Windows to HP OS (big endian / little endian), you won't be able to just do a restore db you will have to do and export/import. This can be accomplished via tape media (tape/vtl/device class file) or the perferred method, server to server. You do know that TSM 7.1.x is out of support next year, and we do not support HP in version 8.1 and above. You might want to rethink the movement of your TSM server. If you go through with it, ensure you keep track of the order in which the tapes are created you will have to reverse the order during the import if you don't go server to server.

Ron Delaware
IBM Systems Lab Service
925-475-5315
 

moon-buddy

ADSM.ORG Moderator
#10
You are going from Windows to HP OS (big endian / little endian), you won't be able to just do a restore db you will have to do and export/import. This can be accomplished via tape media (tape/vtl/device class file) or the perferred method, server to server. You do know that TSM 7.1.x is out of support next year, and we do not support HP in version 8.1 and above. You might want to rethink the movement of your TSM server. If you go through with it, ensure you keep track of the order in which the tapes are created you will have to reverse the order during the import if you don't go server to server.

Ron Delaware
IBM Systems Lab Service
925-475-5315
I think you are off queue: there was no mention of HP OS in the post - just HP server, and I quote:

Our company has recently purchased a new HP server and new disk storage for it so I would like to know the best method and steps needed for moving/migrating our current TSM server setup to it.
The target is also Windows 2012 R2 on the HP server for which should also be running CISC Intel processors and not Alpha or Itanium processors. I further quote:

The new HP server will be running Windows Server 2012 R2 but will keep the same TSM 7.1.6.0 version.
His issue is:

"Can the data from the DB volumes and log be just copied over and the system started"

This will not work
 

rcdelaw

ADSM.ORG Member
#11
I think you are off queue: there was no mention of HP OS in the post - just HP server, and I quote:



The target is also Windows 2012 R2 on the HP server for which should also be running CISC Intel processors and not Alpha or Itanium processors. I further quote:



His issue is:

"Can the data from the DB volumes and log be just copied over and the system started"

This will not work
See what happens when you make assumptions and made an assumption
 

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

    Votes: 16 53.3%
  • Let's be formal and just say Spectrum Protect

    Votes: 4 13.3%
  • Other (please comement)

    Votes: 3 10.0%

Forum statistics

Threads
30,889
Messages
131,422
Members
21,194
Latest member
jamesmacd40