Preparing the system

To prepare the system for the upgrade from V6.2 or V6.3 to V7.1.3, you must gather information about each DB2® instance. Then, back up the server database, save key configuration files, cancel sessions, and stop the server.

Procedure

Log on to the computer where Tivoli® Storage Manager is installed.
Ensure that you are logged on with the instance user ID.

Ensure that you are logged on with the administrative user ID that was used to install the V6.2 or V6.3 server.
Obtain a list of DB2 instances. Issue the following system command:
```
/opt/tivoli/tsm/db2/instance/db2ilist
```
```
db2ilist
```
The output might be similar to the following example:
```
tsminst1
```
```
SERVER1
```
Ensure that each instance corresponds to a server that is running on the system.

For each DB2 instance, note the default database path, actual database path, database name, database alias, and any DB2 variables that are configured for the instance. Keep the record for future reference. This information is required to restore the V6 database.

Obtain the default database path of the DB2 instance by issuing the following system command:
```
. ~/sqllib/db2profile; LC_ALL=C db2 get dbm cfg | grep DFTDBPATH
```
The output might be similar to the following example:
```
Default database path               (DFTDBPATH) = /tsminst1/tsminst1
```
Tip: If you are upgrading the server from V6.3, the default database path is /tsminst1/tsminst1. If you are upgrading the server from V6.2, the default database path is /home/tsminst1/tsminst1.

Obtain information about the DB2 instance databases by issuing the following system command:

. ~/sqllib/db2profile; LC_ALL=C db2 list database directory

The output might be similar to the following example:

System Database Directory

 Number of entries in the directory = 2

Database 1 entry:

 Database alias                       = TSMAL001
 Database name                        = TSMDB1
 Node name                            = TSMNODE1
 Database release level               = d.00
 Comment                              = TSM SERVER DATABASE VIA TCPIP
 Directory entry type                 = Remote
 Catalog database partition number    = -1
 Alternate server hostname            =
 Alternate server port number         =

Database 2 entry:

 Database alias                       = TSMDB1
 Database name                        = TSMDB1
 Local database directory             = /tsminst1/tsminst1
 Database release level               = d.00
 Comment                              = TSM SERVER DATABASE
 Directory entry type                 = Indirect
 Catalog database partition number    = 0
 Alternate server hostname            =
 Alternate server port number         =

Obtain the DB2 instance variables by issuing the following system command:

. ~/sqllib/db2profile; LC_ALL=C db2set -all

The output might be similar to the following example:

[i] DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:500
[i] DB2_SKIPINSERTED=ON
[i] DB2_KEEPTABLELOCK=OFF
[i] DB2_EVALUNCOMMITTED=ON
[i] DB2_SKIPDELETED=ON
[i] DB2COMM=TCPIP
[i] DB2CODEPAGE=819
[i] DB2_PARALLEL_IO=*
[g] DB2FCMCOMM=TCPIP6
[g] DB2INSTDEF=tsminst1inst

Obtain more DB2 instance information by saving the following files:
- ~/sqllib/userprofile
- ~/sqllib/usercshrc
For example, issue the following system commands:
```
cp ~/sqllib/userprofile copy_location
```
```
cp ~/sqllib/usercshrc copy_location
```
where copy_location is the location where the copied file is saved.
The file content might be similar to the following example:
```
setenv DSMI_CONFIG /tsminst1/tsminst1/tsmdbmgr.opt
setenv DSMI_DIR /opt/tivoli/tsm/client/bin64
setenv DSMI_LOG /tsminst1/tsminst1
setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
```

Gather information about each DB2 instance. Note the default database path, actual database path, database name, database alias, and any DB2 variables that are configured for the instance. Keep the record for future reference. This information is required to restore the V6 database.

Open the DB2 command window by issuing the following system command:
```
db2cmd
```
To change the instance, issue the following system command:
```
set DB2INSTANCE=instance
```
where instance specifies the DB2 instance.
Obtain the default database path for the DB2 instance by issuing the following system command:
```
db2 get dbm cfg | findstr DFTDBPATH
```
The output might be similar to the following example:
```
Default database path                       (DFTDBPATH) = D:
```

