IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

Tivoli® Storage Manager

for Sun Solaris

Installation Guide

Version 5.5

GC23-5972-00

��

Tivoli® Storage Manager

for Sun Solaris

Installation Guide

Version 5.5

GC23-5972-00

��

Note!

Before using this information and the product it supports, read the general information in the "Notices" appendix.

Edition notice

This edition applies to Version 5 Release 5 of IBM Tivoli Storage Manager for Sun Solaris (program numbers

5608-ISM, 5608-ISX) and to any subsequent releases until otherwise indicated in new editions.

Changes since the previous edition are marked with a vertical bar (|) in the left margin. Ensure that you are using

the correct edition for the level of the product.

© Copyright International Business Machines Corporation 1993, 2007. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . v

Who should read this guide . . . . . . . . . v

Publications . . . . . . . . . . . . . . v

Tivoli Storage Manager publications . . . . . v

Support information . . . . . . . . . . . vii

Getting technical training . . . . . . . . viii

Searching knowledge bases . . . . . . . . viii

Contacting IBM Software Support . . . . . . ix

Accessibility features . . . . . . . . . . . xi

Technical Changes for Version 5

Release 5 — November 2007 . . . . . xiii

Chapter 1. Installing IBM Tivoli Storage

Manager . . . . . . . . . . . . . . 1

System requirements . . . . . . . . . . . . 1

Evaluation (try and buy) product . . . . . . . 2

Upgrading from the try and buy product . . . . 2

Installing Tivoli Storage Manager . . . . . . . 2

Installing the server to Solaris Zones . . . . . 4

Verifying your installation . . . . . . . . . . 5

Starting and stopping the server . . . . . . . . 6

Registering licenses . . . . . . . . . . . . 7

Upgrading to Tivoli Storage Manager Version 5.5 . . 7

Compatibility with other versions of IBM Tivoli

Storage Manager . . . . . . . . . . . . 7

Before performing an upgrade . . . . . . . 8

Performing an upgrade . . . . . . . . . . 9

Running multiple servers on a single machine . . . 12

Defining environment variables . . . . . . . . 13

Chapter 2. Installing the Integrated

Solutions Console and the

Administration Center . . . . . . . . 15

System requirements . . . . . . . . . . . 15

Configuring the IP address . . . . . . . . . 15

Overview: installing the Integrated Solutions

Console and the Administration Center . . . . . 16

Installing the Integrated Solutions Console . . . . 16

Installing and upgrading the Administration Center 18

Verifying your installation . . . . . . . . . 20

Starting and stopping the console server and

console help server . . . . . . . . . . . 20

Uninstalling the Administration Center . . . . . 21

Uninstalling the Integrated Solutions Console . . . 21

Manually uninstalling the Integrated Solutions

Console . . . . . . . . . . . . . . . . 21

Chapter 3. Specifying server and client

communications . . . . . . . . . . 25

Setting shared memory options . . . . . . . . 25

Setting TCP/IP options . . . . . . . . . . 26

Setting SNMP options . . . . . . . . . . . 27

Appendix A. National Language

Support . . . . . . . . . . . . . . 29

Installing a language package . . . . . . . . 29

Appendix B. Installing an IBM Tivoli

Storage Manager server fix pack . . . 33

Appendix C. Uninstalling the IBM Tivoli

Storage Manager server . . . . . . . 35

Before uninstalling IBM Tivoli Storage Manager . . 35

Removing IBM Tivoli Storage Manager . . . . . 35

Uninstalling Tivoli Storage Manager to return to an

earlier version . . . . . . . . . . . . . 36

Appendix D. Notices . . . . . . . . . 39

Trademarks . . . . . . . . . . . . . . 41

Index . . . . . . . . . . . . . . . 43

© Copyright IBM Corp. 1993, 2007 iii

|||

||

||

iv IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

Preface

This publication contains installation instructions for the Tivoli Storage Manager

server and the Integrated Solutions Console and Administration Center.

Who should read this guide

The target audience for this publication is a system administrator installing or

upgrading Tivoli Storage Manager.

In this book, it is assumed that you have an understanding of the following:

v The operating system on which the server will be installed

v Devices that Tivoli Storage Manager can use

v Workstation operating systems on which the clients reside

v Communication protocols installed on your client and server machines

Publications

Tivoli Storage Manager publications and other related publications are available

online.

You can search all the Tivoli Storage Manager publications in the Information

Center: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp

You can download PDF versions of publications from the IBM® Publications

Center:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order some related publications from this Web site. The Web site

provides information for ordering publications from countries other than the

United States. In the United States, you can order publications by calling

800-879-2755.

Tivoli Storage Manager publications

Tivoli Storage Manager server publications

Publication Title Order Number

IBM Tivoli Storage Manager Messages SC32-0140

IBM Tivoli Storage Manager Performance Tuning Guide SC32-0141

IBM Tivoli Storage Manager Problem Determination Guide SC32-0142

IBM Tivoli Storage Manager for AIX Installation Guide GC23-5969

IBM Tivoli Storage Manager for AIX Administrator’s Guide SC32-0117

IBM Tivoli Storage Manager for AIX Administrator’s Reference SC32-0123

IBM Tivoli Storage Manager for HP-UX Installation Guide GC23-5970

IBM Tivoli Storage Manager for HP-UX Administrator’s Guide SC32-0118

IBM Tivoli Storage Manager for HP-UX Administrator’s Reference SC32-0124

© Copyright IBM Corp. 1993, 2007 v

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp



Tivoli Storage Manager server publications


IBM Tivoli Storage Manager for Linux Installation Guide GC23-5971

IBM Tivoli Storage Manager for Linux Administrator’s Guide SC32-0119

IBM Tivoli Storage Manager for Linux Administrator’s Reference SC32-0125

IBM Tivoli Storage Manager for Sun Solaris Installation Guide GC23-5972

IBM Tivoli Storage Manager for Sun Solaris Administrator’s Guide SC32-0120

IBM Tivoli Storage Manager for Sun Solaris Administrator’s Reference SC32-0126

IBM Tivoli Storage Manager for Windows Installation Guide GC23-5973

IBM Tivoli Storage Manager for Windows Administrator’s Guide SC32-0121

IBM Tivoli Storage Manager for Windows Administrator’s Reference SC32-0127

IBM Tivoli Storage Manager for z/OS Installation Guide GC23-5974

IBM Tivoli Storage Manager for z/OS Administrator’s Guide SC32-0122

IBM Tivoli Storage Manager for z/OS Administrator’s Reference SC32-0128

IBM Tivoli Storage Manager for System Backup and Recovery Installation

and User’s Guide

SC32-6543

Tivoli Storage Manager storage agent publications


IBM Tivoli Storage Manager for SAN for AIX Storage Agent User’s

Guide

SC32-0129

IBM Tivoli Storage Manager for SAN for HP-UX Storage Agent User’s

Guide

SC32-0130

IBM Tivoli Storage Manager for SAN for Linux Storage Agent User’s

Guide

SC32-0131

IBM Tivoli Storage Manager for SAN for Sun Solaris Storage Agent

User’s Guide

SC32-0132

IBM Tivoli Storage Manager for SAN for Windows Storage Agent User’s

Guide

SC32-0133

Tivoli Storage Manager client publications


IBM Tivoli Storage Manager for Macintosh: Backup-Archive Clients

Installation and User’s Guide

SC32-0143

IBM Tivoli Storage Manager for NetWare: Backup-Archive Clients


SC32-0144

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive

Clients Installation and User’s Guide

SC32-0145

IBM Tivoli Storage Manager for Windows: Backup-Archive Clients


SC32-0146

IBM Tivoli Storage Manager for Space Management for UNIX and Linux:

User’s Guide

SC32-0148

IBM Tivoli Storage Manager for HSM for Windows Administration Guide SC32-1773

IBM Tivoli Storage Manager Using the Application Program Interface SC32-0147

vi IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

Tivoli Storage Manager Data Protection publications

Publication Title

Order

Number

IBM Tivoli Storage Manager for Advanced Copy Services: Data Protection for

Snapshot Devices for SAP Installation and User’s Guide for Oracle

SC33-8207


Snapshot Devices for DB2 Installation and User’s Guide

SC33-8330


WebSphere Application Server Installation and User’s Guide

SC32-9075

IBM Tivoli Storage Manager for Databases: Data Protection for Informix®


SH26-4095

IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL

Server Installation and User’s Guide

SC32-9059

IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX

and Linux Installation and User’s Guide

SC32-9064

IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for

Windows Installation and User’s Guide

SC32-9065

IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for

SAP Installation and User’s Guide for DB2

SC33-6341

IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for

SAP Installation and User’s Guide for Oracle

SC33-6340

IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise Storage

Server® for DB2 UDB Installation and User’s Guide

SC32-9060

IBM Tivoli Storage Manager for Hardware: Data Protection for Snapshot Devices

for Oracle Installation and User’s Guide

GC32-1772

IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino® for

UNIX, Linux, and OS/400® Installation and User’s Guide

SC32-9056

IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino for

Windows Installation and User’s Guide

SC32-9057

IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange

Server Installation and User’s Guide

SC32-9058

Support information

You can find support information for IBM products from a number of different

sources:

v “Getting technical training” on page viii

v “Searching knowledge bases” on page viii

v “Contacting IBM Software Support” on page ix

Preface vii

Getting technical training

Information about Tivoli® technical training courses is available online.

http://www.ibm.com/software/tivoli/education/

Searching knowledge bases

If you have a problem with Tivoli Storage Manager, there is a variety of

knowledge bases you can search.

You can begin with the Information Center, from which you can search all the

Tivoli Storage Manager publications: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp

Searching the Internet

If you cannot find an answer to your question in the information center, search the

Internet for the latest, most complete information that might help you resolve your

problem.

To search multiple Internet resources, go to the support web site for Tivoli Storage

Manager: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html. From this section, you can search a variety of

resources including:

v IBM technotes

v IBM downloads

v IBM Redbooks™

If you still cannot find the solution to your problem, you can search forums and

newsgroups on the Internet for the latest information that might help you resolve

your problem.

Using IBM Support Assistant

The IBM Support Assistant is a free, stand-alone application that you can install on

