Scenario 1: Creating the directories and the user ID for the upgraded server instance

http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/topic/com.ibm.itsm.srv.upgrd.doc/t_sr...

IBM Tivoli Storage Manager servers > Installing and upgrading the server > Upgrading the server from V5 to V6.3 or later > Scenario 1: Same system, media method
IBM Tivoli Storage Manager, Version 6.3.3

Scenario 1: 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. Review the information about planning space for the server before you complete this task. See Worksheet for planning space for the V6.3 or later server. 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. a. 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 b. Log off, 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. c. 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. a. Create the user ID. Restriction: The user ID can contain only lowercase letters (a-z), numerals (0-9), and the underscore character (_). The

1 of 3

5/8/2013 11:49 AM

Scenario 1: Creating the directories and the user ID for the upgraded server instance

http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/topic/com.ibm.itsm.srv.upgrd.doc/t_sr...

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. b. Issue the following commands to add the new user ID to the DB2 and Administrators groups: net localgroup Administrators user_ID /add net localgroup DB2ADMNS user_ID /add net localgroup DB2USERS user_ID /add c. Log in to your system, by using the new user ID and password. d. 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 unique, empty directories for each of the items that are shown 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 V6.3 or later server.

Table 1. Worksheet for creating required directories Example commands for creating Item the directories The instance directory for the server, which will contain files for this server instance, including the server options file The database directories mkdir /home/user_ID /tsminst1

Your directories

mkdir /home/user_ID /tsmdb001 mkdir /home/user_ID /tsmdb002 mkdir /home/user_ID /tsmdb003 mkdir /home/user_ID /tsmdb004 mkdir /home/user_ID/tsmlog mkdir /home/user_ID /tsmarchlog mkdir /home/user_ID /tsmlogmirror mkdir /home/user_ID /tsmarchlogfailover

Active log directory Archive log directory Optional: Directory for the log mirror for the active log Optional: Secondary archive log directory, which is the failover location for the archive log

Table 2. Worksheet for creating required directories Example commands for creating Item the directories The instance directory for the server, which will contain files for this server instance, including the server options file The database directories mkdir d:\tsm\server1

Your directories

mkdir mkdir mkdir mkdir

d:\tsm\db001 e:\tsm\db002 f:\tsm\db003 g:\tsm\db004

Active log directory Archive log directory Optional: Directory for the log mirror for the active log Optional: Secondary archive log directory, which is the failover location for the archive log

mkdir h:\tsm\log mkdir i:\tsm\archlog mkdir j:\tsm\logmirror mkdir k:\tsm \archlogfailover

When a server is initially created, with the DSMSERV FORMAT utility or with the configuration wizard, a server database and

2 of 3

5/8/2013 11:49 AM

Scenario 1: Creating the directories and the user ID for the upgraded server instance

http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/topic/com.ibm.itsm.srv.upgrd.doc/t_sr...

recovery log are created. In addition, files are created to hold database information used by the database manager. 3. Create additional logical volumes and mount the volumes on the directories that were created in the previous step. Continue the upgrade process by using one of the following topics: Scenario 1: Upgrading the server by using the upgrade wizard Scenario 1: Upgrading the server manually by using utilities Parent topic: Scenario 1: Same system, media method Related tasks: Planning space for the upgrade process and the upgraded server Related reference: Server naming best practices

Feedback

3 of 3

5/8/2013 11:49 AM