Manual Upgrade IBM Spectrum Protect 7.1.x to 8.1.x

I'm ended up in a situations where a IBM Spectrum Protect (ISP) server was lock down with limitation who is allowed to login over SSH.

The main reason of this is because the server was connected to a Linux based LDAP environment after the installation of ISP was done.

So now did we end up in a situation where we not where able to let the local ISP user account couldn't ssh to itself.
And because we couldn't ssh even though localhost to our ISP user (let's call it tsminst1).

And I guess I'm not alone with this issue so I guess this could be a create blog post for my Spectrum Protect / TSM friends.

First of all if you are using SuSE Linux Enterprise Server 11 you most run minimum SLES 11 Service Pack 4.

Here is a quick and dirty how to upgrade your SLES 11 to SP4.
For more information please go to following link: https://www.suse.com/support/kb/doc/?id=7016711

Before you start upgrade anything, make sure you backup the ISP database/volhistory and device configuration.
After that make sure you stop the ISP Server and disable it so it can't start after a reboot.

Protect> Backup db devclass=dbclass type=full
Protect> Backup volhist file=/path/to/volhist_copy.out 
Protect> Backup devconfig file=/path/to/devconfig_copy.out

Upgrade to SLES 11 SP4


# chkconfig tsminst1 off
# zypper ref -s
# zypper update -t patch

If you have update your kernel, please reboot your server before continue.

# zypper se -t product | grep -h -- "-migration" | cut -d\| -f2
# zypper in -t product sle-sdk-SP4-migration SUSE_SLES-SP4-migration
# suse_register -d 2 -L /root/.suse_register.log
# zypper ref -s
# zypper lr ← See if any Library need to been disable
# zypper mr --disable SLES11-SP3-Pool as an example
# zypper dup --from SLES11-SP4-Pool --from SLES11-SP4-Updates

Reboot your server to make sure you start up the server on SLES 11 SP4.
Before you start the actual ISP upgrade, make sure ISP is working with the new kernel.
If you are using any tape drives such IBM lin_tape also make sure does are working before you continue.

Upgrade IBM Spectrum Protect from 7.1.x to 8.1.x

For more information you can always look at following link from IBM to read more about this upgrade.
http://www-01.ibm.com/support/docview.wss?uid=swg27018195
Login as root on your Linux system and create the instance.info file under /etc/tivoli/tsm

Add following information and the value is what's matching my environment so make sure you change the info so it match your system.

<Instance>
  <InstanceName>tsminst1</InstanceName>
  <InstanceUser>tsminst1</InstanceUser>
  <DefaultDatabasePath>/home/tsminst1/tsminst1</DefaultDatabasePath>
  <Database>
      <DatabaseName>TSMDB1</DatabaseName>
      <DatabasePath>/home/tsminst1/tsminst1</DatabasePath>
  </Database>
  <Variables>
      <Variable>DB2_SKIPINSERTED=ON</Variable>
      <Variable>DB2_KEEPTABLELOCK=ON</Variable>
     <Variable>DB2_EVALUNCOMMITTED=ON</Variable>
     <Variable>DB2_SKIPDELETED=ON</Variable>
     <Variable>DB2CODEPAGE=819</Variable>
     <Variable>DB2_PARALLEL_IO=*</Variable>
  </Variables>
</Instance>

Drop the database connection as root for tsminst1 
# /opt/tivoli/tsm/db2/instance/db2idrop tsminst1

Output: 
DBI1446I  The db2idrop command is running.
DB2 installation is being initialized.

Total number of tasks to be performed: 2
Total estimated time for all tasks to be performed: 305 second(s)

Task #1 start
Description: Initializing instance list
Estimated time 5 second(s)
Task #1 end

Task #2 start
Description: Configuring DB2 instances
Estimated time 300 second(s)
Task #2 end

The execution completed successfully.

For more information see the DB2 installation log at "/tmp/db2idrop.log.1234".
DBI1070I  Program db2idrop completed successfully.

Now let's start upgrading the ISP binary and run the installation software from ISP installation directory.

# ./install.sh -c

Follow the installation screen...

Preprocessing the input.
Loading repositories...
Preparing and resolving the selected packages...
...
...
...

=====> IBM Installation Manager> Update> Packages

Package group:  IBM Tivoli Storage Manager
Update packages:
     1-. [X] IBM Tivoli Storage Manager server 7.1.6.20160608_2027
       2. [X] Version 8.1.1.20170317_1452
     3-. [X] IBM Tivoli Storage Manager license 7.1.1.20140829_1109
       4. [X] Version 8.1.1.20170317_1443

Other Options:
    A. Show All
    R. Select Recommended

    B. Back,      N. Next,     C. Cancel
-----> [N]
Validating package prerequisites...

=====> IBM Installation Manager> Update> Packages> Summary

Target Location:
  Shared Resources Directory :  /opt/IBM/IBMIMShared
Update packages:
    1-. IBM Tivoli Storage Manager (/opt/tivoli/tsm)
       2. IBM Tivoli Storage Manager server 7.1.6.20160608_2027
       3. IBM Tivoli Storage Manager license 7.1.1.20140829_1109

Options:
    G. Generate an Update Response File

    B. Back,      U. Update,      C. Cancel
-----> [U]

                25%                50%                75%                100%
------------------|------------------|------------------|------------------|
............................................................................

=====> IBM Installation Manager> Update> Packages> Summary> Completion

The update completed successfully.
INFORMATION: To learn about best practices for configuring, monitoring, and operating an 

IBM Spectrum Protect solution, go to IBM Knowledge Center:
   http://www.ibm.com/support/knowledgecenter/SSEQVQ/landing/welcome_sseqvq.htm 

Search for IBM Spectrum Protect data protection solutions.