any workstation. You can then enhance the application by installing

product-specific plug-in modules for the IBM products you use.

The IBM Support Assistant helps you gather support information when you need

to open a problem management record (PMR), which you can then use to track the

problem. The product-specific plug-in modules provide you with the following

resources:

v Support links

v Education links

v Ability to submit problem management reports

For more information, see the IBM Support Assistant Web site at

http://www.ibm.com/software/support/isa/

viii IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

http://www.ibm.com/software/tivoli/education/



http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html


http://www.ibm.com/software/support/isa/

Finding product fixes

A product fix might be available to resolve your problem. You can determine what

fixes are available by checking the product support Web site.

1. Go to the IBM Software Support Web site: http://www.ibm.com/software/tivoli/products/storage-mgr/product-links.html

2. Click the Support Pages link for your Tivoli Storage Manager product.

3. Click Fixes for a list of fixes for your product.

4. Click the name of a fix to read the description and optionally download the fix.

Getting E-mail notification of product fixes

You can sign up to receive weekly E-mail notifications about fixes and other news

about IBM products.

1. From the support page for any IBM product, click My support in the

upper-right corner of the page.

2. If you have already registered, skip to the next step. If you have not registered,

click register in the upper-right corner of the support page to establish your

user ID and password.

3. Sign in to My support.

4. On the My support page, click Edit profiles in the left navigation pane, and

scroll to Select Mail Preferences. Select a product family and check the

appropriate boxes for the type of information you want.

5. Click Submit.

6. For E-mail notification for other products, repeat steps 4 and 5.

Contacting IBM Software Support

Before you contact IBM Software Support, you must have an active IBM software

maintenance contract, and you must be authorized to submit problems to IBM. The

type of software maintenance contract that you need depends on the type of

product you have.

v For IBM distributed software products (including, but not limited to, Tivoli,

Lotus®, and Rational® products, as well as DB2® and WebSphere® products that

run on Windows® or UNIX® operating systems), enroll in Passport Advantage®

in one of the following ways:

Online

Go to the Passport Advantage Web page (http://www.ibm.com/software/sw-lotus/services/cwepassport.nsf/wdocs/passporthome) and

click How to Enroll

By phone

For the phone number to call in your country, go to the IBM Contacts

Web page (http://techsupport.services.ibm.com/guides/contacts.html)

and click the name of your geographic region.v For IBM eServer™ software products (including, but not limited to, DB2 and

WebSphere products that run in zSeries®, pSeries®, and iSeries™ environments),

you can purchase a software maintenance agreement by working directly with

an IBM sales representative or an IBM Business Partner. For more information

about support for eServer software products, go to the IBM Technical Support

Advantage Web page: http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call

1-800-IBMSERV (1-800-426-7378) in the United States. For a list of telephone

Preface ix

http://www.ibm.com/software/tivoli/products/storage-mgr/product-links.html

http://www.ibm.com/software/tivoli/products/storage-mgr/product-links.html

http://www.ibm.com/software/sw-lotus/services/cwepassport.nsf/wdocs/passporthome

http://www.ibm.com/software/sw-lotus/services/cwepassport.nsf/wdocs/passporthome

http://techsupport.services.ibm.com/guides/contacts.html

http://www.ibm.com/servers/eserver/techsupport.html

numbers of people who provide support for your location, go to the IBM Contacts

Web page, http://techsupport.services.ibm.com/guides/contacts.html, and click

the name of your geographic region.

Perform these actions to contact IBM Software Support:

1. Determine the business impact of your problem.

2. Describe your problem and gather background information.

3. Submit your problem to IBM Software Support.

Determine the business impact

When you report a problem to IBM, you are asked to supply a severity level.

Therefore, you need to understand and assess the business impact of the problem

you are reporting.

Severity 1 Critical business impact: You are unable to use the program,

resulting in a critical impact on operations. This condition

requires an immediate solution.

Severity 2 Significant business impact: The program is usable but is

severely limited.

Severity 3 Some business impact: The program is usable with less

significant features (not critical to operations) unavailable.

Severity 4 Minimal business impact: The problem causes little impact on

operations, or a reasonable circumvention to the problem has

been implemented.

Describe your problem and gather background information

When explaining a problem to IBM, be as specific as possible. Include all relevant

background information so that IBM Software Support specialists can help you

solve the problem efficiently.

To save time, know the answers to these questions:

v What software versions were you running when the problem occurred?

v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.

v Can the problem be re-created? If so, what steps led to the failure?

v Have any changes been made to the system? For example, hardware, operating

system, networking software, and so on.

v Are you currently using a workaround for this problem? If so, be prepared to

explain it when you report the problem.

Submit your problem to IBM Software Support

You can submit your problem to IBM Software Support online or by phone.

Online

Go to the ″Submit and track problems″ page on the IBM Software Support

site http://www.ibm.com/software/support/probsub.html . Enter your

information into the appropriate problem submission tool.

By phone

For the phone number to call in your country, go to the contacts page of

the IBM Software Support Handbook on the Web and click the name of

your geographic region.

x IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

http://techsupport.services.ibm.com/guides/contacts.html

http://www.ibm.com/software/support/probsub.html

If the problem you submit is for a software defect or for missing or inaccurate

documentation, IBM Software Support creates an Authorized Program Analysis

Report (APAR). The APAR describes the problem in detail. Whenever possible,

IBM Software Support provides a workaround for you to implement until the

APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the

IBM product support Web pages daily, so that other users who experience the

same problem can benefit from the same resolutions.

Accessibility features

Accessibility features help a user who has a physical disability, such as restricted

mobility or limited vision, to use software products successfully. The major

accessibility features of Tivoli Storage Manager are described in this topic.

v Server and client command-line interfaces provide comprehensive control of

Tivoli Storage Manager using a keyboard.

v The Windows client-graphical interface can be navigated and operated using a

keyboard.

v The Web backup-archive client interface is HTML 4.0 compliant, and accessibility

is limited only by the choice of Internet browser.

v All user documentation is provided in HTML and PDF format. Descriptive text

is provided for all documentation images.

v The Tivoli Storage Manager for Windows Console follows Microsoft®

conventions for all keyboard navigation and access. Drag and Drop support is

handled using the Microsoft Windows Accessibility option known as

MouseKeys. For more information about MouseKeys and other Windows

accessibility options, please refer to the Windows Online Help (keyword:

MouseKeys).

Preface xi

xii IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

Technical Changes for Version 5 Release 5 — November 2007

The technical changes summarized here are only for changes that affect installation

for Tivoli Storage Manager Version 5.5.

Solaris Zones

Tivoli Storage Manager supports the Solaris Zones features, which is

available with Solaris Version 10. Utilizing Solaris Zones allows one or

more processes to run in isolation from other activities on the system by

containing them separately in zones. This isolation prevents processes

running within one zone from monitoring or affecting processes running in

other zones. For more information, see “Installing the server to Solaris

Zones” on page 4 and the Administrator’s Guide.

TCP/IP Version 6

Tivoli Storage Manager is now able to use TCP/IP Version 6 (IPv6) as its

communications protocol. IPv6 is interoperable with TCP/IP Version 4. You

can specify either IPv4 or both IPv4 and IPv6 in the COMMMETHOD

option when you start the server, storage agent, client, or API application.

The same port numbers are used by the server, storage agent, client, or API

application for both IPv4 and IPv6.

IPv6 address formats are acceptable for all functions that support IPv6.

However, if you use IPv6 addresses for functions that do not support IPv6,

communications will fail.

See the Administrator’s Reference for more information.

© Copyright IBM Corp. 1993, 2007 xiii

|

|

||

||||||||

|||||||

|||

|

xiv IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

Chapter 1. Installing IBM Tivoli Storage Manager

Install the Tivoli Storage Manager server and related components on the server

machine and Tivoli Storage Manager client code on every machine that will

transfer data to Tivoli Storage Manager server-managed storage.

System requirements

Learn about hardware and software requirements for installing Tivoli Storage

Manager server on a Sun Solaris system.

Minimum Hardware Requirements for Sun Ultra SPARC-based (sun4u

architecture):

v You have at least Sun Solaris 9 running in 64 bit mode on a Sun Ultra Sparc

machine with sun4u architecture, and with a minimum of 100 MB of free disk

storage in the installation directory and 128 MB of main memory.

Minimum Hardware Requirements for Sun Ultra SPARC-based processors

(sun4v architecture):

v You have at least Sun Solaris 10 running in 64 bit mode on sun4v architecture,

with a minimum of 100 MB of free disk storage in the installation directory and

256 MB of main memory.

Minimum Hardware Requirements for x64-based processors (AMD64 or EM64T

architecture):

v You have at least Sun Solaris 10 running in 64-bit mode on a machine with

AMD64 or EM64T architecture, with a minimum of 100 MB of free disk storage

in the installation directory and 256 MB of main memory.v The file system containing the /var/tmp directory has a minimum of 75 MB of

free disk space. This space is freed up after the installation completes.

v TCP/IP is installed and activated (TCP/IP is the default communication

method).

v You have a CD device available for installation.

v If you have an IBM 3570, 3590 or Ultrium tape library or drive, install the most

current device driver before you install Tivoli Storage Manager Version 5.5. You

can locate the device drivers at ftp://ftp.software.ibm.com/storage/devdrvr/

Attention

For requirements, supported devices, client code, and fixes, go to the Tivoli

Storage Manager Web site at http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

© Copyright IBM Corp. 1993, 2007 1

ftp://ftp.software.ibm.com/storage/devdrvr/



Evaluation (try and buy) product

A 30-day evaluation version (try and buy) CD provides the same functions as the

Tivoli Storage Manager standard licensed product. However, the licensing package

is not available with the try and buy product, and you are limited to 50 clients.

The Tivoli Storage Manager installation instructions apply to both the standard

licensed product and the CD try and buy product. You can apply maintenance to a

try and buy version of IBM Tivoli Storage Manager.

Note: The try and buy CD is available from your IBM SE or sales department.

To upgrade to the licensed product, do the following:

1. Mount the Tivoli Storage Manager licensed product CD in your CD drive.

2. Install the license package (TIVsmSlic)

Only the license file is installed, and no server or user data is lost. After installing

the license package, register any licensed features that you purchased.

Upgrading from the try and buy product

You can upgrade from a try and buy version of Tivoli Storage Manager to the

licensed product.

To upgrade to the licensed product, do the following:

1. Mount the Tivoli Storage Manager licensed product CD in your CD drive.

2. Install the license package: TIVsm-licenseTIVsmSlic. Only the license file is

installed; server or user data is not lost.

3. Register the licensed features that you have purchased.

Installing Tivoli Storage Manager

The installation procedure includes the Tivoli Storage Manager server and device

drivers when installing Tivoli Storage Manager for the first time.

If you are installing from the licensed product CD, the licensing component also

needs to be installed. For information on licensing, see “Registering licenses” on

page 7.

All active server or storage agent processes must be halted before installation can

proceed. Installation of Tivoli Storage Manager will be stopped if an active server

or storage agent process is detected, and an error message will be displayed.

During the installation or upgrade, the server may have appeared to have started.

This is part of the installation and you should not attempt any operations until the

installation is complete.

The default clients are registered with the following defaults:

Table 1. Tivoli Storage Manager Default clients

Client Name Password

Administrative admin admin

Backup-archive client client

See the Backup-Archive Clients Installation and User’s Guide for information on

installing the command line administrative and backup-archive clients.

2 IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

The default installation directories are:

v Tivoli Storage Manager server: /opt/tivoli/tsm/server/bin

v Tivoli Storage Manager Device Drivers: /opt/tivoli/tsm/devices/bin

v Tivoli Storage Manager server licenses: /opt/tivoli/tsm/server/bin

v Tivoli Storage Manager storage agent: /opt/tivoli/tsm/StorageAgent/bin

To install Tivoli Storage Manager:

1. Log in as the root user. If you do not log in as root, certain key Tivoli Storage

Manager functions will not work properly.

2. Insert the CD into the drive.

See the readme files in the CD root directory /cdrom.

3. Enter the following command to view a list of packages that you can install:

/usr/bin/pkginfo -ld /cdrom/cdrom0

The Tivoli Storage Manager server packages are:

TIVsmS

The base product with English language support. See Appendix A,

“National Language Support,” on page 29 for instructions about

starting the server in a language other than the server default language,

en_US.

TIVsmSdev

The device driver package. Install this package if you are using any

devices other than IBM 3490, 3580, and 3590 tape drives.

TIVsmSlic

The server license module.4. If you are ready to install the packages, enter the following command:

/usr/sbin/pkgadd -d /cdrom/cdrom0

You will be asked what you want to install: All, None, or Either. It is

recommended that you install all the packages by choosing the option All;

however, it is possible to install them separately. In this example the CD name

is /cdrom; yours may be different. You may make more than one selection at this

step.

Note:

a. Loading the server files can take several minutes, and it may take a

few minutes for the installation to begin after the server package has

been selected.

b. If you install TIVsmS before you install Sun language support, and

you set the locale to a non-English setting, the following errors will

display. You can ignore these messages. The order in which the

packages are installed will not affect the installation.

ANR0915E Unable to open language JA_JP for message formatting.

Error opening catalog ./dsmja_jp.cat,for language ja_jp

c. If you install TIVsmS before you install the Sun server licenses, the

following warning will display:

Chapter 1. Installing IBM Tivoli Storage Manager 3

|

|

|

ANR9613W Error loading /opt/tivoli/tsm/server/bin//./dsmreg64.sl

for Licensing function: ld.so.1: ./dsmserv:

fatal error: /opt/tivoli/tsm/server/bin//./dsmreg64.sl:

open failure: No file nor directory exists.

5. While the Tivoli Storage Manager server pack (TIVsmS) is being installed, the

following prompts will appear:

a. The install_server script will display the license agreement in the language

set by your operating system, and ask for you to accept it. To accept the

license agreement, press 1 followed by the Enter key.

b. The system issues this message:

This package contains scripts which will be executed with super-user (root)

permission during the process of installing the package.

Do you want to continue with the installation of this package?

Enter:

y

6. When the installation has completed successfully, enter the following

commands from a root user command prompt to eject the CD:

cd /

eject cdrom

7.

When you install or upgrade the server to Tivoli Storage Manager Version 5.5,

you must give each server a unique name. For example, if all of your servers

have the default name, SERVER1, you will only be able to add one of them to

the Administration Center.

Use the SET SERVERNAME command to specify the new server name. The

maximum length of the name is 64 characters.

For example, to name the server WELLS_DESIGN_DEPT, start the server and

issue this command:

set servername wells_design_dept

To start the server from the /opt/tivoli/tsm/server/bin directory, enter:

./dsmserv

See the Administrator’s Reference for more details on this command.

Installing the server to Solaris Zones

The Tivoli Storage Manager Version 5.5 server supports the Solaris Zone feature.

There are two different types of supported zones: global and non-global.

The global zone is the default zone on a Solaris host system and controls system

resources. Non-global zones can be created and controlled from the global zone

and they run processes in isolation on the same host system.

To install the Tivoli Storage Manager server to either the global zone or a

non-global zone, log in to the zone in which you want to install the server, and

complete the normal installation process for your system. You can install the server

to more than one zone by completing each installation separately. The Tivoli


|

||

|||

||||

Storage Manager server is installed only to the current zone and ignores the –G

option if it is specified with the pkgadd command.

You can install different versions of the Tivoli Storage Manager server to different

zones. Databases created on Solaris Version 9 SPARC systems can be migrated to

any zone in a Solaris Version 10 SPARC environment but cannot be migrated to

zones in a Solaris Version 10 x64 environment.

For information on installing the Tivoli Storage Manager device driver to a Solaris

Zone, see the Administrator’s Guide. For more information on Solaris Zones, see

your Solaris system administration documentation.

Verifying your installation

You can verify your server installation by issuing several QUERY commands from

either the server console or from an administrative client. Once installed, the server

runs in the background, so you must start the server in the foreground or use an

administrative client to issue the commands.

You can verify server installation by issuing five QUERY commands. Start the

server first. To start the server from the /opt/tivoli/tsm/server/bin directory, enter:

./dsmserv

v QUERY STATUS (shows if the server is enabled)

query status format=detailed

v QUERY STGPOOL (shows the storage pools automatically set up by the

installation)

query stgpool format=detailed

v QUERY DB (shows a basic database set up by the installation)

query db format=detailed

v QUERY LOG (shows a basic recovery log set up by the installation)

query log format=detailed

v QUERY OPTION (shows options set up in dsmserv.opt file)

query option format=detailed

You can verify the complete Tivoli Storage Manager installation by backing up

client data from the default backup-archive client.

Attention Do not select files to back up that exceed your storage pool capacity. A 10

MB backup storage pool and a 5 MB archive storage pool were allocated at

installation.

1. The server must be running before you can use the administrative and

backup-archive clients.


||

||||

|||


./dsmserv

2. Start the backup-archive client graphical user interface by entering the

following command from a root user:

dsmj

The backup-archive client created at server installation is named client and has

the password client.

3. To back up several files, perform the steps listed below. These steps illustrate

two procedures for backing up from a client. For more detailed information

and other backup procedures, see the appropriate Tivoli Storage Manager client

manual.

a. Click Backup. The Backup window displays.

b. You can select files from a directory tree, or you search a drive or directory

to select files:

v To select files from a directory tree, expand the tree and click on the files

you want to back up.

v To search for files, do the following:

1) Click Find icon on the tool bar. The Find Files (Backup) window

displays

2) Enter your search criteria in the Find Files (Backup) window.

