1

Installing Tivoli Storage Manager 6.3 Server

Components
Step1: Go to the directory where you have extracted the directory and run the install.bin file as
shown below.

Step 2: Select the language number you want and and press enter as shown below, default is
ENGLISH

Step 3: Choose the product you want to install, here we have selected Tivoli Storage Manager
Extended Edition.

Step 4: Choose if you want to use LANFree Operations on your TSM Server.

Step 5: Press 1 to view the licenses and accept the licenses

Step 6 : Select components to install. and press enter. You can select multiple components by
using comma(,) as shown below. Then the deployment engine starts and continues for 5-10
minutes.

Step 7: Choose appropriate option here relevant to your setup.

After few minutes the console should show the completion of TSM Installation as below.

Step 8 : Now, we have to check if all the required software is installed by using lslpp -l command
as shown below. Here we can see that all the TSM Server components are successfully
installed.

How to create TSM DB, log and DB2 user directories ?

Create the user ID for the Tivoli Storage Manager server instance and create the directories that
the Tivoli Storage Manager server instance needs for database and recovery logs.
Before configuring TSM 6.3 Server instance on AIX, you have to run TSM 6.3 Prerequisite
Checker and Install TSM 6.3 Server code. You should also install Atape Device Drivers to use
the tape devices
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.

Step 1: Use below commands to create TSM Server Group and TSM User
mkgroup id=1001 tsmsrvrs
mkuser id=1002 pgrp=tsmsrvrs home=/home/tsminst1 tsminst1
passwd tsminst1
Step 2: Create directories that the server requires. Ensure that you are logged in under the new
user ID you just created. Check the below screenshots to know how to do this.
mkdir /tsminst1
mkdir /home/user_ID/tsmdb001
mkdir /home/user_ID/tsmdb002
mkdir /home/user_ID/tsmlog
mkdir /home/user_ID/tsmarchlog
mkdir /home/user_ID/tsmlogmirror
mkdir /home/user_ID/tsmarchlogfailover

Step 3: Make sure that the TSMuser is the owner of the TSMDB & TSM-LOGS and also have
Read/Write Permissions. To do this check this below screen shots. Use ls -ltr command to check
back.
chown -R user:group /directoryname
chmod -R 777 /directoryname

Configuring Tivoli Storage Manager 6.3 using the Configuration Wizard

(dsmicfgx):
After you have installed Tivoli Storage Manager Version 6.3 or later and prepared for the
configuration, configure the Tivoli Storage Manager server instance. You can Configure a Tivoli
Storage Manager server instance by selecting one of the following options:

Use the Tivoli Storage Manager configuration wizard (dsmicfgx) on your local system.

Use the Tivoli Storage Manager configuration wizard in the Administration Center.

Manually configure the new Tivoli Storage Manager instance.

In this post I will demonstrate how to configure using Tivoli Storage Manager configuration wizard
(dsmicfgx) which is also the best recommended method from the above three. This method is
same both in Windows and UNIX environment.

By using the graphical user interface (GUI), you can avoid some configuration steps that are
complex when done manually. Start the wizard on the system where you installed the Tivoli
Storage Manager server program.

Before beginning the configuration wizard, you must complete all preceding steps to prepare for
the configuration, including prerequisite checking, installing Tivoli Storage Manager, creating the
database and log directories, and creating the directories and user ID for the server instance.

Ensure that the following requirements are met:

The system where you installed Tivoli Storage Manager must have the X Window
System client. You must also be running an X Window System server on your desktop.

The system must have one of the following protocols enabled. Ensure hat the port that
the protocol uses is not blocked by a firewall.

Secure Shell (SSH). Ensure that the port is set to the default value, 22. Also ensure that
the SSH daemon service has access rights for connecting to the system by using
localhost.

Remote shell (RSH).

Remote Execution Protocol (REXEC).

You must be able to log in to Tivoli Storage Manager with the user ID that you created for
the server instance, by using the SSH, RSH, or REXEC protocol. When using the wizard,
you must provide this user ID and password to access that system.

Start the Configuration Wizard:

Open the dsmicfgx program in the /opt/tivoli/tsm/server/bin directory.

This wizard can only be run as a root user.

Follow the instructions to complete the configuration. The wizard can be stopped and
restarted, but the server is not operational until the entire configuration process is
complete.

