Migration scenario 2: Creating the server instance and database

Create the server instance and format files for an empty V7.1.1 database. Later, you can migrate data from the V5 server database to the new V7.1.1 database.

Procedure

Log in to the system where you installed the V7.1.1 program by using the root user ID.
Verify the following items:
- The home directory for the user, for example, /home/tsminst1, exists. If the user's home directory does not exist, 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, other servers, and the Operations Center to import the Secure Sockets Layer certificates of the server
  - The device configuration file, if the DEVCONFIG server option does not specify a fully qualified name
  - The volume history file, if the VOLUMEHISTORY server option does not specify a fully qualified name
  - Volumes for storage pools of the FILE device type, if the directory for the device class is not fully qualified
  - User exits
  - Trace output, if it is not fully qualified
- A shell configuration file, for example, a .profile file, 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® documentation and search for information about Linux and UNIX environment variable settings.
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 
user_id 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 by using the user ID that is the instance owner.
Log in to the system by using the user ID that owns the V7.1.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:
- The device configuration file
- The 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, copy the files into the following directory:
- /tsminst1
Ensure that 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.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. Verify that 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, 4096.
  - If the specified value is less than 4096, consider increasing the value, or removing the option so that, when the server is restarted, the new default value is applied.
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
```
Modify the library path to use the version of the IBM® Global Security Kit (GSKit) that is installed with the Tivoli Storage Manager server.
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 line:
```
setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
```
For the instance_directory/sqllib/userprofile file, add the following lines:
```
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.43 or later. Issue the following commands from the instance home directory, for example, /home/tsminst1:
```
echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64
```
If the GSKit version is not 8.0.14.43 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 by using the DSMSERV LOADFORMAT command. 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 or 16384 MB, which is 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 more information about creating and formatting a database, see DSMSERV LOADFORMAT (Format a database).
Monitor the process for errors and warning messages. The final message indicates the success or failure of the operation.