3) Click Search. The Matching Files (Backup) window displays.

4) Click the selection boxes next to the files you want to back up.

5) Close the Matching Files (Backup) window by clicking the

backup-archive icon on the menu bar and selecting Close.c. Click Always Backup from the Type of Backup list.

d. Click Backup. The Backup Status window displays the backup processing

status. You will receive a message when the backup has completed

successfully.

Starting and stopping the server

Issue one command to start the Tivoli Storage Manager server and another to halt

the Tivoli Storage Manager server.


./dsmserv

You can stop the server without warning if an unexpected problem requires you to

return control to the operating system. To avoid losing administrative and client

node connections, stop the server only after current sessions have completed or

been cancelled.

To stop the server, issue the following from an administrative command line:

halt


Registering licenses

You should immediately register any Tivoli Storage Manager licensed functions

that you purchase so you do not lose any data once you begin backing up to the

server. Use the REGISTER LICENSE command for this task.

Upgrading to Tivoli Storage Manager Version 5.5

If you have an earlier version of the Tivoli Storage Manager server, it must be

uninstalled prior to upgrading to Tivoli Storage Manager Version 5.5. To return to

an earlier version of Tivoli Storage Manager, after an upgrade, you must have a

full database backup of that original version and the installation code for the

server of that original version.

The default installation directories changed starting with Tivoli Storage Manager

Version 4.1. If you used disaster recovery manager (DRM) with a version earlier

than Version 4.1, your disaster recovery plan file refers to path names that might

not be valid after you install the latest version of the server. After you install Tivoli

Storage Manager, back up your storage pools and database and create a new

disaster recovery plan file. For the sequence and details of the procedure, see the

disaster recovery manager chapter in the Administrator’s Guide.

v You can use the DSMSERV RESTORE DB utility to restore older versions of

Tivoli Storage Manager databases where needed; this utility will perform

database restores from earlier releases or versions of the product. If an error is

encountered, contact IBM support to diagnose the cause of the restore database

failure and resolve it if possible. Note that the database backup needs to be on a

currently supported device, as IBM does not support being able to read from

devices that are no longer available.

Be aware of the results of returning to an earlier version of the server:

v References to client files that were backed up, archived, or upgraded to the

Tivoli Storage Manager Version 5.5 server will be lost.

v While running Tivoli Storage Manager Version 5.5, some existing volumes might

be overwritten or deleted due to operations such as migration, reclamation, a

MOVE DATA command, or a DELETE VOLUME command. If so, client files

that were on those volumes will no longer be accessible to the earlier version of

the server.

v Definitions, updates, and deletions of objects performed on the Version 5.5

server will be lost.

Compatibility with other versions of IBM Tivoli Storage

Manager

Ensure that your Tivoli Storage Manager server and the storage agent can function