In this post I have used Xmanager as the X window system client to graphically configure the
TSM Server on AIX from a windows machine. Xmanager is the leading PC X server in the market
that brings the power of X applications to a Windows environment. You can learn and download
Xmanager here.

Step 1: Login as root and go the installation directory /opt/tivoli/tsm/server/bin directory run the
dsmicfgx binary file. It will open a pop-up window, a GUI based configuration wizard as shown
below.

10

Step 2: Specify the user ID and password for the new TSM Instance and click NEXT. To know
how to create user ID and password for the new TSM Instance click here.

11

Step 3: Specify the new Instance directory where all the TSM Server configuration files will be
saved and click NEXT.

Step 4: Specify the TSM Database directories and click NEXT. You should create a file with list
of Database directories if you are choosing first option. To know how to create db & log
directories click here.

12

Step 5: Specify the TSM Active log directory, Archive log directory paths. Activemirror log and
Archivefailover log directories are optional but it is strongly recommended.

Step 6: Specify the TSM Server name which you want to use. Check TSM Server naming
conventions before taking server name decision to avoid silly annoying issues. Also select the
option when to start the TSM Instance after completion of this configuration setup.

13

Step 7: Specify the TSM Administrator name and password which is used to login into the TSM
Server.

Step 8: You dont have to change the default settings unless you have different options other than
specified below.

14

Step 9: Review the configuration summary and click NEXT.

Step 10: The TSM instance configuration will start now and it will undergo many steps. It will
approximately take 20-30 minutes to complete the configuration. You can see the steps on the
wizard screen.

15

Step 10: Now the wizard should say that configuration of TSM is successful as shown above.
Now click NEXT and click DONE.

The next step is to start the TSM Server Instance with the TSM Instance user ID:
Log in to the system where Tivoli Storage Manager is installed by using the instance user ID
which was created before.
Issue the following commands to start the TSM Server Instance
. /home/tsminst1/sqllib/db2profile
/opt/tivoli/tsm/server/bin/dsmserv
To start the server in the background, issue the following command
/opt/tivoli/tsm/server/bin/dsmserv -q &

MONITORING DB & LOG

1) You have to create and designate directories or drives that the server uses for the database
during TSM Server instance configuration. Afterward, the database manager, which is part of the
server, automatically manages the space available to the directories as database space.
2) Locate the database on fast reliable storage, such as Redundant Array of Independent Disks
(RAID) hardware. Do not place the database in directories that might run out of space. Locate
the directories across different physical devices (separate LUNs).
3) Database size is determined by the amount of data that you store. The Database Manager
manages the database space automatically. The maximum supported limit is 4 TB. Use the
QUERY DBSPACE command to monitor database space usage. The size of the database
depends on the following factors

The number of client files to store

The number of versions of backed up files that are kept

Whether you use caching

4) Caching option is available in the disk storage pool. When cache is enabled, the migration
process leaves behind duplicate copies of files after the server migrates these files to the next
storage pool in the hierarchy. Consider using Active Data Pools instead

5) There are both advantages and disadvantages of enabling cache on disk pools. You need to
cheese this option according to your resources. Using cache can improve the speed with which
the server retrieves some files. Consider enabling cache for space-managed files that clients
frequently access. If space is needed to store new data in the disk storage pool, cached files are
erased and the space is used for those new files.

16

Using cache can require more space for the server database because the server
maintains two copies of the file.

If you want to use caching, you cannot also enable shredding for that disk storage pool.

TSM Database size estimation:

The size of your Tivoli Storage Manager database depends on the number of client files to store
and how Tivoli Storage Manager manages them. If you can estimate the maximum number of
files that might be in server storage at any time, you can use the following information to come up
with a useful database size estimate

Each version of a file that Tivoli Storage Manager stores requires about 400 to 600 bytes
of database space.

Each cached or storage pool copy of a file requires about 100 to 200 bytes of database
space. Caching is turned off by default. It is used only to move from one storage pool to
next.

Overhead can increase the required space by an additional 50%.

Maximum and Minimum size allowed for Database and Recovery log
Database

Minimum size: 2.2 GB

Maximum size: 4 TB

Consider restore time when deciding how large the database should be.
Active log

