It is a little bit confusing about the TSM version convention, as different components may be at different versions. In my case, I am going to upgrade my TSM to 6.4.1. The server version is actually 6.3.4 instead of 6.4.1.
Tivoli® Storage Manager Version 6.4.1 and Tivoli Storage Manager Extended Edition Version 6.4.1 are made up of the following components and code levels:
- Tivoli Storage Manager Operations Center Version 6.4.1
- Backup-archive client at Version 6.4
- Application programming interface (API) at Version 6.4
- Server at Version 6.3.4, including the Administration Center, Tivoli Monitoring for Tivoli Storage Manager, and device driver components, which are also at Version 6.3.4
Tivoli® Storage Manager Version 6.4 and Tivoli Storage Manager Extended Edition Version 6.4 are made up of the following components and code levels:
- Backup-archive client at Version 6.4
- Application programming interface (API) at Version 6.4
- Server at Version 6.3.3, including the Administration Center, Tivoli Monitoring for Tivoli Storage Manager, and device driver components, which are also at Version 6.3.3
Besides being able to use TSM operation center, I am interested know other benefits that I can get from this upgrade project. What’s new in TSM 6.4?
First thing first, check the upgrade path and compatibility list on IBM website. It looks we are good to go.
Upgrade process starts here:
1) Backup the database. And the preferred method is to use a snapshot database (the backup file can be found in the defined directory in the backup device).
backup db type=dbs dev=DBBAK
2) Backup device configuration and volume history (the backup files can be found in the server instance directory).
backup devconfig filename=devconfig_bak
backup volhistory filename=volhistory_bak
3) Backup the server option file (normally named as dsmserv.opt in the server instance directory).
4) Backup the deployment engine.
c:\Program Files\IBM\Common\acsi\bin>de_backupdb.cmd
5) Delete the nodelock file in C:\ProgramData\IBM\DB2\DB2TSM1\license\. nodelock contains the previous licensing information.
6) Use halt command to stop the TSM service after all backup jobs completed.
7) Double click the fix pack file ‘6.3.4.000-TIV-TSMALL-WindowsX64.exe’. It will extract the files into the same folder.
8) Double click ‘install.exe’ after the extraction finished.
9) Start the TSM service. For the first time, it will take a while to start up.
10) Register the license.
register lic file=*.lic
References:
Jackie Chen's IT Workshop 
Hi just wanted to ask you if you had any problems after performing the upgrade to 6.4.1 with DB2 Licenses?
I followed your post step by step, since i wanted to do the exact same thing, upgrade my TSM server from 6.3.1 to 6.4.1.
I got some warnings when installation ended but nothing relevant.
Then i tried to start the TSM Server service (Running on Windows) without luck, after trying to start the server from command line i got an error pointing to DB2 licenses (see below)
After a few hours trying to look in the internet for hints…. i remembered…. what if i restore that nodelock file (step 5)?! It worked!!! TSM Server service started without problems.
Error when starting the server manually:
C:\Program Files\Tivoli\TSM\server>dsmserv -k ServerB
ANR7800I DSMSERV generated at 10:55:11 on May 23 2013.
Tivoli Storage Manager for Windows
Version 6, Release 3, Level 4.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\ServerB\dsmserv.o-
pt.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
ANR0188E Fail to start the database manager. Database manager license not foundA
NR0172I rdbdb.c(1722): Error encountered performing action InstanceStop.
ANR0162W Supplemental database diagnostic information: -1032:SQLSTATE 57019:
The statement was not successful, because of a problem with a resource.
:-1032
(SQL1032N No start database manager command was issued. SQLSTATE=57019
).
I did not have a single problem, the whole process went smoothly. Did you successfully register your new license file? And where did you get your TSM installation file? It has to be downloaded from the IBM website with a granted login credential, otherwise the media may not contain a valid license file.
Hi franciscobatista2013, Hi Jackie
we had the same problem as Francisco – after upgrading our TSM Server from 6.3.3.100 to 6.3.4.300 using your “Upgrade Guide”. After restoring the nodelock file in the DB2-Licensing-Path the TSM-Server-Instances worked as expected. Could it be that you were updating a TSM-Server which was set up in the last 90 days before your update, Jackie? Anyway, our TSM-Servers are running and we’re not getting any problems, so thank you for your guide!
I’m looking forward hearing from you and following your blog as usual =)
Hi, thank you for your website; it’s very usefull to me and I follow your works.
I have two questions:
1) When upgrading TSM from 6.3.3.0 to 6.3.3.1, my licence went down. The licence is no longer in compliance. Any idea?
2) Is it possible to migrate directly from 6.3.3.1 to 7.1.1 without a transit version? In IBM notes, it possible to migrate from 6.3 or 6.4 to 7.1.1 directly.
If you downloaded the package from IBM after login, the license should be included. Otherwise, you need to copy it from your old package. In terms of upgrade, check the upgrade path and other requirements on IBM website.
But can u update how to update TSM admincenter from version 6.2 to 6.4
Since you already have 6.3.1 installed I think you can leave out the part with the nodelock file. A new license file is necessary when you go from 6.2 to 6.3 (like I did yesterday). With 6.3.1 already installed the upgrade to 6.3.4 does not need a new license? Furthermore in the document for 6.3.4 the nodelock file in “the server instance directory” is deleted during an upgrade from 6.2 to 6.3 and not the one in the C:\Programdata dir.