together by checking compatibility restrictions.

To ensure compatibility between the server and the storage agent, check the Tivoli

Web site at the following address: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html . You can also check that Web

site for maintenance level requirements and to download the latest fix pack.

The Tivoli Storage Manager servers for the z/OS®, AIX®, HP-UX, Linux®, Sun

Solaris, and Windows operating systems support LAN-free data movement.




The Tivoli Storage Manager server and storage agent are not backwards compatible

with prior releases of the server and storage agent. If you have implemented

library sharing, server-to-server, enterprise configuration, or LAN-free, it is

important to note that all Tivoli Storage Manager servers and storage agents must

be upgraded to a compatible and supported level of Version 5.3 or later before

invoking any Version 5.3 library sharing, server-to-server, or LAN-free

communication.

When upgrading multiple servers that participate in library sharing to Version 5.3

and later, the servers acting as library manager must be upgraded first to maintain

compatibility among the servers acting as library clients or storage agents. When

upgrading multiple servers participating in server-to-server to Version 5.3 or later,

all servers must be upgraded at the same time.

As a general rule, the Tivoli Storage Manager server normally supports storage

agents and library clients at the same version, release, and modification level down

to the modification level minus two. When the product release changes, Tivoli

Storage Manager normally supports the last two maintenance releases of the

previous release. For example, a Tivoli Storage Manager Version 5.5 server

supports storage agents and library clients at the Version 5.4.0, Version 5.3.5, and

Version 5.3.4 level. An exception to this rule is when a fix or a product

enhancement requires concurrent code changes to the server, storage agent, and

library client.

A Version 5.3 and later server acting as a library manager is compatible with

Version 5.2 and 5.1 servers acting as library clients. However, Version 5.3 and later

servers acting as library clients remain incompatible with Version 5.2 and Version

5.1 servers acting as library managers. When upgrading multiple servers that

participate in library sharing to Version 5.3 or later, the servers acting as library

managers must be upgraded first to maintain compatibility among the servers.

Before performing an upgrade

You can install Tivoli Storage Manager Version 5.5 over a previous version of Tivoli

Storage Manager, upgrading your server.

This section describes several items to consider before you perform an upgrade.

v The dsmserv.dsk file points to the locations of the current database and recovery

log volumes. An upgrade will not normally create a new database, recovery log,

and storage pool volumes. If the dsmserv.dsk file is not installed, the install

creates the following volumes in the /opt/tivoli/tsm/server/bin directory:

– Database volume (db.dsm)

– Recovery log volume (log.dsm)

– Storage pool volumes (sbkup00.dsm and sarch00.dsm)

For Tivoli Storage Manager Version 5.3 and later, the dsmserv.dsk file is in

/opt/tivoli/tsm/server/bin. To use your existing database, recovery log, and storage

pool volumes, ensure that there is a copy of the dsmserv.dsk file and that the

filesystem is mounted before you do an upgrade. You must not move the

database, recovery log, and storage pool volumes.

v If you decide to return to the previous version of Tivoli Storage Manager, you

must have a backup copy of your previous database, volume history, and device

configuration files. In the following example, the tape device class named

TAPECLASS is used for database backups.


backup db type=full devclass=tapeclass

backup devconfig filenames=devconfig.jan99

backup volhistory filenames=volhistory.jan99

Note: This command retrieves database records into a database dump. This

process does not access the recovery log. Transactions held in the recovery

log are lost.

Store the output volumes and the device configuration and volume history files

in a safe location.

v During an upgrade from versions before 4.1 the following files are automatically

copied to the location of the new Tivoli Storage Manager installation:

– The dsmserv.dsk file

– The Tivoli Storage Manager accounting log file (dsmaccnt.log), if you have

accounting turned on.

– The server options file dsmserv.opt

– An existing device configuration file if it is named devconfig

– An existing volume history file if it is named volhist

If your device configuration and volume history files are not named devconfig

and volhist respectively, back up the files and save them in a temporary

directory. You can later edit the new server options file to include the names of

these files.

You should also save in a temporary directory any existing runfile scripts.

Performing an upgrade

Before migrating the Tivoli Storage Manager server to the new level, perform some

clean up by running the EXPIRE INVENTORY command.

If your server is currently at a release earlier than Version 5.3, there might be

additional steps you should take in preparation for migration to Version 5.5. Search

the support site at http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html for more information.

You can upgrade directly to Tivoli Storage Manager Version 5.5 from any previous

version of Tivoli Storage Manager. The amount of time to upgrade from version 5.4

to 5.5 is negligible. The change in database size between version 5.4 and 5.5 is also

negligible. Versions earlier than 5.3 will take longer to upgrade. The older the

version, the longer this process will take. If migrating to Tivoli Storage Manager

from any previous release, you should take actions to clean up system objects.

1. Consider whether you need to install any operating system patches or a new

operating system level before installing the latest Tivoli Storage Manager

server.

2. Back up critical server information by using the BACKUP DB, BACKUP

DEVCONFIG, and BACKUP VOLHIST commands. For example, the following

commands back up device configuration information to files that you have

identified in the dsmserv.opt file, with the DEVCONFIG option.

backup devconfig

Or, you can specify file names with this command.

backup devconfig filename=filename


||



The following command backs up volume history information to files that you

have identified in the dsmserv.opt file, with the VOLUMEHISTORY option.

Like with the BACKUP DEVCONFIG command, file names may be specified.

backup volhistory

The following command creates a full backup of the server database to a

specified tape device.

backup db type=full devclass=tape_device

If you need to revert to a previous release, you will have to restore from this

database backup.

3. Save the following important files, which are in the default directory for the

Tivoli Storage Manager server:

volhist (file name depends on what you specified with the

backup volhistory command)

devconfig (file name depends on what you specified with the

backup devconfig command)

dsmserv.opt

dsmserv.dsk

4. Ensure that no tapes are mounted. Use the QUERY MOUNT command. If any

tapes are running, use the DISMOUNT VOLUME command and specify the

volume name.

5. Ensure that no Tivoli Storage Manager processes are running. Use the QUERY

PROCESS command. Cancel processes if needed, by using CANCEL PROCESS

process-number. Installation stops if any Tivoli Storage Manager processes are

running.

6. You can find the Tivoli Storage Manager server process ID by displaying the

content of the following file on UNIX. For example:

ps - ef | grep dsm

7. Stop the server if it is running by entering the following from the server

console:

halt

If you started the server as a background process, connect to the server as an

administrative client and issue the HALT command.

Note: Installation will be stopped and an error message displayed if an active

server or storage agent process is detected. All active server or storage

agent processes must be halted before installation can proceed.

8. To install a new package, uninstall the existing Tivoli Storage Manager version

on your machine and install the new one in the same directory. The

installation process is similar for all of the Tivoli Storage Manager server,

Tivoli Storage Manager storage agent, and Tivoli Storage Manager device

driver packages but examples will not be cited for all packages. Use the

Solaris utility pkgrm to remove old Tivoli Storage Manager packages before

updates. For example:

- pkgrm TIVsmS

or

- pkgrm TIVsmSdev

or

- pkgrm TIVsmSsta

Also see Appendix C, “Uninstalling the IBM Tivoli Storage Manager server,”

on page 35. A list of installed Tivoli Storage Manager packages can be

obtained by using ″pkginfo | grep TIVsmS.″


9. Verify that all Tivoli Storage Manager code is removed from the machine.

10. If a distribution file is supplied with the extension of .pkg.z it must be

uncompressed for an installable package. For example:

- uncompress filename

If a distribution is supplied with the extension of .tar.Z, it must be extracted

for an installable package. Create a temporary directory and extract the

package. For example:

- mkdir /tmp/TSM

- cd /tmp/TSM

- uncompress -dc filename | tar xvf -

11. If the installable package (.pkg) is supplied on a CD or extracted from a .tar.Z

file, issue the following command:

pkgadd -d /<package location>/<package name>

For example:

- pkgadd -d /cdrom/TSMSTA5500_SUN.pkg

OR

- cd packagedirectory

pkgadd -d TSMSTA5500_SUN.pkg

A list of packages will be displayed as part of the installation and can be

selected interactively. On any package containing the Tivoli Storage Manager

server it is required that you accept license agreement terms. You will be

prompted to read the license agreement and agree to it before installation

succeeds.

12. Check the Readme for any special instructions or specific information for your

operating system.

13. If you have created scripts that have paths to /opt/lpp/adsmserv/bin, change the

paths to /opt/tivoli/tsm/server/bin.

14. Install the latest Tivoli Storage Manager server software (see “Installing Tivoli

Storage Manager” on page 2).

Note: Until the new version is installed and any required licenses are

reregistered (step 17), clients will not be able to connect to the server.

15. Optional: Load sample server scripts into the database. Tivoli Storage

Manager is shipped with sample command scripts that can be loaded into the

database and run from an administrative client, or server console. They can

also be included in administrative command schedules. The sample scripts, in

scripts.smp, are primarily SELECT queries.

Note: The sample scripts might have been loaded when a previous version of

Tivoli Storage Manager was installed. Loading the sample scripts again

at this point will overlay any existing scripts of the same name, and

any modifications made to those scripts will be lost.

To load the sample scripts into the database, issue the following command:

./dsmserv runfile /opt/tivoli/tsm/server/bin/scripts.smp

16. Verify that the installation was successful by starting the server.

./dsmserv

17. Register licenses. Your licenses from the previous version are no longer valid

and must be registered again. See “Registering licenses” on page 7.


||

|

|

|

|

|

|

|||||

Note: The TIVsmSlic package is required to register licenses. This package is

not automatically installed when you install the server package.

Running multiple servers on a single machine

To run multiple Tivoli Storage Manager servers on the same machine, enter the

DSMSERV FORMAT command from different directories to create multiple pairs of

recovery log and database files. Do not attempt to install the server executable files

in more than one directory.

The following procedure shows how you can set up an additional Tivoli Storage

Manager server:

1. Determine the directory where you want the server files created, for example:

/opt/myserver, and create that directory.

mkdir /opt/myserver

2. Copy the dsmserv.opt file to your directory (myserver).

cp /opt/tivoli/tsm/server/bin/dsmserv.opt /opt/myserver/dsmserv.opt