Minimum size: 2 GB

Maximum size: 128 GB

Default size: 16 GB

Active log space requirements increase when you use data deduplication.
Archive log

Large enough to contain the logs that the previous full backup generates

Cleared only in the case of a full backup

Example for Database estimation

Backed up objects

17

50,000,000 objects might be backed up. Storage policies call for retaining up to three copies of
backed up files. 150,000,000 stored backed up objects.

Archived objects

10,000,000 objects might be archived copies of client files.

Space-managed objects

20,000,000 objects migrated from client workstations might be in server storage. [(50,000,000 X
3 ) + 10,000,000 + 20,000,000)] x 600 bytes = 100 GB

Copy storage pool objects - All primary storage pools are backed up to the copy
storage pool:

(150,000,000 + 10,000,000 + 20,000,000) x 200 bytes = 34.3 GB

Active-data pool objects - All the active client backup data in primary storage pools is
copied to the active-data pool.

Assume that 50,000,000 versions of the backup files in the primary storage pool are active.
50,000,000 x 200 bytes = 9.5 GB
Estimated database size: 144 GB + overhead (up to 50%) = approximate 216 GB
In the above example, the computations represent probable maximums. The numbers are not
based on the use of file aggregation. In general, the more that small files are aggregated, the
less database space that is required.
If you cannot estimate the numbers of files, you can roughly estimate the database size as 1% to
5% of the required server storage space. For example, if you need 1,000 GB of server storage,
make your database between 10 GB and 50 GB.

Increasing the TSM V7 Database Size

1) You can add directories to the database by using the EXTEND DBSPACE command. The
updates for this operation include distributing data across all database directories and the
reclaiming of unused space and returning it to the system. Because redistribution operations take
considerable system resources, plan ahead when you want to add space to the database. For
example
extend dbspace e:\tsm_db\dbs7 on Windows
extend dbspace /tsmdb/dbs7 on UNIX
The directories must be empty and accessible to the user ID of the database manager.
2) DSMSERV EXTEND DBSPACE, can be used to perform the same function as the EXTEND
DBSPACE command, while the server is offline.

18

3) You should run the EXTEND DBSPACE commands while the server is not handling a heavy
load.
4) You can also reduce or remove database directories if they are not required by using
REMOVE DB command

Increasing the TSM V7 Activelog size

If the log is running out of space, the current transaction is rolled back, and the server issues an
error message and halts. You cannot restart the server until you increase the active log size. If
you use the active log mirror, it will also increases to the new size. You can increase the size of
the active log by completing the following steps

Issue the DSMSERV DISPLAY LOG offline utility to verify the size of the active log.

In the dsmserv.opt file, update the ACTIVELOGSIZE server option to the new maximum
size of the active log. For example, to change the active log to 120 GB, enter the
following server option:
activelogsize 122880

If you want to use a new active log directory, update the directory name specified in the
ACTIVELOGDIR server option.

The changes take effect when you restart the server.

TSM Server options to monitor Database and Recovery log

1) You can use server options to control some aspects of database processing. They are
available during and after installation. The following database options are specified in the server
options file during installation:

ACTIVELOGDIR

ACTIVELOGSIZE

ARCHLOGDIR

ARCHFAILLOGDIR

MIRRORLOGDIR

DBMEMPERCENT

2) The ACTIVELOGDIR, ACTIVELOGSIZE, ARCHLOGDIR, ARCHFAILLOGDIR, and

MIRRORLOGDIR options control the location and size of the logs and mirrors. These options are
set during initial configuration.
3) DBMEMPERCENT is the percentage of system memory that is dedicated to the database. If
DBMEMPERCENT is not specified, the default is applied, which is 70% - 80%.

19

4) You can use server options to control how Tivoli Storage Manager groups and transfers
data. Several of these options pertain to the size of the transaction and you can use them for
improving performance. Group options include the following items.

MOVEBATCHSIZE: Specifies the number of files to move and group in a batch, within a
transaction (Default is 1000 files).

MOVESIZETHRESH: Specifies the threshold for the amount of data to move as a batch,
within the same server transaction (Default size is 4096 MB).

TXNGROUPMAX: Specifies the number of files to transfer as a group between a client

and the server between transaction commit points (Default is 4096 objects.)