Options:
    F. Finish
-----> [F]

Recreate the Database Instance in DB2

/opt/tivoli/tsm/db2/instance/db2icrt -u tsminst1 tsminst1

Output:
DBI1446I  The db2icrt command is running.

DB2 installation is being initialized.

 Total number of tasks to be performed: 4
Total estimated time for all tasks to be performed: 309 second(s)

Task #1 start
Description: Setting default global profile registry variables
Estimated time 1 second(s)
Task #1 end

Task #2 start
Description: Initializing instance list
Estimated time 5 second(s)
Task #2 end

Task #3 start
Description: Configuring DB2 instances
Estimated time 300 second(s)
Task #3 end

Task #4 start
Description: Updating global profile registry
Estimated time 3 second(s)
Task #4 end

The execution completed successfully.

For more information see the DB2 installation log at "/tmp/db2icrt.log.4321
DBI1070I  Program db2icrt completed successfully.

Login as your ISP Instance owner

 # su - tsminst1

Set DB2 Value as user tsminst1 
/opt/tivoli/tsm/db2/adm/db2set -i tsminst1 "DB2_SKIPINSERTED=ON"
/opt/tivoli/tsm/db2/adm/db2set -i tsminst1 "DB2_KEEPTABLELOCK=ON"
/opt/tivoli/tsm/db2/adm/db2set -i tsminst1 "DB2_EVALUNCOMMITTED=ON"
/opt/tivoli/tsm/db2/adm/db2set -i tsminst1 "DB2_SKIPDELETED=ON"
/opt/tivoli/tsm/db2/adm/db2set -i tsminst1 "DB2CODEPAGE=819"
/opt/tivoli/tsm/db2/adm/db2set -i tsminst1 "DB2_PARALLEL_IO=*"

Add following info to /home/tsminst1/sqllib/userprofile
DSMI_CONFIG=/home/tsminst1/tsminst1/tsmdbmgr.opt
DSMI_DIR=/opt/tivoli/tsm/server/bin/dbbkapi
DSMI_LOG=/home/tsminst1/tsminst1
LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export DSMI_CONFIG DSMI_DIR DSMI_LOG LD_LIBRARY_PATH

Now do you need to start the DB2 Server to be able to upgrade the database for instance TSMDB1
# db2start

Catalog the old 7.1.6 Database
# db2 catalog db tsmdb1 on /home/tsminst1/tsminst1

If you got following error as below, you have specify the wrong directory, please type the path where the ISP Instance Directory are located. 
NOTE: # db2 catalog db tsmdb1 on /home/tsminst1
SQL6028N  Catalog database failed because database "tsmdb1" was not found in
the local database directory.

Now let's upgrade the Database

# db2 upgrade db tsmdb1
DB20000I  The UPGRADE DATABASE command completed successfully.

Now is the upgrade done and we need to stop the DB2 Server and start the ISP Server as a service again

# db2stop
SQL1064N  DB2STOP processing was successful.

Now can you start the IBM Spectrum Protect Server and will now start up with the upgraded version.

/etc/init.d/tsminst1 start

When your IBM Spectrum Protect Server has started, you need to register the license again, backup the database (as always), backup volume histroy/device configuration file and enable all sessions again.
Protect> Register licence file=*.lic
Protect> Backup db devclass=dbclass type=full wait=yes
Protect> Backup volhist file=/path/to/file.out
Protect> Backup devconfig file=/path/to/file.out
Protect> Enable sessan all

If you got following error when you backup your ISP Database after a upgrade, make sure your userprofile is configured correct.
ANR2984E Database backup terminated due to environment or setup issue related to

 DSMI_CONFIG - DB2 sqlcode -2033 sqlerrmc 406

You can verify if the parameter is correct by using following commands.

# su - tsminst1
# echo $DSMI_CONFIG
# echo $DSMI_DIR
# echo $DSMI_LOG
# cat $DSMI_CONFIG
# cat /home/tsminst1/sqllib/userprofile


Good luck and I hope this help.

Comments

Post a Comment

Popular posts from this blog

Move a Spectrum Scale Filesystem to an new disk

Very few time but it's happened that you need to move a filesystem from one Disk system to another Disk system in IBM Spectrum Scale (GPFS). And here is a little how to how to move a filesystem from one disk to another. Basic overview ·         Create the new disks in Linux ·         Create a NSD on the new disks ·         Add the new NSD to the file system ·         Remove the old NSDs and let Spectrum Scale to migrate the data automatic. ·         Delete the NSDs ·         Delete the Disks in Linux So let's start with Scanning the SCSI bus for new Disks on all NSD Servers [root@server01~] echo "- - -" > /sys/class/scsi_host/hostX/scan    Replace the X with the correct SCSI Host adapter. Create a NSD Stanza file...
Read more

Upgrade GPFS 3.4 to Spectrum Scale 4.1.1

It's funny because it's true…. That´s how I want to start with today's story… And today will I be more technical then normally. Let's start from beginning before I complain too much and showing how easy it is. I have now heard twice where end-users of GPFS heard it isn't possible to upgrade from GPFS 3.4 filesystem to Spectrum Scale 4.x without to shut down the entire cluster. This is not true and I will now show it for you how easy it is and how it's works.  I want with today's topic explain how easy it is to upgrade a GPFS 3.4 filesystem to Spectrum Scale 4.1.1 without to shut down the cluster. This how my test system looks like and see the time stamp when I start with my upgrade. [root@gpfs1 gpfs]# date Tue Jul 28 14:52:21 CEST 2015 [root@gpfs1 src]# mmlscluster GPFS cluster information ========================   GPFS cluster name:         gpfstest.cristie.se   GPFS cluster ...
Read more