Note: Open the dsmserv.opt file and ensure that the communication method

parameters are different from those of the existing Tivoli Storage

Manager servers. For example, the servers cannot use the same

TCPPORT, HTTPPORT, or NDMPCONTROLPORT. Additionally, make

sure that the volhist and devconfig files are pointing to the new server

directory.

3. Define your environment variables, for example:

a. To define the DSMSERV_DIR, enter:

DSMSERV_DIR=/opt/tivoli/tsm/server/bin

export DSMSERV_DIR

Verify that the variable exported correctly.

b. To define the DSMSERV_CONFIG to point to the server options file, enter:

DSMSERV_CONFIG=/opt/myserver/dsmserv.opt

export DSMSERV_CONFIG

4. Enter this in the new server directory. Format the database and recovery log

files, for example:

/opt/myserver/dsmfmt/dsmfmt -m -db dbvol2 5

/opt/myserver/dsmfmt/dsmfmt -m -log logvol2 9

5. Create the database and recovery log in the desired directory for the new

server, for example:

/opt/myserver/dsmfmt/dsmserv format 1 logvol2 1 dbvol2

6. You must be in the correct subdirectory to invoke the appropriate server with

the dsmserv command. See the Administrator’s Guide for more information.

7. In order to access the new server from the administrative client:

a. Create a new entry in the dsm.sys file and include the new server

information.


b. Enter the following command:

dsmadmc -server=newservername

Note:

1. You will need additional license authorizations to run additional servers.

2. When the server is started, it searches the current directory for the

existence of the dsmserv.dsk file. If the file is found, the names of the

recovery log and database files are used for server operation. If the

dsmserv.dsk file is not found in the current directory, Tivoli Storage

Manager issues an error message (ANR0212E) and server initialization

stops.

Defining environment variables

If you want to run the Tivoli Storage Manager server from a directory other than

the default directory or to run multiple servers, you may have to define

environment variables.

An environment variable describes the operating environment of a process, such as

the home directory or the terminal in use. It provides the path that the server

requires to find and create files.

For example, to define the DSMSERV_DIR environment variable to point to the

/opt/tivoli/tsm/server/bin directory so that the server can find various server files:

export DSMSERV_DIR=/opt/tivoli/tsm/server/bin

You can also define an environment variable to point to the server options file. For

example, to define the DSMSERV_CONFIG environment variable to point to the

server options file, enter:

export DSMSERV_CONFIG=/opt/myserver/bin/filename.opt

where filename is the name you assigned your server options file (dsmserv.opt).



Chapter 2. Installing the Integrated Solutions Console and the

Administration Center

Before you install the Integrated Solutions Console and the Administration Center,

you must install, configure, and start the Tivoli Storage Manager server. Install the

Integrated Solutions Console Version 6.0.1.1 before installing the Administration

Center.

The installation wizards for the Integrated Solutions Console and the

Administration Center are on separate CDs. The Integrated Solutions Console is

only available through your regular order system such as Passport Advantage or

the Advanced Administrative System (AAS). If you obtain your IBM software

electronically through Passport Advantage, you must have an authorized user ID

and password.

After both applications are installed, you will be able to administer Tivoli Storage

Manager from anywhere in your network through a web browser.

You can obtain the Release Notes in the IBM Tivoli Storage Manager Information

Center: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp

System requirements

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. If the system meets the

combined requirements for the server and the Administration Center, it can

support both applications.

If you plan to use the Administration Center to manage an environment with a

large number of servers or administrators, consider installing the Administration

Center on a separate system.

For Administration Center system requirements, see the following Web site:

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

Configuring the IP address

The Administration Center assumes that the host system is using a static IP

address instead of a dynamically assigned IP address. A static IP address is

necessary because the Administration Center server must be listed on the domain

name servers, which map the host name to the physical address of the system.

On a system that is not connected to the network, you must configure your system

so that the IP loopback port is mapped to the fully-qualified host name. To enable

that mapping, perform the following procedure on the system where the

Administration Center will be installed.

1. Locate the TCP/IP host file on your system.

Look in /etc/hosts.

2. Use a text editor. Open the host file and add lines similar to the following at

the end:


|

|||||

|||

||


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

127.0.0.1 localhost

127.0.0.1 your.server.name

where your.server.name is the fully-qualified host name for the Administration

Center system.

3. Save the host file.

Overview: installing the Integrated Solutions Console and the

Administration Center

The time required to install the Integrated Solutions Console depends on the speed

of your processor and the memory in your machine.

There are six basic steps for setting up the Integrated Solutions Console and the

Administration Center.

1. Install and start your Tivoli Storage Manager Version 5.5 servers. Give each

server a unique name.

2. Use the Integrated Solutions Console CD or image to install the Integrated

Solutions Console. During the installation process, create an Integrated

Solutions Console user ID and password.

3. Use the Administration Center CD or image to install the Administration

Center, on the same system as the Integrated Solutions Console.

4. Log onto the Integrated Solutions Console using a Web browser. You can then

administer Tivoli Storage Manager from a browser anywhere in your network.

5. Add connections for the Tivoli Storage Manager servers you want to manage.

6. The default Integrated Solutions Console ID is iscadmin. You must specify a

password for this ID. You can create additional Integrated Solutions Console

user IDs and passwords for any other administrators who will access the


For more details about the Administration Center, see http://www.ibm.com/support/.

Installing the Integrated Solutions Console

Integrated Solutions Console 6.0.1.1 is required to use the Administration Center

and it needs to be installed before installing the Administration Center. If an earlier

version of the Integrated Solutions Console is already installed, you must upgrade

to Version 6.0.1.1.

The time for the installation process to complete depends on the speed of your

processor and memory.

The Integrated Solutions Console installation media and the Administration Center

should be extracted to different directories.

To install the Integrated Solutions Console from a CD, do the following steps:

1. Insert the Integrated Solutions Console CD in your CD drive.

2. Open the setup.bin file with your browser.

Note: If you have multiple CD devices defined, the device may be cdrom0 or

cdrom1, depending on the number of devices defined.


http://www.ibm.com/support/search.wss?rs=663&tc=SSGSG7&atrn=Keywords&atrv=ServerRequirements

http://www.ibm.com/support/search.wss?rs=663&tc=SSGSG7&atrn=Keywords&atrv=ServerRequirements

3. Open a command window or go to a command prompt. Change to the CD

directory.

4. Enter one of the following commands to install the Integrated Solutions

Console:

v For the installation wizard : setupISC

v For the console installation wizard :setupISC -console

v For silent installation, enter the following command on a single line:

setupISC -silent -W ConfigInput.adminName="user name"

-W ConfigInput.adminPass="user password"

-W ConfigInput.verifyPass="user password"

-W PortInput.webAdminPort="web administration port"

-W PortInput.secureAdminPort="secure administration port"

-W MediaLocationInput.installMediaLocation="media location"

-P ISCProduct.installLocation="install location"

Note: An installation wizard can be used if you have X-Windows or a similar

program through which to bring up an interface. A console installation

wizard is used via the command line.

5. Release the CD. Make sure you are no longer in the CD directory, then eject

cdrom0.

6. If your system is configured to use a browser, go to the following URL, which

will display the logon screen for the Integrated Solutions Console:

http://machine_name:8421/ibm/console. This indicates a successful installation

of the Integrated Solutions Console.

Note: Auto mounting a cd multiple times can cause the ’#’ character to appear

in the cd path. For example:

first mount of the Integrated Solutions Console Install CD:

/cdrom/lk4t-0344-00

second mount of Integrated Solutions Console Install CD:

/cdrom/lk4t-0344-00#1

The ’#’ character in the installation path will cause the jvm not to extract.

To prevent installation failures, run the following commands between cd

mounts:

/etc/init.d/volmgt stop

/etc/init.d/volmgt start

7. If you are upgrading to the Integrated Solutions Console Version 6.0.1.1, you

must also upgrade the Administration Center to Version 5.5.0.0. Your Integrated

Solutions Console Version 5.1 directory will not be removed because it contains

log files. After your upgrade completes successfully, you can delete this

directory.

8. There is a possibility that the Integrated Solutions Console Version 5.1 will not

properly uninstall, following the upgrade. If you encounter this situation, you

might need to do the following.

v Stop all Integrated Solutions Console and Java™ processes related to the

Integrated Solutions Console.

v Delete the Integrated Solutions Console 5.1 directory (/opt/IBM/ISC) and its

subdirectories.

v Start the Integrated Solutions Console 6.0.1.1 process. See “Starting and

stopping the console server and console help server” on page 20.

To install the Integrated Solutions Console from an image, do the following steps:

Chapter 2. Installing the Integrated Solutions Console and the Administration Center 17

1. Change to the directory where you placed the image and issue the following

commands to extract the files:

chmod u+x file_name.bin

file_name.bin

where file_name is the name of the electronic Integrated Solutions Console bin

file.

2. Enter one of the following commands to install the Integrated Solutions

Console:

v For the installation wizard : setupISC

v For the console installation wizard :setupISC -console

v For silent installation, enter the following command on a single line:

setupISC -silent -W ConfigInput.adminName="user name"

-W ConfigInput.adminPass="user password"

-W ConfigInput.verifyPass="user password"


-W PortInput.secureAdminPort="secure administration port"

-W MediaLocationInput.installMediaLocation="media location"

-P ISCProduct.installLocation="install location"

Note: An installation wizard can be used if you have X-Windows or a similar

program through which to bring up an interface. A console installation

wizard is used via the command line.

3. If your system is configured to use a browser, go to the following URL, which

will display the logon screen for the Integrated Solutions Console:

http://machine_name:8421/ibm/console. This indicates a successful installation

of the Integrated Solutions Console.

4. If you are upgrading to the Integrated Solutions Console Version 6.0.1.1, you

must also upgrade the Administration Center to Version 5.5.0.0. Your Integrated

Solutions Console Version 5.1 directory will not be removed because it contains

log files. After your upgrade completes successfully, you can delete this

directory.

5. There is a possibility that the Integrated Solutions Console Version 5.1 will not

properly uninstall, following the upgrade. If you encounter this situation, you

might need to do the following.

v Stop all Integrated Solutions Console and Java processes related to the

Integrated Solutions Console.

