IBM Tivoli Storage Manager

for AIX
Version 7.1.1

Installation Guide


IBM Tivoli Storage Manager
for AIX
Version 7.1.1

Installation Guide


 Note:
Before using this information and the product it supports, read the information in “Notices” on page 251.

Second edition (September 2014)

This edition applies to version 7, release 1, modification 1 of IBM Tivoli Storage Manager (product numbers
5608-E01, 5608-E02, 5608-E03), and to all subsequent releases and modifications until otherwise indicated in new
editions.
© Copyright IBM Corporation 1993, 2014.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this publication . . . . . . . . vii Configuring server options for server database
Who should read this guide . . . . . . . . . vii maintenance . . . . . . . . . . . . . . 53
Installable components . . . . . . . . . . vii Starting the server instance . . . . . . . . . 54
Publications . . . . . . . . . . . . . . ix Verifying access rights and user limits . . . . 55
Starting the server from the instance user ID . . 56
New for Tivoli Storage Manager Version Automatically starting servers . . . . . . . 57
Stopping the server . . . . . . . . . . . . 58
7.1.1 . . . . . . . . . . . . . . . . xi Registering licenses . . . . . . . . . . . . 58
Specifying a device class in preparation for database
Part 1. Installing and upgrading the backups . . . . . . . . . . . . . . . 59
server . . . . . . . . . . . . . . . 1 Running multiple server instances on a single
system . . . . . . . . . . . . . . . . 59
Monitoring the server . . . . . . . . . . . 60
Chapter 1. Planning to install the Tivoli
Storage Manager server . . . . . . . . 3 Chapter 4. Installing a Tivoli Storage
What you should know first . . . . . . . . . 3
Manager server fix pack . . . . . . . 63
System requirements for the Tivoli Storage Manager
Applying a fix pack to Tivoli Storage Manager V7 in
server. . . . . . . . . . . . . . . . . 4
a clustered environment . . . . . . . . . . 66
Compatibility of the Tivoli Storage Manager server
with other DB2 products on the system . . . . . 7
IBM Installation Manager . . . . . . . . . . 8 Chapter 5. Upgrading to Tivoli Storage
Worksheets for planning details for the Tivoli Storage Manager Version 7.1.1 . . . . . . . . 67
Manager server . . . . . . . . . . . . . 9 Upgrading from Tivoli Storage Manager V6.2 or
Capacity planning . . . . . . . . . . . . 10 V6.3 to V7.1.1. . . . . . . . . . . . . . 68
Estimating space requirements for the database 10 Planning the upgrade . . . . . . . . . . 69
Recovery log space requirements . . . . . . 13 Preparing the system . . . . . . . . . . 70
Monitoring space utilization for the database and Installing the V7.1.1 server and verifying the
recovery logs . . . . . . . . . . . . . 26 upgrade . . . . . . . . . . . . . . 72
Server naming best practices. . . . . . . . . 27 Upgrading from Tivoli Storage Manager V6.1 to
Installation directories . . . . . . . . . . . 29 V7.1.1 . . . . . . . . . . . . . . . . 76
Upgrading Tivoli Storage Manager in a clustered
Chapter 2. Installing the Tivoli Storage environment . . . . . . . . . . . . . . 76
Manager server components . . . . . 31 Upgrading Tivoli Storage Manager from V6.2 or
V6.3 to V7.1.1 in a clustered environment with a
Obtaining the Tivoli Storage Manager installation
shared database instance . . . . . . . . . 77
package . . . . . . . . . . . . . . . 31
Upgrading Tivoli Storage Manager from V6.2 or
Installing Tivoli Storage Manager by using the
V6.3 to V7.1.1 in a clustered environment with
installation wizard . . . . . . . . . . . . 32
separate database instances . . . . . . . . 79
Installing Prerequisite RPM files for the graphical
Upgrading Tivoli Storage Manager from V6.1 to
wizard . . . . . . . . . . . . . . . 34
V7.1.1 in a clustered environment . . . . . . 82
Installing Tivoli Storage Manager by using console
mode . . . . . . . . . . . . . . . . 35
Installing Tivoli Storage Manager in silent mode . . 36 Chapter 6. Reverting from Version 7.1
Installing server language packages . . . . . . 37 to the previous V6 server. . . . . . . 85
Server language locales . . . . . . . . . 38 Steps for reverting to the previous server version. . 85
Configuring a language package . . . . . . 39 Additional recovery steps if you created new
Updating a language package . . . . . . . 39 storage pools or enabled data deduplication . . . 86

Chapter 3. Taking the first steps after

you install Tivoli Storage Manager . . . 41
Creating the user ID and directories for the server
instance . . . . . . . . . . . . . . . 42
Configuring Tivoli Storage Manager . . . . . . 43
Configuring Tivoli Storage Manager using the
configuration wizard . . . . . . . . . . 44
Configuring the server instance manually . . . 44

© Copyright IBM Corp. 1993, 2014 iii

 Chapter 7. Reference: DB2 commands Configuring summarization and pruning
for Tivoli Storage Manager server settings . . . . . . . . . . . . . . 149
Manually configuring the Tivoli Enterprise
databases . . . . . . . . . . . . . 89
Portal server. . . . . . . . . . . . . 150
Manually configuring the Warehouse Proxy
Chapter 8. Uninstalling Tivoli Storage agent . . . . . . . . . . . . . . . 151
Manager . . . . . . . . . . . . . . 93 Manually configuring the Warehouse
Uninstalling Tivoli Storage Manager by using a Summarization and Pruning agent . . . . . 152
graphical wizard . . . . . . . . . . . . 93 | Managing secure communications . . . . . . 153
Uninstalling Tivoli Storage Manager in console | Disabling earlier Transport Layer Security
mode . . . . . . . . . . . . . . . . 94 | versions . . . . . . . . . . . . . . 153
Uninstalling Tivoli Storage Manager in silent mode 94 | Configuring Secure Sockets Layer
Uninstalling and reinstalling Tivoli Storage Manager 95 | communication . . . . . . . . . . . . 154
| Enabling the NIST SP800-131A security standard 158
Part 2. Installing and upgrading
Chapter 10. Upgrading Tivoli
Tivoli Monitoring for Tivoli Storage
Monitoring for Tivoli Storage Manager
Manager . . . . . . . . . . . . . 97
to Version 7.1 . . . . . . . . . . . 163
Upgrade scenarios. . . . . . . . . . . . 163
Chapter 9. Installing Tivoli Monitoring | Upgrading Tivoli Monitoring for Tivoli Storage
for Tivoli Storage Manager . . . . . . 99 | Manager from Version 6.3 to Version 7.1 . . . . 165
Planning to install . . . . . . . . . . . . 100 | Exporting IBM Tivoli Monitoring data . . . . 167
Installation scenarios . . . . . . . . . . 100 | Importing IBM Tivoli Monitoring data . . . . 169
System requirements for Tivoli Monitoring for | Saving the agent instance configurations . . . 170
Tivoli Storage Manager . . . . . . . . . 103 | Importing the agent instance configuration . . 171
| IBM Installation Manager . . . . . . . . 107 | AIX: Upgrading Tivoli Monitoring for Tivoli
Capacity planning . . . . . . . . . . . 108 | Storage Manager . . . . . . . . . . . . 172
Installation worksheet . . . . . . . . . 108 | AIX: Obtaining the Tivoli Monitoring for Tivoli
Installation checklist . . . . . . . . . . 110 | Storage Manager installation package . . . . 173
| Bypassing the prerequisites . . . . . . . . 111 | AIX: Upgrading Tivoli Monitoring for Tivoli
| AIX: Installing Tivoli Monitoring for Tivoli Storage | Storage Manager by using the Upgrade wizard . 174
| Manager . . . . . . . . . . . . . . . 112 | AIX: Upgrading Tivoli Monitoring for Tivoli
| AIX: Obtaining the Tivoli Monitoring for Tivoli | Storage Manager by using console mode . . . 176
| Storage Manager installation package . . . . 113 | AIX: Upgrading Tivoli Monitoring for Tivoli
| AIX: Installing Tivoli Monitoring for Tivoli | Storage Manager in silent mode . . . . . . 177
| Storage Manager by using the Install wizard . . 114 Upgrading the monitoring agent . . . . . . . 178
| AIX: Installing Tivoli Monitoring for Tivoli | Upgrading the operating system . . . . . . . 179
| Storage Manager by using console mode . . . 117
| AIX: Installing Tivoli Monitoring for Tivoli | Chapter 11. Migrating Tivoli
| Storage Manager in silent mode . . . . . . 118
| Monitoring for Tivoli Storage Manager
Installing the monitoring agent . . . . . . . 119
| Installing the monitoring agent on remote | from one system to another . . . . . 181
| servers . . . . . . . . . . . . . . 120 | Migrating Tivoli Monitoring for Tivoli Storage
AIX: Installing and deploying monitoring agents | Manager V6.3 to V7.1, or later on another system . 181
in an existing Tivoli Monitoring environment. . 122 | Migrating Tivoli Monitoring for Tivoli Storage
Creating and configuring the agent instance . . . 134 | Manager V7.1, or later to another system . . . . 182
Creating and configuring the monitoring agent
instance by using CandleManage . . . . . . 135 | Chapter 12. Uninstalling Tivoli
Creating and configuring the monitoring agent | Monitoring for Tivoli Storage Manager 183
instance by using the command-line interface . 138 | Uninstalling Jazz for Service Management . . . . 183
| Installing Jazz for Service Management . . . . . 141 | Uninstalling Tivoli Monitoring for Tivoli Storage
| Installing Jazz for Service Management on AIX | Manager by using IBM Installation Manager . . . 184
| and Linux . . . . . . . . . . . . . 141 | Uninstalling Tivoli Monitoring for Tivoli Storage
| Configuring the WAREHOUS data source and | Manager by using the Uninstall wizard. . . . 184
| importing reports . . . . . . . . . . . . 143 | Uninstalling Tivoli Monitoring for Tivoli Storage
| Starting the Jazz for Service Management service 144 | Manager by using console mode . . . . . . 185
Verifying the installation . . . . . . . . . 145 | Uninstalling Tivoli Monitoring for Tivoli Storage
Taking the first steps after installation . . . . . 147 | Manager by using silent mode . . . . . . 185
| Running a Cognos report . . . . . . . . . 149 | Uninstalling monitoring agents . . . . . . . 186
Configuring agents and services . . . . . . . 149

iv IBM Tivoli Storage Manager for AIX: Installation Guide

| Uninstalling monitoring agents by using IBM Starting and stopping the web server . . . . 224
| Installation Manager . . . . . . . . . . 186 | Collecting diagnostic information with Tivoli
| Uninstalling monitoring agents in an existing | Storage Manager client management services . . . 224
| IBM Tivoli Monitoring environment . . . . . 188 | Installing the client management service by
| using a graphical wizard . . . . . . . . 225
Part 3. Installing and upgrading | Installing the client management service in
| silent mode . . . . . . . . . . . . . 226
the Operations Center . . . . . . 191 | Verifying that the client management service is
| installed correctly . . . . . . . . . . . 227
Chapter 13. Planning to install the | Configuring the Operations Center to use the
Operations Center . . . . . . . . . 193 | client management service . . . . . . . . 228
System requirements for the Operations Center . . 193 | Starting and stopping the client management
Operations Center computer requirements. . . 194 | service. . . . . . . . . . . . . . . 229
Hub and spoke server requirements . . . . . 194 | Uninstalling the client management service . . 229
Operating system requirements . . . . . . 198 | Configuring the client management service for
Web browser requirements . . . . . . . . 198 | custom client installations . . . . . . . . 230
Language requirements . . . . . . . . . 199
| Requirements and limitations for Tivoli Storage Chapter 17. Troubleshooting the
| Manager client management services . . . . 199 Operations Center installation . . . . 239
Administrator IDs that the Operations Center Graphical installation wizard cannot be started on
requires . . . . . . . . . . . . . . . 201 an AIX system . . . . . . . . . . . . . 239
IBM Installation Manager . . . . . . . . . 202
Installation checklist . . . . . . . . . . . 202 Chapter 18. Uninstalling the
Operations Center . . . . . . . . . 241
Chapter 14. Installing the Operations Uninstalling the Operations Center by using a
Center . . . . . . . . . . . . . . 207 graphical wizard . . . . . . . . . . . . 241
Obtaining the Operations Center installation Uninstalling the Operations Center in console
package . . . . . . . . . . . . . . . 207 mode . . . . . . . . . . . . . . . . 241
Installing the Operations Center by using a Uninstalling the Operations Center in silent mode 242
graphical wizard . . . . . . . . . . . . 208
Installing RPM files for the graphical wizard 209 Chapter 19. Rolling back to a previous
Installing the Operations Center in console mode 209
Installing the Operations Center in silent mode . . 210
version of the Operations Center . . . 243

Chapter 15. Upgrading the Operations Part 4. Appendixes . . . . . . . . 245

Center . . . . . . . . . . . . . . 211
Appendix A. Installation log files . . . 247
Chapter 16. Getting started with the
Operations Center . . . . . . . . . 213 Appendix B. Accessibility features for
Configuring the Operations Center . . . . . . 213 the Tivoli Storage Manager product
Designating the hub server . . . . . . . . 214 family. . . . . . . . . . . . . . . 249
Adding a spoke server . . . . . . . . . 214
| Sending email alerts to administrators . . . . 215 Notices . . . . . . . . . . . . . . 251
| Adding customized text to the login screen . . 218
Trademarks . . . . . . . . . . . . . . 253
Configuring for SSL communication . . . . . . 218
Privacy policy considerations . . . . . . . . 253
Configuring for SSL communication between
the Operations Center and the hub server . . . 218
Configuring for SSL communication between Glossary . . . . . . . . . . . . . 255
the hub server and a spoke server . . . . . 221
Resetting the password for the Operations Index . . . . . . . . . . . . . . . 257
Center truststore file . . . . . . . . . . 223

Contents v
vi IBM Tivoli Storage Manager for AIX: Installation Guide
About this publication
This publication contains installation and configuration instructions for the IBM®
Tivoli® Storage Manager server, server languages, and other Tivoli Storage
Manager components.

Instructions for installing the Tivoli Storage Manager license, device driver, storage
agent, Tivoli Monitoring for Tivoli Storage Manager, and the IBM Tivoli Storage
Manager Operations Center are also included in this publication.

Who should read this guide

This publication is intended for a system administrator installing and configuring a
Version 7.1.1 Tivoli Storage Manager server, Tivoli Monitoring for Tivoli Storage
Manager, the Operations Center, or upgrading from Tivoli Storage Manager
Version 6.

If you are upgrading an existing 5.5.x Tivoli Storage Manager server to Tivoli
Storage Manager Version 7.1.1, see the Upgrade and Migration Guide for V5 Servers.

If you are upgrading a Tivoli Storage Manager Version 6.1, Version 6.2, or Version
6.3 server to a newer version, see Chapter 5, “Upgrading to Tivoli Storage Manager
Version 7.1.1,” on page 67.

If you are upgrading an existing Tivoli Storage Manager Version 7.1 server to a
later level of Version 7.1, see Chapter 4, “Installing a Tivoli Storage Manager server
fix pack,” on page 63.

If you are installing Tivoli Monitoring for Tivoli Storage Manager, see Chapter 9,
“Installing Tivoli Monitoring for Tivoli Storage Manager,” on page 99.

If you are upgrading Tivoli Monitoring for Tivoli Storage Manager, see Chapter 10,
“Upgrading Tivoli Monitoring for Tivoli Storage Manager to Version 7.1,” on page
163.

If you are installing or upgrading the Operations Center, see Part 3, “Installing and
upgrading the Operations Center,” on page 191.

Installable components
The IBM Tivoli Storage Manager server and licenses are required components.

You can install the following components for Tivoli Storage Manager V7.1 or later.
v Tivoli Storage Manager server
v Tivoli Storage Manager server languages
v Tivoli Storage Manager licenses
v Tivoli Storage Manager devices
v Tivoli Storage Manager storage agent
v Tivoli Storage Manager Operations Center
v Tivoli Monitoring for Tivoli Storage Manager

© Copyright IBM Corp. 1993, 2014 vii

 Tivoli Monitoring for Tivoli Storage Manager must not be installed on any system
that contains a Tivoli Storage Manager server instance.

Table 1 describes all the installable components. These components are in several
different installation packages.
Table 1. Tivoli Storage Manager installable components
Tivoli Storage Description Additional information
Manager component
Server (required) Includes the database, See Chapter 2, “Installing the Tivoli Storage Manager server
GSKit, and tools to help components,” on page 31.
you configure and manage
Tivoli Storage Manager.
Language package Each language package See “Installing server language packages” on page 37.
(optional) (one for each language)
contains language-specific
information for the server.
Licenses (required) Includes support for all Use the REGISTER LICENSE command.
Tivoli Storage Manager
licensed features. After you
install this package, you
must configure the licenses
you purchased.
Devices (optional) Extends Tivoli Storage A list of devices that are supported by this driver is available
Manager media from the Tivoli Storage Manager website. See
management capability. http://www.ibm.com/support/entry/portal/Overview/
Software/Tivoli/Tivoli_Storage_Manager.
Storage agent Installs the component that For more information about storage agents, see Tivoli Storage
(optional) allows client systems to Manager for Storage Area Networks (http://www.ibm.com/
write data directly to, or support/knowledgecenter/SSSQZW_7.1.1/
read data directly from, com.ibm.itsm.sta.doc/c_overview.html).
storage devices that are
attached to a storage area
network (SAN).
Remember: The IBM
Tivoli Storage Manager for
Storage Area Networks is a
separately licensed
product.
Operations Center Installs the Operations See Part 3, “Installing and upgrading the Operations Center,”
(optional) Center, which is a on page 191.
web-based interface for
managing your storage
environment.
Tivoli Monitoring for Provides reports and real See Chapter 9, “Installing Tivoli Monitoring for Tivoli Storage
Tivoli Storage Manager time monitoring Manager,” on page 99.
(optional) information about Tivoli
Storage Manager servers
and client activity.
Tip: Tivoli Monitoring for
Tivoli Storage Manager is
on a separate DVD.

viii IBM Tivoli Storage Manager for AIX: Installation Guide

Publications
The Tivoli Storage Manager product family includes IBM Tivoli Storage
FlashCopy® Manager, IBM Tivoli Storage Manager for Space Management, IBM
Tivoli Storage Manager for Databases, and several other storage management
products from IBM Tivoli.

To view IBM product documentation, see http://www.ibm.com/support/

knowledgecenter/.

About this publication ix

x IBM Tivoli Storage Manager for AIX: Installation Guide
New for Tivoli Storage Manager Version 7.1.1
Many installation-related features in IBM Tivoli Storage Manager V7.1.1 are new
for Tivoli Storage Manager users. These changes affect the Tivoli Storage Manager
server, the Operations Center, the Administration Center, Tivoli Monitoring for
Tivoli Storage Manager, and the upgrade to V7.1.1.

For a complete list of new V7.1.1 features, see IBM Knowledge Center.
IBM Installation Manager
In Tivoli Storage Manager V7.1.1, the server, Operations Center, and Tivoli
Monitoring for Tivoli Storage Manager use IBM Installation Manager to
install or update software. If the required version of IBM Installation
Manager is not already installed, it is automatically installed or upgraded
when you install the Tivoli Storage Manager server, Operations Center, and
Tivoli Monitoring for Tivoli Storage Manager. It must remain installed on
the system so that the server, Operations Center, and Tivoli Monitoring for
Tivoli Storage Manager can be updated or uninstalled later as needed.
Operations Center updates

Restriction: The Operations Center cannot be installed on HP-UX or

Oracle Solaris systems. However, you can use the Operations Center to
manage Tivoli Storage Manager V6.3.4 or later servers that run on HP-UX
or Oracle Solaris systems.
You can now complete the following tasks through the Operations Center:
Navigation, customization, and reporting
v Use improved linking to navigate between pages of the
Operations Center more easily
v Use advanced filters to construct custom views of table data
v Bookmark and use shared links to commonly accessed web
pages
v Customize the Operations Center login page to include text that
you provide
v Configure daily email reports on client coverage and server
status
v If you have a Tivoli Storage Manager Suite for Unified Recovery
license, compare the amount of data you are managing with
what your entitlement allows
Alerts
v Add an alert by specifying the message that triggers the alert
v Select which administrators receive email notifications for an
alert
v Change the category for an alert
v Delete an alert definition for a message, so the message no
longer triggers an alert
Clients
v View client schedules
v Add client schedules

© Copyright IBM Corp. 1993, 2014 xi

 v Modify client schedules
Services
v Properties of the policy domain, such as the default management
class and the retention grace period
v The files and related objects that were examined and expired
over the previous two weeks
v The active policy set for the policy domain
Servers
You can now view maintenance schedules from the Servers page.
Storage Pools
v Manually migrate storage pool data
v Manually reclaim storage pool space
v View the following storage pool details:
– Properties of the storage pool, such as the device class and
utilization
– The storage pool capacity that was used over the previous
two weeks
– Volumes that are assigned to the storage pool
v Edit certain storage pool properties
Tivoli Monitoring for Tivoli Storage Manager availability
IBM Tivoli Monitoring for Tivoli Storage Manager is delivered with V7.1.1.
You can use Tivoli Monitoring for Tivoli Storage Manager V7.1 with any
Tivoli Storage Manager V7.1 or later server.
Administration Center availability
Although the Tivoli Storage Manager Administration Center is not
delivered with V7.1 or later versions, you can instead use the Operations
Center, which is a web-based interface for managing your storage
environment.
You can use the V6.3.4 Administration Center with any Tivoli Storage
Manager V6.3 or later server, including to automatically update
backup-archive clients. For more information about the Tivoli Storage
Manager Administration Center, see the V6.3 IBM Knowledge Center.

xii IBM Tivoli Storage Manager for AIX: Installation Guide

Part 1. Installing and upgrading the server
Install and upgrade the Tivoli Storage Manager server.

Before you begin

Planning to install Installing components Taking the first steps

Figure 1. As highlighted in the figure, you are in the planning to install the Tivoli Storage Manager server section.
Review this section carefully to ensure that you have the system and other requirements needed to install Tivoli
Storage Manager.

© Copyright IBM Corp. 1993, 2014 1

2 IBM Tivoli Storage Manager for AIX: Installation Guide
Chapter 1. Planning to install the Tivoli Storage Manager
server
Install the Tivoli Storage Manager server software on the computer that manages
storage devices and install the Tivoli Storage Manager client software on every
workstation that transfers data to Tivoli Storage Manager server-managed storage.

About this task

Tivoli Storage Manager server maintenance releases, client software, and

publications are available from the Tivoli Storage Manager website at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.

Allow approximately 30 - 45 minutes to install a Tivoli Storage Manager Version

7.1.1 server, using this guide.

An upgrade from V6.1.x, V6.2.x, or V6.3.x to V7.1.1 takes approximately 20 - 50

minutes. Your environment might produce different results than that obtained in
the labs.

The following figure illustrates the main parts for installing a new Tivoli Storage
Manager server.

Configure and start the

Preview and verify Select a method to First
Planning Installing server, register licenses,
server requirements install the software steps prepare for backups

What you should know first

Before installing IBM Tivoli Storage Manager, be familiar with your operating
systems, storage devices, communication protocols, and system configurations.
Table 2. Upgrade information
To upgrade from this
version To this version See this information
V7.1 V7.1 fix pack or interim fix Chapter 4, “Installing a Tivoli
Storage Manager server fix
pack,” on page 63
V6.2 or V6.3 V7.1.1 “Upgrading from Tivoli
Storage Manager V6.2 or
V6.3 to V7.1.1” on page 68
V6.1 V7.1.1 “Upgrading from Tivoli
Storage Manager V6.1 to
V7.1.1” on page 76

© Copyright IBM Corp. 1993, 2014 3

Installing the Tivoli Storage Manager server

Table 2. Upgrade information (continued)

To upgrade from this
version To this version See this information
V5 V7.1.1 Upgrade and Migration Guide
for V5 Servers

If you are migrating a Tivoli Storage Manager server, see the following
documentation:
v V5 server on a z/OS® operating system to V7.1.1 on an AIX® or Linux on
System z® operating system, see the Upgrade and Migration Guide for V5 Servers
v V5 server on an AIX, HP-UX, or Solaris operating system to V6.3.4 or later on a
Linux x86_64 operating system, see the Upgrade and Migration Guide for V5
Servers.

Restriction: You can install and run the Version 7.1.1 server on a system that
already has DB2® installed on it, whether DB2 was installed independently or as
part of some other application, with some restrictions. For details, see
“Compatibility of the Tivoli Storage Manager server with other DB2 products on
the system” on page 7.

Experienced DB2 administrators can choose to perform advanced SQL queries and
use DB2 tools to monitor the database. Do not, however, use DB2 tools to change
DB2 configuration settings from those that are preset by Tivoli Storage Manager, or
alter the DB2 environment for Tivoli Storage Manager in other ways, such as with
other products. The Tivoli Storage Manager Version 7.1.1 server has been built and
tested extensively using the data definition language (DDL) and database
configuration that Tivoli Storage Manager deploys.

Attention: Do not alter the DB2 software that is installed with Tivoli Storage
Manager installation packages and fix packs. Do not install or upgrade to a
different version, release, or fix pack of DB2 software because doing so can damage
the database.

System requirements for the Tivoli Storage Manager server

The Tivoli Storage Manager server can require a large amount of memory, network
bandwidth, and processor resources. In many cases, the server performs best when
other applications are not installed on the same system.

Hardware and software requirements for the Tivoli Storage

Manager server installation

These tables list the minimum hardware and software requirements for the
installation of a Tivoli Storage Manager server. Use these requirements as a starting
point. You can find the most current information about system requirements at
Tivoli Storage Manager Supported Operating Systems.

See IBM Tivoli Storage Manager Optimizing Performance (http://www.ibm.com/

support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.perf.doc/
c_howtouseinfo.html) for server configuration guidelines and best practices.

4 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Hardware requirements

| Table 3 describes the minimum hardware requirements that are needed for your
| Tivoli Storage Manager AIX system. The installation fails if you do not have the
| minimum requirements. For more details about planning disk space, see “Capacity
| planning” on page 10.
Table 3. Hardware requirements
Type of
hardware Hardware requirements
Hardware An appropriately configured POWER5 or later systems computer (64-bit)
Disk space The following minimum values for disk space:
| v 32 MB for the /var directory
v 5 GB for the installation directory
v 2 GB for the /tmp directory
v 2 GB in the home directory
Tip: Expect to use more space for problem determination.
v 2 GB for the shared resources area

Significant additional disk space is required for database and log files. The
size of the database depends on the number of client files to be stored and
the method by which the server manages them. The default active log
space is 16 GB, the minimum that is needed for most workloads and
configurations. When you create the active log, you need at least 64 GB in
size to run replication. If replication and deduplication are both being used,
create an active log of 128 GB in size. Allocate at least three times the
default active log space for the archive log (48 GB). Ensure that you have
sufficient resources if you are using data deduplication or expect a heavy
client workload.

For optimal performance and to facilitate I/O, specify at least two equally
sized containers or Logical Unit Numbers (LUNs) for the database. See IBM
Tivoli Storage Manager Optimizing Performance (http://www.ibm.com/
support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.perf.doc/
c_howtouseinfo.html) for more information about the configuration of
directories for the database. In addition, each active log and archive log
should have its own container or LUN.

Ensure that you see the capacity planning section for more details about
disk space.
Memory The following minimum values for memory:
v 12 GB.
v 16 GB if you are using data deduplication.
v At least 32 GB for heavily used servers. Using 32 GB or more of memory
enhances performance of the Tivoli Storage Manager server database
inventory.
v If you plan to run multiple instances, each instance requires the memory
listed for one server. Multiply the memory for one server by the number
of instances planned for the system.
v If you plan to use node replication without data deduplication, the
system requires 32 GB of memory. Node replication with data
deduplication requires a minimum of 64 GB of memory.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 5

 Installing the Tivoli Storage Manager server

Software requirements

Table 4 describes the minimum software requirements that are needed for your
Tivoli Storage Manager AIX system.
Table 4. Software requirements
Type of
software Minimum software requirements
Operating AIX 6.1 running in a 64-bit kernel environment with the following
system additional requirements:
v AIX 6.1 TL 7 and SP6.
v Minimum C++ runtime level with the xlC.rte 12.1.0.1 or later file sets.
The file set is automatically upgraded if the level is lower than 12.1.0.1.
The file set is included in the June 2008 fix pack package for IBM C++
Runtime Environment Components for AIX.

AIX 7.1 running in a 64-bit kernel environment.

v AIX 7.1 TL 1 and SP6.
v Minimum C++ runtime level with the xlC.rte 12.1.0.1 or later file sets.
The file set is automatically upgraded if the level is lower than 12.1.0.1.
The file set is included in the June 2008 fix pack package for IBM C++
Runtime Environment Components for AIX.

For the latest recommendations about AIX maintenance levels, see

http://www.ibm.com/support/docview.wss?uid=swg21165448

| To use the N_Port ID Virtualization (NPIV) facility, ensure that you have
| the following minimum requirements:
| v Virtual I/O Server 2.1.2 or later
| v AIX 7.1 or 6.1 TL4 SP 3 or later
| v An HBA adapter supported by the corresponding AIX and Virtual I/O
| Server
Communication A configured communication method.
protocol
Processing Asynchronous I/O must be enabled.
Device drivers The Tivoli Storage Manager device driver required for non-IBM drives
and tape libraries. The Tivoli Storage Manager device driver package
contains device driver tools and ACSLS daemons.

For the IBM 3590, 3592, or the Ultrium tape library or drives, the IBM
device drivers are required. Install the most current device drivers. You
can locate IBM driver packages at the Fix Central website:
http://www.ibm.com/support/fixcentral/.

Configure the device drivers before you use the Tivoli Storage Manager
server with tape devices.
Gunzip utility The gunzip utility must be available on your system before you install or
upgrade the Tivoli Storage Manager Version 7 server. Ensure that the
gunzip utility is installed and the path to it is set in the PATH
environment variable.
Other software Korn Shell (ksh)

You must have the I/O completion ports (IOCP) configured on the
operating system.

6 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Compatibility of the Tivoli Storage Manager server with other DB2

products on the system
You can install other products that deploy and use DB2 products on the same
system as the Tivoli Storage Manager Version 7.1.1 server on AIX, HP-UX, Linux,
and Oracle Solaris platforms, with some limitations.

To install and use other products that use a DB2 product on the same system as
the Tivoli Storage Manager server, ensure that the following criteria are met:
Table 5. Compatibility of the Tivoli Storage Manager server with other DB2 products on the
system
Criterion Instructions
Version level The other products that use a DB2 product
must use DB2 version 9 or later. DB2
products include product encapsulation and
segregation support beginning with Version
9. Starting with this version, you can run
multiple copies of DB2 products, at different
code levels, on the same system. For details,
see the information about multiple DB2
copies: http://www.ibm.com/support/
knowledgecenter/SSEPGG_10.5.0.
User IDs and directories Ensure that the user IDs, fence user IDs,
installation location, other directories, and
related information are not shared across
DB2 installations. Your specifications must
be different from the IDs and locations that
you used for the Tivoli Storage Manager
server installation and configuration. If you
used the dsmicfgx wizard or dsmupgdx
wizard to configure Version 7.1.1, or
upgrade the server from Version 5.5, these
are values that you entered when running
the wizard. If you used the manual
configuration for Version 7.1.1 or upgrade
from Version 5.5 procedures, review the
procedures that you used if necessary to
recall the values that were used for the
server.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 7

Installing the Tivoli Storage Manager server

Table 5. Compatibility of the Tivoli Storage Manager server with other DB2 products on the
system (continued)
Criterion Instructions
Resource allocation Consider the resources and capability of the
system compared to the requirements for
both the Tivoli Storage Manager server and
the other applications that use the DB2
product. To provide sufficient resources for
the other DB2 applications, you might have
to change the Tivoli Storage Manager server
settings so that the server uses less system
memory and resources. Similarly, if the
workloads for the other DB2 applications
compete with the Tivoli Storage Manager
server for processor or memory resources,
the performance of the server in handling
the expected client workload or other server
operations might be adversely affected.

To segregate resources and provide more

capability for the tuning and allocation of
processor, memory, and other system
resources for multiple applications, consider
using logical partition (LPAR), workload
partition (WPAR), or other virtual
workstation support. For example, run a
DB2 application on its own virtualized
system.

IBM Installation Manager

Tivoli Storage Manager uses IBM Installation Manager, which is an installation
program that can use remote or local software repositories to install or update
many IBM products.

If the required version of IBM Installation Manager is not already installed, it is

automatically installed or upgraded when you install Tivoli Storage Manager. It
must remain installed on the system so that Tivoli Storage Manager can be
updated or uninstalled later as needed.

The following list contains explanations of some terms that are used in IBM
Installation Manager:
Offering
An installable unit of a software product.
The Tivoli Storage Manager offering contains all of the media that IBM
Installation Manager requires to install Tivoli Storage Manager.
Package
The group of software components that are required to install an offering.
The Tivoli Storage Manager package contains the following components:
v IBM Installation Manager installation program
v Tivoli Storage Manager offering
Package group
A set of packages that share a common parent directory.

8 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

The default package group for the Tivoli Storage Manager package is IBM
Installation Manager.
Repository
A remote or local storage area for data and other application resources.
The Tivoli Storage Manager package is stored in a repository on IBM Fix
Central.
Shared resources directory
A directory that contains software files or plug-ins that are shared by
packages.
IBM Installation Manager stores installation-related files in the shared
resources directory, including files that are used for rolling back to a
previous version of Tivoli Storage Manager.

Worksheets for planning details for the Tivoli Storage Manager server
You can use the worksheets to help you plan the amount and location of storage
needed for the Tivoli Storage Manager server. You can also use them to keep track
of names and user IDs.

See IBM Tivoli Storage Manager Optimizing Performance (http://www.ibm.com/

support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.perf.doc/
c_howtouseinfo.html) for server configuration guidelines and best practices.

Item Space required Number of directories Location of directories

The database
Active log
Archive log
Optional: Log mirror for
the active log
Optional: Secondary
archive log (failover
location for archive log)

Item Names and user IDs Location

The instance user ID for the
server, which is the ID you use
to start and run the Tivoli
Storage Manager server
The home directory for the server,
which is the directory that
contains the instance user ID
The database instance name
The instance directory for the
server, which is a directory that
contains files specifically for this
server instance (the server
options file and other
server-specific files)
Server name, use a unique name
for each server

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 9

Installing the Tivoli Storage Manager server

Capacity planning
Capacity planning for Tivoli Storage Manager includes managing resources such as
the database and recovery log. To maximize resources as part of capacity planning,
you must estimate space requirements for the database and the recovery log.

Procedure

For information about the benefits of deduplication and guidance on how to make
effective use of the Tivoli Storage Manager deduplication feature, see Optimizing
Performance.

Estimating space requirements for the database

To estimate space requirements for the database, you can use the maximum
number of files that can be in server storage at one time or you can use storage
pool capacity.

About this task

Consider using at least 25 GB for the initial database space. Provision file system
space appropriately. A database size of 25 GB is adequate for a test environment or
a library-manager-only environment. For a production server supporting client
workloads, the database size is expected to be larger. If you use random-access
disk (DISK) storage pools, more database and log storage space is needed than for
sequential-access storage pools.

The maximum size of the Tivoli Storage Manager database is 4 TB.

For information about sizing the database in a production environment that is

based on the number of files and on storage pool size, see the following topics.

Estimating database space requirements based on the number of

files
If you can estimate the maximum number of files that might be in server storage at
a time, you can use that number to estimate space requirements for the database.

About this task

To estimate space requirements that is based on the maximum number of files in

server storage, use the following guidelines:
v 600 - 1000 bytes for each stored version of a file, including image backups.

Restriction: The guideline does not include space that is used during data
deduplication.
v 100 - 200 bytes for each cached file, copy storage pool file, active-data pool file,
and deduplicated file.
v Additional space is required for database optimization to support varying
data-access patterns and to support server back-end processing of the data. The
amount of extra space is equal to 50% of the estimate for the total number of
bytes for file objects.

In the following example for a single client, the calculations are based on the
maximum values in the preceding guidelines. The examples do not take into
account that you might use file aggregation. In general, when you aggregate small

10 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

files, it reduces the amount of required database space. File aggregation does not
affect space-managed files.

Procedure
1. Calculate the number of file versions. Add each of the following values to
obtain the number of file versions:
a. Calculate the number of backed-up files. For example, as many as 500,000
client files might be backed up at a time. In this example, storage policies
are set to keep up to three copies of backed up files:
500,000 files * 3 copies = 1,500,000 files
b. Calculate the number of archive files. For example, as many as 100,000
client files might be archived copies.
c. Calculate the number of space-managed files. For example, as many as
200,000 client files might be migrated from client workstations.
Using 1000 bytes per file, the total amount of database space that is required
for the files that belong to the client is 1.8 GB:
(1,500,000 + 100,000 + 200,000) * 1000 = 1.8 GB
2. Calculate the number of cached files, copy storage-pool files, active-data pool
files, and deduplicated files:
a. Calculate the number of cached copies. For example, caching is enabled in a
5 GB disk storage pool. The high migration threshold of the pool is 90%
and the low migration threshold of the pool is 70%. Thus, 20% of the disk
pool, or 1 GB, is occupied by cached files.
If the average file size is about 10 KB, approximately 100,000 files are in
cache at any one time:
100,000 files * 200 bytes = 19 MB
b. Calculate the number of copy storage-pool files. All primary storage pools
are backed up to the copy storage pool:
(1,500,000 + 100,000 + 200,000) * 200 bytes = 343 MB
c. Calculate the number of active storage-pool files. All the active
client-backup data in primary storage pools is copied to the active-data
storage pool. Assume that 500,000 versions of the 1,500,000 backup files in
the primary storage pool are active:
500,000 * 200 bytes = 95 MB
d. Calculate the number of deduplicated files. Assume that a deduplicated
storage pool contains 50,000 files:
50,000 * 200 bytes = 10 MB
Based on the preceding calculations, about 0.5 GB of extra database space is
required for the client’s cached files, copy storage-pool files, active-data pool
files, and deduplicated files.
3. Calculate the amount of extra space that is required for database optimization.
To provide optimal data access and management by the server, extra database
space is required. The amount of extra database space is equal to 50% of the
total space requirements for file objects.
(1.8 + 0.5) * 50% = 1.2 GB
4. Calculate the total amount of database space that is required for the client. The
total is approximately 3.5 GB:
1.8 + 0.5 + 1.2 = 3.5 GB
5. Calculate the total amount of database space that is required for all clients. If
the client that was used in the preceding calculations is typical and you have

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 11

Installing the Tivoli Storage Manager server

500 clients, for example, you can use the following calculation to estimate the
total amount of database space that is required for all clients:
500 * 3.5 = 1.7 TB

Results

Tip: In the preceding examples, the results are estimates. The actual size of the
database might differ from the estimate because of factors such as the number of
directories and the length of the path and file names. Periodically monitor your
database and adjust its size as necessary.

What to do next

During normal operations, the Tivoli Storage Manager server might require
temporary database space. This space is needed for the following reasons:
v To hold the results of sorting or ordering that are not already being kept and
optimized in the database directly. The results are temporarily held in the
database for processing.
v To give administrative access to the database through one of the following
methods:
– A DB2 open database connectivity (ODBC) client
– An Oracle Java™ database connectivity (JDBC) client
– Structured Query Language (SQL) to the server from an administrative-client
command line

Consider using an extra 50 GB of temporary space for every 500 GB of space for
file objects and optimization. See the guidelines in the following table. In the
example that is used in the preceding step, a total of 1.7 TB of database space is
required for file objects and optimization for 500 clients. Based on that calculation,
200 GB is required for temporary space. The total amount of required database
space is 1.9 TB.

Database size Minimum temporary-space requirement

< 500 GB 50 GB
≥ 500 GB and < 1 TB 100 GB
≥ 1 TB and < 1.5 TB 150 GB
≥ 1.5 and < 2 TB 200 GB
≥ 2 and < 3 TB 250 - 300 GB
≥ 3 and < 4 TB 350 - 400 GB

Estimating database space requirements based on storage pool

capacity
To estimate database space requirements based on storage pool capacity, use a ratio
of 1 - 5%. For example, if you require 200 TB of storage pool capacity, the size of
your database is expected to be 2 - 10 TB. As a general rule, make your database
as large as possible to prevent running out of space. If you run out of database
space, server operations and client-store operations can fail.

12 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

The database manager and temporary space

The Tivoli Storage Manager server database manager manages and allocates
system memory and disk space for the database. The amount of database space
you require depends on the amount of system memory available and the server
workload.

The database manager sorts data in a specific sequence, according to the SQL
statement that you issue to request the data. Depending on the workload on the
server, and if there is more data than the database manager can manage, the data
(that is ordered in sequence) is allocated to temporary disk space. Data is allocated
to temporary disk space when there is a large result set. The database manager
dynamically manages the memory that is used when data is allocated to temporary
disk space.

| For example, expiration processing can produce a large result set. If there is not
| enough system memory on the database to store the result set, some of the data is
| allocated to temporary disk space. During expiration processing, if a node or file
| space are selected that are too large to process, the database manager cannot sort
| the data in memory. The database manager must use temporary space to sort data.

To run database operations, consider adding more database space for the following
scenarios:
v The database has a small amount of space and the server operation that requires
temporary space uses the remaining free space.
v The file spaces are large, or the file spaces has a policy that is assigned to it,
which creates many file versions.
v The Tivoli Storage Manager server must run with limited memory. The database
uses the Tivoli Storage Manager server main memory to run database
operations. However, if there is insufficient memory available, the Tivoli Storage
Manager server allocates temporary space on disk to the database. For example,
if 10G of memory is available and database operations require 12G of memory,
the database uses temporary space.
v An out of database space error is displayed when you deploy a Tivoli Storage
Manager V6 server. Monitor the server activity log for messages that are related
to database space.

Important: Do not change the DB2 software that is installed with the Tivoli
Storage Manager installation packages and fix packs. Do not install or upgrade to a
different version, release, or fix pack, of DB2 software to avoid damage to the
database.

Recovery log space requirements

In Tivoli Storage Manager, the term recovery log comprises the active log, the
archive log, the active log mirror, and the archive failover log. The amount of space
that you require for the recovery log depends on various factors, including, for
example, the amount of client activity with the server.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 13

Installing the Tivoli Storage Manager server

Active and archive log space

When you estimate space requirements for active and archive logs, include some
extra space for contingencies such as occasional heavy workloads and failovers.

In Tivoli Storage Manager servers V6.1 and later, the active log can be a maximum
size of 128 GB. The archive log size is limited to the size of the file system that it is
installed on.

Use the following general guidelines when you estimate the size of the active log:
v The suggested starting size for the active log is 16 GB.
v Ensure that the active log is at least large enough for the amount of concurrent
activity that the server typically handles. As a precaution, try to anticipate the
largest amount of work that the server manages at one time. Provision the active
log with extra space that can be used if needed. Consider using 20% of extra
space.
v Monitor used and available active log space. Adjust the size of the active log as
needed, depending upon factors such as client activity and the level of server
operations.
v Ensure that the directory that holds the active log is as large as, or larger than,
the size of the active log. A directory that is larger than the active log can
accommodate failovers, if they occur.
v Ensure that the file system that contains the active log directory has at least 8
GB of free space for temporary log movement requirements.

The suggested starting size for the archive log is 48 GB.

The archive log directory must be large enough to contain the log files that are
generated since the previous full backup. For example, if you perform a full
backup of the database every day, the archive log directory must be large enough
to hold the log files for all the client activity that occurs during 24 hours. To
recover space, the server deletes obsolete archive log files after a full backup of the
database. If the archive log directory becomes full and a directory for archive
failover logs does not exist, log files remain in the active log directory. This
condition can cause the active log directory to fill up and stop the server. When the
server restarts, some of the existing active-log space is released.

After the server is installed, you can monitor archive log utilization and the space
in the archive log directory. If the space in the archive log directory fills up, it can
cause the following problems:
v The server is unable to perform full database backups. Investigate and resolve
this problem.
v Other applications write to the archive log directory, exhausting the space that is
required by the archive log. Do not share archive log space with other
applications including other Tivoli Storage Manager servers. Ensure that each
server has a separate storage location that is owned and managed by that
specific server.

For guidance about the layout and tuning of the active log and archive log, see
Optimizing Performance.

14 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Example: Estimating active and archive log sizes for basic client-store
operations:

Basic client-store operations include backup, archive, and space management. Log
space must be sufficient to handle all store transactions that are in progress at one
time.

To determine the sizes of the active and archive logs for basic client-store
operations, use the following calculation:
number of clients x files stored during each transaction
x log space needed for each file

This calculation is used in the example in the following table.

Table 6. Basic client-store operations
Example
Item values Description
Maximum number of client nodes 300 The number of client nodes that back up, archive, or migrate
that back up, archive, or migrate files files every night.
concurrently at any time
Files stored during each transaction 4096 The default value of the server option TXNGROUPMAX is 4096.
Log space that is required for each 3053 bytes The value of 3053 bytes for each file in a transaction
file represents the log bytes that are needed when backing up
files from a Windows client where the file names are 12 -
120 bytes.

This value is based on the results of tests performed under

laboratory conditions. The tests consisted of backup-archive
clients performing backup operations to a random-access
disk (DISK) storage pool. DISK pools result in more log use
than sequential-access storage pools. Consider a value larger
than 3053 bytes if the data being stored has file names that
are longer than 12 - 120 bytes.
1
Active log: Suggested size 19.5 GB Use the following calculation to determine the size of the
active log. One GB equals 1,073,741,824 bytes.

(300 clients x 4096 files stored during each

transaction x 3053 bytes for each file) ÷ 1,073,741,824
bytes = 3.5 GB

Increase that amount by the suggested starting size of 16

GB:

3.5 + 16 = 19.5 GB
1
Archive log: Suggested size 58.5 GB Because of the requirement to be able to store archive logs
across three server database-backup cycles, multiply the
estimate for the active log by 3 to estimate the total archive
log requirement.

3.5 x 3 = 10.5 GB

Increase that amount by the suggested starting size of 48

GB:

10.5 + 48 = 58.5 GB

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 15

Installing the Tivoli Storage Manager server

Table 6. Basic client-store operations (continued)

Example
Item values Description
1
The example values in this table are used only to illustrate how the sizes for active logs and archive logs are
calculated. In a production environment that does not use deduplication, 16 GB is the suggested minimum size for
an active log. The suggested minimum size for an archive log in a production environment that does not use
deduplication is 48 GB. If you substitute values from your environment and the results are larger than 16 GB and 48
GB, use your results to size the active log and archive log.

Monitor your logs and adjust their size if necessary.

Example: Estimating active and archive log sizes for clients that use multiple
sessions:

If the client option RESOURCEUTILIZATION is set to a value that is greater than the
default, the concurrent workload for the server increases.

To determine the sizes of the active and archive logs when clients use multiple
sessions, use the following calculation:
number of clients x sessions for each client x files stored
during each transaction x log space needed for each file

This calculation is used in the example in the following table.

Table 7. Multiple client sessions
Item Example values Description
Maximum number of client 300 1000 The number of client nodes that back up, archive, or
nodes that back up, archive, migrate files every night.
or migrate files concurrently
at any time
Possible sessions for each 3 3 The setting of the client option RESOURCEUTILIZATION is
client larger than the default. Each client session runs a maximum
of three sessions in parallel.
Files stored during each 4096 4096 The default value of the server option TXNGROUPMAX is 4096.
transaction
Log space that is required for 3053 3053 The value of 3053 bytes for each file in a transaction
each file represents the log bytes needed when backing up files from
a Windows client where the file names are 12 - 120 bytes.

This value is based on the results of tests performed under

laboratory conditions. Tests consisted of clients performing
backup operations to a random-access disk (DISK) storage
pool. DISK pools result in more log use than
sequential-access storage pools. Consider a value larger
than 3053 bytes if the data being stored has file names that
are longer than 12 - 120 bytes.

16 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Table 7. Multiple client sessions (continued)

Item Example values Description
1 1
Active log: Suggested size 26.5 GB 51 GB The following calculation was used for 300 clients. One GB
equals 1,073,741,824 bytes.

(300 clients x 3 sessions for each client x 4096 files

stored during each transaction x 3053 bytes for each
file) ÷ 1,073,741,824 = 10.5 GB

Increase that amount by the suggested starting size of 16

GB:

10.5 + 16 = 26.5 GB

The following calculation was used for 1000 clients. One

GB equals 1,073,741,824 bytes.

(1000 clients x 3 sessions for each client x 4096

files store during each transaction x 3053 bytes for
each file) ÷ 1,073,741,824 = 35 GB

Increase that amount by the suggested starting size of 16

GB:

35 + 16 = 51 GB
1 1
Archive log: Suggested size 79.5 GB 153 GB Because of the requirement to be able to store archive logs
across three server-database backup cycles, the estimate for
the active log is multiplied by 3:

10.5 x 3 = 31.5 GB

35 x 3 = 105 GB

Increase those amounts by the suggested starting size of 48

GB:

31.5 + 48 = 79.5 GB

105 + 48 = 153 GB
1
The example values in this table are used only to illustrate how the sizes for active logs and archive logs are
calculated. In a production environment that does not use deduplication, 16 GB is the suggested minimum size for
an active log. The suggested minimum size for an archive log in a production environment that does not use
deduplication is 48 GB. If you substitute values from your environment and the results are larger than 16 GB and 48
GB, use your results to size the active log and archive log.

Monitor your active log and adjust its size if necessary.

Example: Estimating active and archive log sizes for simultaneous write
operations:

If client backup operations use storage pools that are configured for simultaneous
write, the amount of log space that is required for each file increases.

The log space that is required for each file increases by about 200 bytes for each
copy storage pool that is used for a simultaneous write operation. In the example
in the following table, data is stored to two copy storage pools in addition to a
primary storage pool. The estimated log size increases by 400 bytes for each file. If
you use the suggested value of 3053 bytes of log space for each file, the total
number of required bytes is 3453.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 17

Installing the Tivoli Storage Manager server

This calculation is used in the example in the following table.

Table 8. Simultaneous write operations
Example
Item values Description
Maximum number of client nodes 300 The number of client nodes that back up, archive, or migrate
that back up, archive, or migrate files files every night.
concurrently at any time
Files stored during each transaction 4096 The default value of the server option TXNGROUPMAX is 4096.
Log space that is required for each 3453 bytes 3053 bytes plus 200 bytes for each copy storage pool.
file
The value of 3053 bytes for each file in a transaction
represents the log bytes that are needed when backing up
files from a Windows client where the file names are 12 - 120
bytes.

This value is based on the results of tests performed under

laboratory conditions. The tests consisted of backup-archive
clients performing backup operations to a random-access
disk (DISK) storage pool. DISK pools result in more log use
than sequential-access storage pools. Consider a value larger
than 3053 bytes if the data being stored has file names that
are longer than 12 - 120 bytes.
1
Active log: Suggested size 20 GB Use the following calculation to determine the size of the
active log. One GB equals 1,073,741,824 bytes.

(300 clients x 4096 files stored during each

transaction x 3453 bytes for each file) ÷ 1,073,741,824
bytes = 4.0 GB

Increase that amount by the suggested starting size of 16 GB:

4 + 16 = 20 GB
1
Archive log: Suggested size 60 GB Because of the requirement to be able to store archive logs
across three server database-backup cycles, multiply the
estimate for the active log by 3 to estimate the archive log
requirement:

4 GB x 3 = 12 GB

Increase that amount by the suggested starting size of 48 GB:

12 + 48 = 60 GB
1
The example values in this table are used only to illustrate how the sizes for active logs and archive logs are
calculated. In a production environment that does not use deduplication, 16 GB is the suggested minimum size for
an active log. The suggested minimum size for an archive log in a production environment that does not use
deduplication is 48 GB. If you substitute values from your environment and the results are larger than 16 GB and 48
GB, use your results to size the active log and archive log.

Monitor your logs and adjust their size if necessary.

18 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Example: Estimating active and archive log sizes for basic client store operations
and server operations:

Migration of data in server storage, identification processes for data deduplication,

reclamation, and expiration might run concurrently with client store operations.
Administrative tasks such as administrative commands or SQL queries from
administrative clients can also run concurrently with client store operations. Server
operations and administrative tasks that run concurrently can increase the active
log space that is required.

For example, migration of files from the random-access (DISK) storage pool to a
sequential-access disk (FILE) storage pool uses approximately 110 bytes of log
space for each file that is migrated. For example, suppose that you have 300
backup-archive clients and each one of them backs up 100,000 files every night.
The files are initially stored on DISK and then migrated to a FILE storage pool. To
estimate the amount of active log space that is required for the data migration, use
the following calculation. The number of clients in the calculation represents the
maximum number of client nodes that back up, archive, or migrate files
concurrently at any time.
300 clients x 100,000 files for each client x 110 bytes = 3.1 GB

Add this value to the estimate for the size of the active log that calculated for basic
client store operations.

Example: Estimating active and archive log sizes under conditions of extreme
variation:

Problems with running out of active log space can occur if you have many
transactions that complete quickly and some transactions that take much longer to
complete. A typical case occurs when many workstation or file-server backup
sessions are active and a few very large database server-backup sessions are active.
If this situation applies to your environment, you might need to increase the size
of the active log so that the work completes successfully.

Example: Estimating archive log sizes with full database backups:

The Tivoli Storage Manager server deletes unnecessary files from the archive log
only when a full database backup occurs. Consequently, when you estimate the
space that is required for the archive log, you must also consider the frequency of
full database backups.

For example, if a full database backup occurs once a week, the archive log space
must be able to contain the information in the archive log for a full week.

The difference in archive log size for daily and full database backups is shown in
the example in the following table.
Table 9. Full database backups
Example
Item values Description
Maximum number of client nodes 300 The number of client nodes that back up, archive, or migrate
that back up, archive, or migrate files files every night.
concurrently at any time
Files stored during each transaction 4096 The default value of the server option TXNGROUPMAX is 4096.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 19

Installing the Tivoli Storage Manager server

Table 9. Full database backups (continued)

Example
Item values Description
Log space that is required for each 3453 bytes 3053 bytes for each file plus 200 bytes for each copy storage
file pool.

The value of 3053 bytes for each file in a transaction

represents the log bytes needed when backing up files from
a Windows client where the file names are 12 - 120 bytes.

This value is based on the results of tests performed under

laboratory conditions. Tests consisted of clients performing
backup operations to a random-access disk (DISK) storage
pool. DISK pools result in more log use than
sequential-access storage pools. Consider a value larger than
3053 bytes if the data being stored has file names that are
longer than 12 - 120 bytes.
1
Active log: Suggested size 20 GB Use the following calculation to determine the size of the
active log. One GB equals 1,073,741,824 bytes.

(300 clients x 4096 files per transaction x 3453 bytes

per file) ÷ 1,073,741,824 bytes = 4.0 GB

Increase that amount by the suggested starting size of 16

GB:

4 + 16 = 20 GB
1
Archive log: Suggested size with a 60 GB Because of the requirement to be able to store archive logs
full database backup every day across three backup cycles, multiply the estimate for the
active log by 3 to estimate the total archive log requirement:

4 GB x 3 = 12 GB

Increase that amount by the suggested starting size of 48

GB:

12 + 48 = 60 GB
1
Archive log: Suggested size with a 132 GB Because of the requirement to be able to store archive logs
full database every week across three server database-backup cycles, multiply the
estimate for the active log by 3 to estimate the total archive
log requirement. Multiply the result by the number of days
between full database backups:

(4 GB x 3 ) x 7 = 84 GB

Increase that amount by the suggested starting size of 48

GB:

84 + 48 = 132 GB
1
The example values in this table are used only to illustrate how the sizes for active logs and archive logs are
calculated. In a production environment that does not use deduplication, 16 GB is the suggested minimum size for
an active log. The suggested starting size for an archive log in a production environment that does not use
deduplication is 48 GB. If you substitute values from your environment and the results are larger than 16 GB and 48
GB, use your results to size the active log and archive log.

Monitor your logs and adjust their size if necessary.

20 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Example: Estimating active and archive log sizes for data deduplication
operations:

If you deduplicate data, you must consider its effects on space requirements for
active and archive logs.

The following factors affect requirements for active and archive log space:
The amount of deduplicated data
The effect of data deduplication on the active log and archive log space
depends on the percentage of data that is eligible for deduplication. If the
percentage of data that can be deduplicated is relatively high, more log
space is required.
The size and number of extents
Approximately 1,500 bytes of active log space are required for each extent
that is identified by a duplicate-identification process. For example, if
250,000 extents are identified by a duplicate-identification process, the
estimated size of the active log is 358 MB:
250,000 extents identified during each process x 1,500 bytes
for each extent = 358 MB

Consider the following scenario. Three hundred backup-archive clients

back up 100,000 files each night. This activity creates a workload of
30,000,000 files. The average number of extents for each file is two.
Therefore, the total number of extents is 60,000,000, and the space
requirement for the archive log is 84 GB:
60,000,000 extents x 1,500 bytes for each extent = 84 GB
A duplicate-identification process operates on aggregates of files. An
aggregate consists of files that are stored in a given transaction, as
specified by the TXNGROUPMAX server option. Suppose that the TXNGROUPMAX
server option is set to the default of 4096. If the average number of extents
for each file is two, the total number of extents in each aggregate is 8192,
and the space required for the active log is 12 MB:
8192 extents in each aggregate x 1500 bytes for each extent =
12 MB
The timing and number of the duplicate-identification processes
The timing and number of duplicate-identification processes also affects the
size of the active log. Using the 12 MB active-log size that was calculated
in the preceding example, the concurrent load on the active log is 120 MB
if 10 duplicate-identification processes are running in parallel:
12 MB for each process x 10 processes = 120 MB
File size
Large files that are processed for duplicate identification can also affect the
size of the active log. For example, suppose that a backup-archive client
backs up an 80 GB, file-system image. This object can have a high number
of duplicate extents if, for example, the files included in the file system
image were backed up incrementally. For example, assume that a file
system image has 1.2 million duplicate extents. The 1.2 million extents in
this large file represent a single transaction for a duplicate-identification
process. The total space in the active log that is required for this single
object is 1.7 GB:
1,200,000 extents x 1,500 bytes for each extent = 1.7 GB

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 21

Installing the Tivoli Storage Manager server

If other, smaller duplicate-identification processes occur at the same time as

the duplicate-identification process for a single large object, the active log
might not have enough space. For example, suppose that a storage pool is
enabled for deduplication. The storage pool has a mixture of data,
including many relatively small files that range from 10 KB to several
hundred KB. The storage pool also has few large objects that have a high
percentage of duplicate extents.
To take into account not only space requirements but also the timing and
duration of concurrent transactions, increase the estimated size of the
active log by a factor of two. For example, suppose that your calculations
for space requirements are 25 GB (23.3 GB + 1.7 GB for deduplication of a
large object). If deduplication processes are running concurrently, the
suggested size of the active log is 50 GB. The suggested size of the archive
log is 150 GB.
The examples in the following tables show calculations for active and
archive logs. The example in the first table uses an average size of 700 KB
for extents. The example in the second table uses an average size of 256
KB. As the examples show, the average deduplicate-extent size of 256 KB
indicates a larger estimated size for the active log. To minimize or prevent
operational problems for the server, use 256 KB to estimate the size of the
active log in your production environment.
Table 10. Average duplicate-extent size of 700 KB
Item Example values Description
Size of largest single 800 GB 4 TB The granularity of processing for deduplication is at the file
object to deduplicate level. Therefore, the largest single file to deduplicate
represents the largest transaction and a correspondingly
large load on the active and archive logs.
Average size of 700 KB 700 KB The deduplication algorithms use a variable block method.
extents Not all deduplicated extents for a given file are the same
size, so this calculation assumes an average size for extents.
Extents for a given 1,198,372 6,135,667 bits Using the average extent size (700 KB), these calculations
file bits represent the total number of extents for a given object.

The following calculation was used for an 800 GB object:

(800 GB ÷ 700 KB) = 1,198,372 bits

The following calculation was used for a 4 TB object: (4 TB ÷

700 KB) = 6,135,667 bits
Active log: Suggested 1.7 GB 8.6 GB The estimated active log space that are needed for this
size that is required transaction.
for the deduplication
of a single large object
during a single
duplicate-
identification process

22 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Table 10. Average duplicate-extent size of 700 KB (continued)

Item Example values Description
1 1
Active log: Suggested 66 GB 79.8 GB After considering other aspects of the workload on the
total size server in addition to deduplication, multiply the existing
estimate by a factor of two. In these examples, the active log
space required to deduplicate a single large object is
considered along with previous estimates for the required
active log size.

The following calculation was used for multiple transactions

and an 800 GB object:

(23.3 GB + 1.7 GB) x 2 = 50 GB

Increase that amount by the suggested starting size of 16 GB:

50 + 16 = 66 GB

The following calculation was used for multiple transactions

and a 4 TB object:

(23.3 GB + 8.6 GB) x 2 = 63.8 GB

Increase that amount by the suggested starting size of 16 GB:

63.8 + 16 = 79.8 GB
1 1
Archive log: 198 GB 239.4 GB Multiply the estimated size of the active log by a factor of 3.
Suggested size
The following calculation was used for multiple transactions
and an 800 GB object:

50 GB x 3 = 150 GB

Increase that amount by the suggested starting size of 48 GB:

150 + 48 = 198 GB

The following calculation was used for multiple transactions

and a 4 TB object:

63.8 GB x 3 = 191.4 GB

Increase that amount by the suggested starting size of 48 GB:

191.4 + 48 = 239.4 GB
1
The example values in this table are used only to illustrate how the sizes for active logs and archive logs are
calculated. In a production environment that uses deduplication, 32 GB is the suggested minimum size for an active
log. The suggested minimum size for an archive log in a production environment that uses deduplication is 96 GB.
If you substitute values from your environment and the results are larger than 32 GB and 96 GB, use your results to
size the active log and archive log.

Monitor your logs and adjust their size if necessary.

Table 11. Average duplicate-extent size of 256 KB

Item Example values Description
Size of largest single 800 GB 4 TB The granularity of processing for deduplication is at the file
object to deduplicate level. Therefore, the largest single file to deduplicate
represents the largest transaction and a correspondingly
large load on the active and archive logs.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 23

Installing the Tivoli Storage Manager server

Table 11. Average duplicate-extent size of 256 KB (continued)

Item Example values Description
Average size of 256 KB 256 KB The deduplication algorithms use a variable block method.
extents Not all deduplicated extents for a given file are the same
size, so this calculation assumes an average extent size.
Extents for a given 3,276,800 bits 16,777,216 Using the average extent size, these calculations represent
file bits the total number of extents for a given object.

The following calculation was used for multiple transactions

and an 800 GB object:

(800 GB ÷ 256 KB) = 3,276,800 bits

The following calculation was used for multiple transactions

and a 4 TB object:

(4 TB ÷ 256 KB) = 16,777,216 bits

Active log: Suggested 4.5 GB 23.4 GB The estimated size of the active log space that is required for
size that is required this transaction.
for the deduplication
of a single large object
during a single
duplicate-
identification process
1 1
Active log: Suggested 71.6 GB 109.4 GB After considering other aspects of the workload on the
total size server in addition to deduplication, multiply the existing
estimate by a factor of 2. In these examples, the active log
space required to deduplicate a single large object is
considered along with previous estimates for the required
active log size.

The following calculation was used for multiple transactions

and an 800 GB object:

(23.3 GB + 4.5 GB) x 2 = 55.6 GB

Increase that amount by the suggested starting size of 16 GB:

55.6 + 16 = 71.6 GB

The following calculation was used for multiple transactions

and a 4 TB object:

(23.3 GB + 23.4 GB) x 2 = 93.4 GB

Increase that amount by the suggested starting size of 16 GB:

93.4 + 16 = 109.4 GB

24 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Table 11. Average duplicate-extent size of 256 KB (continued)

Item Example values Description
1 1
Archive log: 214.8 GB 328.2 GB The estimated size of the active log multiplied by a factor of
Suggested size 3.

The following calculation was used for an 800 GB object:

55.6 GB x 3 = 166.8 GB

Increase that amount by the suggested starting size of 48 GB:

166.8 + 48 = 214.8 GB

The following calculation was used for a 4 TB object:

93.4 GB x 3 = 280.2 GB

Increase that amount by the suggested starting size of 48 GB:

280.2 + 48 = 328.2 GB
1
The example values in this table are used only to illustrate how the sizes for active logs and archive logs are
calculated. In a production environment that uses deduplication, 32 GB is the suggested minimum size for an active
log. The suggested minimum size for an archive log in a production environment that uses deduplication is 96 GB.
If you substitute values from your environment and the results are larger than 32 GB and 96 GB, use your results to
size the active log and archive log.

Monitor your logs and adjust their size if necessary.

Active-log mirror space

The active log can be mirrored so that the mirrored copy can be used if the active
log files cannot be read. There can be only one active log mirror.

Creating a log mirror is a suggested option. If you increase the size of the active
log, the log mirror size is increased automatically. Mirroring the log can affect
performance because of the doubled I/O activity that is required to maintain the
mirror. The additional space that the log mirror requires is another factor to
consider when deciding whether to create a log mirror.

If the mirror log directory becomes full, the server issues error messages to the
activity log and to the db2diag.log. Server activity continues.

Archive-failover log space

The archive failover log is used by the server if the archive log directory runs out
of space.

Specifying an archive failover log directory can prevent problems that occur if the
archive log runs out of space. If both the archive log directory and the drive or file
system where the archive failover log directory is located become full, the data
remains in the active log directory. This condition can cause the active log to fill
up, which causes the server to halt.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 25

Installing the Tivoli Storage Manager server

Monitoring space utilization for the database and recovery

logs
To determine the amount of used and available active log space, you issue the
QUERY LOG command. To monitor space utilization in the database and recovery
logs, you can also check the activity log for messages.

Active log

If the amount of available active log space is too low, the following messages are
displayed in the activity log:
ANR4531I: IC_AUTOBACKUP_LOG_USED_SINCE_LAST_BACKUP_TRIGGER
This message is displayed when the active log space exceeds the maximum
specified size. The Tivoli Storage Manager server starts a full database
backup.
To change the maximum log size, halt the server. Open the dsmserv.opt
file, and specify a new value for the ACTIVELOGSIZE option. When you are
finished, restart the server.
ANR0297I: IC_BACKUP_NEEDED_LOG_USED_SINCE_LAST_BACKUP
This message is displayed when the active log space exceeds the maximum
specified size. You must back up the database manually.
To change the maximum log size, halt the server. Open the dsmserv.opt
file, and specify a new value for the ACTIVELOGSIZE option. When you are
finished, restart the server.
ANR4529I: IC_AUTOBACKUP_LOG_UTILIZATION_TRIGGER
The ratio of used active-log space to available active-log space exceeds the
log utilization threshold. If at least one full database backup has occurred,
the Tivoli Storage Manager server starts an incremental database backup.
Otherwise, the server starts a full database backup.
ANR0295I: IC_BACKUP_NEEDED_LOG_UTILIZATION
The ratio of used active-log space to available active-log space exceeds the
log utilization threshold. You must back up the database manually.

Archive log

If the amount of available archive log space is too low, the following message is
displayed in the activity log:
ANR0299I: IC_BACKUP_NEEDED_ARCHLOG_USED
The ratio of used archive-log space to available archive-log space exceeds
the log utilization threshold. The Tivoli Storage Manager server starts a full
automatic database backup.

Database

If the amount of space available for database activities is too low, the following
messages are displayed in the activity log:
ANR2992W: IC_LOG_FILE_SYSTEM_UTILIZATION_WARNING_2
The used database space exceeds the threshold for database space
utilization. To increase the space for the database, use the EXTEND DBSPACE
command, the EXTEND DBSPACE command, or the DSMSERV FORMAT
utility with the DBDIR parameter.

26 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

ANR1546W: FILESYSTEM_DBPATH_LESS_1GB
The available space in the directory where the server database files are
located is less than 1 GB.
When a Tivoli Storage Manager server is created with the DSMSERV
FORMAT utility or with the configuration wizard, a server database and
recovery log are also created. In addition, files are created to hold database
information used by the database manager. The path specified in this
message indicates the location of the database information used by the
database manager. If space is unavailable in the path, the server can no
longer function.
You must add space to the file system or make space available on the file
system or disk.

Server naming best practices

Use these descriptions as a reference when you install or upgrade a Tivoli Storage
Manager server.

Instance user ID

The instance user ID is used as the basis for other names related to the server
instance. The instance user ID is also called the instance owner.

For example: tsminst1

The instance user ID is the user ID that must have ownership or read/write access
authority to all directories that you create for the database and the recovery log.
The standard way to run the server is under the instance user ID. That user ID
must also have read/write access to the directories that are used for any FILE
device classes.

Home directory for the instance user ID

The home directory can be created when creating the instance user ID, by
using the option (-m) to create a home directory if it does not exist already.
Depending on local settings, the home directory might have the form:
/home/instance_user_ID
For example: /home/tsminst1
The home directory is primarily used to contain the profile for the user ID
and for security settings.

Database instance name

The database instance name must be the same as the instance user ID
under which you run the server instance.
For example: tsminst1

Instance directory

The instance directory is a directory that contains files specifically for a server
instance (the server options file and other server-specific files). It can have any
name that you want. For easier identification, use a name that ties the directory to
the instance name.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 27

Installing the Tivoli Storage Manager server

You can create the instance directory as a subdirectory of the home

directory for the instance user ID. For example: /home/instance_user_ID/
instance_user_ID
The following example places the instance directory in the home directory
for user ID tsminst1: /home/tsminst1/tsminst1
You can also create the directory in another location, for example:
/tsmserver/tsminst1
The instance directory stores the following files for the server instance:
v The server options file, dsmserv.opt
v The server key database file, cert.kdb, and the .arm files (used by clients
and other servers to import the Secure Sockets Layer certificates of the
server)
v Device configuration file, if the DEVCONFIG server option does not specify
a fully qualified name
v Volume history file, if the VOLUMEHISTORY server option does not specify a
fully qualified name
v Volumes for DEVTYPE=FILE storage pools, if the directory for the
device class is not fully specified, or not fully qualified
v User exits
v Trace output (if not fully qualified)

Database name

The database name is always TSMDB1, for every server instance. This name cannot
be changed.

Server name

The server name is an internal name for Tivoli Storage Manager, and is used for
operations that involve communication among multiple Tivoli Storage Manager
servers. Examples include server-to-server communication and library sharing.

The server name is also used when you add the server to the Operations Center so
that it can be managed using that interface. Use a unique name for each server. For
easy identification in the Operations Center (or from a QUERY SERVER command),
use a name that reflects the location or purpose of the server. Do not change the
name of a Tivoli Storage Manager server after it is configured as a hub or spoke
server.

If you use the wizard, the default name that is suggested is the host name of the
system that you are using. You can use a different name that is meaningful in your
environment. If you have more than one server on the system and you use the
wizard, you can use the default name for only one of the servers. You must enter a
unique name for each server.

For example:
PAYROLL
SALES

28 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Directories for database space and recovery log

The directories can be named according to local practices. For easier identification,
consider using names that tie the directories to the server instance.

For example, for the archive log:

/tsminst1_archlog

Installation directories
Installation directories for the Tivoli Storage Manager server include the server,
DB2, device, language, and other directories. Each one contains several additional
directories.

The default directories and their subdirectories are listed here for the server, DB2,
devices, and languages:
v Server directory (/opt/tivoli/tsm/server/bin), which contains:
– Server code and licensing
v Additional server directories:
– The command and message help are located in the /opt/tivoli/tsm/server/
bin/lang directory, where lang is the language that you use to run the server.
v DB2 directories
The DB2 product that is installed as part of the installation of the Tivoli Storage
Manager server has the directory structure as documented in DB2 information
sources. Protect these directories and files as you do the server directories.
– /opt/tivoli/tsm/db2
v Device directories
– /opt/tivoli/tsm/devices/bin
– /usr/lib/drivers
– /usr/lib/methods
v Language directory
Language-dependent portions of the program are located here:
/opt/tivoli/tsm/server/bin/lang, where lang is the language that you use to
run the server.
You can use US English, German, French, Italian, Spanish, Brazilian Portuguese,
Korean, Japanese, traditional Chinese, simplified Chinese, Chinese GBK, Chinese
Big5, and Russian.

Chapter 1. Planning to install the IBM Tivoli Storage Manager server 29

Installing the Tivoli Storage Manager server

30 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 2. Installing the Tivoli Storage Manager server
components
To install the Tivoli Storage Manager 7.1.1 server, you can use the installation
wizard, the command line in console mode, or by using silent mode.

About this task

Planning to install Installing components Taking the first steps

Using the Tivoli Storage Manager installation software, you can install the
following components:
v Tivoli Storage Manager Server

Tip: The database (DB2) and the Global Security Kit (GSKit) are automatically
installed when you select the server component.
v Tivoli Storage Manager Server Languages
v Tivoli Storage Manager License
v Tivoli Storage Manager Devices
v Tivoli Storage Manager Storage Agent
v Tivoli Storage Manager Operations Center

Obtaining the Tivoli Storage Manager installation package

You can obtain the Tivoli Storage Manager installation package from a DVD or an
IBM download site such as IBM Passport Advantage®.

Before you begin

If you plan to download the files, set the system user limit for maximum file size
to unlimited to ensure that the files can be downloaded correctly:
1. To query the maximum file size value, issue the following command:
ulimit -Hf
2. If the system user limit for maximum file size is not set to unlimited, change it
to unlimited by following the instructions in the documentation for your
operating system.

Procedure
1. Download the appropriate package file from one of the following websites, or
you can access the files from the product DVD:
v For a first time installation or a new release go to Passport Advantage at:
http://www.ibm.com/software/lotus/passportadvantage/. Passport
Advantage is the only site that you can download a licensed package file
from.
v For the latest information, updates, and maintenance fixes, go to the Tivoli
Storage Manager support site: http://www.ibm.com/support/entry/portal/
Overview/Software/Tivoli/Tivoli_Storage_Manager.

© Copyright IBM Corp. 1993, 2014 31

 Installing the Tivoli Storage Manager server

2. If you downloaded the package from an IBM download site, complete the
following steps:
a. Verify that you have enough space to store the installation files when they
are extracted from the product package. See the download document for the
space requirements:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035122
v Tivoli Storage Manager Extended Edition: http://www.ibm.com/
support/docview.wss?uid=swg24035635
v System Storage® Archive Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The path must
contain no more than 128 characters. Be sure to extract the installation files
to an empty directory. Do not extract to a directory that contains previously
extracted files, or any other files.
c. Ensure that executable permission is set for the package. If necessary,
change the file permissions by issuing the following command:
chmod a+x package_name.bin
d. Extract the package by issuing the following command:
./package_name.bin
where package_name is the name of the downloaded file, for example:
| 7.1.1.000-TIV-TSMSRV-AIX.bin
3. Ensure that the following command is enabled so that the Tivoli Storage
Manager wizards work properly:
lsuser
By default, the command is enabled.
4. Select one of the following methods of installing Tivoli Storage Manager:
v “Installing Tivoli Storage Manager by using the installation wizard”
v “Installing Tivoli Storage Manager by using console mode” on page 35
v “Installing Tivoli Storage Manager in silent mode” on page 36
5. After you install Tivoli Storage Manager, and before you customize it for your
use, go to the following website: http://www.ibm.com/support/entry/portal/
Overview/Software/Tivoli/Tivoli_Storage_Manager. Click Support and
downloads and apply any applicable fixes.

Installing Tivoli Storage Manager by using the installation wizard

You can install Tivoli Storage Manager by using the IBM Installation Manager
graphical wizard.

Before you begin

Take the following actions before you start the installation:

v If the following RPM files are not installed on your system, you must install
them. For instructions, see “Installing Prerequisite RPM files for the graphical
wizard” on page 34.
atk-1.12.3-2.aix5.2.ppc.rpm
cairo-1.8.8-1.aix5.2.ppc.rpm
expat-2.0.1-1.aix5.2.ppc.rpm
fontconfig-2.4.2-1.aix5.2.ppc.rpm

32 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

freetype2-2.3.9-1.aix5.2.ppc.rpm
gettext-0.10.40-6.aix5.1.ppc.rpm
glib2-2.12.4-2.aix5.2.ppc.rpm
gtk2-2.10.6-4.aix5.2.ppc.rpm
libjpeg-6b-6.aix5.1.ppc.rpm
libpng-1.2.32-2.aix5.2.ppc.rpm
libtiff-3.8.2-1.aix5.2.ppc.rpm
pango-1.14.5-4.aix5.2.ppc.rpm
pixman-0.12.0-3.aix5.2.ppc.rpm
xcursor-1.1.7-3.aix5.2.ppc.rpm
xft-2.1.6-5.aix5.1.ppc.rpm
xrender-0.9.1-3.aix5.2.ppc.rpm
zlib-1.2.3-3.aix5.1.ppc.rpm
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the installation
wizard.

| On test servers only: Use the following command to bypass prerequisite checks
| such as the operating system and the required memory. Do not issue this
| command on a production server.
| For new installations, issue the following command:
| ./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

| Otherwise, update the following file to add the -DBYPASS_TSM_REQ_CHECKS=true

| flag. The dash in the -DBYPASS_TSM_REQ_CHECKS=true flag is required and must be
| added on a new line after the -vmargs flag.
| ../Installation Manager/eclipse/ibmim.ini

| Procedure

Install Tivoli Storage Manager by using one of the following methods:

Option Description
Installing the software from a downloaded 1. Change to the directory where you
package: downloaded the package.
2. Start the installation wizard by issuing
the following command:
./install.sh

Installing the software from a DVD: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard by issuing
the following command from a
command line:
./install.sh

Chapter 2. Installing the Tivoli Storage Manager server components 33

Installing the Tivoli Storage Manager server

What to do next
v If errors occur during the installation process, the errors are recorded in log files
that are stored in the IBM Installation Manager logs directory.
You can view installation log files by clicking File > View Log from the
Installation Manager tool. To collect these log files, click Help > Export Data for
Problem Analysis from the Installation Manager tool.
v After you install Tivoli Storage Manager, and before you customize it for your
use, go to the following website: http://www.ibm.com/support/entry/portal/
Overview/Software/Tivoli/Tivoli_Storage_Manager. Click Support and
downloads and apply any applicable fixes.
v After you install a new Tivoli Storage Manager server, review Taking the first
steps after you install Tivoli Storage Manager to learn about configuring your
server.
Related reference:
Drivers for non IBM devices (http://www.ibm.com/support/
knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
r_device_drivers_nonibm_win.html)

Installing Prerequisite RPM files for the graphical wizard

Before you can use the graphical wizard of IBM Installation Manager to install
Tivoli Storage Manager, you must ensure that the necessary RPM files are installed.

About this task

If the RPM files that are listed in “Installing Tivoli Storage Manager by using the
installation wizard” on page 32 are not installed, you must download and install
the files.

Procedure

To install the necessary RPM files, complete the following steps:

1. Ensure that there is at least 150 MB of free space in the /opt file system.
2. To install the RPM files, choose one of the following options:
v If you plan to install Tivoli Storage Manager from the product DVD, take the
following actions:
a. In the base directory of the DVD, change to the gtk directory.
b. From the gtk directory, copy the download-prerequisites.sh file to a
location where you can download the RPM files.
v If you obtained the Tivoli Storage Manager installation package from an IBM
download site such as IBM Passport Advantage or the Tivoli Storage
Manager support site, take the following action:
From the directory where the installation package file is extracted, go to
the gtk directory.
3. Download the RPM files to the current working directory from the IBM AIX
Toolbox for Linux Applications website, by issuing the following command:
download-prerequisites.sh
4. From the directory that contains the RPM files that you downloaded, install
them by issuing the following command:
rpm -Uvh *.rpm
If a message indicates that one of the files is already installed on the system,
take one of the following actions:

34 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

v Issue the following command:

rpm -Uvh --force *.rpm
v Move the earlier versions of the files to a different directory, and issue the
rpm command again, as shown in the following example:
mkdir already-installed
mv *.rpm already-installed
rpm -Uvh *.rpm

Installing Tivoli Storage Manager by using console mode

You can install Tivoli Storage Manager by using the command line in console
mode.

| Before you begin

| Take the following actions before you start the installation:

| v Verify that the operating system is set to the language that you require. By
| default, the language of the operating system is the language of the installation
| wizard.

| On test servers only: Use the following command to bypass prerequisite checks
| such as the operating system and the required memory. Do not issue this
| command on a production server.
| For new installations, issue the following command:
| ./install.sh -c -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

| Otherwise, update the following file to add the -DBYPASS_TSM_REQ_CHECKS=true

| flag. The dash in the -DBYPASS_TSM_REQ_CHECKS=true flag is required and must be
| added on a new line after the -vmargs flag.
| ../Installation Manager/eclipse/tools/imcl.ini

| Procedure

Install Tivoli Storage Manager by using one of the following methods:

Option Description
Installing the software from a downloaded 1. Change to the directory where you
package: downloaded the package.
2. Start the installation wizard in console
mode by issuing the following
command:
./install.sh -c
3.
Optional: Generate a response file as
part of a console mode installation.
Complete the console mode installation
options, and in the Summary panel,
specify G to generate the responses.

Chapter 2. Installing the Tivoli Storage Manager server components 35

 Installing the Tivoli Storage Manager server

Option Description
Installing the software from a DVD: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard in console
mode by issuing the following
command:
./install.sh -c
3.
Optional: Generate a response file as
part of a console mode installation.
Complete the console mode installation
options, and in the Summary panel,
specify G to generate the responses.

What to do next
| v If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory, for example:
| /var/ibm/InstallationManager/logs
v After you install Tivoli Storage Manager, and before you customize it for your
use, go to the following website: http://www.ibm.com/support/entry/portal/
Overview/Software/Tivoli/Tivoli_Storage_Manager. Click Support and
downloads and apply any applicable fixes.
v After you install a new Tivoli Storage Manager server, review the information in
Taking the first steps after you install Tivoli Storage Manager to learn about
configuring your server.
Related reference:
Drivers for non IBM devices (http://www.ibm.com/support/
knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
r_device_drivers_nonibm_win.html)

Installing Tivoli Storage Manager in silent mode

You can install the IBM Tivoli Storage Manager server in silent mode without any
user interaction.

| Before you begin

| A silent installation can use response files for data input. The input directory,
| which is in the directory where the installation package was extracted, contains the
| following sample response files to install, update, and uninstall Tivoli Storage
| Manager:
| v install_response_sample.xml
| v update_response_sample.xml
| v uninstall_response_sample.xml

| You can use these sample files as they are or you can customize them to suit your
| needs. It is optimal to use the sample response files. These sample files contain
| instructions and default values to help you avoid any unnecessary warnings.

36 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

| On test servers only: Use the following command to bypass prerequisite checks
| such as the operating system and the required memory. Do not issue this
| command on a production server.

| For new installations, issue the following command:

| ./install.sh -s -acceptLicense -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

| Otherwise, update the following file to add the -DBYPASS_TSM_REQ_CHECKS=true

| flag. The dash in the -DBYPASS_TSM_REQ_CHECKS=true flag is required and must be
| added on a new line after the -vmargs flag.
| ../Installation Manager/eclipse/tools/imcl.ini

Procedure
1. Create a response file, or use one of the sample response files, such as
install_response_sample.xml or update_response_sample.xml.
2. Start the silent installation, by issuing the following command from the
directory where the installation package is extracted:

Option Description
Installing the software from To start the installation with a custom response file, issue
a downloaded package file the following command, where response_file is the response
or DVD media: file path, including the file name:
./install.sh -s -input response_file -acceptLicense

What to do next
| v If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory, for example:
| /var/ibm/InstallationManager/logs
v After you install Tivoli Storage Manager, and before you customize it for your
use, go to the following website: http://www.ibm.com/support/entry/portal/
Overview/Software/Tivoli/Tivoli_Storage_Manager. Click Support and
downloads and apply any applicable fixes.
v After you install a new Tivoli Storage Manager server, review the information in
Taking the first steps after you install Tivoli Storage Manager to learn about
configuring your server.
Related reference:
Drivers for non IBM devices (http://www.ibm.com/support/
knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
r_device_drivers_nonibm_win.html)

Installing server language packages

Translations for the IBM Tivoli Storage Manager server allow the server to display
messages and help in languages other than U.S. English. The translations also
allow for the use of locale conventions for date, time, and number formatting.

Chapter 2. Installing the Tivoli Storage Manager server components 37

Installing the Tivoli Storage Manager server

Server language locales

Use either the default language package option or select another language package
to display server messages and help.

This language package is automatically installed for the following default language
option for Tivoli Storage Manager server messages and help:
v LANGUAGE en_US

For languages or locales other than the default, install the language package that
your installation requires.

You can use the languages that are shown:

Table 12. Server languages for AIX
Language LANGUAGE option value
Chinese, Simplified zh_CN
Chinese, Simplified (UTF-8) ZH_CN
Chinese, Traditional (Big5) Zh_TW
Chinese, Traditional (UTF-8) ZH_TW
Chinese, Traditional (euc_tw) zh_TW
English en_US
English (UTF-8) EN_US
French fr_FR
French (UTF-8) FR_FR
German de_DE
German (UTF-8) DE_DE
Italian it_IT
Italian (UTF-8) IT_IT
Japanese, EUC ja_JP
Japanese, PC Ja_JP
Japanese, UTF8 JA_JP
Korean ko_KR
Korean (UTF-8) KO_KR
Portuguese, Brazilian pt_BR
Portuguese, Brazilian (UTF-8) PT_BR
Russian ru_RU
Russian (UTF-8) RU_RU
Spanish es_ES
Spanish (UTF-8) ES_ES
Note:
v For more information about setting the LANGUAGE option, see the Administrator's
Reference.

Restriction: For Operations Center users, some characters might not be displayed
properly if the web browser does not use the same language as the server. If this
problem occurs, set the browser to use the same language as the server.

38 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Configuring a language package

After you configure a language package, messages and help are shown on the
Tivoli Storage Manager in languages other than US English. Installation packages
are provided with Tivoli Storage Manager.

About this task

To set support for a certain locale, complete one of the following tasks:
v Set the LANGUAGE option in the server options file to the name of the locale that
you want to use. For example:
To use the it_IT locale, set the LANGUAGE option to it_IT. See “Server
language locales” on page 38.
v If you are starting the server in the foreground, set the LC_ALL environment
variable to match the value that is set in the server options file. For example, to
set the environment variable for Italian, enter the following value:
export LC_ALL=it_IT

If the locale is successfully initialized, it formats the date, time, and number for the
server. If the locale is not successfully initialized, the server uses the US English
message files and the date, time, and number format.

Updating a language package

You can modify or update a language package by using the IBM Installation
Manager.

About this task

You can install another language package within the same Tivoli Storage Manager
instance.
v Use the Modify function of IBM Installation Manager to install another language
package.
v Use the Update function of IBM Installation Manager to update to newer
versions of the language packages.

Tip: In IBM Installation Manager, the term update means to discover and install
updates and fixes to installed software packages. In this context, update and upgrade
are synonymous.

Chapter 2. Installing the Tivoli Storage Manager server components 39

Installing the Tivoli Storage Manager server

40 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 3. Taking the first steps after you install Tivoli
Storage Manager
After you install Tivoli Storage Manager Version 7.1.1, prepare for the
configuration. Using the configuration wizard is the preferred method of
configuring the Tivoli Storage Manager instance.

About this task

Planning to install Installing components Taking the first steps

Figure 2. You are in the configuring the Tivoli Storage Manager server section.

Configure the Tivoli Storage Manager server instance by completing the following
steps:
1. Create the directories and user ID for the server instance. See “Creating the
user ID and directories for the server instance” on page 42.
2. Configure a Tivoli Storage Manager instance. Select one of the following
options:
v Use the Tivoli Storage Manager configuration wizard, the preferred method.
See “Configuring Tivoli Storage Manager using the configuration wizard” on
page 44.
v Manually configure the new Tivoli Storage Manager instance. See
“Configuring the server instance manually” on page 44. Complete the
following steps during a manual configuration.
a. Set up your directories and create the Tivoli Storage Manager instance.
See “Creating the server instance” on page 45.
b. Create a new server options file by copying the sample file to set up
communications between the server and clients. See “Configuring server
and client communications” on page 46.
c. Issue the DSMSERV FORMAT command to format the database. See
“Formatting the database and log” on page 50.
d. Configure your system for database backup. See “Preparing the database
manager for database backup” on page 50.
3. Configure options to control when database reorganization runs. See
“Configuring server options for server database maintenance” on page 53.
4. Start the Tivoli Storage Manager server instance if it is not already started.
See “Starting the server instance” on page 54.
5. Register your license. See “Registering licenses” on page 58.
6. Prepare your system for database backups. See “Specifying a device class in
preparation for database backups” on page 59.
7. Monitor the server. See “Monitoring the server” on page 60.

© Copyright IBM Corp. 1993, 2014 41

Installing the Tivoli Storage Manager server

Creating the user ID and directories for the server instance

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 you begin

Review the information about planning space for the server before you complete
this task. See “Worksheets for planning details for the Tivoli Storage Manager
server” on page 9.

Procedure
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. The following commands can be run from an administrative user ID
that will set up the user and group. Create the user ID and group in
the home directory of the user.

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:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a
numeral.
v 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
using operating system commands.
mkgroup id=1001 tsmsrvrs
mkuser id=1002 pgrp=tsmsrvrs home=/home/tsminst1 tsminst1
passwd tsminst1

Restriction: DB2 does not support direct operating system user

authentication through LDAP.
b. Log off, then log in to your system. Change to the user account that
you just created. Use an interactive login program, such as telnet, so
that you are prompted for the password and can change it if
necessary.
2. Create directories that the server requires.

42 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Create empty directories for each item in the table and ensure that the directories are
owned by the new user ID you just created. Mount the associated storage to each directory
for the active log, archive log, and database directories.
Example commands for
Item creating the directories Your directories
The instance directory for mkdir /tsminst1
the server, which is a
directory that will
contain files specifically
for this server instance
(the server options file
and other server-specific
files)
The database directories mkdir /tsmdb001
mkdir /tsmdb002
mkdir /tsmdb003
mkdir /tsmdb004
Active log directory mkdir /tsmlog
Archive log directory mkdir /tsmarchlog
Optional: Directory for mkdir /tsmlogmirror
the log mirror for the
active log
Optional: Secondary mkdir /tsmarchlogfailover
archive log directory
(failover location for
archive log)

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. Log off the new user ID.

Configuring Tivoli Storage Manager

After you have installed Tivoli Storage Manager Version 7.1.1 and prepared for the
configuration, configure the Tivoli Storage Manager server instance.

About this task

Configure a Tivoli Storage Manager server instance by selecting one of the

following options:
v Use the Tivoli Storage Manager configuration wizard on your local system. See
“Configuring Tivoli Storage Manager using the configuration wizard” on page
44.
v Manually configure the new Tivoli Storage Manager instance. See “Configuring
the server instance manually” on page 44. Complete the following steps during
a manual configuration.
1. Set up the directories and create the Tivoli Storage Manager instance. See
“Creating the server instance” on page 45.
2. Create a new server options file by copying the sample file in order to set up
communications between the Tivoli Storage Manager server and clients. See
“Configuring server and client communications” on page 46.

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 43
 Installing the Tivoli Storage Manager server

3. Issue the DSMSERV FORMAT command to format the database. See

“Formatting the database and log” on page 50.
4. Configure your system for database backup. See “Preparing the database
manager for database backup” on page 50.

Configuring Tivoli Storage Manager using the configuration

wizard
The wizard offers a guided approach to configuring a server. 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 you begin

Before you begin to use the configuration wizard, you must complete all preceding
steps to prepare for the configuration. These steps include installing Tivoli Storage
Manager, creating the database and log directories, and creating the directories and
user ID for the server instance.

About this task

Procedure
1. Ensure that the following requirements are met:
v 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.
| v The system must have the Secure Shell (SSH) protocol enabled. Ensure that
| the port is set to the default value, 22, and that the port is not blocked by a
| firewall. You must enable password authentication in the sshd_config file in
| the /etc/ssh/ directory. Also, ensure that the SSH daemon service has access
| rights for connecting to the system by using the localhost value.
| v 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 protocol. When you use
| the wizard, you must provide this user ID and password to access that
| system.
2. Start the local version of the wizard:
Open the dsmicfgx program in the /opt/tivoli/tsm/server/bin directory.
This wizard can be only 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.

Configuring the server instance manually

After installing Tivoli Storage Manager Version 7.1.1, you can configure Tivoli
Storage Manager manually instead of using the configuration wizard.

44 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Creating the server instance

Create a Tivoli Storage Manager instance by issuing the db2icrt command.

About this task

You can have one or more server instances on one workstation.

Important: Before you run the db2icrt command, verify the following items:
v 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 (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 not fully qualified)
v 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, see the DB2 product documentation at http://www.ibm.com/
support/knowledgecenter/SSEPGG_10.5.0. Search for Linux and UNIX
environment variable settings.
1. Log in using the root user ID and create a Tivoli Storage Manager instance. The
name of the instance must be the same name as the user that owns the
instance. Use the db2icrt command and enter the command on one line:
/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u
instance_name instance_name

For example, if your user ID for this instance is tsminst1, use the following
command to create the instance. Enter the command on one line.
/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 your
Tivoli Storage Manager server. Log out of the root user ID and log in under the
new instance-user ID.
2. Change the default directory for the database to be the same as the instance
directory for the server. If you have multiple servers, log in under the instance
ID for each server. Issue this command:
db2 update dbm cfg using dftdbpath instance_directory

For example:
db2 update dbm cfg using dftdbpath /tsminst1
3. Modify the library path to use the version of the IBM Global Security Kit
(GSKit) that is installed with the Tivoli Storage Manager server. In the

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 45
 Installing the Tivoli Storage Manager server

following examples, server_bin_directory is a subdirectory of the server

installation directory. For example, /opt/tivoli/tsm/server/bin.
| v Issue the following command, on one line:
| export LIBPATH=server_bin_directory/dbbkapi:
| /usr/opt/ibm/gsk8_64/lib64:$LIBPATH
v You must update the following files to set the library path when DB2 or the
Tivoli Storage Manager server are started:
| instance_users_home_directory/sqllib/usercshrc
| instance_users_home_directory/sqllib/userprofile
| v Add the following entry to the instance_users_home_directory/sqllib/
| usercshrc file, on one line:
| setenv LIBPATH server_bin_directory/dbbkapi:
| /usr/opt/ibm/gsk8_64/lib64:$LIBPATH
| v Add the following entry to the instance_users_home_directory/sqllib/
| userprofile file. Each entry is on one line.
| LIBPATH=server_bin_directory/dbbkapi:
| /usr/opt/ibm/gsk8_64/lib64:$LIBPATH
| export LIBPATH
| v Verify the library path settings and that the GSKit is version 8.0.14.43 or later.
| Issue the following commands:
| echo $LIBPATH
| gsk8capicmd_64 -version
| gsk8ver_64
| If your 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.
4. Create a new server options file. See “Configuring server and client
communications.”

Configuring server and client communications

A default sample server options file, dsmserv.opt.smp, is created during Tivoli
Storage Manager installation in the /opt/tivoli/tsm/server/bin directory. You
must set up communications between the server and clients by creating a new
server options file. To do so, copy the sample file to the directory for the server
instance.

About this task

Ensure that you have a server instance directory, for example /tsminst1, and copy
the sample file to this directory. Name the new file dsmserv.opt and edit the
options. Complete this set-up before you initialize the server database. Each
sample or default entry in the sample options file is a comment, a line beginning
with an asterisk (*). Options are not case-sensitive and one or more blank spaces
are allowed between keywords and values.

When editing the options file, follow these guidelines:

v Remove the asterisk at the beginning of the line to activate an option.
v Begin entering the options in any column.
v Enter only one option per line, and the option must be on only one line.
v If you make multiple entries for a keyword, the Tivoli Storage Manager server
uses the last entry.

46 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

If you change the server options file, you must restart the server for the changes to
take effect.

You can specify one or more of the following communication methods:

v TCP/IP Version 4 or Version 6
v Shared memory
v Simple network management protocol (SNMP) DPI
v Secure Sockets Layer (SSL)

Note: You can authenticate passwords with the LDAP directory server, or
authenticate passwords with the Tivoli Storage Manager server. Passwords that
are authenticated with the LDAP directory server can provide enhanced system
security. For details, see the managing passwords and logon procedures section
in the Administrator's Guide.

Setting TCP/IP options:

Select from a range of TCP/IP options for the Tivoli Storage Manager server or
retain the default.

About this task

The following is an example of a list of TCP/IP options you can use to set up your
system.
commmethod tcpip
tcpport 1500
tcpwindowsize 0
tcpnodelay yes

Tip: You can use TCP/IP Version 4, Version 6, or both.

TCPPORT
The server TCP/IP port address. The default value is 1500.
TCPWINDOWSIZE
Specifies the size of the TCP/IP buffer that is used when sending or
receiving data. The window size that is used in a session is the smaller of
the server and client window sizes. Larger window sizes use additional
memory but can improve performance.
You can specify an integer from 0 to 2048. To use the default window size
for the operating system, specify 0.
TCPNODELAY
Specifies whether or not the server sends small messages or lets TCP/IP
buffer the messages. Sending small messages can improve throughput but
increases the number of packets sent over the network. Specify YES to
send small messages or NO to let TCP/IP buffer them. The default is YES.
TCPADMINPORT
Specifies the port number on which the server TCP/IP communication
driver is to wait for requests other than client sessions. The default value is
1500.
SSLTCPPORT
(SSL-only) Specifies the Secure Sockets Layer (SSL) port number on which

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 47
Installing the Tivoli Storage Manager server

the server TCP/IP communication driver waits for requests for

SSL-enabled sessions for the command-line backup-archive client and the
command-line administrative client.
SSLTCPADMINPORT
Specifies the port address on which the server TCP/IP communication
driver waits for requests for SSL-enabled sessions for the command-line
administrative client.

Setting shared memory options:

You can use shared memory communications between clients and servers on the
same system. To use shared memory, TCP/IP Version 4 must be installed on the
system.

About this task

The following example shows a shared memory setting:

commmethod sharedmem
shmport 1510

In this example, SHMPORT specifies the TCP/IP port address of a server when using
shared memory. Use the SHMPORT option to specify a different TCP/IP port. The
default port address is 1510.

COMMMETHOD can be used multiple times in the Tivoli Storage Manager server
options file, with a different value each time. For example, the following example
is possible:
commmethod tcpip
commmethod sharedmem

The maximum number of concurrent shared memory sessions is based on available

system resources. Each shared memory session uses one shared memory region of
up to 4 MB, and four IPCS message queues, depending on the Tivoli Storage
Manager client level.

If the server and client are not run under the same user ID, then the server must
be root. This prevents shared memory communication errors.

Setting SNMP DPI subagent options:

Tivoli Storage Manager implements a simple network management protocol

(SNMP) subagent. You can configure the SNMP subagent to send traps to an
SNMP manager, such as NetView®, and to provide support for a Management
Information Base (MIB).

About this task

For details about configuring SNMP for use with Tivoli Storage Manager, see the
Administrator's Guide.

The subagent communicates with the snmp daemon, which in turn communicates
with a management application. The snmp daemon must support the DPI protocol.
Agents are available on AIX. The subagent process is separate from the Tivoli

48 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Storage Manager server process, but the subagent gets its information from a
server options file. When the SNMP management application is enabled, it can get
information and messages from servers.

Use the following SNMP DPI options as an example of a SNMP setting. You must
specify the COMMMETHOD option. For details about the other options, see the
Administrator's Reference.
commmethod snmp
snmpheartbeatinterval 5
snmpmessagecategory severity

Setting Secure Sockets Layer options:

You can add more protection for your data and passwords by using Secure Sockets
Layer (SSL).

Before you begin

SSL is the standard technology for creating encrypted sessions between servers and
clients. SSL provides a secure channel for servers and clients to communicate over
open communication paths. With SSL, the identity of the server is verified through
the use of digital certificates.

To ensure better system performance, use SSL only for sessions when it is needed.
Consider adding additional processor resources on the Tivoli Storage Manager
server to manage the increased requirements.

Refer to setting up Transport Layer Security (TLS) in the Administrator's Guide.

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 49
Installing the Tivoli Storage Manager server

Formatting the database and log

Use the DSMSERV FORMAT utility to initialize a server instance. No other server
activity is allowed while initializing the database and recovery log.

After you set up server communications, you are ready to initialize the database.
Ensure that you log in by using the instance user ID. Do not place the directories
on file systems that might run out of space. If certain directories (for example, the
archive log) become unavailable or full, the server stops. See Capacity planning for
more details.

For optimal performance and to facilitate I/O, specify at least two equally sized
containers or Logical Unit Numbers (LUNs) for the database. See IBM Tivoli
Storage Manager Optimizing Performance (http://www.ibm.com/support/
knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.perf.doc/c_howtouseinfo.html) for
more information about the configuration of directories for the database. In
addition, each active log and archive log should have its own container or LUN.

Initializing a server instance

Use the DSMSERV FORMAT utility to initialize a server instance. For example, issue the
following command:
dsmserv format dbdir=/tsmdb001 activelogsize=8192
activelogdirectory=/activelog archlogdirectory=/archlog
archfailoverlogdirectory=/archfaillog mirrorlogdirectory=/mirrorlog

Tip: If DB2 does not start after you issue the DSMSERV FORMAT command, you might
need to disable the file system mount option NOSUID. If this option is set on the file
system that contains the DB2 instance owner directory, or on any file system that
contains the DB2 database, active logs, archive logs, failover logs, or mirrored logs,
the option must be disabled to start the system.

After you disable the NOSUID option, remount the file system and then start DB2 by
issuing the following command:
db2start
Related reference:
DSMSERV FORMAT (Format the database and log) (http://www.ibm.com/
support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.ref.doc/
r_cmd_dsmserv_format.html)

Preparing the database manager for database backup

To back up the data in the database to Tivoli Storage Manager, you must enable
the database manager and configure the Tivoli Storage Manager application
programming interface (API).

About this task

Starting with Tivoli Storage Manager V7.1, it is no longer necessary to set the API
password during a manual configuration of the server. If you set the API password
during the manual configuration process, attempts to back up the database might
fail.

If you use the Tivoli Storage Manager configuration wizard to create a Tivoli
Storage Manager server instance, you do not have to complete these steps. If you
are configuring an instance manually, complete the following steps before you
issue either the BACKUP DB or the RESTORE DB commands.

50 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Attention: If the database is unusable, the entire Tivoli Storage Manager server is
unavailable. If a database is lost and cannot be recovered, it might be difficult or
impossible to recover data that is managed by that server. Therefore, it is critically
important to back up the database.

In the following commands, replace the example values with your actual values.
The examples use tsminst1 for the server instance user ID, /tsminst1 for the Tivoli
Storage Manager server instance directory, and /home/tsminst1 as the server
instance users home directory.
1. Set the Tivoli Storage Manager API environment-variable configuration for the
database instance:
a. Log in by using the tsminst1 user ID.
b. When user tsminst1 is logged in, ensure that the DB2 environment is
properly initialized. The DB2 environment is initialized by running the
/home/tsminst1/sqllib/db2profile script, which normally runs
automatically from the profile of the user ID. Ensure the .profile file exists
in the instance users home directory, for example, /home/tsminst1/.profile.
If .profile does not run the db2profile script, add the following lines:
if [ -f /home/tsminst1/sqllib/db2profile ]; then
. /home/tsminst1/sqllib/db2profile
fi
c. In the instance_directory/sqllib/userprofile file, add the following lines:
DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
DSMI_DIR=server_bin_directory/dbbkapi
DSMI_LOG=server_instance_directory
export DSMI_CONFIG DSMI_DIR DSMI_LOG

where:
v instance_directory is the home directory of the server instance user.
v server_instance_directory is the server instance directory.
v server_bin_directory is the server bin directory. The default location is
/opt/tivoli/tsm/server/bin.
In the instance_directory/sqllib/usercshrc file, add the following lines:
setenv DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
setenv DSMI_DIR=server_bin_directory/dbbkapi
setenv DSMI_LOG=server_instance_directory
2. Log off and log in again as tsminst1, or issue this command:
. ~/.profile

Tip: Ensure that you enter a space after the initial dot (.) character.
3. Create a file that is named tsmdbmgr.opt in the server_instance directory, which
is in the /tsminst1 directory in this example, and add the following line:
SERVERNAME TSMDBMGR_TSMINST1

Remember: The value for SERVERNAME must be consistent in the tsmdbmgr.opt

and dsm.sys files.
4. As root user, add the following lines to the Tivoli Storage Manager API dsm.sys
configuration file. By default, the dsm.sys configuration file is in the following
default location:
server_bin_directory/dbbkapi/dsm.sys

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 51
Installing the Tivoli Storage Manager server

servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
errorlogname /tsminst1/tsmdbmgr.log
nodename $$_TSMDBMGR_$$
where
v servername matches the servername value in the tsmdbmgr.opt file.
v commethod specifies the client API that is used to contact the server for
database backup. This value can be tcpip or sharedmem. For more
information about shared memory, see step 5..
v tcpserveraddr specifies the server address that the client API uses to contact
the server for database backup. To ensure that the database can be backed
up, this value must be localhost.
v tcpport specifies the port number that the client API uses to contact the server
for database backup. Ensure that you enter the same tcpport value that is
specified in the dsmserv.opt server options file.
v errorlogname specifies the error log where the client API logs errors that are
encountered during a database backup. This log is typically in the server
instance directory. However, this log can be placed in any location where the
instance user ID has write-permission.
v nodename specifies the node name that the client API uses to connect to the
server during a database backup. To ensure that the database can be backed
up, this value must be $$_TSMDBMGR_$$.
5. Optional: Configure the server to back up the database by using shared
memory. In this way, you might be able to reduce the processor load and
improve throughput. Complete the following steps:
a. Review the dsmserv.opt file. If the following lines are not in the file, add
them:
commmethod sharedmem
shmport port_number

where port_number specifies the port to be used for shared memory.

b. In the dsm.sys configuration file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport port_number

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port to be used for shared memory.

52 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Configuring server options for server database maintenance

To help avoid problems with database growth and server performance, the server
automatically monitors its database tables and reorganizes them when needed.
Before starting the server for production use, set server options to control when
reorganization runs. If you plan to use data deduplication, ensure that the option
to run index reorganization is enabled.

About this task

Table and index reorganization requires significant processor resources, active log
space, and archive log space. Because database backup takes precedence over
reorganization, select the time and duration for reorganization to ensure that the
processes do not overlap and reorganization can complete. For more information
about scheduling reorganization, see the Administrator's Guide.

If you update these server options while the server is running, you must stop and
restart the server before the updated values take effect.

Procedure
1. Modify the server options.
Edit the server options file, dsmserv.opt, in the server instance directory. Follow
these guidelines when you edit the server options file:
v To enable an option, remove the asterisk at the beginning of the line.
v Enter an option on any line.
v Enter only one option per line. The entire option with its value must be on
one line.
v If you have multiple entries for an option in the file, the server uses the last
entry.
To view available server options, see the sample file, dsmserv.opt.smp, in the
/opt/tivoli/tsm/server/bin directory.
2. If you plan to use data deduplication, enable the ALLOWREORGINDEX server
option. Add the following option and value to the server options file:
allowreorgindex yes
3. Set the REORGBEGINTIME and REORGDURATION server options to control when
reorganization starts and how long it runs. Select a time and duration so that
reorganization runs when you expect that the server is least busy. These server
options control both table and index reorganization processes.
a. Set the time for reorganization to start by using the REORGBEGINTIME server
option. Specify the time by using the 24-hour system. For example, to set
the start time for reorganization as 8:30 p.m., specify the following option
and value in the server options file:
reorgbegintime 20:30
b. Set the interval during which the server can start reorganization. For
example, to specify that the server can start reorganization for four hours
after the time set by the REORGBEGINTIME server option, specify the following
option and value in the server options file:
reorgduration 4
4. If the server was running while you updated the server options file, stop and
restart the server.
Related tasks:

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 53
 Installing the Tivoli Storage Manager server

Table and index reorganization schedules (http://www.ibm.com/support/

knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/t_db_reorg.html)
Related reference:
ALLOWREORGINDEX (http://www.ibm.com/support/knowledgecenter/
SSGSG7_7.1.1/com.ibm.itsm.srv.ref.doc/r_opt_server_allowreorgindex.html)
ALLOWREORGTABLE (http://www.ibm.com/support/knowledgecenter/
SSGSG7_7.1.1/com.ibm.itsm.srv.ref.doc/r_opt_server_allowreorgtable.html)
REORGBEGINTIME (http://www.ibm.com/support/knowledgecenter/
SSGSG7_7.1.1/com.ibm.itsm.srv.ref.doc/r_opt_server_reorgbegintime.html)
REORGDURATION (http://www.ibm.com/support/knowledgecenter/
SSGSG7_7.1.1/com.ibm.itsm.srv.ref.doc/r_opt_server_reorgduration.html)

Starting the server instance

You can start the Tivoli Storage Manager server by using the instance user ID or
the root user ID. You can also use the instance user ID or the root user ID to start
the server automatically.

Before you begin

Ensure that you set access permissions and user limits correctly. For instructions,
see “Verifying access rights and user limits” on page 55.

About this task

The preferred way to start the server is by using the instance user ID. By using the
instance user ID, you simplify the setup process and avoid potential issues.
However, in some cases, it might be necessary to start the server with the root user
ID. For example, you might want to use the root user ID to ensure that the server
can access specific devices.

Procedure

To start the server, take one of the following actions:

v Start the server by using the instance user ID.
For instructions, see “Starting the server from the instance user ID” on page 56.
v Start the server by using the root user ID.
| For instructions about authorizing root user IDs to start the server, see
| Authorizing root user IDs to start the server (http://www.ibm.com/support/
| knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
| t_srv_mng_authority_startsrv.html). For instructions about starting the server by
| using the root user ID, see Starting the server from the root user ID
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.srv.doc/t_srv_mng_startsrv_root.html).
v Start the server automatically.
For instructions, see “Automatically starting servers” on page 57.
For information about other options for starting the server, see Starting the server
on AIX, HP-UX, Linux, and Solaris (http://www.ibm.com/support/
knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
t_srv_mng_start_linux_unix.html).

54 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Verifying access rights and user limits

Before you start the server, verify access rights and user limits.

About this task

If you do not verify user limits, also known as ulimits, you might experience server
instability or a failure of the server to respond. You must also verify the
system-wide limit for the maximum number of open files. The system-wide limit
must be greater than or equal to the user limit.

Procedure
1. Verify that the server instance user ID has permissions to start the server.
2. For the server instance that you plan to start, ensure that you have authority to
read and write files in the server instance directory. Verify that the dsmserv.opt
file exists in the server instance directory, and that the file includes parameters
for the server instance.
3. If the server is attached to a tape drive, medium changer, or removable media
device, and you plan to start the server by using the instance user ID, grant
read/write access to the instance user ID for these devices. To set permissions,
take one of the following actions:
v If the system is dedicated to Tivoli Storage Manager and only the Tivoli
Storage Manager administrator has access, make the device special file
world-writable:
chmod +w /dev/rmtX
v If the system has multiple users, you can restrict access by making the Tivoli
Storage Manager instance user ID the owner of the special device files:
chmod u+w /dev/rmtX
v If multiple user instances are running on the same system, change the group
name, for example TAPEUSERS, and add each Tivoli Storage Manager
instance user ID to that group. Then, change the ownership of the device
special files to belong to the group TAPEUSERS, and make them
group-writable:
chmod g+w /dev/rmtX
4. Verify the following user limits based on the guidelines in the table.
Table 13. User limit (ulimit) values
User limit type Preferred value Command to query value
Maximum size of core files Unlimited ulimit -Hc
created
Maximum size of a data Unlimited ulimit -Hd
segment for a process
Maximum file size Unlimited ulimit -Hf
Maximum number of open 65536 ulimit -Hn
files
Maximum amount of Unlimited ulimit -Ht
processor time in seconds

To modify user limits, follow the instructions in the documentation for your
operating system.

Tip: If you plan to start the server automatically by using a script, you can set
the user limits in the script.

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 55
 Installing the Tivoli Storage Manager server

5. Ensure that the user limit of maximum user processes (the nproc setting) is set
to the minimum suggested value of 16384.
a. To verify the current user limit, issue the ulimit -Hu command by using the
instance user ID. For example:
[user@Machine ~]$ ulimit -Hu
16384
b. If the limit of maximum user processes is not set to 16384, set the value to
16384.
| Add the following line to the /etc/security/limits file:
| instance_user_id - nproc 16384

| where instance_user_id specifies the server instance user ID.

Starting the server from the instance user ID

To start the server from the instance user ID, log in with the instance user ID and
issue the appropriate command from the server instance directory.

Before you begin

Ensure that access rights and user limits are set correctly. For instructions, see
“Verifying access rights and user limits” on page 55.

Procedure
1. Log in to the system where Tivoli Storage Manager is installed by using the
instance user ID for the Tivoli Storage Manager server.
2. If you do not have a user profile that runs the db2profile script, issue the
following command:
. /home/tsminst1/sqllib/db2profile

Tip: For instructions about updating the user ID login script to run the
db2profile script automatically, see the DB2 documentation
(http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0).
3. Start the server by issuing the following command from the server instance
directory:
/usr/bin/dsmserv

Tip: The command runs in the foreground so that you can set an administrator
ID and connect to the server instance.
For example, if the name of the Tivoli Storage Manager server instance is
tsminst1 and the server instance directory is /tsminst1, you can start the
instance by issuing the following commands:
cd /tsminst1
. ~/sqllib/db2profile
/usr/bin/dsmserv

56 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Automatically starting servers

You can configure the server to start automatically at system startup. Use the
rc.dsmserv script, which is provided for this purpose.

Before you begin

Ensure that access rights and user limits are set correctly. For instructions, see
“Verifying access rights and user limits” on page 55.

About this task

The rc.dsmserv script is in the server installation directory, for example, in the
/opt/tivoli/tsm/server/bin directory.

Tip: If you used either the upgrade wizard or the configuration wizard, you might
have chosen to start the server automatically when the system is restarted. If you
selected that choice, an entry for starting the server was added automatically to the
/etc/inittab file.

Procedure

If you did not use a wizard to configure the Tivoli Storage Manager server, add an
entry to the /etc/inittab file for each server that you want to automatically start:
1. Set the run level to the value that corresponds to multiuser mode with
networking enabled. Typically, the run level to use is 2, 3, or 5, depending on
the operating system and its configuration. Ensure that the run level in the
/etc/inittab file matches the run level of the operating system. For more
information about multiuser mode and run levels, see the documentation for
your operating system.
2. On the rc.dsmserv command in the /etc/inittab file, specify the instance user
ID with the -u option, and the location of the server instance directory with the
-i option. If you want to start more than one server instance automatically, add
an entry for each server instance. To verify the syntax, see the documentation
for your operating system.

Tip: To automatically start a server instance with the root user ID, use the -U
option.

Example

For example, if the instance owner is tsminst1 and the server instance directory is
/home/tsminst1/tsminst1, add the following entry to /etc/inittab, on one line:
tsm1:2:once:/opt/tivoli/tsm/server/bin/rc.dsmserv -u tsminst1
-i /home/tsminst1/tsminst1 -q >/dev/console 2>&1

In this example, the ID for the process is tsm1, and the run level is set to 2.

If you have more than one server instance that you want to run, add an entry for
each server instance. For example, if you have instance owner IDs tsminst1 and
tsminst2, and instance directories /home/tsminst1/tsminst1 and
/home/tsminst2/tsminst2, add the following entries to /etc/inittab. Each entry is
on one line.

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 57
Installing the Tivoli Storage Manager server

tsm1:2:once:/opt/tivoli/tsm/server/bin/rc.dsmserv -u tsminst1
-i /home/tsminst1/tsminst1 -q >/dev/console 2>&1
tsm2:2:once:/opt/tivoli/tsm/server/bin/rc.dsmserv -u tsminst2
-i /home/tsminst2/tsminst2 -q >/dev/console 2>&1
Related reference:
Server startup script: rc.dsmserv (http://www.ibm.com/support/
knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.ref.doc/r_srv_rcscript.html)

Stopping the server

You can stop the server when needed to return control to the operating system. To
avoid losing administrative and client node connections, stop the server only after
current sessions are completed or canceled.

About this task

To stop the server, issue the following command from the Tivoli Storage Manager
command line:
halt

The server console stops.

If you cannot connect to the server with an administrative client and you want to
stop the server, you must cancel the process by using the kill command with the
process ID number (pid) that is displayed at initialization.

Important: Before you issue the kill command, ensure that you know the correct
process ID for the Tivoli Storage Manager server.
The dsmserv.v6lock file, in the directory from which the server is running, can be
used to identify the process ID of the process to kill. To display the file enter:
cat /instance_dir/dsmserv.v6lock

Issue the following command to stop the server:

kill -36 dsmserv_pid

where dsmserv_pid is the process ID number.

Registering licenses
Immediately register any Tivoli Storage Manager licensed functions that you
purchase so you do not lose any data after you start server operations, such as
backing up your data.

About this task

Use the REGISTER LICENSE command for this task.

Example: Register a license

Register the base Tivoli Storage Manager license.

register license file=tsmbasic.lic

58 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

Specifying a device class in preparation for database backups

To prepare the system for automatic and manual database backups, you must
specify the device class to be used.

Before you begin

Before you begin the setup, ensure that you have defined a tape or file device
class. See the defining device classes section of the Administrator's Guide.

About this task

To set up your system for database backups, issue the SET DBRECOVERY command to
specify a device class to be used for the backups. You can also change the device
class to be used for database backups with the SET DBRECOVERY command.

Perform the following setup procedure:

Procedure
1. If you did not use the configuration wizard (dsmicfgx) to configure the server,
ensure that you have completed the steps to manually configure the system for
database backups.
2. Select the device class to be used for backups of the database. Issue the
following command from a IBM Tivoli Storage Manager administrative
command line.
set dbrecovery device_class_name

The device class that you specify is used by the database manager for database
backups. If you do not specify a device class with the SET DBRECOVERY
command, the backup fails.

Example

For example, to specify that the DBBACK device class is to be used, issue this
command:
set dbrecovery dbback

What to do next

When you are ready to back up your database, see the BACKUP DB command in the
Administrator's Reference.

Running multiple server instances on a single system

You can create more than one server instance on your system. Each server instance
has its own instance directory, and database and log directories.

Multiply the memory and other system requirements for one server by the number
of instances planned for the system.

The set of files for one instance of the server is stored separately from the files
used by another server instance on the same system. Use the steps in “Creating the
server instance” on page 45 for each new instance, including creation of the new
instance user.

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 59
Installing the Tivoli Storage Manager server

To manage the system memory that is used by each server, use the DBMEMPERCENT
server option to limit the percentage of system memory. If all servers are equally
important, use the same value for each server. If one server is a production server
and other servers are test servers, set the value for the production server to a
higher value than the test servers.

When you upgrade from Tivoli Storage Manager V6.1, you must upgrade to V6.3
first, and then to V7.1.1. You can upgrade directly from either V6.2 or V6.3 to V7.1.
See the upgrade section (Chapter 5, “Upgrading to Tivoli Storage Manager Version
7.1.1,” on page 67) for more details. When you upgrade and have multiple servers
on your system, you must run the installation wizard only once. The installation
wizard collects the database and variables information for all of your original
server instances.

If you upgrade from Tivoli Storage Manager V6.2 or V6.3 to V7.1.1 and have
multiple servers on your system, all instances that exist in DB2 V9.7 are dropped
and recreated in DB2 V10.5. The wizard issues the db2 upgrade db dbname
command for each database. The database environment variables for each instance
on your system are also reconfigured during the upgrade process.

For information about the Server Initialization wizard, see the Tivoli Storage
Manager Administrator's Guide.
Related tasks:
Running multiple server instances on a single system (http://www.ibm.com/
support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
t_srv_mng_start_multi_unix.html)

Monitoring the server

When you start using the server in production, monitor the space used by the
server to ensure that the amount of space is adequate. Make adjustments as
needed.

Procedure
1. Monitor the active log, to ensure that the size is correct for the workload that is
handled by the server instance.
When the server workload is up to its typical expected level, and the space that
is used by the active log is 80 - 90% of the space that is available to the active
log directory, you might need to increase the amount of space. Whether you
need to increase the space depends on the types of transactions in the server's
workload, because transaction characteristics affect how the active log space is
used.
The following transaction characteristics can affect the space usage in the active
log:
v The number and size of files in backup operations
– Clients such as file servers that back up large numbers of small files can
cause large numbers of transactions that complete during a short period of
time. The transactions might use a large amount of space in the active log,
but for a short period of time.
– Clients such as a mail server or a database server that back up large
chunks of data in few transactions can cause small numbers of
transactions that take a long time to complete. The transactions might use
a small amount of space in the active log, but for a long period of time.

60 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Tivoli Storage Manager server

v Network connection types

– Backup operations that occur over fast network connections cause
transactions that complete more quickly. The transactions use space in the
active log for a shorter period of time.
– Backup operations that occur over relatively slower connections cause
transactions that take a longer time to complete. The transactions use
space in the active log for a longer period of time.
If the server is handling transactions with a wide variety of characteristics, the
space that is used for the active log might go up and down by a large amount
over time. For such a server, you might need to ensure that the active log
typically has a smaller percentage of its space used. The extra space allows the
active log to grow for transactions that take a very long time to complete, for
example.
2. Monitor the archive log to ensure that space is always available.

Remember: If the archive log becomes full, and the failover archive log
becomes full, the active log can become full and the server will stop. The goal
is to make enough space available to the archive log so that it never uses all its
available space.
You are likely to notice the following pattern:
a. Initially, the archive log grows rapidly as typical client-backup operations
occur.
b. Database backups occur regularly, either as scheduled or done manually.
c. After at least two full database backups occur, log pruning occurs
automatically. The space used by the archive log decreases when the
pruning occurs.
d. Normal client operations continue, and the archive log grows again.
e. Database backups occur regularly, and log pruning occurs as often as full
database backups occur.
With this pattern, the archive log grows initially, then decreases, then might
grow again. Over a period of time, as normal operations continue, the amount
of space used by the archive log should reach a relatively constant level.
If the archive log continues to grow, consider taking one or both of these
actions:
v Add space to the archive log. This might mean moving the archive log to a
different file system.
For information about moving the archive log, see the Tivoli Storage Manager
Administrator's Guide.
v Increase the frequency of full database backups, so that log pruning occurs
more frequently.
3. If you defined a directory for the failover archive log, determine whether any
logs get stored in that directory during normal operations. If the failover log
space is being used, consider increasing the size of the archive log. The goal is
that the failover archive log is used only under unusual conditions, not in
normal operation.

What to do next

For details about monitoring, see the Administrator's Guide.

Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7.1.1 61
62 IBM Tivoli Storage Manager for AIX: Installation Guide
Chapter 4. Installing a Tivoli Storage Manager server fix pack
Tivoli Storage Manager maintenance updates, which are also referred to as fix
packs, bring your server up to the current maintenance level.

Before you begin

To install a fix pack or interim fix to the server, install the server at the level on
which you want to run it. You do not have to start the server installation at the
base release level. For example, if you currently have Version 6.3.4.2 installed, you
can go directly to the latest fix pack for V7.1. You do not have to start with the
V7.1.0 installation if a maintenance update is available.

You must have the Tivoli Storage Manager license package installed. The license
package is provided with the purchase of a base release. Alternatively, you can
obtain the license package when download a fix pack from the Passport Advantage
website. After the fix pack or interim fix is installed, install the license for the
server. To display messages and help in a language other than US English, install
the language package of your choice.

For information about the estimated time required to install a fix pack, see Techdoc
7023591.

If you upgrade the server to V7.1 or later, and then revert the server to a level that
is earlier than V7.1, you must restore the database to a point in time before the
upgrade. During the upgrade process, complete the required steps to ensure that
the database can be restored: back up the database, the volume history file, the
device configuration file, and the server options file. For more information, see
Chapter 6, “Reverting from Version 7.1 to the previous V6 server,” on page 85.

Ensure that you retain the installation media from the base release of the installed
server. If you installed Tivoli Storage Manager from a DVD, ensure that the DVD is
available. If you installed Tivoli Storage Manager from a downloaded package,
ensure that the downloaded files are available. If the upgrade fails, and the server
license module is uninstalled, the installation media from the server base release
are required to reinstall the license.

Visit this website: http://www.ibm.com/support/entry/portal/Overview/

Software/Tivoli/Tivoli_Storage_Manager for the following information:
v A list of the latest maintenance and download fixes. Click Support and
downloads and apply any applicable fixes.
v Details about obtaining a base license package. Search for Warranties and
licenses.
v Supported platforms and system requirements. Click Server requirements.

© Copyright IBM Corp. 1993, 2014 63

Installing a Tivoli Storage Manager fix pack

About this task

To install a fix pack or interim fix, complete the following steps.

Attention: Do not alter the DB2 software that is installed with Tivoli Storage
Manager installation packages and fix packs. Do not install or upgrade to a
different version, release, or fix pack of DB2 software because doing so can damage
the database.

Procedure
1. Log in as the root user.
2. Obtain the package file for the fix pack or interim fix that you want to install
from the http://www.ibm.com/support/entry/portal/Overview/Software/
Tivoli/Tivoli_Storage_Manager site.
3. Change to the directory where you placed the executable file and complete the
following steps.

Tip: The files are extracted to the current directory. Ensure that the executable
file is in the directory where you want the extracted files to be located.
a. Change file permissions by entering the following command:
chmod a+x 6.x.x.x-TIV-TSMALL-platform.bin

where platform denotes the architecture that Tivoli Storage Manager is to

be installed on.
b. Issue the following command to extract the installation files:
./6.x.x.x-TIV-TSMALL-platform.bin
4. Back up the database. The preferred method is to use a snapshot backup. A
snapshot backup is a full database backup that does not interrupt any
scheduled database backups. For example, issue the following Tivoli Storage
Manager administrative command:
backup db type=dbsnapshot devclass=tapeclass

See the Administrator's Guide for more details.

5. Back up the device configuration information. Issue the following Tivoli
Storage Manager administrative command:
backup devconfig filenames=file_name

where file_name specifies the name of the file in which to store device
configuration information.
6. Save the volume history file to another directory or rename the file. Issue the
following Tivoli Storage Manager administrative command:
backup volhistory filenames=file_name

where file_name specifies the name of the file in which to store the volume
history information.
7. Save a copy of the server options file, typically named dsmserv.opt. The file is
in the server instance directory.
8. Halt the server before installing a fix pack or interim fix. Use the HALT
command.
9. Ensure that extra space is available in the installation directory. The
installation of this fix pack might require additional temporary disk space in
the installation directory of the server. The amount of additional disk space

64 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing a Tivoli Storage Manager fix pack

can be as much as that required for installing a new database as part of a

Tivoli Storage Manager installation. The Tivoli Storage Manager installation
wizard displays the amount of space that is required for installing the fix pack
and the available amount. If the required amount of space is greater than the
available amount, the installation stops. If the installation stops, add the
required disk space to the file system and restart the installation.
10. Select one of the following ways of installing Tivoli Storage Manager.

Important: After a fix pack is installed, it is not necessary to go through the

configuration again. You can stop after completing the installation, fix any
errors, then restart your servers.
Install the Tivoli Storage Manager software by using one of the following
methods:
Installation wizard
Follow the instructions for your operating system:
“Installing Tivoli Storage Manager by using the installation wizard”
on page 32

Tip: After you start the wizard, in the IBM Installation Manager window,
click the Update icon; do not click the Install or Modify icon.
Command line in console mode
Follow the instructions for your operating system:
“Installing Tivoli Storage Manager by using console mode” on page 35
Silent mode
Follow the instructions for your operating system:
“Installing Tivoli Storage Manager in silent mode” on page 36

Tip: If you have multiple server instances on your system, run the installation
wizard only once. The installation wizard upgrades all server instances.

Results

Correct any errors that are detected during the installation process.

If you installed the server by using the installation wizard, you can view
installation logs by using the IBM Installation Manager tool. Click File > View
Log. To collect log files, from the IBM Installation Manager tool, click Help >
Export Data for Problem Analysis.

If you installed the server by using console mode or silent mode, you can view
error logs in the IBM Installation Manager log directory, for example:
/var/ibm/InstallationManager/logs

Chapter 4. Installing a Tivoli Storage Manager fix pack 65

Installing a Tivoli Storage Manager fix pack

Applying a fix pack to Tivoli Storage Manager V7 in a clustered

environment
Tivoli Storage Manager maintenance updates, which are also referred to as fix
packs, bring your server up to the current maintenance level. It is possible to apply
a fix pack onto a clustered environment for AIX.

Before you begin

To install a fix pack or interim fix to the server, install the server at the level on
which you want to run it. You do not have to start the server installation at the
base release level. For example, if you currently have Version 6.3.4.2 installed, you
can go directly to the latest fix pack for V7.1. You do not have to start with the
V7.1.0 installation if a maintenance update is available.

Procedure
1. Back up the database. The preferred method is to use a snapshot backup. A
snapshot backup is a full database backup that does not interrupt any
scheduled database backups. For example, issue the following command:
backup db type=dbsnapshot devclass=tapeclass

If you must revert the server to the previous level, you must have the
database backup and the configuration files to restore the server to the
previous level.
2. Back up the device configuration information. Issue the following command:
backup devconfig filenames=file_name

where file_name specifies the name of the file in which to store device
configuration information.
3. Back up the volume history information. Issue the following command:
backup volhistory filenames=file_name

where file_name specifies the name of the file in which to store the volume
history information.
4. Save a copy of the server options file, typically named dsmserv.opt. The file is
in the server instance directory.
5. If you are using application level monitoring of the Tivoli Storage Manager
server, from the primary node, suspend monitoring of the dsmserv application
resource. To suspend monitoring, use the smitty IBM PowerHA® menu.
6. Stop the Tivoli Storage Manager server.
7. Verify that the database manager is not running.
8. Mount all shared resources on the primary node. Verify that no other nodes
have write access to these resources during the fix pack installation. If your
environment includes multiple instances of Tivoli Storage Manager, shared
resources for all instances must be accessible to the primary node during the
fix pack installation.
9. Install the Tivoli Storage Manager server on the primary node.
10. Start the Tivoli Storage Manager server.
11. Halt the Tivoli Storage Manager server. Go to the secondary node.
12. On the secondary node, install the Tivoli Storage Manager server.

66 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 5. Upgrading to Tivoli Storage Manager Version 7.1.1
You can upgrade a Tivoli Storage Manager V5 or V6 server to V7.1.1. If a V5 server
is installed on an AIX, HP-UX, Solaris, or z/OS operating system, you can
complete a cross-platform migration to V7.1.1 on a different operating system.

About this task

To upgrade the server on the same operating system, see the upgrade instructions:
Table 14. Upgrade information
To upgrade from this
version To this version See this information
V7.1 V7.1 fix pack or interim fix Chapter 4, “Installing a Tivoli
Storage Manager server fix
pack,” on page 63
V6.2 or V6.3 V7.1.1 “Upgrading from Tivoli
Storage Manager V6.2 or
V6.3 to V7.1.1” on page 68
V6.1 V7.1.1 “Upgrading from Tivoli
Storage Manager V6.1 to
V7.1.1” on page 76
V5 V7.1.1 Upgrade and Migration Guide
for V5 Servers

For information about upgrades in a clustered environment, see “Upgrading Tivoli

Storage Manager in a clustered environment” on page 76.

If a Tivoli Storage Manager V5 server is installed, and you prefer to upgrade the
server to V7.1.1 on a different operating system, see the instructions for server
migration:
Table 15. Migration information
To migrate the server from
this operating system To this operating system See this information
AIX Linux x86_64 Section about migrating
Tivoli Storage Manager V5
servers on AIX, HP-UX, or
Solaris systems to V7.1 on
Linux in the Upgrade and
Migration Guide for V5 Servers
HP-UX Linux x86_64 Section about migrating
Tivoli Storage Manager V5
servers on AIX, HP-UX, or
Solaris systems to V7.1 on
Linux in the Upgrade and
Migration Guide for V5 Servers

© Copyright IBM Corp. 1993, 2014 67

Upgrading the Tivoli Storage Manager server

Table 15. Migration information (continued)

To migrate the server from
this operating system To this operating system See this information
Solaris Linux x86_64 Section about migrating
Tivoli Storage Manager V5
servers on AIX, HP-UX, or
Solaris systems to V7.1 on
Linux in the Upgrade and
Migration Guide for V5 Servers
z/OS AIX Section about migrating
Tivoli Storage Manager V5
servers on z/OS systems to
V7 on AIX or Linux on
System z in the Upgrade and
Migration Guide for V5 Servers
z/OS Linux on System z Section about migrating
Tivoli Storage Manager V5
servers on z/OS systems to
V7 on AIX or Linux on
System z in the Upgrade and
Migration Guide for V5 Servers

To revert to an earlier version of Tivoli Storage Manager after an upgrade or

migration, you must have a full database backup and the installation software for
the original server. You must also have key configuration files:
v Volume history file
v Device configuration file
v Server options file
v dsmserv.dsk file (for a server upgrade or migration from V5 to V7.1.1)

Upgrading from Tivoli Storage Manager V6.2 or V6.3 to V7.1.1

You can upgrade the server directly from Tivoli Storage Manager V6.2 or V6.3 to
V7.1.1. You do not need to uninstall V6.2 or V6.3.

Before you begin

Ensure that you retain the installation media from the V6.2 or V6.3 server base
release that you are upgrading. If you installed Tivoli Storage Manager from a
DVD, ensure that the DVD is available. If you installed Tivoli Storage Manager
from a downloaded package, ensure that the downloaded files are available. If the
upgrade fails, and the server license module is uninstalled, the installation media
from the server base release are required to reinstall the license.

Procedure

To upgrade the server to V7.1.1, complete the following tasks:

1. “Planning the upgrade” on page 69
2. “Preparing the system” on page 70
3. “Installing the V7.1.1 server and verifying the upgrade” on page 72

68 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading the Tivoli Storage Manager server

Planning the upgrade

Before you upgrade the server from V6.2 or V6.3 to V7.1.1, you must review the
relevant planning information, such as system requirements and release notes.
Then, select an appropriate day and time to upgrade the system so that you can
minimize the impact on production operations.

About this task

In lab tests, the process of upgrading the server from V6.2 or V6.3 to V7.1 took 14 -
45 minutes. The results that you achieve might differ, depending on your hardware
and software environment, and the size of the server database.

The following table shows the results that were obtained in lab tests.
Table 16. V6 to V7 upgrade times in lab tests
Version of Random
source Version of Operating Size of server access
system target system system database memory Upgrade time
V6.3.4 V7.1 AIX 17 GB 64 GB 40 minutes
V6.3.4 V7.1 AIX 487 GB 32 GB 45 minutes
V6.3.4 V7.1 AIX 3.8 TB 64 GB 35 minutes
V6.2.5 V7.1 Linux 6.16 GB 16 GB 15 minutes
V6.3.4 V7.1 Linux 30 GB 16 GB 14 minutes
V6.2.5 V7.1 Linux 70 GB 16 GB 24 minutes
V6.3.4 V7.1 Linux 1.4 TB 64 GB 30 minutes
V6.2.5 V7.1 Solaris 9.43 GB 32 GB 35 minutes
V6.3.4 V7.1 Windows 2.35 TB 64 GB 45 minutes

Procedure
1. Review the hardware and software requirements:
“System requirements for the Tivoli Storage Manager server” on page 4
For the latest updates related to system requirements, see the Tivoli Storage
Manager support website at http://www.ibm.com/support/
docview.wss?uid=swg21243309.
2. For special instructions or specific information for your operating system,
review the release notes (http://www.ibm.com/support/knowledgecenter/
SSGSG7_7.1.1/com.ibm.itsm.srv.common.doc/r_relnotes_srv.html) and readme
files (http://www.ibm.com/support/docview.wss?uid=swg27039693) for V7.1.1
server components.
3. If the server that you are upgrading is at a release level that is earlier than
V6.2.3.000, review Technote 1452146 (http://www.ibm.com/support/
docview.wss?uid=swg21452146). The technote describes improvements in the
database reorganization process, and configuration changes that you might be
required to make.
4. Select an appropriate day and time to upgrade your system to minimize the
impact on production operations. The amount of time that is required to
update the system depends on the database size and many other factors. When
you start the upgrade process, clients cannot connect to the server until the
new software is installed and any required licenses are registered again.

Chapter 5. Upgrading the server from V6 to V7.1.1 69

Upgrading the Tivoli Storage Manager server

Preparing the system

To prepare the system for the upgrade from V6.2 or V6.3 to V7.1.1, you must
gather information about each DB2 instance. Then, back up the server database,
save key configuration files, cancel sessions, and stop the server.

Procedure
1. Log on to the computer where Tivoli Storage Manager is installed.
Ensure that you are logged on with the instance user ID.
2. Obtain a list of DB2 instances. Issue the following system command:
/opt/tivoli/tsm/db2/instance/db2ilist

The output might be similar to the following example:

tsminst1

Ensure that each instance corresponds to a server that is running on the

system.
3. For each DB2 instance, note the default database path, actual database path,
database name, database alias, and any DB2 variables that are configured for
the instance. Keep the record for future reference. This information is required
to restore the V6 database.
a. Obtain the default database path of the DB2 instance by issuing the
following system command:
. ~/sqllib/db2profile; LC_ALL=C db2 get dbm cfg | grep DFTDBPATH

The output might be similar to the following example:

Default database path (DFTDBPATH) = /tsminst1/tsminst1

Tip: If you are upgrading the server from V6.3, the default database path
is /tsminst1/tsminst1. If you are upgrading the server from V6.2, the
default database path is /home/tsminst1/tsminst1.
b. Obtain information about the DB2 instance databases by issuing the
following system command:
. ~/sqllib/db2profile; LC_ALL=C db2 list database directory

The output might be similar to the following example:

System Database Directory

Number of entries in the directory = 2

Database 1 entry:

Database alias = TSMAL001

Database name = TSMDB1
Node name = TSMNODE1
Database release level = d.00
Comment = TSM SERVER DATABASE VIA TCPIP
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =

Database 2 entry:

Database alias = TSMDB1

Database name = TSMDB1
Local database directory = /tsminst1/tsminst1

70 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading the Tivoli Storage Manager server

Database release level = d.00

Comment = TSM SERVER DATABASE
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =
c. Obtain the DB2 instance variables by issuing the following system
command:
. ~/sqllib/db2profile; LC_ALL=C db2set -all

The output might be similar to the following example:

[i] DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:500
[i] DB2_SKIPINSERTED=ON
[i] DB2_KEEPTABLELOCK=OFF
[i] DB2_EVALUNCOMMITTED=ON
[i] DB2_SKIPDELETED=ON
[i] DB2COMM=TCPIP
[i] DB2CODEPAGE=819
[i] DB2_PARALLEL_IO=*
[g] DB2FCMCOMM=TCPIP6
[g] DB2SYSTEM=freeride.storage.tucson.ibm.com
[g] DB2INSTDEF=tsminst1inst
d. Obtain more DB2 instance information by saving the following files:
v ~/sqllib/userprofile
v ~/sqllib/usercshrc
For example, issue the following system commands:
cp ~/sqllib/userprofile copy_location
cp ~/sqllib/usercshrc copy_location

where copy_location is the location where the copied file is saved.

The file content might be similar to the following example:
setenv DSMI_CONFIG /tsminst1/tsminst1/tsmdbmgr.opt
setenv DSMI_DIR /opt/tivoli/tsm/client/bin64
setenv DSMI_LOG /tsminst1/tsminst1
setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
4. Connect to the Tivoli Storage Manager server by using an administrative user
ID.
5. Back up the Tivoli Storage Manager database by using the BACKUP DB
command. The preferred method is to create a snapshot backup, which is a
full database backup that does not interrupt scheduled database backups. For
example, you can create a snapshot backup by issuing the following
command:
backup db type=dbsnapshot devclass=tapeclass

For more information about this command and other Tivoli Storage Manager
administrative commands, see the Administrator's Reference.
6. Back up the device configuration information to another directory by issuing
the following Tivoli Storage Manager administrative command:
backup devconfig filenames=file_name

where file_name specifies the name of the file in which to store device
configuration information.

Tip: If you decide to restore the V6 database, this file is required.

Chapter 5. Upgrading the server from V6 to V7.1.1 71

Upgrading the Tivoli Storage Manager server

7. Back up the volume history file to another directory. Issue the following Tivoli
Storage Manager administrative command:
backup volhistory filenames=file_name

where file_name specifies the name of the file in which to store the volume
history information.

Tip: If you decide to restore the V6 database, this file is required.

8. Save a copy of the server options file, which is typically named dsmserv.opt.
The file is in the server instance directory.
9. Prevent activity on the server by disabling new sessions. Issue the following
Tivoli Storage Manager administrative commands:
disable sessions client
disable sessions server
10. Verify whether any sessions exist, and notify the users that the server will be
stopped. To check for existing sessions, issue the following Tivoli Storage
Manager administrative command:
query session
11. Cancel sessions by issuing the following Tivoli Storage Manager
administrative command:
cancel session all

This command cancels all sessions except for your current session.
12. Stop the server by issuing the following Tivoli Storage Manager
administrative command:
halt
13. Verify that the server is shut down and no processes are running.
Issue the following command:
ps -ef | grep dsmserv
14. In the server instance directory of your installation, locate the NODELOCK file
and move it to another directory, where you are saving configuration files.
The NODELOCK file contains the previous licensing information for your
installation. This licensing information is replaced when the upgrade is
complete.

Installing the V7.1.1 server and verifying the upgrade

To complete the process of upgrading the server from V6.2 or V6.3 to V7.1.1, you
must install the V7.1.1 server. Then, verify that the upgrade was successful by
starting the server instance.

Before you begin

You must be logged on to the system by using the root user ID.

You can obtain the installation package from the product DVD or from an IBM
download site.

If you plan to download the files, set the system user limit for maximum file size
to unlimited to ensure that the files can be downloaded correctly.
1. To query the maximum file size value, issue the following command:
ulimit -Hf

72 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading the Tivoli Storage Manager server

2. If the system user limit for maximum file size is not set to unlimited, change it
to unlimited by following the instructions in the documentation for your
operating system.

About this task

By using the Tivoli Storage Manager installation software, you can install the
following components:
v Tivoli Storage Manager server
v Tivoli Storage Manager server languages
v Tivoli Storage Manager license
v Tivoli Storage Manager devices
v Tivoli Storage Manager Operations Center
v Tivoli Storage Manager storage agent

Tip: The database (DB2) and the Global Security Kit are automatically installed
when you select the server component.
For more information about storage agents, see Tivoli Storage Manager for
Storage Area Networks (http://www.ibm.com/support/knowledgecenter/
SSSQZW_7.1.1/com.ibm.itsm.sta.doc/c_overview.html).

Procedure
1. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
2. If you are downloading the package from one of the download sites, complete
the following steps:

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035122
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035635
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The
path must contain no more than 128 characters. Be sure to extract
the installation files to an empty directory. Do not extract to a
directory that contains previously extracted files, or any other files.
Also, ensure that you have executable permission for the package
file.
c. If necessary, change the file permissions by issuing the following
command:
chmod a+x package_name.bin

Chapter 5. Upgrading the server from V6 to V7.1.1 73

 Upgrading the Tivoli Storage Manager server

where package_name is like the following example:

7.1.1.000-TIV-TSMSRV-AIX.bin

In the examples, 7.1.1.000 represents the product release level.

d. Extract the installation files by issuing the following command:
./package_name.bin

The package is large. Therefore, the extraction takes some time.

3. To ensure that the Tivoli Storage Manager wizards work correctly, verify that
the following command is enabled:
lsuser
By default, the command is enabled.
4. Install the Tivoli Storage Manager software by using one of the following
methods. During the installation process, you must install the Tivoli Storage
Manager license.

| Tip: If you have multiple server instances on your system, install the Tivoli
| Storage Manager software only once to upgrade all server instances.
Installation wizard
To install the server by using the graphical wizard of IBM Installation
Manager, follow the instructions in “Installing Tivoli Storage Manager
by using the installation wizard” on page 32.
Ensure that your system meets the prerequisites for using the
installation wizard. Then, complete the installation procedure. In the
IBM Installation Manager window, click the Install icon; do not click
the Update or Modify icon.
Command line in console mode
To install the server by using the command line in console mode,
follow the instructions in “Installing Tivoli Storage Manager by using
console mode” on page 35.
Review the information about installing the server in console mode
and then complete the installation procedure.
Silent mode
To install the server by using silent mode, follow the instructions in
“Installing Tivoli Storage Manager in silent mode” on page 36.
Review the information about installing the server in silent mode and
then complete the installation procedure.
| After you install the Tivoli Storage Manager software, you do not have to
| reconfigure the system.
| 5. Correct any errors that are detected during the installation process.
| If you installed the server by using the installation wizard, you can view
| installation logs by using the IBM Installation Manager tool. Click File > View
| Log. To collect log files, from the IBM Installation Manager tool, click Help >
| Export Data for Problem Analysis.
| If you installed the server by using console mode or silent mode, you can
| view error logs in the IBM Installation Manager log directory, for example:
| /var/ibm/InstallationManager/logs

74 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading the Tivoli Storage Manager server

| 6. Obtain any applicable fixes by going to the following website:

| http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
| Tivoli_Storage_Manager. Click Downloads (fixes and PTFs) and apply any
| applicable fixes.
7. Verify that the upgrade was successful:
a. Start the server instance.
For instructions, see “Starting the server instance” on page 54.
b. Monitor the messages that the server issues as it starts. Watch for error
and warning messages, and resolve any issues.
c. Verify that you can connect to the server by using the administrative client.
To start an administrative client session, issue the following Tivoli Storage
Manager administrative command:
dsmadmc
d. To obtain information about the upgraded system, run QUERY commands.
For example, to obtain consolidated information about the system, issue
the following Tivoli Storage Manager administrative command:
query system

To obtain information about the database, issue the following Tivoli

Storage Manager administrative command:
query db format=detailed
8. Register the licenses for the Tivoli Storage Manager server components that
are installed on your system by issuing the REGISTER LICENSE command:
register license file=installation_directory/server/bin/component_name.lic

where installation_directory specifies the directory in which you installed the

component, and component_name specifies the abbreviation for the component.

For example, if you installed the server in the default directory,

/opt/tivoli/tsm, register the license by issuing the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmbasic.lic

For example, if you installed Tivoli Storage Manager Extended Edition in the
/opt/tivoli/tsm directory, issue the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmee.lic

For example, if you installed System Storage Archive Manager in the

/opt/tivoli/tsm directory, issue the following command:
register license file=/opt/tivoli/tsm/server/bin/dataret.lic

Restriction: You cannot use the Tivoli Storage Manager server to register
licenses for Tivoli Storage Manager for Mail, Tivoli Storage Manager for
Databases, Tivoli Storage Manager for ERP, and Tivoli Storage Manager for
Space Management. The REGISTER LICENSE command does not apply to these
licenses. The licensing for these products is done by Tivoli Storage Manager
clients.
9. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
10. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.

Chapter 5. Upgrading the server from V6 to V7.1.1 75

Upgrading the Tivoli Storage Manager server

What to do next

You can authenticate passwords with the LDAP directory server, or authenticate
passwords with the Tivoli Storage Manager server. Passwords that are
authenticated with the LDAP directory server can provide enhanced system
security. For instructions, see the section about managing passwords and logon
procedures in the Administrator's Guide.

Upgrading from Tivoli Storage Manager V6.1 to V7.1.1

You can upgrade the Tivoli Storage Manager server from V6.1 to V6.3, and then
upgrade the server to V7.1.1. It is not possible to upgrade the server directly from
V6.1 to V7.1.1.

Before you begin

Ensure that you retain the installation media from the base release of the V6.1 and
V6.3 servers. If you obtained the Tivoli Storage Manager software from a DVD,
ensure that the DVD is available. If you obtained the Tivoli Storage Manager
software from a downloaded package, ensure that the downloaded files are
available. If the upgrade fails, and the server license module is uninstalled, the
installation media from the server base release are required to reinstall the license.

Procedure
1. Upgrade the server from V6.1 to V6.3, as described in Upgrading from Tivoli
Storage Manager Version 6.1 to 6.3 or later (http://www.ibm.com/support/
knowledgecenter/SSGSG7_6.3.0/com.ibm.itsm.srv.install.doc/
t_srv_upgrade61_63.html).
2. Upgrade the server from V6.3 to V7.1.1, as described in “Upgrading from Tivoli
Storage Manager V6.2 or V6.3 to V7.1.1” on page 68.

Upgrading Tivoli Storage Manager in a clustered environment

To upgrade a Tivoli Storage Manager server to V7.1.1 in a clustered environment,
you must complete preparation and installation tasks. The procedures vary,
depending on the operating system and release.

Procedure

Follow the procedure for your operating system, source release, and target release:
Table 17. Procedures for upgrading the server in a clustered environment on an AIX
operating system
Source release Target release Procedure
V7.1 V7.1 fix pack “Applying a fix pack to
Tivoli Storage Manager V7 in
a clustered environment” on
page 66

76 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading the Tivoli Storage Manager server

Table 17. Procedures for upgrading the server in a clustered environment on an AIX
operating system (continued)
Source release Target release Procedure
V6.2 or V6.3 V7.1.1 “Upgrading Tivoli Storage
Manager from V6.2 or V6.3
to V7.1.1 in a clustered
environment with a shared
database instance”
“Upgrading Tivoli Storage
Manager from V6.2 or V6.3
to V7.1.1 in a clustered
environment with separate
database instances” on page
79
V6.1 V7.1.1 “Upgrading Tivoli Storage
Manager from V6.1 to V7.1.1
in a clustered environment”
on page 82
V5 V7.1.1 Upgrade and Migration Guide
for V5 Servers

Upgrading Tivoli Storage Manager from V6.2 or V6.3 to V7.1.1

in a clustered environment with a shared database instance
You can upgrade a Tivoli Storage Manager server from V6.2 or V6.3 to V7.1.1 in a
clustered environment on AIX with a shared database instance. In this way, you
can take advantage of the new features in Tivoli Storage Manager V7.1.1.

Before you begin

Ensure that you retain the installation media from the V6.2 or V6.3 server base
release that you are upgrading. If you installed Tivoli Storage Manager from a
DVD, ensure that the DVD is available. If you installed Tivoli Storage Manager
from a downloaded package, ensure that the downloaded files are available. If the
upgrade fails, and the server license module is uninstalled, the installation media
from the server base release are required to reinstall the license.

About this task

Use the following procedure when the DB2 instance directory is shared between
the nodes in the cluster. The DB2 instance directory is in the following location:
/home/tsminst1/sqllib

If the DB2 instance directory is not shared between nodes, follow the instructions
in “Upgrading Tivoli Storage Manager from V6.2 or V6.3 to V7.1.1 in a clustered
environment with separate database instances” on page 79.

Procedure
1. Back up the database by using the BACKUP DB command. The preferred method
is to use a snapshot backup, which creates a full database backup without
interrupting any scheduled backups. For example, you can create a snapshot
backup by issuing the following command:
backup db type=dbsnapshot devclass=tapeclass

Chapter 5. Upgrading the server from V6 to V7.1.1 77

Upgrading the Tivoli Storage Manager server

For more information about the BACKUP DB command and other Tivoli Storage
Manager administrative commands, see the Administrator's Reference.
2. Back up the device configuration information to another directory. Issue the
following command:
backup devconfig filenames=file_name

where file_name specifies the name of the file in which to store device
configuration information.
3. Back up the volume history file to another directory. Issue the following
command:
backup volhistory filenames=file_name

where file_name specifies the name of the file in which to store the volume
history information.
4. Save a copy of the server options file, which is typically named dsmserv.opt.
The file is in the server instance directory.
5. Stop all instances of the Tivoli Storage Manager server. Verify that no Tivoli
Storage Manager server processes are running. If you are using
application-level monitoring of the Tivoli Storage Manager server, use your
clustering tool to suspend monitoring of the dsmserv application resource.
6. Verify that the database manager is not running for any instance. Determine
whether any db2sysc processes are running. The owner of running processes
indicates which instances are active. For each server instance owner, run the
following command to stop DB2:
db2stop
7. On the primary node, install the Tivoli Storage Manager V7.1.1 server by
running the ./install.sh command. For instructions, see Chapter 2,
“Installing the Tivoli Storage Manager server components,” on page 31. After
you start the wizard, in the IBM Installation Manager window, click the
Install icon; do not click the Update or Modify icon.
8. Start each Tivoli Storage Manager V7.1.1 server in the foreground:
a. Verify that you are logged in with the instance owner ID.
b. Navigate to the instance directory and issue the following command:
/opt/tivoli/tsm/server/bin/dsmserv
Wait until you see the server prompt, which indicates that the server is
started.
9. Stop the server for each Tivoli Storage Manager instance that is being
upgraded. Issue the following command:
halt
10. On each secondary node in the cluster, complete the following steps:
a. Install the Tivoli Storage Manager V7.1.1 server by running the
./install.sh command. For instructions, see Chapter 2, “Installing the
Tivoli Storage Manager server components,” on page 31.
1) If you are running the installation wizard, in the IBM Installation
Manager window, click the Install icon; do not click the Update or
Modify icon.
2) If you are running the installation wizard, in the Instance Credentials
panel, clear the Update this instance check box for each instance.
3) If you are installing the server in console mode, at the prompt Do you
want update this instance?, enter NO for each instance.

78 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading the Tivoli Storage Manager server

4) If you are installing the server in silent mode, specify FALSE for the
value of the user.instance_name_update variable for each instance.
b. Ensure that each Tivoli Storage Manager V7.1.1 server starts. If you are
using application-level monitoring, use the clustering tool to start the
server.
For instructions about starting the server, see “Starting the server instance”
on page 54.
11. Register the licenses for the Tivoli Storage Manager server components that
are installed on your system by issuing the REGISTER LICENSE command:
register license file=installation_directory/server/bin/component_name.lic

where installation_directory specifies the directory in which you installed the

component and component_name specifies the abbreviation for the component.

For example, if you installed the server in the default directory,

/opt/tivoli/tsm, register the license by issuing the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmbasic.lic

For example, if you installed Tivoli Storage Manager Extended Edition in the
/opt/tivoli/tsm directory, issue the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmee.lic

For example, if you installed System Storage Archive Manager in the

/opt/tivoli/tsm directory, issue the following command:
register license file=/opt/tivoli/tsm/server/bin/dataret.lic

| Restriction: You cannot use the Tivoli Storage Manager server to register
| licenses for Tivoli Storage Manager for Mail, Tivoli Storage Manager for
| Databases, Tivoli Storage Manager for ERP, and Tivoli Storage Manager for
| Space Management. The REGISTER LICENSE command does not apply to these
| licenses. The licensing for these products is done by Tivoli Storage Manager
| clients.

Upgrading Tivoli Storage Manager from V6.2 or V6.3 to V7.1.1

in a clustered environment with separate database instances
You can upgrade a Tivoli Storage Manager server from V6.2 or V6.3 to V7.1.1 in a
clustered environment on AIX with separate database instances. In this way, you
can take advantage of the new features in Tivoli Storage Manager V7.1.1.

Before you begin

Ensure that you retain the installation media from the V6.2 or V6.3 server base
release that you are upgrading. If you installed Tivoli Storage Manager from a
DVD, ensure that the DVD is available. If you installed Tivoli Storage Manager
from a downloaded package, ensure that the downloaded files are available. If the
upgrade fails, and the server license module is uninstalled, the installation media
from the server base release are required to reinstall the license.

About this task

Use the following procedure when the DB2 instance directory is not shared
between the nodes in the cluster. The DB2 instance directory is at the following
location:
/home/tsminst1/sqllib

Chapter 5. Upgrading the server from V6 to V7.1.1 79

Upgrading the Tivoli Storage Manager server

If the DB2 instance directory is shared between the nodes in the cluster, follow the
instructions in “Upgrading Tivoli Storage Manager from V6.2 or V6.3 to V7.1.1 in a
clustered environment with a shared database instance” on page 77.

Procedure
1. Back up the database by using the BACKUP DB command. The preferred method
is to use a snapshot backup, which creates a full database backup without
interrupting any scheduled backups. For example, you can create a snapshot
backup by issuing the following command:
backup db type=dbsnapshot devclass=tapeclass
For more information about the BACKUP DB command and other Tivoli Storage
Manager administrative commands, see the Administrator's Reference.
2. Back up the device configuration information to another directory. Issue the
following command:
backup devconfig filenames=file_name

where file_name specifies the name of the file in which to store device
configuration information.
3. Back up the volume history file to another directory. Issue the following
command:
backup volhistory filenames=file_name

where file_name specifies the name of the file in which to store the volume
history information.
4. Save a copy of the server options file, which is typically named dsmserv.opt.
The file is in the server instance directory.
5. Stop all instances of the Tivoli Storage Manager server. Verify that no Tivoli
Storage Manager server processes are running. If you are using
application-level monitoring of the Tivoli Storage Manager server, use your
clustering tool to suspend monitoring of the dsmserv application resource.
6. Verify that the database manager is not running for any instance. Determine
whether any db2sysc processes are running. The owner of running processes
indicates which instances are active. For each server instance owner, run the
following command to stop DB2:
db2stop
7. Ensure that the shared resources for all Tivoli Storage Manager instances are
on the primary node. Verify that no other nodes have write access to these
resources during the upgrade. If the environment includes multiple instances
of Tivoli Storage Manager, shared resources for all instances must be
accessible to the primary node.
8. On the primary node, install the Tivoli Storage Manager V7.1.1 server by
running the ./install.sh command. For instructions, see Chapter 2,
“Installing the Tivoli Storage Manager server components,” on page 31. After
you start the wizard, in the IBM Installation Manager window, click the
Install icon; do not click the Update or Modify icon.
9. Start each Tivoli Storage Manager V7.1.1 server in the foreground:
a. Verify that you are logged in with the instance owner ID.
b. Navigate to the instance directory and issue the following command:
/opt/tivoli/tsm/server/bin/dsmserv
Wait until you see the server prompt, which indicates that the server is
started.

80 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading the Tivoli Storage Manager server

10. Stop the server for each Tivoli Storage Manager instance that is being
upgraded. Issue the following command:
halt
11. On each secondary node in the cluster, complete the following steps:
a. Move all shared resources to the secondary node. If the environment
includes multiple instances of Tivoli Storage Manager, shared resources for
all instances must be accessible to the secondary nodes during the
upgrade.
b. Stop all instances of the Tivoli Storage Manager server. Verify that no
Tivoli Storage Manager server processes are running.
c. Verify that the database manager is not running for any instance.
Determine whether any db2sysc processes are running. The owner of
running processes indicates which instances are active. For each server
instance owner, run the following command to stop DB2:
db2stop
d. Install the Tivoli Storage Manager V7.1.1 server by running the
./install.sh command. For instructions, see Chapter 2, “Installing the
Tivoli Storage Manager server components,” on page 31.
1) If you are using the installation wizard, in the IBM Installation
Manager window, click the Install icon; do not click the Update or
Modify icon.
2) If you are using the installation wizard, on the Instance Credentials
page, select the Configure this instance on a secondary node of the
cluster check box for each instance that you are configuring.
3) If you are installing the server in console mode, at the prompt
Configure this instance on a secondary node of the cluster?, enter
YES for each instance.
4) If you are installing the server in silent mode, specify TRUE for the
value of the user.instance_name_secondaryNode variable for each
instance.
e. Ensure that each Tivoli Storage Manager V7.1.1 server starts. If you are
using application-level monitoring, use the clustering tool to start the
server.
For instructions about starting the server, see “Starting the server instance”
on page 54.
12. Register the licenses for the Tivoli Storage Manager server components that
are installed on your system by issuing the REGISTER LICENSE command:
register license file=installation_directory/server/bin/component_name.lic

where installation_directory specifies the directory in which you installed the

component and component_name specifies the abbreviation for the component.

For example, if you installed the server in the default directory,

/opt/tivoli/tsm, register the license by issuing the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmbasic.lic

For example, if you installed Tivoli Storage Manager Extended Edition in the
/opt/tivoli/tsm directory, issue the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmee.lic

For example, if you installed System Storage Archive Manager in the

/opt/tivoli/tsm directory, issue the following command:

Chapter 5. Upgrading the server from V6 to V7.1.1 81

 Upgrading the Tivoli Storage Manager server

register license file=/opt/tivoli/tsm/server/bin/dataret.lic

| Restriction: You cannot use the Tivoli Storage Manager server to register
| licenses for Tivoli Storage Manager for Mail, Tivoli Storage Manager for
| Databases, Tivoli Storage Manager for ERP, and Tivoli Storage Manager for
| Space Management. The REGISTER LICENSE command does not apply to these
| licenses. The licensing for these products is done by Tivoli Storage Manager
| clients.

Upgrading Tivoli Storage Manager from V6.1 to V7.1.1 in a

clustered environment
You can upgrade a Tivoli Storage Manager server on AIX from V6.1 to V7.1.1 in a
clustered environment. Complete the upgrade to take advantage of the new
features in V7.1.1.

Before you begin

Ensure that you retain the installation media from the base release of the V6.1 and
V6.3 servers. If you obtained the Tivoli Storage Manager software from a DVD,
ensure that the DVD is available. If you obtained the Tivoli Storage Manager
software from a downloaded package, ensure that the downloaded files are
available. If the upgrade fails, and the server license module is uninstalled, the
installation media from the server base release are required to reinstall the license.

About this task

If the clustered environment contains multiple server instances, move all resources
that are required for the instances onto a single cluster node, which is the primary
node, during the upgrade process.

Procedure
1. Back up the database by using the BACKUP DB command. The preferred method
is to use a snapshot backup, which creates a full database backup without
interrupting any scheduled backups. For example, you can create a snapshot
backup by issuing the following command:
backup db type=dbsnapshot devclass=tapeclass
For more information about the BACKUP DB command and other Tivoli Storage
Manager administrative commands, see the Administrator's Reference.
2. Back up the device configuration information to another directory. Issue the
following command:
backup devconfig filenames=file_name

where file_name specifies the name of the file in which to store device
configuration information.
3. Back up the volume history file to another directory. Issue the following
command:
backup volhistory filenames=file_name

where file_name specifies the name of the file in which to store the volume
history information.
4. Save a copy of the server options file, which is typically named dsmserv.opt.
The file is in the server instance directory.

82 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading the Tivoli Storage Manager server

5. Stop all instances of the Tivoli Storage Manager server. Verify that no Tivoli
Storage Manager server processes are running. If you are using
application-level monitoring of the Tivoli Storage Manager server, use your
clustering tool to suspend monitoring of the dsmserv application resource.
6. Verify that the database manager is not running for any instance. Determine
whether any db2sysc processes are running. The owner of running processes
indicates which instances are active. For each server instance owner, run the
following command to stop DB2:
db2stop
7. Ensure that the shared resources for all Tivoli Storage Manager instances are
on the primary node. Verify that no other nodes have write access to these
resources during the upgrade.
8. On the primary node, install the V6.3 server by using the ./install.bin
command. For detailed instructions about installing the V6.3 server, see
Installing the Tivoli Storage Manager server components (http://
www.ibm.com/support/knowledgecenter/SSGSG7_6.3.0/
com.ibm.itsm.srv.install.doc/t_srv_inst.html).
9. On the primary node, install the Tivoli Storage Manager V7.1.1 server by
running the ./install.sh command. For instructions, see Chapter 2,
“Installing the Tivoli Storage Manager server components,” on page 31. After
you start the wizard, in the IBM Installation Manager window, click the
Install icon; do not click the Update or Modify icon.
10. Start each Tivoli Storage Manager V7.1.1 server in the foreground. Using the
instance owner ID, navigate to the instance directory and issue the following
command:
/opt/tivoli/tsm/server/bin/dsmserv
Wait until you see the server prompt, which indicates that the server is
started.
11. Stop the server for each Tivoli Storage Manager instance that is being
upgraded.
12. On each secondary node in the cluster, complete the following steps:
a. Move all shared resources to the secondary node. If your environment
includes multiple instances of Tivoli Storage Manager, shared resources for
all instances must be accessible to the secondary nodes during the
upgrade.
b. Stop all instances of the Tivoli Storage Manager server. Verify that no
Tivoli Storage Manager server processes are running.
c. Verify that the database manager is not running for any instance.
Determine whether any db2sysc processes are running. The owner of
running processes indicates which instances are active. For each server
instance owner, run the following command to stop DB2:
db2stop
d. Uninstall the V6.1 server:
1) In the /opt/tivoli/tsm/_uninst directory, issue the following
command:
cd _uninst
2) Issue the following command:
./Uninstall_Tivoli_Storage_Manager

For detailed instructions about uninstalling the server, see the Tivoli
Storage Manager V6.1 documentation (https://www.ibm.com/
developerworks/community/wikis/home?lang=en#!/wiki/Tivoli

Chapter 5. Upgrading the server from V6 to V7.1.1 83

 Upgrading the Tivoli Storage Manager server

%20Storage%20Manager/page/PDF%20versions%20of%20the%20IBM
%20Tivoli%20Storage%20Manager%20Version%206.1.x
%20documentation).
e. Install the Tivoli Storage Manager V7.1.1 server by running the
./install.sh command. In the IBM Installation Manager window, click
the Install icon; do not click the Update or Modify icon. For instructions
about installing the server, see Chapter 2, “Installing the Tivoli Storage
Manager server components,” on page 31.
f. Ensure that each Tivoli Storage Manager V7.1.1 server starts.
13. Register the licenses for the Tivoli Storage Manager server components that
are installed on your system by issuing the REGISTER LICENSE command:
register license file=installation_directory/server/bin/component_name.lic

where installation_directory specifies the directory in which you installed the

component and component_name specifies the abbreviation for the component.

For example, if you installed the server in the default directory,

/opt/tivoli/tsm, register the license by issuing the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmbasic.lic

For example, if you installed Tivoli Storage Manager Extended Edition in the
/opt/tivoli/tsm directory, issue the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmee.lic

For example, if you installed System Storage Archive Manager in the

/opt/tivoli/tsm directory, issue the following command:
register license file=/opt/tivoli/tsm/server/bin/dataret.lic

| Restriction: You cannot use the Tivoli Storage Manager server to register
| licenses for Tivoli Storage Manager for Mail, Tivoli Storage Manager for
| Databases, Tivoli Storage Manager for ERP, and Tivoli Storage Manager for
| Space Management. The REGISTER LICENSE command does not apply to these
| licenses. The licensing for these products is done by Tivoli Storage Manager
| clients.

84 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 6. Reverting from Version 7.1 to the previous V6
server
If you must revert to the previous version of the server after an upgrade, you must
have a full database backup from your original version. You must also have the
server installation media for your original version and key configuration files.
Carefully follow the preparation steps before you upgrade the server. By doing so,
it might be possible to revert to the previous version of the Tivoli Storage Manager
server with minimal loss of data.

Before you begin

You must have the following items from the earlier version of the server:
v Server database backup
v Volume history file
v Device configuration file
v Server options file

About this task

Use the same instructions whether you are reverting within releases or to an earlier
release, for example, from 6.2.2 to 6.2.0 or from 6.2.2 to 6.1.2. The older version
must match the version that you used before the upgrade to 7.1.1.

Attention: Specify the REUSEDELAY parameter to help prevent backup-archive

client data loss when you revert the server to a previous version.

Steps for reverting to the previous server version

About this task

Complete the following steps on the system that has the V7.1 server.

Procedure
1. Halt the server to shut down all server operations by using the HALT
command.
2. Remove the database from the database manager, then delete the database and
recovery log directories.
a. Manually remove the database. One way to remove it is by issuing this
command:
dsmserv removedb tsmdb1
b. If you must reuse the space that is occupied by the database and recovery
log directories, you can now delete these directories.
3. Use the uninstallation program to uninstall the V7.1.1 server. Uninstallation
removes the server and the database manager, with their directories. For
details, see Chapter 8, “Uninstalling Tivoli Storage Manager,” on page 93.
4. Reinstall the version of the server program that you were using before the
upgrade to V7.1. This version must match the version that your server was
running when you created the database backup that you restore in a later
step. For example, the server was at version 6.2.2.0 before the upgrade, and

© Copyright IBM Corp. 1993, 2014 85

Reverting to a previous Version 6 server version

you intend to use the database backup that was in use on this server. You
must install the 6.2.2.0 fix pack to be able to restore the database backup.
5. Copy the following files to the instance directory.
v Device configuration file
v Volume history file
v The server options file (typically dsmserv.opt)
6. Configure the new server database by using the configuration wizard. To start
the wizard, issue the following command:
. /dsmicfgx
7. Ensure that no servers are running in the background.
8. Restore the database to a point in time before the upgrade. For more details,
see the restoring the server database to a point in time section in the
Administrator’s Guide.
9. If you enabled data deduplication for any FILE-type storage pools that existed
before the upgrade, or if you moved data that existed before the upgrade into
new storage pools while using the V7.1 server, you must complete additional
recovery steps. For more details, see “Additional recovery steps if you created
new storage pools or enabled data deduplication.”
10. If the REUSEDELAY parameter setting on storage pools is less than the age of the
database that you restored, restore volumes on any sequential-access storage
pools that were reclaimed after that database backup. Use the RESTORE VOLUME
command.
If you do not have a backup of a storage pool, audit the reclaimed volumes
by using the AUDIT VOLUME command, with the FIX=YES parameter to resolve
inconsistencies. For example:
audit volume volume_name fix=yes
11. If client backup or archive operations were completed using the V7.1 server,
audit the storage pool volumes on which the data was stored.

Additional recovery steps if you created new storage pools or enabled

data deduplication
If you created new storage pools, turned on data deduplication for any FILE-type
storage pools, or did both while your server was running as a V7.1.1 server, you
must complete more steps to return to the previous server version.

Before you begin

To complete this task, you must have a complete backup of the storage pool that
was created before the upgrade to V7.1.1.

About this task

Use this information if you did either or both of the following actions while your
server was running as a V7.1.1 server:
v You enabled the data deduplication function for any storage pools that existed
before the upgrade to V7.1.1 program. Data deduplication applies only to
storage pools that use a FILE device type.
v You created new, primary storage pools after the upgrade, and moved data that
was stored in other storage pools into the new storage pools.

Complete these steps after the server is again restored to V6.

86 IBM Tivoli Storage Manager for AIX: Installation Guide

 Reverting to a previous Version 6 server version

Procedure
v For each storage pool for which you enabled the data deduplication function,
restore the entire storage pool by using the RESTORE STGPOOL command.
v For storage pools that you created after the upgrade, determine what action to
take. Data that was moved from existing, V6 storage pools into the new storage
pools might be lost because the new storage pools no longer exist in your
restored V6 server. Possible recovery depends on the type of storage pool:
– If data was moved from V6 DISK-type storage pools into a new storage pool,
space that was occupied by the data that was moved was probably reused.
Therefore, you must restore the original, V6 storage pools, by using the
storage pool backups that were created before the upgrade to V7.1.
If no data was moved from V6 DISK-type storage pools into a new storage
pool, then audit the storage pool volumes in these DISK-type storage pools.
– If data was moved from V6 sequential-access storage pools into a new storage
pool, that data might still exist and be usable in storage pool volumes on the
restored V6 server. The data might be usable if the REUSEDELAY parameter for
the storage pool was set to a value that prevented reclamation while the
server was running as a V7.1.1 server. If any volumes were reclaimed while
the server was running as a V7.1.1 server, restore those volumes from storage
pool backups that were created before the upgrade to V7.1.1.

Chapter 6. Reverting from Version 7.1 to the previous V6 server 87

Reverting to a previous Version 6 server version

88 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 7. Reference: DB2 commands for Tivoli Storage
Manager server databases
Use this list as reference when you are directed to issue DB2 commands by IBM
support.

Purpose

After using the wizards to install and configure Tivoli Storage Manager, you
seldom need to issue DB2 commands. A limited set of DB2 commands that you
might use or be asked to issue are listed in Table 18. This list is supplemental
material only and is not a comprehensive list. There is no implication that a Tivoli
Storage Manager administrator will use it on a daily or ongoing basis. Samples of
some commands are provided. Details of output are not listed.

For a full explanation of the commands described here and of their syntax, see
http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0.
Table 18. DB2 commands
Command Description Example
db2icrt Creates DB2 instances in the home Manually create a Tivoli Storage Manager
directory of the instance owner. instance. Enter the command on one line:
Tip: The Tivoli Storage Manager /opt/tivoli/tsm/db2/instance/
configuration wizard creates the instance db2icrt -a server -s ese -u
used by the server and database. After a instance_name instance_name
server is installed and configured through
the configuration wizard, the db2icrt
command is generally not used.

This utility is in the DB2DIR/instance

directory, where DB2DIR represents the
installation location where the current
version of the DB2 database system is
installed.
db2set Displays DB2 variables. List DB2 variables:
db2set
CATALOG DATABASE Stores database location information in the Catalog the database:
system database directory. The database db2 catalog database tsmdb1
can be located either on the local
workstation or on a remote database
partition server. The server configuration
wizard takes care of any catalog needed
for using the server database. Run this
command manually, after a server is
configured and running, only if something
in the environment changes or is
damaged.
CONNECT TO DATABASE Connects to a specified database for Connect to the Tivoli Storage Manager
command-line interface (CLI) use. database from a DB2 CLI:
db2 connect to tsmdb1

© Copyright IBM Corp. 1993, 2014 89

Reference: DB2 commands for Tivoli Storage Manager server databases

Table 18. DB2 commands (continued)

Command Description Example
GET DATABASE CONFIGURATION Returns the values of individual entries in Show the configuration information for a
a specific database configuration file. database alias:
Important: This command and db2 get db cfg for tsmdb1
parameters are set and managed directly
by DB2. They are listed here for
Retrieve information in order to verify
informational purposes and a means to
settings such as database configuration,
view the existing settings. Changing these
log mode, and maintenance.
settings might be advised by IBM support
or through service bulletins such as db2 get db config for tsmdb1
APARs or Technical Guidance documents show detail
(technotes). Do not change these settings
manually. Change them only at the
direction of IBM and only through the use
of Tivoli Storage Manager server
commands or procedures.
GET DATABASE MANAGER CONFIGURATION Returns the values of individual entries in Retrieve configuration information for the
a specific database configuration file. database manager:
Important: This command and db2 get dbm cfg
parameters are set and managed directly
by DB2. They are listed here for
informational purposes and a means to
view the existing settings. Changing these
settings might be advised by IBM support
or through service bulletins such as
APARs or Technical Guidance documents
(technotes). Do not change these settings
manually. Change them only at the
direction of IBM and only through the use
of Tivoli Storage Manager server
commands or procedures.
GET HEALTH SNAPSHOT Retrieves the health status information for Receive a report on DB2 health monitor
the database manager and its databases. indicators:
The information returned represents a db2 get health snapshot for
snapshot of the health state at the time database on tsmdb1
the command was issued. Tivoli Storage
Manager monitors the state of the
database using the health snapshot and
other mechanisms that are provided by
DB2. There might be cases where the
health snapshot or other DB2
documentation indicates that an item or
database resource might be in an alert
state. Such a case indicates that action
must be considered to remedy the
situation. Tivoli Storage Manager monitors
the condition and responds appropriately.
Not all declared alerts by the DB2
database are acted on.
GRANT (Database Authorities) Grants authorities that apply to the entire Grant access to the user ID itmuser:
database rather than privileges that apply db2 GRANT CONNECT ON DATABASE
to specific objects within the database. TO USER itmuser
db2 GRANT CREATETAB ON DATABASE
TO USER itmuser

90 IBM Tivoli Storage Manager for AIX: Installation Guide

 Reference: DB2 commands for Tivoli Storage Manager server databases

Table 18. DB2 commands (continued)

Command Description Example
RUNSTATS Updates statistics about the characteristics Update statistics on a single table.
of a table and associated indexes or db2 runstats on table
statistical views. These characteristics SCHEMA_NAME.TABLE_NAME
include number of records, number of with distribution and sampled
pages, and average record length. detailed indexes all

To see a table, issue this utility after

updating or reorganizing the table.

A view must be enabled for optimization

before its statistics can be used to
optimize a query. A view that is enabled
for optimization is known as a statistical
view. Use the DB2 ALTER VIEW statement
to enable a view for optimization. Issue
the RUNSTATS utility when changes to
underlying tables substantially affect the
rows returned by the view.
Tip: The server configures DB2 to run the
RUNSTATS command as needed.
SET SCHEMA Changes the value of the CURRENT SCHEMA Set the schema for Tivoli Storage
special register, in preparation for issuing Manager:
SQL commands directly through the DB2 db2 set schema tsmdb1
CLI.
Tip: A special register is a storage area
that is defined for an application process
by the database manager. It is used to
store information that can be referenced in
SQL statements.
START DATABASE MANAGER Starts the current database manager Start the database manager:
instance background processes. The Tivoli db2start
Storage Manager server starts and stops
the instance and database whenever the
server starts and halts.
Important: Allow the Tivoli Storage
Manager server to manage the starting
and stopping of the instance and database
unless otherwise directed by IBM support.
STOP DATABASE MANAGER Stops the current database manager Stop the database manager:
instance. Unless explicitly stopped, the db2 stop dbm
database manager continues to be active.
This command does not stop the database
manager instance if any applications are
connected to databases. If there are no
database connections, but there are
instance attachments, the command forces
the instance attachments to stop first.
Then, it stops the database manager. This
command also deactivates any
outstanding database activations before
stopping the database manager.

This command is not valid on a client.

The Tivoli Storage Manager server starts

and stops the instance and database
whenever the server starts and halts.
Important: Allow the Tivoli Storage
Manager server to manage the starting
and stopping of the instance and database
unless otherwise directed by IBM support.

Chapter 7. Reference: DB2 commands for server databases 91

92 IBM Tivoli Storage Manager for AIX: Installation Guide
Chapter 8. Uninstalling Tivoli Storage Manager
You can use the following procedures to uninstall Tivoli Storage Manager. Before
you remove Tivoli Storage Manager, ensure that you do not lose your backup and
archive data.

Before you begin

Complete the following steps before you uninstall Tivoli Storage Manager:
v Complete a full database backup.
v Save a copy of the volume history and device configuration files.
v Store the output volumes in a safe location.

About this task

You can uninstall Tivoli Storage Manager by using any of the following methods: a
graphical wizard, the command line in console mode, or silent mode.

“Uninstalling Tivoli Storage Manager by using a graphical wizard”

“Uninstalling Tivoli Storage Manager in console mode” on page 94

“Uninstalling Tivoli Storage Manager in silent mode” on page 94

What to do next

See Chapter 2, “Installing the Tivoli Storage Manager server components,” on page
31 for installation steps to reinstall the Tivoli Storage Manager components.

Uninstalling Tivoli Storage Manager by using a graphical wizard

You can uninstall Tivoli Storage Manager by using the IBM Installation Manager
installation wizard.

Procedure
1. Start the Installation Manager.
In the directory where the Installation Manager is installed, go to the eclipse
subdirectory (for example, /opt/IBM/InstallationManager/eclipse), and issue
the following command:
./IBMIM
2. Click Uninstall.
3. Select Tivoli Storage Manager server, and click Next.
4. Click Uninstall.
5. Click Finish.

© Copyright IBM Corp. 1993, 2014 93

Uninstalling Tivoli Storage Manager

Uninstalling Tivoli Storage Manager in console mode

To uninstall Tivoli Storage Manager by using the command line, you must run the
uninstallation program of IBM Installation Manager from the command line with
the parameter for console mode.

Procedure
1. In the directory where IBM Installation Manager is installed, go to the
following subdirectory:
eclipse/tools
For example:
/opt/IBM/InstallationManager/eclipse/tools
2. From the tools directory, issue the following command:
./imcl -c
3. To uninstall, enter 5.
4. Choose to uninstall from the IBM Tivoli Storage Manager package group.
5. Enter N for Next.
6. Choose to uninstall the IBM Tivoli Storage Manager server package.
7. Enter N for Next.
8. Enter U for Uninstall.
9. Enter F for Finish.

Uninstalling Tivoli Storage Manager in silent mode

To uninstall Tivoli Storage Manager in silent mode, you must run the
uninstallation program of IBM Installation Manager from the command line with
the parameters for silent mode.

Before you begin

The input directory, which is in the directory where the installation package is
extracted, contains the following sample response files for installing, updating, and
uninstalling the server:
v install_response_sample.xml
v update_response_sample.xml
v uninstall_response_sample.xml
You can use these sample files as they are with the default values, or you can
customize them to suit your needs.

Procedure
1. In the directory where IBM Installation Manager is installed, go to the
following subdirectory:
eclipse/tools
For example:
/opt/IBM/InstallationManager/eclipse/tools
2. From the tools directory, issue the following command, where response_file
represents the response file path, including the file name:
./imcl -input response_file -silent
The following command is an example:

94 IBM Tivoli Storage Manager for AIX: Installation Guide

 Uninstalling Tivoli Storage Manager

./imcl -input /tmp/input/uninstall_response.xml -silent

Uninstalling and reinstalling Tivoli Storage Manager

If you plan to manually reinstall Tivoli Storage Manager instead of using the
wizard, there are a number of steps to take to preserve your server instance names
and database directories. During an uninstallation, any server instances previously
set up are removed, but the database catalogs for those instances still exist.

About this task

If you are using the wizard to upgrade from Tivoli Storage Manager Version 6.2 or
Version 6.3, it is not necessary to complete these steps, the wizard completes them
automatically. To manually uninstall and reinstall Tivoli Storage Manager, complete
the following steps:
1. Make a list of your current server instances before proceeding to the
uninstallation. Run the following command:
/opt/tivoli/tsm/db2/instance/db2ilist
2. Run the following commands for every server instance:
db2 attach to instance_name
db2 get dbm cfg show detail
db2 detach

Keep a record of the database path for each instance.

3. Uninstall Tivoli Storage Manager. See Chapter 8, “Uninstalling Tivoli Storage
Manager,” on page 93.
4. When you uninstall any version of Tivoli Storage Manager 6.1 or later,
including a fix pack, an instance file is created. The instance file is created to
help reinstall Tivoli Storage Manager. Check this file and use the information
when you are prompted for the instance credentials when reinstalling. In silent
installation mode, you provide these credentials using the INSTANCE_CRED
variable.
You can find the instance file in the following location:
/etc/tivoli/tsm/instanceList.obj
5. Reinstall Tivoli Storage Manager. See Chapter 2, “Installing the Tivoli Storage
Manager server components,” on page 31.
6. Recreate your server instances. See “Creating the server instance” on page 45.

Tip: The installation wizard configures the server instances but you must
verify that they exist. If they do not exist, you must manually configure them.
7. Catalog the database. Log in to each server instance as the instance user, one at
a time, and issue the following commands:
db2 catalog database tsmdb1
db2 attach to instance_name
db2 update dbm cfg using dftdbpath instance_directory
db2 detach
8. Verify that the server instance was created successfully. Issue this command:
/opt/tivoli/tsm/db2/instance/db2ilist
9. Verify that Tivoli Storage Manager recognizes the server instance by listing
your directories. Your home directory appears if you did not change it. Your
instance directory does appear if you used the configuration wizard. Issue this
command:
db2 list database directory

Chapter 8. Uninstalling Tivoli Storage Manager 95

Uninstalling Tivoli Storage Manager

If you see TSMDB1 listed, you can start the server.

96 IBM Tivoli Storage Manager for AIX: Installation Guide

Part 2. Installing and upgrading Tivoli Monitoring for Tivoli
Storage Manager
IBM Tivoli Monitoring for Tivoli Storage Manager brings together multiple
components to monitor Tivoli Storage Manager servers, and to produce historical
reports about server and client activities.

© Copyright IBM Corp. 1993, 2014 97

98 IBM Tivoli Storage Manager for AIX: Installation Guide
 Chapter 9. Installing Tivoli Monitoring for Tivoli Storage
Manager
Tivoli Monitoring for Tivoli Storage Manager brings together multiple components,
to provide real-time monitoring, and historical reporting for your Tivoli Storage
Manager servers.

About this task

Tivoli Common Reporting

Cognos reports User ID:

smadmin

Historical
reports

User ID:
Tivoli Monitoring for Tivoli Enterprise Tivoli Enterprise Tivoli Data Warehouse
Tivoli Storage Manager Portal server Monitoring server
itmuser

ITMuser
Tivoli Enterprise Portal
monitoring
User ID: User ID:
sysadmin
DB2 database db2inst1

db2admin

Tivoli Monitoring for

Tivoli Storage Manager
agent instances

Tivoli Storage Manager servers

Figure 3. Tivoli Monitoring for Tivoli Storage Manager components that provide the reporting and monitoring
capabilities

Procedure

Building a system that can monitor data and produce reports includes the
following tasks:
| 1. Installing Tivoli Monitoring for Tivoli Storage Manager, which includes these
| components:
| v DB2

© Copyright IBM Corp. 1993, 2014 99

 Installing Tivoli Monitoring for Tivoli Storage Manager

| v IBM Tivoli Monitoring, which includes:

| – Tivoli Enterprise Portal server
| – Tivoli Enterprise Monitoring server
| – Summarization Pruning agent
| – Warehouse Proxy agent
| – Tivoli Monitoring for Tivoli Storage Manager agent
| – Tivoli Data Warehouse
| 2. Installing Jazz for Service Management, which requires the following
| components:
| v Tivoli Common Reporting
| v WebSphere® Application Server
3. Creating and configuring agent instances to connect to the Tivoli Storage
Manager servers that you want to monitor.

Planning to install
Be sure to review all applicable planning information, including system
requirements, capacity planning, and installation scenarios, before you install the
software.

Before you install Tivoli Monitoring for Tivoli Storage Manager and Jazz for
Service Management, complete the following tasks:
1. Choose an installation scenario that best suits your needs.
2. Read the system requirements that are required for your operating system.
3. Review the capacity planning information.
4. Review the installation worksheet and note the user IDs, passwords, and other
values that are required during installation.

Restriction: Install Tivoli Monitoring for Tivoli Storage Manager on a system that
is different from where the Tivoli Storage Manager server is installed.

Installation scenarios
Before you install Tivoli Monitoring for Tivoli Storage Manager, choose the
scenario that best meets the needs of your business.
v Scenario 1: New installation, intending to monitor 1 - 5 Tivoli Storage Manager
servers.
v Scenario 2: New installation, intending to monitor more than 5 Tivoli Storage
Manager servers.
v Scenario 3: Installing in to an existing IBM Tivoli Monitoring environment,
intending to monitor 1 - 5 Tivoli Storage Manager servers.
v Scenario 4: Installing in to an existing IBM Tivoli Monitoring environment,
intending to monitor more than 5 Tivoli Storage Manager servers.

| Consider the following restrictions before you decide which scenario to use:
| v If you have a Tivoli Storage Manager server that is in a different time zone than
| the system with Tivoli Monitoring for Tivoli Storage Manager, install the
| monitoring agent on the Tivoli Storage Manager server. See Scenario 2 to install
| the agent directly on the Tivoli Storage Manager server.

100 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| v If you have more than five servers, install the monitoring agent on each of the
| servers because it is the most efficient use of memory on both the Tivoli Storage
| Manager server and the Tivoli Monitoring for Tivoli Storage Manager server.
| v You can only install the monitoring agent on AIX®, Linux X86_64, and Windows
| operating systems.
Table 19. Installation scenarios
Scenario
Number Description Tasks that you must complete
Scenario 1 Use this scenario for a Perform all the tasks in this scenario on the
new installation with a same system:
plan to monitor and 1. Install Tivoli Monitoring for Tivoli Storage
report on 1- 5 Tivoli Manager. The approximate installation
Storage Manager servers. time is 3 hours, depending on the speed
of your system.
2. Create and configure the monitoring
agents for the Tivoli Storage Manager
servers that you want to monitor. The
approximate configuration time is 3
minutes per agent.
| Restriction: You cannot install Tivoli
| Monitoring for Tivoli Storage Manager on a
| system where the Tivoli Storage Manager
| server is installed. However, you can install
| the monitoring agent on any supported
| operating system, including any Tivoli
| Storage Manager servers that you want to
| monitor.
Scenario 2 Use this scenario for a 1. Install Tivoli Monitoring for Tivoli Storage
new installation with a Manager. The approximate installation
plan to monitor and time is 3 hours, depending on the speed
report on more than 5 of your system.
Tivoli Storage Manager
| servers.
2. Install monitoring agents on each
| supported Tivoli Storage Manager server
| that you want to monitor. The
| approximate installation time is 10 - 15
| minutes per additional agent.
3. Create and configure the monitoring
agents to connect to the Tivoli Enterprise
Monitoring server host that was installed
in Step 1. The approximate configuration
time is 3 minutes per agent.
| Restriction: You cannot install Tivoli
| Monitoring for Tivoli Storage Manager on a
| system where the Tivoli Storage Manager
| server is installed. However, you can install
| the monitoring agent on any supported
| operating system, including any Tivoli
| Storage Manager servers that you want to
| monitor.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 101

 Installing Tivoli Monitoring for Tivoli Storage Manager

Table 19. Installation scenarios (continued)

Scenario
Number Description Tasks that you must complete
Scenario 3 Use this scenario when
you install the software Prerequisite: You must have IBM Tivoli
into an existing IBM Monitoring version 6.3.0 FP2, or later
Tivoli Monitoring installed.
environment with a plan
to monitor up to 5 Tivoli Perform all the tasks in this scenario on the
Storage Manager servers. same system:
1. Install the monitoring agent on the IBM
Tivoli Monitoring server where Tivoli
Enterprise Monitoring server and Tivoli
Enterprise Portal server are installed. The
approximate installation time is 15 - 30
minutes per additional agent.
2. Create and configure the monitoring
agents to point to the system where the
Tivoli Enterprise Monitoring server and
Tivoli Enterprise Portal server are
installed. The approximate configuration
time is 10 minutes per agent.
| Restriction: You cannot install Tivoli
| Monitoring for Tivoli Storage Manager on a
| system where the Tivoli Storage Manager
| server is installed. However, you can install
| the monitoring agent on any supported
| operating system, including any Tivoli
| Storage Manager servers that you want to
| monitor.
Scenario 4 Use this scenario when
you install the software Prerequisite: You must have IBM Tivoli
into an existing IBM Monitoring version 6.3.0 FP2, or later
Tivoli Monitoring installed.
environment with a plan 1. Install the monitoring agent on the
to monitor more than 5 supported Tivoli Storage Manager server
Tivoli Storage Manager that you want to monitor. The
servers. approximate installation time is 15 - 30
minutes per additional agent.
2. Create and configure the monitoring
agents to point to the Tivoli Enterprise
Monitoring server host that was installed
in Step 1. The approximate configuration
time is 10 minutes per agent.
| Restriction: You cannot install Tivoli
| Monitoring for Tivoli Storage Manager on a
| system where the Tivoli Storage Manager
| server is installed. However, you can install
| the monitoring agent on any supported
| operating system, including any Tivoli
| Storage Manager servers that you want to
| monitor.

102 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

System requirements for Tivoli Monitoring for Tivoli Storage

Manager
Review the hardware and software requirements that are applicable for your
system before you install Tivoli Monitoring for Tivoli Storage Manager and the
other software.

| You can install the Tivoli Monitoring for Tivoli Storage Manager, which includes
| the monitoring agent to monitor the Tivoli Storage Manager servers. You can also
| install the monitoring agent separately on your Tivoli Storage Manager servers.
| You can install use the monitoring agent on the following Tivoli Storage Manager
| operating systems:
| v AIX
| v Linux X86_64
| v Microsoft Windows

| System requirements
| Your system must meet the hardware and software requirements before you install
| Tivoli Monitoring for Tivoli Storage Manager on an AIX system.

| The following tables list the minimum hardware and software requirements that
| are required for Tivoli Monitoring for Tivoli Storage Manager. You can find the
| latest information on the IBM Support Portal at http://www.ibm.com/support/
| docview.wss?uid=swg21678084.

| Hardware requirements

| Table 20 describes the hardware requirements for Tivoli Monitoring for Tivoli
| Storage Manager.
| Table 20. Hardware requirements
| Type of
| hardware Hardware requirements
|| Hardware v A 64-bit Common Hardware Reference Platform (CHRP) architecture.
| Notes:
| 1. To verify that your system is a CHRP architecture system, issue the
| lscfg command, and look for the following output: Model
| Architecture: chrp.
| 2. You must upgrade POWER3 processor-based systems to POWER4
| before you install DB2.
| v A multiprocessor-based computer with a 2 GHz or greater processor
| v Network interface card

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 103

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Table 20. Hardware requirements (continued)

| Type of
| hardware Hardware requirements
| Disk space The following space is required for the Tivoli Monitoring for Tivoli Storage
| Manager software:
| v 10 MB free disk space (minimum) in the / directory
| v 800 MB free space (minimum) in the /home directory
| v 522 MB free disk space (minimum) in the /var directory
| v 350 MB free disk space (minimum) in the /usr directory
| v 3.4 GB free disk space (minimum) in the /tmp directory
| v 8 GB free space in the installation directory, 30 GB recommended as
| requirements increase as historical data is gathered and stored in the
| WAREHOUS database
| v 4.45 GB free space in the IBM Jazz for Service Management installation
| directory

| The following space is required for the Tivoli Storage Manager monitoring
| agent:
| v 10 MB free disk space (minimum) in the / directory
| v 5 MB free disk space (minimum) in the /var directory
| v 350 MB free disk space (minimum) in the /usr directory
| v 200 MB free disk space (minimum) in the /tmp directory
| The Tivoli Monitoring for Tivoli Storage Manager monitoring agent can be
| used only with IBM Tivoli Monitoring version 6.3.0 FP2 or later.
|| Memory v 8 GB minimum, 16 GB recommended
| v 4 GB of available memory is required at installation time.
| v 2 GB of additional memory per agent instance that is created on the
| Tivoli Monitoring for Tivoli Storage Manager system
| v If a single Tivoli Storage Manager monitoring agent is installed on a
| Tivoli Storage Manager server, no increases in memory requirements are
| required.
| Monitor 1024 x 768 (minimum)
| resolution
|

| Software requirements

| Table 21 on page 105 describes the minimum software requirements for Tivoli
| Monitoring for Tivoli Storage Manager.

104 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Table 21. Software requirements

| Type of
| software Minimum software requirements
|| Operating v AIX 6.1
| system
| v AIX 7.1
| Notes: If the system was manually upgraded to meet the system
| requirements, and was not a new operating system installation, you must
| install I/O completion ports (IOCP) separately. You can obtain the IOCP
| libraries from the AIX installation CD and configure IOCP on the DB2
| server. Client-only installations do not require IOCP.

| For details about known issues for AIX systems see http://
| www.ibm.com/support/docview.wss?&uid=swg21165448.
|| Libraries v AIX 6.1 running in a 64-bit kernel environment with the following
| additional requirements:
| – AIX 6.1 TL7 PS6 or later
| – Minimum C++ runtime level with the xlC.rte 12.1.0.0 or later file
| sets. These file sets are included in the June 2008 fix pack for IBM
| C++ Runtime Environment Components for AIX.
| v AIX 7.1 running in a 64-bit kernel environment.
| – AIX 7.1 TL1 SP6 or later
| – Minimum C++ runtime level requires the xlC.rte 12.1.0.0 or later file
| sets. These file sets are included in the April 2010 IBM C++ Runtime
| Environment Components for AIX V11.1 package.
| v The following libraries must be installed:
| X11.motif.lib-2.1
| atk-1.12.3-2
| cairo-1.8.8-1
| expat-2.0.1-1
| fontconfig-2.4.2-1
| freetype2-2.3.9-1
| gettext-0.10.40-6
| glib2-2.12.4-2
| gtk2-2.10.6-4
| libjpeg-6b-6
| libpng-1.2.32-2
| libtiff-3.8.2-1
| pango-1.14.5-4
| pixman-0.12.0-3
| xcursor-1.1.7-3
| xft-2.1.6-5
| xrender-0.9.1-3
| zlib-1.2.3-3
| /usr/lib/libXt.a
| /usr/lib/libX11.a
| /usr/lib/libXm.a
| /usr/lib/libXext.a
| /usr/lib/libXi.a
| /usr/lib/libXp.a
| /usr/lib/libSM.a
| /usr/lib/libICE.a
| /usr/lib/libIM.a

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 105

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Table 21. Software requirements (continued)

| Type of
| software Minimum software requirements
| Communication One of the following communication protocols:
|| protocol v Named Pipes
| v TCP/IP Version 4 or Version 6
| Restriction: The same TCP/IP version must be configured on both the
| source and target systems.
| Web browser One of the following web browsers:
| v Microsoft Internet Explorer 8.0 and future fix packs
| v Microsoft Internet Explorer 9.0 and future fix packs
| v Mozilla Firefox 17 Extended Service Release (ESR)
| JavaScript must be enabled.

| IBM Java version 7 is required to start the Tivoli Enterprise Portal. IBM
| Java version 7 is included with Tivoli Monitoring for Tivoli Storage
| Manager.

| If the Common Reporting portlet is blank when opened in Internet

| Explorer, the default security settings might be too restrictive. Complete
| these steps to modify the security settings:
| 1. In the Internet Explorer window, click Tools > Internet Options. On
| the Security tab, click Custom level.
| 2. Locate the Miscellaneous category, disable the Access data sources
| across domains option, and click OK to apply the changes.
| Tip: If your browser does not display correctly, consider using a different
| browser.

| To avoid potential compatibility issues with web browsers, you can view
| the Tivoli Enterprise Portal remotely by using the Java Web Start applet:
| 1. Connect to http://hostname:1920.
| 2. Click IBM Tivoli Enterprise Portal Web Start Client to start the Java
| Web Start client.
| 3. Optional: Create a desktop shortcut to start Tivoli Enterprise Portal in
| the future.
| Ports IBM Tivoli Monitoring uses ports 1918 and 1920.

| Jazz for Service Management uses the following ports:

| 9362, 16310, 16311, 16312, 16313, 16314, 16315,
| 16316, 16318, 16320, 16321, 16322, 163203, 16324
|| Additional v Korn Shell
| software
| requirements
| and
| considerations
|
|

106 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| IBM Installation Manager

| Tivoli Monitoring for Tivoli Storage Manager uses IBM Installation Manager, which
| is an installation program that can use remote or local software repositories to
| install or update many IBM products.

| If the required version of IBM Installation Manager is not already installed, it is

| automatically installed or upgraded when you install Tivoli Monitoring for Tivoli
| Storage Manager. It must remain installed on the system so that you can update or
| uninstall Tivoli Monitoring for Tivoli Storage Manager as needed.

| The following list contains explanations of some terms that are used in IBM
| Installation Manager:
| Offering
| An installable unit of a software product.
| The Tivoli Monitoring for Tivoli Storage Manager offering contains all of
| the media that IBM Installation Manager requires to install Tivoli
| Monitoring for Tivoli Storage Manager.
| Package
| The group of software components that are required to install an offering.
| The Tivoli Monitoring for Tivoli Storage Manager package contains the
| following components:
| v IBM Installation Manager installation program
| v DB2
| v IBM Tivoli Monitoring
| v Tivoli Storage Manager agent
| Package group
| A set of packages that share a common parent directory.
| The default package group for the Tivoli Monitoring for Tivoli Storage
| Manager package is IBM Tivoli Monitoring for Tivoli Storage Manager.
| Repository
| A remote or local storage area for data and other application resources.
| The Tivoli Monitoring for Tivoli Storage Manager package is stored in a
| repository on IBM Fix Central.
| Shared resources directory
| A directory that contains software files or plug-ins that are shared by
| packages.
| IBM Installation Manager stores installation-related files in the shared
| resources directory, including files that are used for uninstalling Tivoli
| Monitoring for Tivoli Storage Manager.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 107

 Installing Tivoli Monitoring for Tivoli Storage Manager

Capacity planning
Planning details include determining how many servers you want to monitor, how
many agents and agent instances are required, and how much memory and space
are necessary for growth over time.

About this task

The following list provides planning guidelines so you can anticipate the growth of
your system over time, depending on how many monitoring agents are in your
environment:
v Each agent instance, whether it is an IBM Tivoli Monitoring agent, or a Tivoli
Monitoring for Tivoli Storage Manager agent, requires approximately 150 MB of
memory.
| v Each agent also requires up to 300 MHz worth of a single CPU core during data
| collection.
v During a one-year period, the data WAREHOUS can grow to approximately 500
GB for each Tivoli Storage Manager server that is being monitored using the
installation defaults. This value depends on the number of nodes that are being
backed up and archived to that server, and the frequency of backups that occur.
Enabling pruning on the monitoring server can reduce the size of the
WAREHOUS database by approximately 50 percent.

Installation worksheet
Use this worksheet to record information that you need when you install and
administer Tivoli Monitoring for Tivoli Storage Manager. The worksheet includes
several passwords for user accounts that are created during the installation. The
worksheet is intended to help you remember the values that you specified after the
installation.
Table 22. Tivoli Monitoring for Tivoli Storage Manager installation worksheet
Item Description Default value* Your value
| db2inst1 Database administrator User name: db2inst1
Password:
This is the Tivoli Data Warehouse user
name and password. The password must be 8 - 14 characters in
length and can include letters, numbers,
This user has permission to complete all @, or #.
the administrative tasks in DB2.
| DB2 port Default port number The default port number is the first free
| port starting with 50000.

| Valid port numbers are 1024 - 65535.

db2grp1 This is the group that the DB2 instance
user ID belongs to.
encryption key A default encryption key is provided and IBMTivoliMonitoringEncryptionKey
the fields are prefilled with the default
key. You can specify a different key, Must be exactly 32 characters in length.
however, it is not necessary. The Valid characters are A-Z, a-z, 0-9, @, !, and
encryption key is used to establish a #.
secure connection (using SSL protocol)
between the Hub TEMS and the other
components of the IBM Tivoli Monitoring
environment.

The encryption key must be the same for

all of the agents that access the Tivoli
Enterprise Monitoring server.

108 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

Table 22. Tivoli Monitoring for Tivoli Storage Manager installation worksheet (continued)
Item Description Default value* Your value
sysadmin Tivoli Enterprise Portal user name and User name: sysadmin
password. Password:

This user ID is not automatically The password must be 8 - 14 characters in

generated during the installation process. length and can include letters, numbers,
You can log in to the Tivoli Enterprise @, or #.
Portal without specifying a password. If
you want this ID to require a password
during login, you can manually create
the sysadmin ID, and specify a password.
| Service management The administrator that is used to log on User name: smadmin
administrator ID to IBM Dashboard Application Services Password:
Hub. You can access the Tivoli Common
Reporting reports in the dashboard. Restriction: The password must be at
least 8 characters.
The user ID is created during the
installation of Jazz for Service
Management.
itmuser Tivoli Data Warehouse user name and User name: itmuser
password. Password:

This user has access to read the The password must be 8 - 14 characters in
information from the WAREHOUS length and can include letters, numbers,
database. @, or #.

Note: You are only prompted for this

information during configuration of the
warehouse, not at installation time.
DB2 home directory You can specify which directory that you The default value is /home.
want to store the DB2 instance
information. This is where the database is
stored by default.

If you specify /home, the instance

information is stored in /home/db2admin.

If you specify /information/db2, the

instance information is stored in
/information/db2/db2admin.

Ensure that there is enough space

available in this directory and that the
directory has write-access. For additional
planning help see “Capacity planning”
on page 108.
Monitoring agent You can specify the name of the Your first agent instance name:
instance name monitoring agent instance. If you intend Your second agent instance name:
to monitor more than one Tivoli Storage Your third agent instance name:
Manager server, you must have unique More agent instance names...:
agent instance names for each instance.

When you specify an instance name, the

best practice is to specify the host name
of the Tivoli Storage Manager server, or
the server name from the QUERY STATUS
command as your agent instance name.

Instance names cannot exceed 20

characters.

Note: The monitoring agent instances

can be created and configured after the
installation.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 109

Installing Tivoli Monitoring for Tivoli Storage Manager

Table 22. Tivoli Monitoring for Tivoli Storage Manager installation worksheet (continued)
Item Description Default value* Your value
Location and the name Needed if you decide to use the SSL
of the SSL certificate protocol instead of TCP IP.
*Best practices are to use the default values listed here. If you change these values, ensure that you document them because they
are needed later.

Installation checklist
The checklist summarizes the steps that are required to install and configure a
system that can monitor Tivoli Storage Manager server and client data and
produce reports. You can print this checklist and use it as a guide to verify that all
steps are completed.
Table 23. Installation checklist
Step Installation task or topic Task description
1._____ “System requirements for Tivoli Ensure that your system meets the
Monitoring for Tivoli Storage system and hardware requirements.
Manager” on page 103
2._____ “Capacity planning” on page 108 Review the capacity planning
information to ensure that you
adequately plan for growth.
3._____ “Installation worksheet” on page 108 Complete the installation worksheet to
record password values and other
installation information that you need.
4._____ “Installation scenarios” on page 100 Choose an installation scenario. The
scenario that you choose depends on
the number of servers that you intend
to monitor, and if there is an existing
Tivoli Monitoring environment before
this installation.
5._____ Installing Tivoli Monitoring for Tivoli Run the Tivoli Monitoring for Tivoli
Storage Manager on AIX systems Storage Manager installer.
Tip: If there is an existing Tivoli
Monitoring environment, install only The following components are
the monitoring agent. installed:
Installing the agent in an existing v Tivoli Monitoring, which includes
Tivoli Monitoring environment on the following components:
AIX – Tivoli Enterprise Portal server
– Tivoli Data Warehouse
– Tivoli Enterprise Monitoring
server
– Summarization pruning agent
– Warehouse proxy agent
v Tivoli Monitoring for Tivoli Storage
Manager agent
Remember: IBM Installation Manager
is also installed.

110 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

Table 23. Installation checklist (continued)

Step Installation task or topic Task description
6._____ Install or configure the monitoring
“Installing the monitoring agent” on agents to connect to the Tivoli Storage
page 119 Manager server.
“Creating and configuring the agent If you plan to monitor five or less
instance” on page 134 Tivoli Storage Manager servers,
configure the monitoring agent that
was installed on this system.

Otherwise, install and configure only

the monitoring agent on each Tivoli
Storage Manager server to be
monitored.
Tip: Create 1 agent per Tivoli Storage
Manager server instance.
7._____ “Installing Jazz for Service Install Jazz for Service Management to
Management” on page 141 get access to the Tivoli Common
Reporting feature so that you can view
Cognos® reports.
8._____ “Configuring the WAREHOUS data Run the script to import the Cognos
source and importing reports” on page reports and to connect Tivoli Common
143 Reporting to the WAREHOUS database
to generate reports.
9._____ “Verifying the installation” on page 145 Verify that the installation was
complete and successful.
Tips:
1. To view real-time Tivoli Storage Manager server activity, use the Tivoli Enterprise
Portal.
2. To view historical reports, use Tivoli Common Reporting.
3. For additional help, see Tivoli Monitoring for Tivoli Storage Manager troubleshooting
topics.

| Bypassing the prerequisites

| You can bypass the Tivoli Monitoring for Tivoli Storage Manager prerequisites on
| your test systems during the installation, such as the operating system and the
| required memory. Do not bypass the prerequisites on production systems.

| Bypassing the prerequisites by using the wizard

| You can bypass the prerequisites on a test system when you install or upgrade
| Tivoli Monitoring for Tivoli Storage Manager by using the wizard.

| Choose one of the following methods to bypass prerequisite checks:

| v If you are installing Tivoli Monitoring for Tivoli Storage Manager, issue the
| following command:
| ./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
| v If you are upgrading Tivoli Monitoring for Tivoli Storage Manager, update the
| following file to add the -DBYPASS_TSM_REQ_CHECKS=true statement. The dash in
| the -DBYPASS_TSM_REQ_CHECKS option is required and must be added on a new
| line after the -vmargs option.
| ../Installation Manager/eclipse/ibmim.ini
|

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 111

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Bypassing the prerequisites in console mode

| You can bypass the prerequisites on a test system when you install or upgrade
| Tivoli Monitoring for Tivoli Storage Manager in console mode.

| Choose one of the following methods to bypass prerequisite checks:

| v If you are installing Tivoli Monitoring for Tivoli Storage Manager, issue the
| following command:
| ./install.sh -c -acceptLicense -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
| v If you are upgrading Tivoli Monitoring for Tivoli Storage Manager, update the
| following file to add the -DBYPASS_TSM_REQ_CHECKS=true statement. The dash in
| the -DBYPASS_TSM_REQ_CHECKS option is required and must be added on a new
| line after the -vmargs option.
| ../Installation Manager/eclipse/tools/imcl.ini

| Bypassing the prerequisites in silent mode

| You can bypass the prerequisites on a test system when you install or upgrade
| Tivoli Monitoring for Tivoli Storage Manager in silent mode.

| Choose one of the following methods to bypass prerequisite checks:

| v If you are installing Tivoli Monitoring for Tivoli Storage Manager, issue the
| following command:
| ./install.sh -s -acceptLicense -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
| v If you are upgrading Tivoli Monitoring for Tivoli Storage Manager, update the
| following file to add the -DBYPASS_TSM_REQ_CHECKS=true statement. The dash in
| the -DBYPASS_TSM_REQ_CHECKS option is required and must be added on a new
| line after the -vmargs option.
| ../Installation Manager/eclipse/tools/imcl.ini
|
| AIX: Installing Tivoli Monitoring for Tivoli Storage Manager
| To install or upgrade Tivoli Monitoring for Tivoli Storage Manager, you can use the
| wizard, the command line in console mode, or by using silent mode.

| Before you begin

| Before you install Tivoli Monitoring for Tivoli Storage Manager, verify that the
| following requirements are met:
| v Ensure that your system meets the software and hardware requirements. For
| more information about the system requirements, see “System requirements for
| Tivoli Monitoring for Tivoli Storage Manager” on page 103.
| v Do not install Tivoli Monitoring for Tivoli Storage Manager on a system that has
| a Tivoli Storage Manager server installed.
| v Verify that you have the required access privileges, including user IDs and
| passwords.
| v Ensure that there are no spaces and no non-ASCII characters in the installation
| package name or in the path to the package.
| v If you are installing Tivoli Monitoring for Tivoli Storage Manager on a remote
| system by using an X display, and the local server does not have an X server
| running, the installation might fail. If this happens, you must run the wizard in
| console mode.

112 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| v If you are installation the Tivoli Monitoring for Tivoli Storage Manager
| monitoring agent in to an existing Tivoli Monitoring environment, specify the
| existing Tivoli Monitoring installation directory. The default directory is
| /opt/IBM/ITM.

| Attention: Do not alter the DB2 software that is installed with Tivoli Monitoring
| for Tivoli Storage Manager installation packages and fix packs. Do not install or
| upgrade to a different version, release, or fix pack of DB2 application because
| doing so can damage the database. Tivoli Monitoring for Tivoli Storage Manager
| can use only components and versions that are installed as part of the Tivoli
| Monitoring for Tivoli Storage Manager installation.

| About this task

| The Tivoli Monitoring for Tivoli Storage Manager software provides monitoring
| and reporting features for the Tivoli Storage Manager servers in the environment.
| You can install or upgrade the Tivoli Monitoring for Tivoli Storage Manager and
| the monitoring agents on the Tivoli Storage Manager servers.

| With the Tivoli Monitoring for Tivoli Storage Manager installation package, you
| can install or upgrade the following software:
| v Tivoli Monitoring for Tivoli Storage Manager
| v Tivoli Monitoring for Tivoli Storage Manager agent only
| To determine when and where you would install only the agent package, review
| the installation scenarios. To install the agent on a remote server, see “Installing the
| monitoring agent” on page 119.

| Restriction: You cannot install the Tivoli Monitoring for Tivoli Storage Manager
| package and the agent only package on the same system.

| AIX: Obtaining the Tivoli Monitoring for Tivoli Storage

| Manager installation package
| You can obtain the Tivoli Monitoring for Tivoli Storage Manager installation
| package from a DVD or an IBM download site such as IBM Passport Advantage.

| Before you begin

| If you plan to download the files, set the system user limit for the maximum file
| size to unlimited to ensure that the files can be downloaded correctly:
| 1. To query the maximum file size value, issue the following command from a
| command line:
| ulimit -Hf
| 2. If the system user limit for maximum file size is not set to unlimited, change it
| to unlimited by following the instructions in the documentation for your
| operating system.

| Verify that you have enough space to store the installation files when they are
| extracted from the product packages.

| Procedure
| 1. Download the two installation packages from one of the following websites, or
| you can access the files from the product DVD:

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 113

 Installing Tivoli Monitoring for Tivoli Storage Manager

| v Go to Passport Advantage site at http://www.ibm.com/software/lotus/

| passportadvantage/.
| v Go to the Tivoli Storage Manager support site at http://www.ibm.com/
| support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
| for maintenance fixes, and updates.
| 2. Depending on whether you have the DVD disks or installation packages,
| complete one of the following methods to extract the files to the file system:
| Product DVD disks
| a. Create a directory on the file system.
| b. For each DVD disk, copy the contents of the disk in to the directory
| that you created.

| Tip: You can delete the files after you install Tivoli Monitoring for
| Tivoli Storage Manager to free up space on the file system.
| Installation packages
| a. Create a directory and move the two packages that you
| downloaded in to the directory.
| b. Ensure that executable permission is set for the packages. If
| necessary, change the file permissions by issuing the following
| command:
| chmod a+x package_name.bin
| c. Extract the packages by issuing the following command for each
| package:
| ./package_name.bin
| where package_name is the name of the file that you downloaded, for
| example:
| TSMRPT-Full-Installer-1of2-AIX-7.1.0.000.bin

| Restriction: The path must contain no more than 128 characters. Do

| not extract the packages to a directory that contains previously
| extracted files, or any other files.
| 3. Ensure that the lsuser command is enabled so that the Tivoli Monitoring for
| Tivoli Storage Manager wizards work properly. By default, the command is
| enabled. You can issue the lsuser from a command line, along with a user
| name to verify that it returns a valid result.

| AIX: Installing Tivoli Monitoring for Tivoli Storage Manager by

| using the Install wizard
| You can install Tivoli Monitoring for Tivoli Storage Manager by using the Install
| wizard of IBM Installation Manager.

| Before you begin

| Take the following actions before you start the installation:

| v Verify that you copied the DVD files to the local system, or that you
| downloaded and extracted the packages for Tivoli Monitoring for Tivoli Storage
| Manager.
| v Verify that the following RPM files are installed:
| atk-1.12.3-2.aix5.2.ppc.rpm
| cairo-1.8.8-1.aix5.2.ppc.rpm
| expat-2.0.1-1.aix5.2.ppc.rpm

114 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| fontconfig-2.4.2-1.aix5.2.ppc.rpm
| freetype2-2.3.9-1.aix5.2.ppc.rpm
| gettext-0.10.40-6.aix5.1.ppc.rpm
| glib2-2.12.4-2.aix5.2.ppc.rpm
| gtk2-2.10.6-4.aix5.2.ppc.rpm
| libjpeg-6b-6.aix5.1.ppc.rpm
| libpng-1.2.32-2.aix5.2.ppc.rpm
| libtiff-3.8.2-1.aix5.2.ppc.rpm
| pango-1.14.5-4.aix5.2.ppc.rpm
| xcursor-1.1.7-3.aix5.2.ppc.rpm
| xft-2.1.6-5.aix5.1.ppc.rpm
| xrender-0.9.1-3.aix5.2.ppc.rpm
| zlib-1.2.3-3.aix5.1.ppc.rpm
| pixman-0.12.0-3.aix5.2.ppc.rpm

| Tip: You can issue the following command from a command line to determine
| whether the RPM files are installed:
| rpm -qa |grep rpm_package

| where rpm_package is the name of the RPM package.

| If the RPM files are not installed, complete the steps in Installing RPM files for
| the wizard mode.
| v Verify that the operating system is set to the language that you require. By
| default, the language of the operating system is the language that is used during
| the installation.

| About this task

| With the Tivoli Monitoring for Tivoli Storage Manager installation package, you
| can install or upgrade the following software:
| v Tivoli Monitoring for Tivoli Storage Manager
| v Tivoli Monitoring for Tivoli Storage Manager agent only
| To determine when and where you would install only the agent package, review
| the installation scenarios. To install the agent on a remote server, see “Installing the
| monitoring agent” on page 119.

| Restriction: You cannot install the Tivoli Monitoring for Tivoli Storage Manager
| package and the agent only package on the same system.

| Procedure

| To install Tivoli Monitoring for Tivoli Storage Manager, complete the following
| steps:
| 1. Change to the directory where you extracted the installation files.
| 2. Start the wizard by issuing the following command:
| ./install.sh

| Results

| If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory. You can view
| installation log files by clicking File > View Log from the IBM Installation
| Manager tool.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 115

 Installing Tivoli Monitoring for Tivoli Storage Manager

| What to do next

| Install Jazz for Service Management to view historical reports. Follow the steps in
| “Installing Jazz for Service Management” on page 141.

| Tip: Review the checklist to ensure that you complete all of the steps to install and
| configure Tivoli Monitoring for Tivoli Storage Manager.
| Related concepts:
| Resolving Tivoli Monitoring for Tivoli Storage Manager problems
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.tshoot.doc/c_pdg_reportprobs.html)

| AIX: Installing RPM files for the wizard mode

| Before you can use the wizard to install Tivoli Monitoring for Tivoli Storage
| Manager, you must ensure that the necessary RPM files are installed.

| About this task

| The following RPM files must be installed before you use the wizard of IBM
| Installation Manager to install or upgrade Tivoli Monitoring for Tivoli Storage
| Manager:
| atk-1.12.3-2.aix5.2.ppc.rpm
| cairo-1.8.8-1.aix5.2.ppc.rpm
| expat-2.0.1-1.aix5.2.ppc.rpm
| fontconfig-2.4.2-1.aix5.2.ppc.rpm
| freetype2-2.3.9-1.aix5.2.ppc.rpm
| gettext-0.10.40-6.aix5.1.ppc.rpm
| glib2-2.12.4-2.aix5.2.ppc.rpm
| gtk2-2.10.6-4.aix5.2.ppc.rpm
| libjpeg-6b-6.aix5.1.ppc.rpm
| libpng-1.2.32-2.aix5.2.ppc.rpm
| libtiff-3.8.2-1.aix5.2.ppc.rpm
| pango-1.14.5-4.aix5.2.ppc.rpm
| xcursor-1.1.7-3.aix5.2.ppc.rpm
| xft-2.1.6-5.aix5.1.ppc.rpm
| xrender-0.9.1-3.aix5.2.ppc.rpm
| zlib-1.2.3-3.aix5.1.ppc.rpm
| pixman-0.12.0-3.aix5.2.ppc.rpm

| Tip: You can issue the following command from a command line to determine
| whether the RPM files are installed:
| rpm -qa |grep rpm_package

| where rpm_package is the name of the RPM package.

| Procedure

| To install the necessary RPM files, complete the following steps:

| 1. Ensure that there is at least 150 MB of free space in the /opt file system.
| 2. To install the RPM files, choose one of the following options:
| v If you plan to install Tivoli Monitoring for Tivoli Storage Manager from the
| product DVD, take the following actions:
| a. In the base directory of the DVD, change to the gtk directory.
| b. Copy the download-prerequisites.sh file to a location where you can
| download the RPM files.

116 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| v If you obtained the Tivoli Monitoring for Tivoli Storage Manager installation
| package from an IBM download site, from the directory where the
| installation package file is extracted, go to the gtk directory.
| 3. Download the RPM files to the current working directory from the IBM AIX
| Toolbox for Linux Applications website by issuing the following command:
| download-prerequisites.sh
| 4. From the directory that contains the RPM files that you downloaded, install
| them by issuing the following command:
| rpm -Uvh *.rpm

| AIX: Installing Tivoli Monitoring for Tivoli Storage Manager by

| using console mode
| You can install Tivoli Monitoring for Tivoli Storage Manager by using the
| command line in console mode.

| Before you begin

| Take the following actions before you start the installation:

| v Verify that you copied the DVD files to the local system, or that you
| downloaded and extracted the packages for Tivoli Monitoring for Tivoli Storage
| Manager.
| v Verify that the operating system is set to the language that you require. By
| default, the language of the operating system is the language that is used during
| the installation.

| About this task

| With the Tivoli Monitoring for Tivoli Storage Manager installation package, you
| can install or upgrade the following software:
| v Tivoli Monitoring for Tivoli Storage Manager
| v Tivoli Monitoring for Tivoli Storage Manager agent only
| To determine when and where you would install only the agent package, review
| the installation scenarios. To install the agent on a remote server, see “Installing the
| monitoring agent” on page 119.

| Restriction: You cannot install the Tivoli Monitoring for Tivoli Storage Manager
| package and the agent only package on the same system.

| Procedure

| To install Tivoli Monitoring for Tivoli Storage Manager, complete the following
| steps:
| 1. Change to the directory where you extracted the installation files.
| 2. Start the wizard in console mode by issuing the following command from a
| command line:
| ./install.sh -c
| 3. Optional: Generate a response file as part of a console mode installation.
| Complete the console mode installation options, and in the Summary pane,
| specify G to generate the responses.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 117

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Results

| If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory, for example:
| /var/ibm/InstallationManager/logs

| What to do next

| Install Jazz for Service Management to view historical reports. Follow the steps in
| “Installing Jazz for Service Management” on page 141.

| Tip: Review the checklist to ensure that you complete all of the steps to install and
| configure Tivoli Monitoring for Tivoli Storage Manager.
| Related concepts:
| Resolving Tivoli Monitoring for Tivoli Storage Manager problems
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.tshoot.doc/c_pdg_reportprobs.html)

| AIX: Installing Tivoli Monitoring for Tivoli Storage Manager in

| silent mode
| You can install the Tivoli Monitoring for Tivoli Storage Manager in silent mode by
| specifying a response file.

| Before you begin

| The input directory, which is in the directory where the installation files were
| extracted, contains the following sample response files to install, update, and
| uninstall Tivoli Monitoring for Tivoli Storage Manager:
| v install_response_sample.xml
| v update_response_sample.xml
| v uninstall_response_sample.xml
| You must edit the sample files before you use them.

| About this task

| With the Tivoli Monitoring for Tivoli Storage Manager installation package, you
| can install or upgrade the following software:
| v Tivoli Monitoring for Tivoli Storage Manager
| v Tivoli Monitoring for Tivoli Storage Manager agent only
| To determine when and where you would install only the agent package, review
| the installation scenarios. To install the agent on a remote server, see “Installing the
| monitoring agent” on page 119.

| Restriction: You cannot install the Tivoli Monitoring for Tivoli Storage Manager
| package and the agent only package on the same system.

| Procedure
| 1. Create a response file, or use one of the sample response files, such as
| install_response_sample.xml or update_response_sample.xml.
| 2. Edit the response file and specify a DB2 administrator password and the
| sysadmin user ID. You can also change other defaults if you need.

118 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| 3. Start the silent installation by issuing the following command from the
| directory where the installation files were extracted:
| ./install.sh -s -input response_file -acceptLicense

| where response_file is the response file path, including the file name.

| Results

| If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory, for example:
| /var/ibm/InstallationManager/logs

| What to do next

| Install Jazz for Service Management to view historical reports. Follow the steps in
| “Installing Jazz for Service Management” on page 141.

| Create and configure an agent instance to start collecting data. Follow the steps in
| “Creating and configuring the agent instance” on page 134.

| Tip: Review the checklist to ensure that you complete all of the steps to install and
| configure Tivoli Monitoring for Tivoli Storage Manager.
| Related concepts:
| Resolving Tivoli Monitoring for Tivoli Storage Manager problems
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.tshoot.doc/c_pdg_reportprobs.html)

Installing the monitoring agent

You can install monitoring agents on any remote server that you want to monitor,
or you can install the agent in to an existing IBM Tivoli Monitoring system.

About this task

The Tivoli Monitoring for Tivoli Storage Manager agent gathers data from each
Tivoli Storage Manager server, and sends it to the IBM Tivoli Monitoring server.

Restrictions:
1. To use the agent on an existing IBM Tivoli Monitoring environment, you must
install the agent on the existing Tivoli Enterprise Monitoring server.
2. If you plan to monitor a Tivoli Storage Manager server in a different time zone
than the monitoring server, install the monitoring agent on the Tivoli Storage
Manager server.
| 3. The monitoring agent is only supported on AIX, Linux X86_64, and Windows.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 119

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Installing the monitoring agent on remote servers

| You can install a Tivoli Monitoring for Tivoli Storage Manager monitoring agent on
| any supported server that you want to monitor. To install or upgrade the
| monitoring agent, you can use the installation wizard, the command line in console
| mode, or by using silent mode.

| Before you begin

| Before you decide whether you must install the monitoring agent directly on your
| Tivoli Storage Manager server, consider the following items:
| v The monitoring server can handle up to five monitoring agents. For more
| agents, you must install the monitoring agent directly on each of the Tivoli
| Storage Manager servers that you want to monitor. Alternatively, you can install
| the monitoring agent on any supported operating system and configure an agent
| instance to connect to the Tivoli Storage Manager server that you want to
| monitor.
| v If you create and configure an agent instance on the Tivoli Storage Manager
| server, instead of the monitoring server, you can help avoid an increase in
| memory requirements on the IBM Tivoli Monitoring server.
| v Review the requirements for the operating systems that the monitoring agent is
| supported on. See “System requirements for Tivoli Monitoring for Tivoli Storage
| Manager” on page 103.

| Installing the monitoring agent by using the Install wizard

| You can install the monitoring agent by using the Install wizard.

| Before you begin

| Take the following actions before you start the installation:

| v Verify that you copied the DVD files to the local system, or that you
| downloaded and extracted the packages for Tivoli Monitoring for Tivoli Storage
| Manager.
| v Verify that the following RPM files are installed:
| atk-1.12.3-2.aix5.2.ppc.rpm
| cairo-1.8.8-1.aix5.2.ppc.rpm
| expat-2.0.1-1.aix5.2.ppc.rpm
| fontconfig-2.4.2-1.aix5.2.ppc.rpm
| freetype2-2.3.9-1.aix5.2.ppc.rpm
| gettext-0.10.40-6.aix5.1.ppc.rpm
| glib2-2.12.4-2.aix5.2.ppc.rpm
| gtk2-2.10.6-4.aix5.2.ppc.rpm
| libjpeg-6b-6.aix5.1.ppc.rpm
| libpng-1.2.32-2.aix5.2.ppc.rpm
| libtiff-3.8.2-1.aix5.2.ppc.rpm
| pango-1.14.5-4.aix5.2.ppc.rpm
| xcursor-1.1.7-3.aix5.2.ppc.rpm
| xft-2.1.6-5.aix5.1.ppc.rpm
| xrender-0.9.1-3.aix5.2.ppc.rpm
| zlib-1.2.3-3.aix5.1.ppc.rpm
| pixman-0.12.0-3.aix5.2.ppc.rpm

| Tip: You can issue the following command from a command line to determine
| whether the RPM files are installed:
| rpm -qa |grep rpm_package

| where rpm_package is the name of the RPM package.

120 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| If the RPM files are not installed, complete the steps in Installing RPM files for
| the wizard mode.
| v Verify that the operating system is set to the language that you require. By
| default, the language of the operating system is the language that is used during
| the installation.

| Procedure

| To install Tivoli Monitoring for Tivoli Storage Manager, complete the following
| steps:
| 1. Change to the directory where you extracted the installation files.
| 2. Start the wizard by issuing the following command:
| ./install.sh

| What to do next

| Create and configure an agent instance to start collecting data. Follow the steps in
| “Creating and configuring the agent instance” on page 134.

| If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory. You can view
| installation log files by clicking File > View Log from the IBM Installation
| Manager tool.

| Installing the monitoring agent in console mode

| You can install the monitoring agent by using the command line in console mode.

| About this task

| Take the following actions before you start the installation:

| v Verify that you copied the DVD files to the local system, or that you
| downloaded and extracted the packages for Tivoli Monitoring for Tivoli Storage
| Manager.
| v Verify that the operating system is set to the language that you require. By
| default, the language of the operating system is the language that is used during
| the installation.

| Procedure

| To install Tivoli Monitoring for Tivoli Storage Manager, complete the following
| steps:
| 1. Change to the directory where you extracted the installation files.
| 2. Start the wizard in console mode by issuing the following command from a
| command line:
| ./install.sh -c
| 3. Optional: Generate a response file as part of a console mode installation.
| Complete the console mode installation options, and in the Summary pane,
| specify G to generate the responses.

| What to do next

| Create and configure an agent instance to start collecting data. Follow the steps in
| “Creating and configuring the agent instance” on page 134.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 121

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Installing the monitoring agent in silent mode

| You can install the monitoring agent in silent mode by specifying a response file.

| Before you begin

| The input directory, which is in the directory where the installation files were
| extracted, contains the following sample response files to install, update, and
| uninstall the Tivoli Monitoring for Tivoli Storage Manager monitoring agent:
| v install_agent_only_sample.xml
| v update_agent_only_sample.xml
| v uninstall_agent_only_sample

| Procedure
| 1. Create a response file, or use one of the sample response files, such as
| install_agent_only_sample.xml or update_agent_only_sample.xml.
| 2. Start the silent installation by issuing the following command from the
| directory where the installation files were extracted:
| ./install.sh -s -input response_file -acceptLicense

| where response_file is the response file path, including the file name.

| What to do next

| Create and configure an agent instance to start collecting data. Follow the steps in
| “Creating and configuring the agent instance” on page 134.

AIX: Installing and deploying monitoring agents in an existing

Tivoli Monitoring environment
Remotely deploying monitoring agents is intended only for users who purchased
IBM Tivoli Monitoring separately from Tivoli Storage Manager, and who are
already running an IBM Tivoli Monitoring server. By remotely deploying
monitoring agents, you can monitor Tivoli Storage Manager servers with the
existing IBM Tivoli Monitoring server.

About this task

The operating system agent that is required for remote deployment is not included
in the version of IBM Tivoli Monitoring that is embedded in Tivoli Monitoring for
Tivoli Storage Manager. Therefore, you cannot use remote deployment without
purchasing IBM Tivoli Monitoring.

AIX: Installing monitoring agents, or application support files in

an existing IBM Tivoli Monitoring environment on AIX and Linux
systems
If you have an existing IBM Tivoli Monitoring server that does not have Tivoli
Monitoring for Tivoli Storage Manager installed, you can run the native IBM Tivoli
Monitoring installation wizard to install more monitoring agents. If you do not
want to install the agent, you can install only the application support files, which
are required by the Tivoli Enterprise Monitoring server and Tivoli Enterprise Portal
server to monitor Tivoli Storage Manager servers.

122 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

Before you begin

Restrictions to know before you begin:

v These procedures are for experienced IBM Tivoli Monitoring users only, and are not
intended for novice Tivoli Monitoring for Tivoli Storage Manager users.
v Do not install this option if you previously installed Tivoli Monitoring for Tivoli Storage
Manager. Doing so can interfere with future uninstallations or upgrades of Tivoli
Monitoring for Tivoli Storage Manager.
v You must use Tivoli Monitoring for Tivoli Storage Manager only with IBM Tivoli
Monitoring, version 6.3.0 FP2 or later. See the system requirements for your operating
system for more requirements.
v Ensure that you meet all system requirements.

Procedure

To install the monitoring agent or application support files with a user ID that has
root privileges, complete the following steps:
1. Download the package from one of the following websites:
v Go to Passport Advantage site at http://www.ibm.com/software/lotus/
passportadvantage/.
v Go to the Tivoli Storage Manager support site at http://www.ibm.com/
support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
for maintenance fixes, and updates.
The file name for installing only the monitoring agent, or only the application
support files, can be recognized by the word AGENT in capital letters, for
example:
7.1.0.000-TIV-TSMRPT-AGENT-AIX.bin
| 2. From a command line, go to the following directory:
| cd install_dir/bin

| where the install_dir is the IBM Tivoli Monitoring installation directory. The
| default directory is /opt/IBM/ITM.
3. Stop all of the Tivoli Storage Manager processes and agent instances by using
the CandleManage application, or the command-line interface.

Tip: Always stop processes by issuing the itmcmd commands, or from the
Manage Tivoli Enterprise Monitoring Services application. Do not stop
processes by using the operating system.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 123

 Installing Tivoli Monitoring for Tivoli Storage Manager

Stop the processes by using Stop the processes by using the

CandleManage: command-line interface:

| 1. Run the CandleManage program by 1. Display the agents that are running by
| issuing the following command: issuing the following command, and
| ./CandleManage & checking the output for the list of
services that are running:
./cinfo
-r
2. Stop the Summarization and Pruning
agent by issuing the following command:
./itmcmd agent stop sy
3. Stop the Warehouse Proxy by issuing the
following command:
./itmcmd
agent stop hd
4. Stop the Tivoli Enterprise Portal server
by issuing the following command:
./itmcmd agent stop cq
5. Stop the Tivoli Enterprise Monitoring
server by issuing the following
command:
./itmcmd server stop tems_server
6. Stop all of the Tivoli Storage Manager
instances by issuing the following
command:
./itmcmd agent -o instance_name stop
sk
7. Stop all of the IBM Eclipse server by
issuing the following command:
./itmcmd
server -o stop kf

4. Enter the following command in the directory where you extracted the
installation files:
./install.sh

Optionally: If you are installing from the DVD media, go to the top-level
directory on the DVD and issue the following command:
./install.sh
5. Press Enter to accept the /opt/IBM/ITM path as the default directory, or specify
the full path to a different directory. If the specified directory does not exist,
enter y when prompted to create it.

Tip: If you are installing into an existing IBM Tivoli Monitoring environment,
choose the same directory where IBM Tivoli Monitoring is installed. For
example, if you installed IBM Tivoli Monitoring in the /opt/IBM/ITM directory,
specify /opt/IBM/ITM as the destination folder for this installation.
6. Enter 1 at the prompt to Install products to the local host. For example:

124 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

Select one of the following:

1) Install products to the local host.

2) Install products to depot for remote deployment (requires TEMS).
3) Install TEMS support for remote seeding
4) Exit install.

Please enter a valid number: 1

7. Enter 1 to accept the license agreement.

8. When the list of products that can be installed is displayed, you can choose to
install the monitoring agent, or you can install only the application support
files. To install the monitoring agent, you would select number 1 and after
that completes, you would specify a value of 2, to install the support files for
Tivoli Enterprise Portal Browser Client support. After that completes, you
would specify a value of 3, and so on, until you specified all of the support
files. If you are installing only the application support files, you would begin
by selecting 2, then 3, then 4, and finally 5. For example:
Product packages are available for this operating system and component support
categories:

1) IBM Tivoli Monitoring components for this operating system

2) Tivoli Enterprise Portal Browser Client support
3) Tivoli Enterprise Portal Desktop Client support
4) Tivoli Enterprise Portal Server support
5) Tivoli Enterprise Monitoring Server support
6) Other operating systems

Type the number or type "q" to quit selection

[number "1" or "IBM Tivoli Monitoring components for this operating system"
is default]:2

Installing the monitoring agent: Installing the application support files:

Use this option if you intend to create and You must install the application support files
configure an agent instance on the Tivoli so that the Tivoli Monitoring for Tivoli
Enterprise Monitoring server. Storage Manager agent can display Tivoli
1. Enter the number that corresponds to the Storage Manager data in Tivoli Enterprise
IBM Tivoli Monitoring components for Monitoring server and Tivoli Enterprise
this operating system option. Portal server.
2. Enter a 32-character encryption key, or 1. Enter the number that corresponds to the
press Enter to use the default key. Tivoli Enterprise Portal Browser
Restriction: All agents must use the Client Support option.
same encryption key that was specified 2. Enter the number that corresponds to the
during installation of the monitoring Tivoli Enterprise Portal Desktop
server. The default encryption key is: Client Support option.
IBMTivoliMonitoringEncryptionKey. 3. When prompted again, Enter the number
that corresponds to the Tivoli
Enterprise Portal Server Support
option.
4. When prompted again, Enter the number
that corresponds to the Tivoli
Enterprise Monitoring Server Support
option.

9. Reconfigure the Tivoli Enterprise Portal server by issuing the following

command, follow the prompts, and accept all default values:
/opt/IBM/ITM/bin/itmcmd config -A cq

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 125

 Installing Tivoli Monitoring for Tivoli Storage Manager

10. Start the Tivoli Enterprise Portal server by issuing the following command:
/opt/IBM/ITM/bin/itmcmd agent start cq
11. Restart any agents that you stopped at the beginning of this installation.

What to do next

After you complete the installation, you must configure Tivoli Enterprise Portal to
collect and retain historical data for reports. See Configuring historical data
collection by using the command-line interface on AIX® and Linux systems.

You can also create and configure an agent instance. See “Creating and configuring
the agent instance” on page 134.

AIX: Remotely deploying monitoring agents

Remote deployment provides the ability to add the monitoring agent installation
packages to a central location called an agent depot. From this central location, the
packages can then be pushed out to remote locations and installed silently by
using the IBM Tivoli Monitoring operating system agent. Remote deployment is
useful for larger-scale deployments such as deploying five or more monitoring
agents.

About this task

Remote deployment can be used to deploy monitoring agents to systems that

already have the IBM Tivoli Monitoring operating system agent that is installed on
them. Remote deployment can be used for new installations or to upgrade existing
monitoring agents to new versions.

There are multiple tasks that must be completed to use remote deployment. These
tasks include the following items:
v Add the agents that you want to deploy to the agent depot on the Tivoli
Enterprise Monitoring server hub.

Requirement: The IBM Tivoli Monitoring operating system agents on the

systems that you want to deploy to must be configured to use this Tivoli
Enterprise Monitoring server hub.
v Start the remote deployment.
v Configure historical data collection.

AIX: Remote deployment preinstallation requirements:

Before you begin any remote deployment tasks, ensure that you meet the
preinstallation requirements for your system.

Remote deployment prerequisites include the following tasks:

1. Install IBM Tivoli Monitoring and configure the Tivoli Enterprise Monitoring
server hub.
| 2. Install the IBM Tivoli Monitoring 6.3.0 operating system agent on each system
| that you want to remotely deploy a monitoring agent to, and configure it to
| point to the Tivoli Enterprise Monitoring server.
3. You must also install the IBM Tivoli Monitoring application support files and
configure the Tivoli Enterprise Monitoring server hub. These steps can be
completed before or after any remote deployment tasks, but are required to
view data in historical reports.

126 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

You can verify whether these prerequisites are met by logging in to Tivoli
Enterprise Portal, selecting the systems that you want to deploy to, and verifying
that the operating system agent is displaying information. For example, select the
Memory workspace in Tivoli Enterprise Portal, and verify that data is displayed.

If you must install the IBM Tivoli Monitoring operating system agent to the agent
depot, the easiest method is to copy the agent to the agent depot by issuing the
tacmd addbundles command, and then install it by issuing the tacmd createNode
command, for example:
v Extract the Tivoli Monitoring 6.3.0 operating system agent, then copy the
operating system agent to the depot by issuing the following command:
./tacmd addbundles -i /path_to_agent/unix
v Deploy the operating system agent by issuing the following command:
./tacmd createNode -h host_name -u user_name -w password

Restriction: You cannot install the UNIX operating system agent into an AIX
WPAR with IBM Tivoli Monitoring version 6.3.0 FP2. The operating system agent
is required to remotely deploy the monitoring agent, and therefore you cannot
remotely deploy to an AIX WPAR.

AIX: Populating the agent depot on AIX and Linux systems:

Before you can remotely deploy a monitoring agent, you must populate the agent
depot. The agent depot is an installation directory on the monitoring server that
you must copy the agent to, and then deploy from, to remote systems.

Before you begin

Before you begin, ensure that you meet all of the remote deployment
preinstallation requirements.

Procedure

To add the monitoring agent to the agent depot for remote deployment, complete
the following steps:
1. Copy and extract the agent installation package to a directory that is accessible
by the Tivoli Enterprise Monitoring server hub. For example, you can copy the
package to the following directory:
/tmp/tsmrptagent

Tip: Ensure that you select the appropriate executable file from the Passport
Advantage, FTP download site, or from the DVD media. The file name for
installing only the monitoring agent, or the application support files can be
identified by the word AGENT, in capital letters, for example:
7.1.0.000-TIV-TSMRPT-AGENT-AIX.bin
2. Optional: Modify the silent response file that will be used during the agent
installation to specify items such as the installation directory and the
encryption key that is required to communicate with the Tivoli Enterprise
Monitoring server hub.

Tips:
a. The default encryption key value is IBMTivoliMonitoringEncryptionKey
b. The silent response file names are:
v unix\skaix526.txt

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 127

Installing Tivoli Monitoring for Tivoli Storage Manager

3. Add the agent to the agent depot. This process copies the files to a directory on
the Tivoli Enterprise Monitoring server.
a. Change directories to the location where the tacmd command is located, for
example:
/opt/IBM/ITM/bin
b. Log in to Tivoli Enterprise Monitoring server by issuing the following
command:
./tacmd login -s host_name -u sysadmin -p password
c. Add the agent to the agent depot by issuing the following command:
./tacmd addbundles -i /path_to_agent/unix
If the command was successful, the a message similar to the following
message is displayed:
KUICAB020I: Adding bundles to the /opt/IBM/ITM/tables/TEMS/depot depot.
The time required to complete this operation depends on the number and size of
the added bundles.

KUICAB022I: The following bundles were successfully added to the

/opt/IBM/ITM/tables/TEMS/depot depot:

Product Code : sk
Deployable : True
Version : 063300000
Description : Monitoring Agent for Tivoli Storage Manager
Host Type : li6243
Host Version : li6243
Prerequisites: ci:062202000 la:010001000 gs:074027000 jr:043000000
ui:062202000 ax:062202000

Product Code : sk
Deployable : True
Version : 063300000
Description : Monitoring Agent for Tivoli Storage Manager
Host Type : li6263
Host Version : li6263
Prerequisites: ci:062202000 la:010001000 gs:074027000 jr:050900000
ui:062202000 ax:062202000

Product Code : sk
Deployable : True
Version : 063300000
Description : Monitoring Agent for Tivoli Storage Manager
Host Type : lx8266
Host Version : lx8266
Prerequisites: ci:062202000 la:010001000 gs:074027000 jr:050900000
ui:062202000 ax:062202000

4. Verify that the bundles exist in the agent depot by go to the

/opt/IBM/ITM/tables/TEMS/depot directory, or by issuing the following
command:
./tacmd viewdepot -t sk

Tip: You can limit the output to only the Tivoli Monitoring for Tivoli Storage
Manager monitoring agent by using the SK product code.
Example output:

128 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

Product Code : sk
Version : 063300000
Description : Monitoring Agent for Tivoli Storage Manager
Host Type : li6243
Host Version : li6243
Prerequisites: ci:062000000,la:010001000,ui:062000000,ax:062000000

Product Code : sk
Version : 063000000
Description : Monitoring Agent for Tivoli Storage Manager
Host Type : unix
Host Version : aix523,aix526,aix533,aix536,aix613,aix616,hp11,hp116,hpi116,lx8266,
lia266,lpp266,li6223,li6242,li6243,li6245,li6246,li6262,li6263,li6265,
li6266,ls3223,ls3226,ls3242,ls3243,ls3245,ls3246,ls3262,ls3263,ls3265,
ls3266,sol283,sol286,sol293,sol296,sol503,sol506,sol606
Prerequisites:

Tip: You can remove older bundles if they are no longer needed by issuing the
tacmd removebundles command, for example:
./tacmd removebundles -t sk -i /opt/IBM/ITM/tables/TEMS/depot

What to do next

After you populated the agent depot with the monitoring agent, you can deploy
the agent to remote sites from this central location. For detailed procedures, see the
following section:
Remotely deploying monitoring agents on AIX systems

AIX: Remotely deploying monitoring agents on AIX and Linux systems:

After you populate the agent depot, you can deploy the monitoring agent to
remote systems.

Before you begin

Before you begin, ensure that your system meets all of the remote deployment
preinstallation requirements, and that the operating system agent on the remote
system is started and has root access.

Procedure

To install the monitoring agent, and initiate the deployment, complete the
following steps:
1. Go to where the tacmd command is located. For example, the default directory
is:
/opt/IBM/ITM/bin
2. Log on to the remote system by using the sysadmin user ID and password:
./tacmd login -s host_name -u sysadmin -p password
3. Locate the nodes that you want to deploy the monitoring agent to, by issuing
the following command:
./tacmd listSystems -t UX
4. Deploy the monitoring agent by issuing the following command:
./tacmd addSystem -t sk -n Primary:yourhost:UX -p INSTANCE=yourhost
TSM_AUTHENTICATION_INFORMATION.KSK_SERVER_ADDR=yourhost.yourcompany.com
TSM_AUTHENTICATION_INFORMATION.KSK_PORT_NUMBER=1500
TSM_AUTHENTICATION_INFORMATION.KSK_USER=tsmusername
TSM_AUTHENTICATION_INFORMATION.KSK_PASSWORD=tsmpassword

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 129

Installing Tivoli Monitoring for Tivoli Storage Manager

where:
v TSM_AUTHENTICATION_INFORMATION.KSK_SERVER_ADDR indicates the server IP
address of the Tivoli Storage Manager server
v TSM_AUTHENTICATION_INFORMATION.KSK_PORT_NUMBER indicates the port that is
required to access the Tivoli Storage Manager server
v TSM_AUTHENTICATION_INFORMATION.KSK_USER indicates the user ID that is used
to access the Tivoli Storage Manager server
v TSM_AUTHENTICATION_INFORMATION.KSK_PASSWORD indicates the password for
the user ID that is used to access the Tivoli Storage Manager server
v TSM_AUTHENTICATION_INFORMATION.KSK_KEYSTORE indicates the file system
location if your agent will be communicating with the Tivoli Storage
Manager server through an SSL connection. Leave this blank to use the
default non-SSL authentication method.
If your agent will be communicating with the server through an SSL
connection, specify a value by using the
TSM_AUTHENTICATION_INFORMATION.KSK_KEYSTORE option.

Tip: When specifying a monitoring agent instance name, as a best practice, you
can specify the name of the Tivoli(r) Storage Manager server, or the host name
of the server as your instance name.
For example:
./tacmd addSystem -t sk -n Primary:yourhost:UX -p INSTANCE=yourhost
TSM_AUTHENTICATION_INFORMATION.KSK_SERVER_ADDR=yourhost.yourcompany.com
TSM_AUTHENTICATION_INFORMATION.KSK_PORT_NUMBER=1500
TSM_AUTHENTICATION_INFORMATION.KSK_USER=tsmusername
TSM_AUTHENTICATION_INFORMATION.KSK_PASSWORD=tsmpassword

KUICAR010I: The agent type SK is being deployed.

KUICAR028I: The operation has been successfully queued for deployment,

the transaction id is 1329702031328000000000041,
use the getDeployStatus CLI to view the status.

5. Review the deployment status by issuing the following command:

./tacmd getDeployStatus -t sk

For example:
Transaction ID : 1334178758871657000027663
Command : INSTALL
Status : SUCCESS
Retries : 0
TEMS Name : TEMS
Target Hostname: yourhost:UX
Platform : aix526
Product : SK
Version : 063300000
Error Message : KDY0028I: Request completed successfully. Deployment request was
processed successfully and is now completed.

What to do next

After you deployed the agent, verify that the Tivoli Storage Manager data is being
collected and displayed in Tivoli Enterprise Portal. Log in to Tivoli Enterprise
Portal, select the system that the monitoring agent was deployed to, and verify
that data is displayed correctly in the workspaces.

130 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

AIX: Configuring historical data collection from within Tivoli Enterprise Portal:

After you install the monitoring agent in to an existing IBM Tivoli Monitoring
environment, you must configure historical data collection if you intend to
generate reports based on this data. You can configure historical data collection
from within Tivoli Enterprise Portal, but consider using the command-line interface
instead because it is quicker than doing it from within the Tivoli Enterprise Portal.

About this task

If you installed Tivoli Monitoring for Tivoli Storage Manager by using the standard
installation method, historical data collection was configured for you automatically.
If you are using the native IBM Tivoli Monitoring installer, then you must
manually configure historical data collection.

You must configure history configuration to have the data from the monitored
servers stored in the WAREHOUS database. This is a requirement if you plan to
use Tivoli Common Reporting to view historical reports.

You can use the following steps to start data collection. In the steps, example
values are used. Your selections depend on your criteria.

Procedure
1. Start the Tivoli Enterprise Portal:
a. Open a web browser and specify the address of the server where the Tivoli
Enterprise Portal was installed, similar to the following example:
http://hostname:1920///cnp/kdh/lib/cnp.html
where hostname is the server name and 1920///cnp/kdh/lib/cnp.html is the
port and location of the Java™ Tivoli Enterprise Portal web client.
2. Log on to the Tivoli Enterprise Portal by using the sysadmin user ID, and the
password that was specified during installation.
3. From the Tivoli Enterprise Portal menu, click Edit > History Configuration.
4. Specify collection settings by completing the following steps for each of the
following attribute groups:
v KSK CLIENT NODE STORAGE
v KSK CLIENT MISSED FILES
v KSK CLIENT NODE STATUS
v KSK DATABASE
v KSK SCHEDULE
v KSK STORAGE POOL
v KSK TAPE USAGE
v KSK TAPE VOLUME
v KSK NODE ACTIVITY
v KSK SERVER
v KSK STORAGE DEVICE
v KSK ACTIVITY LOG
v KSK OCCUPANCY
v KSK REPLSTATUS (Listed as Replication Status)
v KSK REPLDETAILS (Listed as Replication Details)
v KSK ACTIVITY SUMMARY

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 131

Installing Tivoli Monitoring for Tivoli Storage Manager

Tip: KSK denotes the Tivoli Monitoring for Tivoli Storage Manager product
code.
a. Right-click Tivoli Storage Manager, and select Create new collection setting.
b. Select an attribute group from the menu.
c. Specify a name for the new collection setting, and optionally provide a
description. As a best practice, include the attribute group in the name.
d. In the Collection interval field, set the value to 1 hour. This value specifies
how often the data is retrieved from the monitoring agent.
e. In the Collection location field, select Tivoli Enterprise Monitoring server,
TEMA. This server is where the historical data files are stored.
f. In the Warehouse interval field, select 1 day for how often you want the
warehouse data to store data. If you select 1 day, you cannot view reports
for at least a day.

Note: These settings are examples. Your selections depend on how often, and
how much data you want to collect. To test the data that is collected, start with
a short interval such as 1 hour. After you are sure that the data is being
collected correctly, you can adjust the collection interval to every 12 or 24
hours.

To verify that historical collection is activated, you can look for the History
Configuration icon next to each attribute group.
5. After the historical data collection settings are configured, complete the
following steps to configure summarization and pruning of the data in the
Tivoli Data Warehouse.

Tip: Summarization combines multiple data points into a single data point
across a date range such as a monthly or quarterly. Pruning removes older data
that is no longer needed to save database space.
a. Left-click on Tivoli Storage Manager to open the summarization and
pruning settings window.
b. Select all of the attributes that are configured for historical data collection. A
blue icon next to the attribute group indicates that data collection is
running.
c. In the summarization settings, enable summarization for Yearly, Quarterly,
Monthly, Weekly, Daily, and Hourly.
d. In the Pruning section, you can also optionally enable pruning. By default
no pruning is enabled. If your Tivoli Data Warehouse database size is
growing too large, pruning older data can be enabled here for each attribute
group.

Note: Pruning too vigorously can result in no data, or not enough data being
displayed in the Tivoli Common Reporting reports.

132 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

AIX: Configuring historical data collection by using the command-line interface

on AIX and Linux systems:

After you install the monitoring agents in an existing IBM Tivoli Monitoring
environment, you must configure historical data collection if you intend to
generate reports based on this data.

About this task

If you installed Tivoli Monitoring for Tivoli Storage Manager by using the standard
installation method, historical data collection was configured for you automatically.
If you are using the native IBM Tivoli Monitoring installer, then you must
manually configure historical data collection.

You can also configure historical data collection from within the Tivoli Enterprise
Portal. However, it is much quicker using the command-line interface because
there are many attribute groups that must be configured.

You must configure history configuration to have the data from the monitored
servers stored in the WAREHOUS database. This is a requirement if you plan to
use Tivoli Common Reporting to view historical reports.

The following commands can be copied and pasted in to a terminal session

window. Be sure to adjust any of the variables such as your password, to match
your installation environment before pasting them in to a terminal session.

Procedure

To configure historical data collection and summarization and pruning, complete

the following steps:
1. Issue the following commands and specify the sysadmin ID and password, and
the CandleManage directory:
| export admin=sysadmin
| export pswd=your_password
| export CANDLE_HOME=/opt/tivoli/tsm/reporting/itm
2. Paste the following text in the same terminal window:

Tip: Remember to change the sysadmin ID and password variables to match

the values that you specified during installation.
| export warehouseinterval=1h
| export collectioninterval=1h
| export summarization=HDWMQY
| export type="Tivoli Storage Manager"
| cd $CANDLE_HOME/bin
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK CLIENT NODE STORAGE"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK CLIENT MISSED FILES"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK CLIENT NODE STORAGE"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK DATABASE"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK SCHEDULE"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK STORAGE POOL"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK TAPE USAGE"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 133

 Installing Tivoli Monitoring for Tivoli Storage Manager

| -c $collectioninterval -d $summarization -o "KSK TAPE VOLUME"

| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK NODE ACTIVITY"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK SERVER"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK STORAGE DEVICE"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK ACTIVITY LOG"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK OCCUPANCY"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK REPLSTATUS"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK REPLDETAILS"
| ./tacmd histconfiguregroups -u $admin -w $pswd -t "$type" -i $warehouseinterval
| -c $collectioninterval -d $summarization -o "KSK ACTIVITY SUMMARY"
3. Start collecting data by issuing the following commands:
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| CLIENT NODE STORAGE"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| CLIENT MISSED FILES"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| CLIENT NODE STORAGE"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| DATABASE"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| SCHEDULE"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| STORAGE POOL"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| TAPE USAGE"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| TAPE VOLUME"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| NODE ACTIVITY"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| SERVER"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| STORAGE DEVICE"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| ACTIVITY LOG"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| OCCUPANCY"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| REPLSTATUS"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| REPLDETAILS"
| ./tacmd histstartcollection -u $admin -w $pswd -t "$type" -o "KSK
| ACTIVITY SUMMARY"

Creating and configuring the agent instance

After you install Tivoli Monitoring for Tivoli Storage Manager, you must create
and configure the monitoring agent instance to begin collecting data.

About this task

If you plan to monitor less than 5 Tivoli Storage Manager servers, you can use the
monitoring agent template that was installed as part of the Tivoli Monitoring for
Tivoli Storage Manager installation to create and configure the agent instances.

134 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| If you plan to monitor more than 5 Tivoli Storage Manager servers, you must
| install additional monitoring agents on each Tivoli Storage Manager server that
| you want to monitor. Alternatively, you can install the agent on any supported
| operating system and configure the agent instances to connect to the Tivoli Storage
| Manager servers that you want to monitor. For example, you cannot install the
| Tivoli Monitoring for Tivoli Storage Manager monitoring agent directly on HP-UX,
| Solaris, or zLinux operating systems. To collect data for Tivoli Storage Manager
| servers on these operating systems, you must create a monitoring agent instance
| on the IBM Tivoli Monitoring server or on another supported operating system.

This configuration provides the most efficient use of memory on both the Tivoli
Storage Manager server, and the IBM Tivoli Monitoring server.

Install and configure an agent instance by using one of the following methods:
v “Creating and configuring the monitoring agent instance by using
CandleManage”
v “Creating and configuring the monitoring agent instance by using the
command-line interface” on page 138

Creating and configuring the monitoring agent instance by

using CandleManage
After you install the Tivoli Monitoring for Tivoli Storage Manager monitoring
agent, you can use the CandleManage graphical interface to create and configure
an agent instance.

About this task

Complete these steps to create and configure the agent instance by using the
CandleManage graphical interface, or you can use the command-line interface:
“Creating and configuring the monitoring agent instance by using the
command-line interface” on page 138.

You must create and configure an agent instance for each server that you want to
monitor. You can monitor up to 5 Tivoli Storage Manager servers from the same
IBM Tivoli Monitoring server. If you plan to monitor more than 5 servers, you
should install additional monitoring agents on each of your Tivoli Storage Manager
servers. Alternatively, you can install the agent on any supported operating system
and configure the agent instances to connect to the Tivoli Storage Manager servers
that you want to monitor.

Note: The term, agent, is synonymous with the Tivoli Monitoring for Tivoli Storage
Manager monitoring agent. This term is used throughout the CandleManage
program.

Procedure

To configure an agent instance, complete the following steps:

1. Run the CandleManage program by using the following command:
a. Go to the directory where the CandleManage program is located by issuing
the following command:
cd /opt/tivoli/tsm/reporting/itm/bin
b. Run the CandleManage program by issuing this command:
./CandleManage &

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 135

Installing Tivoli Monitoring for Tivoli Storage Manager

2. In the CandleManage window, right-click Monitoring Agent for Tivoli Storage

Manager, and select configure, to create an instance of the Tivoli Monitoring
for Tivoli Storage Manager agent.
3. In the Manage Application Instances window, click Add instance.
4. In the Input window, specify an agent instance name, for example, SERVER1,
and click OK.

Tip: When you specify an instance name, the best practice is to specify the host
name of the Tivoli Storage Manager server, or the server name from the QUERY
STATUS command as your instance name. Instance names must be unique, and
cannot exceed 20 characters.
5. In the Agent Configuration window, complete the following fields for the Tivoli
Storage Manager server to be monitored:
a. In the Server Address field, specify the fully qualified IP server address for
the Tivoli Storage Manager server.
b. In the Port Number field, specify the port number that is used to
communicate with the Tivoli Storage Manager server.

Tip: For normal TCP/IP traffic, you can determine the port number by
issuing one of the following commands:
QUERY OPT TCPPORT
QUERY OPT TCPADMINPORT

For SSL encrypted TCP/IP traffic, you can determine the port number by
issuing one of the following commands:
QUERY OPT SSLTCPPORT
QUERY OPT SSLTCPADMINPORT
c. In the TSM Administrator field, specify the Tivoli Storage Manager
administrator ID used to access the server.

Note: The Tivoli Monitoring for Tivoli Storage Manager agent runs only
queries on the Tivoli Storage Manager server and does not change anything.
The administrator that you choose to run the queries can be an
administrator ID without the following privileges:
v System Privileges
v Policy Privileges
v Storage Privileges
v Operator Privileges
v Client Access Privileges
v Client Owner Privileges
d. In the TSM Administrator Password field, enter the password twice for the
Tivoli Storage Manager administrator ID.
e. In the File System Location and Name of SSL Certificate field, either
browse to the location where the SSL certificates are located, or leave the
field blank if you do not intend to use SSL.

Tip: If you intend to use SSL to encrypt network traffic, ensure that your
Tivoli Storage Manager server is enabled for this type of secure
communication and that you specified the correct port number. For
additional information, see Configuring Tivoli Storage Manager
client/server communication with Secure Sockets Layer

136 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

(http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
com.ibm.itsm.client.doc/t_cfg_ssl.html).
f. Click OK to save the settings.
6. Specify the Tivoli Enterprise Monitoring server information, but before you
click Save, ensure that all the settings in the Tivoli Enterprise Monitoring server
connection tab are correct:
v Ensure that there is no check mark in the No TEMS connection box.
v Specify the name of the host where Tivoli Enterprise Monitoring server is
installed. If the TEMS Hostname field is prefilled, verify that the host name
is correct.
v Ensure that the Protocol field indicates one of the following values:
– IP.PIPE, if you are not using the SSL protocol
– IP.SPIPE, if you are using the SSL protocol
v The Port Number should indicate 1918.
The Manage Tivoli Enterprise Monitoring Services window displays the new
Tivoli Monitoring for Tivoli Storage Manager agent instance.
7. If the agent was installed separately on an existing IBM Tivoli Monitoring
server, you might need to seed the Tivoli Enterprise Monitoring server and
Tivoli Enterprise Portal server, to allow it to pick up the new agent
configuration. From a command line, issue the following commands:
./itmcmd config -A cq
./itmcmd support -t tems_name sk

Tip: The itmcmd program is in the bin directory under the ITM installation
directory. The default is: /opt/IBM/ITM/bin.
8. Stop and restart the Tivoli Enterprise Monitoring server and the Tivoli
Enterprise Portal server. From the CandleManage program, select the Tivoli
Enterprise Portal server, right-click, and select Stop. Wait for the process to
stop and click Start. Repeat this step for the Tivoli Enterprise Monitoring
server.
9. Start the Tivoli Monitoring for Tivoli Storage Manager agent instance. Select
Monitoring Agent for Tivoli Storage Manager, right-click Start Service. Select
the agent instance that you want to start and click Start Agent.
If an error occurs, examine the $CANDLE_HOME/logs directory for the most recent
hostname_sk_instancename_timestamp.log file. This file contains error messages
from when the agent starts.

Results

After you start the agent, it starts to collected data. You can view real-time data by
using the workspaces in the Tivoli Enterprise Portal, or you can view historical
data by using Cognos reports.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 137

Installing Tivoli Monitoring for Tivoli Storage Manager

Creating and configuring the monitoring agent instance by

using the command-line interface
After you install the Tivoli Monitoring for Tivoli Storage Manager agent, you can
manually create and configure the agent instance by using the command-line
interface method.

About this task

Create and configure the agent instance by using this command-line interface
method, or you can use the CandleManage graphical interface method: “Creating
and configuring the monitoring agent instance by using CandleManage” on page
135.

You can monitor multiple Tivoli Storage Manager servers from the same IBM
Tivoli Monitoring server, but you must create and configure an agent instance for
each server that you want to monitor.

Note: The term, agent, that is displayed in the following examples is synonymous
with the Tivoli Monitoring for Tivoli Storage Manager agent.

Procedure
To configure a Tivoli Monitoring for Tivoli Storage Manager agent instance using
the command-line interface, complete the following steps:
1. Run the following command from the directory where you installed the Tivoli
Monitoring for Tivoli Storage Manager agent. The default directory is:
/opt/tivoli/tsm/reporting/itm/bin.
./itmcmd config -A sk

The command returns the following instruction:

Enter the instance name

2. Specify a name for the Tivoli Monitoring for Tivoli Storage Manager agent
instance, for example, SERVER1.

Tip: When you specify an instance name, the best practice is to include the
host name of the Tivoli Storage Manager server. You can find the server name
by issuing the QUERY STATUS command. Instance names must be unique, and
cannot exceed 20 characters.
The command returns the following question:
Edit "Monitoring Agent for Tivoli Storage Manager" settings?
[ 1=Yes, 2=No ] (default is: 1): myserver.mycompany.com
3. Enter 1. The command returns the following question: Edit 'TSM Server
Connection Information' settings? [ 1=Yes, 2=No ] (default is: 1):
4. Enter 1. The command returns the following prompts for your response:
Server Address (default is: ):
Port Number (default is: 1500):
TSM Administrator (default is: ):
TSM Administrator Password (default is: ):

a. In the Server Address field, specify the address of the Tivoli Storage
Manager server to be monitored.

138 IBM Tivoli Storage Manager for AIX: Installation Guide

Installing Jazz for Service Management components
 Installing Tivoli Monitoring for Tivoli Storage Manager

| v The user name and password for the services management administrator. The
| default is smadmin.
| v The installation location of Tivoli Monitoring for Tivoli Storage Manager.
| v The installation location of Jazz for Service Management.

| About this task

| The data source script imports the Cognos reports and connects Tivoli Common
| Reporting to the WAREHOUS database. The data source script and the
| TSM_Cognos.zip files are in the tools directory of the installation directory.

| Procedure
| 1. Open a command line and change to the following directory:
| install_dir/tools
| where install_dir is the Tivoli Monitoring for Tivoli Storage Manager installation
| location.
| 2. From a command line, issue the following command:
| datasource.sh -j jazzsm_location -u jazzsm_user -p jazzsm_password -i
| itmuser_password
| where:
| jazzsm_location is the installation location for Jazz for Service Management
| jazzsm_user is the service management administrator ID that was created
| during the installation of Jazz for Service Management
| jazzsm_password is the password for jazzsm_user
| itmuser_password is the password for itmuser

| Tip: If you want to import Cognos reports from a previous setup, use the -r
| option and specify the location of the compressed reports file.

| What to do next

| You can run Cognos reports to see historical data from the Tivoli Storage Manager
| servers that you are monitoring. Go to “Running a Cognos report” on page 149.

| For a list of Cognos reports that are available, see Cognos status and trend reports
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.srv.doc/r_rpt_cognos_rpts.html).

| Starting the Jazz for Service Management service

| By default, the Jazz for Service Management service does not restart after the
| system restarts. You must start Jazz for Service Management manually or you can
| configure it restart automatically.

| About this task

| If you want to access the Dashboard Application Services Hub or view Cognos
| reports, Jazz for Service Management must be running.

| Procedure

| To start Jazz for Service Management, complete one of the following actions:

144 IBM Tivoli Storage Manager for AIX: Installation Guide

Installing Jazz for Service Management components
Installing Tivoli Monitoring for Tivoli Storage Manager

v Open a web browser and specify the address of the server where the
Tivoli Enterprise Portal was installed, similar to the following example:
http://hostname:1920///cnp/kdh/lib/cnp.html
where hostname is the server name and 1920///cnp/kdh/lib/cnp.html is
the port and location of the Java Tivoli Enterprise Portal web Client.

Tip: Always use this port number and location.

b. Click the Warehouse Proxy node to highlight it in the Navigator pane.

Note: The Warehouse Proxy node can be found in the following location:

Enterprise > UNIX System > hostname > Warehouse Proxy

c. In the Database Information table, verify that the DB Connectivity has a
value of YES and that the DB Version has a value of 10.05.
d. Click the Summarization and Pruning Agent node to highlight it in the
Navigator pane.
e. In the Connectivity table, verify that the TEPS Connectivity value and the
DB Connectivity values are YES.
4. Verify that the history configuration is configured:
a. Log on to the Tivoli Enterprise Portal by following the steps in Step 3.a.
b. Click Edit > History Configuration.
c. Verify that there are several KSK_* attribute groups under the Tivoli
Storage Manager node in the navigation pane.
d. Click to highlight Tivoli Storage Manager in the content pane. Under the

Group column, verify that there are several groups with the icon that
precedes the name. The icon indicates that the attribute is running to
summarize and store data.
5. If you completed a new installation, verify that pruning is configured:
a. Log on to the Tivoli Enterprise Portal by following the steps in Step 3.a.
b. Click Edit > History Configuration.
c. Click the Tivoli Storage Manager node to highlight it.

d. Click any of the attribute groups with the icon, and view the Pruning
section in the window. If configured, all the check boxes are selected and
there are numerical values in the fields. For more information, see
“Configuring summarization and pruning settings” on page 149.
6. Optional: If you configured the monitoring agent, installed Jazz for Service
Management, and ran the data source script, you can verify the configuration
and begin working with the reports.
a. Log on to the Tivoli Enterprise Portal by following the steps in Step 3.a
with the sysadmin user ID and password and review the workspaces to
verify that data is being collected.

Note: The workspaces can be found in the Navigator pane under the
following node:

Enterprise > UNIX System > hostname > Tivoli Storage Manager
If you created multiple instances of the agent, click each agent instance that
is listed under the Tivoli Storage Manager branch in the Navigator pane.

146 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| v The user name and password for the services management administrator. The
| default is smadmin.
| v The installation location of Tivoli Monitoring for Tivoli Storage Manager.
| v The installation location of Jazz for Service Management.

| About this task

| The data source script imports the Cognos reports and connects Tivoli Common
| Reporting to the WAREHOUS database. The data source script and the
| TSM_Cognos.zip files are in the tools directory of the installation directory.

| Procedure
| 1. Open a command line and change to the following directory:
| install_dir/tools
| where install_dir is the Tivoli Monitoring for Tivoli Storage Manager installation
| location.
| 2. From a command line, issue the following command:
| datasource.sh -j jazzsm_location -u jazzsm_user -p jazzsm_password -i
| itmuser_password
| where:
| jazzsm_location is the installation location for Jazz for Service Management
| jazzsm_user is the service management administrator ID that was created
| during the installation of Jazz for Service Management
| jazzsm_password is the password for jazzsm_user
| itmuser_password is the password for itmuser

| Tip: If you want to import Cognos reports from a previous setup, use the -r
| option and specify the location of the compressed reports file.

| What to do next

| You can run Cognos reports to see historical data from the Tivoli Storage Manager
| servers that you are monitoring. Go to “Running a Cognos report” on page 149.

| For a list of Cognos reports that are available, see Cognos status and trend reports
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.srv.doc/r_rpt_cognos_rpts.html).

| Starting the Jazz for Service Management service

| By default, the Jazz for Service Management service does not restart after the
| system restarts. You must start Jazz for Service Management manually or you can
| configure it restart automatically.

| About this task

| If you want to access the Dashboard Application Services Hub or view Cognos
| reports, Jazz for Service Management must be running.

| Procedure

| To start Jazz for Service Management, complete one of the following actions:

144 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| v To start Jazz for Service Management manually, issue the following commands
| from the command line:
| cd jazzsm_install_dir/profile/bin
| ./startServer.sh server1
| where jazzsm_install_dir is the Jazz for Service Management installation directory.
| By default, the installation directory is in the following location:
| /opt/IBM/JazzSM
| v To ensure that Jazz for Service Management starts automatically when the
| system restarts, issue the following commands from the command line:
| cd installation_dir/tools
| ./autostartOSNAME.sh -j jazzsm_install_dir

| where:
| – installation_dir is the Tivoli Monitoring for Tivoli Storage Manager installation
| directory. By default, the installation directory is in the following location:
| /opt/tivoli/tsm/reporting
| – OSNAME is the name of the operating system on which Jazz for Service
| Management is installed, for example, Redhat in autostartRedhat.sh.
| – jazzsm_install_dir is the Jazz for Service Management installation directory. By
| default, the installation directory is in the following location:
| /opt/IBM/JazzSM
|
Verifying the installation
After you install Tivoli Monitoring for Tivoli Storage Manager and Jazz for Service
Management, verify that all of the components are installed and configured
correctly.

Procedure

To verify that the installation was successful, complete these steps:

1. Verify that the Tivoli Enterprise Portal server version is 06.30.02.00:
a. Open the Manage Tivoli Enterprise Management Services application:
v Run the CandleManage program by using the following commands:
cd install_dir/itm/bin
./CandleManage &

where install_dir is the installation directory. The default installation

directory is /opt/tivoli/tsm/reporting.
b. Verify that the version of Tivoli Enterprise Portal server is 06.30.02.00 in the
Version column.
2. In Manage Tivoli Enterprise Management Services, verify that the Monitoring
Agent for Tivoli Storage Manager template version is correct. For example, for
version 7.1.0, the version is 07.10.00.00.
3. Verify database connectivity:
a. Log on to the Tivoli Enterprise Portal with your sysadmin user ID and
password by using one of the following methods:
v Use the Web Client
1) Open a web browser and go to: http://hostname:1920, where
hostname is the name of your operating system.
2) Select IBM Tivoli Enterprise Portal Web Client.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 145

Installing Tivoli Monitoring for Tivoli Storage Manager

v Open a web browser and specify the address of the server where the
Tivoli Enterprise Portal was installed, similar to the following example:
http://hostname:1920///cnp/kdh/lib/cnp.html
where hostname is the server name and 1920///cnp/kdh/lib/cnp.html is
the port and location of the Java Tivoli Enterprise Portal web Client.

Tip: Always use this port number and location.

b. Click the Warehouse Proxy node to highlight it in the Navigator pane.

Note: The Warehouse Proxy node can be found in the following location:

Enterprise > UNIX System > hostname > Warehouse Proxy

c. In the Database Information table, verify that the DB Connectivity has a
value of YES and that the DB Version has a value of 10.05.
d. Click the Summarization and Pruning Agent node to highlight it in the
Navigator pane.
e. In the Connectivity table, verify that the TEPS Connectivity value and the
DB Connectivity values are YES.
4. Verify that the history configuration is configured:
a. Log on to the Tivoli Enterprise Portal by following the steps in Step 3.a.
b. Click Edit > History Configuration.
c. Verify that there are several KSK_* attribute groups under the Tivoli
Storage Manager node in the navigation pane.
d. Click to highlight Tivoli Storage Manager in the content pane. Under the

Group column, verify that there are several groups with the icon that
precedes the name. The icon indicates that the attribute is running to
summarize and store data.
5. If you completed a new installation, verify that pruning is configured:
a. Log on to the Tivoli Enterprise Portal by following the steps in Step 3.a.
b. Click Edit > History Configuration.
c. Click the Tivoli Storage Manager node to highlight it.

d. Click any of the attribute groups with the icon, and view the Pruning
section in the window. If configured, all the check boxes are selected and
there are numerical values in the fields. For more information, see
“Configuring summarization and pruning settings” on page 149.
6. Optional: If you configured the monitoring agent, installed Jazz for Service
Management, and ran the data source script, you can verify the configuration
and begin working with the reports.
a. Log on to the Tivoli Enterprise Portal by following the steps in Step 3.a
with the sysadmin user ID and password and review the workspaces to
verify that data is being collected.

Note: The workspaces can be found in the Navigator pane under the
following node:

Enterprise > UNIX System > hostname > Tivoli Storage Manager
If you created multiple instances of the agent, click each agent instance that
is listed under the Tivoli Storage Manager branch in the Navigator pane.

146 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

Each agent instance has its own list of workspaces. Review a few
workspaces to verify that data is coming in from the Tivoli Storage Manager
server.
You can also navigate to the Agent Log workspace and look for messages
such as TSM login succeeded. If you see a message that indicates that the
login failed, you probably specified an incorrect ID or password when you
configured the agent instance. If data is not being collected, see Resolving
Tivoli Monitoring for Tivoli Storage Manager problems
(http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
com.ibm.itsm.tshoot.doc/c_pdg_reportprobs.html).
| b. Log on to the IBM Dashboard Application Services Hub with the Jazz for
| Service Management administrator ID and password:
| 1) Open a web browser and enter the following address:
| https://hostname:port/ibm/console

| where port is the port number that is specified when you installed Jazz
| for Service Management. The default port is 16311. The hostname is the
| host name of the system where Jazz for Service Management is installed.
c. Click the Reporting icon in the side navigation menu and click Common
Reporting. You can view Cognos reports by selecting IBM Tivoli Storage
Manager Cognos Reports.

Tip: You might need to wait 1 or 2 hours after configuration before you can
see historical data in the Cognos reports.

What to do next

If you experience issues with your installation such as data not displaying in your
reports, or other issues, see Resolving Tivoli Monitoring for Tivoli Storage Manager
problems (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
com.ibm.itsm.tshoot.doc/c_pdg_reportprobs.html).

For more information about reports, see Reporting and monitoring with Tivoli
Monitoring for Tivoli Storage Manager (http://www.ibm.com/support/
knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/c_rpt_adm_ovr.html).

Taking the first steps after installation

After you install Tivoli Monitoring for Tivoli Storage Manager, you must complete
additional tasks to finish your setup. Then you can start real-time monitoring of
your Tivoli Storage Manager servers and start collecting historical data so you can
run Tivoli Common Reporting reports.

Procedure

Complete the following steps after the installation:

| 1. Configure the WAREHOUS data source to connect Tivoli Common Reporting to
| the WAREHOUS database. Complete the steps in “Configuring the
| WAREHOUS data source and importing reports” on page 143.
2. Create an agent instance for each Tivoli Storage Manager server that you want
to monitor.
| You must create and configure a monitoring agent instance for each Tivoli
| Storage Manager server that you want to monitor. You can create up to 5 agent
| instances on the monitoring server. If you intend to monitor more than 5 Tivoli

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 147

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Storage Manager servers, you must use the installer to install only the
| monitoring agent directly on the Tivoli Storage Manager servers you want to
| monitor. Alternatively, you can install the agent on a supported operating
| system and configure the agent instance to connect to the Tivoli Storage
| Manager server.
v See “Creating and configuring the monitoring agent instance by using
CandleManage” on page 135.
v See “Creating and configuring the monitoring agent instance by using the
command-line interface” on page 138.
3. View the real-time workspaces from the Tivoli Enterprise Portal. There is a set
of workspaces available for each monitoring agent that is created. After you
configure the monitoring agents, you can immediately see data in several of the
workspaces.
a.
Log on to the Tivoli Enterprise Portal with your sysadmin user ID and
password by using one of the following methods:
v Use the Web Client
1) Open a web browser and go to: http://hostname:1920, where
hostname is the name of your operating system.
2) Select IBM Tivoli Enterprise Portal Web Client.
v Or, open a web browser and specify the address of the server where the
Tivoli Enterprise Portal is installed, similar to the following example:
http://hostname:1920///cnp/kdh/lib/cnp.html
where hostname is the server name and 1920///cnp/kdh/lib/cnp.html is the
port and location of the Java Tivoli Enterprise Portal web Client.

Tip: Always use this port number and location.

b. Review the workspaces to monitor the Tivoli Storage Manager servers in
real time. The workspaces can be found in the Navigator pane under the
following node:
Enterprise > UNIX System > hostname > Warehouse Proxy

Note: If the workspaces do not display data, review the Agent Log workspace
for any errors.
| 4. View the historical reports by completing the steps in “Running a Cognos
| report” on page 149.
5. Review the WAREHOUS pruning settings and update them if necessary. The
WAREHOUS data is pruned at set intervals and affects the data that is
displayed in your historical reports.
a. Log on to the Tivoli Enterprise Portal by completing Step 3a.
b. Click Edit > History Configuration.
c. Click the Tivoli Storage Manager node to highlight it.
d. In the Pruning section, update any of the settings, and click OK to save the
changes.

148 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Running a Cognos report

| You can view historical reports by running the Cognos reports from the Dashboard
| Application Services Hub.

| Before you begin

| Before you can run a report, the following tasks must be completed:
| v Tivoli Monitoring for Tivoli Storage Manager is installed.
| v Jazz for Service Management, which includes Tivoli Common Reporting and
| WebSphere Application Server, is installed.
| v The WAREHOUS data source is configured.

| Procedure
| 1. Open a web browser and go to https://hostname:16311/ibm/console/
| logon.jsp, where hostname is the name of your operating system.
| 2. Log on to the Dashboard Application Services Hub with the service
| management administrator ID and password. The default user name is smadmin.
| 3. Click the Reporting icon in the navigation menu and click Common Reporting
| to access the list of Cognos reports.
| 4. Click a report to run it.
|
Configuring agents and services
After you install Tivoli Monitoring for Tivoli Storage Manager, you can manually
configure the IBM Tivoli Monitoring agents.

Configuring summarization and pruning settings

After you install Tivoli Monitoring for Tivoli Storage Manager, you can configure
summarization and pruning settings for the WAREHOUS database.

Before you begin

The summarization and pruning settings control how often data is collected and
pruned from the WAREHOUS database. The values are set independently for each
attribute group. The attribute groups correspond to workspaces in the Tivoli
Enterprise Portal. The summarized data is stored in the WAREHOUS database and
is used to populate the Cognos reports. When the summarized data is periodically
pruned, the data is removed from the WAREHOUS database.

About this task

Summarization and pruning values are automatically configured during

installation. Pruning can help reduce the amount of data that is stored in the
database, in some cases by as much as 50%. Pruning can also help with
performance issues if the database becomes too large. You can adjust the values so
that they are appropriate for your organization.

Note: DB2 allocates space for the database size to increase. Pruning reduces the
amount of data that is stored in the database. To reduce the size of the database,
go to the DB2 Knowledge Center: http://www.ibm.com/support/
knowledgecenter/SSEPGG_10.5.0 and search for reducing databases.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 149

 Installing Tivoli Monitoring for Tivoli Storage Manager

Procedure

To configure summarization and pruning settings, complete the following steps:

1. Log on to the Tivoli Enterprise Portal by using the sysadmin ID and password.
| 2. From the main menu, click Edit > History Configuration and click Tivoli
| Storage Manager to highlight it.
3. In the Select Attribute Groups pane, highlight the rows that contain the groups
that you want to modify. The summarization and pruning fields become active.
4. Select the summarization and pruning values that you want to modify, specify
how long you want to keep the data, and click OK.
The following table shows one example of a modified pruning setup. Your
settings can vary depending on the data that you collect, how often you collect
it, how long you keep it, and how often you prune it.
Table 26. Default pruning setup
Summarization
value Pruning value Numeric value Time units
Yearly Yearly 7 Years
Quarterly Quarterly 2 Years
Monthly Monthly 2 Years
Weekly Weekly 6 Months
Daily Daily 2 Months
| Hourly Hourly 14 Days
Detailed data 3 Months

As a best practice, start with the default settings, and test your system to
ensure that data is being collected. When you are satisfied that the data is
being collected correctly, you can adjust the collection interval and pruning
values to suit the needs of your organization. Be sure to allow sufficient time to
elapse before you expect data to display in reports. Data is displayed in the
reports that are based on the summarization intervals that you choose.
You cannot run a report on data that was removed through pruning.

Manually configuring the Tivoli Enterprise Portal server

When Tivoli Monitoring for Tivoli Storage Manager is installed, a script is run to
configure the Tivoli Enterprise Portal server. You can verify that the server is
configured correctly, or you can manually reconfigure this server if necessary.

Procedure
1. Start the Manage Tivoli Enterprise Monitoring Services application:
v Run the CandleManage program by using the following commands:
– cd install_dir/itm/bin
– ./CandleManage &
where install_dir is the installation directory for Tivoli Monitoring for Tivoli
Storage Manager. The default installation directory is /opt/tivoli/tsm/
reporting.
2. From the Manage Tivoli Enterprise Monitoring Services window, select Tivoli
Enterprise Portal Server, right-click, and select Reconfigure.
3. Verify that the host name and port numbers specify where the Tivoli
Enterprise Monitoring server is located, and click OK. Click OK again.

150 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

4. Click Yes to reconfigure the warehouse connection information for the Tivoli
Enterprise Portal Server.
5. Click OK in the Warehouse Proxy Database Selection window to accept DB2
as the default database type.

Restriction: There are other choices that are listed, but DB2 is the database
that is required for Tivoli Monitoring for Tivoli Storage Manager.
6. Verify that the following fields are correct:
v Data Source Name: ITM Warehouse
v Database User ID: itmuser
v Database Name: Warehous
v DB Admin User ID: db2inst1
7. Remove, and retype the password in the Database Password field and the DB
Admin Password field.
8. Click OK.

Note: The message Successfully configured warehouse data source

displays. If you do not receive this message, there is at least one empty field
or an error in configuring the service.

Tip: There is no check for valid passwords, therefore it is important to retype

the passwords correctly.
9. Click OK to complete the configuration process.
10. Click OK in the Common Event Console Configuration window.
11. From the Manage Tivoli Enterprise Monitoring Services window, right-click
Tivoli Enterprise Portal Server, and click Start.

Manually configuring the Warehouse Proxy agent

When Tivoli Monitoring for Tivoli Storage Manager is installed, a script is run to
configure the Warehouse Proxy agent. Sometimes you might need to verify that the
agent is configured correctly, or manually reconfigure the agent if necessary.

Procedure
| 1. Start the Manage Tivoli Enterprise Monitoring Services application:
| v Run the CandleManage program by using the following commands:
| – cd install_dir/itm/bin
| – ./CandleManage &
| where install_dir is the installation directory for Tivoli Monitoring for Tivoli
| Storage Manager. The default installation directory is /opt/tivoli/tsm/
| reporting.
| 2. From the Manage Tivoli Enterprise Monitoring Services window, right-click
| Warehouse Proxy, and click Reconfigure.
| 3. Click OK to the message that says When configuring the Warehouse Proxy,
| remember that it must connect to a HUB TEMS (not a remote TEMS).
| 4. Ensure that the Primary TEMS connection field indicates IP.PIPE, or IP.SPIPE
| if you are using the SSL protocol.
| 5. Verify that the host name and port numbers specify where the Tivoli
| Enterprise Monitoring server is located, and click OK.
| 6. Verify that DB2 is selected as the database and click Next to continue.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 151

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Restriction: There are other choices that are listed, but DB2 is the database
| that is required for Tivoli Monitoring for Tivoli Storage Manager.
| 7. Verify that the following fields are correct:
| v ODBC DSN: ITM Warehouse
| v Username: itmuser
| 8. Verify that the following options are selected:
| v Use Batch
| v Warehouse Compression for Distributed Sources
| 9. Remove, and retype the password in the Password field and the Confirm
| Password field.
| 10. Click Test connection to verify that connection to the database is successful.
| 11. Click OK to complete the configuration process.
| 12. From the Manage Tivoli Enterprise Monitoring Services window, right-click
| Warehouse Proxy, and click Start.

Manually configuring the Warehouse Summarization and

Pruning agent
When Tivoli Monitoring for Tivoli Storage Manager is installed, a script is run to
configure the Warehouse Summarization and Pruning agent. Sometimes you might
need to verify that the agent is configured correctly, or manually reconfigure this
agent if necessary.

Procedure
1. Start the Manage Tivoli Enterprise Monitoring Services application:
v Run the CandleManage program by using the following commands:
– cd install_dir/itm/bin
– ./CandleManage &
where install_dir is the installation directory for Tivoli Monitoring for Tivoli
Storage Manager. The default installation directory is /opt/tivoli/tsm/
reporting.
2. From the Manage Tivoli Enterprise Monitoring Services window, right-click
Warehouse Summarization and Pruning Agent, and click Reconfigure.

Tip: If Reconfigure is not available, double-click Warehouse Summarization

and Pruning Agent in the Manage Tivoli Monitoring Services application, to
start the initial configuration wizard.
3. Ensure that the Primary TEMS connection field indicates IP.PIPE, or IP.SPIPE
if you are using the SSL protocol.
4. Verify that the host name and port numbers specify where the Tivoli Enterprise
Monitoring server is located, and click OK.
5. Verify that DB2 is selected as the database and click Next to continue.
6. Verify that the following information is specified:
v In the JDBC JARS section, verify that the following jar files are specified:
/opt/tivoli/tsm/reporting/db2/java/db2jcc.jar
/opt/tivoli/tsm/reporting/db2/java/db2jcc_license_cu.jar
v JDBC URL: jdbc:db2://myserver:50000/WAREHOUS
– where myserver can be the IP address or host name of the system. You can
also use localhost.
– The default DB2 port number is 50000.

152 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

– Ensure that the default Tivoli Warehouse database name WAREHOUS is

appended to the end of the URL.
v JDBC Driver: com.ibm.db2.jcc.DB2Driver
v The Warehouse User is the IBM Tivoli Monitoring user ID. The default user
ID is:
itmuser
v The default value for TEP Server Host is localhost.
v The default value for TEP Server Port is 1920.
7. Click Test connection to verify that the connection to the database is successful.
8. Click OK to complete the configuration process.
9. From the Manage Tivoli Enterprise Monitoring Services window, right-click
Warehouse Summarization and Pruning Agent, and click Start.

| Managing secure communications

| You can add more protection for your data and passwords by using the Secure
| Sockets Layer (SSL) protocol and ensuring that the system complies with the NIST
| SPS800-131A security standard.

| Disabling earlier Transport Layer Security versions

| You can use the Transport Layer Security (TLS) 1.2 protocol for communications
| between a monitoring agent and a Tivoli Storage Manager server. TLS 1.2 is
| designed to provide a higher level of security than TLS 1.1.

| About this task

| TLS is a cryptographic protocol that provides communication security. The highest

| version of the protocol is selected. To increase security, you can disable TLS
| versions earlier than 1.2. The monitoring agent uses TLS 1.2. You can use the TLS
| 1.2 protocol by editing the environment file of the monitoring agent to make earlier
| versions of the TLS protocol unavailable.

| Procedure

| To disable TLS 1.1 and earlier, complete the following steps:

| 1. Open the environment file of the monitoring agent instance.
| The environment files are named sk.ini and sk_xxx.config, where xxx is
| the instance name of the monitoring agent that you created. The file is in
| the IBM Tivoli Monitoring installation directory, for example,
| /opt/tivoli/tsm/reporting/itm/config.
| 2. Add the following line to the environment file:
| KSK_SSL_DISABLE_LEGACY_TLS=1
| 3. Restart the monitoring agent:
| a. Run the CandleManage program by using the following commands:
| cd install_dir/itm/bin
| ./CandleManage &

| where install_dir is the installation directory. The default installation

| directory is /opt/tivoli/tsm/reporting.
| b. Right-click the monitoring agent and click Stop, then click Start.
|

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 153

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Configuring Secure Sockets Layer communication

| You can use the Secure Sockets Layer (SSL) protocol to encrypt communications
| between a monitoring agent and a Tivoli Storage Manager server.

| About this task

| To secure communications by using the SSL protocol, you must obtain an SSL
| certificate from the Tivoli Storage Manager server. You must place the certificate in
| a local truststore file that is accessible by the monitoring agent.

| Setting up communications with SSL, involves the following tasks:

| v You must obtain the SSL certificate.
| v You must create the local truststore file.
| v For each monitoring agent instance, you must add the Tivoli Storage Manager
| server certificate to the truststore file, and configure the monitoring agent to use
| SSL.

| Configuring the server to use the cert256.arm certificate

| To use the SSL protocol with the TLS 1.2 protocol for communications between a
| server and a monitoring agent, you must specify the cert256.arm certificate as the
| default certificate on the Tivoli Storage Manager server.

| Before you begin

| Determine whether the Tivoli Storage Manager server is using the cert256.arm
| certificate by default by issuing the following command:
| gsk8capicmd_64 -cert -list -db cert.kdb -stashed

| Review the output to determine whether the TSM Server SelfSigned SHA Key label
| is set as the default certificate. If it is not the default, complete the steps in the
| procedure.

| Procedure

| To specify the cert256.arm certificate as the default, complete the following steps
| from the Tivoli Storage Manager server:
| 1. Issue the following command from the Tivoli Storage Manager server instance
| directory:
| gsk8capicmd_64 -cert -setdefault -db cert.kdb -stashed
| -label "TSM Server SelfSigned SHA Key"
| 2. Restart the Tivoli Storage Manager server so that it can receive the changes to
| the key database file.
| 3. Optional: To verify that the TSM Server SelfSigned SHA Key label is set as the
| default, issue the following command.
| gsk8capicmd_64 -cert -list -db cert.kdb -stashed
|

154 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Creating the truststore file

| If you plan to secure communications between monitoring agents and the Tivoli
| Storage Manager server by using the SSL protocol, you must create a local
| truststore file.

| About this task

| The local truststore file is used to store trusted certificates. On each system where
| you installed the monitoring agent software, you must create one truststore file.

| Procedure

| To create the local truststore file, complete the following steps from the system
| where you installed and configured the monitoring agent:
| 1. Start IBM Key Management by opening a command line and issuing the
| ikeyman command:
| install_dir/itm/JRE/aix_architecture/bin/ikeyman
| where
| v install_dir is the directory where the monitoring agent is installed.
| v aix_architecture is the system-specific architecture, such as aix526.
| The default installation path is /opt/tivoli/tsm/reporting.
| 2. Create a database file by clicking Key Database File > New.
| 3. In the Key database type field, select JKS.
| 4. Specify the file name and the location for the truststore file. The default file
| name is key.jks. Click OK.

| Restriction: The monitoring agent must have access rights to the truststore file.
| 5. In the Password Prompt window, specify and confirm the password. Click OK.
| The password is required to access the truststore file.
| 6. Restart the monitoring agent:
| a. Run the CandleManage program by using the following commands:
| cd install_dir/itm/bin
| ./CandleManage &

| where install_dir is the installation directory. The default installation

| directory is /opt/tivoli/tsm/reporting.
| b. Right-click the monitoring agent and click Stop, then click Start.

| Adding the Tivoli Storage Manager certificate to the truststore

| file
| You must add the Tivoli Storage Manager server self-signed certificate to the
| truststore file.

| Before you begin

| Before you add the Tivoli Storage Manager certificate to the truststore file, verify
| that you completed the following tasks:
| v You created a local truststore file on the same system where the monitoring
| agent is installed and configured.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 155

 Installing Tivoli Monitoring for Tivoli Storage Manager

| v The Tivoli Storage Manager server that you are configuring for SSL is using the
| cert256.arm certificate by default. To ensure that the certificate is set by default,
| follow the instructions in “Configuring the server to use the cert256.arm
| certificate” on page 154.

| About this task

| Each Tivoli Storage Manager server creates a self-signed certificate when the server
| is first started. For each server that is being monitored, the certificate must be
| added to the truststore file.

| Procedure

| To add the Tivoli Storage Manager self-signed certificate to the local truststore file,
| complete the following steps:
| 1. If the monitoring agent is installed and configured on the IBM Tivoli
| Monitoring system, copy the Tivoli Storage Manager server certificate to the
| Tivoli Monitoring for Tivoli Storage Manager file system. The file name of the
| certificate is cert256.arm. The file is stored on the Tivoli Storage Manager
| server in the server instance directory, for example:
| /opt/tivoli/tsm/server/bin/cert256.arm
| Complete the remaining steps from the system where you installed the
| monitoring agent:
| 2. Start IBM Key Management by opening a command line and issuing the
| ikeyman command:
| install_dir/itm/JRE/aix_architecture/bin/ikeyman
| where
| v install_dir is the directory where the monitoring agent is installed.
| v aix_architecture is the system-specific architecture, such as aix526.
| The default installation path is /opt/tivoli/tsm/reporting.
| 3. Click Key Database File > Open.
| 4. In the Key database type field, select JKS.
| 5. In the Open window, click Browse, and go to the directory where you created
| the truststore file, key.jks. Click Open, and click OK.
| 6. In the Password Prompt window, specify the password for the truststore file,
| and click OK.
| 7. In the IBM Key Management window, in the Key database content area,
| select Signer Certificates from the list, and click Add.
| 8. In the Open window, click Browse, and go to the directory where you placed
| the Tivoli Storage Manager server certificate file, cert256.arm. Click Open,
| and click OK.
| 9. Specify a label for the certificate and click OK. For example, you can specify
| the name of the Tivoli Storage Manager server along with the name of the
| certificate: server1.cert256.arm. The certificate is stored in the truststore file.
| 10. Close the IBM Key Management window.
| 11. Restart the monitoring agent:
| a. Run the CandleManage program by using the following commands:
| cd install_dir/itm/bin
| ./CandleManage &

156 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| where install_dir is the installation directory. The default installation

| directory is /opt/tivoli/tsm/reporting.
| b. Right-click the monitoring agent and click Stop, then click Start.

| Configuring the monitoring agent to use Secure Sockets Layer

| Before you can secure communications by using the SSL protocol, you must
| reconfigure the monitoring agent instances to use the SSL protocol.

| Before you begin

| Ensure that you created a local truststore file on the system where the monitoring
| agent is installed and that you added the Tivoli Storage Manager certificate to the
| truststore file. Ensure that all the monitoring agents are configured this way.

| Procedure

| To configure a monitoring agent instance to use the SSL protocol, complete the
| following steps:
| 1. Open the Manage Tivoli Enterprise Management Services application:
| v Run the CandleManage program by using the following commands:
| cd install_dir/itm/bin
| ./CandleManage &

| where install_dir is the installation directory. The default installation directory

| is /opt/tivoli/tsm/reporting.
| 2. Right-click the Tivoli Storage Manager monitoring agent instance and click
| Reconfigure.
| 3. In the Port Number (TCP/IP or SSL) field, specify the port number:
| v If the dsmserv.opt file specifies the ADMINONCLIENT NO option, use the port
| number that is specified by SSLTCPADMINPort.
| v If the dsmserv.opt file does not specify the ADMINONCLIENT NO option, use the
| port number that is specified by SSLTCPPort.
| 4. In the File/Location of SSL Certificate store field, specify the location of the
| local truststore file that you created. The default file name is key.jks. Click OK
| to finish the configuration.

| What to do next

| If you want to disable earlier TLS connection protocols to increase security, follow
| the instructions in “Disabling earlier Transport Layer Security versions” on page
| 153.

| To enhance system security, you can enable the NIST SP800-131A security
| standard. To configure the components in your environment to comply with the
| NIST SP800-131A standard, follow the instructions in “Enabling the NIST
| SP800-131A security standard” on page 158.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 157

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Enabling the NIST SP800-131A security standard

| The National Institute of Standards and Technology (NIST) Special Publications
| (SP) 800-131A standard strengthens algorithms and increases key lengths to
| improve security. To enable the NIST SP800-131A security standard, you must
| configure Tivoli Monitoring for Tivoli Storage Manager components individually.

| Configuring the monitoring agent for compliance with the NIST

| SP800-131A standard
| To enhance communication security, you can configure a Tivoli Monitoring for
| Tivoli Storage Manager monitoring agent to comply with the NIST SP800-131A
| standard.

| Before you begin

| Before you configure the monitoring agent to comply with the NIST SP800-131A
| standard, ensure that the following requirements are met:
| v You must have at least one monitoring agent instance. To create a monitoring
| agent instance, follow the instructions in “Creating and configuring the agent
| instance” on page 134.
| v The monitoring agent is configured to use SSL protocol. For more information
| about setting up SSL communication, see “Configuring Secure Sockets Layer
| communication” on page 154.
| v The Tivoli Storage Manager server is using the cert256.arm certificate by
| default. For more information about setting the default certificate, see
| “Configuring the server to use the cert256.arm certificate” on page 154.
| v The Tivoli Storage Manager server is configured to comply with the NIST
| SP800-131A security standard. For more information about configuring the
| server to comply with the security standard, see “Configuring the Tivoli Storage
| Manager server for compliance with the NIST SP800-131A standard” on page
| 161.

| About this task

| To enable the monitoring agent to be in compliance with the NIST SP800-131A

| standard, you must configure the following communication paths:
| v From the monitoring agent to the Tivoli Storage Manager server
| v From the monitoring agent to the Tivoli Enterprise Monitoring server hub

| Procedure
| 1. Open the Manage Tivoli Enterprise Management Services application:
| v Run the CandleManage program by using the following commands:
| cd install_dir/itm/bin
| ./CandleManage &

| where install_dir is the installation directory. The default installation directory

| is /opt/tivoli/tsm/reporting.
| 2. Secure the communication path from the monitoring agent to the Tivoli
| Enterprise Monitoring server hub:
| a. Right-click the monitoring agent and click Reconfigure.
| b. In the Primary TEMS Connection area of the window, set Protocol 1 to
| IP.SPIPE.
| c. Click OK and follow the instructions in the wizard to complete the
| configuration.
158 IBM Tivoli Storage Manager for AIX: Installation Guide
 Installing Tivoli Monitoring for Tivoli Storage Manager

| d. Restart the agent.

| 1) Run the CandleManage program by using the following commands:
| cd install_dir/itm/bin
| ./CandleManage &

| where install_dir is the installation directory. The default installation

| directory is /opt/tivoli/tsm/reporting.
| 2) Right-click the monitoring agent and click Stop, then click Start.
| 3. Repeat the steps to set Protocol 1 to IP.SPIPE for the following servers and
| agents:
| v Tivoli Enterprise Monitoring server
| v Tivoli Enterprise Portal server
| v Summarization and Pruning Agent
| v Warehouse Proxy Agent
| 4. Secure the communication path from the monitoring agent to the Tivoli Storage
| Manager server. Disable communications that use protocols earlier than TLS 1.2
| by completing the steps in “Disabling earlier Transport Layer Security versions”
| on page 153.

| Configuring IBM Tivoli Monitoring for compliance with the NIST

| SP800-131A standard
| To enhance communication security, you can configure IBM Tivoli Monitoring to
| comply with the NIST SP800-131A standard.

| About this task

| You must complete the configuration for all of the following components:
| v Warehouse Proxy Agent
| v Summarization and Pruning Agent
| v Tivoli Enterprise Monitoring server
| v Tivoli Enterprise Portal server
| v Other services, commands, and servers can optionally be configured if you are
| using them.

| For instructions about configuring the IBM Tivoli Monitoring components to be in

| compliance with the NIST SP 800-131A standard, go to the IBM Tivoli Monitoring
| Knowledge Center at http://www.ibm.com/support/knowledgecenter/
| SSTFXA_6.3.0.2 and review the Enabling SP800-131A for IBM Tivoli Monitoring
| section.

| Configuring Jazz for Service Management for compliance with

| the NIST SP800-131A standard
| Jazz for Service Management is installed along with IBM WebSphere Application
| Server. To make Jazz for Service Management NIST SP800-131A compliant, you
| must configure WebSphere Application Server to comply with the NIST
| SP800-131A standard.

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 159

 Installing Tivoli Monitoring for Tivoli Storage Manager

| Exporting the WebSphere Application Server certificate:

| You can export the WebSphere Application Server certificate so that you can
| import it in to the truststore file.

| Procedure

| To export the WebSphere Application Server certificate, complete the following

| steps:
| 1. Log on to the WebSphere Integrated Solutions console. Open a web browser
| and enter the following address:
| https://hostname:16316/ibm/console

| where hostname is the host name of the system where you installed Jazz for
| Service Management.
| 2. In the WebSphere Integrated Solutions Console navigation tree, click Security >
| SSL certificate and key management. Then click Key stores and certificates >
| NodeDefaultKeyStore > Personal Certificates.
| 3. Select the default certificate and click Extract.
| 4. Enter a file name for the extracted certificate, for example, was_cert.arm. Select
| the default data type and click OK.
| The file is created in the following directory:
| JazzSM_directory/profile/etc/
| where JazzSM_directory is the path where you installed Jazz for Service
| Management.

| Adding the WebSphere Application Server certificate to the truststore file:

| You can add the WebSphere Application Server certificate to the truststore file to
| secure communications between the WebSphere Application Server and Tivoli
| Monitoring for Tivoli Storage Manager.

| Before you begin

| Ensure that you have a local truststore file on the Tivoli Monitoring for Tivoli
| Storage Manager system. If you did not create a truststore file, complete the steps
| in “Creating the truststore file” on page 155.

| Procedure

| To add the WebSphere certificate to the local truststore file, complete the following
| steps:
| 1. Start IBM Key Management by opening a command line and issuing the
| ikeyman command:
| install_dir/itm/JRE/aix_architecture/bin/ikeyman
| where
| v install_dir is the directory where the monitoring agent is installed.
| v aix_architecture is the system-specific architecture, such as aix526.
| The default installation path is /opt/tivoli/tsm/reporting.
| 2. Click Key Database File > Open.
| 3. In the Key database type field, select JKS.

160 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing Tivoli Monitoring for Tivoli Storage Manager

| 4. In the Open window, click Browse, and go to the directory where you created
| the truststore file, for example, key.jks. Click Open, and click OK.
| 5. In the Password Prompt window, specify the password for the truststore file,
| and click OK.
| 6. In the IBM Key Management window, from the list in the Key database
| content area, select Signer Certificates, and click Add.
| 7. In the Open window, click Browse, and go to the directory where you placed
| the WebSphere Application Server certificate file. Click Open, and click OK.
| 8. Specify a label for the certificate and click OK. The certificate is stored in the
| truststore file.
| 9. Close the IBM Key Management window.

| Configuring the Tivoli Storage Manager server for compliance

| with the NIST SP800-131A standard
| To enhance communication security, you can configure the Tivoli Storage Manager
| server to be in compliance with the NIST SP800-131A standard.

| About this task

| The Tivoli Storage Manager server must be configured to secure the

| communications from the monitoring agent to the Tivoli Storage Manager server.

| Procedure

| To configure the Tivoli Storage Manager server to be in compliance with the NIST
| SP800-131A standard, complete the following tasks:
| 1. Set up the SSL and TLS protocols by following the instructions in Setting up
| Secure Sockets Layer and Transport Layer Security (http://www.ibm.com/
| support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
| t_mngdata_setupssl.html).
| 2. Specify communication ports for TLS by following the instructions in
| Specifying communication ports (http://www.ibm.com/support/
| knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
| r_mngdata_specommports.html).
| 3. Replace certificates in the key database file for the Tivoli Storage Manager
| server by following the instructions in Adding a certificate to the key database
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.srv.doc/r_mngdata_sslkeyring.html).

Chapter 9. Installing Tivoli Monitoring for Tivoli Storage Manager 161

Installing Tivoli Monitoring for Tivoli Storage Manager

162 IBM Tivoli Storage Manager for AIX: Installation Guide

|

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage

Manager to Version 7.1
You can upgrade Tivoli Monitoring for Tivoli Storage Manager to V7.1. The
monitoring agents that are installed on any of your Tivoli Monitoring for Tivoli
Storage Manager servers must be upgraded to the same level.

Upgrade scenarios
Before you upgrade Tivoli Monitoring for Tivoli Storage Manager, choose the
scenario that best meets the needs of your company.
v Scenario 1: Your environment is monitoring 1-5 Tivoli Storage Manager servers.
v Scenario 2: Your environment is monitoring more than 5 Tivoli Storage Manager
servers.
v Scenario 3: You have an existing IBM Tivoli Monitoring environment that was
not installed as part of Tivoli Monitoring for Tivoli Storage Manager.

| Consider the following restrictions before you decide which scenario to use:
| v If you have a Tivoli Storage Manager server that is in a different time zone than
| the system with Tivoli Monitoring for Tivoli Storage Manager, install the
| monitoring agent on the Tivoli Storage Manager server. See Scenario 2 to install
| the agent directly on the Tivoli Storage Manager server.
| v If you have more than five servers, install the monitoring agent on each of the
| servers because it is the most efficient use of memory on both the Tivoli Storage
| Manager server and the Tivoli Monitoring for Tivoli Storage Manager server.
| v You can only install the monitoring agent on AIX®, Linux X86_64, and Windows
| operating systems.
Table 27. Upgrade scenarios
Upgrade
scenario Description Tasks that you must complete
Scenario 1 Use this scenario for an Complete all of the tasks in this scenario on
upgraded installation, the same system:
with a plan to monitor 1. Upgrade Tivoli Monitoring for Tivoli
and report on 1-5 Tivoli Storage Manager. The approximate
Storage Manager servers. installation time is 45 - 90 minutes,
depending on the speed of your system.
| Restriction: You cannot install Tivoli
| Monitoring for Tivoli Storage Manager on a
| system where the Tivoli Storage Manager
| server is installed. However, you can install
| the monitoring agent on any supported
| operating system, including any Tivoli
| Storage Manager servers that you want to
| monitor.

© Copyright IBM Corp. 1993, 2014 163

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

Table 27. Upgrade scenarios (continued)

Upgrade
scenario Description Tasks that you must complete
Scenario 2 Use this scenario for an 1. Upgrade Tivoli Monitoring for Tivoli
upgraded installation, Storage Manager. The approximate
with a plan to monitor installation time is 45 - 90 minutes.
and report on more than
| 5 Tivoli Storage Manager
2. Upgrade the monitoring agents that are
| servers.
installed on any of your Tivoli Storage
| Manager servers. Optionally, install and
| configure additional agents on any Tivoli
| Storage Manager servers that you want to
| monitor. The approximate upgrade time
| for the agent is 15 - 30 minutes, and an
| additional 10 minutes, per agent, to
| manually configure each agent.
| Restriction: You cannot install Tivoli
| Monitoring for Tivoli Storage Manager on a
| system where the Tivoli Storage Manager
| server is installed. However, you can install
| the monitoring agent on any supported
| operating system, including any Tivoli
| Storage Manager servers that you want to
| monitor.

Scenario 3 Use this scenario for Prerequisite: You must have IBM Tivoli
upgrading an existing Monitoring version 6.3.0 FP2, or later
IBM Tivoli Monitoring installed.
environment. 1. Upgrade the monitoring agent on the IBM
Tivoli Monitoring server where Tivoli
Enterprise Monitoring server and Tivoli
Enterprise Portal server are installed.
During the agent upgrade, you must
specify the same directory as you did
when you installed IBM Tivoli
Monitoring.
2. Upgrade any monitoring agents that are
installed on any of your Tivoli Storage
Manager servers. Optionally, install and
configure additional agents on any Tivoli
Storage Manager servers that you want to
monitor. The approximate upgrade time
for the agent is 15 - 30 minutes, and an
additional 10 minutes, per agent, to
manually configure each agent.
| Restriction: You cannot install Tivoli
| Monitoring for Tivoli Storage Manager on a
| system where the Tivoli Storage Manager
| server is installed. However, you can install
| the monitoring agent on any supported
| operating system, including any Tivoli
| Storage Manager servers that you want to
| monitor.

164 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| Upgrading Tivoli Monitoring for Tivoli Storage Manager from Version

| 6.3 to Version 7.1
| You can upgrade Tivoli Monitoring for Tivoli Storage Manager from V6.3 to V7.1.

| Before you begin

| Before you upgrade to Tivoli Monitoring for Tivoli Storage Manager V7.1, ensure
| that the following tasks are completed:
| v You have Tivoli Monitoring for Tivoli Storage Manager V6.3 installed. If not, you
| must upgrade to version 6.3 before you can upgrade Tivoli Monitoring for Tivoli
| Storage Manager to version 7.1.
| v Review the planning information such as system requirements and release notes.
| v You have the required access privileges, including the user IDs and passwords.
| You can use the installation worksheet to record the information.
| v Review the upgrade scenarios, and choose the one that best suits your needs.
| v You know the DB2 database instance user ID password that was created during
| the V6.3 installation.
| v Optional: Back up the WAREHOUS database to ensure that you have a copy
| that you can restore if needed. To back up the V6.3 WAREHOUS database, see
| Backing up the DB2 WAREHOUS V6.3 database (http://www.ibm.com/
| support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
| t_rpt_bkup_warehous_634.html).

| Attention: Do not alter the DB2 software that is installed with Tivoli Monitoring
| for Tivoli Storage Manager installation packages and fix packs. Do not install or
| upgrade to a different version, release, or fix pack of DB2 application because
| doing so can damage the database. Tivoli Monitoring for Tivoli Storage Manager
| can use only components and versions that are installed as part of the Tivoli
| Monitoring for Tivoli Storage Manager installation.

| The upgrade procedure must be done on the same system. To upgrade Tivoli
| Monitoring for Tivoli Storage Manager to V7.1 on a different system, see
| Chapter 11, “Migrating Tivoli Monitoring for Tivoli Storage Manager from one
| system to another,” on page 181.

| About this task

| Restriction: If you created your own BIRT reports, they cannot be imported in to
| Tivoli Common Reporting. All of the packaged BIRT reports are available as
| Cognos reports in Tivoli Monitoring for Tivoli Storage Manager V7.1.

| Procedure

| To upgrade Tivoli Monitoring for Tivoli Storage Manager from V6.3 to V7.1,
| complete the following steps:
| 1. Log on to the system where Tivoli Monitoring for Tivoli Storage Manager is
| installed.
| Log in by using the root user ID.
| 2. Change the password for the sysadmin, itmuser, and TEPS user IDs so that the
| passwords are the same. Follow the steps in Resetting passwords for Tivoli

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage Manager to V7.1 165
 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| Monitoring for Tivoli Storage Manager (http://www.ibm.com/support/

| knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.tshoot.doc/
| ts_pdg_update_services_win.html).
| 3. Optional: Export the Cognos reports, if you customized any reports or created
| your own:
| a. Create the upgradeData.zip file by issuing the following command:
| TCR_install_dir/profiles/TIPProfile/upgrade/bin/preupgrade.sh
| TCR_install_dir --username username --password password --productId TCR

| where
| v username and password is the user name and password for the tipadmin
| user ID
| v TCR_install_dir is the Tivoli Common Reporting installation directory.
| The default directory is:
| /opt/IBM/tivoli/tipv2
| The compressed file is created in the following location:
| TCR_install_dir\profiles\TIPProfile\upgrade\data\upgradeData.zip.
| b. Move the upgradeData.zip file out of the Administration Center
| installation directory so that the file is not deleted when you uninstall the
| Administration Center.
| 4. Optional: Export the IBM Tivoli Monitoring situations, workspaces, and
| historical data: “Exporting IBM Tivoli Monitoring data” on page 167
| 5. Optional: Save the agent instance configuration files to avoid manually
| re-creating them: “Saving the agent instance configurations” on page 170
| 6. Uninstall Tivoli Monitoring for Tivoli Storage Manager V6.3:

| Restriction: During the V6.3 uninstallation, do not delete the historical data
| from the WAREHOUS database. The WAREHOUS database will be used after
| you install 7.1.
| a. Completing steps 1-6 in http://www.ibm.com/support/knowledgecenter/
| SSGSG7_6.3.4/com.ibm.itsm.srv.install.doc/t_rpt_inst_uninstall_unix.html.
| 7. Uninstall the Administration Center:
| a. Complete steps in http://www.ibm.com/support/knowledgecenter/
| SSGSG7_6.3.4/com.ibm.itsm.srv.install.doc/t_ac_uninst.html.
| b. Restart the operating system.
| 8. Download and install Tivoli Monitoring for Tivoli Storage Manager V7.1. The
| full installation also installs the monitoring agent on the system. Complete the
| steps in the following section:
| Upgrading Tivoli Monitoring for Tivoli Storage Manager
| 9. Recreate or import your agent instances. If you saved your agent instance
| configuration files, you can import them by completing the steps in
| “Importing the agent instance configuration” on page 171. Otherwise, recreate
| and configure your agent instances by completing the steps in “Creating and
| configuring the agent instance” on page 134.
| 10. Install Jazz for Service Management: “Installing Jazz for Service Management”
| on page 141
| 11. Configure the data source: “Configuring the WAREHOUS data source and
| importing reports” on page 143
| The data source script configures the data source and imports the Cognos
| reports that you exported. When you run the script, specify the -r option for

166 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| TCR cognos report import zip file, and specify the path to the compressed
| Cognos file that you exported, for example:
| datasource.sh -j jazzsm_location -u jazzsm_user -p
| jazzsm_password -i itmuser_password -r upgradeData.zip
| 12. Optional: Import the IBM Tivoli Monitoring data if you exported any
| situations or workspaces: “Importing IBM Tivoli Monitoring data” on page
| 169
| 13. Optional: Configure the historical settings. You can use the historical settings
| file that you exported as a reference. Complete the steps in “Configuring
| summarization and pruning settings” on page 149.

| What to do next

| If you installed the monitoring agent on a remote server, for instance a Tivoli
| Storage Manager server, you must upgrade the monitoring agent. Follow the steps
| in “Upgrading the monitoring agent” on page 178.
| Related tasks:
| “Taking the first steps after installation” on page 147

| Exporting IBM Tivoli Monitoring data

| You can export data that you created or customized on Tivoli Monitoring for Tivoli
| Storage Manager Version 6.3 so that you can import them after you upgrade.

| About this task

| Before you upgrade Tivoli Monitoring for Tivoli Storage Manager from V6.3 to
| V7.1, or later, you can export situations and workspaces that you either customized
| or created, and you can export the historical settings.

| Procedure
| 1. From a command line, go to the following directory:
| installation_dir/ITM/bin

| where installation_dir is the Tivoli Monitoring for Tivoli Storage Manager

| installation directory. The default is:
| /opt/tivoli/tsm/reporting
| 2. Log on using the sysadmin user ID by issuing the following command:
| ./tacmd login -s hostname -u sysadmin -p pswd

| where hostname is the name of the system.

| 3. Export the IBM Tivoli Monitoring situations if you created your own. Issue the
| following command:
| ./tacmd bulkExportSit -t sk -d -f -p /my_sitation_dir

| where my_sitation_dir is the path to the directory where you want to save the
| situations. The situations are exported to the Bulk\SITUATION directory in the
| path that you specified in the command.

| Restriction: The directory must not exist in the Tivoli Monitoring for Tivoli
| Storage Manager installation directory.
| 4. Export the workspaces that you customized:
| a. Verify that your ID has workspace administration-mode authority:

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage Manager to V7.1 167
 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| 1) Start Tivoli Enterprise Portal.

| 2) Click Edit > Administer Users.
| 3) Select your ID, for example SYSADMIN.
| 4) In the Authorities section, select Workspace Administration.
| 5) Ensure that Workspace Administration Mode is selected, and click OK.
| b. Increase the maximum heap size to ensure that JVM has sufficient space by
| issuing the following commands:
| export TACMD_JVM_MAX_MEMORY=2048
| c. Export the workspaces by issuing the following command for each
| workspace that you customized:
| ./tacmd exportWorkspaces -s hostname -w workspace_name -u sysadmin -p pswd
| -x /workspace_dir/workspace_name.xml

| where workspace_dir is the directory path where you want to save the
| exported workspace.

| Restriction: The directory must not exist in the Tivoli Monitoring for Tivoli
| Storage Manager installation directory.
| 5. Export the historical data to record the settings:
| Issue the following commands from a command line. Ensure that you update
| the pswd, CANDLE_HOME, and hostname variables.
| export admin=sysadmin
| export pswd=sysadmin_password
| export hostname=your_hostname
| export CANDLE_HOME=/opt/tivoli/tsm/reporting/itm
| export type="Tivoli Storage Manager"
| cd $CANDLE_HOME/bin
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK ACTIVITY LOG"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK ACTIVITY SUMMARY"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK CLIENT MISSED FILES"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK CLIENT NODE STATUS"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK CLIENT NODE STORAGE"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK NODE ACTIVITY"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK REPLDETAILS"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK REPLSTATUS"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK SCHEDULE"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK STORAGE DEVICE"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK STORAGE POOL"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK TAPE USAGE"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| ./tacmd histViewAttributeGroup -t "$type" -o "KSK TAPE VOLUME"
| -s $hostname -u $admin -w $pswd >> /temp_dir/collection_settings.txt
| 6. Verify that the historical data was successfully exported by reviewing the
| collections_settings.txt file. For each workspace, you might see text similar
| to the following example:

168 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| KUIHVA001I Validating user credentials...

| Attribute Group Name : KSK ACTIVITY LOG
| Status : Configured
| Collections : KSK_KSKACTVLOG
| Summarization :
| Yearly : On
| Quarterly : On
| Monthly : On
| Weekly : On
| Daily : On
| Hourly : On
| Pruning :
| Yearly : 7 Years
| Quarterly : 2 Years
| Monthly : 2 Years
| Weekly : 6 Months
| Daily : 2 Months
| Hourly : 14 Days
| Detailed Data : 3 Months
| Available TEMS : TEMS_TCR

| Importing IBM Tivoli Monitoring data

| You can import the data from IBM Tivoli Monitoring Version 6.3 to Tivoli
| Monitoring for Tivoli Storage Manager Version 7.1, or later.

| Before you begin

| Before you can import the IBM Tivoli Monitoring data, you must have the
| situations and workspaces files that you exported.

| About this task

| After you upgrade Tivoli Monitoring for Tivoli Storage Manager from V6.3 to V7.1,
| or later, you can import situations and workspaces.

| Procedure
| 1. From a command line, go to the following directory:
| installation_dir/ITM/bin

| where installation_dir is the Tivoli Monitoring for Tivoli Storage Manager

| installation directory. The default is:
| /opt/tivoli/tsm/reporting
| 2. Log in as sysadmin by issuing the following command:
| ./tacmd login -s hostname -u sysadmin -p pswd

| where hostname is the name of the system.

| 3. Import the IBM Tivoli Monitoring situations that you exported. Issue the
| following command:
| ./tacmd bulkImportSit -p /my_situations_dir

| where my_situations_dir is the path to the directory where you exported the
| situations.
| 4. Assign the situations to managed systems where the situations will run and
| then start the situations:
| a. Start Tivoli Enterprise Portal.
| b. Click Edit > Situation Editor

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage Manager to V7.1 169
 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| c. For each situation, select it, click the Distribution tab, assign it to a
| managed system, and then right-click the situation and click Start.
| d. If the imported situation was associated with a navigator item, recreate the
| association.
| 5. Import the workspaces that you customized or created:
| a. Verify that your ID has workspace administration-mode authority:
| 1) Start Tivoli Enterprise Portal.
| 2) Click Edit > Administer Users.
| 3) Select your ID, for example SYSADMIN.
| 4) In the Authorities section, select Workspace Administration.
| 5) Ensure that Workspace Administration Mode is selected, and click OK.
| b. Increase the maximum heap size to ensure that JVM has sufficient space by
| issuing the following commands:
| export TACMD_JVM_MAX_MEMORY=2048
| c. Import the workspaces that you exported. Issuing the following command
| for each workspace that you exported:
| ./tacmd importWorkspaces -s hostname -u sysadmin -p pswd
| -x /workspace_dir/workspace_name.xml

| where:
| v workspace_dir is the path to where you extracted the workspaces
| v workspace_name is the name of the workspace that you exported
| d. Optional: If you changed the workspace administration mode for the Tivoli
| Enterprise Portal user ID, you can change it back to the original setting. See
| Step 5a.

| What to do next

| Configure the historical settings, if you do not want to use the default settings. You
| can refer to the historical settings output if you exported the settings. Complete the
| steps in “Configuring the WAREHOUS data source and importing reports” on
| page 143.

| Saving the agent instance configurations

| You can save the monitoring agent instance configurations before you upgrade
| Tivoli Monitoring for Tivoli Storage Manager. Therefore, after you upgrade, you do
| not need to manually re-create the agent instances.

| Before you begin

| Before you can save the agent instance configuration, you must have Tivoli
| Monitoring for Tivoli Storage Manager V6.3 installed.

| About this task

| Tivoli Monitoring for Tivoli Storage Manager V6.3 is installed with a large amount
| of custom configuration that can make it complex to re-create after an upgrade. If
| your agent instance configurations are complex, you can save them before you
| upgrade Tivoli Monitoring for Tivoli Storage Manager to V7.1, or later.

| If the agent configuration is not complex, re-create the agent after you upgrade
| Tivoli Monitoring for Tivoli Storage Manager.

170 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| Procedure

| To save the agent instances, complete the following steps:

| 1. From Manage Tivoli Enterprise Monitoring Services, stop all agents and
| services.
| 2. Download and install the agent package V7.1, or later:
| Installing monitoring agents on AIX

| Tip: Install the agent in to the same directory where the V6.3 agent is installed.
| The default directory is:
| /opt/tivoli/tsm/reporting/itm
| 3. Go to the following directory:
| installation_dir/itm/config
| 4. Back up or move the configuration files to a temporary location.
| For example, back up or move the following files:
| v sk.ini
| v sk_instance_name.config
| v host_sk_instance_name.cfg
| where instance_name is the name of the agent instance, and host is the host
| name of the system.

| Importing the agent instance configuration

| If you saved the configuration files for the monitoring agents, you can import the
| agents in to Tivoli Monitoring for Tivoli Storage Manager V7.1, or later.

| Before you begin

| Before you can import the agent instances in to Tivoli Monitoring for Tivoli Storage
| Manager V7.1, or later, ensure that the following tasks are complete:
| v You saved the configuration files for the Tivoli Monitoring for Tivoli Storage
| Manager V6.3 agent instances by completing the steps from “Saving the agent
| instance configurations” on page 170.

| Procedure

| To import the agent instances, complete the following steps:

| 1. Go to the following directory:
| installation_dir/itm/config
| 2. Restore, or move the configuration files that you saved in to the directory:
| v sk.ini
| v sk_instance_name.config
| v host_sk_instance_name.cfg
| where instance_name is the name of the agent instance, and host is the host
| name of the system.
| 3. For each agent instance, reconfigure the instance. Accept the default values
| during the reconfiguration. The values are the same values as the Tivoli
| Monitoring for Tivoli Storage Manager V6.3 agent instance.

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage Manager to V7.1 171
 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| What to do next

| You can start the agent instances to start collecting data.

| AIX: Upgrading Tivoli Monitoring for Tivoli Storage Manager

| To upgrade Tivoli Monitoring for Tivoli Storage Manager, you can use the
| graphical installation wizard, the command line in console mode, or silent mode.

| Before you begin

| Before you install Tivoli Monitoring for Tivoli Storage Manager, verify that the
| following requirements are met:
| v Ensure that your system meets the software and hardware requirements. For
| more information about the system requirements, see “System requirements for
| Tivoli Monitoring for Tivoli Storage Manager” on page 103.
| v Do not install Tivoli Monitoring for Tivoli Storage Manager on a system that has
| a Tivoli Storage Manager server installed.
| v Verify that you have the required access privileges, including user IDs and
| passwords.
| v Ensure that there are no spaces and no non-ASCII characters in the installation
| package name or in the path to the package.
| v If you are installing Tivoli Monitoring for Tivoli Storage Manager on a remote
| system by using an X display, and the local server does not have an X server
| running, the installation might fail. If this happens, you must run the wizard in
| console mode.
| v If you are installation the Tivoli Monitoring for Tivoli Storage Manager
| monitoring agent in to an existing Tivoli Monitoring environment, specify the
| existing Tivoli Monitoring installation directory. The default directory is
| /opt/IBM/ITM.

| If you are upgrading from Tivoli Monitoring for Tivoli Storage Manager V6, see
| “Upgrading Tivoli Monitoring for Tivoli Storage Manager from Version 6.3 to
| Version 7.1” on page 165.

| Attention: Do not alter the DB2 software that is installed with Tivoli Monitoring
| for Tivoli Storage Manager installation packages and fix packs. Do not install or
| upgrade to a different version, release, or fix pack of DB2 application because
| doing so can damage the database. Tivoli Monitoring for Tivoli Storage Manager
| can use only components and versions that are installed as part of the Tivoli
| Monitoring for Tivoli Storage Manager installation.

| About this task

| With the Tivoli Monitoring for Tivoli Storage Manager installation package, you
| can install or upgrade the following software:
| v Tivoli Monitoring for Tivoli Storage Manager
| v Tivoli Monitoring for Tivoli Storage Manager agent only
| To determine when and where you would install only the agent package, review
| the installation scenarios. To install the agent on a remote server, see “Installing the
| monitoring agent” on page 119.

172 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| Restriction: You cannot install the Tivoli Monitoring for Tivoli Storage Manager
| package and the agent only package on the same system.

| AIX: Obtaining the Tivoli Monitoring for Tivoli Storage

| Manager installation package
| You can obtain the Tivoli Monitoring for Tivoli Storage Manager installation
| package from a DVD or an IBM download site such as IBM Passport Advantage.

| About this task

| If you plan to download the files, set the system user limit for the maximum file
| size to unlimited to ensure that the files can be downloaded correctly:
| 1. To query the maximum file size value, issue the following command from a
| command line:
| ulimit -Hf
| 2. If the system user limit for maximum file size is not set to unlimited, change it
| to unlimited by following the instructions in the documentation for your
| operating system.

| Verify that you have enough space to store the installation files when they are
| extracted from the product package.

| Procedure
| 1. Download the two installation packages from one of the following websites, or
| you can access the files from the product DVD:
| v Go to Passport Advantage site at http://www.ibm.com/software/lotus/
| passportadvantage/.
| v Go to the Tivoli Storage Manager support site at http://www.ibm.com/
| support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
| for maintenance fixes, and updates.
| 2. Depending on whether you have the DVD disks or installation packages,
| complete one of the following methods to extract the files to the file system:
| Product DVD disks
| a. Create a directory on the file system.
| b. For each DVD disk, copy the contents of the disk in to the directory
| that you created.

| Tip: You can delete the files after you install Tivoli Monitoring for
| Tivoli Storage Manager to free up space on the file system.
| Installation packages
| a. Create a directory and move the two packages that you
| downloaded in to the directory.
| b. Ensure that executable permission is set for the packages. If
| necessary, change the file permissions by issuing the following
| command:
| chmod a+x package_name.bin
| c. Extract the packages by issuing the following command for each
| package:
| ./package_name.bin
| where package_name is the name of the file that you downloaded, for
| example:

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage Manager to V7.1 173
 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| TSMRPT-Full-Installer-1of2-AIX-7.1.0.000.bin

| Restriction: The path must contain no more than 128 characters. Do

| not extract the packages to a directory that contains previously
| extracted files, or any other files.
| 3. Ensure that the lsuser command is enabled so that the Tivoli Monitoring for
| Tivoli Storage Manager wizards work properly. By default, the command is
| enabled. You can issue the lsuser from a command line, along with a user
| name to verify that it returns a valid result.

| AIX: Upgrading Tivoli Monitoring for Tivoli Storage Manager

| by using the Upgrade wizard
| You can upgrade Tivoli Monitoring for Tivoli Storage Manager by using the
| Upgrade wizard of IBM Installation Manager.

| Before you begin

| Take the following actions before you start the installation:

| v Verify that you copied the DVD files to the local system, or that you
| downloaded and extracted the packages for Tivoli Monitoring for Tivoli Storage
| Manager.
| v Verify that the following RPM files are installed:
| atk-1.12.3-2.aix5.2.ppc.rpm
| cairo-1.8.8-1.aix5.2.ppc.rpm
| expat-2.0.1-1.aix5.2.ppc.rpm
| fontconfig-2.4.2-1.aix5.2.ppc.rpm
| freetype2-2.3.9-1.aix5.2.ppc.rpm
| gettext-0.10.40-6.aix5.1.ppc.rpm
| glib2-2.12.4-2.aix5.2.ppc.rpm
| gtk2-2.10.6-4.aix5.2.ppc.rpm
| libjpeg-6b-6.aix5.1.ppc.rpm
| libpng-1.2.32-2.aix5.2.ppc.rpm
| libtiff-3.8.2-1.aix5.2.ppc.rpm
| pango-1.14.5-4.aix5.2.ppc.rpm
| xcursor-1.1.7-3.aix5.2.ppc.rpm
| xft-2.1.6-5.aix5.1.ppc.rpm
| xrender-0.9.1-3.aix5.2.ppc.rpm
| zlib-1.2.3-3.aix5.1.ppc.rpm
| pixman-0.12.0-3.aix5.2.ppc.rpm

| Tip: You can issue the following command from a command line to determine
| whether the RPM files are installed:
| rpm -qa |grep rpm_package

| where rpm_package is the name of the RPM package.

| If the RPM files are not installed, complete the steps in Installing RPM files for
| the wizard mode.
| v Verify that the operating system is set to the language that you require. By
| default, the language of the operating system is the language that is used during
| the installation.

| About this task

| With the Tivoli Monitoring for Tivoli Storage Manager installation package, you
| can install or upgrade the following software:
| v Tivoli Monitoring for Tivoli Storage Manager

174 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| v Tivoli Monitoring for Tivoli Storage Manager agent only

| To determine when and where you would install only the agent package, review
| the installation scenarios. To install the agent on a remote server, see “Installing the
| monitoring agent” on page 119.

| Restriction: You cannot install the Tivoli Monitoring for Tivoli Storage Manager
| package and the agent only package on the same system.

| Procedure

| To install Tivoli Monitoring for Tivoli Storage Manager, complete the following
| steps:
| 1. Change to the directory where you extracted the installation files.
| 2. Start the wizard by issuing the following command:
| ./install.sh

| Results

| If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory. You can view
| installation log files by clicking File > View Log from the IBM Installation
| Manager tool.

| What to do next

| If you already have Jazz for Service Management installed, reconfigure the
| WAREHOUS data source to reconnect Tivoli Common Reporting to the
| WAREHOUS database. Follow the steps in “Configuring the WAREHOUS data
| source and importing reports” on page 143. Otherwise, install Jazz for Service
| Managementso that you can view historical reports. Go to “Installing Jazz for
| Service Management” on page 141.

| After you upgrade Tivoli Monitoring for Tivoli Storage Manager, see “Taking the
| first steps after installation” on page 147.

| AIX: Installing RPM files for the installation wizard

| Before you can use the wizard to install Tivoli Monitoring for Tivoli Storage
| Manager, you must ensure that the necessary RPM files are installed.

| About this task

| The following RPM files must be installed before you use the wizard of IBM
| Installation Manager to install or upgrade Tivoli Monitoring for Tivoli Storage
| Manager:
| atk-1.12.3-2.aix5.2.ppc.rpm
| cairo-1.8.8-1.aix5.2.ppc.rpm
| expat-2.0.1-1.aix5.2.ppc.rpm
| fontconfig-2.4.2-1.aix5.2.ppc.rpm
| freetype2-2.3.9-1.aix5.2.ppc.rpm
| gettext-0.10.40-6.aix5.1.ppc.rpm
| glib2-2.12.4-2.aix5.2.ppc.rpm
| gtk2-2.10.6-4.aix5.2.ppc.rpm
| libjpeg-6b-6.aix5.1.ppc.rpm
| libpng-1.2.32-2.aix5.2.ppc.rpm
| libtiff-3.8.2-1.aix5.2.ppc.rpm
| pango-1.14.5-4.aix5.2.ppc.rpm
| xcursor-1.1.7-3.aix5.2.ppc.rpm

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage Manager to V7.1 175
 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| xft-2.1.6-5.aix5.1.ppc.rpm
| xrender-0.9.1-3.aix5.2.ppc.rpm
| zlib-1.2.3-3.aix5.1.ppc.rpm
| pixman-0.12.0-3.aix5.2.ppc.rpm

| Tip: You can issue the following command from a command line to determine
| whether the RPM files are installed:
| rpm -qa |grep rpm_package

| where rpm_package is the name of the RPM package.

| Procedure

| To install the necessary RPM files, complete the following steps:

| 1. Ensure that there is at least 150 MB of free space in the /opt file system.
| 2. To install the RPM files, choose one of the following options:
| v If you plan to install Tivoli Monitoring for Tivoli Storage Manager from the
| product DVD, take the following actions:
| a. In the base directory of the DVD, change to the gtk directory.
| b. Copy the download-prerequisites.sh file to a location where you can
| download the RPM files.
| v If you obtained the Tivoli Monitoring for Tivoli Storage Manager installation
| package from an IBM download site, from the directory where the
| installation package file is extracted, go to the gtk directory.
| 3. Download the RPM files to the current working directory from the IBM AIX
| Toolbox for Linux Applications website by issuing the following command:
| download-prerequisites.sh
| 4. From the directory that contains the RPM files that you downloaded, install
| them by issuing the following command:
| rpm -Uvh *.rpm

| AIX: Upgrading Tivoli Monitoring for Tivoli Storage Manager

| by using console mode
| You can upgrade Tivoli Monitoring for Tivoli Storage Manager by using the
| command line. You must run the installation program of IBM Installation Manager
| from the command line with the parameter for console mode.

| Before you begin

| Take the following actions before you start the installation:

| v Verify that the operating system is set to the language that you require. By
| default, the language of the operating system is the language that is used during
| the installation.

| About this task

| With the Tivoli Monitoring for Tivoli Storage Manager installation package, you
| can install or upgrade the following software:
| v Tivoli Monitoring for Tivoli Storage Manager
| v Tivoli Monitoring for Tivoli Storage Manager agent only

176 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| To determine when and where you would install only the agent package, review
| the installation scenarios. To install the agent on a remote server, see “Installing the
| monitoring agent” on page 119.

| Restriction: You cannot install the Tivoli Monitoring for Tivoli Storage Manager
| package and the agent only package on the same system.

| Procedure

| To install Tivoli Monitoring for Tivoli Storage Manager, complete the following
| steps:
| 1. Change to the directory where you extracted the installation files.
| 2. Start the wizard in console mode by issuing the following command from a
| command line:
| ./install.sh -c
| 3. Optional: Generate a response file as part of a console mode installation.
| Complete the console mode installation options, and in the Summary pane,
| specify G to generate the responses.

| Results

| If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory, for example:
| /var/ibm/InstallationManager/logs

| What to do next

| If you already have Jazz for Service Management installed, reconfigure the
| WAREHOUS data source to reconnect Tivoli Common Reporting to the
| WAREHOUS database. Follow the steps in “Configuring the WAREHOUS data
| source and importing reports” on page 143. Otherwise, install Jazz for Service
| Managementso that you can view historical reports. Go to “Installing Jazz for
| Service Management” on page 141.

| After you upgrade Tivoli Monitoring for Tivoli Storage Manager, see “Taking the
| first steps after installation” on page 147.

| AIX: Upgrading Tivoli Monitoring for Tivoli Storage Manager in

| silent mode
| You can upgrade the Tivoli Monitoring for Tivoli Storage Manager in silent mode
| without any user interaction by specifying a response file. You must run the
| installation program of IBM Installation Manager from the command line with the
| parameters for silent mode.

| Before you begin

| The input directory, which is in the directory where the installation files were
| extracted, contains the following sample response files to install, update, and
| uninstall Tivoli Monitoring for Tivoli Storage Manager:
| v install_response_sample.xml
| v update_response_sample.xml
| v uninstall_response_sample.xml
| You must edit the sample files before you use them.

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage Manager to V7.1 177
 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| About this task

| With the Tivoli Monitoring for Tivoli Storage Manager installation package, you
| can install or upgrade the following software:
| v Tivoli Monitoring for Tivoli Storage Manager
| v Tivoli Monitoring for Tivoli Storage Manager agent only
| To determine when and where you would install only the agent package, review
| the installation scenarios. To install the agent on a remote server, see “Installing the
| monitoring agent” on page 119.

| Restriction: You cannot install the Tivoli Monitoring for Tivoli Storage Manager
| package and the agent only package on the same system.

| Procedure
| 1. Create a response file, or use one of the sample response files, such as
| install_response_sample.xml or update_response_sample.xml.
| 2. Edit the response file and specify a DB2 administrator password and the
| sysadmin user ID. You can also change other defaults if you need.
| 3. Start the silent installation by issuing the following command from the
| directory where the installation files were extracted:
| ./install.sh -s -input response_file -acceptLicense

| where response_file is the response file path, including the file name.

| Results

| If errors occur during the installation process, the errors are recorded in log files
| that are stored in the IBM Installation Manager logs directory, for example:
| /var/ibm/InstallationManager/logs

| What to do next

| If you already have Jazz for Service Management installed, reconfigure the
| WAREHOUS data source to reconnect Tivoli Common Reporting to the
| WAREHOUS database. Follow the steps in “Configuring the WAREHOUS data
| source and importing reports” on page 143. Otherwise, install Jazz for Service
| Managementso that you can view historical reports. Go to “Installing Jazz for
| Service Management” on page 141.

| After you upgrade Tivoli Monitoring for Tivoli Storage Manager, see “Taking the
| first steps after installation” on page 147.

Upgrading the monitoring agent

You can upgrade the monitoring agent so that the version is at the same level as
the monitoring agent on the IBM Tivoli Monitoring server.

| About this task

| You can upgrade the monitoring agent on remote servers for the Tivoli Storage
| Manager servers that are being monitored. You can also upgrade the monitoring
| agent on an existing system that has IBM Tivoli Monitoring installed.

178 IBM Tivoli Storage Manager for AIX: Installation Guide

 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| Restriction: The monitoring agent in the environment must be at the same version
| as the agent on the system where IBM Tivoli Monitoring is installed.

Procedure

To upgrade your existing monitoring agents to V7.1, complete the following steps:
1. Stop all existing monitoring agents by using one of the following methods:
v From the Manage Tivoli Enterprise Monitoring Services window, select each
monitoring agent instance, and click Actions > Stop.
v To stop the agents by using the command line, complete the following steps:
| a. From a command line, go to the following directory:
| cd install_dir/itm/bin

| where the install_dir is the IBM Tivoli Monitoring installation directory.

| The default directory is /opt/IBM/ITM.
b. Display the agents that are running by issuing the following command,
and then review the output to determine which services are running:
./cinfo -r
c. Stop all of the Tivoli Storage Manager instances by issuing the following
command:
./itmcmd agent -o instance_name stop sk
2. Install the monitoring agent V7.1 on the remote Tivoli Storage Manager server,
or on an existing system that has IBM Tivoli Monitoring installed. Complete the
steps in “Installing the monitoring agent” on page 119.
3. Return to the Manage Tivoli Enterprise Monitoring Services window, right-click
each monitoring agent instance, and click Start.

Tip: Alternatively, you can restart the agents by issuing the following
commands:
cd install_dir/itm/tables
../bin/itmcmd agent -o instance_name start sk

| Upgrading the operating system

| You can upgrade the operating system so that it meets the Tivoli Monitoring for
| Tivoli Storage Manager V7.1 system requirements.

| About this task

| When you decide to upgrade Tivoli Monitoring for Tivoli Storage Manager to V7.1,
| you might find that the operating system no longer meets the minimum system
| requirements. You can either upgrade the operating system, or migrate Tivoli
| Monitoring for Tivoli Storage Manager to another system. For more information
| about migrating the system, see Chapter 11, “Migrating Tivoli Monitoring for Tivoli
| Storage Manager from one system to another,” on page 181.

| Procedure

| To upgrade the operating system and upgrade Tivoli Monitoring for Tivoli Storage
| Manager, complete the following steps:

Chapter 10. Upgrading Tivoli Monitoring for Tivoli Storage Manager to V7.1 179
 Upgrading Tivoli Monitoring for Tivoli Storage Manager

| 1. Back up the Tivoli Monitoring for Tivoli Storage Manager environment: Backing
| up Tivoli Monitoring for Tivoli Storage Manager (http://www.ibm.com/
| support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
| t_rpt_bkup_itm4tsm.html)
| 2. Optional: Export the IBM Tivoli Monitoring historical settings and situations
| that you created or customized. Ensure that you use the backup-archive client
| to back up the exported data. Complete the steps in “Exporting IBM Tivoli
| Monitoring data” on page 167.
| 3. Optional: Save the agent instance configuration files to avoid manually
| re-creating them: “Saving the agent instance configurations” on page 170
| 4. Upgrade your operating system so that the system meets the minimum system
| requirements.
| 5. On the new system, download and install Tivoli Monitoring for Tivoli Storage
| Manager V7.1, or later. The full installation also installs the monitoring agent
| on the system. Complete the steps in Chapter 9, “Installing Tivoli Monitoring
| for Tivoli Storage Manager,” on page 99.

| Restriction: To avoid overwriting data, do not start any monitoring agents

| until after you restore the WAREHOUS database.
| 6. On the new system, restore the Tivoli Monitoring for Tivoli Storage Manager
| V6.3 data that you backed up, such as the WAREHOUS database, workspaces,
| and Cognos reports: Restoring Tivoli Monitoring for Tivoli Storage Manager
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.srv.doc/t_rpt_restore_itm4tsm.html).
| 7. Recreate or import your agent instances. If you saved your agent instance
| configuration files, you can import them by completing the steps in “Importing
| the agent instance configuration” on page 171. Otherwise, recreate and
| configure your agent instances by completing the steps in “Creating and
| configuring the agent instance” on page 134.

| What to do next

| After you move Tivoli Monitoring for Tivoli Storage Manager to the new system,
| you can configure the historical settings and the data source:
| v You can configure the historical settings if you do not want to use the default
| settings. You can use the historical settings file that you exported as a reference.
| Follow the steps in “Configuring summarization and pruning settings” on page
| 149.
| v Configure the data source by following the steps in “Configuring the
| WAREHOUS data source and importing reports” on page 143.
|

180 IBM Tivoli Storage Manager for AIX: Installation Guide

|

| Chapter 11. Migrating Tivoli Monitoring for Tivoli Storage

| Manager from one system to another
| You can move the Tivoli Monitoring for Tivoli Storage Manager environment to a
| new system, with your configuration settings and data.

| About this task

| You might have to migrate Tivoli Monitoring for Tivoli Storage Manager to another
| system for any of the following reasons:
| v The operating system does not meet the system requirements for Tivoli
| Monitoring for Tivoli Storage Manager V7.1, or later.
| v The system that you are using will no longer be available to host Tivoli
| Monitoring for Tivoli Storage Manager.
| v You want to move Tivoli Monitoring for Tivoli Storage Manager to newer or
| faster hardware.

| Restriction: A database backup from one platform family can only be restored on
| any system within the same platform family. Migration is only supported from
| Tivoli Monitoring for Tivoli Storage Manager V6.3 to V7.1, or later. You must
| upgrade Tivoli Monitoring for Tivoli Storage Manager V6.1 or V6.2 to V6.3 before
| you move to V7.1, or later. You can upgrade Tivoli Monitoring for Tivoli Storage
| Manager from a Windows 32-bit system to a Windows 64-bit system. Similarly, you
| can upgrade Tivoli Monitoring for Tivoli Storage Manager on any Linux 32-bit
| system to any Linux 64-bit system.
|
| Migrating Tivoli Monitoring for Tivoli Storage Manager V6.3 to V7.1, or
| later on another system
| You can move the Tivoli Monitoring for Tivoli Storage Manager environment to a
| new system and upgrade it at the same time.

| Procedure
| 1. Back up the Tivoli Monitoring for Tivoli Storage Manager environment: Backing
| up Tivoli Monitoring for Tivoli Storage Manager (http://www.ibm.com/
| support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
| t_rpt_bkup_itm4tsm.html)
| 2. Optional: Export the IBM Tivoli Monitoring historical settings and situations
| that you created or customized. Ensure that you use the backup-archive client
| to back up the exported data. Complete the steps in “Exporting IBM Tivoli
| Monitoring data” on page 167.
| 3. On the new system, download and install Tivoli Monitoring for Tivoli Storage
| Manager V7.1, or later. The full installation also installs the monitoring agent
| on the system. Complete the steps in Chapter 9, “Installing Tivoli Monitoring
| for Tivoli Storage Manager,” on page 99.

| Restriction: To avoid overwriting data, do not start any monitoring agents

| until after you restore the WAREHOUS database.
| 4. On the new system, restore the Tivoli Monitoring for Tivoli Storage Manager
| V6.3 data that you backed up, such as the WAREHOUS database, workspaces,

© Copyright IBM Corp. 1993, 2014 181

| and Cognos reports: Restoring Tivoli Monitoring for Tivoli Storage Manager
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.srv.doc/t_rpt_restore_itm4tsm.html).

| What to do next

| After you move Tivoli Monitoring for Tivoli Storage Manager to the new system,
| you can configure the historical settings and the data source:
| v You can configure the historical settings if you do not want to use the default
| settings. You can use the historical settings file that you exported as a reference.
| Follow the steps in “Configuring summarization and pruning settings” on page
| 149.
| v Configure the data source by following the steps in “Configuring the
| WAREHOUS data source and importing reports” on page 143.
|
| Migrating Tivoli Monitoring for Tivoli Storage Manager V7.1, or later to
| another system
| You can move Tivoli Monitoring for Tivoli Storage Manager V7.1, or later to a new
| system.

| Procedure
| 1. Back up the Tivoli Monitoring for Tivoli Storage Manager environment: Backing
| up Tivoli Monitoring for Tivoli Storage Manager (http://www.ibm.com/
| support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/
| t_rpt_bkup_itm4tsm.html)
| 2. On the new system, download and install Tivoli Monitoring for Tivoli Storage
| Manager V7.1, or later. The full installation also installs the monitoring agent
| on the system. Complete the steps in Chapter 9, “Installing Tivoli Monitoring
| for Tivoli Storage Manager,” on page 99.

| Restriction: To avoid overwriting data, do not start any monitoring agents

| until after you restore the WAREHOUS database.
| 3. On the new system, restore the Tivoli Monitoring for Tivoli Storage Manager
| V6.3 data that you backed up, such as the WAREHOUS database, workspaces,
| and Cognos reports: Restoring Tivoli Monitoring for Tivoli Storage Manager
| (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/
| com.ibm.itsm.srv.doc/t_rpt_restore_itm4tsm.html).
| 4. Reconfigure the monitoring agents by completing the steps in “Creating and
| configuring the agent instance” on page 134.

| What to do next

| After you move Tivoli Monitoring for Tivoli Storage Manager to the new system,
| you can configure the historical settings and the data source:
| v You can configure the historical settings if you do not want to use the default
| settings. You can use the historical settings file that you exported as a reference.
| Follow the steps in “Configuring summarization and pruning settings” on page
| 149.
| v Configure the data source by following the steps in “Configuring the
| WAREHOUS data source and importing reports” on page 143.
|

182 IBM Tivoli Storage Manager for AIX: Installation Guide

|

| Chapter 12. Uninstalling Tivoli Monitoring for Tivoli Storage

| Manager
| You can uninstall Tivoli Monitoring for Tivoli Storage Manager and the monitoring
| agents in your environment if you no longer need them.

| About this task

| Use IBM Installation Manager to uninstall Tivoli Monitoring for Tivoli Storage
| Manager or the monitoring agent. However, If you installed the monitoring agent
| on an existing IBM Tivoli Monitoring server, complete the steps in “Uninstalling
| monitoring agents in an existing IBM Tivoli Monitoring environment” on page 188.

| Tip: When you uninstall Tivoli Monitoring for Tivoli Storage Manager, the
| monitoring agent on the system is also uninstalled. Therefore, you do not have to
| uninstall the monitoring agent on the system after you uninstall Tivoli Monitoring
| for Tivoli Storage Manager.
|
| Uninstalling Jazz for Service Management
| You can uninstall Jazz for Service Management if you no longer need it.

| About this task

| Before you uninstall Jazz for Service Management, you must uninstall Tivoli
| Common Reporting.

| Tip: The Cognos reports are removed from the system when you uninstall Tivoli
| Common Reporting. If you must retain the reports, you can export them.

| Procedure
| 1. Uninstall Tivoli Common Reporting by completing the steps in
| http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.0/
| com.ibm.psc.doc_1.1.0/tcr_original/ttcr_uninstall.html.
| 2. Uninstall Jazz for Service Management by completing the steps in
| http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.0/
| com.ibm.psc.doc_1.1.0/install/psc_t_install_uninstall_adv_oview.html.
| 3. Remove the Deployment Engine entries for Tivoli Common Reporting by
| completing the following steps:
| a. Open a command line and go to the following directory:
| If you installed the Administration Center as root, go to
| /usr/ibm/common/acsi/bin. Otherwise, go to USER_HOME/USER/
| .acsi_USERID, where USER_HOME, USER, and USERID is the
| information for the user that completed the installation.
| b. Issue the following command:
| de_lsrootiu.sh > de_lsrootiu.txt
| c. Review de_lsrootiu.txt and collect the UUID and discriminant values for
| the following identityNames:
| v TCRCore
| v TCREmbedded

© Copyright IBM Corp. 1993, 2014 183

 Uninstalling Tivoli Monitoring for Tivoli Storage Manager

| v TCRStandalone
| v Install IU
| d. Delete the entry for each identityName by issuing the following command:
| deleteRootIU.sh UUID discriminant

| where UUID and discriminant are the values from the de_lsrootiu.txt
| output.
| For example, to delete the TCRCore identityName, issue the following
| command:
| DelRootIUnRelationships 3DD9564D2E7442788584C1F35B07F2A2
| /opt/IBM/JazzSM/reporting
|
| Uninstalling Tivoli Monitoring for Tivoli Storage Manager by using IBM
| Installation Manager
| To uninstall Tivoli Monitoring for Tivoli Storage Manager, you can use the wizard,
| the command line in console mode, or silent mode.

| Uninstalling Tivoli Monitoring for Tivoli Storage Manager by

| using the Uninstall wizard
| You can uninstall Tivoli Monitoring for Tivoli Storage Manager by using the
| Uninstall wizard of IBM Installation Manager.

| Before you begin

| Before you uninstall Tivoli Monitoring for Tivoli Storage Manager, you must know
| the DB2 administrator password.

| Restriction: You must uninstall Jazz for Service Management before you uninstall
| Tivoli Monitoring for Tivoli Storage Manager. To uninstall Jazz for Service
| Management, see “Uninstalling Jazz for Service Management” on page 183.

| Procedure
| 1. Open IBM Installation Manager by issuing the following command from a
| command line:
| cd installation_manager/eclipse
| ./IBMIM

| where installation_manager is the IBM Installation Manager installation directory.

| The default installation directory is:
| /opt/IBM/InstallationManager
| 2. Click Uninstall.
| 3. Select IBM Tivoli Monitoring for Tivoli Storage Manager, and click Next.
| 4. Enter the DB2 administrator password, and click Next.
| 5. Enter a selection depending on whether you want to delete or keep the
| historical data, and click Next.
| You can delete the historical data if you no longer need the data in the
| WAREHOUS database.
| 6. Click Uninstall and click Finish.
|

184 IBM Tivoli Storage Manager for AIX: Installation Guide

 Uninstalling Tivoli Monitoring for Tivoli Storage Manager

| Uninstalling Tivoli Monitoring for Tivoli Storage Manager by

| using console mode
| You can uninstall Tivoli Monitoring for Tivoli Storage Manager by using the
| command line in console mode. You must run the uninstallation program of IBM
| Installation Manager from the command line.

| Before you begin

| Before you uninstall Tivoli Monitoring for Tivoli Storage Manager, you must know
| the DB2 administrator password.

| Restriction: You must uninstall Jazz for Service Management before you uninstall
| Tivoli Monitoring for Tivoli Storage Manager. To uninstall Jazz for Service
| Management, see “Uninstalling Jazz for Service Management” on page 183.

| Procedure
| 1. From a command line, go to the following directory:
| installation_manager/eclipse/tools
| where installation_manager is the IBM Installation Manager installation
| directory, for example:
| /opt/IBM/InstallationManager/eclipse/tools
| 2. Start the uninstallation process by issuing the following command:
| ./imcl -c
| 3. Enter 5 to remove the installed software packages.
| 4. Enter N to accept the IBM Tivoli Monitoring for Tivoli Storage Manager
| package group.
| 5. Enter the item number to select the IBM Tivoli Monitoring for Tivoli Storage
| Manager installed package, and enter N for Next.
| 6. Enter 1 for DB2 configuration.
| 7. Enter 1 to type the DB2 administrators password, and enter the DB2
| administrator password, and enter N for Next.
| 8. Enter a selection depending on whether you want to delete or keep the
| historical data.
| You can delete the historical data if you no longer need the data in the
| WAREHOUS database.
| 9. Enter N for Next.
| 10. Enter U for Uninstall, and enter F for Finish.

| Uninstalling Tivoli Monitoring for Tivoli Storage Manager by

| using silent mode
| You can uninstall Tivoli Monitoring for Tivoli Storage Manager in silent mode. You
| must run the uninstallation program of IBM Installation Manager from the
| command line.

| Before you begin

| Before you uninstall Tivoli Monitoring for Tivoli Storage Manager, you must know
| the DB2 administrator password.

Chapter 12. Uninstalling Tivoli Monitoring for Tivoli Storage Manager 185
 Uninstalling Tivoli Monitoring for Tivoli Storage Manager

| The input directory, which is in the directory where the installation package was
| extracted, contains a sample response file for uninstalling Tivoli Monitoring for
| Tivoli Storage Manager. If you installed Tivoli Monitoring for Tivoli Storage
| Manager from a DVD, you can find the input directory on the DVD. You can use
| the uninstall_response_sample.xml.

| Restriction: You must uninstall Jazz for Service Management before you uninstall
| Tivoli Monitoring for Tivoli Storage Manager. To uninstall Jazz for Service
| Management, see “Uninstalling Jazz for Service Management” on page 183.

| Procedure
| 1. Create a response file, or use the uninstall_response_sample.xml sample
| response file.
| 2. Edit the response file to add the DB2 administrator password.
| 3. From a command line, go to the following directory:
| installation_manager/eclipse/tools
| where installation_manager is the IBM Installation Manager installation directory,
| for example:
| /opt/IBM/InstallationManager/eclipse/tools
| 4. Start the uninstallation process by issuing the following command, where
| response_file represents the response file path, including the file name:
| ./imcl -input response_file -silent

| Use the format in the following example:

| ./imcl -input /tmp/input/uninstall_response.xml -silent
|
| Uninstalling monitoring agents
| You can uninstall the Tivoli Monitoring for Tivoli Storage Manager monitoring
| agents if you no longer need them.

| About this task

| If you used the Tivoli Monitoring for Tivoli Storage Manager installation package
| to install the monitoring agent, you can use the uninstallation program of IBM
| Installation Manager to uninstall the monitoring agent. However, if you installed
| the monitoring agent on an existing IBM Tivoli Monitoring server, complete the
| steps in “Uninstalling monitoring agents in an existing IBM Tivoli Monitoring
| environment” on page 188.

| Uninstalling monitoring agents by using IBM Installation

| Manager
| To uninstall the monitoring agents, you can use the wizard, the command line in
| console mode, or silent mode.

186 IBM Tivoli Storage Manager for AIX: Installation Guide

 Uninstalling Tivoli Monitoring for Tivoli Storage Manager

| Uninstalling the monitoring agent by using the wizard

| You can uninstall the monitoring agent by using the IBM Installation Manager
| wizard.

| Procedure
| 1. Open IBM Installation Manager by issuing the following command from a
| command line:
| cd installation_manager/eclipse
| ./IBMIM

| where installation_manager is the IBM Installation Manager installation directory.

| The default installation directory is:
| /opt/IBM/InstallationManager
| 2. Click Uninstall.
| 3. Select IBM Tivoli Monitoring for Tivoli Storage Manager agent only, and
| click Next.
| 4. Click Uninstall and click Finish.

| Uninstalling the monitoring agent by using the console

| You can uninstall the monitoring agent by using the command line. You must run
| the uninstallation program of IBM Installation Manager from the command line.

| Procedure
| 1. From a command line, go to the following directory:
| installation_manager/eclipse/tools
| where installation_manager is the IBM Installation Manager installation directory,
| for example:
| /opt/IBM/InstallationManager/eclipse/tools
| 2. Start the uninstallation process by issuing the following command:
| ./imcl -c
| 3. Enter 5 to remove the installed software packages.
| 4. Enter N to accept the IBM Tivoli Monitoring for Tivoli Storage Manager package
| group.
| 5. Enter 1 for IBM Tivoli Monitoring for Tivoli Storage Manager agent only, and
| enter N for Next.
| 6. Enter N for Next.
| 7. Enter U for Uninstall, and enter F for Finish.

| Uninstalling the monitoring agent by using silent mode

| You can uninstall the monitoring agent in silent mode. You must run the
| uninstallation program of IBM Installation Manager from the command line.

| Before you begin

| The input directory, which is in the directory where the installation package was
| extracted, contains a sample response file for uninstalling the monitoring agent. If
| you installed Tivoli Monitoring for Tivoli Storage Manager from a DVD, you can
| find the input directory on the DVD. You can use the
| uninstall_agent_only_sample.xml file.

Chapter 12. Uninstalling Tivoli Monitoring for Tivoli Storage Manager 187
 Uninstalling Tivoli Monitoring for Tivoli Storage Manager

| Procedure
| 1. Create a response file, or use the uninstall_agent_only_sample.xml sample
| response file.
| 2. From a command line, go to the following directory:
| installation_manager/eclipse/tools
| where installation_manager is the IBM Installation Manager installation directory,
| for example:
| /opt/IBM/InstallationManager/eclipse/tools
| 3. Start the uninstallation process by issuing the following command, where
| response_file represents the response file path, including the file name:
| ./imcl -input response_file -silent

| Use the format in the following example:

| ./imcl -input /tmp/input/uninstall_response.xml -silent

| Uninstalling monitoring agents in an existing IBM Tivoli

| Monitoring environment
| You can uninstall the monitoring agents on existing IBM Tivoli Monitoring servers
| if you no longer need them.

| Uninstalling monitoring agents and application support files

| If you installed Tivoli Monitoring for Tivoli Storage Manager agents by using the
| IBM Tivoli Monitoring installer, you can uninstall the agents by using the
| command-line interface.

| Procedure

| To uninstall Tivoli Monitoring for Tivoli Storage Manager agents, complete the
| following steps:
| 1. From a command line, go to the following directory:
| cd install_dir/bin

| where the install_dir is the IBM Tivoli Monitoring installation directory. The
| default directory is /opt/IBM/ITM.
| 2. Stop all of the Tivoli Storage Manager agent instances by using the
| CandleManage application, or the command-line interface.

| Tip: Always stop processes by issuing the itmcmd commands, or from the
| Manage Tivoli Enterprise Monitoring Services application. Do not kill
| processes by using the operating system.
| Stop the agent by using CandleManage:
| a. Run the CandleManage program by issuing the following
| command:
| ./CandleManage &
| b. Right-click each agent and click Stop.
| Stop the agent instances by using the command-line interface:
| a. Display the agents that are running by issuing the following
| command, and then refer to the output:
| ./cinfo -r
| b. Issue the following command for each agent instance:

188 IBM Tivoli Storage Manager for AIX: Installation Guide

 Uninstalling Tivoli Monitoring for Tivoli Storage Manager

| ./itmcmd agent -o instance_name stop sk

| 3. Issue the following command:
| ./uninstall.sh
| 4. In the list of features, locate an agent to uninstall. Agents are identified by the
| name Reporting Agent for Tivoli Storage Manager. Uninstall an agent by
| entering the feature number of the agent and pressing the Enter key. To
| confirm your choice, enter 1 and press the Enter key. An updated list of
| features is displayed. Repeat this step to uninstall all monitoring agents.
| 5. Exit the window by entering 99 and pressing the Enter key.
| 6. Identify the support files for the monitoring agents. Issue the ./cinfo
| command, for example:
| /opt/IBM/ITM/bin # ./cinfo -i -t sk

| The result is similar to the following list:

| PC APPLICATION SUPPORT DESC PLAT APP VER
|
| sk Monitoring Agent for Tivoli Storage Manager tpd 07.10.00.
| sk Monitoring Agent for Tivoli Storage Manager tps 07.10.00.
| sk Monitoring Agent for Tivoli Storage Manager tpw 07.10.00.
| 7. Uninstall the support files for the monitoring agents by using the
| ./uninstall.sh command. For example, if the entry in the PLAT column is tpd,
| enter the following command to uninstall the corresponding support files:
| /opt/IBM/ITM/bin # ./uninstall.sh sk tpd
| 8. For each support file that you uninstall, confirm the choice by entering 1 and
| pressing the Enter key.
| 9. When you finish the uninstall process, to exit the window, enter 99 and press
| the Enter key.
| 10. Restart any agents that you stopped.

Chapter 12. Uninstalling Tivoli Monitoring for Tivoli Storage Manager 189
Uninstalling Tivoli Monitoring for Tivoli Storage Manager

190 IBM Tivoli Storage Manager for AIX: Installation Guide

|

Part 3. Installing and upgrading the Operations Center

The IBM Tivoli Storage Manager Operations Center is the web-based interface for
managing your storage environment.

Before you begin

Before you install and configure the Operations Center, review the following
information:
v “System requirements for the Operations Center” on page 193
– “Operations Center computer requirements” on page 194
– “Hub and spoke server requirements” on page 194
– “Operating system requirements” on page 198
– “Web browser requirements” on page 198
– “Language requirements” on page 199
| – “Requirements and limitations for Tivoli Storage Manager client management
| services” on page 199
v “Administrator IDs that the Operations Center requires” on page 201
v “IBM Installation Manager” on page 202
v “Installation checklist” on page 202
v “Obtaining the Operations Center installation package” on page 207

About this task

Table 28 lists the methods for installing or uninstalling the Operations Center and
indicates where to find the associated instructions.

For information about upgrading the Operations Center, see Chapter 15,
“Upgrading the Operations Center,” on page 211.
Table 28. Methods for installing or uninstalling the Operations Center
Method Instructions
Graphical wizard v “Installing the Operations Center by using a graphical
wizard” on page 208
v “Uninstalling the Operations Center by using a graphical
wizard” on page 241
Console mode v “Installing the Operations Center in console mode” on page
209
v “Uninstalling the Operations Center in console mode” on
page 241
Silent mode v “Installing the Operations Center in silent mode” on page 210
v “Uninstalling the Operations Center in silent mode” on page
242

© Copyright IBM Corp. 1993, 2014 191

192 IBM Tivoli Storage Manager for AIX: Installation Guide
Chapter 13. Planning to install the Operations Center
Before you install the Operations Center, you must understand the system
requirements, the administrator IDs that the Operations Center requires, and the
information that you must provide to the installation program.

About this task

From the Operations Center, you can manage the following primary aspects of the
storage environment:
v Tivoli Storage Manager servers and clients
v Services such as backup and restore, archive and retrieve, and migrate and recall
v Storage pools and storage devices

The Operations Center includes the following features:

User interface for multiple servers
You can use the Operations Center to manage one or more Tivoli Storage
Manager servers.
In an environment with multiple Tivoli Storage Manager servers, you can
designate one Tivoli Storage Manager server as a hub server and the others
as spoke servers. The hub server can receive alerts and status information
from the spoke servers and present the information in a consolidated view
in the Operations Center.
Alert monitoring
An alert is a notification of a relevant problem on the Tivoli Storage
Manager server and is triggered by a Tivoli Storage Manager server
message. You can define which server messages trigger alerts, and only
those messages are reported as alerts in the Operations Center or in an
email.
This alert monitoring can help you identify and track relevant problems on
the Tivoli Storage Manager server.
Convenient command-line interface
The Operations Center includes a command-line interface for advanced
features and configuration.

System requirements for the Operations Center

Before you install the Operations Center, ensure that your system meets the
minimum requirements.

Use the Operations Center System Requirements Calculator to estimate the system
requirements for running the Operations Center and the hub and spoke servers
that are monitored by the Operations Center.

Requirements that are verified during the installation

Table 29 on page 194 lists the prerequisite requirements that are verified during the
installation and indicates where to find more information about these
requirements.

© Copyright IBM Corp. 1993, 2014 193

Planning to install the Operations Center

Table 29. Requirements that are verified during the installation

Requirement Details
Minimum memory requirement “Operations Center computer requirements”
Operating system requirement “Operating system requirements” on page
198
Host name for the computer where the “Installation checklist” on page 202
Operations Center will be installed
Requirements for the Operations Center “Installation checklist” on page 202
installation directory

Operations Center computer requirements

You can install the Operations Center on the same computer as a Tivoli Storage
Manager server or on a different computer. If you install the Operations Center on
the same computer as a Tivoli Storage Manager server, that computer must meet
the system requirements for both the Operations Center and the Tivoli Storage
Manager server.

Resource requirements

The following resources are required to run the Operations Center:

v One processor core
v 4 GB of memory
v 1 GB of disk space

The hub and spoke servers that are monitored by the Operations Center require
additional resources, as described in “Hub and spoke server requirements.”

Hub and spoke server requirements

When you open the Operations Center for the first time, you must associate the
Operations Center with a Tivoli Storage Manager server that is designated as the
hub server. In a multiple-server environment, you can connect the other servers,
called spoke servers, to the hub server.

The spoke servers send alerts and status information to the hub server. The
Operations Center shows you a consolidated view of alerts and status information
for the hub server and any spoke servers.

If only one Tivoli Storage Manager server is monitored by the Operations Center,
that server is still called a hub server, even though no spoke servers are connected
to it.

Table 30 on page 195 indicates the version of Tivoli Storage Manager server that
must be installed on the hub server and on each spoke server that is managed by
the Operations Center.

194 IBM Tivoli Storage Manager for AIX: Installation Guide

 Planning to install the Operations Center

Table 30. Tivoli Storage Manager server version requirements for hub and spoke servers
Tivoli Storage Manager on the Tivoli Storage Manager on
Operations Center hub server each spoke server
| V7.1.1 V7.1.1 or later V6.3.4 or later

| Tip: Some Operations Center

| function is not available for
| servers that use a version
| earlier than V7.1.1

Number of spoke servers that a hub server can support

The number of spoke servers that a hub server can support depends on the
configuration and on the version of Tivoli Storage Manager on each spoke server.
However, a general guideline is that a hub server can support 10 - 20 V6.3.4 spoke
servers but can support more V7.1 spoke servers.

Tips for designing the hub and spoke server configuration

In designing the hub and spoke configuration, especially consider the resource
requirements for status monitoring. Also, consider how you want to group hub
and spoke servers and whether you want to use multiple hub servers.

Use the Operations Center System Requirements Calculator to estimate the system
requirements for running the Operations Center and the hub and spoke servers
that are monitored by the Operations Center.

Primary factors that affect performance

The following factors have the most significant impact on the performance of the
Operations Center:
v The processor and memory on the computer where the Operations Center is
installed
v The system resources of the hub and spoke servers, including the disk system
that is in use for the hub server database
v The number of Tivoli Storage Manager client nodes and virtual machine file
spaces that are managed by the hub and spoke servers
v The frequency at which data is refreshed in the Operations Center

For information about optimizing performance, see the information about tuning
the Operations Center in Tivoli Storage Manager Optimizing Performance.

How to group hub and spoke servers

Consider grouping hub and spoke servers by geographic location. For example,
managing the servers within the same data center can help prevent issues that are
caused by firewalls or by inadequate network bandwidth between different
locations. If necessary, you can further divide servers according to one or more of
the following characteristics:
v The administrator who manages the servers
v The organizational entity that funds the servers
v Server operating system
v The language in which the servers run

Chapter 13. Planning to install the Operations Center 195

 Planning to install the Operations Center

Tip: If the hub and spoke servers are not running in the same language, you
might see corrupted text in the Operations Center.

| How to group hub and spoke servers in an enterprise configuration

| In an enterprise configuration, a network of Tivoli Storage Manager servers are

| managed as a group. Changes that are made on the configuration manager can be
| distributed automatically to one or more managed servers in the network.

| The Operations Center normally registers and maintains a dedicated administrator

| ID on the hub and spoke servers. This monitoring administrator must always have
| the same password on all the servers.

| If you use an enterprise configuration, you can improve the process by which the
| administrator credentials are synchronized on spoke servers. To improve the
| performance and efficiency of maintaining the monitoring administrator ID,
| complete the following steps:
| 1. Designate the configuration manager server as the Operations Center hub
| server. During the hub server configuration, a monitoring administrator ID
| named IBM-OC-hub_server_name is registered.
| 2. On the hub server, add the monitoring administrator ID to a new or existing
| enterprise configuration profile. Issue the NOTIFY SUBSCRIBERS command to
| distribute the profile to the managed servers.
| 3. Add one or more of the managed servers as Operations Center spoke servers.

| The Operations Center detects this configuration and allows the configuration
| manager to distribute and update the monitoring administrator ID on the spoke
| servers.

When to use multiple hub servers

If you have more than 10 - 20 V6.3.4 spoke servers, or if resource limitations

require the environment to be partitioned, you can configure multiple hub servers,
and connect a subset of the spoke servers to each hub server.

Restrictions:
v A single server cannot be both a hub server and a spoke server.
v Each spoke server can be assigned to only one hub server.
v Each hub server requires a separate instance of the Operations Center, each of
which has a separate web address.

Tips for choosing a hub server

For the hub server, you must choose a Tivoli Storage Manager server that has
adequate resources and is located for minimal roundtrip network latency.

For more information about server resource usage and about the effect of the
network on performance, see the information about tuning Operations Center
performance in Tivoli Storage Manager Optimizing Performance.

Attention: Do not use the same Tivoli Storage Manager server as the hub server
for multiple Operations Centers.

Use the following guidelines in deciding which server to designate as the hub
server:

196 IBM Tivoli Storage Manager for AIX: Installation Guide

 Planning to install the Operations Center

Choose a lightly loaded server

Consider a Tivoli Storage Manager server that has a light load for Tivoli
Storage Manager operations such as client backup and archive. A lightly
loaded server is also a good choice as the host system for the Operations
Center.
Ensure that the server has the resources to handle both its typical Tivoli
Storage Manager server workload and the estimated workload for acting as
the hub server.
Locate the server for minimal roundtrip network latency
Locate the hub server so that the network connection between the hub
server and the spoke servers has a roundtrip latency that is no greater than
5 ms. This latency can typically be achieved when the servers are on the
same local area network (LAN).
Networks that are poorly tuned, are heavily used by other applications, or
have roundtrip latency much higher than 5 ms can degrade
communications between the hub and spoke servers. For example,
roundtrip latencies of 50 ms or higher can result in communication
timeouts that cause spoke servers to disconnect or reconnect to the
Operations Center. Such high latencies might be experienced in
long-distance, wide area network (WAN) communications.
If spoke servers are a long distance from the hub server and experience
frequent disconnects in the Operations Center, you can increase the value
of the ADMINCOMMTIMEOUT option on each server to reduce the problem.
Verify that the hub server meets the resource requirements for status monitoring
Status monitoring requires extra resources on each server on which it is
enabled. The resources that are required depend primarily on the number
of clients that are managed by the hub and spoke servers. Fewer resources
are used on a hub server with a V7.1 spoke server than on a hub server
with a V6.3.4 spoke server.
Verify that the hub server meets the resource requirements for processor
usage, database space, archive log space, and I/O operations per second
(IOPS) capacity.
A hub server with high IOPS capacity can handle a larger amount of
incoming status data from spoke servers. Use of the following storage
devices for the hub server database can help meet this capacity:
v An enterprise-level solid-state drive (SSD)
v An external SAN disk storage device with multiple volumes or multiple
spindles under each volume
In an environment with fewer than 1000 clients, consider establishing a
baseline capacity of 1000 IOPS for the hub server database if the hub
server manages any spoke servers.
Determine whether your environment requires multiple hub servers
If more than 10,000 - 20,000 client nodes and virtual machine file spaces
are managed by one set of hub and spoke servers, the resource
requirements might exceed what the hub server has available, especially if
the spoke servers are Tivoli Storage Manager V6.3.4 servers. Consider
designating a second server as a hub server and moving spoke servers to
the new hub server to balance the load.

Chapter 13. Planning to install the Operations Center 197

 Planning to install the Operations Center

Operating system requirements

The Operations Center is available for AIX, Linux, and Windows systems.

You can run the Operations Center on the following systems:

v AIX systems:
– IBM AIX V6.1 (64 bit) TL 7 and SP 6
– IBM AIX V7.1 (64 bit) TL 1 and SP 6

You cannot run the Operations Center on HP-UX or Oracle Solaris systems.
However, you can use the Operations Center to manage Tivoli Storage Manager
V6.3.4 or later servers that run on any supported server operating system.

The operating systems on which the server can run are not limited to the operating
systems on which the Operations Center can run.

| For the most up-to-date requirements information, see Tivoli Storage Manager
| Operations Center Software and Hardware Requirements.

Web browser requirements

The Operations Center can run in Apple, Google, Microsoft, and Mozilla web
browsers.

For optimal viewing of the Operations Center in the web browser, ensure that the
screen resolution for the system is set to a minimum of 1024 X 768 pixels.

For optimal performance, use a web browser that has good JavaScript
performance, and enable browser caching.

The Operations Center can run in the following web browsers:

| v Apple Safari on the iPad
| v Google Chrome
| v Microsoft Internet Explorer 10 and 11
| v Mozilla Firefox ESR 17 or later

| To run the Operations Center in compliance with the National Institute of

| Standards and Technology (NIST) Special Publications (SP) 800-131A
| recommendation, communication between the Operations Center and the web
| browser must be secured by using the Transport Layer Security (TLS) 1.2 protocol.
| During installation, you specify whether SP 800-131A compliance is required and
| the level of compliance. If strict SP 800-131A compliance is specified during
| installation, the web browser must support TLS 1.2, and TLS 1.2 must be enabled.

| The following web browser versions are the earliest versions that support TLS 1.2:
| v Apple Safari on the iPad running iOS 5
| v Google Chrome 30
| v Microsoft Internet Explorer 10
| v Mozilla Firefox ESR 24
| Because the web browser might support multiple versions of TLS, make sure TLS
| 1.2 is enabled.

| The web browser displays an SSL error if strict SP 800-131A compliance is specified
| during installation, and the web browser does not meet the preceding

198 IBM Tivoli Storage Manager for AIX: Installation Guide

 Planning to install the Operations Center

| requirements.

Language requirements
By default, the Operations Center uses the language that the web browser uses.
However, the installation process uses the language that the operating system uses.
Verify that the web browser and the operating system are set to the language that
you require.
Table 31. Operations Center language values that you can use on AIX systems
Language Language option value
Chinese, Simplified zh_CN
Chinese, Simplified (UTF-8) ZH_CN
Chinese, Traditional (Big5) Zh_TW
Chinese, Traditional (UTF-8) ZH_TW
Chinese, Traditional (euc_tw) zh_TW
English en_US
English (UTF-8) EN_US
French fr_FR
French (UTF-8) FR_FR
German de_DE
German (UTF-8) DE_DE
Italian it_IT
Italian (UTF-8) IT_IT
Japanese (EUC) ja_JP
Japanese (PC) Ja_JP
Japanese (UTF-8) JA_JP
Korean ko_KR
Korean (UTF-8) KO_KR
Portuguese, Brazilian pt_BR
Portuguese, Brazilian (UTF-8) PT_BR
Russian ru_RU
Russian (UTF-8) RU_RU
Spanish es_ES
Spanish (UTF-8) ES_ES

| Requirements and limitations for Tivoli Storage Manager client

| management services
| Tivoli Storage Manager client management services is a component that you install
| on Tivoli Storage Manager backup-archive clients to collect diagnostic information
| such as client log files. Before you install the client management service on your
| system, you must understand the requirements and limitations.

| In the documentation for the client management service, client system is the system
| where the backup-archive client is installed.

Chapter 13. Planning to install the Operations Center 199

 Planning to install the Operations Center

| Requirements for the client management service

| Verify the following requirements before you install the client management service:
| v To remotely access the client, the Operations Center administrator must have
| system authority or one of the following client authority levels:
| – Policy authority
| – Client owner authority
| – Client node access authority
| v Ensure that the client system meets the following requirements:
| – The backup-archive client must be at Tivoli Storage Manager Version 6 or
| Version 7.
| – The client management service can be installed only on client systems that
| run on Linux or Windows operating systems:
| - Linux x86 64-bit operating systems that are supported for the
| backup-archive client
| - Windows 32-bit and 64-bit operating systems that are supported for the
| backup-archive client
| – The SSL security protocol is required for transmission of data between the
| client management service and Operations Center. Basic authentication is
| provided and data and authentication information are encrypted through the
| SSL channel. SSL is automatically installed along with the necessary SSL
| certificates when you install the client management service.
| v On Linux client systems, you must have root user authority to install the client
| management service.
| v For client systems that can have multiple client nodes, such as Linux client
| systems, ensure that each node name is unique on the client system.

| Tip: After you install the client management service, you do not have to install
| it again because the service can discover multiple client options files.

| For the most up-to-date system requirements for the client management service,
| see http://www.ibm.com/support/docview.wss?uid=swg21243309.

| Limitations of the client management service

| The client management service provides basic services for collecting diagnostic
| information from backup-archive clients. The following limitations exist for the
| client management service:
| v You can install the client management service only on backup-archive clients,
| and not on other Tivoli Storage Manager client components and products.
| v If the backup-archive clients are protected by a firewall, ensure that there is
| firewall connectivity between the Operations Center and the backup-archive
| client through the configured port for the client management service. The default
| port is 9028, but it can be changed.
| v The client management service scans all client log files to locate entries for the
| previous 72-hour period.
| v The Diagnosis page in the Operations Center provides basic troubleshooting
| information for backup-archive clients. However, for some backup issues, you
| might have to access the client system and obtain further diagnostic information.
| v If the combined size of the client error log files and schedule log files on a client
| system is more than 500 MB, delays can occur in sending log records to the

200 IBM Tivoli Storage Manager for AIX: Installation Guide

 Planning to install the Operations Center

| Operations Center. You can control the size of the log files by enabling log file
| pruning or wrapping by specifying the errorlogretention or errorlogmax client
| option.
| v If you use the same client node name to connect to multiple Tivoli Storage
| Manager servers that are installed on the same server hardware, you can view
| log files for only one of the client nodes.
|
Administrator IDs that the Operations Center requires
An administrator must have a valid ID and password on the hub server to log in
to the Operations Center. An administrator ID is also assigned to the Operations
Center so that the Operations Center can monitor servers.

The Operations Center requires the following Tivoli Storage Manager administrator
IDs:
Administrator IDs that are registered on the hub server
Any administrator ID that is registered on the hub server can be used to
log in to the Operations Center. The authority level of the ID determines
which tasks can be completed. You can create new administrator IDs by
using the REGISTER ADMIN command.

Restriction: To use an administrator ID in a multiple-server configuration,

the ID must be registered on the hub and spoke servers with the same
password and authority level.

To manage authentication for these servers, consider using one of the

following methods:
v A Lightweight Directory Access Protocol (LDAP) server
v The Tivoli Storage Manager enterprise configuration functions to
automatically distribute changes to the administrator definitions.
For more information about the enterprise configuration functions, see
the information about managing a network of Tivoli Storage Manager
servers in the Administrator's Guide.
Monitoring administrator ID
When you initially configure the hub server, an administrator ID named
IBM-OC-server_name is registered with system authority on the hub server
and is associated with the initial password that you specify. This ID, which
is sometimes called the monitoring administrator, is intended for use only by
the Operations Center.
Do not delete, lock, or modify this ID. The same administrator ID with the
same password is registered on the spoke servers that you add. The
password is automatically changed on the hub and spoke servers every 90
days. You do not need to use or manage this password.

| Restriction: The Operations Center maintains the monitoring

| administrator ID and password on spoke servers unless you use an
| enterprise configuration to manage these credentials. For more information
| about using an enterprise configuration to manage the credentials, see
| “Tips for designing the hub and spoke server configuration” on page 195.

Chapter 13. Planning to install the Operations Center 201

Planning to install the Operations Center

IBM Installation Manager

The Operations Center uses IBM Installation Manager, which is an installation
program that can use remote or local software repositories to install or update
many IBM products.

If the required version of IBM Installation Manager is not already installed, it is

automatically installed or upgraded when you install the Operations Center. It
must remain installed on the system so that the Operations Center can be updated
or uninstalled later as needed.

The following list contains explanations of some terms that are used in IBM
Installation Manager:
Offering
An installable unit of a software product.
The Operations Center offering contains all of the media that IBM
Installation Manager requires to install the Operations Center.
Package
The group of software components that are required to install an offering.
The Operations Center package contains the following components:
v IBM Installation Manager installation program
v Operations Center offering
Package group
A set of packages that share a common parent directory.
The default package group for the Operations Center package is IBM
Tivoli Storage Manager.
Repository
A remote or local storage area for data and other application resources.
The Operations Center package is stored in a repository on IBM Fix
Central.
Shared resources directory
A directory that contains software files or plug-ins that are shared by
packages.
IBM Installation Manager stores installation-related files in the shared
resources directory, including files that are used for rolling back to a
previous version of the Operations Center.

Installation checklist
Before you install the Operations Center, you must verify certain information, such
as the installation credentials, and you must determine the input to provide to IBM
Installation Manager for the installation.

The following checklist highlights the information that you must verify or
determine before you install the Operations Center, and Table 32 on page 203
describes the details of this information:
__ Verify the host name for the computer where the Operations Center will be
installed.
__ Verify the installation credentials.

202 IBM Tivoli Storage Manager for AIX: Installation Guide

 Planning to install the Operations Center

__ Determine the Operations Center installation directory, if you do not want to

accept the default path.
__ Determine the IBM Installation Manager installation directory, if you do not
want to accept the default path.
__ Determine the port number to be used by the Operations Center web server,
if you do not want to accept the default port number.
__ Determine the password for secure communications.
| __ Determine whether secure communications must comply with the National
| Institute of Standards and Technology (NIST) Special Publications (SP)
| 800-131A recommendation.
Table 32. Information to verify or determine before you install the Operations Center
Information Details
Host name for the computer The host name must meet the following criteria:
where the Operations Center v It must not contain double-byte character set (DBCS) characters or the underscore
will be installed character (_).
v Although the host name can contain the hyphen character (-), it cannot have a
hyphen as the last character in the name.
Installation credentials To install the Operations Center, you must use the following user account:
v root
Operations Center installation The Operations Center is installed in the ui subdirectory of the installation directory.
directory
The following path is the default path for the Operations Center installation
directory:
v /opt/tivoli/tsm
For example, if you use this default path, the Operations Center is installed in the
following directory:
/opt/tivoli/tsm/ui

The installation directory path must meet the following criteria:

v The path must contain no more than 128 characters.
v The path must include only ASCII characters.
v The path cannot include non-displayable control characters.
v The path cannot include any of the following characters:
% | < > ’ " $ & ; *

IBM Installation Manager The following path is the default path for the IBM Installation Manager installation
installation directory directory:
v /opt/IBM/InstallationManager
Port number that is used by The value for the secure (https) port number must meet the following criteria:
the Operations Center web v The number must be an integer in the range 1024 - 65535.
server
v The number cannot be in use or allocated to other programs.

If you do not specify a port number, the default value is 11090.

Tip: If you later do not remember the port number that you specified, refer to the
following file, where installation_dir represents the directory where the
Operations Center is installed:
v installation_dir/ui/Liberty/usr/servers/guiServer/bootstrap.properties

The bootstrap.properties file contains the Tivoli Storage Manager server connection
information.

Chapter 13. Planning to install the Operations Center 203

Planning to install the Operations Center

Table 32. Information to verify or determine before you install the Operations Center (continued)
Information Details
Password for secure The Operations Center uses Hypertext Transfer Protocol Secure (HTTPS) to
communications communicate with web browsers. You can optionally use the Secure Sockets Layer
(SSL) protocol to secure communications between the Operations Center and the hub
server, and between Tivoli Storage Manager servers.

The truststore file of the Operations Center contains the SSL certificate that the
Operations Center uses for HTTPS communication with web browsers. During
installation of the Operations Center, you create a password for the truststore file.

Tip: If you later choose to set up SSL communication between the Operations
Center and the hub server, you must use the same password to add the SSL
certificate of the hub server to the truststore file.

The password for the truststore file must meet the following criteria:
v The password must contain a minimum of 6 characters and a maximum of 64
characters.
v The password must contain at least the following characters:
– One uppercase letter (A – Z)
– One lowercase letter (a – z)
– One digit (0 – 9)
– Two of the following non-alphanumeric characters:
~ ! @ # $ % ^ & * _ - + = ` |
( ) { } [ ] : ; < > , . ? /

204 IBM Tivoli Storage Manager for AIX: Installation Guide

 Planning to install the Operations Center

Table 32. Information to verify or determine before you install the Operations Center (continued)
Information Details
| NIST SP800-131A compliance When you install the Operations Center, you can specify whether NIST SP800-131A
| mode compliance is required, and the level of compliance. Before you install the
| Operations Center, determine if you want strict SP800-131A compliance, transitional
| SP800-131A compliance, or if you do not need to comply with the recommendation.

| If you enable SP800-131A compliance, stronger cryptographic keys and algorithms

| are used for HTTPS communication between the Operations Center and the web
| browsers. There are two compliance modes: transition and strict. Both modes enable
| the web server to secure HTTPS communication by using the Transport Layer
| Security (TLS) 1.2 protocol. In transition mode, however, TLS 1.0 or TLS 1.1 are
| allowed if the web browser is not enabled for TLS 1.2. In strict mode, full
| SP800-131A compliance is enforced, and the web browser must have TLS 1.2 enabled
| to run the Operations Center.

| If you do not enable SP800-131A compliance, HTTPS communication is secured by

| less-complex cryptography. However, processor usage and network latency might be
| reduced.

| Requirement: If you specify strict SP800-131A compliance, the web browser must
| support TLS 1.2, and TLS 1.2 must be enabled.

| Restrictions:
| v You cannot change the SP800-131A compliance mode after installation. To change
| this setting you must uninstall and reinstall the Operations Center.
| v This installation option is available only when you use the Install function of the
| IBM Installation Manager. This option is not available when you use the Update
| function. If you have an earlier version of the Operations Center installed and you
| want to enable SP800-131A compliance, you must uninstall and reinstall the
| Operations Center.

| Remember: The SP800-131A compliance option applies only to the Operations

| Center communication with web browsers. To fully enable SP800-131A compliance,
| you must configure Tivoli Storage Manager components in your environment
| individually. To secure communications between the Operations Center and the hub
| server, you can add the SSL certificate of the hub server to the truststore file of the
| Operations Center. For SP800-131A compliance, the cert256.arm certificate must be
| the default certificate on the hub server, you must copy this certificate to the
| truststore file of the Operations Center.

Related tasks:
“Configuring for SSL communication” on page 218
“Resetting the password for the Operations Center truststore file” on page 223

Chapter 13. Planning to install the Operations Center 205

Planning to install the Operations Center

206 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 14. Installing the Operations Center
You can install the Operations Center by using any of the following methods: a
graphical wizard, the command line in console mode, or silent mode.

Before you begin

You cannot configure the Operations Center until you install, configure, and start
the Tivoli Storage Manager server. Therefore, before you install the Operations
Center, install the appropriate Tivoli Storage Manager server package, according to
the server version requirements in “Hub and spoke server requirements” on page
194.

You can install the Operations Center on a computer with the Tivoli Storage
Manager server or on a separate computer.

Obtaining the Operations Center installation package

You can obtain the installation package from the product DVD or from an IBM
download site such as IBM Passport Advantage or IBM Fix Central.

About this task

If you obtain the package from the product DVD, ensure that the installation files
are visible on the DVD drive.

If you obtain the package from an IBM download site, you must extract the
installation files.

Procedure

Use the following procedure to extract the Operations Center installation files:
v On AIX systems:
1. Download the following package file to the directory of your choice:
7.1.1.000-TIV-TSMOC-AIX.bin
2. Ensure that you have executable permission for the package file.
If necessary, change the file permissions by issuing the following command:
chmod a+x 7.1.1.000-TIV-TSMOC-AIX.bin
3. Issue the following command to extract the installation files:
./7.1.1.000-TIV-TSMOC-AIX.bin
The self-extracting package file is extracted to the directory.

© Copyright IBM Corp. 1993, 2014 207

Installing the Operations Center

Installing the Operations Center by using a graphical wizard

You can install or update the Operations Center by using the graphical wizard of
IBM Installation Manager.

Before you begin

If the following RPM files are not installed on the computer, install them. For
instructions, see “Installing RPM files for the graphical wizard” on page 209.
atk-1.12.3-2.aix5.2.ppc.rpm
cairo-1.8.8-1.aix5.2.ppc.rpm
expat-2.0.1-1.aix5.2.ppc.rpm
fontconfig-2.4.2-1.aix5.2.ppc.rpm
freetype2-2.3.9-1.aix5.2.ppc.rpm
gettext-0.10.40-6.aix5.1.ppc.rpm
glib2-2.12.4-2.aix5.2.ppc.rpm
gtk2-2.10.6-4.aix5.2.ppc.rpm
libjpeg-6b-6.aix5.1.ppc.rpm
libpng-1.2.32-2.aix5.2.ppc.rpm
libtiff-3.8.2-1.aix5.2.ppc.rpm
pango-1.14.5-4.aix5.2.ppc.rpm
pixman-0.12.0-3.aix5.2.ppc.rpm
xcursor-1.1.7-3.aix5.2.ppc.rpm
xft-2.1.6-5.aix5.1.ppc.rpm
xrender-0.9.1-3.aix5.2.ppc.rpm
zlib-1.2.3-3.aix5.1.ppc.rpm

Procedure
1. From the directory where the Operations Center installation package file is
extracted, issue the following command:
./install.sh
2. Follow the wizard instructions to install the IBM Installation Manager and
Operations Center packages.
The following message might be displayed, and the installation wizard might
be slow, if your locale uses UTF-8 encoding:
Cannot create font set

If the message is displayed, take one of the following actions:

v Change to a locale that does not use UTF-8 encoding. For language-option
values that do not use UTF-8 encoding, see “Language requirements” on
page 199.
v Install the Operations Center by using the command line in console mode.
v Install the Operations Center in silent mode.

What to do next

See “Configuring the Operations Center” on page 213.

208 IBM Tivoli Storage Manager for AIX: Installation Guide

 Installing the Operations Center

Installing RPM files for the graphical wizard

Before you can use the graphical wizard of IBM Installation Manager to install the
Operations Center, certain RPM files must be installed.

About this task

If the RPM files that are listed in “Installing the Operations Center by using a
graphical wizard” on page 208 are not installed, you must download and install
the files.

Procedure
1. Ensure that there is at least 150 MB of free space in the /opt file system.
2. Choose one of the following options:
v If you are installing the Operations Center from the product DVD, take the
following actions:
a. In the base directory of the DVD, change to the gtk directory.
b. From the gtk directory, copy the download-prerequisites.sh file to a
location where you can download the RPM files.
v If you obtained the Operations Center installation package from an IBM
download site such as IBM Passport Advantage or IBM Fix Central, take the
following action:
In the directory where the Operations Center installation package file is
extracted, change to the gtk directory.
3. To automatically download the RPM files to the current directory from the IBM
AIX Toolbox for Linux Applications website, issue the following command:
download-prerequisites.sh
4. Install the files by issuing the following command from the directory that
contains the files:
rpm -Uvh *.rpm
If a message indicates that one of the files is already installed on the system,
take one of the following actions:
v Issue the following command:
rpm -Uvh --force *.rpm
v Move the earlier versions of the files to a different directory, and issue the
rpm command again, as shown in the following example:
mkdir already-installed
mv gettext*.rpm already-installed
rpm -Uvh *.rpm

Installing the Operations Center in console mode

You can install or update the Operations Center by using the command line in
console mode.

Procedure
1. From the directory where the installation package file is extracted, run the
following program:
./install.sh -c
2. Follow the console instructions to install the Installation Manager and
Operations Center packages.

Chapter 14. Installing the Operations Center 209

Installing the Operations Center

What to do next

See “Configuring the Operations Center” on page 213.

Installing the Operations Center in silent mode

You can install or update the Operations Center in silent mode. In silent mode, the
installation does not send messages to a console but instead stores messages and
errors in log files. A silent installation can use response files for data input.

Before you begin

The input directory, which is in the directory where the installation package is
extracted, contains the following sample response files for installing, updating, and
uninstalling the Operations Center:
v install_response_sample.xml
v update_response_sample.xml
v uninstall_response_sample.xml

You can use these sample files as they are, with the default values, or you can
customize them.

Procedure
1. Create a response file, or use one of the following default response files:
v install_response_sample.xml
v update_response_sample.xml
If you use a default response file, update the following line of the file to create
a password for the truststore file of the Operations Center, where mypassword
represents the password:
<data key=’user.SSL_PASSWORD’ value=’mypassword’/>

For more information about this password, see Installation checklist.

To generate a response file as part of a console-mode installation, complete the
selection of the console-mode installation options. Then, in the Summary panel,
enter G to generate the response file according to the previously selected
options.
2. From the directory where the installation package file is extracted, issue the
following command, where response_file represents the response file path,
including the file name:
v ./install.sh -s -input response_file -acceptLicense

What to do next

See “Configuring the Operations Center” on page 213.

210 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 15. Upgrading the Operations Center
You can upgrade the Operations Center by using any of the following methods: a
graphical wizard, the command line in console mode, or silent mode.

Before you begin

Before you upgrade the Operations Center, review the system requirements and
the installation checklist. The new version of the Operations Center might have
more or different requirements and considerations than the version you are
currently using.

Restriction: During installation of the Operations Center, you can specify whether
NIST SP800-131A compliance is required. This installation option is not available
during a regular upgrade. If you want to use the TLS 1.2 protocol to secure
communication between the Operations Center and web browsers, you must
uninstall and then reinstall the Operations Center.

About this task

The instructions for upgrading the Operations Center are the same as the
instructions for installing the Operations Center, with the following exceptions:
v You use the Update function of IBM Installation Manager rather than the Install
function.

Tip: In IBM Installation Manager, the term update means to discover and install
updates and fixes to installed software packages. In this context, update and
upgrade are synonymous.
v If you are upgrading the Operations Center in silent mode, you can skip the
step of creating a password for the truststore file.

© Copyright IBM Corp. 1993, 2014 211

Upgrading the Operations Center

212 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 16. Getting started with the Operations Center
Before you can use the Operations Center to manage your storage environment,
you must configure it.

About this task

After you install the Operations Center, complete the following basic configuration
steps:
1. Designate the hub server.
2. Add any spoke servers.
3. Optionally, configure email alerts on the hub and spoke servers.

Figure 4 illustrates an Operations Center configuration.

Spoke server

Hub server
Spoke server

Operations Center
(on hub server computer
or separate computer)
Spoke server

Spoke server

Figure 4. Example of an Operations Center configuration with the hub and spoke servers

Configuring the Operations Center

When you open the Operations Center for the first time, you must configure it to
manage your storage environment. You must associate the Operations Center with
a Tivoli Storage Manager server that is designated as the hub server. You can then
connect additional Tivoli Storage Manager servers as spoke servers.

© Copyright IBM Corp. 1993, 2014 213

 Getting started with the Operations Center

Designating the hub server

When you connect to the Operations Center for the first time, you must designate
which Tivoli Storage Manager server is the hub server.

Procedure

In a web browser, enter the following address, where hostname represents the name
of the computer where the Operations Center is installed, and secure_port
represents the port number that the Operations Center uses for HTTPS
communication on that computer:
https://hostname:secure_port/oc

Tips:
| v The URL is case-sensitive. For example, ensure that you type “oc” in lowercase
| as indicated.
| v For more information about the port number, see the Installation checklist.
| v If you are connecting to the Operations Center for the first time, you must
| provide the following information:
| – Connection information for the Tivoli Storage Manager server that you want
| to designate as a hub server
| – Login credentials for an administrator ID that is defined for that Tivoli
| Storage Manager server
| v If the event-record retention period of the Tivoli Storage Manager server is less
| than 14 days, the period is automatically reset to 14 days if you configure the
| server as a hub server.

What to do next

If you have multiple Tivoli Storage Manager servers in your environment, add the
other Tivoli Storage Manager servers as spoke servers to the hub server.

Attention: Do not change the name of a Tivoli Storage Manager server after it is
configured as a hub or spoke server.
Related concepts:
“Hub and spoke server requirements” on page 194
“Administrator IDs that the Operations Center requires” on page 201

Adding a spoke server

After you configure the hub server for the Operations Center, you can add one or
more spoke servers to the hub server.

Procedure
1. In the Operations Center menu bar, click Servers. The Servers page opens.
In the table on the Servers page, a server might have a status of
“Unmonitored.” This status means that although an administrator defined this
server to the hub server by using the DEFINE SERVER command, the server is
not yet configured as a spoke server.
2. Complete one of the following steps:
v Click the server to highlight it, and in the table menu bar, click Monitor
Spoke.

214 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

v If the server that you want to add is not shown in the table, click + Spoke in
the table menu bar.
3. Provide the necessary information, and complete the steps in the spoke
configuration wizard.

Tip: If the event-record retention period of the Tivoli Storage Manager server is
less than 14 days, the period is automatically reset to 14 days if you configure
the server as a spoke server.

| Sending email alerts to administrators

| An alert is a notification of a relevant problem on the Tivoli Storage Manager
| server and is triggered by a Tivoli Storage Manager server message. Alerts can be
| shown in the Operations Center and can be sent from the server to administrators
| by email.

| Before you begin

| Before you configure email notification for administrators about alerts, ensure that
| the following requirements are met:
| v An SMTP server is required to send and receive alerts by email, and the Tivoli
| Storage Manager server that sends the alerts by email must have access to the
| SMTP server.

| Tip: If the Operations Center is installed on a separate computer, that computer

| does not need access to the SMTP server.
| v An administrator must have system privilege to configure email notification.

| About this task

| An email notification is sent only for the first occurrence of an alert. Also, if an
| alert is generated before you configure email notification, no email notification is
| sent for that alert.

| You can configure email notification in the following ways:

| v Send notification for individual alerts
| v Send alert summaries

| An alert summary contains information about current alerts. The summary

| includes the total number of alerts, the total number of active and inactive alerts,
| the oldest alert, the newest alert, and the most frequently occurring alert.

| You can specify a maximum of three administrators to receive alert summaries by

| email. Alert summaries are sent approximately every hour.

| Procedure

| To configure email notification for administrators about alerts, complete the

| following steps on each hub and spoke server from which you want to receive
| email alerts:
| 1. To verify that alert monitoring is turned on, issue the following command:
| QUERY MONITORSETTINGS
| 2. If the command output indicates that alert monitoring is turned off, issue the
| following command. Otherwise, proceed to the next step.

Chapter 16. Getting started with the Operations Center 215

 Getting started with the Operations Center

| SET ALERTMONITOR ON
| 3. To enable the sending of email notification, issue the following command:
| SET ALERTEMAIL ON
| 4. To define the SMTP server that is used to send email notification, issue the
| following command:
| SET ALERTEMAILSMTPHOST host_name
| 5. To specify the port number for the SMTP server, issue the following command:
| SET ALERTEMAILSMTPPORT port_number
| The default port number is 25.
| 6. To specify the email address of the sender of the alerts, issue the following
| command:
| SET ALERTEMAILFROMADDR email_address
| 7. For each administrator ID that must receive email notification, issue one of the
| following commands to activate email notification and to specify the email
| address:
| REGISTER ADMIN admin_name ALERT=YES EMAILADDRESS=email_address
| UPDATE ADMIN admin_name ALERT=YES EMAILADDRESS=email_address
| 8. Choose either, or both, of the following options, and specify the administrator
| IDs to receive email notification:
| v Send notification for individual alerts
| To specify or update the administrator IDs to receive email notification for an
| individual alert, issue one of the following commands:
| DEFINE ALERTTRIGGER message_number ADmin=admin_name1,admin_name2
| UPDATE ALERTTRIGGER message_number ADDadmin=admin_name3 DELadmin=admin_name1

| Tip: From the Configure Alerts page of the Operations Center, you can select
| the administrators who will receive email notification.
| v Send alert summaries
| To specify or update the administrator IDs to receive alert summaries by
| email, issue the following command:
| SET ALERTSUMMARYTOADMINS admin_name1,admin_name2,admin_name3
| If you want to receive alert summaries but do not want to receive notification
| about individual alerts, complete the following steps:
| a. Suspend notification about individual alerts, as described in “Suspending
| email alerts temporarily” on page 217.
| b. Ensure that the respective administrator ID is listed in the following
| command:
| SET ALERTSUMMARYTOADMINS admin_name1,admin_name2,admin_name3

| Sending email alerts to multiple administrators

| The following example illustrates the commands that cause any alerts for message
| ANR1075E to be sent in an email to the administrators myadmin, djadmin, and
| csadmin:
| SET ALERTMONITOR ON
| SET ALERTEMAIL ON
| SET ALERTEMAILSMTPHOST mymailserver.domain.com
| SET ALERTEMAILSMTPPORT 450
| SET ALERTEMAILFROMADDR srvadmin@mydomain.com
| UPDATE ADMIN myadmin ALERT=YES EMAILADDRESS=myaddr@anycompany.com

216 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

| UPDATE ADMIN djadmin ALERT=YES EMAILADDRESS=djaddr@anycompany.com

| UPDATE ADMIN csadmin ALERT=YES EMAILADDRESS=csaddr@anycompany.com
| DEFINE ALERTTRIGGER anr0175e ADMIN=myadmin,djadmin,csadmin

| Suspending email alerts temporarily

| In certain situations, you might want to suspend email alerts temporarily. For
| example, you might want to receive alert summaries but suspend notification
| about individual alerts, or you might want to suspend email alerts when an
| administrator is on vacation.

| Before you begin

| Configure email notification for administrators, as described in “Sending email

| alerts to administrators” on page 215.

| Procedure

| Suspend email notification for individual alerts or for alert summaries.

| v Suspend notification about individual alerts
| Use either of the following methods:
| UPDATE ADMIN command
| To turn off email notification for the administrator, issue the following
| command:
| UPDATE ADMIN admin_name ALERT=NO

| To turn on email notification again later, issue the following command:

| UPDATE ADMIN admin_name ALERT=YES
| UPDATE ALERTTRIGGER command
| To prevent a specific alert from being sent to an administrator, issue the
| following command:
| UPDATE ALERTTRIGGER message_number DELADMIN=admin_name

| To start sending that alert to the administrator again, issue the following
| command:
| UPDATE ALERTTRIGGER message_number ADDADMIN=admin_name
| v Suspend notification about alert summaries
| To prevent alert summaries from being sent to an administrator, remove the
| administrator ID from the list in the following command:
| SET ALERTSUMMARYTOADMINS admin_name1,admin_name2,admin_name3
| If an administrator ID is listed in the preceding command, the administrator
| receives alert summaries by email, even if notification about individual alerts is
| suspended for the respective administrator ID.
|

Chapter 16. Getting started with the Operations Center 217

 Getting started with the Operations Center

| Adding customized text to the login screen

| You can add customized text, such as your organization's Terms of Use of the
| software, to the login screen of the Operations Center so that users of the
| Operations Center see the text before they enter their user name and password.

| Procedure

| To add customized text to the login screen, complete the following steps:
| 1. On the computer where the Operations Center is installed, go to the following
| directory, where installation_dir represents the directory in which the
| Operations Center is installed:
| installation_dir/ui/Liberty/usr/servers/guiServer
| 2. In the directory, create a file that is named loginText.html that contains the
| text that you want to add to the login screen. Any special, non-ASCII text must
| be UTF-8 encoded.

| Tip: You can format the text by adding HTML tags.

| 3. Review the added text on the login screen of the Operations Center.
| To open the Operations Center, enter the following address in a web browser,
| where hostname represents the name of the computer where the Operations
| Center is installed, and secure_port represents the port number that the
| Operations Center uses for HTTPS communication on that computer:
| https://hostname:secure_port/oc
|
Configuring for SSL communication
The Operations Center uses Hypertext Transfer Protocol Secure (HTTPS) to
communicate with web browsers. You can optionally use the Secure Sockets Layer
(SSL) protocol to secure communications between the Operations Center and the
hub server, and between the hub server and associated spoke servers.

Configuring for SSL communication between the Operations

Center and the hub server
To use the Secure Sockets Layer (SSL) protocol to secure communications between
the Operations Center and the hub server, you must add the SSL certificate of the
hub server to the truststore file of the Operations Center.

Before you begin

The truststore file of the Operations Center is a container for SSL certificates that
the Operations Center can access. The truststore file contains the SSL certificate that
the Operations Center uses for HTTPS communication with web browsers.

During the installation of the Operations Center, you create a password for the
truststore file. To set up SSL communication between the Operations Center and
the hub server, you must use the same password to add the SSL certificate of the
hub server to the truststore file. If you do not remember this password, you can
reset it. See “Resetting the password for the Operations Center truststore file” on
page 223.

Procedure
1. To ensure that SSL ports are set on the hub server, complete the following
steps:

218 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

a. From a Tivoli Storage Manager command line, issue the following

command to the hub server:
QUERY OPTION SSL*
The results include four server options, as shown in the following
example:
Server Option Option Setting
------------------------------
SSLTCPPort 3700
SSLTCPADMINPort 3800
SSLTLS12 Yes
SSLFIPSMODE No

b. Ensure that the SSLTCPPORT option has a value in the Option Setting
column. Also, ensure that the SSLTLS12 option is set to YES so that the
Transport Layer Security (TLS) protocol version 1.2 is used for
communication. To update the values of these options, edit the
dsmserv.opt file of the hub server, and restart the hub server.
| 2. Specify the cert256.arm certificate as the default certificate in the key database
| file of the hub server.
| The cert256.arm certificate must be used for SSL connections to the hub
| server if the SSLTLS12 option is set to YES. To specify cert256.arm as the
| default certificate, complete the following steps:
| a. Issue the following command from the hub server instance directory:
| gsk8capicmd_64 -cert -setdefault -db cert.kdb -stashed
| -label "TSM Server SelfSigned SHA Key"
| b. Restart the hub server so that it can receive the changes to the key
| database file.
| 3. To verify that the cert256.arm certificate is set as the default certificate in the
| key database file of the hub server, issue the following command:
| gsk8capicmd_64 -cert -list -db cert.kdb -stashed
4. Stop the Operations Center web server.
5. Go to the command line of the operating system on which the Operations
Center is installed.
6. Go to the following directory, where installation_dir represents the
directory in which the Operations Center is installed:
v installation_dir/ui/jre/bin
7. Open the IBM Key Management window by issuing the following command:
ikeyman
8. Click Key Database File > Open.
9. In the Open window, click Browse, and go to the following directory, where
installation_dir represents the directory in which the Operations Center is
installed:
v installation_dir/ui/Liberty/usr/servers/guiServer
10. In the guiServer directory, select the gui-truststore.jks file.
11. Click Open, and click OK.
12. Enter the password for the truststore file, and click OK.
13. In the Key database content area of the IBM Key Management window, click
the arrow, and select Signer Certificates from the list.
14. Click Add.
| 15. In the Open window, click Browse, and go to the hub server instance
| directory, as shown in the following example:

Chapter 16. Getting started with the Operations Center 219

 Getting started with the Operations Center

| v /opt/tivoli/tsm/server/bin
| The directory contains the following SSL certificates:
| v cert.arm
| v cert256.arm
| If you cannot access the hub server instance directory from the Open window,
| complete the following steps:
| a. Use FTP or another file-transfer method to copy the cert256.arm files from
| the hub server to the following directory on the computer where the
| Operations Center is installed:
| v installation_dir/ui/Liberty/usr/servers/guiServer
| b. In the Open window, go to the guiServer directory.
| 16. Because the SSLTLS12 server option is set to YES, select the cert256.arm
| certificate as the SSL certificate.

| Tip: The certificate that you choose must be set as the default certificate in the
| key database file of the hub server. For more information, see step 2 on page
| 219 and 3 on page 219.
17. Click Open, and click OK.
18. Enter a label for the certificate. For example, enter the name of the hub server.
19. Click OK. The SSL certificate of the hub server is added to the truststore file,
and the label is displayed in the Key database content area of the IBM Key
Management window.
20. Close the IBM Key Management window.
21. Start the Operations Center web server.
22. To configure the Operations Center, complete the following steps in the login
window of the configuration wizard:
a. In the Connect to field, enter the value of one of the following server
options as the port number:
v SSLTCPPORT
v SSLTCPADMINPORT

Tip: If the SSLTCPADMINPORT option has a value, use that value. Otherwise,
use the value of the SSLTCPPORT option.
b. Select the Use SSL option.
If the Operations Center was previously configured, you can review the
contents of the serverConnection.properties file to verify the connection
information. The serverConnection.properties file is in the following
directory on the computer where the Operations Center is installed:
v installation_dir/ui/Liberty/usr/servers/guiServer

What to do next

To set up SSL communication between the hub server and a spoke server, see
“Configuring for SSL communication between the hub server and a spoke server”
on page 221.

220 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

Configuring for SSL communication between the hub server

and a spoke server
To use the Secure Sockets Layer (SSL) protocol to secure communications between
the hub server and a spoke server, you must define the SSL certificate of the spoke
server to the hub server. You must also configure the Operations Center to monitor
the spoke server.

Before you begin

Ensure that the Operations Center is configured to use the SSL protocol for
communication between the Operations Center and the hub server.

Procedure
| 1. To ensure that SSL ports are correctly set on the hub server and each spoke
| server, complete the following steps:
| a. From a Tivoli Storage Manager command line, issue the following
| command to each server:
| QUERY OPTION SSL*
| The results include four server options, as shown in the following
| example:
| Server Option Option Setting
| ------------------------------
| SSLTCPPort 3700
| SSLTCPADMINPort 3800
| SSLTLS12 Yes
| SSLFIPSMODE No
|
|
| b. Ensure that the SSLTCPPORT and SSLTCPADMINPORT options have values in
| the Option Setting column. Also, ensure that the SSLTLS12 option is set to
| YES so that the Transport Layer Security (TLS) protocol version 1.2 is used
| for communication. To update the values of these options, edit the
| dsmserv.opt file of the respective server, and restart that server.
| The SSLTCPPORT, SSLTCPADMINPORT, and SSLTLS12 options are required for
| all Tivoli Storage Manager servers that use SSL. The SSLTCPPORT option
| triggers the generation of the following files in the server instance
| directory:
| v cert.arm (SSL certificate)
| v cert256.arm (SSL certificate)
| v cert.kdb (key database file)

| Restriction: Because server-to-server connections are not supported by the

| cert.arm certificate, you must use the cert256.arm certificate.
| 2. On the spoke server, change to the directory of the spoke server instance.
3. To specify the required cert256.arm certificate as the default certificate in the
key database file of the spoke server, issue the following command:
gsk8capicmd_64 -cert -setdefault -db cert.kdb -stashed
-label "TSM Server SelfSigned SHA Key"
4. To verify the certificates in the key database file of the spoke server, issue the
following command:
gsk8capicmd_64 -cert -list -db cert.kdb -stashed

The following output is an example of the command output:

Chapter 16. Getting started with the Operations Center 221

Getting started with the Operations Center

Certificates found
* default, - personal, ! trusted
! Entrust.net Secure Server Certification Authority
! Entrust.net Certification Authority (2048)
! Entrust.net Client Certification Authority
! Entrust.net Global Client Certification Authority
! Entrust.net Global Secure Server Certification Authority
! VeriSign Class 1 Public Primary Certification Authority
! VeriSign Class 2 Public Primary Certification Authority
! VeriSign Class 3 Public Primary Certification Authority
! VeriSign Class 1 Public Primary Certification Authority - G2
! VeriSign Class 2 Public Primary Certification Authority - G2
! VeriSign Class 3 Public Primary Certification Authority - G2
! VeriSign Class 4 Public Primary Certification Authority - G2
! VeriSign Class 1 Public Primary Certification Authority - G3
! VeriSign Class 2 Public Primary Certification Authority - G3
! VeriSign Class 3 Public Primary Certification Authority - G3
! VeriSign Class 3 Public Primary Certification Authority - G5
! VeriSign Class 4 Public Primary Certification Authority - G3
! VeriSign Class 3 Secure Server CA
! Thawte Primary Root CA
! Thawte Primary Root CA - G2 ECC
! Thawte Server CA
! Thawte Premium Server CA
! Thawte Personal Basic CA
! Thawte Personal Freemail CA
! Thawte Personal Premium CA
- TSM Server SelfSigned Key
*- TSM Server SelfSigned SHA Key
5. Securely transfer the cert256.arm file of the spoke server to the hub server.
6. On the hub server, change to the directory of the hub server instance.
7. To define the spoke server SSL certificate to the hub server, issue the following
command from the hub server instance directory, where spoke_servername is
the name of the spoke server, and spoke_cert256.arm is the file name of the
spoke server SSL certificate:
gsk8capicmd_64 -cert -add -db cert.kdb -stashed -format ascii
-label spoke_servername -file spoke_cert256.arm
The spoke server does not require the hub server SSL certificate for
hub-to-spoke communication. However, other Tivoli Storage Manager server
configurations that require cross-defined servers do require the spoke server
to have the hub server SSL certificate.

Tip: From each server, you can view the certificates in the key database file
by issuing the following command:
gsk8capicmd_64 -cert -list -db cert.kdb -stashed
8. Restart the hub server and the spoke server.
9. For the hub server, issue the DEFINE SERVER command, according to the
following example:
DEFINE SERVER spoke_servername HLA=spoke_address
LLA=spoke_SSLTCPADMINPort SERVERPA=spoke_serverpassword SSL=YES
10. In the Operations Center menu bar, click Servers.
In the table on the Servers page, the spoke server that you defined in step 9
should have a status of “Unmonitored.” However, depending on the setting
for the status refresh interval, you might not see the spoke server immediately.
11. Click the spoke server to highlight it, and in the table menu bar, click Monitor
Spoke.

222 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

Resetting the password for the Operations Center truststore

file
To set up SSL communication between the Operations Center and the hub server,
you must know the password for the truststore file of the Operations Center. You
create this password during the installation of the Operations Center. If you do not
know the password, you can reset it.

About this task

To reset the password, you must create a new password, delete the truststore file
of the Operations Center, and restart the Operations Center web server.

Procedure
1. Stop the Operations Center web server.
2. Go to the following directory, where installation_dir represents the directory
in which the Operations Center is installed:
installation_dir/ui/Liberty/usr/servers/guiServer
3. Open the bootstrap.properties file, which contains the password for the
truststore file. If the password is unencrypted, you can use it to open the
truststore file without having to reset it.
The following examples indicate the difference between an encrypted and an
unencrypted password:
Encrypted password example
Encrypted passwords begin with the text string {xor}.
The following example shows the encrypted password as the value of
the tsm.truststore.pswd parameter:
tsm.truststore.pswd={xor}MiYPPiwsKDAtOw==
Unencrypted password example
The following example shows the unencrypted password as the value
of the tsm.truststore.pswd parameter:
tsm.truststore.pswd=J8b%^B
4. Reset the password by replacing the password in the bootstrap.properties file
with a new password. You can replace the password with an encrypted or
unencrypted password. Remember the unencrypted password for future use.
To create an encrypted password, complete the following steps:
a. Create an unencrypted password.
The password for the truststore file must meet the following criteria:
v The password must contain a minimum of 6 characters and a maximum
of 64 characters.
v The password must contain at least the following characters:
– One uppercase letter (A – Z)
– One lowercase letter (a – z)
– One digit (0 – 9)
– Two of the following non-alphanumeric characters:
~ ! @ # $ % ^ & * _ - + = ` |
( ) { } [ ] : ; < > , . ? /
b. From the command line of the operating system, go to the following
directory:
installation_dir/ui/Liberty/bin

Chapter 16. Getting started with the Operations Center 223

 Getting started with the Operations Center

c. To encrypt the password, issue the following command, where myPassword

represents the unencrypted password:
securityUtility encode myPassword
5. Close the bootstrap.properties file.
6. Go to the following directory:
installation_dir/ui/Liberty/usr/servers/guiServer
7. Delete the gui-truststore.jks file, which is the truststore file of the Operations
Center.
8. Start the Operations Center web server.

Results

A new truststore file is automatically created for the Operations Center, and the
SSL certificate of the Operations Center is automatically included in the truststore
file.

Starting and stopping the web server

The web server of the Operations Center runs as a service and starts automatically.
You might need to stop and start the web server, for example, to make
configuration changes.

Procedure

Stop and start the web server.

v From the /installation_dir/ui/utils directory, where installation_dir
represents the directory where the Operations Center is installed, issue the
following commands:
– To stop the server:
./stopserver.sh
– To start the server:
./startserver.sh

| Collecting diagnostic information with Tivoli Storage Manager client

| management services
| Tivoli Storage Manager client management services collects diagnostic information
| about Tivoli Storage Manager backup-archive clients and makes the information
| available to the Operations Center for basic monitoring capability.

| About this task

| After you install the client management service, you can view the Diagnosis page
| in the Operations Center to obtain troubleshooting information for backup-archive
| clients.

224 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

| Installing the client management service by using a graphical

| wizard
| To collect diagnostic information about backup-archive clients such as client log
| files, you must install the client management service on the client systems that you
| manage.

| Before you begin

| Review “Requirements and limitations for Tivoli Storage Manager client

| management services” on page 199.

| About this task

| You must install the client management service on the same computer as the
| backup-archive client.

| Procedure
| 1. Obtain the installation package for the client management service. The
| installation package is included in the Operations Center installation package,
| which is on the product DVD. Alternatively, you can download the installation
| package for the client management service from an IBM download site such as
| IBM Passport Advantage or IBM Fix Central.
| The following table shows the names of the installation packages.
|| Client operating system Installation package name
| Linux x86 64-bit 7.1.1.000-TIV-TSMCMS-Linuxx64.bin
| Windows 32-bit 7.1.1.000-TIV-TSMCMS-Windows32.exe
| Windows 64-bit 7.1.1.000-TIV-TSMCMS-Windows64.exe
|
| 2. Create a directory on the client system that you want to manage, and copy the
| installation package there.
| 3. Extract the contents of the installation package file.
| v On Linux client systems, complete the following steps:
| a. Change the file to an executable file by issuing the following command:
| chmod +x 7.1.1.000-TIV-TSMCMS-Linuxx64.bin
| b. Issue the following command:
| ./7.1.1.000-TIV-TSMCMS-Linuxx64.bin
| v On Windows client systems, double-click the installation package name in
| Windows Explorer.

| Tip: If you previously installed and uninstalled the package, select All when
| prompted to replace the existing installation files.
| 4. Run the installation batch file from the directory where you extracted the
| installation files and associated files. This is the directory that you created in
| step 2.
| v On Linux client systems, issue the following command:
| ./install.sh
| v On Windows client systems, double-click install.bat.
| 5. To install the client management service, follow the instructions in the IBM
| Installation Manager wizard.

Chapter 16. Getting started with the Operations Center 225

 Getting started with the Operations Center

| If IBM Installation Manager is not already installed on the client system, you
| must select both IBM Installation Manager and IBM Tivoli Storage Manager
| Client Management Services.

| Tip: You can accept the default locations for the shared resources directory and
| the installation directory for IBM Installation Manager.

| What to do next

| Follow the instructions in “Verifying that the client management service is installed
| correctly” on page 227.

| Installing the client management service in silent mode

| You can install the client management service in silent mode. When you use silent
| mode, you provide the installation values in a response file and then run an
| installation command.

| Before you begin

| Review “Requirements and limitations for Tivoli Storage Manager client

| management services” on page 199.

| Extract the installation package by following the instructions in “Installing the

| client management service by using a graphical wizard” on page 225.

| About this task

| You must install the client management service on the same computer as the
| backup-archive client.

| The input directory, which is in the directory where the installation package is
| extracted, contains the following sample response file:

| install_response_sample.xml

| You can use the sample file with the default values, or you can customize it.

| Tip: If you want to customize the sample file, create a copy of the sample file,
| rename it, and edit the copy.

| Procedure
| 1. Create a response file based on the sample file, or use the sample file,
| install_response_sample.xml.
| In either case, ensure that the response file specifies the port number for the
| client management service. The default port is 9028. For example:
| <variable name='port' value='9028'/>
| 2. Run the command to install the client management service and accept the
| license. From the directory where the installation package file is extracted, issue
| the following command, where response_file represents the response file path,
| including the file name:
| On a Linux client system:
| ./install.sh -s -input response_file -acceptLicense
| For example:
| ./install.sh -s -input /cms_install/input/install_response.xml -acceptLicense

226 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

| On a Windows client system:

| install.bat -s -input response_file -acceptLicense
| For example:
| install.bat -s -input c:\cms_install\input\install_response.xml -acceptLicense

| What to do next

| Follow the instructions in “Verifying that the client management service is installed
| correctly.”

| Verifying that the client management service is installed

| correctly
| Before you use the client management service to collect diagnostic information
| about a backup-archive client, you can verify that the client management service is
| correctly installed and configured.

| Procedure

| On the client system, at the command line, run the following commands to view
| the configuration of the client management service:
| v On Linux client systems, issue the following command:
| client_install_dir/cms/bin/CmsConfig.sh list

| where client_install_dir is the directory where the backup-archive client is

| installed. For example, with the default client installation, issue the following
| command:
| /opt/tivoli/tsm/cms/bin/CmsConfig.sh list

| The output is similar to the following text:

| List:
| server1.example.com:1500 HOSTNAME
| /opt/tivoli/tsm/client/ba/bin/dsmerror.log
| en_US MM/dd/yyyy HH:mm:ss UTF-8
| v On Windows client systems, issue the following command:
| client_install_dir\cms\bin\CmsConfig.bat list

| where client_install_dir is the directory where the backup-archive client is

| installed. For example, with the default client installation, issue the following
| command:
| C:\"Program Files"\Tivoli\TSM\cms\bin\CmsConfig.bat list

| The output is similar to the following text:

| List:
| server1.example.com:1500 HOSTNAME
| C:/Program Files/Tivoli/TSM/baclient/dsmerror.log
| en_US MM/dd/yyyy HH:mm:ss Windows-1252
| If the client management service is correctly installed and configured, the output
| displays the location of the error log file.
| The output text is extracted from the following configuration file:
| v On Linux client systems:
| client_install_dir/cms/Liberty/usr/servers/cmsServer/client-configuration.xml
| v On Windows client systems:
| client_install_dir\cms\Liberty\usr\servers\cmsServer\client-configuration.xml

Chapter 16. Getting started with the Operations Center 227

 Getting started with the Operations Center

| If the output does not contain any entries, you must configure the
| client-configuration.xml file. For instructions about how to configure this file,
| see “Configuring the client management service for custom client installations” on
| page 230.

| Configuring the Operations Center to use the client

| management service
| If you did not use the default configuration for the client management service, you
| must configure the Operations Center to access the client management service.

| Before you begin

| Ensure that the client management service is installed and started on the client
| system.

| Verify whether the default configuration is used. The default configuration is not
| used if either of the following conditions is met:
| v The client management service does not use the default port number, 9028.
| v The backup-archive client is not accessed by the same IP address as the client
| system where the backup-archive client is installed. For example, a different IP
| address might be used in the following situations:
| – The computer system has two network cards. The backup-archive client is
| configured to communicate on one network, while the client management
| service communicates on the other network.
| – The client system is configured with the Dynamic Host Configuration
| Protocol (DHCP). As a result, the client system is dynamically assigned an IP
| address, which is saved on the Tivoli Storage Manager server during the
| previous backup-archive client operation. When the client system is restarted,
| the client system might be assigned a different IP address. To ensure that the
| Operations Center can always find the client system, you specify a fully
| qualified domain name.

| Procedure

| To configure the Operations Center to use the client management service, complete
| the following steps:
| 1. On the Clients page of the Operations Center, select the client.
| 2. Click Details.
| 3. Click the Properties tab.
| 4. In the Remote diagnostics URL field in the General section, specify the URL
| for the client management service on the client system.
| The address must start with https. The following table shows examples of the
| remote diagnostics URL.
|| Type of URL Example
| With DNS host name and default port, 9028 https://server.example.com
| With DNS host name and non-default port https://server.example.com:1599
| With IP address and non-default port https://192.0.2.0:1599
|
| 5. Click Save.

228 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

| What to do next

| You can access client diagnostic information such as client log files from the
| Diagnosis tab in the Operations Center.

| Starting and stopping the client management service

| The client management service is automatically started after it is installed on the
| client system. You might need to stop and start the service in certain situations.

| Procedure
| v To stop, start, or restart the client management service on Linux client systems,
| issue the following commands:
| – To stop the service:
| service cms.rc stop
| – To start the service:
| service cms.rc start
| – To restart the service:
| service cms.rc restart
| v On Windows client systems, open the Services window, and stop, start, or restart
| the Tivoli Storage Manager Client Management Services service.

| Uninstalling the client management service

| If you no longer have to collect client diagnostic information, you can uninstall the
| client management service from the client system.

| About this task

| You must use IBM Installation Manager to uninstall the client management service.
| If you no longer plan to use IBM Installation Manager, you can also uninstall it.

| Procedure
| 1. Uninstall the client management service from the client system:
| a. Open IBM Installation Manager:
| v On the Linux client system, in the directory where IBM Installation
| Manager is installed, go to the eclipse subdirectory (for example,
| /opt/IBM/InstallationManager/eclipse), and issue the following
| command:
| ./IBMIM
| v On the Windows client system, open IBM Installation Manager from the
| Start menu.
| b. Click Uninstall.
| c. Select IBM Tivoli Storage Manager Client Management Services, and click
| Next.
| d. Click Uninstall, and then click Finish.
| e. Close the IBM Installation Manager window.
| 2. If you no longer require IBM Installation Manager, uninstall it from the client
| system:
| a. Open the IBM Installation Manager uninstall wizard:

Chapter 16. Getting started with the Operations Center 229

 Getting started with the Operations Center

| v On the Linux client system, change to the IBM Installation Manager

| uninstallation directory (for example, /var/ibm/InstallationManager/
| uninstall), and issue the following command:
| ./uninstall
| v On the Windows client system, click Start > Control Panel. Then, click
| Uninstall a program > IBM Installation Manager > Uninstall.
| b. In the IBM Installation Manager window, select IBM Installation Manager
| if it is not already selected, and click Next.
| c. Click Uninstall, and click Finish.

| Configuring the client management service for custom client

| installations
| The client management service uses information in the client configuration file
| (client-configuration.xml) to discover diagnostic information. If the client
| management service is unable to discover the location of log files, you must run
| the CmsConfig utility to add the location of the log files to the client-
| configuration.xml file.

| The CmsConfig utility

| If you are not using the default configuration, you can run the CmsConfig utility on
| the client system to discover and add the location of the client log files to the
| client-configuration.xml file. After you complete the configuration, the client
| management service can access the client log files and make them available for
| diagnosis in the Operations Center.

| You can also use the CmsConfig utility to show the configuration of the client
| management service and to remove a node name from the client-
| configuration.xml file.

| The client-configuration.xml file is in the following directory:

| v On Linux client systems:
| client_install_dir/cms/Liberty/usr/servers/cmsServer
| v On Windows client systems:
| client_install_dir\cms\Liberty\usr\servers\cmsServer
| where client_install_dir is the directory where the backup-archive client is installed.

| The CmsConfig utility is available in the following locations.

|| Client operating system Utility location and name
| Linux client_install_dir/cms/bin/CmsConfig.sh
| Windows client_install_dir\cms\bin\CmsConfig.bat
|

| To use the CmsConfig utility, issue any command that is included in the utility.
| Ensure that you enter each command on a single line.

| Use the commands to complete the following tasks.

230 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

|| Task Command
| Discover the location of log files and “CmsConfig discover command”
| automatically add them to the
| client-configuration.xml file.

| Run this command only if you are not using

| the default configuration, or you changed
| the backup-archive client, the server
| configuration, or the location of the log files.
| Manually add the location of log files to the “CmsConfig add command” on page 232
| client-configuration.xml file.

| Run this command only if client log files are

| stored in a non-default location on the client
| system.
| Show the configuration of the client “CmsConfig list command” on page 236
| management service.

| Run this command only if you want to

| verify the configuration.
| Remove a node name from the “CmsConfig remove command” on page 237
| client-configuration.xml file.

| Run this command only if the node no

| longer exists, or you do not want to obtain
| diagnostic information about the node.
|

| CmsConfig discover command:

| You can use the CmsConfig discover command to discover options files and log
| files, and add them to the client configuration file, client-configuration.xml. In
| this way, you can help to ensure that the client management service can access the
| client log files and make them available for diagnosis in the Operations Center.

| Typically, the client management service installer runs the CmsConfig discover
| command automatically. However, you must run this command manually if you
| changed the backup-archive client, such as added a client, or changed the server
| configuration or location of log files.

| For the client management service to create a log definition in the

| client-configuration.xml file, the Tivoli Storage Manager server address, server
| port, and client node name must be obtained. If the node name is not defined in
| the client options file (typically, dsm.sys on Linux client systems and dsm.opt on
| Windows client systems), the host name of the client system is used.

| To update the client configuration file, the client management service must access
| one or more log files, such as dsmerror.log and dsmsched.log. For best results, run
| the CmsConfig discover command in the same directory and by using the same
| environment variables as you would for the backup-archive client command, dsmc.
| In this way, you can improve the chances of finding the correct log files.

| Syntax

|  CmsConfig discover 
|

Chapter 16. Getting started with the Operations Center 231

 Getting started with the Operations Center

| Example for a Linux client system

| For a Linux client system, discover the client log files and automatically add the
| log definitions to the client-configuration.xml file.
| Command:
| /opt/tivoli/tsm/cms/bin/CmsConfig.sh discover
| Output:
| Discover:
| server.example.com:1500 SUSAN
| /opt/tivoli/tsm/client/ba/bin/dsmerror.log

| Example for a Windows client system

| For a Windows client system, discover the client log files and automatically add
| the log definitions to the client-configuration.xml file.
| Command:
| C:\"Program Files"\Tivoli\TSM\cms\bin\cmsconfig discover
| Output:
| Discover:
| server.example.com:1500 SUSAN
| C:\Program Files\Tivoli\TSM\baclient\dsmerror.log

| CmsConfig add command:

| Use the CmsConfig add command to manually add the location of client log files to
| the client-configuration.xml configuration file. Use this command only if the
| client log files are stored in a non-default location on the client system.

| Syntax

|  CmsConfig add nodeName serverIP serverPort serverProtocol logPath 

|
|  
| language dateFormat timeFormat encoding
|

| Parameters
| nodeName
| The client node name that is associated with the log files. For most client
| systems, only one node name is registered to the Tivoli Storage Manager
| server. However, on systems with multiple users, such as Linux client systems,
| there can be more than one client node name. This parameter is required.
| serverIP
| The TCP/IP address of the Tivoli Storage Manager server that the client
| management service authenticates to. This parameter is required.
| You can specify a 1 - 64 character TCP/IP address for the server. The server
| address can be a TCP/IP domain name or a numeric IP address. The numeric
| IP address can be either a TCP/IP v4 or TCP/IP v6 address. You can use IPv6
| addresses only if the commmethod V6Tcpip option is specified for the client
| system.
| Examples:
| v server.example.com
| v 192.0.2.0
232 IBM Tivoli Storage Manager for AIX: Installation Guide
 Getting started with the Operations Center

| v 2001:0DB8:0:0:0:0:0:0
| serverPort
| The TCP/IP port number that is used to communicate with the Tivoli Storage
| Manager server. You can specify a value in the range 1 - 32767. This parameter
| is required.
| Example: 1500
| serverProtocol
| The protocol that is used for communication between the client management
| service and the Tivoli Storage Manager server. This parameter is required.
| You can specify one of the following values.
|| Value Meaning
| NO_SSL The SSL security protocol is not used.
| SSL The SSL security protocol is used.
| FIPS The TLS 1.2 protocol is used in Federal
| Information Processing Standard (FIPS)
| mode.
| Tip: Alternatively, you can enter TLS_1.2 to
| specify that the TLS 1.2 protocol is used in
| FIPS mode.
|
| logPath
| The fully qualified path of the log files. This parameter is required.
| Windows client system example: C:\backup tools\Tivoli\TSM\baclient\
| dsmerror.log
| Linux client system example: /opt/backup_tools/tivoli/tsm/baclient/
| dsmerror.log
| language
| The language locale of the log file. This parameter is optional. However, if you
| specify this parameter, you must also specify the dateFormat, timeFormat, and
| encoding parameters. You must specify the locale for the following languages.
|| Language Locale
| Brazilian Portuguese pt_BR
| Chinese, Simplified zh_CN
| Chinese, Traditional zh_TW
| Czech cs_CZ
| English en_US
| French fr_FR
| German de_DE
| Hungarian hu_HU
| Italian it_IT
| Japanese ja_JP
| Korean ko_KR
| Polish pl_PL
| Russian ru_RU
| Spanish es_ES

Chapter 16. Getting started with the Operations Center 233

 Getting started with the Operations Center

|
| dateFormat
| The date format of the time stamp entries in the client log file. This parameter
| is optional. However, if you specify this parameter, you must also specify the
| language, timeFormat, and encoding parameters.
| The following table shows the date formats for the languages.

| Tip: Instead of using one of the date formats that are listed in the table, you
| can specify a date format by using the backup-archive client dateformat
| option.
|| Language Date format
| Chinese, Simplified yyyy-MM-dd
| Chinese, Traditional yyyy/MM/dd
| Czech dd.MM.yyyy
| English MM/dd/yyyy
| French dd/MM/yyyy
| German dd.MM.yyyy
| Hungarian yyyy.MM.dd
| Italian dd/MM/yyyy
| Japanese yyyy-MM-dd
| Korean yyyy/MM/dd
| Polish yyyy-MM-dd
| Portuguese, Brazilian dd/MM/yyyy
| Russian dd.MM.yyyy
| Spanish dd.MM.yyyy
|
| timeFormat
| The time format of the time stamp entries in the client log file. This parameter
| is optional. However, if you specify this parameter, you must also specify the
| language, dateFormat, and encoding parameters.
| The following table shows examples of default time formats that you can
| specify and client operating systems.

| Tip: Instead of using one of the time formats that are listed in the table, you
| can specify a time format by using the backup-archive client timeformat
| option.
|| Time format for Linux client Time format for Windows
| Language systems client systems
| Chinese, Simplified HH:mm:ss HH:mm:ss
| Chinese, Traditional HH:mm:ss ahh:mm:ss
| Czech HH:mm:ss HH:mm:ss
| English HH:mm:ss HH:mm:ss
| French HH:mm:ss HH:mm:ss
| German HH:mm:ss HH:mm:ss
| Hungarian HH.mm.ss HH:mm:ss

234 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

| Time format for Linux client Time format for Windows

| Language systems client systems
| Italian HH:mm:ss HH:mm:ss
| Japanese HH:mm:ss HH:mm:ss
| Korean HH:mm:ss HH:mm:ss
| Polish HH:mm:ss HH:mm:ss
| Portuguese, Brazilian HH:mm:ss HH:mm:ss
| Russian HH:mm:ss HH:mm:ss
| Spanish HH:mm:ss HH:mm:ss
|
| encoding
| The character encoding of the entries in the client log files. This parameter is
| optional. However, if you specify this parameter, you must also specify the
| language, dateFormat, and timeFormat parameters.
| For Linux client systems, the typical character encoding is UTF-8. For Windows
| client systems, the default encoding values are shown in the following table. If
| your client system is customized differently, use the encoding parameter to
| specify a value other than the default.
|| Language Encoding
| Chinese, Simplified CP936
| Chinese, Traditional CP950
| Czech Windows-1250
| English Windows-1252
| French Windows-1252
| German Windows-1252
| Hungarian Windows-1250
| Italian Windows-1252
| Japanese CP932
| Korean CP949
| Polish Windows-1250
| Portuguese, Brazilian Windows-1252
| Russian Windows-1251
| Spanish Windows-1252
|

| Example for a Linux client system

| For a Linux client system, add the client log file location to the
| client-configuration.xml file. Also, add the language specification, time format,
| and date format. Then, verify the output to ensure that you entered the command
| correctly.
| Command:
| /opt/tivoli/tsm/cms/bin/CmsConfig.sh add SUSAN server.example.com
| 1500 /usr/work/logs/dsmerror.log fr_FR yyyy/MM/dd HH:MM:ss UTF-8

Chapter 16. Getting started with the Operations Center 235

 Getting started with the Operations Center

| Output:
| Add: SUSAN server.example.com:1500 /usr/work/logs/dsmerror.log fr_FR
| yyyy/MM/dd HH:MM:ss UTF-8

| Example for a Windows client system

| For a Windows client system, add the client log file location to the
| client-configuration.xml. Also, add the language specification, date format, and
| time format. Then, verify the output to ensure that you entered the command
| correctly.
| Command:
| C:\"Program Files"\Tivoli\TSM\cms\bin\cmsconfig add SUSAN
| server.example.com 1500 c:\work\logs\dsmerror.logfr_FR yyyy/MM/dd
| HH:MM:ss UTF-8
| Output:
| Add: SUSAN server.example.com:1500 c:\work\logs\dsmerror.log fr_FR
| yyyy/MM/dd HH:MM:ss UTF-8

| CmsConfig list command:

| Use the CmsConfig list command to show the client management service
| configuration.

| Syntax

|  CmsConfig list 
|

| Example for a Linux client system

| For a Linux client system, show the configuration of the client management
| service. Then, view the output to ensure that you entered the command correctly.
| Command:
| /opt/tivoli/tsm/cms/bin/CmsConfig.sh list
| Output:
| List:
| server.example.com:1500 SUSAN
| /opt/tivoli/tsm/client/ba/bin/dsmerror.log
| en_US MM/dd/yyyy HH:mm:ss Windows-1252

| Example for a Windows client system

| For a Windows client system, show the configuration of the client management
| service. Then, view the output to ensure that you entered the command correctly.
| Command:
| C:\"Program Files"\Tivoli\TSM\cms\bin\cmsconfig list
| Output:
| List:
| server.example.com:1500 SUSAN
| C:/Program Files/Tivoli/TSM/baclient/dsmerror.log
| en_US MM/dd/yyyy HH:mm:ss Windows-1252

236 IBM Tivoli Storage Manager for AIX: Installation Guide

 Getting started with the Operations Center

| CmsConfig remove command:

| Use the CmsConfig remove command to remove a client node name from the client
| configuration file, client-configuration.xml. All log files that are associated with
| the client node name are also removed.

| Syntax

|  CmsConfig remove nodeName 

|

| Parameters
| nodeName
| The client node name that is associated with the log files. For most client
| systems, only one node name is registered to the Tivoli Storage Manager
| server. However, on systems with multiple users, such as Linux client systems,
| more than one client node name can be used. This parameter is required.

| Example for a Linux client system

| For a Linux client system, remove the node name SUSAN from the
| client-configuration.xml file. Then, verify the output to ensure that you entered
| the command correctly.
| Command:
| /opt/tivoli/tsm/cms/bin/CmsConfig.sh remove SUSAN
| Output:
| Remove: SUSAN

| Example for a Windows client system

| For a Windows client system, remove the node name SUSAN from the
| client-configuration.xml file. Then, verify the output to ensure that you entered
| the command correctly.
| Commands:
| C:\"Program Files"\Tivoli\TSM\cms\bin\CmsConfig remove SUSAN
| Output:
| Remove: SUSAN

Chapter 16. Getting started with the Operations Center 237

Getting started with the Operations Center

238 IBM Tivoli Storage Manager for AIX: Installation Guide

|

Chapter 17. Troubleshooting the Operations Center

installation
If a problem occurs with the Operations Center installation and you cannot solve
it, you can consult the descriptions of known problems for a possible solution.

Graphical installation wizard cannot be started on an AIX system

You are installing the Operations Center on an AIX system by using the graphical
wizard, and the installation program does not start.

Solution

The RPM files that are listed in “Installing the Operations Center by using a
graphical wizard” on page 208 must be installed on the computer. Verify that the
RPM files are installed.

© Copyright IBM Corp. 1993, 2014 239

240 IBM Tivoli Storage Manager for AIX: Installation Guide
Chapter 18. Uninstalling the Operations Center
You can uninstall the Operations Center by using any of the following methods: a
graphical wizard, the command line in console mode, or silent mode.

Uninstalling the Operations Center by using a graphical wizard

You can uninstall the Operations Center by using the graphical wizard of IBM
Installation Manager.

Procedure
1. Open IBM Installation Manager.
In the directory where IBM Installation Manager is installed, go to the eclipse
subdirectory (for example, /opt/IBM/InstallationManager/eclipse), and issue
the following command:
./IBMIM
2. Click Uninstall.
3. Select IBM Tivoli Storage Manager Operations Center, and click Next.
4. Click Uninstall.
5. Click Finish.

Uninstalling the Operations Center in console mode

To uninstall the Operations Center by using the command line, you must run the
uninstallation program of IBM Installation Manager from the command line with
the parameter for console mode.

Procedure
1. In the directory where IBM Installation Manager is installed, go to the
following subdirectory:
eclipse/tools
For example:
/opt/IBM/InstallationManager/eclipse/tools
2. From the tools directory, issue the following command:
./imcl -c
3. To uninstall, enter 5.
4. Choose to uninstall from the IBM Tivoli Storage Manager package group.
5. Enter N for Next.
6. Choose to uninstall the IBM Tivoli Storage Manager Operations Center
package.
7. Enter N for Next.
8. Enter U for Uninstall.
9. Enter F for Finish.

© Copyright IBM Corp. 1993, 2014 241

Uninstalling the Operations Center

Uninstalling the Operations Center in silent mode

To uninstall the Operations Center in silent mode, you must run the uninstallation
program of IBM Installation Manager from the command line with the parameters
for silent mode.

Before you begin

The input directory, which is in the directory where the installation package is
extracted, contains the following sample response files for installing, updating, and
uninstalling the Operations Center:
v install_response_sample.xml
v update_response_sample.xml
v uninstall_response_sample.xml

You can use these sample files as they are, with the default values, or you can
customize them.

Procedure
1. In the directory where IBM Installation Manager is installed, go to the
following subdirectory:
eclipse/tools
For example:
/opt/IBM/InstallationManager/eclipse/tools
2. From the tools directory, issue the following command, where response_file
represents the response file path, including the file name:
./imcl -input response_file -silent
The following command is an example:
./imcl -input /tmp/input/uninstall_response.xml -silent

242 IBM Tivoli Storage Manager for AIX: Installation Guide

Chapter 19. Rolling back to a previous version of the
Operations Center
By default, IBM Installation Manager saves earlier versions of a package to roll
back to if you experience a problem with later versions of updates, fixes, or
packages.

Before you begin

The rollback function is available only after the Operations Center is updated.

About this task

When IBM Installation Manager rolls back a package to a previous version, the
current version of the package files is uninstalled, and an earlier version is
reinstalled.

To roll back to a previous version, IBM Installation Manager must access files for
that version. By default, these files are saved during each successive installation.
Because the number of saved files increases with each installed version, you might
want to delete these files from your system on a regular schedule. However, if you
delete the files, you cannot roll back to a previous version.

To delete saved files or to update your preference for saving these files in future
installations, complete the following steps:
1. In IBM Installation Manager, click File > Preferences.
2. On the Preferences page, click Files for Rollback, and specify your preference.

Procedure

To roll back to a previous version of the Operations Center, use the Roll Back
function of IBM Installation Manager.

© Copyright IBM Corp. 1993, 2014 243

244 IBM Tivoli Storage Manager for AIX: Installation Guide
Part 4. Appendixes

© Copyright IBM Corp. 1993, 2014 245

246 IBM Tivoli Storage Manager for AIX: Installation Guide
Appendix A. Installation log files
If you experience errors during installation, these errors are recorded in log files
that are stored in the IBM Installation Manager logs directory.

You can view installation log files by clicking File > View Log from the Installation
Manager tool. To collect these log files, click Help > Export Data for Problem
Analysis from the Installation Manager tool.

© Copyright IBM Corp. 1993, 2014 247

248 IBM Tivoli Storage Manager for AIX: Installation Guide
Appendix B. Accessibility features for the Tivoli Storage
Manager product family
Accessibility features help users who have a disability, such as restricted mobility
or limited vision to use information technology products successfully.

Accessibility features

The IBM Tivoli Storage Manager family of products includes the following
accessibility features:
v Keyboard-only operation using standard operating-system conventions
v Interfaces that support assistive technology such as screen readers

The command-line interfaces of all products in the product family are accessible.

Tivoli Storage Manager Operations Center provides the following additional

accessibility features when you use it with a Mozilla Firefox browser on a
Microsoft Windows system:
v Screen magnifiers and content zooming
v High contrast mode

The Operations Center and the Tivoli Storage Manager Server can be installed in
console mode, which is accessible.

The Operations Center help system is enabled for accessibility. For more
information, click the question mark icon on the help system menu bar.

Vendor software

The Tivoli Storage Manager product family includes certain vendor software that is
not covered under the IBM license agreement. IBM makes no representation about
the accessibility features of these products. Contact the vendor for the accessibility
information about its products.

IBM and accessibility

See the IBM Human Ability and Accessibility Center (http://www.ibm.com/able)

for information about the commitment that IBM has to accessibility.

© Copyright IBM Corp. 1993, 2014 249

250 IBM Tivoli Storage Manager for AIX: Installation Guide
Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.

© Copyright IBM Corp. 1993, 2014 251

 IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who want to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

252 IBM Tivoli Storage Manager for AIX: Installation Guide

 Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_.

If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at http://www.ibm.com/legal/copytrade.shtml.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or

its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United

States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software
Offerings”) may use cookies or other technologies to collect product usage
information, to help improve the end user experience, to tailor interactions with
the end user, or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings
can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific
information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect
personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer
the ability to collect personally identifiable information from end users via cookies

Notices 253
 and other technologies, you should seek your own legal advice about any laws
applicable to such data collection, including any requirements for notice and
consent.

For more information about the use of various technologies, including cookies, for
these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy and
IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in the
section entitled “Cookies, Web Beacons and Other Technologies,” and the “IBM
Software Products and Software-as-a-Service Privacy Statement” at
http://www.ibm.com/software/info/product-privacy.

254 IBM Tivoli Storage Manager for AIX: Installation Guide

Glossary
A glossary is available with terms and definitions for the IBM Tivoli Storage Manager family of products.

See Tivoli Storage Manager glossary (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/

com.ibm.itsm.ic.doc/glossary.html).

To view glossaries for other IBM products, see http://www.ibm.com/software/globalization/

terminology/.

© Copyright IBM Corp. 1993, 2014 255

256 IBM Tivoli Storage Manager for AIX: Installation Guide
Index
Special characters client management service
add log file location 232
(TLS) Transport Layer Security 49 CmsConfig add 232
CmsConfig list 236
CmsConfig remove 237
A CmsConfig utility 230
access rights collecting diagnostic information 224
setting configuring for custom client installation 230
before server startup 55 configuring the Operations Center 228
accessibility features 249 discover 231
activating installing 225
server 54 in silent mode 226
active log Operations Center
space requirements 14 view client log files 224
adding the agent to the agent depot 127 remove node name 237
Administration Center xi requirements and limitations 199
administrative commands show configuration 236
HALT 58 starting and stopping 229
REGISTER LICENSE 58 uninstalling 229
administrator ID 201 verifying installation 227
administrator password 201 client nodes
agent reverting to previous server version
Tivoli Monitoring for Tivoli Storage Manager, installing on data affected 85
existing server 123 client options
AIX for shared memory communications 48
system requirements 4 client-configuration.xml file 227, 230
alerts clustered environment
sending by email 215 applying a fix pack to a V7.x server on AIX 66
API 50 upgrading server on AIX
API configuration 50 V6.1 to V7.1.1 82
archive failover log space V6.2 to V7.1.1 77, 79
description 25 V6.3 to V7.1.1 77, 79
archive log upgrading the server to V7.1.1 76
space requirements 14 CmsConfig utility
archive log directory 42 add 232
automatic starting, server 57 client management service 230
discover 231
list 236
B remove 237
commands
BACKUP DB command 50 administrative, SET DBRECOVERY 59
backups DSMSERV FORMAT 50
database 59 ikeyman 155, 160
commands, administrative
HALT 58
C REGISTER LICENSE 58
capacity planning communication methods
database space requirements Shared Memory 48
estimates based on number of files 10 SNMP 48
estimates based storage pool capacity 12 TCP/IP 47
starting size 10 compatibility, server with other DB2 products 7
recovery log space requirements components
active and archive logs 14 installable vii
active log mirror 25 configuration
Tivoli Monitoring for Tivoli Storage Manager 108 Operations Center 194
certificates configuring 41, 43, 44, 133
adding the Jazz for Service Management certificate 160 historical data collection 131
cert256.arm 154 hub server 214
exporting the Jazz for Service Management certificate 160 Operations Center 213
Tivoli Storage Manager server spoke server 214
adding to truststore file 155 configuring agents 149

© Copyright IBM Corp. 1993, 2014 257

Configuring monitoring agents using CandleManage 135
configuring services 149
G
configuring the Operations Center group 42
for client management service 228
configuring, manually 43, 44
configuring, server instance 43 H
configuring, wizard 43, 44 HALT command 58
Console language support 37, 38 halting the server 58
console mode 35, 121 hardware requirements
create server instance 41, 43 Tivoli Monitoring for Tivoli Storage Manager 103
creating and configuring Tivoli Storage Manager 4
the monitoring agent using CLI 138 historical data collection 133
creating and configuring the monitoring agent instance 134 configuring 133
custom configuration home directory 45
client management service 230 HTTPS 218, 221
password for truststore file 202, 223
hub server 194
D configuring 214
data deduplication
effects when reverting to previous server version 85
data source 143 I
database IBM Installation Manager xi, 8, 107, 202
backups 59 installing the RPM files on AIX 175
installing 50 IBM Knowledge Center ix
name 27 IBM Tivoli Monitoring
database directories 42 exporting data 167
database manager 13, 50 installing an agent on an existing server 123
DB2 commands 89 IBM Tivoli Storage Manager
DB2 directories 29 uninstalling 93
DB2 products, compatibility with the server 7 in silent mode 94
db2icrt command 45 using a graphical installation wizard 93
db2profile 56 using command line in console mode 94
default installation directories 29 IBM Tivoli Storage Manager Operations Center xi
deploying monitoring agents 126 ikeyman command 155, 160
deploying remotely 129 importing
device driver, Tivoli Storage Manager viii IBM Tivoli Monitoring data 169
directories Install wizard 120
DB2 29 installable components viii
default installation 29 installation
devices 29 work sheet for Tivoli Monitoring for Tivoli Storage
languages 29 Manager 108
naming for server 27 installation checklist 110
directories, instance 42 installation directories
disability 249 Operations Center
disk space 4 Installation Manager 202
DSMSERV FORMAT command 50 installation log 32, 35, 120, 121
dsmserv.v6lock 58 Installation Manager xi, 8, 202
logs directory 247
installation packages 31, 113, 141, 173
E Operations Center 207
email alerts 215 installation wizard 32
suspending temporarily 217 installing 120, 121
enabling communications 46 client management service 225
expiration database 50
server option 54 device support 31
Exporting IBM Tivoli Monitoring data 167 fix packs 63
graphical user interface
using 32
minimum requirements for 4
F monitoring agents
files using silent mode 122
dsmserv.opt.smp 46 Operations Center 207
first steps 41 recovery log 50
fix packs 63 server 3, 31
fixes 31 Tivoli Monitoring for Tivoli Storage Manager 100, 112
using console mode 117
using silent mode 118

258 IBM Tivoli Storage Manager for AIX: Installation Guide

installing (continued) multiple servers
Tivoli Monitoring for Tivoli Storage Manager (continued) upgrading
using the wizard 114 multiple servers 59
Tivoli Storage Manager reporting and monitoring 100
using command line in console mode
using 35
what to know before 3
N
names, best practices
installing overview 99, 141
database name 27
installing the Tivoli Storage Manager server 36
directories for server 27
silently 36
instance user ID 27
installingOperations Center 191
server instance 27
instance directories 42
server name 27
instance user ID 27
new features xi
interim fix 63
NIST SP800-131A standard 158
IBM Tivoli Monitoring 159
Jazz for Service Management 159
J monitoring agents 158
Jazz for Service Management 141 Tivoli Storage Manager server 161
installation 142
installation packages 141
start service 144 O
offering 8, 107, 202
operating system requirements
K Operations Center 198
keyboard 249 Operations Center vii
KILL command 58 administrator IDs 201
Knowledge Center ix Chrome 198
computer requirements 194
configuring 213
L credentials for installing 202
Firefox 198
LANGUAGE option 37, 38, 39
hub server 194
language package 39
IE 198
language packages 38
installation directory 202
language support 39
installation packages 207
languages
installing 191, 207
set 39
in silent mode 210
license, Tivoli Storage Manager 58
using a graphical wizard 208
licenses
using command line in console mode 209
installable package viii
Internet Explorer 198
limitations
language requirements 199
client management service 199
login screen text 218
log files
opening 214
installation 247
operating system requirements 198
login screen text
overview 193
Operations Center 218
password for secure communications 202, 223
port number 202
prerequisite checks 193
M rolling back to a previous version 243
maintenance updates 63 Safari 198
memory requirements 4, 103 spoke server 194, 214
Migrating SSL 218, 221
Tivoli Monitoring for Tivoli Storage Manager 181 system requirements 193
migrating V7.1 to a new system 182 troubleshooting the installation 239
V6.3 to V7.1 181 uninstalling 241
monitoring in silent mode 242
logs 60 using a graphical wizard 241
monitoring administrator 201 using command line in console mode 241
monitoring agent upgrading 191, 211
installation 120, 121 web browser requirements 198
monitoring agents 129 web server 224
installing and deploying 119 options
Tivoli Monitoring for Tivoli Storage Manager, starting the server 54
installing 120 options file
multiple DB2 copies 7 editing 46

Index 259
options, client
SSLTCPADMINPORT 48
S
SSLTCPPORT 47 scripts
TCPADMINPORT 47 rc.dsmserv 57
TCPPORT 47 starting servers automatically 57
TCPWINDOWSIZE 47 secure communications 218, 221
overview Secure Sockets Layer 218, 221
Operations Center 191, 193 between a monitoring agent and a Tivoli Storage Manager
server 154
monitoring agents 157
Secure Sockets Layer (SSL) 47
P communication using 49
package 8, 107, 202 Transport Layer Security (TLS) 49
package group 8, 107, 202 security standards
Passport Advantage 31 IBM Tivoli Monitoring 159
password Jazz for Service Management 159
Operations Center truststore file 202, 223 monitoring agents 158
password for secure communications 202 Tivoli Storage Manager server 161
performance server
Operations Center 194 after upgrade
user limits, setting for optimal performance 54 reverting to previous server version 85
planning before upgrade
installing Tivoli Monitoring for Tivoli Storage importance of preparation steps 85
Manager 100 compatibility
installing Tivoli Storage Manager reporting and DB2 products 7
monitoring 100 naming best practices 27
Tivoli Monitoring for Tivoli Storage Manager starting
upgrade scenarios 163 automatic 57
planning, capacity stopping 58
database space requirements upgrading
estimates based on number of files 10 V6 to V7.1 67
estimates based storage pool capacity 12 V6.1 to V7.1.1 76
starting size 10 V6.2 to V7.1.1 68
recovery log space requirements V6.3 to V7.1.1 68
active log mirror 25 server database
recovery log space requirementsv 14 reorganization options 53
port number server instance 43, 45
Operations Center 202 server instance, creating 45
prerequisite checker 4 server instances
prerequisite checks naming 27
Operations Center 193 naming best practices 27
publications ix server license 58
server options
dsmserv.opt.smp 46
R tailoring 46
recovery log server options file
archive failover log space 25 setting 46
installing 50 server, Tivoli Storage Manager
reference, DB2 commands 89 activating 54
REGISTER LICENSE command 58 halting 58
remote deployment options 46, 47
monitoring agents 126 setting up 54
remote deployment requirements starting 54
Tivoli Monitoring for Tivoli Storage Manager 126 SET DBRECOVERY 59
repository 8, 107, 202 shared memory client options 48
requirements shared memory communications method 48
client management service 199 shared resources directory 8, 107, 202
resource requirements silent installation
Operations Center 194 Tivoli Storage Manager 36
reverting to previous server version 85 SNMP communication method 48
rollback software requirements
Operations Center 243 Tivoli Monitoring for Tivoli Storage Manager 103
RPM files Tivoli Storage Manager 4
installing 34, 116, 209 spoke server 194
installing on AIX 175 adding 214
SSL 218, 221
password for truststore file 202, 223

260 IBM Tivoli Storage Manager for AIX: Installation Guide

SSL (Secure Sockets Layer) Tivoli Storage Manager
(TLS) Transport Layer Security 49 installation 32, 35
communication using 49 installation packages 31
SSLTCPADMINPORT option 48 server changes xi
SSLTCPPORT option 47 uninstalling 93
starting in silent mode 94
client management service 229 using a graphical installation wizard 93
server 54 using command line in console mode 94
starting server upgrading
from user ID 56 V6 to V7.1 67
starting servers automatically 57 V6.1 to V7.1.1 76
status monitoring 194 V6.2 to V7.1.1 68
stopping V6.3 to V7.1.1 68
client management service 229 Version 7.1.1 xi
server 58 Tivoli Storage Manager device driver, installable package viii
storage pools Tivoli Storage Manager fix packs 63
reverting to previous server version 85 Tivoli Storage Manager support site 31
summary of amendments Tivoli Storage Manager, setting up 54
Version 7.1.1 xi TLS 218, 221
system requirements translation features 37, 38
Operations Center 193, 194, 198, 199 translations 37, 38
Transport Layer Security
disabling TLS 1.1 and earlier 153
T Transport Layer Security (TLS) 49
Transport Layer Security protocol 218, 221
TCP/IP
troubleshooting
setting options 47
Operations Center graphical installation wizard on AIX
Version 4 47
systems 239
Version 6 47
Operations Center installation 239
TCPNODELAY option 47
truststore file 218, 221
TCPPORT option 47
monitoring agents 155
TCPWINDOWSIZE option 47
Operations Center 202
technical changes xi
resetting password 223
temporary disk space 13
Tivoli Storage Manager server 155
temporary space 13
tuning
time
Operations Center 194
server upgrade 69
Tivoli Monitoring for Tivoli Storage Manager xi, 110
agent instances
exporting instances 170 U
importing instances 171 ulimits
bypass prerequisites 111 setting
using the installation wizard 111 before server startup 55
data source 143 uninstalling 95
installation packages 113, 173 client management service 229
installing monitoring agents 186
using console mode 117 Tivoli Monitoring for Tivoli Storage Manager 183, 184
using silent mode 118, 122 monitoring agents 186
using the wizard 114 using console mode 185
installing the RPM files on AIX 175 using silent mode 185
uninstalling 183, 184 using the wizard 184
monitoring agents 186 uninstalling and reinstalling 95
using console mode 185 uninstalling monitoring agents
using silent mode 185 application support files 188
using the wizard 184 using console mode 187
uninstalling monitoring agents using silent mode 187
application support files 188 using the wizard 187
using console mode 187 updating 39, 211
using silent mode 187 upgrade
using the wizard 187 server
upgrade scenarios 163 estimated time 69
upgrading 172 V6 to V7.1 67
in console mode 176 V6.1 to V7.1.1 76
in silent mode 177 V6.2 to V7.1.1 68
monitoring agents 178 V6.3 to V7.1.1 68
using the wizard 174 upgrading
upgrading from V6.3 to V7.1 165 Tivoli Monitoring for Tivoli Storage Manager 163, 172
what to configure after installing 147 in console mode 176

Index 261
upgrading (continued)
Tivoli Monitoring for Tivoli Storage Manager (continued)
in silent mode 177
monitoring agents 178
operating system 179
upgrade scenarios 163
upgrading from V6.3 to V7.1 165
using the wizard 174
upgrading Operations Center 191
US English 39
user ID 42
user limits 54
setting
before server startup 55

V
verifying installation
client management service 227
Version 7.1.1 xi

W
web server
starting 224
stopping 224
wizard 41
worksheet
server space planning 9

262 IBM Tivoli Storage Manager for AIX: Installation Guide




Product Number: 5608-E01

5608-E02
5608-E03

Printed in USA