Obtain information about the DB2 instance databases by issuing the following system command:

db2 list database directory

The output might be similar to the following example:

System Database Directory

		 Number of entries in the directory = 2

		Database 1 entry:

		 Database alias                       = TSMAL001
		 Database name                        = TSMDB1
		 Node name                            = TSMNODE1
		 Database release level               = d.00
		 Comment                              = TSM SERVER DATABASE VIA TCPIP
		 Directory entry type                 = Remote
 		 Catalog database partition number    = -1
		 Alternate server hostname            =
		 Alternate server port number         =

		Database 2 entry:

		 Database alias                       = TSMDB1
		 Database name                        = TSMDB1
		 Local database directory             = D:
		 Database release level               = d.00
		 Comment                              =
		 Directory entry type                 = Indirect
		 Catalog database partition number    = 0
		 Alternate server hostname            =
		 Alternate server port number         =

Obtain the DB2 instance variables by issuing the following system command:

db2set -all

The output might be similar to the following example:

		[e] DB2CODEPAGE=1208
		[e] DB2PATH=D:\TSM\db2
		[i] DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:500
		[i] DB2_SKIPINSERTED=ON
		[i] DB2_KEEPTABLELOCK=OFF
		[i] DB2_EVALUNCOMMITTED=ON
		[i] DB2_VENDOR_INI=D:\Server1\tsmdbmgr.env
		[i] DB2_SKIPDELETED=ON
		[i] DB2INSTPROF=C:\ProgramData\IBM\DB2\DB2TSM1
		[i] DB2COMM=TCPIP
		[i] DB2CODEPAGE=819
		[i] DB2_PARALLEL_IO=*
		[g] DB2_EXTSECURITY=YES
		[g] DB2_COMMON_APP_DATA_PATH=C:\ProgramData
		[g] DB2PATH=D:\TSM\db2
		[g] DB2INSTDEF=SERVER1

Connect to the Tivoli Storage Manager server by using an administrative user ID.
Back up the Tivoli Storage Manager database by using the BACKUP DB command. The preferred method is to create a snapshot backup, which is a full database backup that does not interrupt scheduled database backups. For example, you can create a snapshot backup by issuing the following command:
```
backup db type=dbsnapshot devclass=tapeclass
```
Back up the device configuration information to another directory by issuing the following Tivoli Storage Manager administrative command:
```
backup devconfig filenames=file_name
```
where file_name specifies the name of the file in which to store device configuration information.
Tip: If you decide to restore the V6 database, this file is required.
Back up the volume history file to another directory. Issue the following Tivoli Storage Manager administrative command:
```
backup volhistory filenames=file_name
```
where file_name specifies the name of the file in which to store the volume history information.
Tip: If you decide to restore the V6 database, this file is required.
Save a copy of the server options file, which is typically named dsmserv.opt. The file is in the server instance directory.
Prevent activity on the server by disabling new sessions. Issue the following Tivoli Storage Manager administrative commands:
```
disable sessions client
disable sessions server
```
Verify whether any sessions exist, and notify the users that the server will be stopped. To check for existing sessions, issue the following Tivoli Storage Manager administrative command:
```
query session
```
Cancel sessions by issuing the following Tivoli Storage Manager administrative command:
```
cancel session all
```
This command cancels all sessions except for your current session.
Stop the server by issuing the following Tivoli Storage Manager administrative command:
```
halt
```
Verify that the server is shut down and no processes are running.
Issue the following command:
```
ps -ef | grep dsmserv
```
Open the Windows Task Manager application and review the list of active processes.
In the server instance directory of your installation, locate the NODELOCK file and move it to another directory, where you are saving configuration files. The NODELOCK file contains the previous licensing information for your installation. This licensing information is replaced when the upgrade is complete.