v Delete the Integrated Solutions Console 5.1 directory (/opt/IBM/ISC) and its

subdirectories.

v Start the Integrated Solutions Console 6.0.1.1 process. See “Starting and

stopping the console server and console help server” on page 20.

Installing and upgrading the Administration Center

The Integrated Solutions Console must be running when you install or upgrade the


The Administration Center can display information in languages other than

English. You can enable language support during installation. If this support is

enabled, the Administration Center attempts to display the same language as the

Web browser used to access it. If the Web browser uses a different language than

the Tivoli Storage Manager server, some information will be displayed in the

language used by the server. To change the default language used by the Web

browser, see the browser documentation.


To install the Administration Center from a CD, do the following steps:

1. Insert the CD in your CD drive.

2. Open a command window or go to a command prompt.

3. Change the directory to the CD directory.

4. Run one of the following commands to install the Administration Center:

v For the installation wizard : startInstall.sh

v For the console installation wizard : startInstall.sh -console

v For silent install, enter the following command on a single line:

startInstall.sh -silent -W AdminNamePanel.adminName="user name"

-W Passwordinput.adminPass="user password"

-W Passwordinput.verifyPass="user password"

-W MediaLocationInput.InstallMediaLocation="media location"


-P AdminCenterdeploy.installLocation="install location"

5. To release the CD, make sure you are no longer in the CD directory, then issue

the following command: eject cdrom0.

Note: Automounting a cd multiple times can cause the ’#’ character to appear in

the cd path. For example:

first mount of the Integrated Solutions Console Install CD:

/cdrom/lk4t-0344-00

second mount of Integrated Solutions Console Install CD:

/cdrom/lk4t-0344-00#1

The ’#’ character in the installation path will cause the jvm not to extract. To

prevent installation failures, run the following commands between cd

mounts:

/etc/init.d/volmgt stop

/etc/init.d/volmgt start

To install the Administration Center from an image, do the following steps:


2. If you are installing from an image with the 5.5.0.0-TIV-TSMAC-MULTI.tar

file, issue the following command:

tar -xf 5.5.0.0-TIV-TSMAC-MULTI.tar

3. Run one of the following commands to install the Administration Center:

v For the installation wizard : startInstall.sh

v For the console installation wizard : startInstall.sh -console

v For silent install, enter the following command on a single line:

startInstall.sh -silent -W AdminNamePanel.adminName="user name"

-W Passwordinput.adminPass="user password"

-W Passwordinput.verifyPass="user password"

-W MediaLocationInput.InstallMediaLocation="media location"


-P AdminCenterdeploy.installLocation="install location"


Verifying your installation

After installing the Integrated Solutions Console and Administration Center,

conduct several procedures to verify your installation.

Perform the following steps:

1. Enter the following address in a supported Web browser: http://machine_name:8421/ibm/console. The machine_name is the network name or IP

address of the machine on which you installed the Administration Center. The

default Web administration port (HTTP) is 8421. The default secure Web

administration port (HTTPS) is 8422.

2. To get started, log in using the Integrated Solutions Console user ID and

password you created during the installation. After you successfully log in, the

Integrated Solutions Console welcome page is displayed. Expand the Tivoli

Storage Manager folder in the Work Items list and click Getting Started to

display the Tivoli Storage Manager welcome page. This page provides

instructions for using the Administration Center.

Starting and stopping the console server and console help

server

The Integrated Solutions Console server and help are automatically started after a

successful installation. If you shut down the system after the initial installation,

any Integrated Solutions Console servers that were started will be stopped.

This section describes the commands you use to start and stop Integrated Solutions

Console servers.

In the following commands, the variables have these meanings:

v isc_home is the root directory for your Integrated Solutions Console installation.

v iscadmin is the administrator user ID for Administration Center if the installation

uses the WebSphere Application Server embedded in the console runtime. If the

installation uses a separate WebSphere Application Server installation,

administrator is the administrator user ID for the WebSphere Application Server

installation.

v iscpass is the password for the administrator.

To start Integrated Solutions Console system servers, complete the following steps:

1. Change your directory to isc_home/PortalServer/bin

2. Run the shell script startISC.sh ISC_Portal

To stop Integrated Solutions Console system servers, complete the following steps:

1. Change your directory to isc_home/PortalServer/bin

2. Run the shell script stopISC.sh ISC_Portal iscadmin iscpass

Note: It may take a few minutes for the service to stop even though the service

manager indicates the server is stopped.


|||

|

Uninstalling the Administration Center

Uninstall the Administration Center before uninstalling the Integrated Solutions

Console. There is a separate procedure for removing the Integrated Solutions

Console.



v iscadmin is the administrator user ID for Administration Center if the

installation uses the WebSphere Application Server embedded in the console

runtime. If the installation uses a separate WebSphere Application Server

installation, administrator is the administrator user ID for the WebSphere

Application Server installation.


Note: The Integrated Solutions Console must be running when you uninstall the


1. Open a command window or go to a command prompt and change to the root

directory for your Integrated Solutions Console installation. For example:

cd isc_home

2. Run the following command:

acuninst.sh iscadmin iscpass

Uninstalling the Integrated Solutions Console

Before uninstalling the Integrated Solutions Console, you must uninstall the


Note: To uninstall the Administration Center, see “Uninstalling the Administration

Center”

1. In the following command, the variable isc_home is the root directory for your

Integrated Solutions Console installation. Open a command window or go to a

command prompt and change to the following directory:

cd isc_home/_iscuninst

2. Run one of the following commands to uninstall the Integrated Solutions

Console:

v To run the uninstall wizard: uninstaller

v To run the console uninstall wizard: uninstaller -console

v To perform a silent uninstall: uninstaller -silent

Manually uninstalling the Integrated Solutions Console

If the installation program fails or you are unable to uninstall with the wizard, you

can try manually removing the Integrated Solutions Console and then installing it

again.



v iscadmin is the administrator user ID for Administration Center if the installation

uses the WebSphere Application Server embedded in the console runtime. If the


installation uses a separate WebSphere Application Server installation,

administrator is the administrator user ID for the WebSphere Application Server

installation.


Perform the following steps to manually uninstall the Integrated Solutions Console:


2. Stop the console server (which is the application server named ISC_Portal) by

issuing the following command:

isc_home/PortalServer/bin/stopISC.bat ISC_Portal iscadmin iscpass

3. Stop the application server named server1 by issuing the following command

on a single line:

isc_home/AppServer/bin/stopServer.sh server1 -user

application_server_administrator -password

application_server_password

4. Clean the system temporary directory by performing the following steps:

a. Change to the system temporary directory. The temporary directory is the

value of the operating system variable /tmp.

b. Save a copy of the following files in the temporary directory:

v ISCRuntimeInstall.log

v ISCRuntime.rsp

v ISCRuntimeUninstall.log

v All of the Portal*.log filesc. In the temporary directory, delete all of the files and the directories that

begin with the string ISC (such as ISCRuntime.rsp, ISC_TEMP,

ISCToolkitInstall.log) and all files that begin with the string Portal (such as

PortalInit.log and PortalSetupWAS.log). 5. Clean the registry that InstallShield for Multiplatforms uses by performing the

following steps:

a. Search for the vpd.properties file.

b. Save a copy of the vpd.properties file.

c. Use a text editor to open the vpd.properties file.

Note: Use an editor that does not wrap lines so that you can easily isolate

single lines for removal.

Set the editor to use a monospace font (for example, Courier). This makes

it easier to see the file structure.

d. Delete each line that refers to the path for the root directory of the console

runtime. If there are no remaining lines in vpd.properties, leave the file

empty or delete it. 6. To manually disable automatic restart at reboot of the console and console

server, edit the operating system file /etc/inittab to remove the following line:

isc6:23:boot:isc_home/PortalServer/bin/startISC.sh ISC_Portal

ISCUSER ISCPASS

7. Stop all Java processes for the Integrated Solutions Console by performing the

following steps:

a. Issue the following command to find the processes that are using

isc_home/AppServer/java/bin/java.exe:

ps -ef | grep java

b. Stop all of those processes.


Note: There may be other Java processes running for other applications.

8. Run the following commands to locate entries in the operating system

package registry:

cd /var/sadm/pkg

