IBM Tivoli Storage Manager, Version 7.1

Scenario 1: Creating and formatting the new database

Create the server instance and format files for an empty V7.1 database.

Procedure

Log on to the system where you installed the V7.1 program.
Log in by using the root user ID. Verify the following items:
- The home directory for the user, /home/tsminst1, exists. If there is no home directory, you must create it.
  The instance directory stores the following core files that are generated by the Tivoli® Storage Manager server:
  The server options file, dsmserv.opt
  
  The server key database file, cert.kdb, and the .arm files, which are used by clients and other servers to import the Secure Sockets Layer certificates of the server
  
  Device configuration file, if the DEVCONFIG server option does not specify a fully qualified name
  
  Volume history file, if the VOLUMEHISTORY server option does not specify a fully qualified name
  
  Volumes for DEVTYPE=FILE storage pools, if the directory for the device class is not fully specified, or not fully qualified
  
  User exits
  
  Trace output, if it is not fully qualified
- A shell configuration file, for example, .profile, exists in the home directory. The root user and instance user ID must have write permission to this file. For more information, go to the DB2® Information Center (http://pic.dhe.ibm.com/infocenter/db2luw/v10r5), and search for information about Linux and UNIX environment variable settings.
Log on as an administrator.
Create a Tivoli Storage Manager instance by using the db2icrt command.
Enter the following command on one line. For the instance name, specify the user ID that you created to own the instance:
```
/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u 
instance_name instance_name
```
For example, if the user ID for this instance is tsminst1, use the following command to create the instance:
```
/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u 
tsminst1 tsminst1
```
Remember: From this point on, use this new user ID when you configure the Tivoli Storage Manager server. Log out of the root user ID, and log in using the user ID that is the instance owner.
Enter the following command on one line. The user account that you specify becomes the user ID that owns the V7.1 server; this ID is the instance user ID.
```
db2icrt -s ese -u user_account instance_name
```
For example, if the user account is tsminst1 and the server instance is Server1, enter the following command:
```
db2icrt -s ese -u tsminst1 server1
```
The database service for the server instance logs on to the user account that is specified in this command.
Use the registry key name of the V5 server as the instance name for the V7.1 server. You are prompted to enter the password for the user account.

The instance name that you specify on this db2icrt command is the name that you later specify with the -k option on the DSMSERV LOADFORMAT command, when you create and format the database and recovery log.
Log on to the system by using the user ID that owns the V7.1 server instance (the instance user ID).
Copy the configuration files to the instance directory that you created for the new server. The files are the configuration files that you saved from the original V5 server:
- Device configuration
- Server options file, which is typically named dsmserv.opt
For example, if you created the instance directory that is shown in the example in the step to create directories for the V7.1 server, copy the files into the following directory:
- /tsminst1
- d:\tsm\server1
Ensure that the user ID that owns the V7.1 server (the instance user ID) has ownership or read/write permission to the files that you copied.
Edit the server options file.
1. Remove any options that are not supported for V7.1. For the list of deleted options, see Table 3.
2. Verify that the server options file contains at least one VOLUMEHISTORY option and at least one DEVCONFIG option. By specifying these options, you ensure that a volume history file and a device configuration file are generated and updated automatically. If you must restore the database, these files are required.
3. Check whether the server options file includes the TXNGROUPMAX option with a value, and if it does, what the value is. You might want to change the current value because the default value for this option changed from 256 to 4096, starting in V6. The increased value can improve the performance for data movement operations such as storage pool migration and storage pool backup.
  - If the server options file does not include this option, the server automatically uses the new default value of 4096.
  - If the server options file includes a value for this option, the server uses that specified value. If the specified value is less than 4096, consider increasing the value, or removing the option so that the new default value is applied.
Change the default path for the database.
Change the default path for the database to be the same as the instance directory for the server. Issue the command:
```
db2 update dbm cfg using dftdbpath instance_directory
```
For example:
```
db2 update dbm cfg using dftdbpath /tsminst1
```
Change the default path for the database to be the drive where the instance directory for the server is located. Complete the following steps:
1. Click Start > Programs > IBM DB2 > DB2TSM1 > Command Line Tools > Command Line Processor.
2. Enter quit to exit the command line processor.
  A window with a command prompt opens, with the environment correctly set up to successfully issue the commands in the next steps.
3. From the command prompt in that window, issue the following command to set the environment variable for the server instance that you are working with:
```
set db2instance=instance_name
```
  The instance_name is the same as the instance name that you specified when you issued the db2icrt command. For example, to set the environment variable for the Server1 server instance, issue the following command:
```
set db2instance=server1
```
4. Issue the command to set the default drive:
```
db2 update dbm cfg using dftdbpath instance_location
```
  For example, if the instance directory is d:\tsm\server1, the instance location is drive d:. Enter the command:
```
db2 update dbm cfg using dftdbpath d:
```
Modify the library path to use the version of the IBM® Global Security Kit (GSKit) that is installed with the Tivoli Storage Manager server:
Issue the following command:
```
export LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
```
You must update the following files to set the library path when DB2 or the Tivoli Storage Manager server is started:
- instance_directory/sqllib/usercshrc
- instance_directory/sqllib/userprofile
For the instance_directory/sqllib/usercshrc file, add the following lines:
- ```
setenv LIBPATH /usr/opt/ibm/gsk8_64/lib64:$LIBPATH
```
- ```
setenv LD_LIBRARY_PATH /opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
```
- ```
setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
```
For the instance_directory/sqllib/userprofile file, add the following lines:
- ```
LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
export LIBPATH
```
- ```
LD_LIBRARY_PATH=/opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
```
- ```
LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
```
Verify the library path settings and ensure that the GSKit version is 8.0.14.14 or later. Issue the following commands:
- ```
echo $LIBPATH
gsk8capicmd_64 -version
gsk8ver_64
```
- ```
echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64
```
If the GSKit version is not 8.0.14.14 or later, you must reinstall the Tivoli Storage Manager server. The reinstallation ensures that the correct GSKit version is available.
Change to the instance directory that you created for the server.
Create and format the database and recovery logs. In the command, specify the directories that you created for the database and logs. The directories must be empty.
For example, to get an active log size of 16 GB (16384 MB, the default size), issue the following command, on one line:
```
/opt/tivoli/tsm/server/bin/dsmserv loadformat \
dbdir=/tsmdb001,/tsmdb002,/tsmdb003,/tsmdb004 \ 
activelogsize=16384 activelogdirectory=/tsmlog \
mirrorlogdirectory=/tsmlogmirror archlogdirectory=/tsmarchlog
```
For example, to get an active log size of 16 GB (16384 MB, the default size) for the Server1 server instance, issue the following command, on one line:
```
"c:\Program Files\Tivoli\TSM\server\dsmserv" loadformat
dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log 
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog
```
If the server that you are upgrading is not Server1, you must use the -k option. The -k option specifies the instance name for running this utility. For example, if the system has more than one server instance and the instance that you are upgrading is Server2, issue the command:
```
"c:\Program Files\Tivoli\TSM\server\dsmserv" -k server2
loadformat dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log 
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog
```
Important: The server instance that you specify must have already been through all preceding steps for the upgrade process, including the creation of the database instance (db2icrt command).
Monitor the process for errors and warning messages. The final message indicates success or failure of the operation.

Feedback