Scenario 3, manual: Creating the directories and the user ID for the upgraded server instance

Create the directories that the server instance needs for database and recovery logs, and create the user ID that will own the server instance.

1. Create the user ID that will own the server instance. You use this user ID when you create the server instance in a later step.

   

   Create a user ID and group that will be the owner of the Tivoli® Storage Manager server instance.

   1. Create the user ID and group.
      Restriction: In the user ID, only lowercase letters (a-z), numerals (0-9), and the underscore character (_) can be used. The user ID and group name must comply with the following rules:

      • The length must be 8 characters or less.
      • The user ID and group name cannot start with ibm, sql, sys, or a numeral.
      • The user ID and group name cannot be user, admin, guest, public, local, or any SQL reserved word.

      For example, create user ID tsminst1 in group tsmsrvrs. The following examples show how to create this user ID and group by using operating system commands:

      

      # mkgroup id=1001 tsmsrvrs
      # mkuser id=1002 pgrp=tsmsrvrs home=/home/tsminst1 tsminst1
      # passwd tsminst1

      

      # groupadd tsmsrvrs
      # useradd -d /home/tsminst1 -m -g tsmsrvrs 
          -s /bin/ksh tsminst1
      # passwd tsminst1

      

      # groupadd tsmsrvrs
      # useradd -d /home/tsminst1 -m -g tsmsrvrs -s /bin/bash tsminst1
      # passwd tsminst1

      

      # groupadd tsmsrvrs
      # useradd -d /export/home/tsminst1 -m -g tsmsrvrs 
           -s /bin/ksh tsminst1
      # passwd tsminst1

   2. Log out and then log in to your system by using the new user ID and password. Use an interactive login program, such as telnet, so that you are prompted for the password and can change it if necessary.
   3. If a configuration profile does not exist for the user ID, create the file. For example, create a .profile file if you are using the Korn shell (ksh).

   

   Identify the user account that will own the Tivoli Storage Manager server instance. When the server is started as a Windows service, this is the account that the service will log on to. The user account must have administrative authority on the system. One user account can own more than one server instance.

   You can create a user account, or use an existing account.

   If you have multiple servers on one system and want to run each server with a different user account, create a user account in this step.

   1. Create the user ID.
      Restriction: The user ID can contain only lowercase letters (a-z), numerals (0-9), and the underscore character (_). The user ID must be 30 characters or less, and cannot start with ibm, sql, sys, or a numeral. The user ID and group name cannot be user, admin, guest, public, local, or any SQL reserved word.
      Use the following command to create the user ID:

      net user user_ID * /add

      You are prompted to create and verify a password for the new user ID.
   2. Issue the following operating system commands to add the new user ID to the Administrators groups:

      net localgroup Administrators user_ID /add
      net localgroup DB2ADMNS user_ID /add

   3. Log in to your system, by using the new user ID and password.
   4. For all directories that were created for the server instance, ensure that the user ID for the server instance has read/write access. The directories to check include the instance directory and all database and log directories.

2. Create the directories that the server requires. Ensure that you are logged in under the new user ID that you created.

   You need a unique, empty directory for each item in the following table. Create the database directories, the active log directory, and the archive log directory on different physical volumes. For space requirements, see Worksheet for planning space for the V7.1 server.

   

   Table 1. Worksheet for creating required directories

   Item	Example commands for creating the directories	Your directories
   The instance directory for the server, which will contain files for this server instance, including the server options file	mkdir /home/user_ID/tsminst1
   The database directories	mkdir /home/user_ID/tsmdb001 mkdir /home/user_ID/tsmdb002 mkdir /home/user_ID/tsmdb003 mkdir /home/user_ID/tsmdb004
   Active log directory	mkdir /home/user_ID/tsmlog
   Archive log directory	mkdir /home/user_ID/tsmarchlog
   Optional: Directory for the log mirror for the active log	mkdir /home/user_ID/tsmlogmirror
   Optional: Secondary archive log directory, which is the failover location for the archive log	mkdir /home/user_ID/tsmarchlogfailover

   

   Table 2. Worksheet for creating required directories

   Item	Example commands for creating the directories	Your directories
   The instance directory for the server, which will contain files for this server instance, including the server options file	mkdir d:\tsm\server1
   The database directories	mkdir d:\tsm\db001 mkdir e:\tsm\db002 mkdir f:\tsm\db003 mkdir g:\tsm\db004
   Active log directory	mkdir h:\tsm\log
   Archive log directory	mkdir i:\tsm\archlog
   Optional: Directory for the log mirror for the active log	mkdir j:\tsm\logmirror
   Optional: Secondary archive log directory, which is the failover location for the archive log	mkdir k:\tsm\archlogfailover

   When a server is initially created by using the DSMSERV FORMAT utility or the configuration wizard, a server database and recovery log are created. In addition, files are created to hold database information that is used by the database manager.

3. Create additional logical volumes and mount the volumes on the directories that were created in the previous step.