grep -l BASEDIR=isc_home/PortalServer$ ./*/pkginfo

9. Delete each directory that contains a pkginfo file found by the grep command.

This step will allow a successful re-install.

10. Delete the environment variable isc_home. Issue the following command:

unset isc_home

11. Delete the root directory for the Integrated Solutions Console.



Chapter 3. Specifying server and client communications

A default sample server options file, dsmserv.opt.smp, is created during Tivoli

Storage Manager installation. To set up communications between the server and

clients, you must create a new server options file by copying the sample file.

Name the new file dsmserv.opt and edit the options. 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.

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

take effect. See the Administrator’s Reference for a description of all server options.

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

v Shared memory

v TCP/IP Version 4 or Version 6

v SNMP DPI®

Note: This is not supported on Sun Solaris x86_64.

You also can specify that no communication method be used by adding the

following server option to the server options file:

commmethod none

With this option, users cannot connect to the server. It is useful for experimenting

with policy commands.

Setting shared memory options

IBM Tivoli Storage Manager supports shared memory communication between

clients and servers on the same machine. To use shared memory, TCP/IP Version 4

or Version 6 must be installed on the machine. This is the default communication

method.

Here is a sample 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.

Note: 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 will prevent shared memory communication errors.

Setting TCP/IP options

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

retain the default.

Here is a sample TCP/IP setting:

commmethod tcpip tcpport 1500 tcpwindowsize 0 tcpnodelay yes

Note: TCP/IP has to be either Version 4 or Version 6. See the Administrator’s

Reference for more information.

TCPPORT

The server TCP/IP port address. The default value is 1500.

TCPWINDOWSIZE

The size of the TCP/IP buffer used when sending or receiving data. The

window size used in a session is the smaller of the server and client

window sizes. Larger window sizes use additional memory but may

improve performance.

You can specify an integer from zero to 64. To use the default window size

for the operating system, specify zero.

TCPNODELAY

Whether or not the server sends small messages or lets TCP/IP buffer the

messages. Sending small messages may 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. See the Administrator’s Reference for further information.


||

Setting SNMP options

Tivoli Storage Manager implements a simple network management protocol

(SNMP) subagent. This protocol is only supported on Sun SPARC (sun4u and

sun4v) platforms and not on x86_64 based platforms. 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).

Note: For details about configuring SNMP for use with IBM Tivoli Storage

Manager, see the Administrator’s Guide.

The subagent communicates with the snmpd daemon, which in turn communicates

with a management application. The snmpd daemon must support the DPI

protocol. Agents are available on AIX. SNMP options are supported on Sun SPARC

platforms and not on Sun x86_64 platforms

The subagent process is separate from the Tivoli Storage Manager server process,

but the subagent gets its information from the server options file. When the SNMP

management application is enabled, it can get information from Tivoli Storage

Manager servers.

Chapter 3. Specifying server and client communications 27


Appendix A. National Language Support

National Language Support (NLS) for the IBM Tivoli Storage Manager server

allows the server to display messages and help in languages other than U.S.

English. It also allows for the use of locale conventions for date, time, and number

formatting.

The languages supported are:

Brazilian Portuguese (pt_BR.ISO8859-1)

Chinese, simplified (zh)

Chinese, BIG5 (zh_TW.BIG5)

Chinese, traditional (zh_TW)

French (fr_FR.ISO8859-1)

German (de_DE.ISO8859-1)

Italian ( it_IT.ISO8859-1)

Japanese (ja)

Korean (ko)

Spanish (es_ES.ISO8859-1)

English (en_US.ISO8859-1)

English (en_US.UTF-8)

Brazilian Portuguese (pt_BR.UTF-8)

Chinese, simplified (zh_CN.UTF-8)

Chinese, traditional (zh_TW.UTF-8)

French (fr_FR.UTF-8)

German (de_DE.UTF-8)

Italian (it_IT.UTF-8)

Japanese (ja_JP.UTF-8)

Korean (ko_KR.UTF-8)

Spanish (es_ES.UTF-8)

Note: For Administration Center users, some characters might not display

properly if the HTML browser version is not the same language as the

server. If this problem, occurs, use a browser version that uses the same

language as the server.

Installing a language package

If you install a National Language Support (NLS) package, the IBM Tivoli Storage

Manager server displays messages and help in languages other than U.S. English.

Installation packages are provided with the Tivoli Storage Manager.

The NLS packages are located on the Sun server CD in the /NLS directory.

Note: The LANGUAGE option in the server options file is not a valid option for

the Tivoli Storage Manager for Solaris server. If you specify the

LANGUAGE option, the server ignores it. The server attempts to start the

language that you specified on the system language environment variable.

To install a language package, follow these instructions.

1. Enter:

pkgadd -d /cdrom/cdrom0/NLS

2.

The following packages are available:

TIVsmSchU IBM Tivoli Storage Manager/Sun - Locale zh_TW.UTF-8 (sparc)

Version 5 Release 5 Level 0.0

TIVsmScht IBM Tivoli Storage Manager/Sun - Locale zh_TW.BIG5 (sparc)


TIVsmScn IBM Tivoli Storage Manager/Sun - Locale zh (sparc) Version 5

Release 5 Level 0.0

TIVsmSde IBM Tivoli Storage Manager/Sun Language Support, Locale

de_DE.ISO8859-1 (sparc) Version 5 Release 5 Level 0.0


TIVsmScnU IBM Tivoli Storage Manager/Sun - Locale zh_CN.UTF-8 (sparc)


TIVsmSde IBM Tivoli Storage Manager/Sun Language Support, Locale

fr_FR.ISO8859-1 (sparc) Version 5 Release 5 Level 0.0

TIVsmSdeU IBM Tivoli Storage Manager/Sun - Locale de_DE.UTF-8 (sparc)


TIVsmSenU IBM Tivoli Storage Manager/Sun - Locale en_US.UTF-8 (sparc)


TIVsmSes IBM Tivoli Storage Manager/Sun - Locale es_ES.ISO8859-1 (sparc)


TIVsmSesU IBM Tivoli Storage Manager/Sun - Locale es_ES.UTF-8 (sparc)


TIVsmSfr IBM Tivoli Storage Manager/Sun - Locale fr_FR.ISO8859-1 (sparc)


TIVsmSfrU IBM Tivoli Storage Manager/Sun - Locale fr_FR.UTF-8 (sparc)


TIVsmSit IBM Tivoli Storage Manager/Sun - Locale it_IT.ISO8859-1 (sparc)


TIVsmSitU IBM Tivoli Storage Manager/Sun - Locale it_IT.UTF-8 (sparc)


TIVsmSjp IBM Tivoli Storage Manager/Sun - Locale ja (sparc) Version 5

Release 5 Level 0.0

TIVsmSjpU IBM Tivoli Storage Manager/Sun - Locale ja_JP.UTF-8 (sparc)


TIVsmSko TIVsmSko IBM Tivoli Storage Manager/Sun - Locale ko (sparc)


TIVsmSko TIVsmSkoU IBM Tivoli Storage Manager/Sun - Locale ko_KR.UTF-8

(sparc) Version 5 Release 5 Level 0.0

TIVsmSptU IBM Tivoli Storage Manager/Sun - Locale pt_BR.UTF-8 (sparc)


TIVsmSptb IBM Tivoli Storage Manager/Sun - Locale pt_BR.ISO8859-1 (sparc)


TIVsmStw IBM Tivoli Storage Manager/Sun - Locale zh_TW (sparc) Version 5

Release 5 Level 0.0

Select package(s) you wish to process (or all to process all

packages). (default: all) [?,??,q]:

3. Select and install your language choice from the menu.

4. Enter the following command to set the language environment variable:

export LC_ALL=xx

Where xx is the locale that you want; for example, ja. The server will run with

the language that you specified if:

v The locale is installed on the system.

v Tivoli Storage Manager supports the locale.

v The appropriate Tivoli Storage Manager server language package is installed.5. Start the server.

To enable support for a given locale, perform the following:

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.

If the locale successfully initializes, it will control the date, time, and number

formatting for the server. If the locale does not successfully initialize, the server

defaults to the U.S. English message files and the date, time, and number format

defaults to the U.S. English locale.


||||

The server console uses the locale and language that are defined by the server

options language variable. However, if an administrative client connects to the

server and specifies a locale that is different from the one that is specified at the

server, the server tries to initialize that specified locale for returning messages to

the client.

v Set the LC_MESSAGES environment variable to match that which is set in the

server options file. For example, to set the environment variable for Italian, enter

the following:

Appendix A. National Language Support 31


Appendix B. Installing an IBM Tivoli Storage Manager server

fix pack

IBM Tivoli Storage Manager maintenance updates are also called fix packs. Fix

packs bring the Tivoli Storage Manager server up to the current maintenance level.

To see a list of the latest maintenance and download fixes, visit this Web site:


Installation of IBM Tivoli Storage Manager will be stopped if an active server or

storage agent process is detected, and an error message displayed. All active server

or storage agent processes must be halted before installation can proceed.

Fix packs are shipped as compressed PKGADD-installable files and on CD. To

install a Tivoli Storage Manager fix pack, follow this procedure:

1. Back up the Tivoli Storage Manager database and the device configuration and

volume history files. In the following example, the tape device class named

TAPECLASS is used for database backups.


backup devconfig filenames=devconfig.jan99

backup volhistory filenames=volhistory.jan99

2. After the backup has completed, stop the server. Otherwise, a server crash

could result.

halt

3. Remove Tivoli Storage Manager (TIVsmS):

pkgrm TIVsmS

4. Install the fix pack, which includes the complete server program code:

v CD format:

pkgadd -d /cdrom/cdrom0 TIVsmS

v Compressed PKGADD file format:

pkgadd -d /<media_dir> TIVsmS

where media_dir is the location to where the server package was extracted.5. If this service level replaces the Tivoli Storage Manager tape, optical, and

library device drivers (non-IBM), reconfigure the device drivers into the kernel.

This step ensures that the device special file names are consistent.

a. Note the existing device special file names. You may want to redirect them

to a file.

ls -l /dev/rmt/*mt (tape)

ls -l /dev/rmt/*lb | grep lb@ (library)

ls -l /dev/rmt/*op (optical)




b. Remove the device special files. The device drivers were removed from the

kernel when the previous packages were removed.

rm /dev/rmt/xmt

rm /dev/rmt/xlb

rm /dev/rmt/xop

Where x is the appropriate number

c. Reconfigure the device drivers by running the autoconf script in the

/opt/tivoli/tsm/devices/bin/ directory.

d. Compare the device special file names with the names noted in step 5a on

page 33 and note any differences.

ls -l /dev/rmt/*mt (tape)

ls -l /dev/rmt/*lb | grep lb@ (library)

ls -l /dev/rmt/*op (optical)

e. Remove the st’s device special files which correspond to the Tivoli Storage

Manager device drivers’s device special files.

ls –l /dev/rmt/*st

After you start Tivoli Storage Manager, use the UPDATE PATH command to

make any device special file name changes. For more information on UPDATE

PATH, see the Administrator’s Reference.


||

Appendix C. Uninstalling the IBM Tivoli Storage Manager

server

You can either return to a previous version of Tivoli Storage Manager, or uninstall

the current IBM Tivoli Storage Manager server.

Note: You must have an existing database backup of the previous version that can

be restored if you want to return to an earlier version of Tivoli Storage

Manager after you perform an upgrade.

Before uninstalling IBM Tivoli Storage Manager

There are three steps to perform before you remove the Tivoli Storage Manager

server to ensure that you do not lose your backup and archive data. Those steps

are to perform a full database backup, save a copy of the volume history and

device configuration files, and store the output volumes in a safe location.

If you reinitialize the database and recovery log by issuing the DSMSERV

FORMAT command, any data that resided in your database, recovery log, and

storage pool volumes is destroyed.

Note: You must have an existing database backup of the previous version that can

be restored if you want to return to an earlier version of Tivoli Storage

Manager after an upgrade.

Perform the following procedure before uninstalling Tivoli Storage Manager:

1. Perform a full database backup. For example, if you have a tape device class

named tapeclass, enter the following command to perform a full backup:


2. Save a copy of the volume history and device configuration files that you

defined on the VOLHISTORY and DEVCONFIG options in the server options

file. For example, to save the volume history in a file named volhist and the

device configuration in a file named devices, enter the following:

backup volumehistory filenames=volhist

backup devconfig filenames=devices

3. Store the output volumes in a safe location.

Removing IBM Tivoli Storage Manager

If you would like to remove the Tivoli Storage Manager server from your system

because you no longer need it or would like to free up space, halt all active server

and storage agent processes first. Removal of Tivoli Storage Manager is stopped if

an active server or storage agent process is detected, and an error message

appears.

Enter the following command to remove the Tivoli Storage Manager server:

/usr/sbin/pkgrm TIVsmS

The system displays messages saying that the system is obtaining file information,

removing selected files, and finally confirming that removal is complete.


Attention: Database and recovery log files contain information pertaining to

backup-archive clients. The database and recovery log are not deleted when you

issue the PKGRM command.

Uninstalling Tivoli Storage Manager to return to an earlier version

It is possible to return to an earlier version of the Tivoli Storage Manager server. If

you want to return to an earlier version of Tivoli Storage Manager after an

upgrade, you must have a full database backup from your original version and the

server installation code for your original version.

Attention: You cannot restore a backed-up database from a prior version onto a

newer version of the Tivoli Storage Manager server.

Be aware of the following results when returning to an earlier version of Tivoli

Storage Manager:

v References to client files that were backed up, archived, or updated to the Tivoli

Storage Manager Version 5.5 server will be lost.

v Some existing volumes may be overwritten or deleted during the Tivoli Storage

Manager Version 5.5 operation. If so, client files that were on those volumes and

that were migrated, reclaimed, moved (MOVE DATA command), or deleted

(DELETE VOLUME command) may no longer be accessible to the earlier version

of Tivoli Storage Manager.

v Definitions, updates, and deletions of Tivoli Storage Manager objects performed

on the Version 5.5 server will be lost.

To return to a previous version of Tivoli Storage Manager, perform the following

steps.

Note: If you want to uninstall the Tivoli Storage Manager server without returning

to a previous version, see step 3. Be aware that you will be unable to restore

your database after you uninstall the Tivoli Storage Manager server.

1. Enter the Tivoli Storage Manager halt command to stop the Tivoli Storage

Manager server if it is currently running.

2. Delete the current device definitions.

Select Devices.

Note: It is not necessary to remove the non-Tivoli Storage Manager devices

that IBM Tivoli Storage Manager uses (3480, 3490, and 3590 drives, and

3494 and 3495 tape libraries).

3. Remove the current Tivoli Storage Manager server software. Issue the following

command:

/usr/sbin/pkgrm TIVsmS

Note: Remove any other NLS IBM Tivoli Storage Manager packages that you

might have installed (for example, TIVsmSjp).

Remove the license package.

4. Reinstall the previous version of Tivoli Storage Manager and the most recent

maintenance.

/usr/sbin/pkgadd -d/cdrom/cdrom0 TIVsmS


|||

||

5. Define the IBM Tivoli Storage Manager devices to the operating system.

6. Reinitialize any database and recovery log volumes, other than those created

during install, using the DSMSERV FORMAT utility. See the Administrator’s

Reference for details.

7. Reload the Tivoli Storage Manager database using the DSMSERV RESTORE DB

utility.

./dsmserv restore db todate=07/04/2007

See the Administrator’s Reference for details.

8. Start the server by issuing the following command:

./dsmserv

9. Examine the saved volume history file from step 2 on page 35.

For every sequential volume specified in the volume history file with a volume

type of STGREUSE or STGDELETE, execute the AUDIT VOLUME FIX=YES

command to clean up invalid database references to the volume(s) and to audit

all disk storage pool volumes.

If you cannot locate a volume that has a volume type of STGDELETE, use the

DELETE VOLUME DISCARDDATA=YES command to remove references to the

volume from the server database.

Appendix C. Uninstalling the IBM Tivoli Storage Manager server 37


Appendix D. 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 (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106-0032, 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 Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those Web

sites. The materials at those Web sites are not part of the materials for this IBM

product and use of those Web sites is at your own risk.


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 wish 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.

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.


Trademarks

The following terms are trademarks of International Business Machines

Corporation in the United States, other countries, or both:

AIX

AS/400

DB2

DFS

DFSMS/MVS

DFSMShsm

DFSMSrmm

DPI

Enterprise Storage Server

ESCON

eServer

FICON

FlashCopy

HACMP

Informix

iSeries

Lotus

Lotus 123

Lotus Approach

Lotus Domino

Lotus Notes

Magstar

MVS

NetView

OpenEdition

OS/2

OS/390

OS/400

Passport Advantage

pSeries

RACF

Rational

Redbooks

RS/6000

S/390

SANergy

SecureWay

StorageSmart

SystemView

Tivoli

Tivoli Enterprise Console

Tivoli Management Environment

TotalStorage

TME

VTAM

WebSphere

z/OS

zSeries

Intel®, Intel Inside® (logos), MMX and Pentium® are trademarks of Intel

Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the

United States, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft

Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other

countries.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Other company, product or service names may be trademarks or service marks of

others.

Appendix D. Notices 41


Index

Aaccessibility features xi

activatingserver 6

Administration Centerinstalling 18

overview 16

system requirements 15

uninstalling 21

upgrading 18

verifying 20

Administration Center, installing 15

administrative clientWeb interface 12

administrative commandsDSMSERV DUMPDB 9

HALT 6

REGISTER LICENSE 7

applying PTFs 33

archivedescription 6

Bbackup

description 6

selective 6

Cclient components 2

client directory 2

client node, Tivoli Storage Managerdescription 6

client optionsfor shared memory

communications 25

command scripts 11

commands, administrativeDSMSERV DUMPDB 9

HALT 6

REGISTER LICENSE 7

commands, clientSELECTIVE 6

communication methodsShared Memory 25

SNMP 27

TCP/IP 26

configuringAdministration Center IP address 15

console installation wizard 16

customer support, contacting ix

Ddefault installation directories 3

directories, client and server 2

directories, default installation 3

disaster recovery managerDRM) 7

disaster, protecting against 7

disk spacerequired for installation 2

DSMSERV DUMPDB command 9

dsmserv runfile, for web client 12

DSMSERV_DIR environment variable 13

dsmserv.dsk file 8, 9, 13

dump database 9

Eeducation

see Tivoli technical training viii

enabling communications 25

environment variables 12, 13

evaluation productupgrading to license product 2

expirationserver option 6

Ffiles

dsmserv.idl (web definition file) 12

dsmserv.opt 3

dsmserv.opt.smp 25

server directory 4

Fix pack 7

fixes, obtaining ix

Gglobal zone 4

HHALT command 6

halting the server 6

hardware requirements 1

IIBM Software Support

submitting a problem x

IBM Support Assistant viii

installationverifying 5

installation wizard 16

installingminimum requirements for 2

over a previous versionprocedure 2

space requirements for 2

PTFs 33

Tivoli Storage Manager clientsprocedure 2

verification 5

installing server 1

installing the Administration Center 15

installing the Integrated Solutions

Console 15

Integrated Solutions Consoleconsole help server

start 20

stop 20

console serverstart 20

stop 20

installing 16

overview 16

silent installation 16

uninstalling 21

Integrated Solutions Console,

installing 15

Integrated Solutions Console,

uninstalling 21

Internet, search for problem

resolution viii

Internet, searching for problem

resolution ix

IP addressconfiguring 15

ISC, installing 15

Kknowledge bases, searching viii

Llanguage

non-English 29

LANGUAGE option 29

language package 29

language, install from SMIT 29

latest version, upgrading to 7

license, Tivoli Storage Manager 7

Mmaintenance upgrade 33

multiple servers, running 12

Nname, administrative client 2

name, backup-archive client 2

national language support 29

national language version features 29

NLS 29

NLS (national language support) 29

non-global zone 4

Ooptions

starting the server 6


options fileediting 25

options, clientTCPADMINPORT 26

TCPPORT 26

TCPWINDOWSIZE 26

options, servercommunications 25

Pprevious versions

compatibility 7

problem determinationdescribing problem for IBM Software

Support x

determining business impact for IBM

Software Support x

submitting a problem to IBM

Software x

program temporary fix 33

PTF 33

publicationsdownload v

order v

search v

Tivoli Storage Manager v

RREGISTER LICENSE command 7

reinstalling an earlier version of the Tivoli

Storage Manager server 35

removing server 35

removing the Tivoli Storage Manager

server 35

runfile command 11

Sscripts, Tivoli Storage Manager

command 11

selective backup 6

SELECTIVE command 6

server directory 2

server license 7

server optionsdsmserv.opt.smp 25

tailoring 25

server options filesetting 25

server upgrade 9

server, Tivoli Storage Manageractivating 6

halting 6

installation minimum requirements 2

multiple instances 12

options 25

setting up 6

starting 6

stopping 6

verifying configuration 5

service 33

shared memory client options 25

shared memory communications

method 25

SNMP communication method 27

software requirements 1

Software Supportcontacting ix

describing problem for IBM Software

Support x

determining business impact for IBM

Software Support x

Solaris Zones 4

startingserver 6

stoppingserver 6

storage pooldescription 6

support information vii

system requirements 1

TTCP/IP

setting options 26

Version 4 25

Version 6 25

TCPNODELAY option 26

TCPPORT option 26

TCPWINDOWSIZE option 26

technical changes xiii

Tivoli Storage Manager installation 1

Tivoli Storage Manager serverearlier versions 36

Tivoli Storage Manager server

requirements 1

Tivoli Storage Manager upgrade 9

Tivoli Storage Manager, setting up 6

Tivoli technical training viii

training, Tivoli technical viii

try and buy productupgrading to license product 2

Uuninstalling

preparation 35

upgrade to the latest version 7

upgrade, before performing 8

upgrading 9

Wwizard

console installation 16

installation 16


��

Program Number: 5608-ISM5608-ISX

Printed in USA

GC23-5972-00

Date post:	15-Jan-2017
Category:	Documents
Upload:	vanxuyen
View:	220 times
Download:	1 times

IBM Tivoli Storage Manager for Sun Solaris: Installation Guide

Documents