IBM Tivoli Storage Manager

Version 7.1

Upgrade and Migration Guide for V5

Servers

IBM Tivoli Storage Manager
Version 7.1

Upgrade and Migration Guide for V5

Servers

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

First edition (December 2013)

This edition applies to version 7, release 1, modification 0 of IBM Tivoli Storage Manager (product numbers
5608-E01, 5608-E02, 5608-E03), and to all subsequent releases and modifications until otherwise indicated in new
editions.
© Copyright IBM Corporation 2009, 2013.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Preface . . . . . . . . . . . . . . . xi Hardware and software requirements for the V5
Who should read this guide . . . . . . . . . xi server system that is being upgraded . . . . . 17
How to use this guide . . . . . . . . . . . xi Hardware and software requirements for the
Publications . . . . . . . . . . . . . . xii upgraded server . . . . . . . . . . . . 19
Compatibility of the Tivoli Storage Manager server
New for Tivoli Storage Manager with other DB2 products on the system . . . . . 35
Determining the appropriate level for a V5 server
Version 7.1. . . . . . . . . . . . . xiii before an upgrade . . . . . . . . . . . . 36
New in Version 7.1 . . . . . . . . . . . xiii Planning space for the upgrade process and the
Operations Center updates . . . . . . . . xiii upgraded server . . . . . . . . . . . . . 37
Automatic client failover for restore operations Space requirements for the V5 server system . . 37
from replicated servers . . . . . . . . . xiii Space requirements for the V7 server system . . 38
Software upgrade for the server database Estimating total space requirements for the
manager . . . . . . . . . . . . . . xiv upgrade process and upgraded server . . . . 39
Deprecated device types . . . . . . . . . xiv Worksheet for planning space for the V7.1 server 42
EMC Centera availability on Linux x86_64 Estimating the upgrade time. . . . . . . . . 42
systems for Tivoli Storage Manager servers . . xiv Example: Estimating the upgrade time based on
File-space level collocation groups. . . . . . xv the database size . . . . . . . . . . . 43
Improved server efficiency when migrating from Performance tips for the V5 database extraction
disk for nodes with a large number of file spaces. xv process . . . . . . . . . . . . . . . 44
Shared memory for database backup and restore Performance tips for inserting data into the V7.1
operations . . . . . . . . . . . . . . xv database . . . . . . . . . . . . . . 45
Immediate use of space that is added to the Planning for upgrading multiple servers and
server database . . . . . . . . . . . . xv components . . . . . . . . . . . . . . 45
Server components that are not delivered with Components that are available for installation . . 46
Version 7.1 . . . . . . . . . . . . . . xvi Compatibility with servers and components that
are running at earlier versions . . . . . . . 46
Part 1. Upgrading the server from V5 Planning for upgrading multiple servers on a
to V7.1 . . . . . . . . . . . . . . . 1 single system . . . . . . . . . . . . . 46
Planning for upgrading library managers and
library clients . . . . . . . . . . . . . 47
Chapter 1. Server database updates Planning for upgrading clients . . . . . . . 47
overview . . . . . . . . . . . . . . 3 Planning for upgrading storage agents . . . . 47
The server database . . . . . . . . . . . . 3 Testing the upgrade process for a server . . . . . 47
Database space for a V7.1 server . . . . . . . 4 Testing by extracting data from a separate copy
Recovery log . . . . . . . . . . . . . 4 of the server . . . . . . . . . . . . . 49
Operation changes . . . . . . . . . . . . 4 Testing by extracting data from the production
Database operations . . . . . . . . . . . 4 server . . . . . . . . . . . . . . . 49
Database protection and recovery . . . . . . 5 Preparing for operational changes . . . . . . . 50
Multiple server instances on a single system . . . 7 Reference information for planning . . . . . . 51
Changes to starting the server . . . . . . . 8 Command and option changes . . . . . . . 51
Files and environment changes . . . . . . . 9 New and changed server messages . . . . . 70
Administrative command changes . . . . . . 10 Server naming best practices. . . . . . . . 70

Chapter 2. Planning the upgrade of the Chapter 3. Upgrade scenarios overview 73

server . . . . . . . . . . . . . . . 11 Scenario 1 for upgrading the server: same system,
The process for upgrading the server from V5 to media method . . . . . . . . . . . . . 73
V7.1 . . . . . . . . . . . . . . . . . 12 Upgrading the server by using the wizard . . . 74
Comparison of upgrading on an existing system Upgrading the server manually by using utilities 76
and a new system . . . . . . . . . . . 13 Scenario 2 for upgrading the server: same system,
Comparison of methods for moving data to the network method . . . . . . . . . . . . . 78
V7.1 database. . . . . . . . . . . . . 15 Upgrading the server by using the wizard . . . 78
DSMUPGRD upgrade utilities . . . . . . . . 16 Upgrading the server manually by using utilities 80
Hardware and software requirements for upgrading Scenario 3 for upgrading the server: new system,
to the V7.1 server . . . . . . . . . . . . 17 media method . . . . . . . . . . . . . 82

© Copyright IBM Corp. 2009, 2013 iii

Upgrading the server by using the wizard . . . 82 Scenario 1: Creating and formatting the new
Upgrading the server manually by using utilities 84 database . . . . . . . . . . . . . . 122
Scenario 4 for upgrading the server: New system, Scenario 1: Loading the extracted data into the
network method . . . . . . . . . . . . . 86 new database . . . . . . . . . . . . 126
Upgrading the server by using the wizard . . . 86 Scenario 1: Creating a Windows service for the
Upgrading the server manually by using utilities 88 server instance . . . . . . . . . . . . 128
Scenario 1: Configuring the system for database
Chapter 4. Scenario 1: Same system, backup . . . . . . . . . . . . . . 129
media method . . . . . . . . . . . 91
Scenario 1: Preparing for the upgrade . . . . . 91 Chapter 5. Scenario 2: Same system,
Scenario 1: Checking the prerequisites for the network method . . . . . . . . . . 135
upgrade . . . . . . . . . . . . . . 92 Scenario 2: Preparing for the upgrade . . . . . 135
Scenario 1: Preparing space for the upgrade Scenario 2: Checking the prerequisites for the
process . . . . . . . . . . . . . . . 95 upgrade . . . . . . . . . . . . . . 136
Scenario 1: Modifying the server before the Scenario 2: Preparing space for the upgrade
upgrade . . . . . . . . . . . . . . 96 process . . . . . . . . . . . . . . 139
Scenario 1: Disabling sessions . . . . . . . 97 Scenario 2: Modifying the server before the
Scenario 1: Backing up storage pools and the upgrade . . . . . . . . . . . . . . 139
server database . . . . . . . . . . . . 98 Scenario 2: Disabling sessions . . . . . . . 141
Scenario 1: Moving the NODELOCK file . . . 98 Scenario 2: Backing up storage pools and the
Scenario 1: Backing up configuration information 99 server database . . . . . . . . . . . . 141
Scenario 1: Creating a summary of database Scenario 2: Moving the NODELOCK file . . . 142
contents . . . . . . . . . . . . . . 99 Scenario 2: Backing up configuration
Scenario 1: Stopping the server before installing information . . . . . . . . . . . . . 142
the upgrade . . . . . . . . . . . . . 100 Scenario 2: Creating a summary of database
Scenario 1: Installing the upgrade utilities . . . . 100 contents . . . . . . . . . . . . . . 143
Scenario 1: Installing the upgrade utilities on Scenario 2: Stopping the server before installing
AIX systems . . . . . . . . . . . . . 101 the upgrade . . . . . . . . . . . . . 143
Scenario 1: Installing the upgrade utilities on Scenario 2: Installing the upgrade utilities . . . . 144
HP-UX systems. . . . . . . . . . . . 102 Scenario 2: Installing the upgrade utilities on
Scenario 1: Installing the upgrade utilities on AIX systems . . . . . . . . . . . . . 144
Linux systems . . . . . . . . . . . . 103 Scenario 2: Installing the upgrade utilities on
Scenario 1: Installing the upgrade utilities on HP-UX systems. . . . . . . . . . . . 146
Oracle Solaris systems . . . . . . . . . 104 Scenario 2: Installing the upgrade utilities on
Scenario 1: Setting environment variables for the Linux systems . . . . . . . . . . . . 147
upgrade utilities on AIX, HP-UX, Linux, and Scenario 2: Installing the upgrade utilities on
Oracle Solaris systems . . . . . . . . . 106 Oracle Solaris systems . . . . . . . . . 148
Scenario 1: Installing the upgrade utilities on Scenario 2: Setting environment variables for the
Microsoft Windows systems . . . . . . . 107 upgrade utilities on AIX, HP-UX, Linux, and
Scenario 1: Preparing the database of a V5 server Oracle Solaris systems . . . . . . . . . 149
for upgrade . . . . . . . . . . . . . . 107 Scenario 2: Installing the upgrade utilities on
Scenario 1: Uninstalling the V5 program before Microsoft Windows systems . . . . . . . 150
installing V7.1 . . . . . . . . . . . . . 109 Scenario 2: Preparing the database of a V5 server
Scenario 1: Uninstalling the V5 program on AIX for upgrade . . . . . . . . . . . . . . 151
systems . . . . . . . . . . . . . . 109 Scenario 2: Uninstalling the V5 program before
Scenario 1: Uninstalling the V5 program on installing V7.1 . . . . . . . . . . . . . 152
HP-UX systems. . . . . . . . . . . . 109 Scenario 2: Uninstalling the V5 program on AIX
Scenario 1: Uninstalling the V5 program on systems . . . . . . . . . . . . . . 152
Linux systems . . . . . . . . . . . . 110 Scenario 2: Uninstalling the V5 program on
Scenario 1: Uninstalling the V5 program on HP-UX systems. . . . . . . . . . . . 153
Oracle Solaris systems . . . . . . . . . 110 Scenario 2: Uninstalling the V5 program on
Scenario 1: Uninstalling the V5 program on Linux systems . . . . . . . . . . . . 153
Microsoft Windows systems . . . . . . . 111 Scenario 2: Uninstalling the V5 program on
Scenario 1: Installing the V7.1 server. . . . . . 111 Oracle Solaris systems . . . . . . . . . 154
Scenario 1: Creating the directories and the user ID Scenario 2: Uninstalling the V5 program on
for the upgraded server instance . . . . . . . 115 Microsoft Windows systems . . . . . . . 154
Scenario 1: Upgrading the server by using the Scenario 2: Installing the V7.1 server . . . . . 155
upgrade wizard . . . . . . . . . . . . 118 Scenario 2: Creating the directories and the user ID
Scenario 1: Upgrading the server manually by for the upgraded server instance . . . . . . . 159
using utilities . . . . . . . . . . . . . 120 Scenario 2: Upgrading the server by using the
Scenario 1: Extracting the data to media . . . 121 upgrade wizard . . . . . . . . . . . . 162

iv IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Scenario 2: Upgrading the server manually by Scenario 3: Loading the extracted data into the
using utilities . . . . . . . . . . . . . 164 new database . . . . . . . . . . . . 216
Scenario 2: Creating and formatting the new Scenario 3: Creating a Windows service for the
database . . . . . . . . . . . . . . 164 server instance . . . . . . . . . . . . 218
Scenario 2: Moving the server database over a Scenario 3: Configuring the system for database
network . . . . . . . . . . . . . . 169 backup . . . . . . . . . . . . . . 219
Scenario 2: Creating a Windows service for the
server instance . . . . . . . . . . . . 170 Chapter 7. Scenario 4: New system,
Scenario 2: Configuring the system for database network method . . . . . . . . . . 225
backup . . . . . . . . . . . . . . 171
Scenario 4: Preparing for the upgrade . . . . . 225
Scenario 4: Checking the prerequisites for the
Chapter 6. Scenario 3: New system, upgrade . . . . . . . . . . . . . . 226
media method . . . . . . . . . . . 177 Scenario 4: Preparing space for the upgrade
Scenario 3: Preparing for the upgrade . . . . . 177 process . . . . . . . . . . . . . . 229
Scenario 3: Checking the prerequisites for the Scenario 4: Modifying the server before the
upgrade . . . . . . . . . . . . . . 178 upgrade . . . . . . . . . . . . . . 229
Scenario 3: Preparing space for the upgrade Scenario 4: Disabling sessions . . . . . . . 230
process . . . . . . . . . . . . . . 181 Scenario 4: Backing up storage pools and the
Scenario 3: Modifying the server before the server database . . . . . . . . . . . . 231
upgrade . . . . . . . . . . . . . . 182 Scenario 4: Moving the NODELOCK file . . . 232
Scenario 3: Disabling sessions . . . . . . . 183 Scenario 4: Backing up configuration
Scenario 3: Backing up storage pools and the information . . . . . . . . . . . . . 232
server database . . . . . . . . . . . . 184 Scenario 4: Creating a summary of database
Scenario 3: Moving the NODELOCK file . . . 184 contents . . . . . . . . . . . . . . 233
Scenario 3: Backing up configuration Scenario 4: Stopping the server before installing
information . . . . . . . . . . . . . 185 the upgrade . . . . . . . . . . . . . 233
Scenario 3: Creating a summary of database Scenario 4: Installing the upgrade utilities . . . . 233
contents . . . . . . . . . . . . . . 185 Scenario 4: Installing the upgrade utilities on
Scenario 3: Stopping the server before installing AIX systems . . . . . . . . . . . . . 234
the upgrade . . . . . . . . . . . . . 186 Scenario 4: Installing the upgrade utilities on
Scenario 3: Installing the upgrade utilities . . . . 186 HP-UX systems. . . . . . . . . . . . 236
Scenario 3: Installing the upgrade utilities on Scenario 4: Installing the upgrade utilities on
AIX systems . . . . . . . . . . . . . 187 Linux systems . . . . . . . . . . . . 237
Scenario 3: Installing the upgrade utilities on Scenario 4: Installing the upgrade utilities on
HP-UX systems. . . . . . . . . . . . 188 Oracle Solaris systems . . . . . . . . . 238
Scenario 3: Installing the upgrade utilities on Scenario 4: Setting environment variables for the
Linux systems . . . . . . . . . . . . 189 upgrade utilities on AIX, HP-UX, Linux, and
Scenario 3: Installing the upgrade utilities on Oracle Solaris systems . . . . . . . . . 239
Oracle Solaris systems . . . . . . . . . 191 Scenario 4: Installing the upgrade utilities on
Scenario 3: Setting environment variables for the Microsoft Windows systems . . . . . . . 240
upgrade utilities on AIX, HP-UX, Linux, and Scenario 4: Upgrading the server by using the
Oracle Solaris systems . . . . . . . . . 192 upgrade wizard . . . . . . . . . . . . 241
Scenario 3: Installing the upgrade utilities on Scenario 4, wizard: Installing the V7.1 server 241
Microsoft Windows systems . . . . . . . 193 Scenario 4, wizard: Creating the directories and
Scenario 3: Upgrading the server by using the the user ID for the upgraded server instance . . 245
upgrade wizard . . . . . . . . . . . . 194 Scenario 4: Starting the upgrade wizard . . . 248
Scenario 3, wizard: Installing the V7.1 server 194 Scenario 4: Upgrading the server manually by
Scenario 3, wizard: Creating the directories and using utilities . . . . . . . . . . . . . 250
the user ID for the upgraded server instance . . 198 Scenario 4: Preparing the database of a V5
Scenario 3: Starting the upgrade wizard . . . 201 server for upgrade . . . . . . . . . . 250
Scenario 3: Upgrading the server manually by Scenario 4, manual: Installing the V7.1 server 252
using utilities . . . . . . . . . . . . . 202 Scenario 4, manual: Creating the directories and
Scenario 3: Preparing the database of a V5 the user ID for the upgraded server instance . . 256
server for upgrade . . . . . . . . . . 203 Scenario 4: Creating and formatting the new
Scenario 3: Extracting the data to media . . . 204 database . . . . . . . . . . . . . . 259
Scenario 3, manual: Installing the V7.1 server 205 Scenario 4: Moving the server database over a
Scenario 3, manual: Creating the directories and network . . . . . . . . . . . . . . 263
the user ID for the upgraded server instance . . 209 Scenario 4: Creating a Windows service for the
Scenario 3: Creating and formatting the new server instance . . . . . . . . . . . . 265
database . . . . . . . . . . . . . . 212 Scenario 4: Configuring the system for database
backup . . . . . . . . . . . . . . 265

Contents v
Chapter 8. Clustered environments: Chapter 10. Taking the first steps after
Upgrade procedures . . . . . . . . 271 upgrade. . . . . . . . . . . . . . 323
Upgrading the server to V7.1 in an AIX clustered Verifying access to storage pools on disk . . . . 323
environment. . . . . . . . . . . . . . 271 Setting up Solaris services for the server instance 324
Upgrading the server to V7.1 in a Windows Configuring server options for server database
clustered environment . . . . . . . . . . 273 maintenance . . . . . . . . . . . . . . 324
Planning the upgrade and preparing the system 273 Starting the server instance after the upgrade. . . 325
Installing the V7.1 server and running the Starting the server on AIX, HP-UX, Linux, and
upgrade wizard . . . . . . . . . . . 274 Oracle Solaris systems . . . . . . . . . 325
Starting the server on Windows systems . . . 331
Chapter 9. General procedures for Registering licenses . . . . . . . . . . . 334
upgrading a server to V7.1 . . . . . 277 Backing up the database after upgrading the server 335
Verifying the upgraded server . . . . . . . . 336
Preparing for the upgrade . . . . . . . . . 277
Changing the host name for the Tivoli Storage
Checking the prerequisites for the upgrade . . 278
Manager server. . . . . . . . . . . . . 336
Preparing space for the upgrade process . . . 281
Changing the host name for a server running on
Modifying the server before the upgrade . . . 282
AIX, HP-UX, Linux, or Solaris systems . . . . 337
Disabling sessions . . . . . . . . . . . 284
Changing the host name for a server running on
Backing up storage pools and the server
Windows . . . . . . . . . . . . . . 337
database . . . . . . . . . . . . . . 284
Updating automation. . . . . . . . . . . 338
Moving the NODELOCK file . . . . . . . 285
Monitoring the upgraded server . . . . . . . 339
Backing up configuration information . . . . 285
Removing GSKit Version 7 after upgrading to
Creating a summary of database contents . . . 286
Tivoli Storage Manager V7.1 . . . . . . . . 340
Stopping the server before installing the
upgrade . . . . . . . . . . . . . . 286
Installing the upgrade utilities on the original Chapter 11. Troubleshooting the
server . . . . . . . . . . . . . . . . 287 database upgrade . . . . . . . . . 343
Installing the upgrade utilities on AIX systems 287 Server upgrade phase: warnings about
Installing the upgrade utilities on HP-UX unsupported server options . . . . . . . . 343
systems . . . . . . . . . . . . . . 289 Database extraction phase: connection refusal
Installing the upgrade utilities on Linux systems 290 message . . . . . . . . . . . . . . . 343
Installing the upgrade utilities on Oracle Solaris Database formatting phase: failure with rc=499 . . 344
systems . . . . . . . . . . . . . . 291 Database insertion phase: ANR1338E messages
Setting environment variables for the upgrade from the upgrade utility . . . . . . . . . . 345
utilities on AIX, HP-UX, Linux, and Oracle Database insertion phase: ANR1525I messages with
Solaris systems . . . . . . . . . . . . 292 no apparent progress . . . . . . . . . . . 346
Installing the upgrade utilities on Microsoft Database insertion phase: problems with restarting
Windows systems . . . . . . . . . . . 293 the upgrade process . . . . . . . . . . . 347
Preparing the database of a V5 server for upgrade 294 Server startup phase: error ANR0162W . . . . . 349
Uninstalling the V5 program before installing V7.1 295 Server startup phase: warnings about unsupported
Uninstalling the V5 program on AIX systems 295 server options . . . . . . . . . . . . . 350
Uninstalling the V5 program on HP-UX systems 296 Postupgrade phase: dsmserv.dsk file no longer
Uninstalling the V5 program on Linux systems 296 available . . . . . . . . . . . . . . . 351
Uninstalling the V5 program on Oracle Solaris Postupgrade phase: VARY command fails . . . . 351
systems . . . . . . . . . . . . . . 297 Reverting from V7.1 to the previous V5 server
Uninstalling the V5 program on Microsoft version . . . . . . . . . . . . . . . 351
Windows systems . . . . . . . . . . . 297 Steps for reverting to the previous server
Installing the V7.1 server . . . . . . . . . 297 version . . . . . . . . . . . . . . 352
Creating the directories and the user ID for the Additional recovery steps if you created new
upgraded server instance . . . . . . . . . 302 storage pools or enabled data deduplication . . 353
Upgrading the server by using the upgrade wizard 305
Upgrading the server manually by using utilities 307
Part 2. Migrating Tivoli Storage
Creating and formatting the new database . . 308
Moving the server database using media . . . 312 Manager V5 servers on AIX,
Moving the server database over a network . . 316 HP-UX, or Solaris systems to V7.1
Creating a Windows service for the server on Linux . . . . . . . . . . . . . 355
instance . . . . . . . . . . . . . . 318
Configuring the system for database backup 318
Chapter 12. Migration overview. . . . 357
Migration roadmap . . . . . . . . . . . 357
Scenarios for migrating a server from an AIX,
HP-UX, or Solaris system to V7.1 on Linux . . . 358

vi IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
The migration process . . . . . . . . . . 363 Migration scenario 2: Extracting the data to
Utilities and commands for data migration . . 363 media . . . . . . . . . . . . . . . 393
Data movement . . . . . . . . . . . 363 Migration scenario 2: Installing the V7.1 server 393
Device availability . . . . . . . . . . . 364 Migration scenario 2: Setting up devices . . . 396
Protection for client data and the server during Migration scenario 2: Configuring devices . . . 397
the process . . . . . . . . . . . . . 364 Migration scenario 2: Creating the user ID and
directories for the server instance. . . . . . 398
Chapter 13. Planning the migration 365 Migration scenario 2: Creating the server
Hardware and software requirements for the V5 instance and database . . . . . . . . . 400
and V7.1 servers . . . . . . . . . . . . 366 Migration scenario 2: Loading the extracted data
Estimating database and recovery log requirements 366 into the V7.1 database . . . . . . . . . 402
Estimating the time required for migration . . . 367 Migration scenario 2: Configuring the system
Planning data movement . . . . . . . . . 368 for database backup . . . . . . . . . . 404
Planning for upgrading multiple servers and Migration scenario 3: Using the network method
components . . . . . . . . . . . . . . 368 and the upgrade wizard . . . . . . . . . . 406
Preparing for operational changes . . . . . . 368 Migration scenario 3: Installing the V7.1 server 406
Estimating storage and device requirements . . . 369 Migration scenario 3: Setting up devices . . . 409
Performance tips for the V5 database extraction Migration scenario 3: Creating the user ID and
process . . . . . . . . . . . . . . . 369 directories for the server instance. . . . . . 410
Performance tips for inserting data into the V7.1 Migration scenario 3: Running the upgrade
database . . . . . . . . . . . . . . . 370 wizard. . . . . . . . . . . . . . . 411
Reference information for planning the migration 371 Migration scenario 4: Using the network method
and the command line . . . . . . . . . . 412
Migration scenario 4: Preparing the database of
Chapter 14. Preparing for the
the V5 server . . . . . . . . . . . . 412
migration . . . . . . . . . . . . . 373 Migration scenario 4: Installing the V7.1 server 413
Preparing space for the migration process . . . . 373 Migration scenario 4: Setting up devices . . . 416
Upgrading the V5 server to V5.5.6 or later. . . . 373 Migration scenario 4: Creating the user ID and
Disabling sessions . . . . . . . . . . . . 374 directories for the server instance. . . . . . 417
Backing up or migrating data stored on DISK and Migration scenario 4: Creating the server
FILE devices. . . . . . . . . . . . . . 375 instance and database . . . . . . . . . 418
Migrating data that is stored on GENERICTAPE Migration scenario 4: Moving the server
devices . . . . . . . . . . . . . . . 376 database over a network . . . . . . . . 420
Moving backup sets that are stored on FILE Migration scenario 4: Configuring the system
devices . . . . . . . . . . . . . . . 376 for database backup . . . . . . . . . . 422
Backing up the server database . . . . . . . 377
Creating a summary of database contents . . . . 377
Chapter 16. Taking the first steps after
Modifying the server to prevent potential issues 378
Stopping the server before the migration . . . . 379 migration . . . . . . . . . . . . . 425
Installing the upgrade utilities . . . . . . . . 380 Configuring server options for server database
Installing the upgrade utilities on AIX systems 380 maintenance . . . . . . . . . . . . . . 425
Installing the upgrade utilities on HP-UX Starting the server . . . . . . . . . . . . 426
systems . . . . . . . . . . . . . . 381 Verifying the migration results . . . . . . . 426
Installing the upgrade utilities on Oracle Solaris Registering licenses . . . . . . . . . . . 427
systems . . . . . . . . . . . . . . 382 Updating device path information . . . . . . 428
Backing up the database. . . . . . . . . . 428
Changing the host name for the Tivoli Storage
Chapter 15. Migrating the server
Manager server. . . . . . . . . . . . . 429
database to the V7.1 server . . . . . 385 Updating the tcpserveraddress option . . . . . 430
Migration scenario 1: Using the media method and Setting the IP address of the server . . . . . . 430
the upgrade wizard . . . . . . . . . . . 385 Migrating data from tape to DISK or FILE devices 431
Migration scenario 1: Installing the V7.1 server 386 Restoring backup sets . . . . . . . . . . 432
Migration scenario 1: Setting up devices . . . 388 Updating automation. . . . . . . . . . . 433
Migration scenario 1: Creating the user ID and Beginning operations and monitoring the server 433
directories for the server instance. . . . . . 389
Migration scenario 1: Running the upgrade
Chapter 17. Troubleshooting the
wizard . . . . . . . . . . . . . . 390
Migration scenario 2: Using the media method and migration of a V5 server from AIX,
the command line . . . . . . . . . . . . 391 HP-UX, or Solaris. . . . . . . . . . 435
Migration scenario 2: Preparing the database of Reverting from V7.1 to the previous V5 server
the V5 server . . . . . . . . . . . . 392 version . . . . . . . . . . . . . . . 435

Contents vii
Part 3. Migrating Tivoli Storage Installing Tivoli Storage Manager for z/OS
Media . . . . . . . . . . . . . . . 481
Manager V5 servers on z/OS Defining a server that corresponds to the z/OS
systems to V7.1 on AIX or Linux media server . . . . . . . . . . . . 481
on System z . . . . . . . . . . . 437 Disabling sessions . . . . . . . . . . . 482
Analyzing the Tivoli Storage Manager server by
using ZMSPREPARE . . . . . . . . . . 482
Chapter 18. Migration overview. . . . 439
Removing volumes of disk-based copy storage
Migration road map . . . . . . . . . . . 439
pools . . . . . . . . . . . . . . . 484
Scenarios for migrating a server from a z/OS
Backing up data from disk-based primary
system to AIX or Linux on System z. . . . . . 439
storage pools . . . . . . . . . . . . 485
Tivoli Storage Manager for z/OS Media overview 443
Identifying and deleting FILE backup sets . . . 486
The migration process . . . . . . . . . . 443
Creating the Tivoli Storage Manager server
Migration process overview . . . . . . . 444
options file . . . . . . . . . . . . . 486
Key tasks in the migration process . . . . . 446
Running the ZMSPREPARE command again to
Utilities and commands for data migration . . 447
verify prerequisites . . . . . . . . . . 486
Device migration . . . . . . . . . . . 448
Backing up the server database . . . . . . 488
Backup sets . . . . . . . . . . . . . 450
Stopping the server before the migration . . . 488
Effects of migration on storage agents . . . . 451
Preparing the database of a V5 server for
Protection for client data and the server during
migration. . . . . . . . . . . . . . 489
the process . . . . . . . . . . . . . 452
Comparison of database migration methods . . 452
Operational changes and requirements . . . . . 453 Chapter 21. Migrating the z/OS server
Automated message response systems . . . . 453 database to the V7.1 server . . . . . 491
Performance considerations. . . . . . . . 453 Migrating a V5 z/OS server by using the media
method . . . . . . . . . . . . . . . 491
Chapter 19. Planning the migration 455 Creating and formatting the new database . . 491
Hardware and software requirements for the V5 Extracting the data to media . . . . . . . 492
and V7.1 servers . . . . . . . . . . . . 455 Moving tape to another tape library . . . . . 492
Compatibility with other components and versions 456 Loading the extracted data into the new
Estimating database and recovery log requirements 457 database . . . . . . . . . . . . . . 493
Planning data movement from FILE and DISK Migrating a V5 z/OS server by using the network
devices . . . . . . . . . . . . . . . 458 method . . . . . . . . . . . . . . . 494
Estimating storage and device requirements . . . 458 Creating and formatting the new database . . 494
Estimating the time required for migration . . . 458 Moving the server database over a network . . 494
Example: Estimating the migration time based
on the database size . . . . . . . . . . 459 Chapter 22. Configuring the z/OS
Performance tips for the V5 database extraction media server devices on the new
process . . . . . . . . . . . . . . 461 server . . . . . . . . . . . . . . 497
Performance tips for inserting data into the V7.1
database . . . . . . . . . . . . . . 461
Chapter 23. Taking the first steps after
Planning for upgrading multiple servers and
components . . . . . . . . . . . . . . 462 the migration . . . . . . . . . . . 499
Planning for changes to storage agents . . . . . 462 Configuring server options for the migrated server 499
Preparing for operational changes . . . . . . 463 Starting the server . . . . . . . . . . . . 501
Reference information for planning . . . . . . 463 Verifying the migration results . . . . . . . 501
Migration of device and library attributes . . . 464 Recreating disk-based storage pools that were
Migration of server options. . . . . . . . 469 moved to tape . . . . . . . . . . . . . 502
Recreating deleted storage pools . . . . . . 502
Recreating storage pool volumes marked as
Chapter 20. Preparing for the
destroyed. . . . . . . . . . . . . . 502
migration . . . . . . . . . . . . . 473 Restoring data from backed-up storage pools 502
Preparing space for the migration process . . . . 473 Cleaning up by deleting z/OS DISK and FILE
Backing up configuration information . . . . . 474 volumes that were marked as destroyed . . . 503
Installing and configuring the V7.1 server . . . . 474 Registering licenses . . . . . . . . . . . 503
Installing the V7.1 server on AIX or Linux Backing up the database. . . . . . . . . . 504
systems . . . . . . . . . . . . . . 474 Updating automation. . . . . . . . . . . 504
Creating the directories and the user ID for the Updating configuration of storage agents . . . . 505
server instance . . . . . . . . . . . . 477 Beginning operations and monitoring the servers 505
Preparing the V5 server on z/OS for migration . . 479 Migrating data from z/OS media volumes to other
Modifying the server before the migration. . . 479 devices . . . . . . . . . . . . . . . 507
Upgrading the V5 server to V5.5.6 . . . . . 480

viii IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 24. Troubleshooting the DSMUPGRD EXTEND DB (Extend the size of the
migration of a V5 server from a z/OS database) . . . . . . . . . . . . . . . 533
DSMUPGRD EXTEND LOG (Extend the size of the
system to AIX or Linux on System z . 509
recovery log) . . . . . . . . . . . . . 534
Reverting to the V5 server running on z/OS after a
DSMUPGRD UPDATE (Create backup registry
migration. . . . . . . . . . . . . . . 509
entries for a V5 server instance) . . . . . . . 535
Reverting to the V5 server before data is moved
DSMSERV LOADFORMAT (Format a database) 536
to the V7.1 server . . . . . . . . . . . 509
DSMSERV INSERTDB (Move a server database
Reverting to the V5 server before volumes are
into an empty database) . . . . . . . . . . 538
deleted . . . . . . . . . . . . . . 509
ZMSPREPARE (Prepare a server on a z/OS system
Reverting to the V5 server after the V5 database
for migration) . . . . . . . . . . . . . 541
is deleted. . . . . . . . . . . . . . 510
Server startup script: rc.dsmserv . . . . . . . 544
Server startup script: dsmserv.rc . . . . . . . 545
Part 4. Appendixes . . . . . . . . 513 Sample commands to run for validation of the
database upgrade . . . . . . . . . . . . 546
Appendix A. Tivoli support
information . . . . . . . . . . . . 515 Appendix C. Installing server
Communities and other learning resources . . . 515 language packages . . . . . . . . . 547
Searching knowledge bases . . . . . . . . . 517 Server language locales . . . . . . . . . . 547
Searching the Internet . . . . . . . . . 517 Configuring a language package . . . . . . . 551
Using IBM Support Assistant . . . . . . . 517
Finding product fixes. . . . . . . . . . 518 Appendix D. HP-UX system resource
Receiving notification of product fixes . . . . 518 requirements . . . . . . . . . . . 553
Contacting IBM Software Support . . . . . . 518 Estimating required semaphore resources . . . . 553
Setting up and managing support contracts . . 519 Estimating required process resources . . . . . 553
Determining the business impact . . . . . . 519 Estimating required number of threads per process 554
Describing the problem and gathering Viewing and modifying the kernel configuration 554
background information . . . . . . . . . 519
Submitting the problem to IBM Software
Support . . . . . . . . . . . . . . 520
Appendix E. Services associated with
the Tivoli Storage Manager server . . 555
Appendix B. Utilities, scripts, and
commands for server upgrade and Appendix F. Accessibility features for
migration . . . . . . . . . . . . . 521 the Tivoli Storage Manager product
DSMUPGRD QUERYDB (Display information family. . . . . . . . . . . . . . . 557
about a V5 database) . . . . . . . . . . . 522
DSMUPGRD PREPAREDB (Prepare a V5 database Notices . . . . . . . . . . . . . . 559
for upgrade). . . . . . . . . . . . . . 523 Trademarks . . . . . . . . . . . . . . 561
DELETE VOLHISTORY (Delete sequential volume Privacy policy considerations . . . . . . . . 561
history information) . . . . . . . . . . . 524
DSMUPGRD EXTRACTDB (Extract data from a V5 Glossary . . . . . . . . . . . . . 563
server database) . . . . . . . . . . . . 529
The manifest file for the data extraction to
media . . . . . . . . . . . . . . . 531
Index . . . . . . . . . . . . . . . 565

Contents ix
x IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Preface
This publication provides information about upgrading IBM® Tivoli® Storage
Manager servers from one of the supported Version 5 levels to Version 7.1.

Who should read this guide

This publication is intended for server administrators who are responsible for
upgrading Tivoli Storage Manager V5 servers to V7.1.

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

areas:
v The operating system and platform that each server runs on
v Typical administrative operations for Tivoli Storage Manager servers that will be
upgraded
v Storage that is used by the servers that will be upgraded
v The network that is used by the servers

Tip: For information about upgrading the server from V6 to V7.1, see the upgrade
procedures in the Installation Guide.

How to use this guide

To make the best use of this guide, follow the suggested sequence.

If you are upgrading the server from V5 to V7.1 on the same operating system,
follow this sequence:
1. Read the overview information about the updates to the server: Chapter 1,
“Server database updates overview,” on page 3.
2. Read the planning information, and the descriptions of the scenarios:
a. Chapter 2, “Planning the upgrade of the server,” on page 11
b. Chapter 3, “Upgrade scenarios overview,” on page 73
3. Select the scenario to use, and plan for the hardware, software, and storage
space requirements for your server and environment. A worksheet can be used
for space planning: “Worksheet for planning space for the V7.1 server” on page
42.
4. Run a test of the upgrade process: “Testing the upgrade process for a server”
on page 47. Use the results of the test to refine plans, such as the estimated
amount of time that a server will be unavailable because of the upgrade
process.
5. Upgrade the server, following the steps in the scenario that you selected:
v Chapter 4, “Scenario 1: Same system, media method,” on page 91
v Chapter 5, “Scenario 2: Same system, network method,” on page 135
v Chapter 6, “Scenario 3: New system, media method,” on page 177
v Chapter 7, “Scenario 4: New system, network method,” on page 225
6. Complete the upgrade process by following the steps in the section:
v Chapter 10, “Taking the first steps after upgrade,” on page 323

© Copyright IBM Corp. 2009, 2013 xi

If you are migrating the server from V5 to V7.1 on a different operating system,
follow the sequence for your selected migration path:
v Part 2, “Migrating Tivoli Storage Manager V5 servers on AIX, HP-UX, or Solaris
systems to V7.1 on Linux,” on page 355
v Part 3, “Migrating Tivoli Storage Manager V5 servers on z/OS systems to V7.1
on AIX or Linux on System z,” on page 437

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

To search across all publications or to download PDF versions of individual

publications, go to the Tivoli Storage Manager information center at
http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1.

You also can find the Tivoli Storage Manager product family information centers
and other information centers that contain official product documentation for
current and previous versions of Tivoli products at Tivoli Documentation Central.
Tivoli Documentation Central is available at http://www.ibm.com/
developerworks/community/wikis/home/wiki/Tivoli Documentation Central.

xii IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
New for Tivoli Storage Manager Version 7.1
Many features in Tivoli Storage Manager Version 7.1 are new for Tivoli Storage
Manager users.

New in Version 7.1

New features and other changes are available in the Tivoli Storage Manager
Version 7.1 server.

Operations Center updates

AIX Windows Linux

New features are available in Tivoli Storage Manager Operations Center Version
7.1 to help you manage your storage environment.

You can now do the following additional administrative tasks through the
Operations Center:
v Customize the settings for servers and clients by editing the server and client
properties.
v View or cancel the sessions and processes that are in progress by using the
Active Tasks view for servers.
v View the sessions and processes that succeeded or failed by using the
Completed Tasks view for servers.
v View activity log messages that are related to specific alerts, sessions, and
processes. These activity log messages are available on the Alerts page and in
the Active Tasks and Completed Tasks views.
v Manually back up clients, storage pools, and the server database.
v View the replication server configuration for a client.
v Register clients, and configure basic backup settings.
v Suppress risk warnings for specific clients.
v View the authority level of the administrator ID that is used to log in to the
Operations Center.

Automatic client failover for restore operations from replicated

servers
A Tivoli Storage Manager Version 7.1 client can automatically fail over to a target
replication server, if the source replication server is unavailable.

To use automatic failover when node replication is in use, both the source and
target replication servers and the client must be at V7.1. You can use only one
failover server for each replicating node at any time. The failover server is the last
server that a node successfully replicated to. The client can recover data from the
target replication server, but it cannot store data during failover processing.

© Copyright IBM Corp. 2009, 2013 xiii

Software upgrade for the server database manager
Tivoli Storage Manager Version 7.1 is installed with the latest version of the IBM
DB2® database software, V10.5. The DB2 technology provides management
functions for the server database.

The previous Tivoli Storage Manager server release, V6.3, was packaged with a
DB2 V9.7 database.

If you are upgrading the server, you must ensure that the correct version of DB2 is
installed. If you are using a Tivoli Storage Manager V6.1 server, and you want to
upgrade to V7.1, you must upgrade the V6.1 server to V6.2 or V6.3. Then, upgrade
the server from V6.2 or V6.3 to V7.1. The Tivoli Storage Manager V6.1 server was
packaged with a DB2 V9.5 database, which cannot be upgraded to V10.5. The
Tivoli Storage Manager V6.2 and V6.3 servers were packaged with a DB2 V9.7
database, which can be upgraded to V10.5.

Deprecated device types

In Tivoli Storage Manager Version 7.1, certain device types are deprecated.

The following device types are deprecated. While you can use these device types
with Tivoli Storage Manager Version 7.1, plan to migrate data to new devices
before you upgrade to a later release of Tivoli Storage Manager.
v 3490
v 3570
v CARTRIDGE
v OPTICAL
v WORM
v QIC
v DTF

For a list of devices and valid device class formats, see the Tivoli Storage Manager
Supported Devices website for your operating system:

AIX HPUX Solaris Windows

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

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

EMC Centera availability on Linux x86_64 systems for Tivoli

Storage Manager servers
You can now use EMC Centera for versions of Linux x86_64 that are supported by
the Tivoli Storage Manager Version 7.1 server.

For details about Centera-related commands, refer to the Administrator's Reference.

xiv IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
File-space level collocation groups
File-space level collocation groups are introduced in Tivoli Storage Manager
Version 7.1.

You can group file spaces that belong to a single node, which allows data for these
file spaces to be collocated efficiently without requiring separate volumes for each
file space. When you use file-space level collocation groups, you can group data
for a limited set of file systems, for example, virtual machines. Fewer volumes are
required for the data and placement can be coordinated in the server storage
hierarchy.

Use the DEFINE COLLOCMEMBER command to define members of a file-space

collocation group.

For more information about collocation, see Keeping client files together using
collocation in the Administrator's Guide.

For detailed information about the DEFINE COLLOCMEMBER command, see the
Administrator's Reference.

Improved server efficiency when migrating from disk for

nodes with a large number of file spaces
With the new functions that are added to migration processing, you can improve
the efficiency of the server by using file space level migration. Nodes with multiple
large file spaces can take advantage of faster migration processing for
random-access storage pools.

For updated information about how collocation settings affect data processing and
how the server migrates files, see How the server selects files to migrate in the
Administrator's Guide.

Shared memory for database backup and restore operations

You can now use shared memory to reduce processor load and improve
throughput, if the database backup performance is slow.

You can manually configure a Tivoli Storage Manager server, or use the instance
configuration wizard, to use shared memory with DB2.

Immediate use of space that is added to the server database

When you add space to the database, new database directories are now available
for immediate use and parallel I/O performance is improved.

You can add directories to the database by using the EXTEND DBSPACE command. In
Version 7.1, the updates for this operation include distributing data across all
database directories and then reclaiming unused space and returning it to the
system. Because redistribution operations take considerable system resources, plan
ahead when you want to add space to the database. You must complete the
process while the server is not handling a heavy load.

For detailed requirements, see the EXTEND DBSPACE command in the Administrator’s
Reference.

As part of these enhancements, a new server utility, DSMSERV EXTEND DBSPACE, is

available to perform the same function as the EXTEND DBSPACE command, while the

New for Tivoli Storage Manager Version 7.1 xv

server is offline.

Server components that are not delivered with Version 7.1

Tivoli Monitoring for Tivoli Storage Manager and the Administration Center are
not delivered with Tivoli Storage Manager Version 7.1.
Tivoli Monitoring for Tivoli Storage Manager
You can use Tivoli Monitoring for Tivoli Storage Manager V6.3.4 with any
Tivoli Storage Manager V 5.5 or later server. For more information about
installing and configuring Tivoli Monitoring for Tivoli Storage Manager,
see Technote 1649883 at: http://www.ibm.com/support/
docview.wss?uid=swg21649883
Administration Center
The Administration Center is not delivered in V7.1 or later releases. You
can use the V6.3.4 Administration Center with any Tivoli Storage Manager
V6.3 or later server, including to automatically update backup-archive
clients. For more information about the Tivoli Storage Manager
Administration Center, see the Tivoli Storage Manager V6.3 Information
Center at: http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/index.jsp
AIX Linux Windows In V7.1, you can use the Operations Center,
a web-based interface for managing your storage environment. The
Operations Center has many of the same functions as the Administration
Center. For more information about the Operations Center, see Installing
and upgrading the Operations Center and Managing the storage
environment with the Operations Center.

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

Oracle Solaris systems. However, you can use the Operations Center to
manage Tivoli Storage Manager V6.3.4 or later servers that run on HP-UX
or Oracle Solaris systems.

xvi IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Part 1. Upgrading the server from V5 to V7.1
You can upgrade the IBM Tivoli Storage Manager server directly from Version 5 to
Version 7.1.

About this task

Tivoli Storage Manager V7 provides a relational database that is based on IBM®

DB2® technology. When you upgrade the system from V5 to V7.1, you extract the
data in a current Tivoli Storage Manager server database and load it into the new
database structure. Tivoli Storage Manager provides utilities to complete the
process.

Upgrading from V5 to V7.1 requires planning, and possibly testing. Start by

reviewing what is new in V7.1, and collecting information about your current
Tivoli Storage Manager servers.
Who should read this information
This information is intended for system administrators who are responsible
for upgrading Tivoli Storage Manager V5 servers to V7.1. Administrators
should have an understanding of the following areas:
v The operating system and platform that each server runs on
v Typical administrative operations for Tivoli Storage Manager servers that
will be upgraded
v Storage that is used by the servers that will be upgraded
v The network that the servers connect to

Procedure

Review the information about upgrading the server from V5 to V7.1. Here is the
suggested sequence for using this information:
1. Read the overview information about the updates to the server: Chapter 1,
“Server database updates overview,” on page 3.
2. Read the planning information, and the descriptions of the scenarios:
a. Chapter 2, “Planning the upgrade of the server,” on page 11
b. Chapter 3, “Upgrade scenarios overview,” on page 73
3. Select the scenario to use, and plan for the hardware, software, and storage
space requirements for your server and environment. A worksheet can be used
for space planning: “Worksheet for planning space for the V7.1 server” on page
42.
4. Run a test of the upgrade process: “Testing the upgrade process for a server”
on page 47. Use the results of the test to refine plans, such as the estimated
amount of time that a server will be unavailable because of the upgrade
process.
5. Upgrade the server, following the steps in the scenario that you selected:
v Chapter 4, “Scenario 1: Same system, media method,” on page 91
v Chapter 5, “Scenario 2: Same system, network method,” on page 135
v Chapter 6, “Scenario 3: New system, media method,” on page 177
v Chapter 7, “Scenario 4: New system, network method,” on page 225
6. Complete the upgrade process by following the steps in the section:

© Copyright IBM Corp. 2009, 2013 1

v Chapter 10, “Taking the first steps after upgrade,” on page 323

2 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 1. Server database updates overview
Tivoli Storage Manager V7.1 uses a relational database that is based on IBM DB2
technology. Versions of Tivoli Storage Manager earlier than V6.1 did not use the
DB2 technology. Before you upgrade the server to V7.1, learn more about DB2.

The server database

The V7 server integrates IBM DB2 database technology, which provides database
management functions for the server database. An administrator can manage the
server database by using Tivoli Storage Manager administrative interfaces.

The Tivoli Storage Manager administrative interfaces are updated so that an

administrator who is accustomed to working with earlier versions of the server can
continue to administer the server in much the same way as before. The skills of a
database administrator are not required to manage the database. The database
manager program offers the following advantages:
Improved server availability
Online, automated reorganization of the database occurs while server
operations continue.
Audits on the database are run automatically as needed to ensure
consistency. As data is added to the server database, the database manager
checks data constraints and data types. The online checks for integrity
prevent problems for which offline audits had been needed in earlier
releases.
Improved scalability
The server has an improved capacity for concurrent operations, through
the larger maximum size for the recovery log.
The maximum number of objects that can be managed by a single server is
increased.
Practical database size might be limited by the time that is available to
complete operations such as database backup, client backups, and data
deduplication.
Complete SQL function
You can obtain information from the server database more easily than
before with full-function SQL queries.
The database makes more sophisticated SQL queries on the data possible.
If you choose to take advantage of its full capabilities, SQL skills might be
required to develop new tools.

© Copyright IBM Corp. 2009, 2013 3

Server database updates overview

Database space for a V7.1 server

The database is stored on the set of directories that you specify. The amount of
space that is available to the directories determines the amount of space that is
available for the database.

With V7.1, you do not create or track database volumes for the server database.
Instead you create and designate directories that the server can use for the
database. The database manager that is part of the server automatically manages
the space available to the directories as database space.

The database can be distributed across as many as 128 directories. Place the
database directories on fast, reliable disks that are configured for random access
I/O. Locating each directory on a different file system provides the best
performance because the data is striped across the directories. Enable read cache
for the database file systems, and enable write cache if the disk subsystem
supports it.

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

A practical size for the database might be limited in your environment by the time
that is available to complete operations such as database backup, client backups,
and data deduplication (if used).

Recovery log
The recovery log helps to ensure that a failure (for example, a system power
outage) does not leave the database in an inconsistent state. The recovery log is
also essential when you must restore the database.

For details, see the recovery log section in the Administrator's Guide.

Operation changes
The server delivers significant improvements in operations, including more
automated database management.

For details about operations with a V7.1 server, see the Administrator's Guide
section about managing the database and recovery log.

Database operations
The database manager controls operations for the database by running automatic
tasks that can help keep the database in good condition.

The database manager controls the storage space for the database. The server can
use all of the space that is available to the directories that you specify for the
database. In V7, you do not manage individual volumes for the database, which
was necessary in V5. When the database needs more space, instead of adding
volumes and extending the database, you add more directories (preferably on
different physical volumes) to the database space.

Database reorganization occurs automatically. Based on activity, the database

manager program selects database tables to analyze, to determine when
reorganization is needed for the tables. The database manager then runs
reorganization while server operations continue.

4 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Server database updates overview

As data is added to the server database, the database manager automatically

checks data constraints and data types. The online integrity checks prevent
problems for which offline audits were required in earlier releases.

Monitor the space that is used by the server and the space that is available in the
file systems where the directories are located. Ensure that space is always
available. You can obtain information about database space usage and recovery log
usage by reviewing data in the Operations Center or by issuing administrative
commands.

Tivoli Storage Manager V7.1 is installed with the DB2 database application. Users
who are experienced DB2 administrators can choose to perform advanced SQL
queries and use DB2 tools to monitor the database. However, do not use DB2 tools
to change DB2 configuration settings from those settings that are preset by Tivoli
Storage Manager. Do not alter the DB2 environment for Tivoli Storage Manager in
other ways, such as with other products. The Tivoli Storage Manager server was
built and tested with the data definition language (DDL) and database
configuration that Tivoli Storage Manager deploys.

Attention: Modifying the DDL or database configuration without using Tivoli

Storage Manager interfaces can adversely affect performance, damage or destroy
the server database, or cause data to become lost. Observe the following
restrictions:
v Do not use database tools or interfaces other than the tools or interfaces that are
delivered with Tivoli Storage Manager to change configuration settings from
those that are set by Tivoli Storage Manager during the installation process.
v Do not alter the DB2 environment.
v If you use database tools or interfaces other than the tools or interface that are
provided by Tivoli Storage Manager, you must treat the server database as
read-only. Do not use other interfaces to modify the Tivoli Storage Manager
server database.
v Do not alter the DB2 software that is installed with Tivoli Storage Manager
installation packages and fix packs.
v Do not install or upgrade to a different version, release, or fix pack of DB2
software.

Database protection and recovery

Database backups are essential to protect all the data that the server manages. You
can recover a damaged or lost database by using database backups, together with
volume history backups and the recovery log. In this way, you can restore the
database to the latest possible time, or to a specific point in time.
Database backups
Protect the server by using administrative schedules to run database
backups regularly, at least once per day. More frequent backups might be
needed if the server handles high numbers of client transactions.
You can create full, incremental, and snapshot backups of the server
database. You can schedule the backups to run automatically, or perform
the backups manually.
The archive log is included in database backups, and is used for
roll-forward recovery of the database. At the end of a full database backup,
space is recovered by the automatic pruning of older archive log files that

Chapter 1. Server database updates overview 5

Server database updates overview

are no longer needed. The archive log files that are included in a backup
are automatically pruned after two more full database backups are
completed.
If space for the recovery log is limited, more frequent full backups of the
database might be required so that space is recovered through the
automatic pruning operation.
An incremental backup of the database includes all changes to the database
since the last full backup. In earlier versions of the server, an incremental
backup included changes since the last full or incremental backup, and
multiple incremental backups might have been needed to restore the
database. With V7.1, when you must restore a database, you must use the
last full backup and only the last incremental backup.
Automatic backups are performed by the database manager based on
active log space usage since the last database backup and the ratio of space
that is used to total space for the active log. To configure automatic
database backups, during initial configuration of the server you specify a
device class that is to be used for these backups. The database backups
that are performed by the database manager are either full or incremental
backups.
Database mirroring
The database cannot be mirrored through Tivoli Storage Manager in V7.1.
Use hardware mirroring instead.
Recovery log mode
The V7.1 server always runs in a mode that is equivalent to the
roll-forward mode.
Changes to the database are recorded in the recovery log to maintain a
consistent database image. Active and archive log files, which are included
in database backups, make it possible to restore the server to the latest
time possible. You can also restore the database to a specific point in time.
To help ensure that the required log information is available for restoring
the database, you can specify that the active log is mirrored to another file
system location. For the best availability, locate the active log mirror on a
different physical device.
Files that are required to restore the database
Both the volume history file and the device configuration file are required
to restore the database.
Before V6.1, the volume history file was optional for restoring the database,
and if a device configuration file was not available, you could re-create the
file. Starting with the V6.1 server, both the volume history file and the
device configuration file must be available; the device configuration file
cannot be re-created.

Important: Ensure that the server options file includes the following
options:
v At least one VOLUMEHISTORY option with the name of a file to be
automatically updated when volume history information changes.
v At least one DEVCONFIG option with the name of a file in which to store a
backup copy of device configuration information.
Disaster recovery manager
The disaster recovery manager works with the new database and database

6 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Server database updates overview

backup operations. Some of the stanzas in the recovery plan are new or
changed to accommodate the changes to the database operations.
Database restoration
The database can be restored to the latest possible time, or to a specific
point in time. The volume history file and the device configuration file are
required for restoring the database.
You can restore the database to a location that is different from the original
location. Using database restore is one way to move a server.

Multiple server instances on a single system

A server instance runs the server program by using its unique database, recovery
log, and server options. To run multiple server instances on a single system, set up
separate database and recovery log directories. In addition, set up an instance
directory for each server to contain the server options file and other files that are
needed to run each server instance.

On AIX®, HP-UX, Linux, and Solaris systems, each server instance requires a
unique user ID that is the instance owner. On Windows systems, the server
instances can be owned by the same or different user accounts.

The files for each instance are stored separately from the server program files. As
part of server configuration, you create a directory to store the files for the server
instance. The following files are stored in the instance directory:
v The server options file, dsmserv.opt
v The device configuration file, if the DEVCONFIG server option does not specify a
fully qualified name
v The volume history file, if the VOLUMEHISTORY server option does not specify a
fully qualified name
v Volumes for DEVTYPE=FILE storage pools, if the directory for the device class
is not fully specified, or not fully qualified
v The dsmserv.V6lock file
v User exits
v Trace output (if not fully qualified)

Database and recovery log files are stored in separate directories, not in the
instance directory.

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

AIX HPUX Linux Solaris

For example, to run two server instances, tsminst1 and tsminst2, you might create
instance directories such as /tsminst1 and /tsminst2. In each directory, place the
dsmserv.opt file for that server. Each dsmserv.opt file must specify a different port
for the server to use. To automatically start the two server instances, you can use
the script, rc.dsmserv.

Chapter 1. Server database updates overview 7

Server database updates overview

Changes to starting the server

You can automatically start multiple instances of the Tivoli Storage Manager server
at system startup.

Startup of server instances (AIX, HP-UX, Linux, Solaris)

AIX HPUX Linux Solaris

You can automatically start multiple instances of the Tivoli Storage Manager server
at system startup (for example, from /etc/inittab on an AIX system) without the
need for user-configured scripts. Two DSMSERV options and a script make it possible
to start server instances in this way.

The preferred way to start the server is by using the instance user ID. By using the
instance user ID, you simplify the setup process and avoid potential issues.
However, in some cases, it might be necessary to start the server with the root user
ID. For example, you might want to use the root user ID to ensure that the server
can access specific devices. To start the server, the root user ID must meet the
following requirements:
v Have authority to issue the start command for the server and database manager
v Belong to the group that is specified by the database manager SYSADM_GROUP
setting
v Have database administration authority (DBADM) granted by the instance user
ID
v Have authority to access the server database
v Have authority to use all files, directories, and devices that are required by the
server
Before you start the server with the root user ID, explicitly grant server database
authority to the root user ID and verify all other authorities for the root user ID.

Tip: Solaris If you are running a Tivoli Storage Manager server on a Solaris
system, you can use the Solaris Service Management Facility (SMF) to set up and
control the Tivoli Storage Manager server as a service. For more information, see
Technote 7021102 (http://www.ibm.com/support/docview.wss?uid=swg27021102).
Switching user IDs
The -u userID option for DSMSERV makes it possible for the server to switch
user IDs at invocation. This option is primarily intended to be used in
/etc/inittab for AIX systems, or similar methods on other platforms.
Configuration is easier if you can switch to the user ID that is the instance
owner at startup.
Changing the current working directory
The -i instance_dir option for DSMSERV makes it possible for the server to
change its current working directory at invocation. This option is primarily
intended to ensure that multiple instances of the Tivoli Storage Manager
server can be launched from /etc/inittab without the need for
user-configured scripts.
Setting up the environment by using a script
A script, /opt/tivoli/tsm/server/bin/rc.dsmserv, is provided for use on
AIX, HP-UX, Linux, and Solaris systems. The script sets up environment
variables and changes the library path to resolve libraries that are required
by Tivoli Storage Manager. The library path is the variable:
AIX LIBPATH

8 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Server database updates overview

Linux LD_LIBRARY_PATH
Invoke the script from the system startup location, for example,
/etc/inittab on an AIX system.
Related tasks:
“Starting the server on AIX, HP-UX, Linux, and Oracle Solaris systems” on page
325

Startup of server instances (Windows)

Windows

You can automatically start multiple instances of the Tivoli Storage Manager server
at system startup by configuring the options for the server as a service.

You can set the start mode and options for the server service so that the server
starts at system startup.

When the server is started as a service, the service for the corresponding database
manager is also automatically started. The service for the database manager is
named as a DB2 service, and its name includes the name of the server instance. For
example, the database-manager service for the Server1 server instance has the
name: DB2 - DB2TSM1 - SERVER1

When you stop the service for the server, the service for the database manager is
not automatically stopped. If you intend to stop both the server and its database
manager, you must stop the service for the database manager separately.
Related concepts:
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555
Related tasks:
“Starting the server on Windows systems” on page 331

Files and environment changes

Locations and names of some files are changing from previous versions.
AIX Installation location
The location of the files for the Tivoli Storage Manager server and device
driver is changed from /usr to /opt.
The location of the files for the Tivoli Storage Manager storage agent is
also changed from /usr to /opt.
AIX HPUX Linux SolarisLog files location
During installation, logs are written in /var/tivoli/tsm. Logs and trace for
the configuration and upgrade wizards are also written to this location.
AIX HPUX Linux SolarisFile set names
File sets have been merged and the names changed. Except for messages,
the server is contained in tivoli.tsm.server.
Environment variables
v The DSMSERV_DIR variable is no longer valid. The Tivoli Storage
Manager server automatically determines the directory in which it
resides, and looks for necessary exits, loadable modules, and message
files relative to that directory. On Windows, the program uses registry
entries.
Chapter 1. Server database updates overview 9
Server database updates overview

v The DSMSERV_CONFIG variable is no longer valid.

Important: When you use the upgrade utilities for a V5 server,

environment variables still must be set for the utilities. See “Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 292 for the details.
Related tasks:
“Setting environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 292

Administrative command changes

With the new database manager, you still manage the database using Tivoli
Storage Manager commands. Tasks for administering the database are different, so
changes to the server include new, changed, and deleted administrative
commands.

Some server options and utilities also change.

Related reference:
“Command and option changes” on page 51

10 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 2. Planning the upgrade of the server
Planning the upgrade to Tivoli Storage Manager V7.1 is important because, in
addition to installing the new software, you must move the contents of the V5
server database into the V7.1 database.

About this task

Tivoli Storage Manager V5 servers can be upgraded directly to V7.1. However,

Tivoli Storage Manager V7.1 servers cannot be used with V5 clients or with other
servers in the system that are at V5. Unless all V5 clients and V5 servers can be
upgraded at the same time, consider upgrading the server to a level that can be
used with V5 clients and V5 servers. Then, upgrade all servers and clients to V7.1
when possible. For information about the levels of the Tivoli Storage Manager
server that can be used with V5 clients and V5 servers, see the following technotes:
IBM Tivoli Storage Manager Server-Client Compatibility and Upgrade
Considerations
(http://www.ibm.com/support/docview.wss?uid=swg21053218)
Storage-agent and library-client compatibility with the IBM Tivoli Storage
Manager server
(http://www.ibm.com/support/docview.wss?uid=swg21302789)

When you move data from a V5 server database to a V7.1 database, a large
amount of system processing capacity is used. The move also requires a large
amount of I/O activity.

Procedure

As you start to plan the upgrade process, consider the following options:
v You can test the upgrade on nonproduction systems. Testing gives you
information about how long the upgrade of the server database takes, which
will help you to plan for the time that the server will be unavailable. Some
databases might take much longer than others to upgrade. Testing also gives
you more information about the size of the new database compared to the
original, giving you more precise information about database storage
requirements.
v If you have multiple servers, you can upgrade one server first, to determine how
the upgrade process will work for your data. Use the results of the first upgrade
to plan for upgrading the remaining servers.
Related tasks:
“Estimating the upgrade time” on page 42

© Copyright IBM Corp. 2009, 2013 11

Upgrading the server from V5 to V7.1

The process for upgrading the server from V5 to V7.1

Moving from Tivoli Storage Manager V5 to V7.1 requires more preparation and
planning than previous upgrades. Because of the database program that the server
is using, an existing database must be moved into the new database structure by
using the provided upgrade tools.

Except for the database extraction and insertion steps, the server upgrade process
is similar to the disaster recovery process. Critical server files, such as the option
and device configuration files, must be available, and storage pool devices must be
made available to the upgraded server.

The major steps in the upgrade process from V5 to V7.1 are as follows:
1. Plan system hardware and software, and estimate the upgrade time.
Use information about the Tivoli Storage Manager upgrade process together
with operational requirements for your existing servers to decide how and
when to perform the upgrade.

Tip: If you are introducing new hardware or changes in the storage system
infrastructure, plan the zoning for the storage area network (SAN). Allow time
to create device statements and paths, and to check in tape volumes following
the upgrade. For IBM tape devices, no multipathing driver is available for tape
drives that are distributed over more than one adapter. Use zoning and device
definitions to balance the workload.
2. Back up the Tivoli Storage Manager server database and configuration files.
Ensure that at least one full database backup is available onsite.

Tip: If you must restore the database after a failed upgrade, having an onsite
backup database saves time.
3. Install the server code. Installation tasks include the following:
v Installing the new server code, which includes the server and its database
manager program. Configure a user ID for the new server instance.
v Installing the upgrade utilities package on the system where the existing V5
server is located.
4. Upgrade the database. This task includes preparing the database, and then
moving the database. Use the upgrade utilities or the upgrade wizard to
complete these tasks.
The upgrade utilities or upgrade wizard extracts data from an existing database
and inserts the data into a new V7.1 database. Media or the network can be
used for the data movement.
As a database is moved into the new database structure, the validity of the data
is checked against constraints that are enforced in the new database. The
upgrade tools automatically correct some errors in the database. Other errors
might require manual correction.
If you use the wizard, you are guided to complete the upgrade steps in the
correct order. If you are performing the upgrade manually by using utilities
from a command line, follow the procedure carefully.
5. Verify the upgrade by running basic operations and querying information
about the system to confirm that all information transferred correctly.

To help you decide how to perform the upgrade process, review the information
that compares upgrade methods, and the descriptions of upgrade scenarios.
Related tasks:

12 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Chapter 3, “Upgrade scenarios overview,” on page 73

Comparison of upgrading on an existing system and a new

system
Upgrading the V7.1 server on an existing system requires that the system is
unavailable for production use during installation and when the data is moved
into the new database. Moving the server to a new system gives you more
flexibility in terms of the upgrade procedure, but with some additional costs.

If you are upgrading Tivoli Storage Manager to a different operating system, a

limited set of migration paths is available. For instructions about migrating a
server that is running on a z/OS® operating system, see Part 3, “Migrating Tivoli
Storage Manager V5 servers on z/OS systems to V7.1 on AIX or Linux on System
z,” on page 437. For instructions about migrating a server that is running on an
AIX, HP-UX, or Solaris operating system, see Part 2, “Migrating Tivoli Storage
Manager V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux,” on page
355.

The following table lists items to consider when you decide how to upgrade the
server.
Table 1. Considerations for selecting a server upgrade scenario
Item Upgrade on an existing system Upgrade on a new system
System hardware More resources (disk space, memory, A new system that meets requirements,
and possibly processor capacity) are in addition to the existing system, is
required on the existing system. required.

You must upgrade to a new system if

the existing server is on one of the
platforms that are not supported for
V7.1.
Software Software on the system must meet Software on the new system must meet
requirements for V7.1. requirements for V7.1.

The V7.1 server cannot coexist with Software on the original V5 system must
other versions on the same system. meet requirements for the upgrade
utilities (upgrade utilities requirements
are the same as for a V5.5 server).

Chapter 2. Planning the upgrade 13

Upgrading the server from V5 to V7.1

Table 1. Considerations for selecting a server upgrade scenario (continued)

Item Upgrade on an existing system Upgrade on a new system
V5 server availability All V5 server instances on the system You can stage the upgrade of multiple
are unavailable after the V7.1 server servers because the V5 server program
program is installed. Data that is can be left on the original system.
managed by a server instance cannot be
accessed until the upgrade process is After the database extraction completes,
complete for that server instance. the V5.5 server on the original system
can be restarted. However, if you restart
To revert to using the V5 server, you the V5.5 server for production
must reinstall the same level of the V5 operations after database extraction, you
server program as before. Then, restore must carefully plan how you will
the V5 database from a backup that was complete the upgrade process to avoid
made before the upgrade process. data loss. See the Tivoli Storage Manager
wiki (http://www.ibm.com/
developerworks/mydeveloperworks/
wikis/home/wiki/Tivoli Storage
Manager) for information and discussion
about hybrid upgrade methods to use,
including export and import operations,
and important tips about how to avoid
data loss.

A V5.3 or V5.4 server on the original

system can be restarted, but its database
must be restored first from the database
backup.
Database movement method The database can be moved with a You must have either a network
local-host network connection, or can be connection between the existing and the
moved by using disk or external media. new systems, or a device and media
available to store the extracted database.
Storage devices and storage Existing attached devices can be used. The new system must have access to all
pools storage that is used by the original
You must change ownership or system.
permissions for all disk space that is
used for storage pools (device types of Definitions for devices such as FILE
FILE or DISK). The user ID that you will device types might need to be changed
create to be the owner of the upgraded after the upgrade.
server instance must be given ownership
or read/write permission to the disk You must change ownership or
space for storage pools. permissions for all disk space that is
used for storage pools (device types of
FILE or DISK). The user ID that you will
create to be the owner of the upgraded
server instance must be given ownership
or read/write permission to the disk
space for storage pools.

If the environment includes a storage

area network (SAN), zone changes or
logical unit number (LUN) masking
changes might be necessary.

14 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 1. Considerations for selecting a server upgrade scenario (continued)

Item Upgrade on an existing system Upgrade on a new system
Client and storage agent No changes are necessary. The network address on clients and
connections, and library storage agents must be updated after the
sharing upgrade. Alternatively, you can make
network changes so that the new system
has the same address as the original
system.

Similarly, if the server is in a library

sharing relationship with other servers,
network address changes might be
necessary after the upgrade.

Related concepts:
“Hardware and software requirements for the upgraded server” on page 19
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39
Related reference:
“Hardware and software requirements for the V5 server system that is being
upgraded” on page 17

Comparison of methods for moving data to the V7.1 database

The upgrade utilities are required for moving data from an earlier version of the
database into the V7.1 database. You can use the upgrade wizard to run the
utilities with guidance.

To move the database, you must install the upgrade utilities package on the system
where the original server database is located. The utilities package is available
from the FTP downloads site for the Tivoli Storage Manager product. Installing the
upgrade utilities package is a separate task from installing the V7.1 server.

You can move the database in two ways:

Media method
You can extract data from the original database to media, and later load
the data into the new database. The new database can be located either on
the same system or a different system.
The media method can be a good method to choose if you are upgrading
to a new physical system for the server, and you cannot have both your
old and new systems available at the same time or cannot connect them
with a high speed network. It is also a good method to choose if you are
not upgrading to a new system, and want the V7.1 server to use the same
disk storage space that is used by the V5 server.
Network method
You can simultaneously extract data from the original database and load
the data into the new database. The new database can be located either on
the same system or on a system connected on the network.
The network method is a good method to choose if you are looking for
maximum performance from the upgrade utility, particularly if you are
migrating from one physical system to a new system, and the systems are
connected by a high speed network. The network method reduces the

Chapter 2. Planning the upgrade 15

Upgrading the server from V5 to V7.1

amount of storage that is required because there are no requirements for

disk or tapes to hold the data unloaded from the V5 database.

With either method, the original server cannot be running in production mode
while the data is being extracted.
Related concepts:
“DSMUPGRD upgrade utilities”
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39

DSMUPGRD upgrade utilities

You can use the DSMUPGRD upgrade utilities to prepare and extract data from a V5.3,
V5.4, or V5.5 server database for insertion into an empty V7.1 server database.

The DSMUPGRD utilities are run on the original database.

The DSMUPGRD PREPAREDB utility upgrades a server database version to V5.5, and
performs some cleanup to prepare for the extraction process.

Important: After a V5.3 or V5.4 server database is upgraded to V5.5, the database
can no longer be used by a V5.3 or V5.4 server. If you do not want the database on
your production server to be upgraded, you can restore the database backup on
another system. Then, upgrade that copy of the database.

The DSMUPGRD EXTRACTDB utility extracts the data from a server database. You can
use the utility to simultaneously extract and insert the data into a new database
over a network. Alternatively, you can use the utility to extract the data to media
for later insertion into a new database. The data extraction operation can be run
with multiple processes.

If a problem occurs during the database preparation or extraction, the DSMUPGRD

EXTEND DB and DSMUPGRD EXTEND LOG utilities are available to make more space
available for the database or log.
Related reference:
“DSMUPGRD QUERYDB (Display information about a V5 database)” on page 522
“DSMUPGRD PREPAREDB (Prepare a V5 database for upgrade)” on page 523
“DSMUPGRD EXTRACTDB (Extract data from a V5 server database)” on page 529

“DSMUPGRD EXTEND DB (Extend the size of the database)” on page 533

“DSMUPGRD EXTEND LOG (Extend the size of the recovery log)” on page 534
“DSMUPGRD UPDATE (Create backup registry entries for a V5 server instance)”
on page 535
“DSMSERV INSERTDB (Move a server database into an empty database)” on page
538
DSMSERV LOADFORMAT (Format a database)

16 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Hardware and software requirements for upgrading to the V7.1 server

Use the requirements that are described here as a starting point.

For the latest information about hardware and software requirements, see the
Tivoli Storage Manager Supported Operating Systems technote at
http://www.ibm.com/support/docview.wss?uid=swg21243309.

Restrictions: AIX HPUX Linux Solaris You can install and run the
V7.1 server on a system that already has DB2 installed on it, whether DB2 was
installed by itself or as part of another application, with restrictions. For details,
see the section about compatibility of the Tivoli Storage Manager server with other
DB2 products on the system in the Installation Guide.

Restriction: Windows You cannot install and run the V7.1 server on a system that
already has DB2 installed on it, whether DB2 was installed by itself or as part of
another application. The V7.1 server requires the installation and use of the DB2
version that is packaged with the V7.1 server. No other version of DB2 can exist on
the system.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39

Hardware and software requirements for the V5 server system

that is being upgraded
A V5.3, V5.4, or V5.5 server can be upgraded to V7.1. The upgrade utility package
must be installed on the system where the V5 database is located. The V5 system
must meet the requirements for running the upgrade utilities, even if you intend to
place the upgraded server on a new system.

V5.3 or V5.4 servers might be running on operating systems that are not supported
by the upgrade utilities. Therefore, you might need to update your system before
you begin the upgrade procedure. Use the information in Table 2 on page 18 to
determine whether you are using one of the operating system versions that must
be upgraded.

When you prepare to upgrade a system, you must ensure that the source server is
at V5.3.6 or later, and that the latest interim fix for the selected level is installed.

To optimize the upgrade process and avoid potential issues, consider upgrading
the V5 server to the latest available level and installing the latest interim fix for
that level. Follow the guidelines in “Determining the appropriate level for a V5
server before an upgrade” on page 36. To download the latest fix pack and interim
fix, go to the IBM Support Portal at http://www.ibm.com/support/entry/portal/
Downloads. Locate the appropriate version of Tivoli Storage Manager.

If your operating system is listed in the second column of the following table, you
must upgrade the system to the required minimum level in the third column, or to
a later level.

Chapter 2. Planning the upgrade 17

Upgrading the server from V5 to V7.1

Table 2. Operating system versions that must be upgraded to run the upgrade utilities
Operating
system Version that must be upgraded Required minimum level
AIX v IBM AIX 5L™ V5.1 (32 or 64 bit) v AIX V5.3 (64 bit only)
v AIX V5.2 (32 or 64 bit) v AIX V7.1 (64 bit only)
HP-UX v PA-RISC: v PA-RISC:
HP-UX 11i V1.0 (32 or 64 bit) HP-UX 11i v2 (64 bit)
HP-UX 11i v3 (64 bit)
Linux on v Red Hat® Enterprise Linux 3 v Red Hat Enterprise Linux 4
Power® (supported on POWER5 processors v Red Hat Enterprise Linux 5
only)
v SUSE Linux Enterprise Server 9
v SUSE Linux Enterprise Server and 10
8/UnitedLinux 1.0 (supported only
v Asianux 2.0 - Red Flag DC 5.0 and
on processors earlier to POWER5)
Haansoft Linux 2006 or Asianux 3.0
v Miracle Linux 4.0 or Asianux 2.0
v V2.3.3 or later of the GNU C
v GNU C libraries 2.2.5-108 libraries that are installed on the
target system
Linux x86 v Red Hat Enterprise Linux 3 (AS, v Red Hat Enterprise Linux 4
WS, ES) v Red Hat Enterprise Linux 5
v SUSE Linux Enterprise Server v SUSE Linux Enterprise Server 9
(SLES) 8 / UnitedLinux 1.0 and 10
v V2.2.5-213 of the GNU C libraries v Asianux 2.0 - Red Flag DC 5.0,
Miracle Linux 4.0, and Haansoft
Linux 2006 or Asianux 3.0
v V2.3.3 or later of the GNU C
libraries that are installed on the
target system
Linux v Red Hat Enterprise Linux 3 v Red Hat Enterprise Linux 4
x86_64
v Red Flag Advanced Server 4.1 v Red Hat Enterprise Linux 5
v SUSE Linux Enterprise Server 8 v SUSE Linux Enterprise Server 9
v V2.2.5-213 of the GNU C libraries and 10
v Asianux 2.0 - Red Flag DC 5.0,
Miracle Linux 4.0, and Haansoft
Linux 2006 or Asianux 3.0
v V2.3.3 or later of the GNU C
libraries that are installed on the
target computer
Linux on v SUSE Linux Enterprise Server 8 / v Red Hat® Enterprise Linux 4
System z UnitedLinux 1.0 v Red Hat® Enterprise Linux 5
v Version 2.2.5-108 of the GNU C v SUSE Linux Enterprise Server 9
libraries and 10
v V2.3.3 or later of the GNU C
libraries that are installed on the
target system
Oracle v Oracle Solaris 8 (64 bit) v SPARC 64 bit:
Solaris
Oracle Solaris 9
Oracle Solaris 10
v x86_64:
Oracle Solaris 10

18 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 2. Operating system versions that must be upgraded to run the upgrade
utilities (continued)
Operating
system Version that must be upgraded Required minimum level
Microsoft v Windows 2000 Professional v Windows Server 2003 (Standard,
Windows Enterprise, or Datacenter) Edition
v Windows 2000 Server
v Windows 2000 Advanced Server v Windows Server 2003 (Standard,
Enterprise, or Datacenter) x64
v Windows 2000 Datacenter Server
Edition
v Windows Server 2008 (Standard,
Enterprise, or Datacenter) Edition
v Windows Server 2008 (Standard,
Enterprise, or Datacenter) x64
Edition

Tip: The system requirements for the upgrade utility are the same as the system
requirements for a V5.5 server because the upgrade utility is based on the V5.5
server code. See system requirements for a V5.5 server at one of the following
websites. Compare the system on which your V5.3 or V5.4 server is running with
the system requirements for a V5.5 server.
AIX http://www.ibm.com/support/docview.wss?uid=swg21052220
HP-UX
http://www.ibm.com/support/docview.wss?uid=swg21052219
Linux
Linux on Power Systems™ Servers: http://www.ibm.com/support/
docview.wss?uid=swg21108042
Linux x86: http://www.ibm.com/support/
docview.wss?uid=swg21107360
Linux x86_64: http://www.ibm.com/support/
docview.wss?uid=swg21204361
Linux on System z: http://www.ibm.com/support/
docview.wss?uid=swg21108040
Solaris
http://www.ibm.com/support/docview.wss?uid=swg21053216
Windows
http://www.ibm.com/support/docview.wss?uid=swg21064234

Hardware and software requirements for the upgraded server

Use these requirements as a starting point. Find the latest information about
hardware and software requirements on the product support site.

The product support site is located at http://www.ibm.com/support/entry/

portal/Overview/Software/Tivoli/Tivoli_Storage_Manager.

If you are upgrading Tivoli Storage Manager on a different operating system, a

limited set of migration paths is available. For instructions about migrating a
server that is running on a z/OS operating system, see Part 3, “Migrating Tivoli
Storage Manager V5 servers on z/OS systems to V7.1 on AIX or Linux on System
z,” on page 437. For instructions about migrating a server that is running on an

Chapter 2. Planning the upgrade 19

Upgrading the server from V5 to V7.1

AIX, HP-UX, or Solaris operating system, see Part 2, “Migrating Tivoli Storage
Manager V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux,” on page
355.

Some platforms that were supported for earlier versions of the server are not
supported for V7.1. If the server that you want to upgrade is running on one of
these platforms, you cannot upgrade your server to V7.1 on the same platform.
You must install your V7.1 server on a system that is a specific supported
platform, depending on the original platform. For required platforms, see the
following table.
Table 3. Required platforms for upgrading from V5 to V7.1
Platform for V5 server Required platform for upgrade to V7.1
HP-UX running on a PA-RISC system HP-UX running on an Intel Itanium system
Linux running on an Itanium system (IA64) Linux running on an x86_64 system
Linux running on an x86_32 system Linux running on an x86_64 system
Solaris running on an x86_64 system Linux running on an x86_64 system
Windows running on an Itanium system Windows running on an x86_64 system
(IA64)

If you are upgrading from Tivoli Storage Manager V5 to V7.1 on a new system,
restrictions apply. Ensure that you install the V7.1 server in a compatible hardware
and software environment, as described in the following table.
Table 4. Requirements for upgrading from V5 to V7.1 on a new system
V5 server V7.1 server Comments
AIX running on an IBM AIX running on an IBM
POWER® system POWER system
HP-UX running on an HP-UX running on an
Itanium system Itanium system
HP-UX running on a HP-UX running on an HP-UX running on PA-RISC
PA-RISC system Itanium system is not supported for V7.1
servers.
Linux running on an IBM Linux running on an IBM
POWER system POWER system
Linux running on an Itanium Linux running on an x86_64 Linux running on Itanium is
system (IA64) system not supported for V7.1
servers.
Linux running on an x86_32 Linux running on an x86_64 Linux running on x86_32 is
system system not supported for V7.1
servers.
Linux on System z® Linux on System z

20 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 4. Requirements for upgrading from V5 to V7.1 on a new system (continued)

V5 server V7.1 server Comments
Solaris running on an x86_64 Operating system depends A V7.1 server cannot be
system on the migration method installed on a Solaris x86_64
system. However, you can
migrate a V5 server that is
running on a Solaris x86_64
operating system to V7.1 on
a Linux x86_64 operating
system. For instructions, see
Part 2, “Migrating Tivoli
Storage Manager V5 servers
on AIX, HP-UX, or Solaris
systems to V7.1 on Linux,”
on page 355.

Alternatively, you can

migrate the Solaris x86_64
system by installing a V7.1
server on any operating
system that is supported for
V7.1. Then, use Tivoli
Storage Manager server
EXPORT and IMPORT
commands to move the
server from the V5 source
system to the V7.1 target
system.
Windows running on an Windows running on an Windows running on
Itanium system (IA64) x86_64 system Itanium is not supported for
V7.1 servers.
Windows running on an Windows running on an Windows running on x86_32
x86_32 system x86_64 system is not supported for V7.1
servers.
z/OS AIX or Linux on System z See the section on migrating
from V5 on z/OS to V7.1 on
AIX or Linux on System z.

Server requirements on AIX systems

AIX

Check that your AIX system meets the requirements.

Hardware requirements

The following table describes the minimum hardware requirements.

For information about estimating the total disk space that is required, see
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39.

Chapter 2. Planning the upgrade 21

Upgrading the server from V5 to V7.1

Table 5. Hardware requirements

Type of
hardware Hardware requirements
Hardware An appropriately configured POWER4, POWER5, POWER6®, POWER7®
systems computer (64-bit)
Disk space The following minimum values for disk space:
v 512 MB for the /var directory
v 5 GB for the installation directory
v 2 GB for the /tmp directory
v 300 MB for the /usr directory
v 2 GB in the home directory
Tip: Expect to use more space for problem determination.
v 2 GB for the shared resources area

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

For optimal performance and to facilitate I/O, specify at least two equally
sized containers or Logical Unit Numbers (LUNs) for the database. See
Optimizing Performance for more information about the configuration of
directories for the database. In addition, each active log and archive log
should have its own container or LUN.

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

22 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Software requirements

The following table describes the minimum software requirements.

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

AIX 7.1 running in a 64-bit kernel environment.

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

For the latest recommendations about AIX maintenance levels, see

http://www.ibm.com/support/docview.wss?uid=swg21165448
Communication A configured communication method.
protocol
Processing Asynchronous I/O must be enabled.
Device drivers The Tivoli Storage Manager device driver required for non-IBM drives
and tape libraries. The Tivoli Storage Manager device driver package
contains device driver tools and ACSLS daemons.

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

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

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

Chapter 2. Planning the upgrade 23

Upgrading the server from V5 to V7.1

Server requirements on HP-UX systems

HPUX

Check that your HP-UX system meets the requirements.

You cannot run a V7.1 server on a PA-RISC system that is running an HP-UX
operating system. If the server that you want to upgrade is running on this
operating system, you cannot upgrade your server to V7.1 on the same operating
system. You must install your V7.1 server on an Itanium system that is running the
HP-UX operating system, and then use the network or media method to upgrade
your V5 server to that system.

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

Hardware requirements

For information about estimating the total disk space that is required, see
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39.
Table 7. Hardware requirements
Type of
hardware Hardware requirements
Hardware A 64-bit Intel Itanium system.
Disk space The following minimum values for disk space:
v 512 MB for the /var directory
v 6 GB in the installation directory
v 2 GB for the /opt directory if you do not create mount points
v 2 GB for the /tmp directory
v 300 MB for the /usr directory
v 2 GB in the home directory
Tip: Expect to use more space for problem determination.
v 2 GB for the shared resources area

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

For optimal performance and to facilitate I/O, specify at least two equally
sized containers or Logical Unit Numbers (LUNs) for the database. See
Optimizing Performance for more information about the configuration of
directories for the database. In addition, each active log and archive log
should have its own container or LUN.

Ensure that you see the capacity planning section for more details about
disk space.

24 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 7. Hardware requirements (continued)

Type of
hardware Hardware requirements
Memory The following minimum values for memory:
v 12 GB.
v 16 GB if you are using data deduplication.
v At least 32 GB for heavily used servers. Using 32 GB or more of memory
enhances performance of the Tivoli Storage Manager server database
inventory.
v If you plan to run multiple instances, each instance requires the memory
that is listed for one server. Multiply the memory for one server by the
number of instances that are planned for the system.
v Node replication processing requires additional memory. Use a minimum
of 32 GB of memory for node replication without data deduplication.
Node replication with data deduplication requires a minimum of 64 GB
of memory.
v When you create the active log, you need at least 64 GB of memory to
run replication. If replication and deduplication are both being used,
create an active log of 128 GB in size.
Devices A DVD device that is available for the installation process, if you are
installing from DVD media.

Software requirements

The following table describes the minimum software requirements.

System resources such as semaphores and kernel values might require special
configuration and tuning. See the information in Appendix D, “HP-UX system
resource requirements,” on page 553.
Table 8. Software requirements
Type of
software Minimum software requirements
Operating The HP Itanium system must have operating system 11i v3 (11.31) with
system the most current maintenance levels installed.

11i v3 with:
v PHCO_38658 - libc cumulative patch
v PHSS_37202
v PHKL_41481
v PHKL_42035
v PHKL_42335
v PHKL_41588
v PHSS_41496

The latest available service patches for the operating system must be
applied. Older levels without patches do not work with the device
drivers that Tivoli Storage Manager uses.
Communication A communication method that is installed and activated (shared memory
protocol is the default).

Chapter 2. Planning the upgrade 25

Upgrading the server from V5 to V7.1

Table 8. Software requirements (continued)

Type of
software Minimum software requirements
Device drivers The Tivoli Storage Manager passthru device driver is used for non-IBM
devices. It uses the SCSI passthru interface to communicate with tape
drives and tape libraries. The stape device driver is required for tape
drives. The schgr device driver is required for tape libraries. The Tivoli
Storage Manager device driver package contains device driver tools and
ACSLS daemons.

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

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

Server requirements on Linux systems

Linux

Check that your Linux system meets the requirements.

Some platforms that were supported for earlier versions of the server are not
supported for V7.1:
v Linux running on an Itanium system (IA64)
v Linux running on a 32-bit x86 system
If the server that you want to upgrade is running on one of these platforms, you
cannot upgrade your server to V7.1 on the same platform. You must install your
V7.1 server on an x86_64 system that is running the Linux operating system, and
then use the network or media method to upgrade your V5 server to that system.

Server requirements for Linux on x86_64 systems: Linux

The Tivoli Storage Manager server has minimum requirements for hardware and
software.

Hardware requirements

The following table describes the minimum hardware requirements.

For information about estimating the total disk space that is required, see
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39.

If you have an IBM 3592 or Ultrium tape library or drive, install the most current
device driver before you install Tivoli Storage Manager. You can locate the device
drivers at http://www.ibm.com/support/fixcentral/.

26 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 9. Hardware requirements

Type of
hardware Hardware requirements
Hardware An AMD64 or Intel EMT-64 processor
Disk space The following minimum values for disk space:
v 512 MB for the /var directory
v 4 GB for the installation directory
v 2 GB for the /tmp directory
v 300 MB for the /usr directory
v 2 GB in the home directory
Tip: Expect to use more space for problem determination.
v 2 GB for the shared resources area

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

For optimal performance and to facilitate I/O, specify at least two equally
sized containers or Logical Unit Numbers (LUNs) for the database. See
Optimizing Performance for more information about the configuration of
directories for the database. In addition, each active log and archive log
should have its own container or LUN.

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

Chapter 2. Planning the upgrade 27

Upgrading the server from V5 to V7.1

Software requirements

The following table describes the minimum software requirements.

Table 10. Software requirements
Type of
software Minimum software requirements
Operating The Tivoli Storage Manager server on Linux X86_64 requires one of the
system following operating systems:
v Red Hat Enterprise Linux 6
v SUSE Linux Enterprise Server 11, Service Pack 2
Libraries GNU C libraries, Version 2.3.3-98.38 or later that is installed on the Tivoli
Storage Manager system.

For SUSE Linux Enterprise Servers:

v libaio
v libstdc++.so.5 at version 3.3 or later (32 and 64 bit packages are
required)
v libstdc++.so.6 at version 4.3 or later (32 and 64 bit packages are
required)
For Red Hat Enterprise Linux Servers:
v libaio
v libstdc++.so.6 (32 and 64 bit packages are required)

To determine if SELinux is installed and in enforcing mode, perform one

of the following tasks:
v Check the /etc/sysconfig/selinux file.
v Run the sestatus operating system command.
v Check the /var/log/messages file for SELinux notices.
To disable SELinux, complete one of the following tasks:
v Set permissive mode by issuing the setenforce 0 command as a
superuser.
v Modify the /etc/sysconfig/selinux file and reboot the machine.
Communication v TCP/IP Version 4 or Version 6, which is standard with Linux
protocol
v Shared memory protocol (with Tivoli Storage Manager Version 7.1
Linux X86_64 client)
Processing Asynchronous I/O must be enabled. On Linux kernels at 2.6 or later,
install the libaio library to enable Asynchronous I/O.
Device drivers The Tivoli Storage Manager passthru device driver is used for non- IBM
devices. It uses the SCSI passthru interface to communicate with tape
devices and tape libraries. The Linux SCSI Generic (sg) device driver is
required for tape drives and tape libraries. The Tivoli Storage Manager
device driver package contains device driver tools and ACSLS daemons.

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

Configure the device drivers before you use the Tivoli Storage Manager
server with tape devices.
Other software Korn Shell (ksh)

28 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Server requirements for Linux on System z systems: Linux

The Tivoli Storage Manager server has minimum requirements for hardware and
software.

Hardware requirements

The following table describes the minimum hardware requirements.

For information about estimating the total disk space that is required, see
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39.

If you have an IBM 3592 or Ultrium tape library or drive, install the most current
device driver before you install Tivoli Storage Manager. You can locate the device
drivers at http://www.ibm.com/support/fixcentral/.
Table 11. Hardware requirements
Type of
hardware Hardware requirements
Hardware An IBM zSeries, IBM System z9®, IBM System z10®, or IBM zEnterprise®
System (z114 and z196) 64-bit native logical partition (LPAR) or z/VM®
guest.
Disk space The following minimum values for disk space:
v 512 MB for the /var directory
v 3 GB for the installation directory
v 2 GB for the /tmp directory
v 300 MB for the /usr directory
v 2 GB in the home directory
Tip: Expect to use more space for problem determination.
v 2 GB for the shared resources area

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

For optimal performance and to facilitate I/O, specify at least two equally
sized containers or Logical Unit Numbers (LUNs) for the database. See
Optimizing Performance for more information about the configuration of
directories for the database. In addition, each active log and archive log
should have its own container or LUN.

Ensure that you see the capacity planning section for more details about
disk space.

Chapter 2. Planning the upgrade 29

Upgrading the server from V5 to V7.1

Table 11. Hardware requirements (continued)

Type of
hardware Hardware requirements
Memory The following minimum values for memory:
v 12 GB.
v 16 GB if you are using data deduplication.
v At least 32 GB for heavily used servers. Using 32 GB or more of memory
enhances performance of the Tivoli Storage Manager server database
inventory.
v If you plan to run multiple instances, each instance requires the memory
listed for one server. Multiply the memory for one server by the number
of instances planned for the system.
v Node replication processing requires additional memory. Use a minimum
of 32 GB of memory for node replication without data deduplication.
Node replication with data deduplication requires a minimum of 64 GB
of memory.
v When you create the active log, you need at least 64 GB of memory to
run replication. If replication and deduplication are both being used,
create an active log of 128 GB in size.

Software requirements

The following table describes the minimum software requirements.

Table 12. Software requirements
Type of
software Minimum software requirements
Operating The Tivoli Storage Manager server on Linux on System z (s390x 64-bit
system architecture) requires one of the following operating systems:
v Red Hat Enterprise Linux 6
v SUSE Linux Enterprise Server 11, Service Pack 2
Libraries GNU C library, Version 2.4-31.43.6 is installed on the Tivoli Storage
Manager system.

For SUSE Linux Enterprise Servers:

v libaio
v libstdc++.so.5 at version 3.3 or later (32 and 64 bit packages are
required)
v libstdc++.so.6 at version 4.3 or later (32 and 64 bit packages are
required)
For Red Hat Enterprise Linux Servers:
v libaio
v libstdc++.so.6 (32 and 64 bit packages are required)
Communication v TCP/IP Version 4 or Version 6, which is standard with Linux
protocol
v Shared memory protocol (with Tivoli Storage Manager Version 7.1
Linux on System z client)
Processing Asynchronous I/O must be enabled. On Linux kernels at 2.6 or later,
install the libaio library to enable Asynchronous I/O.
Other software Korn Shell (ksh)

30 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Server requirements on Solaris systems

Solaris

Check that your Solaris system meets the requirements.

Hardware requirements

The following table describes the minimum hardware requirements.

For information about estimating the total disk space that is required, see
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39.
Table 13. Hardware requirements
Type of
hardware Hardware requirements
Hardware One of the following processors is required:
v Ultra SPARC-based processors (sun4u architecture)
v Ultra SPARC-based processors (sun4v architecture)
Disk space The following list is the minimum values for disk space for Ultra
SPARC-based processors (sun4u and sun4v architecture) for the respective
directories and logs:
v 512 MB for the /var directory
v 4 GB for the installation directory
v 2 GB for the /tmp directory
v 300 MB for the /usr directory
v 2 GB in the home directory
Tip: Expect to use more space for problem determination.
v 2 GB for the shared resources area

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

For optimal performance and to facilitate I/O, specify at least two equally
sized containers or Logical Unit Numbers (LUNs) for the database. See
Optimizing Performance for more information about the configuration of
directories for the database. In addition, each active log and archive log
should have its own container or LUN.

Ensure that you see the capacity planning section for more details about
disk space.

Chapter 2. Planning the upgrade 31

Upgrading the server from V5 to V7.1

Table 13. Hardware requirements (continued)

Type of
hardware Hardware requirements
Memory The following minimum values for memory:
v 12 GB.
v 16 GB if you are using data deduplication.
v At least 32 GB for heavily used servers. Using 32 GB or more of memory
enhances performance of the Tivoli Storage Manager server database
inventory.
v If you plan to run multiple instances, each instance requires the memory
listed for one server. Multiply the memory for one server by the number
of instances planned for the system.
v Node replication processing requires additional memory. Use a minimum
of 32 GB of memory for node replication without data deduplication.
Node replication with data deduplication requires a minimum of 64 GB
of memory.
v When you create the active log, you need at least 64 GB of memory to
run replication. If replication and deduplication are both being used,
create an active log of 128 GB in size.
Tip: Ensure that there is at least twice as much swap space allocated as
there is physical memory on the system.

Software requirements

The following table describes the minimum software requirements.

Table 14. Software requirements
Type of
software Minimum software requirements
Operating Oracle Solaris 10 Update 10 on SPARC, running in 64-bit kernel system
system with sun4u or sun4v architecture
v Patch 118822-25
v If raw devices are used, patch 125100-07
Communication TCP/IP
protocol
Device drivers The Tivoli Storage Manager device driver required for non-IBM drives
and tape libraries. The Tivoli Storage Manager device driver package
contains device driver tools and ACSLS daemons.

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

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

32 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Server requirements on Microsoft Windows systems

Windows

Check that your Microsoft Windows system meets the requirements.

You cannot run a V7.1 server on an Itanium system (IA64) that is running the
Windows operating system. If the server that you want to upgrade is running on
this platform, you cannot upgrade your server to V7.1 on the same platform. You
must install your V7.1 server on an x86_64 system that is running the Windows
operating system, and then use the network or media method to upgrade your V5
server to that system.

Hardware requirements

The following table describes the minimum hardware requirements.

For information about estimating the total disk space that is required, see
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39.
Table 15. Hardware requirements
Type of
hardware Hardware requirements
Hardware An AMD64 or Intel EMT-64 processor
Disk Space The following minimum values for disk space:
v At least 5 GB of free disk storage (for a typical installation)
v 60 MB in the temporary directory space
v 2 GB partition size in the C:\ drive
v 300 MB in the instance directory
v 2 GB in the shared resources area

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

For optimal performance and to facilitate I/O, specify at least two equally
sized containers or Logical Unit Numbers (LUNs) for the database. See
Optimizing Performance for more information about the configuration of
directories for the database. In addition, each active log and archive log
should have its own container or LUN.

Ensure that you see the capacity planning section for more details about
disk space.

Chapter 2. Planning the upgrade 33

Upgrading the server from V5 to V7.1

Table 15. Hardware requirements (continued)

Type of
hardware Hardware requirements
Memory The following minimum values for memory:
v 12 GB.
v 16 GB if you are using data deduplication.
v At least 32 GB for heavily used servers. Using 32 GB or more of memory
enhances performance of the Tivoli Storage Manager server database
inventory.
v If you plan to run multiple instances, each instance requires the memory
listed for one server. Multiply the memory for one server by the number
of instances planned for the system.
v Node replication processing requires additional memory. Use a minimum
of 32 GB of memory for node replication without data deduplication.
Node replication with data deduplication requires a minimum of 64 GB
of memory.
v When you create the active log, you need at least 64 GB of memory to
run replication. If replication and deduplication are both being used,
create an active log of 128 GB in size.

Software requirements

The following table describes the minimum software requirements.

Table 16. Software requirements
Type of
software Minimum software requirements
Operating One of the following operating systems:
system v Microsoft Windows Server 2008 R2: Standard, Enterprise, or Datacenter
Edition (64-bit)
v Microsoft Windows Server 2012 (64-bit)
Communication At least one of the following communication protocols (installed by
protocol default with the current Windows operating systems):
v Named Pipes
v TCP/IP Version 4 or Version 6
Device drivers The Tivoli Storage Manager passthru device driver that is required for
non-IBM drives and tape libraries. The Windows native device driver is
recommended for tape drives and tape libraries. Otherwise, the Tivoli
Storage Manager kernel device driver can be used.

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

Configure the device drivers before you use the Tivoli Storage Manager
server with tape devices.

34 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 16. Software requirements (continued)

Type of
software Minimum software requirements
Other software Windows 2012 requires that .NET Framework 3.5 is installed and
enabled.

The following User Account Control policies must be disabled:

v User Account Control: Admin Approval Mode for the Built-in
Administrator account
v User Account Control: Run all administrators in Admin Approval
Mode

Compatibility of the Tivoli Storage Manager server with other DB2

products on the system
AIX HPUX Linux Solaris

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

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

Chapter 2. Planning the upgrade 35

Upgrading the server from V5 to V7.1

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

To segregate resources and provide more

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

Determining the appropriate level for a V5 server before an upgrade

When you prepare a system for an upgrade, you must verify the level of the V5
server and upgrade the server if required. By reviewing the guidelines and
upgrading the V5 server to an appropriate level, you can optimize the subsequent
upgrade to V7.

About this task

The guidelines apply to server upgrades from V5 to V7 on the same operating

system. The guidelines also apply if you are migrating a V5 server to V7 on a
different operating system.

Procedure

You can upgrade the server from V5.3.6 or later to any level of V7. However, to
determine the most appropriate level for a V5 server, review the following
guidelines:
v The preferred method is to upgrade the server to the latest level of V5. In this
way, you can use the latest upgrade utilities to extract information from a source
server database and to insert the information into a target server database.
v For the selected server level, ensure that the latest interim fix is installed. In this
way, you can reduce the risk of upgrade issues.
v Because upgrade utilities are provided in a separate package, you can install the
latest version of the utilities without upgrading the server. If you are installing
only the upgrade utilities without upgrading the server, the following
restrictions apply:

36 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

– The upgrade utilities must be at the same level as the V5 server or at a later
level.
– To avoid a potential issue with data extraction, the upgrade utilities must be
at V5.5.4 or later.
– If you plan to extract the server database to media, the preferred method is to
upgrade the source server to V5.5.6 or later.
To find the latest level of the V5 server and the latest interim fixes, go to the FTP
downloads site at ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/.

Planning space for the upgrade process and the upgraded server
Plan for the space requirements for the upgrade process, and for the server
database and recovery log for the upgraded server. Consider the disk storage
currently in use for the server, and whether changes in hardware can be timed to
coincide with the upgrade of the server.

Space requirements for the V5 server system

Space is required for storing the backup of the server database, which is an
important step in preparing for the upgrade process. If you are using the media
method for moving the database, you need space for storing the extracted data.

The backup of the server database requires as much space as is used by your V5
database. Store the backup on the form of sequential media that is convenient for
you, either tape or disk.

Additional space requirements depend on the method that you choose for moving
the data from the V5 database:
Media method
You need media to store the data that will be extracted from the V5
database. The media can be tape, or disk space that is defined as a
sequential-access disk device class. The space required for the extracted
data is the same as the used space in your database. If your database is
safely backed up, and you are certain that you no longer need to run the
V5 server, after you extract the data you can optionally release the space
used by the V5 database and recovery log.
Network method
You must have the working copy of the V5 database and recovery log on
the V5 system. If you are working with a copy of the database that was
created for testing the upgrade process, you need enough space to hold the
total allocated size of the database; you can use the minimum size for a V5
recovery log.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39

Chapter 2. Planning the upgrade 37

Upgrading the server from V5 to V7.1

Space requirements for the V7 server system

Before beginning the upgrade process, plan for the space that is required for the
database and recovery log. Where you locate the database and recovery log
directories is very important to the operation of your server.

You need unique, empty directories for the following items for the upgraded
server:
v The database
v The recovery log
– Active log
– Archive log
– Optional: Active log mirror
– Optional: Secondary archive log (archive failover log)
v The instance directory for the server, which is a directory that will contain files
specifically for this server instance (the server options file and other
server-specific files)

Locate the database and the active log on fast, reliable storage, with high
availability characteristics. Ideally, use multiple directories for database space and
locate them across as many physical devices or logical unit numbers (LUNs) as
there are directories.

Place the database and recovery log directories on separate physical volumes or
file systems.

To maintain database integrity, ensure that the storage hardware can withstand
failures such as power outages and controller failure. You can improve database
performance by using hardware that provides a fast, nonvolatile write cache for
both the database and logs.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39
Related information:
Tivoli Storage Manager support site

Database space requirements

The amount of database space that is required depends on the size of the original
V5 database, and on how much data the server will manage.

The amount of storage space for the database is managed automatically. The
database space can be spread across up to 128 directories. After you specify the
directories for the database, the server uses the disk space available to those
directories as required.

Plan for 33 - 50% more than the space that is used by the V5 database. (Do not
include allocated but unused space for the V5 database in the estimate.) Some
databases can grow temporarily during the upgrade process; consider providing
up to 80% more than the space that is used by the V5 database.

Estimate the amount of space that the database will require by completing the
following steps:

38 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

1. Use the QUERY DB FORMAT=DETAILED command to determine the number of used

database pages in your V5 database.
2. Multiply the number of used database pages by 4096 to get the number of used
bytes.
3. Add 33 - 50% to the used bytes to estimate the database space requirements.
Consider testing the upgrade of the database to get a more accurate estimate. Not
all databases will grow as much as the suggested 33 - 50% increase in space.

When the server is operating normally, after the upgrade process, some operations
might cause occasional large, temporary increases in the amount of space used by
the database. Continue to monitor the usage of database space to determine
whether the server needs more database space.

For the best efficiency in database operations, anticipate future growth when you
set up space for the database. If you underestimate the amount of space that is
needed for the database and must add directories later, the database manager
might need to perform more database reorganization, which can consume
resources on the system. Estimate the requirements for database growth based on
the predicted number of additional objects to be stored in server storage. For more
information about estimating database space requirements, see the Administrator's
Guide.

Restriction: You cannot use raw logical volumes for the database. If you want to
reuse space on the disk where raw logical volumes were located for an earlier
version of the server, you must create file systems on the disk first.

For the latest information and recommendations, see the Tivoli Storage Manager
support website at http://www.ibm.com/support/entry/portal/Overview/
Software/Tivoli/Tivoli_Storage_Manager.

Recovery log space requirements

The amount of space that you require for the recovery log depends on various
factors, including, for example, the amount of client activity with the server.

For details, see the section that describes recovery log space requirements in the
Installation Guide.

For the latest information and updates, go to the Tivoli Storage Manager support
site: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager

Estimating total space requirements for the upgrade process

and upgraded server
In addition to the space required for the upgraded server itself, some additional
disk space is needed for the upgrade process. For example, if you are upgrading
the server on the same system, you need enough space for two copies of the
database during the upgrade process.

About this task

The space requirements for the upgraded, V7.1 server depend on the size of the V5
database and other factors. For details, see “Database space requirements” on page
38 and “Recovery log space requirements.”

Chapter 2. Planning the upgrade 39

Upgrading the server from V5 to V7.1

The space requirements for the upgrade process depend on how you move the
data from the V5 database to the new database. You can move the data to the new
database by using the media method or the network method, with the following
requirements:
v The media method requires sequential media. The sequential media can be tape
or sequential disk device class (FILE device type).
v The network method requires a network connection between systems, if you are
upgrading on a new system.

Table 18 shows basic tips for estimating each item, for each of the main scenarios.
For details about sizing the V7.1 database and recovery log, see “Space
requirements for the V7 server system” on page 38.
Table 18. Tips for estimating space requirements. Select the scenario. Then, read down the column.
Item that Type of Scenario 1: Scenario 2: Scenario 3: Scenario 4:
requires space space v Same system as v Same system as v New system v New system
V5 server V5 server v Media method v Network method
v Media method v Network method
V5 database: Disk Space that is Space that is 0 0
space allocated allocated for the V5 allocated for the V5
for the original database database
database
V5 database: final Sequential Space that is used Space that is used Space that is used Space that is used
backup copy media by the V5 database by the V5 database by the V5 database by the V5 database
(based on % (based on % (based on % (based on %
utilization) utilization) utilization) utilization)
V5 database: Sequential Space that is used 0 Space that is used 0
extracted data media by the V5 database by the V5 database
(based on % (based on %
utilization) utilization)
V5 recovery log Disk The amount of The amount of 0 0
space that is space that is
allocated for the V5 allocated for the V5
recovery log recovery log
V7.1 database: Disk Space that is used Space that is used Space that is used Space that is used
estimated size by the V5 database by the V5 database by the V5 database by the V5 database
plus 33 - 50% more plus 33 - 50% more plus 33 - 50% more plus 33 - 50% more
V7.1 database: Sequential Same as estimated Same as estimated Same as estimated Same as estimated
first backup media database size database size database size database size
V7.1 active log Disk 16 GB during the 16 GB during the 16 GB during the 16 GB during the
directory upgrade process. A upgrade process. A upgrade process. A upgrade process. A
higher value might higher value might higher value might higher value might
be needed for be needed for be needed for be needed for
normal use. normal use. normal use. normal use.
V7.1 active log Disk If used, same size If used, same size If used, same size If used, same size
mirror (optional) as active log as active log as active log as active log
V7.1 archive log Disk Estimate based on Estimate based on Estimate based on Estimate based on
directory client activity and client activity and client activity and client activity and
database backup database backup database backup database backup
frequency frequency frequency frequency

Table 19 on page 41 shows a sample completed worksheet for a 100 GB, V5

database that has 80% space utilization, with the assumption that the database
increases by 33% - 50% when upgraded.

40 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 19. Sample space estimates for a 100 GB V5 database

Item that Type of Scenario 1: Scenario 2: Scenario 3: Scenario 4:
requires space space v Same system as v Same system as v New system v New system
V5 server V5 server v Media method v Network method
v Media method v Network method
V5 database: Disk 100 GB 100 GB 0 0
space allocated
for the original
database
V5 database: final Sequential 80 GB 80 GB 80 GB 80 GB
backup copy media
V5 database: Sequential 80 GB 0 80 GB 0
extracted data media
V5 recovery log Disk 12 12 0 0
V7.1 database: Disk 106 - 120 GB 106 - 120 GB 106 - 120 GB 106 - 120 GB
estimated size
V7.1 database: Sequential 106 - 120 GB 106 - 120 GB 106 - 120 GB 106 - 120 GB
first backup media
V7.1 active log Disk 8 GB 8 GB 8 GB 8 GB
directory
V7.1 active log Disk (8 GB) (8 GB) (8 GB) (8 GB)
mirror (optional)
V7.1 archive log Disk 80 GB 80 GB 80 GB 80 GB
directory
Total disk space Disk 307 - 320 GB 307 - 320 GB 195 - 208 GB 195 - 208 GB
required during
the upgrade (315 - 328 GB) (315 - 328 GB) (203 - 216 GB) (203 - 216 GB)
process
Total sequential Sequential 267 - 280 GB 187 - 200 GB 267 - 280 GB 187 - 200 GB
media required media
during the
upgrade process
Total disk space Disk 195 - 208 GB 195 - 208 GB 195 - 208 GB 195 - 208 GB
for the V7.1
server after (203 - 216 GB) (203 - 216 GB) (203 - 216 GB) (203 - 216 GB)
upgrade and
cleanup

Related concepts:
“Space requirements for the V5 server system” on page 37
“Space requirements for the V7 server system” on page 38
Related tasks:
Chapter 3, “Upgrade scenarios overview,” on page 73

Chapter 2. Planning the upgrade 41

Upgrading the server from V5 to V7.1

Worksheet for planning space for the V7.1 server

You can use the worksheet to help you plan the amount and location of storage
needed for the V7.1 server.

Item Space required Location

The instance directory for the
server, which is a directory that
contains files specifically for this
server instance (the server
options file and other
server-specific files)
The database
Active log
Archive log
Optional: Log mirror for the
active log
Optional: Secondary archive log
(failover location for archive log)

Estimating the upgrade time

The V5 server is not available for use during upgrade operations. To help plan for
the amount of time that the server will be unavailable, estimate the upgrade time.
The time that is required to complete the upgrade of a V5 server depends on
several factors.

About this task

The following factors can affect the upgrade time:

v The size of the database that is being upgraded.
v The number and speed of system processors.
v The configuration of storage devices. If new hardware is being introduced, time
is required to define the new devices to the server, test the configuration, and
adjust storage pools.
v The method for moving the data from the V5 database to the V7 database
(media or network). The network method for the data movement overlaps the
extraction time with the insertion time. Using the network method might help
reduce the total time that is required for the upgrade because of the overlap.
v The type of workload that the server handles. A workload that consists of large
numbers of small files, or files with long file names, can cause a relatively longer
upgrade time.
v The amount of fragmentation in the V5 database. A higher level of
fragmentation results in a more efficient database insertion process. The reason
is that fragmented data on the V5 system can use multiple threads and
processors on the V7 system.

Procedure

When you estimate the time it might take to migrate the system, consider the
results that were obtained in labs. For example, in benchmark environments in
IBM labs, upgrade operations achieved 5 - 10 GB per hour by using the network
method. This rate is based on the amount of space that is used by the V5 database,

42 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

not the allocated space for the database. Your environment might produce different
results. Results are dependent on system configuration. If you use the media
method, the rate is decreased.
Estimate the time that is required to migrate your system based on the amount of
data in the server database.

Results

Your estimate might be higher than the actual time that is required. Because of the
way that databases are structured, the amount of data that the extraction utility
extracts might be much less than the total amount of space that is used by the
database.

What to do next

Test upgrade operations for Tivoli Storage Manager servers that are used by
essential systems.

Example: Estimating the upgrade time based on the database

size
You can roughly estimate the time that is required for the upgrade based on the
amount of data in the V5 database. To this estimate, add the time that is required
for additional tasks, such as configuring storage devices.

Procedure
1. Issue a command to obtain details about the V5 database.
v If the V5 server is running, issue the command:
query db format=detailed
v If the V5 server is not running and you have installed the upgrade utilities,
use the upgrade utility:
dsmupgrd querydb
An example of results:
Available Space (MB): 16,384
Assigned Capacity (MB): 16,364
Maximum Extension (MB): 20
Maximum Reduction (MB): 772
Page Size (bytes): 4,096
Total Usable Pages: 4,189,184
Used Pages: 3,214,880
Pct Util: 76.7
Max. Pct Util: 76.7
Physical Volumes: 8
Buffer Pool Pages: 8,192
Total Buffer Requests: 4,510
Cache Hit Pct.: 94.15
Cache Wait Pct.: 0.00
Backup in Progress?: No
Type of Backup In Progress:
Incrementals Since Last Full: 0
Changed Since Last Backup (MB): 12,558.12
Percentage Changed: 100.00
Last Complete Backup Date/Time: 07/02/2008 02:24:16 AM
Estimate of Recoverable Space (MB):
Last Estimate of Recoverable Space (MB):
Pages Available for Temp Objects: 197,632
Pages Allocated for Temp Objects: 0
Pages Used for Temp Objects: 0

Chapter 2. Planning the upgrade 43

Upgrading the server from V5 to V7.1

2. Use the results of the query command to calculate the amount of data in the
database. Multiply the number of used pages by the page size.
Using the results in the example, you can calculate the amount of data in this
database:
3,214,880 used pages × 4096 bytes/page = 13,168,148,480 bytes, or 12.26 GB
3. Estimate the time that is required for the upgrade operation by dividing the
amount of data by the expected rate.
For example, by using rates of 5 GB/hour and 10 GB/hour:
12.26 GB ÷ 5 GB/hour = 2.5 hours
12.26 GB ÷ 10 GB/hour = 1.2 hours

Performance tips for the V5 database extraction process

Review the performance tips for the V5 database extraction process so that you can
minimize the time that is required for the upgrade. In this way, you can reduce the
time that the Tivoli Storage Manager server is unavailable.

The speed of the extraction process is typically limited by the speed of I/O to the
destination for the extracted data. The length of time that the process runs also
depends on the size of the database. The time will be approximately as long as the
time required for a full backup of the database.

Do not reorganize the Tivoli Storage Manager V5 database before the upgrade. The
extraction process can achieve faster throughput when the source database does
not contain long sequences of pages that are allocated to a single database table.
This tip applies to both the media method and the network method.

The following performance tips depend on the method that you choose for moving
the data from the V5 database.
Media method
If you are using the media method, consider the following tips:
v If you are extracting the data to tape, use a high-speed tape device. For
example, select a device with a transfer rate of at least 1000 MB per
second.
v If you are extracting the data to disk, use a disk device or LUN that is
different from the device that is used for the V5 database and recovery
log.
v If both the V5 database and the destination for the extracted data are on
a virtualization device (high-end storage controller, or a SAN
virtualization device), ensure that the two virtual LUNs are not on the
same physical disk drive. Ensure that the space for the V5 database and
the destination for the extracted data are on different physical disk
drives within the virtualization device.
v If it is not possible to provide different LUNs for the V5 database and
the extraction destination, the extraction process will take more time.
The slower speed of extraction might be acceptable, depending on the
size of the database and your requirements for the upgrade.
Network method
If you are using the network method, consider the following tips:
v Use a high-speed link if you are extracting the data to a different system.
If you are upgrading a database that is larger than 2 - 3 GB, use at least
a 1-gigabit (Gb) Ethernet network.

44 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

v If you are extracting the database on the same system, no external

network connections are required.

Performance tips for inserting data into the V7.1 database

The process for inserting the V5 extracted data into the V7.1 database is the
longest-running part of an upgrade process. The performance of the data insertion
process depends on the system configuration.

On a system that meets only the minimum requirements, the insertion process will
run, but performance might be slow. For better performance, set up the system as
described in the following tips:
Processors
The insertion process is designed to use multiple processors or cores. The
insertion process typically performs better on a system with a relatively
small number of fast processors. If the system has many slow processors,
you might experience reduced performance levels.
Disk storage
The insertion process is designed to use high-bandwidth disk storage
subsystems. The speed of the process is dependent on the disk storage that
is used.
For best performance, use multiple LUNs that map to multiple
independent disks, or that map to redundant arrays of independent disks
(RAIDs) with a large stripe size (for example, 128 KB). Use a different file
system on each LUN.
The following table shows an example of good usage of LUNs.
Table 20. Example of LUN use
LUN Usage
1 Active log
2 Archive log
3, 4, 5 Database directories
6 Extracted V5 database, which is required only if the media method
is used to extract the V5 database to a sequential disk device class

If the disk storage is supplied by a virtualization device (high-end storage

controller, or a SAN virtualization device), ensure that none of the virtual
LUNs are on the same physical disk drive. Ensure that the directories in
use are on different physical disk drives within the virtualization device.

Planning for upgrading multiple servers and components

If your environment includes multiple servers and storage agents, evaluate the
compatibility of the versions being run with an upgraded V7.1 server. Plan to
upgrade one server first in a test environment. Then stage the upgrade of
additional servers and storage agents.

Chapter 2. Planning the upgrade 45

Upgrading the server from V5 to V7.1

Components that are available for installation

In addition to the server, you can choose to install language packages, devices, the
Operations Center, and other components.

Compatibility with servers and components that are running

at earlier versions
Details about the levels of server, client, storage agent, library manager server,
library client servers, and configuration manager servers that can work together
are available from the product support site.

The product support site is located at: http://www.ibm.com/support/entry/

portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

To use the new functions that are available in Tivoli Storage Manager V7.1, install
the latest version of the IBM Tivoli Storage Manager Operations Center.

Planning for upgrading multiple servers on a single system

How you upgrade multiple servers that run on a single system depends on
whether the servers are to remain on that system, or be moved to a new system.
After you install the V7.1 server on a system, you can no longer run any V5
servers on that system.

About this task

If the upgraded servers are to remain on the same system, all server instances
must be upgraded at the same time. After the point in the upgrade process when
you install the V7.1 server program on the system, a V5 server cannot be started
on that system. Each V5 server must be upgraded separately before you can start
that server again.

If the upgraded servers are to be moved to a new system as part of the upgrade
process, you can upgrade the servers independently of one another.

You can use the upgrade wizard, or manually use the upgrade utilities to upgrade
the servers:

Procedure
v If you use the upgrade wizard, run the wizard once for each server instance.
You can upgrade multiple servers at the same time. Each time that you start the
upgrade wizard, you work with a single server, but you can start the wizard in
multiple windows at the same time.
v If you use the upgrade utilities manually from a command line, repeat the
procedure for upgrading each server instance.

What to do next

You can begin running one upgraded server instance while other server instances
are still being upgraded.
Related concepts:
“Comparison of upgrading on an existing system and a new system” on page 13

46 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Planning for upgrading library managers and library clients

To work with a Version 7.1 library manager, servers that are library clients must be
at Version 5.4 or later.

About this task

If library client servers are at V5.3 or earlier, you must upgrade the library client
servers to at least V5.4 before upgrading the library manager server to V7.1. If
library client servers are at V5.4 or later, you can upgrade the server that is the
library manager to V7.1 first, and then upgrade the library client servers later.

If you are moving a library manager or library clients to new systems for the
upgrade to V7.1, consider moving the servers to the new systems before upgrading
the servers. By moving the servers first, you can reestablish connectivity to all
servers and devices before the upgrade. Then upgrade the library manager,
followed by upgrading the library clients.

For the most recent information about supported levels of library clients, see the
following website: http://www.ibm.com/support/docview.wss?uid=swg21302789

Planning for upgrading clients

To connect to a V7.1 server, client nodes must be running a version 5.5 or later
client program.

Planning for upgrading storage agents

To connect to a V7.1 server, storage agents must be at V7.1.

Procedure

If you have storage agents at earlier versions, upgrade them to V7.1 before you
upgrade the server to V7.1. Verify that LAN-free data movement works as
expected before you upgrade the server.

What to do next

For the most recent information about supported levels of storage agents, go to the
following website: http://www.ibm.com/support/docview.wss?uid=swg21302789

Testing the upgrade process for a server

Test the upgrade to ensure a smooth upgrade process. The larger and more
complex your environment, the more important testing the upgrade is. Testing can
help to plan for the amount of time that the server is unavailable because of the
upgrade.

About this task

The original server and the V7.1 server cannot both be installed on a system at the
same time. To evaluate the V7.1 server, you can install the program on a new
system.

To test with a copy of production data, or to test the upgrade process, you can use
the upgrade utilities to create a test server. Follow the normal upgrade procedure,
but consider these tips:

Chapter 2. Planning the upgrade 47

Upgrading the server from V5 to V7.1

Minimizing impact to your production server

To avoid affecting your original production server, you must install the
V7.1 server on a different system. Different versions of the server cannot be
run on a system at the same time.
The DSMUPGRD utility must be installed on the system that has your original
server, or a copy of your original server. The utility package installs by
default in a different location than a normal server, so it can be installed
without affecting your production server.

Important: When you run the DSMUPGRD PREPAREDB utility, the utility
upgrades the database version to a V5.5 fix pack level. If you do not want
the database on your production server to be upgraded to the V5.5 fix
pack level, back up the database and use the backup on another system to
test the upgrade.
You can extract the production database for the test by using either media
or the network. The advantage of extracting the database to media is that
you can repeatedly load the test database without stopping your
production server each time.
Detecting problems in the database
A PREVIEW parameter is available for the DSMSERV INSERTDB utility. When
you use the PREVIEW=YES parameter, the operation includes all the steps
of the process, except for the actual insertion of data into the new
database.
When you preview the insertion operation, you can quickly verify that the
source database is readable. You can also identify any data constraint
violations before you run the actual upgrade process for your server.
Investigate any data constraint violations that are discovered during the
preview so that you can avoid delays when you run the actual upgrade
process.
Protecting storage and stored data
Ensure that the storage devices for your production server are not available
to the test server. If the test server can detect the devices that your
production server uses, it might start operations such as issuing resets on
tape drives or unloading tapes.
For example, if your tape drives are connected in a storage area network
(SAN), you might need to change the zones in your SAN to prevent the
test server from detecting the devices.

For testing, you can use one of the following methods to use a backup copy of the
database. The methods are given in outline form. See the detailed procedures for
instructions for each step.
Related tasks:
Chapter 9, “General procedures for upgrading a server to V7.1,” on page 277

48 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Testing by extracting data from a separate copy of the server

Either the media method or the network method can be used to move the
database.

Procedure
1. Prepare a test system. This system is a different system than the production
server, where you must install a separate copy of the V5.3, V5.4, or V5.5 server
(the same version as your production server).
2. Back up the database of the production server.
3. Restore the database backup on the test system. Start the server to verify that
the restore operation worked.

Tip: If you are upgrading the server by using media, ensure that the device
class is valid on the test system. For example, if you are using a FILE device
class for the extraction step, ensure that the path for the device class is valid on
the test system. The path that is in the server database for the device class must
be correct. If necessary, start the server and update the path.

If you are using a tape device class for the extraction step, ensure that the
device names for the library and drives are correct.
4. From this point, you can use the detailed procedures in one of the following
sections to complete your test:
Chapter 4, “Scenario 1: Same system, media method,” on page 91
Chapter 5, “Scenario 2: Same system, network method,” on page 135

Testing by extracting data from the production server

This example process uses the media method to move the database to the test
system.

About this task

You follow the steps in the procedures for Chapter 6, “Scenario 3: New system,
media method,” on page 177, with just a few changes.

With this process, the production server is unavailable for at least the amount of
time that is required to prepare and extract the database. The time is
approximately as much as the time required for a full backup of the database.

Procedure
1. Prepare for the test by backing up the database of the production server.
Consider making a second copy of the database backup. For details, see
“Scenario 3: Preparing for the upgrade” on page 177.
2. Install the DSMUPGRD utilities on the same system as the production server. For
details, see “Installing the upgrade utilities on the original server” on page 287.
3. Prepare the database and extract the data from the database of the production
server to media by using either the upgrade wizard or commands. For details,
see:
v “Scenario 3: Upgrading the server by using the upgrade wizard” on page 194
a. “Scenario 3, wizard: Installing the V7.1 server” on page 194
b. “Scenario 3, wizard: Creating the directories and the user ID for the
upgraded server instance” on page 198
c. “Scenario 3: Starting the upgrade wizard” on page 201

Chapter 2. Planning the upgrade 49

Upgrading the server from V5 to V7.1

After the database extraction is completed, you can pause the process by
exiting the wizard while you complete step 4 to restore and restart the
production server.
v “Scenario 3: Upgrading the server manually by using utilities” on page 202
a. “Scenario 3: Preparing the database of a V5 server for upgrade” on page
203
b. “Scenario 3: Extracting the data to media” on page 204
4. After the data is extracted from the production server, resume normal
operations by restoring the database backup that you made in step 1 on page
49 to the production server. You can then restart the production server.
5. From this point, continue your test by using the detailed procedures for
Scenario 3, using the test system as the new system.
v If you are using the wizard, restart the wizard if necessary, and continue at
the step after the extraction.
v If you are using commands, follow these steps:
a. Scenario 3: Installing the V7.1 server
b. Scenario 3: Creating the directories and the user ID for the upgraded
server instance
c. “Scenario 3: Creating and formatting the new database” on page 212
d. “Scenario 3: Loading the extracted data into the new database” on page
216
As part of your testing, you can use the PREVIEW=YES parameter on
the DSMSERV INSERTDB utility to test the insertion. When you preview the
insertion operation, you can quickly verify that the source database is
readable. You can also identify any data constraint violations that might
prevent an upgraded database from being put into production. When you
use this parameter, the operation includes all steps of the process, except
for the actual insertion of data into the new database.
e. “Scenario 3: Configuring the system for database backup” on page 219

Preparing for operational changes

As you upgrade your system from V5 to V7.1, the method for backing up and
monitoring the server database changes.

Procedure

Verify the operating procedures, scripts, and administrative schedules that you use
for server operations:
v Plan to back up the server database regularly by using administrative schedules,
a maintenance script, or your own scripts. Back up the server database at least
once per day. For best results, consider scheduling more frequent backups for
the V7.1 database than you did for the V5 database. To ensure that archive log
space is pruned, consider scheduling more full database backups and fewer
incremental backups.
Review information about how database backups are performed automatically
for the V7.1 server. For details, see the Administrator's Guide.
v Understand how database and recovery log space is used, and how monitoring
will change.
v Verify scripts and administrative schedules. The V7.1 server adds new
commands, changes some commands, and deletes some commands that are no

50 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

longer needed. These changes will affect your automated operations. For
information about new and changed commands, see “Command and option
changes.”
v Verify the SELECT commands that you use regularly. Some parameters and
syntax that were previously allowed are not accepted by the database manager
program. For information about SELECT command updates, see “Changes to the
SELECT command” on page 68. To resolve problems that are related to SELECT
commands, see Technote 1380830 (http://www.ibm.com/support/
docview.wss?uid=swg21380830).
v If you use products from independent software vendors to interface with the
server, ensure that the products are compatible with the V7.1 server.

What to do next

To use the new functions that are available in Tivoli Storage Manager V7.1, install
the latest version of the IBM Tivoli Storage Manager Operations Center.
Related concepts:
“Database protection and recovery” on page 5
“Recovery log” on page 4
“Database operations” on page 4
Related reference:
“Command and option changes”
“Changes to the SELECT command” on page 68

Reference information for planning

Information about new, changed, and deleted administrative commands, server
options, and server messages can help you plan for the V7.1 upgrade.

Command and option changes

Use the lists of new, changed, and deleted commands and options to help you
identify operation changes that are needed for your server.

New server commands, utilities, and options

As you plan to upgrade the server, be aware of new commands, utilities, and
options that were introduced in V6 and later.
“New commands”
“New utilities” on page 54
“New server options” on page 55

New commands
Table 21. New commands
Comparable commands
Command Function in previous versions
AUDIT LDAPDIRECTORY Audits a namespace that is controlled by Tivoli Storage None
Manager on a Lightweight Directory Access Protocol
(LDAP) server.
CANCEL REPLICATION Cancels all node replication processes. None
DEFINE ALERTTRIGGER Triggers an alert in the Operations Center whenever a None
server issues a specified error message.

Chapter 2. Planning the upgrade 51

Upgrading the server from V5 to V7.1

Table 21. New commands (continued)

Comparable commands
Command Function in previous versions

AIX Linux
DEFINE Defines a device class for a type of storage device. A None
DEVCLASS - z/OS media limited set of device class types is available for devices
server that are accessed through the z/OS media server.

AIX Linux
DEFINE Defines a library that represents a TAPE or FILE None
LIBRARY (Define a ZOSMEDIA storage resource that is maintained by Tivoli Storage
library type) Manager for z/OS Media.

AIX LinuxDEFINE Defines a path to a ZOSMEDIA library. You must first None
PATH (Define a path when the define the z/OS media server in your configuration
destination is a ZOSMEDIA with the DEFINE SERVER command.
library)
DEFINE STATUSTHRESHOLD Defines a status monitoring threshold. None
DELETE STATUSTHRESHOLD Deletes a status monitoring threshold. None
EXTEND DBSPACE Makes more storage space available for the server to DEFINE DBVOLUME
use for its database.
EXTEND DB
You can have multiple locations for database storage
space. After you install and use the DSMSERV FORMAT or
DSMSERV LOADFORMAT utility, you can add more storage
locations.
IDENTIFY DUPLICATES Starts or stops processes that identify duplicate data in None
a storage pool.
PERFORM LIBACTION Defines or deletes all drives and their paths for a None
single library in one step.
QUERY ALERTSTATUS Displays information about alerts that are issued on None
the Tivoli Storage Manager server.
QUERY ALERTTRIGGER Displays which server messages are defined as alerts. None
QUERY DBSPACE Displays information about the directories that are QUERY DBVOLUME
used by a database to store data.
QUERY MONITORSETTINGS Displays information about the configuration settings None
for monitoring alerts and server status.
QUERY MONITORSTATUS Displays monitoring messages that are within a None
defined status retention period.
QUERY PVUESTIMATE Generates an estimate of the client devices and server None
devices that are managed by a Tivoli Storage Manager
server. In addition, this command provides an estimate
of the processor value unit (PVU) totals for server
devices.
QUERY REPLICATION Displays information about running and completed None
node-replication processes.
QUERY REPLNODE Displays the number of client node files that are stored None
on source and target replication servers.
QUERY REPLRULE Displays information about replication rules. None
QUERY SSLKEYRINGPW Displays the Secure Sockets Layer (SSL) key database None
file password.
QUERY STATUSTHRESHOLD Displays information about thresholds for status None
monitoring.
REMOVE REPLNODE Removes a client node from replication. None

52 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 21. New commands (continued)

Comparable commands
Command Function in previous versions
REPLICATE NODE Replicates data in file spaces that belong to one or None
more client nodes or defined groups of client nodes.
SET ALERTACTIVEDURATION Specifies how long an alert remains active before it None
becomes inactive.
SET Specifies how long an alert remains closed before it is None
ALERTCLOSEDDURATION deleted.
SET ALERTEMAIL Enables alerts to be sent to specified administrators by None
email.
SET ALERTEMAILFROMADDR Specifies the email address of the alert sender. None
SET ALERTEMAILSMTPHOST Specifies the Simple Mail Transfer Protocol (SMTP) None
mail server host name that is used to send alerts by
email.
SET ALERTEMAILSMTPPORT Specifies the port number of an SMTP mail server that None
is used to send alerts by email.
SET Specifies how long an alert remains inactive. None
ALERTINACTIVEDURATION
SET ALERTMONITOR Enables or disables an alert monitor. None
SET Specifies the administrators who receive hourly alert None
ALERTSUMMARYTOADMINS summaries by email.
SET ALERTUPDATEINTERVAL Specifies how often an alert monitor updates and None
prunes alerts that are stored in the Tivoli Storage
Manager server database.
SET ARREPLRULEDEFAULT Sets the server replication rule for archive data. None
SET BKREPLRULEDEFAULT Sets the server replication rule for backup data. None
SET CPUINFOREFRESH Specifies the number of days between workstation None
scans, which are used to estimate PVU.
SET DBRECOVERY Sets the device class to use for backing up the server DEFINE
database. The database manager uses the device class DBBACKUPTRIGGER
for automatic backups of the database.
SET DBREPORTMODE Sets the amount of diagnostic information that is None
reported for a database.
SET Verifies extents that are sent to the server during None
DEDUPVERIFICATIONLEVEL client-side data deduplication.
SET Sets the default password authentication method for None
DEFAULTAUTHENTICATION nodes and administrators.
SET Sets the active-data pools that are included in recovery None
DRMACTIVEDATASTGPOOL plans and procedures.
SET LDAPPASSWORD Defines a password for a user name or ID that you None
specify by using the SET LDAPUSER command.
SET LDAPUSER Specifies the ID of a user or account that can conduct None
administrative operations when the user or account
accesses an LDAP directory server.
SET Defines a server group that is monitored for alerts and None
MONITOREDSERVERGROUP status.
SET MONITORINGADMIN Sets the name of the monitoring administrator that is None
used to connect to the servers in a monitored server
group.

Chapter 2. Planning the upgrade 53

Upgrading the server from V5 to V7.1

Table 21. New commands (continued)

Comparable commands
Command Function in previous versions
SET REPLRETENTION Specifies the retention period for client-node None
replication records in the source replication-server
database.
SET REPLSERVER Sets the name of a target replication server. None
SET SPREPLRULEDEFAULT Sets the server replication rule for space-managed None.
data.
SET SSLKEYRINGPW Provides the key database file password to the server. None
SET STATUSMONITOR Enables or disables status monitoring. None
SET Specifies the number of minutes between server None
STATUSREFRESHINTERVAL queries. The queries are used for status monitoring.
UPDATE ALERTTRIGGER Updates the attributes of one or more alert triggers. None
UPDATE ALERTSTATUS Updates the status of a reported alert. None

AIX Linux
UPDATE Updates a device class. A limited set of device class None
DEVCLASS - z/OS media types is available for devices that are accessed through
server a z/OS media server.

UPDATE FILESPACE Updates replication rules for file spaces. None

AIX LinuxUPDATE Updates a path to a ZOSMEDIA library. None

PATH (Update a path when the
destination is a ZOSMEDIA
library)
UPDATE REPLRULE Enables or disables a replication rule. None
UPDATE STATUSTHRESHOLD Updates a threshold for status monitoring. None
VALIDATE REPLICATION Identifies the replication rules that apply to file spaces None
in client nodes that are configured for replication.

z/OS ZMSPREPARE Analyzes the V5 server and generates a report that None
describes the steps that you must take before data
migration can begin.

New utilities
Table 22. New utilities
Comparable commands
Command Function in previous versions
DSMSERV DISPLAY DBSPACE Offline utility to view the current locations for DSMSERV DISPLAY
database storage. DBVOLUMES
DSMSERV DISPLAY LOG Offline utility to view information about recovery logs, DSMSERV DISPLAY
including active logs and archive logs. LOGVOLUMES
DSMSERV INSERTDB Offline utility that is used only for inserting data that None
was extracted from a V5 server database into an empty
V7.1 database.
DSMSERV REMOVEDB Offline utility that is used only when you are sure that None
you no longer need a server database and recovery
logs. Use with caution.
DSMUPGRD EXTEND DB Offline utility that is used only on a V5 server to None
extend the database when database space is
insufficient to complete the upgrade process.

54 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 22. New utilities (continued)

Comparable commands
Command Function in previous versions
DSMUPGRD EXTEND LOG Offline utility that is used only on a V5 server to None
extend the recovery log when recovery log space is
insufficient to complete the upgrade process.
DSMUPGRD EXTRACTDB Offline utility that is used only on a V5 server to None
extract the data from the database. The extracted data
is inserted into a V7.1 database by using the DSMSERV
INSERTDB utility.
DSMUPGRD PREPAREDB Offline utility that is used only on a V5 server to None
prepare the database for extraction. After this utility is
run, the data can be extracted from the database by
using the DSMUPGRD EXTRACTDB utility.
DSMUPGRD QUERYDB Offline utility that is used only on a V5 server to None
display information about the database and recovery
log.

New server options

Table 23. New server options. For some options, changes have no effect until the server is restarted.
Comparable
commands or options
New server option Function in previous versions
ACTIVELOGDIRECTORY The name of the directory where all active logs are DEFINE
stored. LOGVOLUME
ACTIVELOGSIZE The maximum size of the active log. EXTEND LOG

REDUCE LOG
ALLOWREORGINDEX Specifies whether server-initiated index reorganization None
is enabled.

ALLOWREORGTABLE Specifies whether server-initiated table reorganization None

is enabled.

ARCHFAILOVERLOGDIRECTORY The directory in which the server stores archive log None
files if they cannot be stored in the archive log
location.
ARCHLOGDIRECTORY The directory in which the server stores the archive None
log.
CLIENTDEDUPTXNLIMIT The maximum size of a transaction when client-side None
deduplicated data is backed up or archived.
DBDIAGPATHFSTHRESHOLD The threshold for free space on the file system or disk None
that contains the db2diag.log file. When the amount
of free space is equal to or less than the specified
threshold, the ANR1545W error message is shown.
DBMEMPERCENT The limit on the percentage of the system memory None
that is used for the database.
DBMTCPPORT The port number on which the TCP/IP None
communication driver for the database manager waits
for requests for client sessions.

Chapter 2. Planning the upgrade 55

Upgrading the server from V5 to V7.1

Table 23. New server options (continued). For some options, changes have no effect until the server is restarted.
Comparable
commands or options
New server option Function in previous versions
DEDUPTIER2FILESIZE Specifies at what file size Tivoli Storage Manager None
begins to use Tier 2 data deduplication.
DEDUPTIER3FILESIZE Specifies at what file size Tivoli Storage Manager None
begins to use Tier 3 data deduplication.
ENABLENASDEDUP Specifies whether a server deduplicates data that is None
stored by a network-attached storage (NAS) file server.
This option applies only to NetApp file servers.
FFDCLOGNAME The name of the first failure data capture (FFDC) log. None
FFDCMAXLOGSIZE The size of the FFDC log. None
LDAPCACHEDURATION The length of time that the Tivoli Storage Manager None
server caches LDAP password authentication
information.
LDAPURL The location of an LDAP directory server. None
MIRRORLOGDIRECTORY The directory where the log mirror for the active log is DEFINE LOGCOPY
stored.
NDMPENABLEKEEPALIVE Specifies whether the server enables the Transmission None
Control Protocol (TCP) keepalive function on network
data-management protocol (NDMP) control
connections to NAS devices.
NDMPKEEPIDLEMINUTES The amount of time, in minutes, before an operating None
system transmits the first TCP keepalive packet on an
NDMP control connection.
REORGBEGINTIME The earliest time that the Tivoli Storage Manager None
server can start table or index reorganization.
REORGDURATION The interval during which server-initiated table or None
index reorganization can start.

AIX Linux Solaris The amount of time that is allowed for host bus None
adapters to respond when they are queried by the
Windows
SAN discovery process.
SANDISCOVERYTIMEOUT
SERVERDEDUPTXNLIMIT The maximum size of objects that can be deduplicated None
on a server.
SSLFIPSMODE Specifies whether the Federal Information Processing None
Standards (FIPS) mode is in effect for SSL.
SSLTLS12 Controls Transport Layer Security (TLS) 1.2, an SSL None
protocol that is available for use with Tivoli Storage
Manager V6.3 or later. TLS 1.2 can be used only with
V6.3 or later clients.

56 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Updated server commands, utilities, and options

Be aware of the commands, utilities, and options that are updated in V6 and later.
“Updated commands”
“Updated utilities” on page 63
“Updated server options” on page 64

Updated commands
Table 24. Updated commands
Command Changes
BACKUP DB You must run the SET DBRECOVERY command
before the BACKUP DB command. By running
the SET DBRECOVERY command, you set the
device class for the database backup.

An incremental database backup is a backup

of all changes since the last full backup. In
earlier versions of the server, an incremental
backup was a backup of all changes since
either the last full backup or the last
incremental backup.

New parameters are available:

v The DEDUPDEVICE parameter identifies
storage devices that support data
deduplication and optimize backup
images that are stored on these devices.
v The NUMSTREAMS parameter specifies the
number of parallel data movement
streams that are used for database backup.
BACKUP NODE The commands include the SNAPMIRROR value
QUERY NASBACKUP for the TYPE parameter:
RESTORE NODE v When you specify the SNAPMIRROR value
for the BACKUP NODE command, the file
system is copied to a storage pool by
using the NetApp SnapMirror to Tape
feature.
v When you specify the SNAPMIRROR value
for the QUERY NASBACKUP command, the
output shows information about NetApp
SnapMirror images.
v When you specify the SNAPMIRROR value
for the RESTORE NODE command, the file
system is retrieved from a NetApp
SnapMirror image.
BACKUP STGPOOL The commands can be used with data
DEFINE STGPOOL deduplication functions.
QUERY STGPOOL
UPDATE STGPOOL

Chapter 2. Planning the upgrade 57

Upgrading the server from V5 to V7.1

Table 24. Updated commands (continued)

Command Changes
BACKUP VOLHISTORY Database memory dump operations are no
DELETE VOLHISTORY longer available. Therefore, database
QUERY VOLHISTORY memory dump volumes are not displayed in
UPDATE VOLHISTORY volume history.

AIX Linux z/OS If you are

migrating a V5 server that is running on a
z/OS operating system to a V7.1 server on
an AIX or Linux operating system, you can
issue the DELETE VOLHISTORY command on
the V5 server to prepare for the migration.
The command specifies the device class of
volumes to be deleted.
DEFINE DEVCLASS When you run the DEFINE DEVCLASS
UPDATE DEVCLASS command or the UPDATE DEVCLASS command
to specify a 3592 or LTO device class, you
can use the LBPROTECT parameter. The
LBPROTECT parameter specifies whether
logical block protection is used to ensure
data integrity on tape.

AIX Linux z/OS A limited

set of device class types is available for
devices that are accessed through a z/OS
media server.
DEFINE LIBRARY AIX Linux You can use the
DEFINE LIBRARY command to define a
ZOSMEDIA library type. In this way, you
can define a library that represents a tape or
FILE storage resource that is maintained by
Tivoli Storage Manager for z/OS Media.
DEFINE LIBRARY You can use the DEFINE LIBRARY command
UPDATE LIBRARY to define a virtual tape library (VTL) to the
Tivoli Storage Manager server. You can use
the UPDATE LIBRARY command to update a
VTL definition.

AIX Linux You can use the DEFINE PATH command to

DEFINE PATH define a path to a ZOSMEDIA library.

DEFINE SERVER You can use the DEFINE SERVER command to

define a server for the following functions:
LAN-free data movement, node replication,
and data movement by using z/OS media
server.
DEFINE SPACETRIGGER The commands can be used only for storage
DELETE SPACETRIGGER pools. Space triggers are no longer available
QUERY SPACETRIGGER for databases and logs.
UPDATE SPACETRIGGER
DEFINE VOLUME The maximum capacity of a volume in a
DISK storage pool is 8 TB.
DISABLE SESSIONS The DIRECTION parameter specifies whether
ENABLE SESSIONS to disable or enable inbound sessions,
outbound sessions, or both.

58 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 24. Updated commands (continued)

Command Changes
EXPIRE INVENTORY Expiration processing can be run for specific
nodes and node groups, or for all nodes in a
policy domain. The types of data to be
examined for expiration can be specified.

The values for the DURATION parameter are

changed. You can specify a value in the
range 1 - 999999 to define the maximum
number of minutes for the expiration
process.
GRANT AUTHORITY The ANALYST privilege class is removed.
REVOKE AUTHORITY
HALT The QUIESCE parameter is removed.
LOCK ADMIN The AUTHENTICATION parameter specifies the
method of authentication that the
administrator uses to log on.
LOCK NODE The AUTHENTICATION parameter specifies the
method of password authentication that is
required to log on to a node.
MOVE DRMEDIA Changes to disaster recovery manager
PREPARE commands make it possible to include
QUERY DRMEDIA active-data pools in recovery plans and
QUERY DRMSTATUS procedures.

The MOVE DRMEDIA command cannot be used

concurrently with the BACKUP STGPOOL
command. Ensure that the primary storage
pool backup process is complete before you
back up the database. Ensure that the BACKUP
STGPOOL command and the BACKUP DB
command are complete before you issue the
MOVE DRMEDIA command.
QUERY DB The output shows the total number of free
pages in all table spaces.

AIX Linux You can use this command to view

QUERY DEVCLASS information that is specific to the z/OS
QUERY LIBRARY media server.
QUERY PATH
QUERY FILESPACE You can use this command to view
replication information.
QUERY LOG You can use this command to view
information about the active log directory,
mirror log directory, archive failover log
directory, and archive log directory.
QUERY NODE You can use this command to view
information about the password
authentication method and security settings
for the administrator ID.
QUERY OPTION Obsolete options are removed from the
output. The output is updated to include
information about settings for LDAP
directory servers.

Chapter 2. Planning the upgrade 59

Upgrading the server from V5 to V7.1

Table 24. Updated commands (continued)

Command Changes
QUERY PROCESS You can use this command to obtain
information about duplicate identification
processes.
QUERY SERVER You can use this command to find out
whether Secure Sockets Layer (SSL)
communication is used.
QUERY SESSION You can use this command to display the
actions that occurred during the session.
QUERY STATUS Obsolete options and the database backup
trigger are removed.

You can use this command to verify whether

passwords are authenticated with the Tivoli
Storage Manager server or with the LDAP
directory server.

You can also view the name that is specified

for the default target replication server.
QUERY VOLHISTORY For the TYPE parameter, the values RPFile
and RPFSnapshot are added. By using the
values, you can display records that contain
information about recovery plan file objects.
QUERY VOLUME You can use this command to verify whether
logical block protection is enabled.
REGISTER ADMIN New parameters are available:
v The ALERT parameter specifies whether
alerts are sent to an administrator email
address.
v The AUTHENTICATION parameter specifies
the authentication method for the
administrator user ID.
v The SSLREQUIRED parameter specifies
whether the administrator user ID must
use SSL to communicate with the
backup-archive client from the Tivoli
Storage Manager server.
REGISTER ADMIN In these commands, the ALERT parameter
QUERY ADMIN specifies whether alerts are sent to an
UPDATE ADMIN administrator email address.

In the QUERY ADMIN command, the output is

updated to include information about email
alerts, the password authentication method,
and security settings for the administrator
ID.
REGISTER LICENSE You are required to use this command to
register licenses for server components. Use
of the REGISTER LICENSE command implies
that you agree to and accept the license
terms that are specified in the license
agreement.

60 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 24. Updated commands (continued)

Command Changes
REGISTER NODE New parameters are available:
v The AUTHENTICATION parameter specifies
the password authentication method for
the node.
v The BACKUPINITIATION parameter specifies
whether the non-root user ID on the client
node can back up files to the server.
v The BKREPLRULEDEFAULT,
ARREPLRULEDEFAULT, and
SPREPLRULEDEFAULT parameters specify the
replication rule that applies to a data type
if the file space rules for the data type are
set to DEFAULT.
v The REPLSTATE parameter specifies
whether data that belongs to the client
node is ready to be replicated.
v The ROLEOVERRIDE parameter specifies
whether to override the reported role of
the client for PVU estimation.
v The SSLREQUIRED parameter specifies
whether the node must use SSL to
communicate with the Tivoli Storage
Manager server.
REMOVE ADMIN You can use the SYNCLDAPDELETE parameter
to remove an administrative user ID that is
stored on an LDAP directory server.
REMOVE NODE You can use the SYNCLDAPDELETE parameter
to remove a node ID that is stored on an
LDAP directory server.
RENAME ADMIN You can use the SYNCLDAPDELETE parameter
to rename an administrative user ID that
authenticates to an LDAP directory server.
RENAME NODE You can use the SYNCLDAPDELETE parameter
to rename a node ID that is stored on an
LDAP directory server.

Chapter 2. Planning the upgrade 61

Upgrading the server from V5 to V7.1

Table 24. Updated commands (continued)

Command Changes
SELECT The following updates apply to the SELECT
command:
v In previous versions of the server, syntax
that did not conform to SQL syntax rules
could be used in the SELECT command. In
V6.3 and later, you must use SQL syntax
that conforms to the syntax rules of the
database manager, DB2.
v You can use the SELECT * FROM
PVUESTIMATE_DETAILS query to generate a
PVU report that provides detailed
information at the node level.
v You can use the SELECT command to list
user ID passwords for administrators and
nodes that authenticate with an LDAP
directory server.
v You can use the SELECT command to
verify whether logical block protection is
enabled for a device class or volume.
SET DBRECOVERY The NUMSTREAMS parameter specifies the
number of concurrent data movement
streams to use while you back up the
database.
SETOPT Obsolete options are removed. The
LDAPCACHEDURATION option determines the
length of time that the Tivoli Storage
Manager server caches information about
LDAP password authentication.
UNLOCK ADMIN The AUTHENTICATION parameter specifies the
method of password authentication that is
required for an administrator to log on.
UNLOCK NODE The AUTHENTICATION parameter specifies the
method for node password authentication.
UPDATE ADMIN The ANALYST privilege class is removed. New
parameters are available:
v The AUTHENTICATION parameter specifies
the password authentication method that
is used for the administrator ID.
v The SSLREQUIRED parameter specifies
whether the administrator user ID must
use SSL to communicate with the
backup-archive client from the Tivoli
Storage Manager server.
v The SYNCLDAPDELETE parameter is used to
remove an administrator user ID from an
LDAP directory server.

62 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 24. Updated commands (continued)

Command Changes
UPDATE NODE The ANALYST privilege class is removed. New
parameters are available:
v The AUTHENTICATION parameter specifies
the password authentication method.
v The SSLREQUIRED parameter specifies
whether a node must use SSL to
communicate with the Tivoli Storage
Manager server.
v The SYNCLDAPDELETE parameter is used to
change the authentication method for a
node from authentication with the LDAP
directory server to authentication with the
Tivoli Storage Manager server.
UPDATE LIBRARY You can use this command to update a
library definition for a VTL.
UPDATE NODE New parameters are available:
v The BACKUPINITIATION parameter specifies
whether the non-root user ID on the client
node can back up files to the server.
v The ROLEOVERRIDE parameter specifies
whether to override the reported role of
the client for PVU estimation.

AIX Linux UPDATE PATH You can use this command to update a path
to a ZOSMEDIA library.
UPDATE SERVER You can use this command to specify
whether to use SSL during server-to-server
communications.

Updated utilities
Table 25. Updated utilities
Utility Changes
DSMSERV You can specify the owning user ID for the
server instance on startup. You can also
specify the user ID for other DSMSERV
utilities.
DSMSERV FORMAT Obsolete parameters are removed. New
parameters are available to specify the
directories for database space, and the
maximum size and locations of the recovery
log.
DSMSERV INSERTDB The CONFIGINFO parameter specifies the
device configuration information that is used
by the DSMSERV INSERTDB utility to load a
database.

Chapter 2. Planning the upgrade 63

Upgrading the server from V5 to V7.1

Table 25. Updated utilities (continued)

Utility Changes
DSMSERV RESTORE DB Volume history is required for restoring a
database.

All restore operations use rollforward

recovery.

The function for restoring individual

database volumes is removed. The server no
longer manages database volumes.

AIX Linux The MEDIASERVER parameter is used during

DSMUPGRD EXTRACTDB an upgrade from a V5 server on z/OS. The
DSMUPGRD PREPAREDB parameter specifies the name of the server to
be used as the z/OS media server.

Updated server options

Table 26. Updated server options
Option Changes
CHECKTAPEPOS You can use the CHECKTAPEPOS option to
enable append-only mode for IBM LTO
Generation 5 and later drives, and for any
drives that support this feature.

AIX Linux Solaris The SANDISCOVERY option changed in Tivoli

Storage Manager V5.5.3 and later releases.
To ensure that the system operates correctly,
Windows SANDISCOVERY verify the setting for the SANDISCOVERY
option.
TXNGROUPMAX The default value is increased from 256 to
4096. Verify whether the server options file
has this option:
v If the server options file does not include
this option, the server automatically uses
the new default value.
v If the server options file includes a value
for the option, the server uses the
specified value. If the specified value is
less than 4096, consider increasing this
value, or removing the option so that the
server uses the new default value. By
increasing the value or using the new
default value, you can improve the
performance for data movement
operations such as storage pool migration
and storage pool backup.

Increasing the value for the TXNGROUPMAX

option has no effect on data-movement
performance for files that were stored on the
server by using a smaller value for the
option.

64 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Deleted server commands, utilities, and options

Some commands, utilities, and options are deleted because their function is no
longer needed. In some cases, new commands replace deleted commands.
“Deleted commands”
“Deleted utilities” on page 66
“Deleted server options” on page 67

Deleted commands
Table 27. Deleted commands
Deleted command Comments
CONVERT ARCHIVE The operation that this command performed
is no longer needed.
DEFINE DBBACKUPTRIGGER Ensure that you schedule backups of the
DELETE DBBACKUPTRIGGER database to occur at least once per day.
QUERY DBBACKUPTRIGGER
UPDATE DBBACKUPTRIGGER
DEFINE DBCOPY Database volumes are no longer used.
DEFINE DBVOLUME Space allocation is done automatically in the
QUERY DBVOLUME directory locations specified for the database.
DEFINE LOGCOPY Instead of log volume copies, you can
specify a log mirror to have the active log
protected by a mirror copy.
DEFINE LOGVOLUME The database manager automatically
DELETE LOGVOLUME manages space in the recovery log
QUERY LOGVOLUME directories.

For information about the directories that

are used for the logs, use the QUERY LOG
command.
ESTIMATE DBREORGSTATS Collecting and resetting database statistics
occurs automatically.

Database-reorganization operations are done

automatically by the database manager as
needed.
EXTEND DB Space allocation is done automatically in the
directory locations specified for the database.
If the server needs additional space, you can
add directory locations by using the EXTEND
DBSPACE command.
EXTEND LOG Server options are available for increasing
the size of recovery logs.
QUERY SQLSESSION The information that this command supplied
is no longer in the server database. SQL
SELECT settings are replaced by syntax
options that are available in a DB2 SELECT
command.
REDUCE DB Space allocation is done automatically in the
directory locations specified for the database.
You cannot adjust the assigned capacity of
the database.

Chapter 2. Planning the upgrade 65

Upgrading the server from V5 to V7.1

Table 27. Deleted commands (continued)

Deleted command Comments
REDUCE LOG The database manager automatically
manages space in the recovery log
directories.
RESET BUFPOOL The BUFPOOLSIZE option is eliminated;
therefore, this command is not needed.
RESET DBMAXUTILIZATION Collecting and resetting database statistics
RESET LOGCONSUMPTION occurs automatically.
RESET LOGMAXUTILIZATION
SET LOGMODE Logging mode for the database is now
always roll-forward mode.
SET SQLDATETIMEFORMAT The commands are replaced by options in
SET SQLDISPLAYMODE the DB2 SELECT command syntax.
SET SQLMATHMODE
UNDO ARCHCONVERSION The operation that this command performed
is no longer needed.
UPDATE ARCHIVE The operation that this command performed
is no longer needed.

Deleted utilities
Table 28. Deleted utilities
Deleted utility Comments
DSMFMT Space allocation is done automatically in the
directory locations specified for the database.
DSMSERV AUDITDB Offline database audits are no longer
required.

As data is added to the server database, the

database manager automatically checks data
constraints and data types. The online
integrity checks prevent problems for which
offline audits were required in earlier
releases.
DSMSERV DISPLAY DBBACKUPVOLUME Information about volumes used for
database backup is available from the
volume history file. The volume history file
is now required to restore the database.
DSMSERV DISPLAY DBVOLUMES Use DSMSERV DISPLAY DBSPACE to view
information about database space when the
server is not running.
DSMSERV DISPLAY LOGVOLUMES Use DSMSERV DISPLAY LOG to display
information about recovery logs including
the active log, the mirror for the active log,
the failover directory for the archive log, and
the overflow location for logs.
DSMSERV DUMPDB The operation that this utility performed is
no longer needed.

66 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 28. Deleted utilities (continued)

Deleted utility Comments
DSMSERV EXTEND LOG This utility is replaced by the following
server options:
ACTIVELOGSIZE
ACTIVELOGDIRECTORY
MIRRORLOGDIRECTORY
With these options, you can add recovery
log space if the log is full when the server is
down.
DSMSERV LOADDB The operation that this utility performed is
no longer needed.
DSMSERV RESTORE DB The server does not track individual
v Restore a single database volume to its database volumes in V7.1.
most current state
The volume history file is required to
v Restore a database to a point in time perform database restore operations.
when a volume history file is unavailable
DSMSERV UNLOADDB The operation that this utility performed is
no longer needed.

Deleted server options

When you start the server, you might receive warning messages about server
options that are not supported, but that cannot be found in this list of deleted
options. V5 releases tolerated the presence of some server options that were not
supported by the server. The V7.1 server flags such options by issuing warning
messages. You can ignore the error, or update the server options file and restart the
server.
Table 29. Deleted server options
Deleted option Comments
BUFPOOLSIZE The server adjusts the value of buffer pool
size dynamically.
DBPAGESHADOW The option is no longer needed.
DBPAGESHADOWFILE The option is no longer needed.
LOGPOOLSIZE The server uses its own fixed-size recovery
log buffer pool.
LOGWARNFULLPERCENT The option is no longer needed.
MIRRORREAD Mirroring of the active log is supported, but
MIRRORWRITE not of the database. Provide availability
protection for the database by locating the
database on devices that have high
availability characteristics.
SELFTUNEBUFPOOLSIZE The server adjusts the buffer pool size
dynamically.

Chapter 2. Planning the upgrade 67

Upgrading the server from V5 to V7.1

Changes to the SELECT command

In previous versions of the server, the SELECT command allowed syntax that did
not always conform to SQL syntax rules. With V7, the server conforms to SQL
syntax rules in use by its database manager, the DB2 program. Some examples
illustrate changes that you might need to make to SELECT statements that you use.
“LIKE predicate for a nested SELECT statement”
“SELECT statements for time calculation”
“The index_keyseq and index_order columns”
“Access to database objects by using the SELECT command” on page 69
“Retrieval of information from more than one database table” on page 69
“Results of the SELECT command for the DISK device class” on page 69
“Extra spaces in output” on page 69
“Data types for arithmetic operations” on page 69

LIKE predicate for a nested SELECT statement

You cannot use the LIKE predicate for a nested SELECT statement. For example, you
receive an error if you use the LIKE predicate as in this statement:
select * from volumeusage where volume_name like (select distinct volume_name
from volumeusage where node_name=’node1’)

Replace such usage with the in parameter, as in this statement:

select * from volumeusage where volume_name in (select distinct volume_name
from volumeusage where node_name=’node1’)

SELECT statements for time calculation

Labeled duration cannot be compared in a SELECT statement. For example, the

following statement results in an SQL error:
select * from actlog where (current_time-date_time) seconds <= 60 seconds

The following statements are examples of correct usage.

To list the activity log entries for the last 60 seconds, use a statement similar to this
one:
select * from actlog where
TIMESTAMPDIFF(2,CHAR(current_timestamp-date_time)) <= 60

To list the activity log entries for the last 60 minutes, use a statement similar to this
one:
select * from actlog where
TIMESTAMPDIFF(4,CHAR(current_timestamp-date_time)) <= 60

The index_keyseq and index_order columns

The system catalog tables SYSCAT.COLUMNS and SYSCAT.TABLES are now

processed by the database manager, instead of directly by the Tivoli Storage
Manager server. The INDEX_KEYSEQ and INDEX_ORDER columns are not available. Use
the KEYSEQ column instead. For instructions, go to the DB2 information center at
http://pic.dhe.ibm.com/infocenter/db2luw/v10r5. Enter keyseq as the search
term.

68 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Access to database objects by using the SELECT command

The database objects that can be accessed by using the SELECT command are the
same as for earlier versions of the server, with some additions for new functions.

However, the SYSCAT.COLUMNS and SYSCAT.TABLES catalog tables now include

all database objects that are known to the server, including some objects that
cannot be accessed through the SELECT command. You receive an error message if a
SELECT command includes an attempt to access one of these objects.

Retrieval of information from more than one database table

To retrieve information from more than one table, use a join process. Many types
of join processes can be used.

For example, the following command, which worked with earlier versions of the
server, no longer works:
select entity,activity,sum(bytes),sum(end_time-start_time),sum(affected),sum(failed),sum(mediaw)
from summary where entity in (select node_name from nodes) and
cast((current_timestamp-start_time)hours as decimal)<24 group by entity,activity

You can declare names for columns that are retrieved from multiple tables so that a
conditional statement can be run with the results that you want from the SELECT
command. For example:
select entity,activity,sum(bytes),sum(end_time-start_time),sum(affected),sum(failed),sum(mediaw)
from summary su, nodes nd where su.entity=nd.node_name and
cast((current_timestamp-start_time)hours as decimal)<24 group by entity,activity

Results of the SELECT command for the DISK device class

Results when you use the SELECT command to get information from the DEVCLASSES
table have changed slightly for the DISK device class.

In previous releases, the SHARED field was blank (null) for the DISK device class.
Now, the SHARED field contains the value NO. The SHARED field does not apply to the
DISK device class, and the value NO can be ignored.

Extra spaces in output

If the output includes trailing spaces, such as in the following tabschema output
example, you can use the RTRIM scalar function to remove them.
dsmadmc -errorlogn=errorlog -id=admin -pa=admin -comma -dataonly=y
’select tabschema,tabname from tables’

SYSCAT ,ATTRIBUTES
SYSCAT ,AUDITPOLICIES
SYSCAT ,AUDITUSE

For example, if you are writing scripts for automation and must strip out the
additional spaces, you can use the RTRIM scalar function:
select rtrim(tabschema) as tabschema, tabname from syscat.tables

Data types for arithmetic operations

Changes in how data types for arithmetic operations are handled might require
changes to SELECT commands that worked in earlier versions of the server.

Chapter 2. Planning the upgrade 69

Upgrading the server from V5 to V7.1

For example, the following command causes an arithmetic overflow error because
of the SUM statement:
select node_name,sum(capacity) as capacity,
sum(capacity * (pct_util/100)) as used from filespaces group by node_name

To make the command compatible with V7.1, add the CAST function to convert the
items in the SUM statement to decimal data types:
select node_name,sum(capacity) as capacity,
sum(cast(capacity as decimal) * cast((pct_util/100) as decimal)) as used from
filespaces group by node_name

New and changed server messages

If you have scripts or other automation that use server messages, check the lists of
new, changed, and deleted messages for items that you might need to change.

Lists are available in the information center:

http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1

Server naming best practices

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

Instance user ID

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

For example: tsminst1

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

AIX HPUX Linux Solaris

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

Database instance name

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

70 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Windows
The database instance name is the name of the server instance as it is listed
in the registry.
For example: Server1

Instance directory

The instance directory is a directory that contains files specifically for a server
instance (the server options file and other server-specific files). It can have any
name that you want. For easier identification, use a name that ties the directory to
the instance name.
AIX HPUX Linux Solaris
You can create the instance directory as a subdirectory of the home
directory for the instance user ID. For example: /home/instance_user_ID/
instance_user_ID
The following example places the instance directory in the home directory
for user ID tsminst1: /home/tsminst1/tsminst1
You can also create the directory in another location, for example:
/tsmserver/tsminst1
The instance directory stores the following files for the server instance:
v The server options file, dsmserv.opt
v The server key database file, cert.kdb, and the .arm files (used by clients
and other servers to import the Secure Sockets Layer certificates of the
server)
v Device configuration file, if the DEVCONFIG server option does not specify
a fully qualified name
v Volume history file, if the VOLUMEHISTORY server option does not specify a
fully qualified name
v Volumes for DEVTYPE=FILE storage pools, if the directory for the
device class is not fully specified, or not fully qualified
v User exits
v Trace output (if not fully qualified)
Windows
You can use a name that includes the name of the server instance as it is
listed (or will be listed) in the registry. Default server instance names have
the form Serverx.
For example: C:\tsm\server1
The instance directory stores the following files for the server instance:
v The server options file, dsmserv.opt
v The server key database file, cert.kdb, and the .arm files (used by clients
and other servers to import the Secure Sockets Layer certificates of the
server)
v Device configuration file, if the DEVCONFIG server option does not specify
a fully qualified name
v Volume history file, if the VOLUMEHISTORY server option does not specify a
fully qualified name
v Volumes for DEVTYPE=FILE storage pools, if the directory for the
device class is not fully specified, or not fully qualified

Chapter 2. Planning the upgrade 71

Upgrading the server from V5 to V7.1

v User exits
v Trace output (if not fully qualified)

Database name

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

Server name

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

AIX Linux The server name is also used when you add the
Windows
server to the Operations Center so that it can be managed by using that interface.
Use a unique name for each server. For easy identification in the Operations Center
(or from a QUERY SERVER command), use a name that reflects the location or
purpose of the server.

Do not change the name of a Tivoli Storage Manager server after it is configured as
a hub or spoke server.

HPUX Use a unique name for each server. For easy identification from a QUERY
SERVER command, use a name that reflects the location or purpose of the server.

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

For example:
AIX HPUX Linux Solaris

PAYROLL
SALES
Windows

TUCSON_SERVER1
TUCSON_SERVER2

For more information about server names, see the Administrator's Guide.

Directories for database space and recovery log

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

For example, for the archive log:

AIX HPUX Linux Solaris /tsminst1_archlog
Windows f:\server1\archlog

72 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 3. Upgrade scenarios overview
You can upgrade the IBM Tivoli Storage Manager server on the same system or a
new system. You can use either a media method or a network method to move
data from the original server database to the upgraded server database.
Descriptions of the scenarios illustrate the order of steps for the different
approaches.

About this task

Select the scenario that you are interested in from the following table. The
scenarios are presented in overview form in this section, to summarize the steps
that are required in each case. To complete the procedure, follow the link from the
scenario overview to the detailed procedures.
Table 30. Links to scenario overviews
Scenario Location of upgraded server Method for moving data
“Scenario 1 for upgrading Same system as original Media method
the server: same system, server
media method”
“Scenario 2 for upgrading Same system as original Network method
the server: same system, server
network method” on page 78
“Scenario 3 for upgrading New system Media method
the server: new system,
media method” on page 82
“Scenario 4 for upgrading New system Network method
the server: New system,
network method” on page 86

Related concepts:
“Comparison of upgrading on an existing system and a new system” on page 13
“Comparison of methods for moving data to the V7.1 database” on page 15

Scenario 1 for upgrading the server: same system, media method

In this scenario, all upgrade tasks are completed on the same system. The database
is extracted to media and later inserted into the V7.1 database.

You can use the wizard, or upgrade the server manually by using the utilities. The
wizard offers a guided approach to the upgrade of a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Related concepts:
“Comparison of upgrading on an existing system and a new system” on page 13
“Comparison of methods for moving data to the V7.1 database” on page 15
Related tasks:
Chapter 4, “Scenario 1: Same system, media method,” on page 91

© Copyright IBM Corp. 2009, 2013 73

Upgrading the server from V5 to V7.1

Upgrading the server by using the wizard

To upgrade the server by using the wizard, you must complete preparation tasks,
uninstall the V5 server, install the V7.1 server, and start the upgrade wizard.

74 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Upgrade to V7 on the same system, media method

Upgrade using the upgrade wizard

V5 database tasks

V7 database tasks 1. Preparation tasks. Back up the V5 database.

2. Install DSMUPGRD utilities.

3. Prepare the V5 database. Run the

DSMUPGRD PREPAREDB utility.

4. Uninstall the V5 server.

5. Install the V7 server.

6. Create the directories and the user ID for

the V7 server.

Version 5 Tivoli
Storage Manager
server

7. Start the upgrade wizard. Use the wizard

to configure the V7 server and upgrade
the V5 database.

8. Complete postinstallation steps.

Figure 1. Scenario 1

The following steps are a summary of the procedure for this scenario. If this
scenario matches your environment, see the details for the procedure: Chapter 4,
“Scenario 1: Same system, media method,” on page 91.

Chapter 3. Upgrade scenarios overview 75

Upgrading the server from V5 to V7.1

Procedure
1. Complete all preparation tasks, which include backing up the database.
2. Install the upgrade utilities package (DSMUPGRD) on the system. The utilities
package must be installed whether you are using the upgrade wizard or
performing the upgrade with utilities.
3. Prepare the V5 database by using the DSMUPGRD PREPAREDB utility.
4. Uninstall the V5 server code.
5. Install the V7.1 server code on the system.
6. Create the directories for the V7.1 database and logs, and the user ID that will
own the server instance.
7. Start the upgrade wizard to configure the new server and upgrade the V5
database. With the wizard, you complete the following tasks:
a. Extract the V5 database to external media.
b. Create and format an empty database to receive the data.
c. Insert the data from the media to which it was extracted.
d. Configure the system for database backup.
8. Complete the post-installation tasks, including backing up the database and
verifying the database contents.

Upgrading the server manually by using utilities

To upgrade the server manually, you must uninstall the V5 server, install the V7.1
server, and complete manual steps to move the data to the V7.1 database.

76 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Upgrade to V7 on the same system, media method

Upgrade using the command line and upgrade utilities

V5 database tasks V7 database tasks

1. Preparation tasks. Back up 7. Extract the V5 database to external

media. Run the DSMUPGRD
the V5 database.
EXTRACTDB utility.

2. Install DSMUPGRD utilities. 8. Create and format an empty V7

database. Run db2icrt and the
DSMSERV LOADFORMAT utility.

3. Prepare the V5 database.

Run the DSMUPGRD
PREPAREDB utility.

9. Insert data from media into the new

database. Run the DSMSERV
4. Uninstall the V5 server. INSERTDB utility.

5. Install the V7 server. 10. Configure

backup.
the system for a database

6. Create the directories and the

user ID for the V7 server.
11. Complete postinstallation steps.

Version 5 Tivoli
Storage Manager
server

Figure 2. Scenario 1

The following steps are a summary of the procedure for this scenario. If this
scenario matches your environment, see the details for the procedure: Chapter 4,
“Scenario 1: Same system, media method,” on page 91.

Chapter 3. Upgrade scenarios overview 77

Upgrading the server from V5 to V7.1

Procedure
1. Complete all preparation tasks, which include backing up the database.
2. Install the upgrade utilities package (DSMUPGRD) on the system. The utilities
package must be installed whether you are using the upgrade wizard or
performing the upgrade with utilities.
3. Prepare the V5 database by using the DSMUPGRD PREPAREDB utility.
4. Uninstall the V5 server code.
5. Install the V7.1 server code on the system.
6. Create the directories for the V7.1 database and logs, and the user ID that will
own the server instance.
7. Extract the V5 database to external media by using the DSMUPGRD EXTRACTDB
utility.
8. Create and format an empty database to receive the data. The database is
created with the db2icrt command. The database is formatted by using the
DSMSERV LOADFORMAT utility.
9. Insert the data from the media to which it was extracted. You must have the
manifest file that was created as part of the extraction process. Use the
DSMSERV INSERTDB utility.
10. Configure the system for database backup.
11. Complete the post-installation tasks, including backing up the database and
verifying the database contents.

Scenario 2 for upgrading the server: same system, network method

In this scenario, all upgrade tasks are completed on the same system. The data is
extracted from the original server database and inserted into the new server
database at the same time.

You can use the wizard, or upgrade the server manually by using the utilities. The
wizard offers a guided approach to the upgrade of a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Related concepts:
“Comparison of upgrading on an existing system and a new system” on page 13
“Comparison of methods for moving data to the V7.1 database” on page 15
Related tasks:
Chapter 5, “Scenario 2: Same system, network method,” on page 135

Upgrading the server by using the wizard

To upgrade the server by using the wizard, you must complete preparation tasks,
uninstall the V5 server, install the V7.1 server, and start the upgrade wizard.

78 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Upgrade to V7 on the same system, network method

Upgrade using the upgrade wizard

V5 database tasks

V7 database tasks
1. Preparation tasks. Back up the V5 database.

2. Install DSMUPGRD utilities.

3. Prepare the V5 database. Run the

DSMUPGRD PREPAREDB utility.

4. Uninstall the V5 server.

5. Install the V7 server.

6. Create the directories and the user ID for

the V7 server.
Version 5 Tivoli
Storage Manager
server

7. Start the upgrade wizard. Use the wizard

to configure the V7 server and upgrade
the V5 database.

8. Complete postinstallation steps.

Figure 3. Scenario 2

The following steps are a summary of the procedure for this scenario. If this
scenario matches your environment, see the details for the procedure: Chapter 5,
“Scenario 2: Same system, network method,” on page 135.

Chapter 3. Upgrade scenarios overview 79

Upgrading the server from V5 to V7.1

Procedure
1. Complete all preparation tasks, which include backing up the database.
2. Install the upgrade utilities package (DSMUPGRD) on the system. The utilities
package must be installed whether you are using the upgrade wizard or
performing the upgrade with utilities.
3. Prepare the V5 database by using the DSMUPGRD PREPAREDB utility.
4. Uninstall the V5 server code.
5. Install the V7.1 server code on the system.
6. Create the directories for the V7.1 database and logs, and the user ID that will
own the server instance.
7. Start the upgrade wizard to configure the new server and upgrade the V5
database. With the wizard, you complete the following tasks:
a. Create and format an empty database to receive the data.
b. Move the data from the V5 database to the V7.1 database.
c. Configure the system for database backup.
8. Complete the post-installation tasks, including backing up the database and
verifying the database contents.

Upgrading the server manually by using utilities

To upgrade the server manually, you must uninstall the V5 server, install the V7.1
server, and complete manual steps to move the data to the V7.1 database.

80 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Upgrade to V7 on the same system, network method

Upgrade using the command line and upgrade utilities

V5 database tasks V7 database tasks

1. Preparation tasks. Back up 7. Create and format an empty V7 database.

Run db2icrt and the DSMSERV
the V5 database.
LOADFORMAT utility.

2. Install DSMUPGRD utilities.

8. Start the insertion for the new server. Run
the DSMSERV INSERTDB utility.

3. Prepare the V5 database.

Run the DSMUPGRD
PREPAREDB utility.

9. Start the extraction process. Run the

DSMUPGRD EXTRACTDB utility.
4. Uninstall the V5 server.

5. Install the V7 server. 10. Configure

backup.
the system for a database

6. Create the directories and the

user ID for the V7 server. 11. Complete postinstallation steps.

Version 5 Tivoli
Storage Manager
server

Figure 4. Scenario 2

The following steps are a summary of the procedure for this scenario. If this
scenario matches your environment, see the details for the procedure: Chapter 5,
“Scenario 2: Same system, network method,” on page 135.

Chapter 3. Upgrade scenarios overview 81

Upgrading the server from V5 to V7.1

Procedure
1. Complete all preparation tasks, which include backing up the database.
2. Install the upgrade utilities package (DSMUPGRD) on the system. The utilities
package must be installed whether you are using the upgrade wizard or
performing the upgrade with utilities.
3. Prepare the V5 database by using the DSMUPGRD PREPAREDB utility.
4. Uninstall the V5 server code.
5. Install the V7.1 server code on the system.
6. Create the directories for the V7.1 database and logs, and the user ID that will
own the server instance.
7. Create and format an empty database to receive the data. The database is
created with the db2icrt command. The database is formatted by using the
DSMSERV LOADFORMAT utility.
8. Start the insertion process for the new server by using the DSMSERV INSERTDB
utility.
9. Start the extraction process from the V5 database by using the DSMUPGRD
EXTRACTDB utility.
10. Configure the system for database backup.
11. Complete the post-installation tasks, including backing up the database and
verifying the database contents.

Scenario 3 for upgrading the server: new system, media method

In this scenario, some upgrade tasks are completed on the original system and
some on the new system. The database is extracted to media and later inserted into
the V7.1 database.

You can use the wizard, or upgrade the server manually by using the utilities. The
wizard offers a guided approach to the upgrade of a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Related concepts:
“Comparison of upgrading on an existing system and a new system” on page 13
“Comparison of methods for moving data to the V7.1 database” on page 15
Related tasks:
Chapter 6, “Scenario 3: New system, media method,” on page 177

Upgrading the server by using the wizard

To upgrade the server by using the wizard, you must install the upgrade utilities
and the V7.1 server. Then, create the directories and user ID for the 7.1 server and
start the upgrade wizard.

82 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Upgrade to V7 on a new system, media method

Upgrade using the upgrade wizard

3. Install the V7 server.

4. Create the directories and the

user ID for the V7 server.

1. Preparation
database.
tasks. Back up the V5

5. Start the upgrade wizard. Use

the wizard to configure the V7
server and upgrade the V5
2. Install DSMUPGRD utilities on the
V5 system.
database.

6. Complete postinstallation steps.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager
server server

Figure 5. Scenario 3

The following steps are a summary of the procedure for this scenario. If this
scenario matches your environment, see the details for the procedure: Chapter 6,
“Scenario 3: New system, media method,” on page 177.

Procedure
1. Complete all preparation tasks on the original system. Preparation includes
performing a database backup.
2. Install the DSMUPGRD utilities package on the original system. The utilities
package must be installed whether you are using the upgrade wizard or are
upgrading the server manually by using utilities.

Chapter 3. Upgrade scenarios overview 83

Upgrading the server from V5 to V7.1

3. Install the V7.1 server code on the new system.

4. Create the directories for the V7.1 database and logs, and the user ID that will
own the server instance.
5. Start the upgrade wizard to configure the new server and upgrade the V5
database. With the wizard, you complete the following tasks:
a. On the original system, prepare the V5 database.
b. On the original system, extract the V5 database to external media.
c. On the new system, create and format an empty database to receive the
data.
d. On the new system, insert the data from the media to which it was
extracted.
e. Configure the new system for database backup.
6. Complete the post-installation tasks, including backing up the database and
verifying the database contents.

Upgrading the server manually by using utilities

To upgrade the server manually, you must install the upgrade utilities on the V5
system and extract the database. Then, install the V7.1 server and complete manual
steps to move the data into the V7.1 database.

84 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Upgrade to V7 on a new system, media method

Upgrade using the command line and upgrade utilities

1. Preparation tasks. Back up the V5 5. Install the V7 server.

database.

6. Create the directories and the user ID

for the V7 server.

2. Install
system.
DSMUPGRD utilities on the V5

7. Create and format an empty database.

Run db2icrt and the DSMSERV
3. Prepare the V5 database. Run the
DSMUPGRD PREPAREDB utility.
LOADFORMAT utility.

4. Extract the V5 database to external 8. Insert data from media into the new
database. Run the DSMSERV
media. Run the DSMUPGRD INSERTDB utility.
EXTRACTDB utility.

9. Configure the system for a database backup.

10. Complete postinstallation steps.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager
server server

Figure 6. Scenario 3

The following steps are a summary of the procedure for this scenario. If this
scenario matches your environment, see the details for the procedure: Chapter 6,
“Scenario 3: New system, media method,” on page 177.

Chapter 3. Upgrade scenarios overview 85

Upgrading the server from V5 to V7.1

Procedure
1. Complete all preparation tasks on the original system. Preparation includes
performing a database backup.
2. Install the DSMUPGRD utilities package on the original system. The utilities
package must be installed whether you are using the upgrade wizard or are
upgrading the server manually by using utilities.
3. On the original system, prepare the V5 database by using the DSMUPGRD
PREPAREDB utility.
4. On the original system, extract the V5 database to external media by using the
DSMUPGRD EXTRACTDB utility.
5. Install the V7.1 server code on the new system.
6. Create the directories for the V7.1 database and logs, and the user ID that will
own the server instance.
7. On the new system, create and format an empty database to receive the data.
The database is created with the db2icrt command. The database is formatted
by using the DSMSERV LOADFORMAT utility.
8. On the new system, insert the data from the media to which it was extracted.
You must have the manifest file that was created as part of the extraction
process. Use the DSMSERV INSERTDB utility.
9. Configure the system for database backup.
10. Complete the post-installation tasks, including backing up the database and
verifying the database contents.

Scenario 4 for upgrading the server: New system, network method

In this scenario, some upgrade tasks are completed on the original system and
some on the new system. The data is extracted from the original server database
and sent over the network connection to be inserted into the new server database.

You can use the wizard, or upgrade the server manually by using the utilities. The
wizard offers a guided approach to the upgrade of a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Related concepts:
“Comparison of upgrading on an existing system and a new system” on page 13
“Comparison of methods for moving data to the V7.1 database” on page 15
Related tasks:
Chapter 7, “Scenario 4: New system, network method,” on page 225

Upgrading the server by using the wizard

To upgrade the server by using the wizard, you must install the upgrade utilities
and the V7.1 server. Then, create the directories and user ID for the 7.1 server and
start the upgrade wizard.

86 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Upgrade to V7 on a new system, network method

Upgrade using the upgrade wizard

3. Install the V7 server.

4. Create the directories and the user

ID for the V7 server.

1. Preparation
database.
tasks. Back up the V5

5. Start the upgrade wizard. Use

the wizard to configure the V7
server and upgrade the V5
2. Install DSMUPGRD utilities on the
V5 system. database.

6. Complete postinstallation steps.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager
server server

Figure 7. Scenario 4

The following steps are a summary of the procedure for this scenario. If this
scenario matches your environment, see the details for the procedure: Chapter 7,
“Scenario 4: New system, network method,” on page 225.

Procedure
1. Complete all preparation tasks on the original system. Preparation includes
performing a database backup.
2. Install the DSMUPGRD utilities package on the original system. The utilities
package must be installed whether you are using the upgrade wizard or are
upgrading the server manually by using utilities.
3. Install the V7.1 server code on the new system.

Chapter 3. Upgrade scenarios overview 87

Upgrading the server from V5 to V7.1

4. Create the directories for the V7.1 database and logs, and the user ID that will
own the server instance.
5. Start the upgrade wizard to configure the new server and upgrade the V5
database. With the wizard, you complete the following tasks:
a. On the original system, prepare the V5 database.
b. On the new system, create and format an empty database to receive the
data.
c. Move the data from the V5 database to the V7.1 database.
d. Configure the new system for database backup.
6. Complete the post-installation tasks, including backing up the database and
verifying the database contents.

Upgrading the server manually by using utilities

To upgrade the server manually, you must install the upgrade utilities on the V5
system and extract the database. Then, install the V7.1 server and complete manual
steps to move the data into the V7.1 database.

88 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Upgrade to V7 on a new system, network method

Upgrade using the command line and upgrade utilities

4. Install the V7 server.

1. Preparation tasks. Back up the V5 database.
5. Create the directories and the user ID for
the V7 server.

2. Install DSMUPGRD utilities on the V5 system.

6. Create and format an empty database.
Run db2icrt and the DSMSERV
LOADFORMAT utility.

3. Prepare the V5 database. Run the

DSMUPGRD PREPAREDB utility.

7. Start the insertion for the new server. Run

the DSMSERV INSERTDB utility.

8. Start the extraction process. Run the

DSMUPGRD EXTRACTDB utility.
9. Configure the system for a database backup.

10. Complete postinstallation steps.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager
server server

Figure 8. Scenario 4

The following steps are a summary of the procedure for this scenario. If this
scenario matches your environment, see the details for the procedure: Chapter 7,
“Scenario 4: New system, network method,” on page 225.

Chapter 3. Upgrade scenarios overview 89

Upgrading the server from V5 to V7.1

Procedure
1. Complete all preparation tasks on the original system. Preparation includes
performing a database backup.
2. Install the DSMUPGRD utilities package on the original system. The utilities
package must be installed whether you are using the upgrade wizard or are
upgrading the server manually by using utilities.
3. On the original system, prepare the V5 database by using the DSMUPGRD
PREPAREDB utility.
4. Install the V7.1 server code on the new system.
5. Create the directories for the V7.1 database and logs, and the user ID that will
own the server instance.
6. On the new system, create and format an empty database to receive the data.
The database is created with the db2icrt command. The database is formatted
by using the DSMSERV LOADFORMAT utility.
7. On the new system, start the insertion process for the new server. Use the
DSMSERV INSERTDB utility.
8. On the original system, start the extraction process for the V5 database by
using the DSMUPGRD EXTRACTDB utility.
9. Configure the system for database backup.
10. Complete the post-installation tasks, including backing up the database and
verifying the database contents.

90 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 4. Scenario 1: Same system, media method
Use this procedure if you are upgrading the Tivoli Storage Manager server on the
same system as the V5 server, and you are using the media method to move the
data.

Procedure

The procedure for upgrading the server includes the following tasks:
1. “Scenario 1: Preparing for the upgrade”
2. “Scenario 1: Installing the upgrade utilities” on page 100
3. “Scenario 1: Preparing the database of a V5 server for upgrade” on page 107
4. “Scenario 1: Uninstalling the V5 program before installing V7.1” on page 109
5. “Scenario 1: Installing the V7.1 server” on page 111
6. “Scenario 1: Creating the directories and the user ID for the upgraded server
instance” on page 115
7. Upgrading the server, by using one of the following methods:
v “Scenario 1: Upgrading the server by using the upgrade wizard” on page 118
v “Scenario 1: Upgrading the server manually by using utilities” on page 120
8. The following tasks are completed after the upgrade:
a. “Verifying access to storage pools on disk” on page 323
b. “Setting up Solaris services for the server instance” on page 324
c. “Configuring server options for server database maintenance” on page 324
d. “Starting the server instance after the upgrade” on page 325
e. “Registering licenses” on page 334
f. “Backing up the database after upgrading the server” on page 335
g. “Verifying the upgraded server” on page 336
h. “Changing the host name for the Tivoli Storage Manager server” on page
336
i. “Updating automation” on page 338
j. “Monitoring the upgraded server” on page 339
k. “Removing GSKit Version 7 after upgrading to Tivoli Storage Manager
V7.1” on page 340

Scenario 1: Preparing for the upgrade

Prepare for the upgrade by checking requirements, preparing the space that is
required, backing up the server, and modifying certain server settings.

About this task

Follow the preparation steps carefully to protect your server and its data.

Important: It is possible, after the upgrade to V7.1 is complete, that conditions

might cause the need to temporarily revert to the previous version of the server.
Successfully reverting to the previous version of the server is possible only if you

© Copyright IBM Corp. 2009, 2013 91

Upgrading the server from V5 to V7.1

have completed all preparation steps. To understand why it is important to

complete all preparation steps, review the procedure for reverting an upgraded
server to its previous version.

Procedure
1. “Scenario 1: Checking the prerequisites for the upgrade”
2. “Scenario 1: Preparing space for the upgrade process” on page 95
3. “Scenario 1: Modifying the server before the upgrade” on page 96
4. “Scenario 1: Disabling sessions” on page 97
5. “Scenario 1: Backing up storage pools and the server database” on page 98
6. “Scenario 1: Moving the NODELOCK file” on page 98
7. “Scenario 1: Backing up configuration information” on page 99
8. “Scenario 1: Creating a summary of database contents” on page 99
9. “Scenario 1: Stopping the server before installing the upgrade” on page 100
Related tasks:
“Reverting from V7.1 to the previous V5 server version” on page 351

Scenario 1: Checking the prerequisites for the upgrade

Check your system against requirements for the server.

Before you begin

Requirement: If you are upgrading the Tivoli Storage Manager server on the same
system, the system must meet the minimum requirements for both the V5 and V7.1
servers.

Procedure
1. Ensure that the server that you plan to upgrade is at the V5.5 release level, and
that the latest interim fix is installed. For example, if the server is at V5.5.6,
install the latest interim fix for V5.5.6. Take the following actions:
a. Select the appropriate server level. For detailed guidelines, see
“Determining the appropriate level for a V5 server before an upgrade” on
page 36. If the server is at an appropriate level, no action is required.
b. If the server is not at an appropriate level, download the appropriate server
fix pack and the latest interim fix from the FTP downloads site at
ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server/. Locate the appropriate version of Tivoli Storage
Manager and install it.
2. Ensure that the system where the V5 server is located meets the minimum
requirements. Review the information in “Hardware and software requirements
for the V5 server system that is being upgraded” on page 17 to determine
whether you must update your system before you continue.
3. Ensure that the system where you plan to install the V7.1 server meets
requirements for the operating system type and level. For the latest information
about system requirements, see Tivoli Storage Manager Supported Operating
Systems (http://www.ibm.com/support/docview.wss?uid=swg21243309).
If you are upgrading Tivoli Storage Manager to a different operating system, a
limited set of migration paths is available. For instructions about migrating a
server that is running on a z/OS operating system, see Part 3, “Migrating Tivoli
Storage Manager V5 servers on z/OS systems to V7.1 on AIX or Linux on
System z,” on page 437. For instructions about migrating a server that is

92 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

running on an AIX, HP-UX, or Solaris operating system, see Part 2, “Migrating

Tivoli Storage Manager V5 servers on AIX, HP-UX, or Solaris systems to V7.1
on Linux,” on page 355.
Some platforms that were supported for earlier versions of the server are not
supported for V7.1. If the server that you want to upgrade is running on one of
these platforms, you cannot upgrade your server to V7.1 on the same platform.
You must install your V7.1 server on a system that is a specific supported
platform, depending on the original platform. For required platforms, see the
following table.
Table 31. Required platforms for upgrading from V5 to V7.1
Platform for V5 server Required platform for upgrade to V7.1
HP-UX running on a PA-RISC system HP-UX running on an Intel Itanium system
Linux running on an Itanium system (IA64) Linux running on an x86_64 system
Linux running on an x86_32 system Linux running on an x86_64 system
Solaris running on an x86_64 system Linux running on an x86_64 system
Windows running on an Itanium system Windows running on an x86_64 system
(IA64)

If you are upgrading from Tivoli Storage Manager V5 to V7.1 on a new system,
restrictions apply. Ensure that you install the V7.1 server in a compatible
hardware and software environment, as described in the following table.
Table 32. Requirements for upgrading from V5 to V7.1 on a new system
V5 server V7.1 server Comments
AIX running on an IBM AIX running on an IBM
POWER system POWER system
HP-UX running on an HP-UX running on an
Itanium system Itanium system
HP-UX running on a HP-UX running on an HP-UX running on PA-RISC
PA-RISC system Itanium system is not supported for V7.1
servers.
Linux running on an IBM Linux running on an IBM
POWER system POWER system
Linux running on an Itanium Linux running on an x86_64 Linux running on Itanium is
system (IA64) system not supported for V7.1
servers.
Linux running on an x86_32 Linux running on an x86_64 Linux running on x86_32 is
system system not supported for V7.1
servers.
Linux on System z Linux on System z

Chapter 4. Scenario 1: Same system, media method 93

Upgrading the server from V5 to V7.1

Table 32. Requirements for upgrading from V5 to V7.1 on a new system (continued)
V5 server V7.1 server Comments
Solaris running on an x86_64 Operating system depends A V7.1 server cannot be
system on the migration method installed on a Solaris x86_64
system. However, you can
migrate a V5 server that is
running on a Solaris x86_64
operating system to V7.1 on
a Linux x86_64 operating
system. For instructions, see
Part 2, “Migrating Tivoli
Storage Manager V5 servers
on AIX, HP-UX, or Solaris
systems to V7.1 on Linux,”
on page 355.

Alternatively, you can

migrate the Solaris x86_64
system by installing a V7.1
server on any operating
system that is supported for
V7.1. Then, use Tivoli
Storage Manager server
EXPORT and IMPORT
commands to move the
server from the V5 source
system to the V7.1 target
system.
Windows running on an Windows running on an Windows running on
Itanium system (IA64) x86_64 system Itanium is not supported for
V7.1 servers.
Windows running on an Windows running on an Windows running on x86_32
x86_32 system x86_64 system is not supported for V7.1
servers.
z/OS AIX or Linux on System z See the section on migrating
from V5 on z/OS to V7.1 on
AIX or Linux on System z.

4. Verify that the system memory meets the server requirements. If you plan to
run multiple instances of the V7.1 server on the system, each instance requires
the memory that is listed for one server. Multiply the memory for one server by
the number of instances that are planned for the system.
For specific information about memory requirements, see the section for your
operating system:
Table 33. Memory requirements for the V7.1 system
Operating system Memory requirements
AIX “Server requirements on AIX systems” on
page 21
HP-UX “Server requirements on HP-UX systems” on
page 24
Linux “Server requirements on Linux systems” on
page 26
Solaris “Server requirements on Solaris systems” on
page 31

94 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 33. Memory requirements for the V7.1 system (continued)

Operating system Memory requirements
Windows “Server requirements on Microsoft Windows
systems” on page 33

5. Ensure that the system has enough disk storage for the database and recovery
logs. Review the planning information for requirements and guidance.
You can take one of two approaches:
v Ensure that the system has enough disk storage for storing database and
recovery logs for both the original server and the new V7.1 server. Both are
stored on disk storage during the upgrade process.
v After you back up the V5 database and extract the data to media, reconfigure
the disk subsystem that is used for the database storage. Then, insert the
data to the new database from the media. You must take this approach if you
do not have enough disk space for both servers.
If you are adding new hardware for the server, such as new disk storage for
the database, ensure that the hardware is installed and running.
Related concepts:
“Hardware and software requirements for upgrading to the V7.1 server” on page
17

Scenario 1: Preparing space for the upgrade process

Determine the amount and type of space that is required for the upgrade process
before beginning the process.

Procedure
1. Verify that the system has the amount of space that was estimated in the
planning step. Use the planning worksheet that you completed with your
information. See “Worksheet for planning space for the V7.1 server” on page
42.
2. Ensure that you have space available for storing the database and the manifest
file that the extraction process creates.
a. Identify the device class to which you will extract the original database. The
definition must exist in the server database, not just in the device
configuration file. View information about devices classes by issuing the
command:
query devclass format=detailed
The device class must be a sequential device class that has volumes or space
available. Define a new device class if necessary. The device class type
cannot be NAS or CENTERA.

Important: You must confirm now that the definition that is in the server
database for the device class is correct. After you prepare the database for
upgrade (by completing the Prepare Database phase in the upgrade wizard,
or by using the DSMUPGRD PREPAREDB utility), you cannot update this device
class definition. For example, check the path for a FILE device class. If you
copied the original server to a different system to extract the data, the path
might be different on the current system.
b. Ensure that space or volumes are available in the selected device class. The
amount of space that you need is about the same as the current size of the
original database.

Chapter 4. Scenario 1: Same system, media method 95

Upgrading the server from V5 to V7.1

For example, if the device class is FILE, ensure that the directory has
sufficient space for your environment. If the device class is TAPE, ensure
that sufficient scratch volumes are available for your environment.
Ensure that the instance user ID that you create for the upgraded server has
access permission to the location of the extracted data.
c. Check that the access permissions are correct for the location that you plan
to specify for the manifest file.
The user ID that will run the database preparation and extraction utilities
(DSMUPGRD PREPAREDB and DSMUPGRD EXTRACTDB) must have write access to
this file. This is typically the root user ID.
When the data is later inserted into the V7.1 database, the instance user ID
that you use for the upgraded server must have access permission for the
manifest file.
The manifest file is typically less than 1 KB.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39

Scenario 1: Modifying the server before the upgrade

A command must be run on the server to prevent one type of problem during the
upgrade process. Some modifications to typical server settings can be useful to
prepare for the upgrade.

Procedure
1. From a Tivoli Storage Manager administrative command line, issue the
command:
convert ussfilespace

This command fixes a problem that might exist in older Tivoli Storage Manager
databases. If the problem does not exist in your database, the command is
completed and you might see error ANR2034E. This error can be ignored. For
more information, see Technote 1408895 (http://www.ibm.com/support/
docview.wss?uid=swg21408895). If the problem exists in your database, the
command might take some time to run.

Important: Do not skip this step. If your database has the problem and you do
not run this command now, the DSMUPGRD PREPAREDB utility fails when you run
it. You must then restart the V5 server and run the CONVERT USSFILESPACE
command before you continue the upgrade process.
2. Review the steps for reverting to the earlier version of the server in the section,
“Reverting from V7.1 to the previous V5 server version” on page 351.
If you must revert to the earlier version after the upgrade to V7.1, the results of
the reversion will be better if you understand the steps and prepare for the
possibility now.
3. Make the following adjustments to settings on your server and clients. These
adjustments must be done to make it possible for you to revert to the original
server after the upgrade, if problems occur.
a. For each sequential-access storage pool, set the REUSEDELAY parameter to the
number of days during which you want to be able to revert to the original
server, if necessary.

96 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

For example, if you want to be able to revert to the original server for up to
30 days after the upgrade to V7.1, set the REUSEDELAY parameter to 31 days.
Issue the following administrative command:
update stgpool sequential_access_storage_pool reusedelay=31
b. For each copy storage pool, set the RECLAIM parameter to 100 (meaning
100%). Issue the following administrative command:
update stgpool copy_storage_pool reclaim=100
c. If you typically use a DELETE VOLHISTORY command to delete database
backups, ensure that the command does not delete database backups too
frequently. The interval between backups should be at least the same
number of days that you set for the REUSEDELAY period for sequential-access
storage pools. For example, to delete database backups every 45 days, issue
the following administrative command:
delete volhist type=dbbackup todate=-45
d. For important clients that use the server, verify that the value for the
schedlogretention client option is set to retain the client schedule log for a
sufficient time. Update the option for clients if needed.
The entries in the client schedule log might be useful if the server must
revert to the original version. If the retention period for the schedule log is
too short, the schedule log information might be deleted too soon.
For example, to prune the log every 45 days and save the log entries, add
the following option:
schedlogretention 45 S
AIX HPUX Linux Solaris Add the option to the dsm.sys file
within a server stanza.
Windows Add the option to the client options file, dsm.opt.

Scenario 1: Disabling sessions

In preparation for the upgrade, prevent activity on the server by disabling new
sessions. Cancel any existing sessions.

About this task

The commands in the following procedure are Tivoli Storage Manager

administrative commands.

Procedure
1. Prevent all clients, storage agents, and other servers from starting new sessions
with the server. Use the commands:
disable sessions client
disable sessions server
For more information about these commands and other Tivoli Storage Manager
administrative commands, see the Administrator's Reference.
2. Verify whether any sessions exist, and notify the users that the server is going
to be stopped. To check for existing sessions, use the command:
query session
3. Cancel sessions that are still running. Use the command:
cancel session all

Chapter 4. Scenario 1: Same system, media method 97

Upgrading the server from V5 to V7.1

Scenario 1: Backing up storage pools and the server database

Immediately before upgrading the server, back up primary storage pools to copy
storage pools, and perform a full database backup.

Before you begin

Back up storage pools and the server database by using Tivoli Storage Manager
administrative commands:

Procedure
1. Back up primary storage pools to copy storage pools by using the BACKUP
STGPOOL command:
backup stgpool primary_pool copy_stg

where primary_pool specifies the primary storage pool and copy_stg specifies the
copy storage pool. If you have been performing regular backups of the storage
pools, this step backs up only the data that was added to the primary storage
pools since they were last backed up.
2. Back up the database. The preferred method is to use a snapshot backup. A
snapshot backup is a full database backup that does not interrupt any
scheduled database backups. Issue the command:
backup db type=dbsnapshot devclass=device_class_name

The device class that you specify must exist and have volumes that are
available to it. For example, to perform a snapshot backup of your database to
the TAPECLASS device class by using scratch volumes, enter:
backup db type=dbsnapshot devclass=tapeclass

To use specific volumes instead of scratch volumes, specify the volume names
in the command.

Tip: Consider making two copies of the backup to protect the backup from
media failures. Ensure that at least one full database backup is available onsite.
If you must restore the database after a failed upgrade, having an onsite
backup database saves time.

Scenario 1: Moving the NODELOCK file

To ensure that licensing information is updated during the upgrade process, move
the NODELOCK file from the server instance directory to another directory.

About this task

The NODELOCK file contains the licensing information from the previous Tivoli
Storage Manager installation. This licensing information is replaced when the
upgrade is complete.

Procedure
1. In the server instance directory of your installation, locate the NODELOCK file.
2. Move the NODELOCK file to another directory. For example, you can save it to a
directory where you are saving configuration files from the previous release.

98 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 1: Backing up configuration information

Before you install the new version, back up critical files and information for each
server instance. Store the files in a safe place, on a different system from the
system that is being upgraded or on offline media, such as a CD. The files are
required after the installation of the new software version is complete. You also
need these files if you must revert to the previous version after the upgrade.

Procedure
1. Back up device configuration information to another directory by using the
following Tivoli Storage Manager administrative command:
backup devconfig filenames=file_name

where file_name specifies the file in which to store device configuration

information.
2. Back up volume history information to another directory by using the
following Tivoli Storage Manager administrative command:
backup volhistory filenames=file_name

where file_name specifies the file in which to store volume history information.
Ensure that the volume history includes information about the database backup
that you completed in the preceding steps. For example, issue the following
command:
query volhistory type=dbsnapshot

Review the query output to verify that the time stamp for the database backup
matches the actual time of the backup.
3. Save copies of the following files, which are in the server instance directory:
v Server options file, typically named dsmserv.opt
v dsmserv.dsk

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.
4. In the server instance directory, look for the accounting log file, dsmaccnt.log.
If the file exists, save a copy.
5. Back up any scripts that were used to complete daily housekeeping for the
server. Examine the scripts for changes that are needed after the upgrade.
6. Store the device configuration file, the volume history file, the server options
file, and the other files in a safe place. Ensure that the files are stored on a
different system from the system that is being upgraded, or on offline media.

Scenario 1: Creating a summary of database contents

Create a summary of the contents of the original database. After the upgrade, you
can use the same commands to compare the results and to confirm that the
database contents are intact.

Procedure

Run commands that give a summary of information about your database contents.
For example, issue commands that summarize the file spaces that are being
protected, and save the results. For a list of commands, see “Sample commands to
run for validation of the database upgrade” on page 546.
Related reference:

Chapter 4. Scenario 1: Same system, media method 99

Upgrading the server from V5 to V7.1

“Sample commands to run for validation of the database upgrade” on page 546

Scenario 1: Stopping the server before installing the upgrade

Stop all server processes and unmount any tapes that are mounted. Then, stop the
server.

Procedure

Use Tivoli Storage Manager administrative commands to stop the server:

1. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the following commands:
query process
cancel process process_number

Allow time for the processes to be stopped. Some processes, such as storage
pool migration, might take some time to stop.
For more information about the QUERY PROCESS and CANCEL PROCESS commands
and other Tivoli Storage Manager administrative commands, see the
Administrator's Reference.
2. After all sessions and processes are stopped, determine whether any tapes are
mounted. Unmount any tapes that are mounted. Use the following commands:
query mount
dismount volume volume_name
3. Stop the server. Use the following command:
halt

Scenario 1: Installing the upgrade utilities

You must install the upgrade utilities on the system. The installation package for
the utilities must be downloaded from a website.

Before you begin

The preferred method is to install the latest available version of the upgrade
utilities. For more information about selecting the version, see “Determining the
appropriate level for a V5 server before an upgrade” on page 36.

Procedure

Use the procedure for your operating system:

v AIX “Scenario 1: Installing the upgrade utilities on AIX systems” on page
101
v HPUX “Scenario 1: Installing the upgrade utilities on HP-UX systems” on
page 102
v Linux “Scenario 1: Installing the upgrade utilities on Linux systems” on page
103
v Solaris “Scenario 1: Installing the upgrade utilities on Oracle Solaris systems”
on page 104
v Windows“Scenario 1: Installing the upgrade utilities on Microsoft Windows
systems” on page 107
Related concepts:

100 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

“DSMUPGRD upgrade utilities” on page 16

Scenario 1: Installing the upgrade utilities on AIX systems

AIX

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The
5.5.x.x number must be the same as or later than the level of the V5
server that you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-AIX.tar.gz
The numbers at the beginning of the package name identify the release
level of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Ensure that the system has the following file sets installed:
xlC.rte 8.0.0.5, or later
gsksa.rte 7.0.4.11
You can use the following commands to check for these file sets:
lslpp -L xlC.rte

lslpp -L gsksa.rte

If needed, you can obtain the gsksa.rte file set from any of the regular V5.5
maintenance packages for the AIX server. The maintenance packages are
available on the FTP downloads site: ftp://public.dhe.ibm.com/storage/tivoli-
storage-management/maintenance/server/v5r5/AIX/
4. Extract the contents of the upgrade utilities package. If you downloaded a
language package, also extract the contents of that package.
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Access the System Management Interface Tool (SMIT).
a. Enter smitty install_update
b. Select Install and Update Software > Install and Update from ALL
Available Software.
7. Select the INPUT device. Specify the directory location of the upgrade utilities
package on the system.

Chapter 4. Scenario 1: Same system, media method 101

Upgrading the server from V5 to V7.1

8. Select Software to Install. Press F4 or Esc+4 for the list of available file sets in
the directory.
9. Select the file sets for the upgrade utilities, the device driver, and optionally
the language package. The file set for the upgrade utilities is
tivoli.tsmupg.server. Optional language packages include messages for
languages other than US English.
10. Set COMMIT software updates to Yes. Press F4 or Esc+4.
11. Set SAVE replaced files to No.
12. Ensure that the default settings for the options in the window for all the
selected file sets show success.
13. Press Enter, and respond to the ARE YOU SURE? question by pressing Enter
again. The installation begins.
14. When the installation is complete, exit the SMIT program.
15. Optional: If you installed a language package, ensure that the locale
environment variable is set to use it. Enter the following command to set the
locale environment variable for messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
16. After the upgrade utilities are installed, continue at “Scenario 1: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 106.

Scenario 1: Installing the upgrade utilities on HP-UX systems

HPUX

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.gz
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.

102 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

d. Optional: To install messages in a language other than English, open the

LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
gzip -dc package_name.tar.gz | tar -xvf -
4. Navigate to the directory that corresponds to the processor architecture of the
operating system.
5. Install the upgrade utilities and the device driver. Use the source argument (-s)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
swinstall -s /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin.

6. Optional: Install the language package.
a. Extract the contents of the package.
gzip -d package_name.img.gz
b. Install the package. For example, if the directory is /tmp/TSM, issue the
command:
swinstall -s /tmp/TSM/package_name.img package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Scenario 1: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 106.

Scenario 1: Installing the upgrade utilities on Linux systems

Linux

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.

Chapter 4. Scenario 1: Same system, media method 103

Upgrading the server from V5 to V7.1

c. Open the directory for your operating system and download the package.
The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.bz2
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the commands:
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
4. Navigate to the directory that corresponds to the processor architecture of the
operating system, for example, x86_64.
5. Install the upgrade utilities and the device driver. Use the following command:
rpm -ivh package_name.rpm
The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by
default.
6. Optional: Install the language package.
a. Extract the contents of the downloaded package.
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
b. Install the package for the language that you want to use.
rpm -ivh package_name.rpm
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Scenario 1: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 106.

Scenario 1: Installing the upgrade utilities on Oracle Solaris

systems
Solaris

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

104 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

About this task

Restriction: Do not install the utilities in the installation directory of the server that
must be upgraded. Install the utilities package in its own directory.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.Z
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Change to the directory where the upgrade utilities package was downloaded.
4. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
uncompress -c package_name.tar.Z | tar -xvf -
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Install the upgrade utilities and the device driver. Use the source argument (-d)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
pkgadd -d . /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by

default.
7. Optional: Install the language package.
a. Extract the contents of the downloaded package.
uncompress package_name.pkg.Z
b. Install the package for the language that you want to use. Use the source
argument (-d) to specify the directory where the package was extracted. For
example, if the directory is /tmp/TSM, issue the command:
pkgadd -d /tmp/TSM package_name.pkg package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.

Chapter 4. Scenario 1: Same system, media method 105

Upgrading the server from V5 to V7.1

v The upgrade utilities support the locale.

v The language package that you installed for the upgrade utilities matches
the locale.
8. After the upgrade utilities are installed, continue at “Scenario 1: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems.”

Scenario 1: Setting environment variables for the upgrade

utilities on AIX, HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

After installing the upgrade utility package, you must set environment variables in
the shell from which you will run the utilities. An environment variable describes
the operating environment of a process, such as the home directory or terminal in
use.

About this task

The DSMSERV_DIR variable specifies the installed location of the upgrade utilities. By
default, the location is the following directory:

AIX

/usr/tivoli/tsm/upgrade/bin

HPUX Linux Solaris

/opt/tivoli/tsm/upgrade/bin

Procedure

Use the appropriate command for your system to set the environment variable for
running the utilities. If the shell is in the ksh or bash family, enter the following
command to set the DSMSERV_DIR variable:
export DSMSERV_DIR=upgrade_utilities_directory

If your shell is in the csh family, use the following command:

setenv DSMSERV_DIR upgrade_utilities_directory

where upgrade_utilities_directory is the directory where the upgrade utilities are

installed.

What to do next

After you set the environment variables, continue at “Scenario 1: Preparing the
database of a V5 server for upgrade” on page 107.

106 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 1: Installing the upgrade utilities on Microsoft

Windows systems
Windows

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/WIN
b. Open the 5.5.x.x directory. The 5.5.x.x number must be the same as or
later than the level of the V5 server that you are upgrading.
c. Select the package and download it to a convenient location on the server
system. The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-Windows.exe
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, install the
language package that your installation requires.
2. Log on with an administrator ID.
3. Run the executable package for the upgrade utilities.
The default location for the installation of the utilities is based on the location
where the V5 server was last installed. For example, if the V5 server was
installed using the default path, C:\Program Files\Tivoli\TSM\server, the
upgrade utilities are installed in C:\Program Files\Tivoli\TSM\upgrade.

What to do next

After the upgrade utilities are installed, continue at “Scenario 1: Preparing the
database of a V5 server for upgrade.”

Tip: When you use the upgrade utilities, if you have multiple servers running on
the system, you must use the -k option to specify the name of the Windows
registry key from which to retrieve information about the server being upgraded.
The default value for the option is SERVER1.

Scenario 1: Preparing the database of a V5 server for upgrade

Before you extract the data from the database, you must prepare the server
database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a
single system, you must repeat this task for each server.

Procedure
1. Ensure that you have completed all preparation steps.
2. Log in using the root user ID on the system that has the original server. Log on
with the administrator ID on a Windows system.
3. Change to the instance directory for the server that you are upgrading. The
instance directory is the directory that contains the files such as dsmserv.dsk for
the server.

Chapter 4. Scenario 1: Same system, media method 107

Upgrading the server from V5 to V7.1

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.
4. Prepare the database. Direct the output of the process to a file for monitoring.
AIX
From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

HPUX Linux Solaris

From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

Windows
From the instance directory for the server that you are upgrading, issue
the following command to run the process and direct the output to the
file called prepare.out:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd"
preparedb 1>>prepare.out 2>&1

If multiple servers exist on the system, issue the command from the
instance directory for the server that you want to prepare. Specify the
registry key for that server. For example, if the server is SERVER2:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" -k server2
preparedb 1>>prepare.out 2>&1
5. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation. From the instance directory for the
server that you are upgrading, issue the following command to monitor the
process:
tail -f prepare.out

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
6. Ensure that the prepare operation is completed successfully before you continue
to the next step. If the prepare operation fails, you might need to restart the V5
server to fix the problem and run the prepare operation again. If the server that
is being upgraded is a V5.3 or V5.4 server, you might need to restore the
database by using a backup before you can restart the server to correct the
problem.
Related reference:
“DSMUPGRD PREPAREDB (Prepare a V5 database for upgrade)” on page 523

108 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 1: Uninstalling the V5 program before installing V7.1

For best results when you are upgrading the server to V7.1 on the same system
where the V5 server is located, uninstall the V5 server program. Then, install the
V7.1 server program.

Procedure

Use the procedure for your operating system:

v AIX “Scenario 1: Uninstalling the V5 program on AIX systems”
v HPUX “Scenario 1: Uninstalling the V5 program on HP-UX systems”
v Linux “Scenario 1: Uninstalling the V5 program on Linux systems” on page
110
v Solaris “Scenario 1: Uninstalling the V5 program on Oracle Solaris systems”
on page 110
v Windows “Scenario 1: Uninstalling the V5 program on Microsoft Windows
systems” on page 111

Scenario 1: Uninstalling the V5 program on AIX systems

AIX

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
v For a V5.4 or V5.5 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license.aix5.rte64
/usr/sbin/installp -ug tivoli.tsm.devices.aix5.rte
/usr/sbin/installp -ug tivoli.tsm.server.aix5.rte64
v For a V5.3 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license
/usr/sbin/installp -ug tivoli.tsm.devices
/usr/sbin/installp -ug tivoli.tsm.server

What to do next

After the V5 server program is uninstalled, continue at “Scenario 1: Installing the

V7.1 server” on page 111.

Scenario 1: Uninstalling the V5 program on HP-UX systems

HPUX

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
v For a V5.4 or V5.5 server, issue the following commands:
swremove TIVsmS64IA.server
swremove TIVsmS64IA.license
swremove TIVsmDD64_IA11_23.tsmscsi

Chapter 4. Scenario 1: Same system, media method 109

Upgrading the server from V5 to V7.1

v For a V5.3 server, issue the following commands:

swremove TIVsmS64.server
swremove TIVsmS64.license
swremove TIVsmDD64_HP11_11.tsmscsi

What to do next

After the V5 server program is uninstalled, continue at “Scenario 1: Installing the

V7.1 server” on page 111.

Scenario 1: Uninstalling the V5 program on Linux systems

Linux

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
1. To determine the Tivoli Storage Manager packages that are installed, issue the
following command:
rpm -qa | grep TIVsm
2. Remove the server, server license, and device driver packages. Issue the
following commands:
rpm -e TIVsm-server
rpm -e TIVsm-license
rpm -e TIVsm-tsmscsi

What to do next

After the V5 server program is uninstalled, continue at “Scenario 1: Installing the

V7.1 server” on page 111.

Scenario 1: Uninstalling the V5 program on Oracle Solaris

systems
Solaris

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure

Issue the following commands:

/usr/sbin/pkgrm TIVsmS
/usr/sbin/pkgrm TIVsmSlic
/usr/sbin/pkgrm TIVsmSdev

What to do next

After the V5 server program is uninstalled, continue at “Scenario 1: Installing the

V7.1 server” on page 111.

110 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 1: Uninstalling the V5 program on Microsoft

Windows systems
Windows

Uninstall the V5 server and server license. Do not remove the database, recovery
log, or any other related files or directories, such as the server options file.

About this task

Do not remove registry entries for the server.

Procedure
1. Click Start > Control Panel > Add or Remove Programs.
2. Select the Tivoli Storage Manager server component, and click Remove.
For this step and all remaining steps, if you see any messages that suggest that
you restart the system, ignore them until the selected Tivoli Storage Manager
component is removed.
3. Select the Tivoli Storage Manager license, and click Remove.
4. Determine whether the device driver must be uninstalled.
Do not uninstall the device driver if the following conditions are true:
v You are migrating the server database to a tape device.
v The tape drive or tape changer uses the Tivoli Storage Manager device
driver.
If the conditions are not true, uninstall the device driver.
5. To uninstall the device driver, select the Tivoli Storage Manager device driver,
and click Remove.

What to do next

After the V5 server program is uninstalled, continue at “Scenario 1: Installing the

V7.1 server.”

Scenario 1: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

Take the following actions:

v Ensure that you have completed all upgrade preparation steps, including the
database backup. The server that you are upgrading will not be available until
after the installation and upgrade steps are completed.
v Ensure that you retain the installation media from the V5 base release of the
installed server. If you installed Tivoli Storage Manager from a DVD, ensure that
the DVD is available. If you installed Tivoli Storage Manager from a
downloaded package, ensure that the downloaded files are available. If the
upgrade fails, and the server license module is uninstalled, the installation
media from the server base release are required to reinstall the license.

Chapter 4. Scenario 1: Same system, media method 111

Upgrading the server from V5 to V7.1

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

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

Procedure
1. Log on to the system.
AIX HPUX Linux Solaris Log in by using the root user ID.
Log on as an administrator. You must be logged on to the system
Windows
with the administrative user ID that was used to install the V5 server.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
AIX HPUX Linux Solaris

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

112 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

AIX

7.1.0.000-TIV-TSMSRV-AIX.bin

HPUX

7.1.0.000-TIV-TSMSRV-HP-UX.bin

Linux

7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin
7.1.0.000-TIV-TSMSRV-Linuxs390x.bin

Solaris

7.1.0.000-TIV-TSMSRV-SolarisSPARC.bin

In the examples, 7.1.0.000 represents the product release level.

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

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

Windows

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035121
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035636
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035638
b. Change to the directory where you placed the executable file.
In the next step, the files are extracted to the current directory. The
path must contain no more than 128 characters. Ensure that you
extract the installation files to an empty directory. Do not extract to
a directory that contains previously extracted files, or any other
files.
c. To extract the installation files, double-click the executable file:
package_name.exe
where package_name is like this example:
7.1.0.000-TIV-TSMSRV-Windows.exe
The package is large. Therefore, the extraction takes some time.
4. AIX HPUX Solaris To ensure that the Tivoli Storage Manager
wizards work correctly, verify that the following command is enabled:
AIX lsuser
HPUX Solaris logins
By default, the command is enabled.
5. If you plan to install the server by using the graphical wizard of IBM
Installation Manager, review the following information and verify that your
system meets the requirements:

Chapter 4. Scenario 1: Same system, media method 113

Upgrading the server from V5 to V7.1

v AIX Verify that all required RPM files are installed. For a list of
required RPM files and instructions about installing RPM files, see the
section about installing Tivoli Storage Manager by using the installation
wizard in the Installation Guide.
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the
installation wizard.
v Windows The user ID that you use during installation must be a user with
local Administrator authority.
v Solaris Ensure that the LD_LIBRARY_PATH_64 environment variable is not
set.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
AIX HPUX Linux Solaris

./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

Windows

install.bat -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

6. If you use the installation wizard, complete the following steps to begin the
installation:

Option Description
Installing from a downloaded package file: 1. Change to the directory where you
downloaded the package file.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat

Installing from DVD media: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat
Windows Or, in the directory where the
installation files were extracted,
double-click the install.bat file.

114 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

7. If you are installing the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
8. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
9. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
10. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
11. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.
12. HPUX Linux Solaris To prevent server failures during interaction
with DB2, tune the kernel parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
13. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
14. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.
Related concepts:
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555

Scenario 1: Creating the directories and the user ID for the upgraded
server instance
Create the directories that the server instance needs for database and recovery logs,
and create the user ID that will own the server instance.

Before you begin

Review the information about planning space for the server before you complete
this task. See “Worksheet for planning space for the V7.1 server” on page 42.

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

Create a user ID and group that will be the owner of the Tivoli Storage
Manager server instance.
Chapter 4. Scenario 1: Same system, media method 115
Upgrading the server from V5 to V7.1

a. Create the user ID and group.

Restriction: In the user ID, only lowercase letters (a-z), numerals

(0-9), and the underscore character (_) can be used. The user ID and
group name must comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a
numeral.
v The user ID and group name cannot be user, admin, guest, public,
local, or any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The
following examples show how to create this user ID and group by
using operating system commands:
AIX

# mkgroup id=1001 tsmsrvrs

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

HPUX

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

Linux

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

Solaris

# groupadd tsmsrvrs
# useradd -d /export/home/tsminst1 -m -g tsmsrvrs
-s /bin/ksh tsminst1
# passwd tsminst1
b. Log out and then log in to your system by using the new user ID
and password. Use an interactive login program, such as telnet, so
that you are prompted for the password and can change it if
necessary.
c. If a configuration profile does not exist for the user ID, create the
file. For example, create a .profile file if you are using the Korn
shell (ksh).
Windows
Identify the user account that will own the Tivoli Storage Manager
server instance. When the server is started as a Windows service, this is
the account that the service will log on to. The user account must have
administrative authority on the system. One user account can own
more than one server instance.
You can create a user account, or use an existing account.
If you have multiple servers on one system and want to run each
server with a different user account, create a user account in this step.
a. Create the user ID.

116 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Restriction: The user ID can contain only lowercase letters (a-z),

numerals (0-9), and the underscore character (_). The user ID must
be 30 characters or less, and cannot start with ibm, sql, sys, or a
numeral. The user ID and group name cannot be user, admin, guest,
public, local, or any SQL reserved word.
Use the following command to create the user ID:
net user user_ID * /add

You are prompted to create and verify a password for the new user
ID.
b. Issue the following operating system commands to add the new
user ID to the Administrators groups:
net localgroup Administrators user_ID /add
net localgroup DB2ADMNS user_ID /add
c. Log in to your system, by using the new user ID and password.
d. For all directories that were created for the server instance, ensure
that the user ID for the server instance has read/write access. The
directories to check include the instance directory and all database
and log directories.
2. Create the directories that the server requires. Ensure that you are logged in
under the new user ID that you created.
You need a unique, empty directory for each item in the following table. Create
the database directories, the active log directory, and the archive log directory
on different physical volumes. For space requirements, see “Worksheet for
planning space for the V7.1 server” on page 42.
AIX HPUX Linux Solaris

Table 34. Worksheet for creating required directories

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

Windows

Chapter 4. Scenario 1: Same system, media method 117

Upgrading the server from V5 to V7.1

Table 35. Worksheet for creating required directories

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

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
3. Create additional logical volumes and mount the volumes on the directories
that were created in the previous step.

What to do next

Continue the upgrade process by using one of the following topics:

“Scenario 1: Upgrading the server by using the upgrade wizard”
“Scenario 1: Upgrading the server manually by using utilities” on page 120
Related tasks:
“Planning space for the upgrade process and the upgraded server” on page 37
Related reference:
“Server naming best practices” on page 70

Scenario 1: Upgrading the server by using the upgrade wizard

The wizard offers a guided approach to upgrading a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Start the wizard on the system where you installed the V7.1 server program.

Before you begin

You must complete all preceding steps to prepare for the upgrade, to install the
upgrade utilities, to install the V7.1 server program, and to create the directories
and user ID for the server instance.

118 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Procedure
1. Ensure that the following requirements are met.
AIX HPUX Linux Solaris

v The system must have the X Window client. You must also be
running an X Window server on your desktop.
v The system must have one of the following protocols enabled. Ensure
that the port that the protocol uses is not blocked by a firewall.
– Secure Shell (SSH). Ensure that the port is set to the default value,
22. Also, ensure that the SSH daemon service has access rights for
connecting to the system by using localhost.
– Remote shell (rsh).
– Remote Execution Protocol (REXEC).
v You must be able to log in to the system with the user ID that you
created for the server instance, by using the SSH, rsh, or REXEC
protocol. When you use the wizard, you must provide this user ID
and password to access that system.
Windows

v The system where you installed the V7.1 server program must have
the Windows server message block (SMB) protocol enabled. SMB is
the interface that is used by File and Print Sharing (also known as
CIFS). To use the SMB protocol, you must ensure that File and Print
Sharing is enabled, and that port 445 is not blocked by your firewall.
v If the V5 server is on a different system than the V7.1 server, that
system must also have SMB enabled.
v You must be able to log on to the system that has SMB enabled by
using either the user ID that you created for the server instance, or
another user ID that exists on the system. When you use the wizard,
you must provide the user ID and password to access the system.
2. Windows If the system is running on Windows Server 2008, complete the
following steps to disable User Account Control:
a. Ensure that the Remote Registry in Windows Services is started, and ports
445, 137, and 139 are unblocked in the firewall.
b. Configure both the framework server and the targets as members of a
Windows domain. Use a user account in that domain, or in a trusted
domain, when you connect to the target.
c. Connect to the target workstation by enabling and using the built-in
administrator account. To enable the built-in administrator account, click
Control Panel > Administrative Tools > Local Security Policy > Security
Settings > Local Policies > Security Options. Double-click the Accounts:
Administrator account status section. Select Enable and click OK.
d. Click Control Panel > Administrative Tools > Local Security Policy >
Security Settings > Local Policies > Security Options. Double-click the
User Account Control: Run all administrators in Admin Approval Mode
section. Select Disable and click OK.
3. Start the upgrade wizard, dsmupgdx, from the V7.1 server installation directory.
AIX HPUX Linux Solaris
Log in using the root user ID. Issue the command:
/opt/tivoli/tsm/server/bin/dsmupgdx

Chapter 4. Scenario 1: Same system, media method 119

Upgrading the server from V5 to V7.1

Windows
Open a new Command Prompt window, and issue the command:
"c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe"
4. Follow the instructions to complete the upgrade. The upgrade wizard can be
stopped and restarted, but the server will not be operational until the entire
upgrade process is complete.
In the message display area within the wizard, read all messages that are
displayed for each phase of the upgrade process. Informational messages might
show actions that occurred during the process that are important to you.
Windows If you are moving the server database to a tape device, and the tape
drive or tape changer uses a Tivoli Storage Manager device driver, you might
see a message about a drive or tape library error. In this case, you must
complete Step 5.
5. Windows If you see a message about a drive or tape library error, complete the
following actions:
a. Uninstall the Tivoli Storage Manager V5 device driver by clicking Start >
Control Panel > Add or Remove Programs. Select the Tivoli Storage
Manager device driver, and then click Remove.
b. Install the V7.1 Tivoli Storage Manager device driver.
Follow the instructions for installing a Tivoli Storage Manager device driver
in the Administrator's Guide.
c. Restart the upgrade wizard as described in Step 3 on page 119. Step through
the wizard, but skip the step for extracting the server database.

What to do next

To complete the upgrade, perform the steps described in Chapter 10, “Taking the
first steps after upgrade,” on page 323.

Scenario 1: Upgrading the server manually by using utilities

Use the utilities to upgrade the server by using a command interface.

Before you begin

Complete all preceding steps to prepare for the upgrade. Ensure that you have
installed the upgrade utilities, installed the V7.1 server program, and created the
directories and user ID for the server instance.

Procedure

Complete the following steps:

1. “Scenario 1: Extracting the data to media” on page 121
2. “Scenario 1: Creating and formatting the new database” on page 122
3. “Scenario 1: Loading the extracted data into the new database” on page 126
4. “Scenario 1: Creating a Windows service for the server instance” on page 128
5. “Scenario 1: Configuring the system for database backup” on page 129

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

120 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Related concepts:
“The manifest file for the data extraction to media” on page 531
“DSMUPGRD upgrade utilities” on page 16

Scenario 1: Extracting the data to media

You can extract the data from the original server database to sequential media. The
sequential media can be tape, or disk space that is defined with the FILE device
class.

Procedure
1. Log in using the root user ID on the system that has the original server. Log on
with the administrator ID on a Windows system.
2. Ensure that the device that you want to use to store the extracted data is
available. The server database and the device configuration file must contain a
valid device class definition for the device.
3. From the instance directory for the server that you are upgrading, issue the
command to start the extraction. Direct the output of the process to a file for
monitoring. For example, issue the following command on one line:
AIX

nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

devclass=file manifest=./manifest.txt >extract.out 2>&1 &

HPUX Linux Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

devclass=file manifest=./manifest.txt >extract.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" extractdb

devclass=file manifest=.\manifest.txt 1>>extract.out 2>&1

Tip: Messages that are issued during the extract operation are not saved in the
server activity log. Direct the output of the utility to a file, as shown in the
examples, to record the messages.
4. Monitor the process for errors and warning messages, and for items that you
might need to take action on. A message near the end of the process output
indicates success or failure of the operation:
Success message: ANR1382I EXTRACTDB: Process 1, database extract, has
completed.
Failure message: ANR1396E EXTRACTDB: Process 1, database extract, has
completed with errors.
For example, from the instance directory for the server that you are upgrading,
issue the following command to monitor the process:
tail -f extract.out
The length of time that the process runs depends on the size of the database.
The time will be approximately as much as the time required for a full backup
of the database.

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
Related concepts:
Chapter 4. Scenario 1: Same system, media method 121
Upgrading the server from V5 to V7.1

“The manifest file for the data extraction to media” on page 531
Related tasks:
“Scenario 1: Preparing space for the upgrade process” on page 95
Related reference:
“DSMUPGRD EXTRACTDB (Extract data from a V5 server database)” on page 529

Scenario 1: Creating and formatting the new database

Create the server instance and format files for an empty V7.1 database.

Procedure
1. Log on to the system where you installed the V7.1 program.
AIX HPUX Linux Solaris
Log in by using the root user ID. Verify the following items:
v The home directory for the user, /home/tsminst1, exists. If there is
no home directory, you must create it.
The instance directory stores the following core files that are
generated by the Tivoli Storage Manager server:
– The server options file, dsmserv.opt
– The server key database file, cert.kdb, and the .arm files, which
are used by clients and other servers to import the Secure
Sockets Layer certificates of the server
– Device configuration file, if the DEVCONFIG server option does not
specify a fully qualified name
– Volume history file, if the VOLUMEHISTORY server option does not
specify a fully qualified name
– Volumes for DEVTYPE=FILE storage pools, if the directory for
the device class is not fully specified, or not fully qualified
– User exits
– Trace output, if it is not fully qualified
v A shell configuration file, for example, .profile, exists in the home
directory. The root user and instance user ID must have write
permission to this file. For more information, go to the DB2
Information Center (http://pic.dhe.ibm.com/infocenter/db2luw/
v10r5), and search for information about Linux and UNIX
environment variable settings.
Windows
Log on as an administrator.
2. Create a Tivoli Storage Manager instance by using the db2icrt command.
AIX HPUX Linux Solaris
Enter the following command on one line. For the instance name,
specify the user ID that you created to own the instance:
AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

instance_name instance_name

For example, if the user ID for this instance is tsminst1, use the
following command to create the instance:

122 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

tsminst1 tsminst1

Remember: From this point on, use this new user ID when you
configure the Tivoli Storage Manager server. Log out of the root user
ID, and log in using the user ID that is the instance owner.
Windows
Enter the following command on one line. The user account that you
specify becomes the user ID that owns the V7.1 server; this ID is the
instance user ID.
db2icrt -s ese -u user_account instance_name

For example, if the user account is tsminst1 and the server instance is
Server1, enter the following command:
db2icrt -s ese -u tsminst1 server1

The database service for the server instance logs on to the user
account that is specified in this command.

Use the registry key name of the V5 server as the instance name for
the V7.1 server. You are prompted to enter the password for the user
account.
The instance name that you specify on this db2icrt command is the
name that you later specify with the -k option on the DSMSERV
LOADFORMAT command, when you create and format the database and
recovery log.
3. Log on to the system by using the user ID that owns the V7.1 server instance
(the instance user ID).
4. Copy the configuration files to the instance directory that you created for the
new server. The files are the configuration files that you saved from the
original V5 server:
v Device configuration
v Server options file, which is typically named dsmserv.opt
For example, if you created the instance directory that is shown in the
example in the step to create directories for the V7.1 server, copy the files into
the following directory:
AIX HPUX Linux Solaris /tsminst1
Windows d:\tsm\server1
Ensure that the user ID that owns the V7.1 server (the instance user ID) has
ownership or read/write permission to the files that you copied.
5. Edit the server options file.
a. Remove any options that are not supported for V7.1. For the list of deleted
options, see Table 29 on page 67.
b. Verify that the server options file contains at least one VOLUMEHISTORY
option and at least one DEVCONFIG option. By specifying these options, you
ensure that a volume history file and a device configuration file are
generated and updated automatically. If you must restore the database,
these files are required.

Chapter 4. Scenario 1: Same system, media method 123

Upgrading the server from V5 to V7.1

c. Check whether the server options file includes the TXNGROUPMAX option
with a value, and if it does, what the value is. You might want to change
the current value because the default value for this option changed from
256 to 4096, starting in V6. The increased value can improve the
performance for data movement operations such as storage pool migration
and storage pool backup.
v If the server options file does not include this option, the server
automatically uses the new default value of 4096.
v If the server options file includes a value for this option, the server uses
that specified value. If the specified value is less than 4096, consider
increasing the value, or removing the option so that the new default
value is applied.
6. Change the default path for the database.
AIX HPUX Linux Solaris
Change the default path for the database to be the same as the
instance directory for the server. Issue the command:
db2 update dbm cfg using dftdbpath instance_directory

For example:
db2 update dbm cfg using dftdbpath /tsminst1

Windows
Change the default path for the database to be the drive where the
instance directory for the server is located. Complete the following
steps:
a. Click Start > Programs > IBM DB2 > DB2TSM1 > Command
Line Tools > Command Line Processor.
b. Enter quit to exit the command line processor.
A window with a command prompt opens, with the environment
correctly set up to successfully issue the commands in the next
steps.
c. From the command prompt in that window, issue the following
command to set the environment variable for the server instance
that you are working with:
set db2instance=instance_name

The instance_name is the same as the instance name that you

specified when you issued the db2icrt command. For example, to
set the environment variable for the Server1 server instance, issue
the following command:
set db2instance=server1
d. Issue the command to set the default drive:
db2 update dbm cfg using dftdbpath instance_location

For example, if the instance directory is d:\tsm\server1, the

instance location is drive d:. Enter the command:
db2 update dbm cfg using dftdbpath d:
7. Modify the library path to use the version of the IBM Global Security Kit
(GSKit) that is installed with the Tivoli Storage Manager server:
AIX Issue the following command:
export LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH

124 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

AIX HPUX Linux Solaris You must update the following files
to set the library path when DB2 or the Tivoli Storage Manager server is
started:
v instance_directory/sqllib/usercshrc
v instance_directory/sqllib/userprofile
For the instance_directory/sqllib/usercshrc file, add the following lines:
v AIX

setenv LIBPATH /usr/opt/ibm/gsk8_64/lib64:$LIBPATH

v HPUX Solaris

setenv LD_LIBRARY_PATH /opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

v Linux

setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

For the instance_directory/sqllib/userprofile file, add the following lines:
v AIX

LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
export LIBPATH
v HPUX Solaris

LD_LIBRARY_PATH=/opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
v Linux

LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Verify the library path settings and ensure that the GSKit version is 8.0.14.14
or later. Issue the following commands:
v AIX

echo $LIBPATH
gsk8capicmd_64 -version
gsk8ver_64
v HPUX Linux Solaris

echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64
If the GSKit version is not 8.0.14.14 or later, you must reinstall the Tivoli
Storage Manager server. The reinstallation ensures that the correct GSKit
version is available.
8. Change to the instance directory that you created for the server.
9. Create and format the database and recovery logs. In the command, specify
the directories that you created for the database and logs. The directories must
be empty.
AIX HPUX Linux Solaris

For example, to get an active log size of 16 GB (16384 MB, the default
size), issue the following command, on one line:
/opt/tivoli/tsm/server/bin/dsmserv loadformat \
dbdir=/tsmdb001,/tsmdb002,/tsmdb003,/tsmdb004 \
activelogsize=16384 activelogdirectory=/tsmlog \
mirrorlogdirectory=/tsmlogmirror archlogdirectory=/tsmarchlog

Windows

Chapter 4. Scenario 1: Same system, media method 125

Upgrading the server from V5 to V7.1

For example, to get an active log size of 16 GB (16384 MB, the default
size) for the Server1 server instance, issue the following command, on
one line:
"c:\Program Files\Tivoli\TSM\server\dsmserv" loadformat
dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog
If the server that you are upgrading is not Server1, you must use the
-k option. The -k option specifies the instance name for running this
utility. For example, if the system has more than one server instance
and the instance that you are upgrading is Server2, issue the
command:
"c:\Program Files\Tivoli\TSM\server\dsmserv" -k server2
loadformat dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog

Important: The server instance that you specify must have already
been through all preceding steps for the upgrade process, including
the creation of the database instance (db2icrt command).
10. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39
Related reference:
DSMSERV LOADFORMAT (Format a database)
“Deleted server commands, utilities, and options” on page 65

Scenario 1: Loading the extracted data into the new database

After you format an empty database by using the DSMSERV LOADFORMAT utility, load
the data that you extracted from the original server database.

Before you begin

Ensure that the following requirements are met before you begin to load the data:
v The manifest file from the DSMUPGRD EXTRACTDB operation must be available.
v The server options file must contain an entry for the device configuration file.
v The device configuration file must have information about the device class that
is specified in the manifest file.
v The media that contains the extracted database must be available to the V7.1
server. The device must be physically attached to the system. The permissions
must be set to grant access to the media for the user ID that owns the V7.1
server instance.

Procedure
1. Verify that the V7.1 server can access the extracted data.
v If the extracted data is on tape, the tape drive must be physically attached to
the system.
v If the extracted data was stored by using a FILE or DISK device class,
complete the following steps:
a. Log on to the system by using the root user ID.

126 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

b. Ensure that the user ID that owns the V7.1 server (the instance user ID)
has ownership or read/write permission for the extracted files.
2. For the manifest file that was created by the extraction process, ensure that the
instance user ID has ownership or read/write permission.
3. Log on with the instance user ID.
4. On the V7.1 server, complete the following steps:
a. Verify that the server options file from the V5 server includes the DEVCONFIG
option, and that the option specifies the full path of the device
configuration file.
b. Verify that the device configuration file from the V5 server is available in
the location that is specified by the DEVCONFIG option.
c. Verify that the permissions on the device configuration file allow read
access for the instance user ID.
5. Verify that the contents of the device configuration file are correct. The device
class that was used for the extraction step is recorded in the manifest file, and
that device class must exist and be valid on the V7.1 system.
a. Verify entries for FILE device classes. For example, paths might be different
on the system.
b. Verify entries for tape and other devices. For example, the device names
might have changed.
6. Verify the contents of the manifest file and edit the file if necessary:
a. Ensure that the device names in the manifest file are valid for the V7.1
system. Device names for the same device might be different on V5 and V7
systems.
b. Ensure that the manifest file contains a list of volumes to be used when the
extracted data is loaded into the new database. For example, if the manifest
file contains a list of volumes that belong to a FILE device class, ensure that
the fully qualified path to the volumes is correct for the system.
7. Issue the DSMSERV INSERTDB command to load an extracted server database into
the prepared, empty V7.1 database. Direct the output of the process to a file for
monitoring. For example, enter the following command on one line:
AIX HPUX Linux Solaris

nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \

manifest=./manifest.txt >insert.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\server\dsmserv" insertdb \

manifest=.\manifest.txt 1>>insert.out 2>&1
8. Monitor the process for error messages, warning messages, and any items that
you might need to address. The system displays interim statistics about the
process of loading the database. However, there might be time periods when
no messages are issued. During this time, DB2 operations are running in the
background. The length of time that the process runs depends on the size of
the database. For more information, see “Example: Estimating the upgrade time
based on the database size” on page 43.
Optional: Verify that the database is being loaded by monitoring the processor
and I/O usage for the server process and the corresponding DB2 process. For
example, issue the following command to monitor the process:
tail -f insert.out

Chapter 4. Scenario 1: Same system, media method 127

Upgrading the server from V5 to V7.1

Tip: Windows On Windows systems, use the tail command or an equivalent

utility with which you can monitor the contents of a file as it changes. For
example, the Windows Server 2003 Resource Kit Tools includes the tail
command, which can be used as shown in the preceding example.
A message in the output of the DSMSERV INSERTDB command indicates the status
of the operation:
Success message: ANR1395I INSERTDB: Process 1, database insert, has
completed.
Failure message: ANR1396E INSERTDB: Process 1, database insert, has
completed with errors.
9. If you used a tape device, after the insertion operation is complete remove or
check out from the library the tape that holds the extracted data. Prevent the
tape from being reused until you are sure that you do not need to run the
insertion operation again.
Related concepts:
“The manifest file for the data extraction to media” on page 531
Related reference:
“DSMSERV INSERTDB (Move a server database into an empty database)” on page
538

Scenario 1: Creating a Windows service for the server

instance
Windows

A Windows service is created for the Tivoli Storage Manager V7.1 server
automatically if you use the upgrade wizard (dsmupgdx). If you do not use the
wizard, you must create the Windows service for the Tivoli Storage Manager
server manually.

Procedure
1. Change to the installation directory for the server program. By default, the
directory is C:\Program Files\Tivoli\TSM\console. If you installed the server
in a different directory, change to the console subdirectory of the server
installation directory.
2. Install the Windows service by using the Tivoli Storage Manager server
instance name and password in the service name. Issue the following
command:
install "TSM server_instance_name"
"C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
instance_owner instance_owner_password

where:
"TSM server_instance_name" is the name of the service that is being
installed.
server_instance_name is the instance name that was specified when you
issued the db2icrt command.
instance_owner is the instance owner account; this account will own the
service.
instance_owner_password is the password for the instance owner account.
Example
To install the Windows service for the server1 server instance, enter the

128 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

following command on one line. The example uses rudy as the instance
owner and s21ret as the password for the instance owner account.
install "TSM server1" "C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
rudy s21ret
3. Optional: Manually change the service to an automatic startup type by using
Windows administrative tools (Administrative Tools > Services).
Related tasks:
“Starting the server on Windows systems” on page 331

Scenario 1: Configuring the system for database backup

The database manager and the Tivoli Storage Manager API must be configured so
that the database manager can back up the server database. The configuration is
completed for you automatically if you use the upgrade wizard (dsmupgdx). If you
do not use the wizard, you must complete the configuration manually.

Procedure
v “Scenario 1: Configuring the system for database backup on AIX, HP-UX, Linux,
and Oracle Solaris systems”
v “Scenario 1: Configuring the system for database backup on Microsoft Windows
systems” on page 131

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Scenario 1: Configuring the system for database backup on AIX,

HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

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

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, replace the example values with your actual values.
The examples use tsminst1 for the server instance user ID, /tsminst1 for the Tivoli
Storage Manager server instance directory, and /home/tsminst1 as the home
directory of the server instance user.

Chapter 4. Scenario 1: Same system, media method 129

Upgrading the server from V5 to V7.1

Procedure
1. Set the Tivoli Storage Manager API environment-variable configuration for the
database instance:
a. Log in by using the tsminst1 user ID.
b. When user tsminst1 is logged in, ensure that the DB2 environment is
correctly initialized. The DB2 environment is initialized by running the
/home/tsminst1/sqllib/db2profile script, which normally runs
automatically from the profile of the user ID. Ensure that the .profile file
exists in the home directory of the instance user, for example,
/home/tsminst1/.profile. If .profile does not run the db2profile script,
add the following lines:
if [ -f /home/tsminst1/sqllib/db2profile ]; then
. /home/tsminst1/sqllib/db2profile
fi
c. In the instance_directory/sqllib/userprofile file, add the following lines:
DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
DSMI_DIR=server_bin_directory/dbbkapi
DSMI_LOG=server_instance_directory
export DSMI_CONFIG DSMI_DIR DSMI_LOG
d. In the instance_directory/sqllib/usercshrc file, add the following lines:
setenv DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
setenv DSMI_DIR=server_bin_directory/dbbkapi
setenv DSMI_LOG=server_instance_directory
2. Log out and log in again as tsminst1, or issue this command:
. ~/.profile

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

The value for SERVERNAME must be consistent in the tsmdbmgr.opt and dsm.sys
files.
4. Locate the Tivoli Storage Manager API dsm.sys configuration file. By default,
the dsm.sys file is in the following location:

server_bin_directory/dbbkapi/dsm.sys
5. As root user, add the following lines to the dsm.sys configuration file:
servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
errorlogname /tsminst1
nodename $$_TSMDBMGR_$$

where
v servername matches the servername value in the tsmdbmgr.opt file.
v commmethod specifies the client API that is used to contact the server for
database backup. This value can be tcpip or sharedmem. For more
information about shared memory, see Step 6 on page 131.
v tcpserveraddr specifies the server address that the client API uses to contact
the server for database backup. To ensure that the database can be backed
up, this value must be localhost.

130 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

v tcpport specifies the port number that the client API uses to contact the
server for database backup. Ensure that you enter the same tcpport value
that is specified in the dsmserv.opt server options file.
v errorlogname specifies the error log where the client API logs errors that are
encountered during a database backup. This log is typically in the server
instance directory. However, this log can be placed in any location where the
instance user ID has write-permission.
v nodename specifies the node name that the client API uses to connect to the
server during a database backup. To ensure that the database can be backed
up, this value must be $$_TSMDBMGR_$$.
Linux Do not add the PASSWORDACCESS generate option to the dsm.sys
configuration file. This option can cause the database backup to fail.
6. Optional: Configure the server to back up the database by using shared
memory. In this way, you might be able to reduce the processor load and
improve throughput. Complete the following steps:
a. Review the dsmserv.opt file. If the following lines are not in the file, add
them:
commmethod sharedmem
shmport port_number

where port_number specifies the port that you use for shared memory.
b. In the dsm.sys configuration file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport port_number

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port that you use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Scenario 1: Configuring the system for database backup on

Microsoft Windows systems
Windows

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

Chapter 4. Scenario 1: Same system, media method 131

Upgrading the server from V5 to V7.1

In the following commands, the examples use server1 for the database instance
and d:\tsmserver1 for the Tivoli Storage Manager server directory. When you
issue the commands, replace these values with your actual values.

Procedure
1. Create a file that is named tsmdbmgr.env in the d:\tsmserver1 directory with
the following contents:
DSMI_CONFIG=server_instance_directory\tsmdbmgr.opt
DSMI_LOG=server_instance_directory
2. Set the DSMI_ api environment-variable configuration for the database instance:
a. Open a DB2 command window. One method is to go to the C:\Program
Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage
Manager in a different location, go to the db2\bin subdirectory in your main
installation directory. Then, issue the following command:
db2cmd
b. Issue the following command:
db2set -i server1 DB2_VENDOR_INI=d:\tsmserver1\tsmdbmgr.env
c. Create a file that is named tsmdbmgr.opt in the d:\tsmserver1 directory
with the following contents:
*************************************************
nodename $$_TSMDBMGR_$$
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
passwordaccess generate
errorlogname d:\tsmserver1
where
v nodename specifies the node name that the client API uses to connect to
the server during a database backup. To ensure that the database can be
backed up, this value must be $$_TSMDBMGR_$$.
v commmethod specifies the client API that is used to contact the server for
database backup. This value can be tcpip or sharedmem. For more
information about shared memory, see Step 3.
v tcpserveraddr specifies the server address that the client API uses to
contact the server for database backup. To ensure that the database can be
backed up, this value must be localhost.
v tcpport is the port number that the client API uses to contact the server
for database backup. Ensure that you enter the same tcpport value that is
specified in the dsmserv.opt server options file.
v passwordaccess is required to ensure that the backup node can connect to
the server.
v errorlogname is the error log where the client API logs errors that are
encountered during a database backup. This log is typically in the server
instance directory. However, this log can be placed in any location where
the instance user ID has write-permission.
3. Optional: Configure the server to back up the database by using shared
memory. In this way, you might be able to reduce the processor load and
improve throughput. Complete the following steps:
a. Review the dsmserv.opt file. If the following lines are not in the file, add
them:
commmethod sharedmem
shmport port_number

132 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

where port_number specifies the port to use for shared memory.

b. In the tsmdbmgr.opt file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport 1500

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port to use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Chapter 4. Scenario 1: Same system, media method 133

134 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 5. Scenario 2: Same system, network method
Use this procedure if you are upgrading the Tivoli Storage Manager server on the
same system as the V5 server, and you are using the network method to move the
data.

Procedure

The procedure for upgrading the server includes the following tasks:
1. “Scenario 2: Preparing for the upgrade”
2. “Scenario 2: Installing the upgrade utilities” on page 144
3. “Scenario 2: Preparing the database of a V5 server for upgrade” on page 151
4. “Scenario 2: Uninstalling the V5 program before installing V7.1” on page 152
5. “Scenario 2: Installing the V7.1 server” on page 155
6. “Scenario 2: Creating the directories and the user ID for the upgraded server
instance” on page 159
7. Upgrading the server, by using one of the following methods:
v “Scenario 2: Upgrading the server by using the upgrade wizard” on page 162
v “Scenario 2: Upgrading the server manually by using utilities” on page 164
8. The following tasks are completed after the upgrade:
a. “Verifying access to storage pools on disk” on page 323
b. “Setting up Solaris services for the server instance” on page 324
c. “Configuring server options for server database maintenance” on page 324
d. “Starting the server instance after the upgrade” on page 325
e. “Registering licenses” on page 334
f. “Backing up the database after upgrading the server” on page 335
g. “Verifying the upgraded server” on page 336
h. “Changing the host name for the Tivoli Storage Manager server” on page
336
i. “Updating automation” on page 338
j. “Monitoring the upgraded server” on page 339
k. “Removing GSKit Version 7 after upgrading to Tivoli Storage Manager
V7.1” on page 340

Scenario 2: Preparing for the upgrade

Prepare for the upgrade by checking requirements, preparing the space that is
required, backing up the server, and modifying certain server settings.

About this task

Follow the preparation steps carefully to protect your server and its data.

Important: It is possible, after the upgrade to V7.1 is complete, that conditions

might cause the need to temporarily revert to the previous version of the server.
Successfully reverting to the previous version of the server is possible only if you

© Copyright IBM Corp. 2009, 2013 135

Upgrading the server from V5 to V7.1

have completed all preparation steps. To understand why it is important to

complete all preparation steps, review the procedure for reverting an upgraded
server to its previous version.

Procedure
1. “Scenario 2: Checking the prerequisites for the upgrade”
2. “Scenario 2: Preparing space for the upgrade process” on page 139
3. “Scenario 2: Modifying the server before the upgrade” on page 139
4. “Scenario 2: Disabling sessions” on page 141
5. “Scenario 2: Backing up storage pools and the server database” on page 141
6. “Scenario 2: Moving the NODELOCK file” on page 142
7. “Scenario 2: Backing up configuration information” on page 142
8. “Scenario 2: Creating a summary of database contents” on page 143
9. “Scenario 2: Stopping the server before installing the upgrade” on page 143
Related tasks:
“Reverting from V7.1 to the previous V5 server version” on page 351

Scenario 2: Checking the prerequisites for the upgrade

Check your system against requirements for the server.

Before you begin

Requirement: If you are upgrading the Tivoli Storage Manager server on the same
system, the system must meet the minimum requirements for both the V5 and V7.1
servers.

Procedure
1. Ensure that the server that you plan to upgrade is at the V5.5 release level, and
that the latest interim fix is installed. For example, if the server is at V5.5.6,
install the latest interim fix for V5.5.6. Take the following actions:
a. Select the appropriate server level. For detailed guidelines, see
“Determining the appropriate level for a V5 server before an upgrade” on
page 36. If the server is at an appropriate level, no action is required.
b. If the server is not at an appropriate level, download the appropriate server
fix pack and the latest interim fix from the FTP downloads site at
ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server/. Locate the appropriate version of Tivoli Storage
Manager and install it.
2. Ensure that the system where the V5 server is located meets the minimum
requirements. Review the information in “Hardware and software requirements
for the V5 server system that is being upgraded” on page 17 to determine
whether you must update your system before you continue.
3. Ensure that the system where you plan to install the V7.1 server meets
requirements for the operating system type and level. For the latest information
about system requirements, see Tivoli Storage Manager Supported Operating
Systems (http://www.ibm.com/support/docview.wss?uid=swg21243309).
If you are upgrading Tivoli Storage Manager to a different operating system, a
limited set of migration paths is available. For instructions about migrating a
server that is running on a z/OS operating system, see Part 3, “Migrating Tivoli
Storage Manager V5 servers on z/OS systems to V7.1 on AIX or Linux on
System z,” on page 437. For instructions about migrating a server that is

136 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

running on an AIX, HP-UX, or Solaris operating system, see Part 2, “Migrating

Tivoli Storage Manager V5 servers on AIX, HP-UX, or Solaris systems to V7.1
on Linux,” on page 355.
Some platforms that were supported for earlier versions of the server are not
supported for V7.1. If the server that you want to upgrade is running on one of
these platforms, you cannot upgrade your server to V7.1 on the same platform.
You must install your V7.1 server on a system that is a specific supported
platform, depending on the original platform. For required platforms, see the
following table.
Table 36. Required platforms for upgrading from V5 to V7.1
Platform for V5 server Required platform for upgrade to V7.1
HP-UX running on a PA-RISC system HP-UX running on an Intel Itanium system
Linux running on an Itanium system (IA64) Linux running on an x86_64 system
Linux running on an x86_32 system Linux running on an x86_64 system
Solaris running on an x86_64 system Linux running on an x86_64 system
Windows running on an Itanium system Windows running on an x86_64 system
(IA64)

If you are upgrading from Tivoli Storage Manager V5 to V7.1 on a new system,
restrictions apply. Ensure that you install the V7.1 server in a compatible
hardware and software environment, as described in the following table.
Table 37. Requirements for upgrading from V5 to V7.1 on a new system
V5 server V7.1 server Comments
AIX running on an IBM AIX running on an IBM
POWER system POWER system
HP-UX running on an HP-UX running on an
Itanium system Itanium system
HP-UX running on a HP-UX running on an HP-UX running on PA-RISC
PA-RISC system Itanium system is not supported for V7.1
servers.
Linux running on an IBM Linux running on an IBM
POWER system POWER system
Linux running on an Itanium Linux running on an x86_64 Linux running on Itanium is
system (IA64) system not supported for V7.1
servers.
Linux running on an x86_32 Linux running on an x86_64 Linux running on x86_32 is
system system not supported for V7.1
servers.
Linux on System z Linux on System z

Chapter 5. Scenario 2: Same system, network method 137

Upgrading the server from V5 to V7.1

Table 37. Requirements for upgrading from V5 to V7.1 on a new system (continued)
V5 server V7.1 server Comments
Solaris running on an x86_64 Operating system depends A V7.1 server cannot be
system on the migration method installed on a Solaris x86_64
system. However, you can
migrate a V5 server that is
running on a Solaris x86_64
operating system to V7.1 on
a Linux x86_64 operating
system. For instructions, see
Part 2, “Migrating Tivoli
Storage Manager V5 servers
on AIX, HP-UX, or Solaris
systems to V7.1 on Linux,”
on page 355.

Alternatively, you can

migrate the Solaris x86_64
system by installing a V7.1
server on any operating
system that is supported for
V7.1. Then, use Tivoli
Storage Manager server
EXPORT and IMPORT
commands to move the
server from the V5 source
system to the V7.1 target
system.
Windows running on an Windows running on an Windows running on
Itanium system (IA64) x86_64 system Itanium is not supported for
V7.1 servers.
Windows running on an Windows running on an Windows running on x86_32
x86_32 system x86_64 system is not supported for V7.1
servers.
z/OS AIX or Linux on System z See the section on migrating
from V5 on z/OS to V7.1 on
AIX or Linux on System z.

4. Verify that the system memory meets the server requirements.

v Ensure that the system memory is sufficient to run two servers at the same
time.
When you run the process that extracts the database from the existing server
and inserts the database for the new server, the net effect is that two servers
are running.
v If you plan to run multiple instances of the V7.1 server on the system, each
instance requires the memory that is listed for one server. Multiply the
memory for one server by the number of instances that are planned for the
system.
For specific information about memory requirements, see the section for your
operating system:
Table 38. Memory requirements for the V7.1 system
Operating system Memory requirements
AIX “Server requirements on AIX systems” on
page 21

138 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 38. Memory requirements for the V7.1 system (continued)

Operating system Memory requirements
HP-UX “Server requirements on HP-UX systems” on
page 24
Linux “Server requirements on Linux systems” on
page 26
Solaris “Server requirements on Solaris systems” on
page 31
Windows “Server requirements on Microsoft Windows
systems” on page 33

5. Ensure that the system has enough disk storage for the database and recovery
logs. Review the planning information for requirements and guidance.
Ensure that the system has enough disk storage for storing database and
recovery logs for both the original server and the new V7.1 server. Both are
stored on disk storage during the upgrade process.
If you are adding new hardware for the server, such as new disk storage for
the database, ensure that the hardware is installed and running.
Related concepts:
“Hardware and software requirements for upgrading to the V7.1 server” on page
17

Scenario 2: Preparing space for the upgrade process

Determine the amount and type of space that is required for the upgrade process
before beginning the process.

Procedure

Verify that the system has the amount of space that was estimated in the planning
step. Use the planning worksheet that you completed with your information. See
“Worksheet for planning space for the V7.1 server” on page 42.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39

Scenario 2: Modifying the server before the upgrade

A command must be run on the server to prevent one type of problem during the
upgrade process. Some modifications to typical server settings can be useful to
prepare for the upgrade.

Procedure
1. From a Tivoli Storage Manager administrative command line, issue the
command:
convert ussfilespace

This command fixes a problem that might exist in older Tivoli Storage Manager
databases. If the problem does not exist in your database, the command is
completed and you might see error ANR2034E. This error can be ignored. For
more information, see Technote 1408895 (http://www.ibm.com/support/
docview.wss?uid=swg21408895). If the problem exists in your database, the
command might take some time to run.

Chapter 5. Scenario 2: Same system, network method 139

Upgrading the server from V5 to V7.1

Important: Do not skip this step. If your database has the problem and you do
not run this command now, the DSMUPGRD PREPAREDB utility fails when you run
it. You must then restart the V5 server and run the CONVERT USSFILESPACE
command before you continue the upgrade process.
2. Review the steps for reverting to the earlier version of the server in the section,
“Reverting from V7.1 to the previous V5 server version” on page 351.
If you must revert to the earlier version after the upgrade to V7.1, the results of
the reversion will be better if you understand the steps and prepare for the
possibility now.
3. Make the following adjustments to settings on your server and clients. These
adjustments must be done to make it possible for you to revert to the original
server after the upgrade, if problems occur.
a. For each sequential-access storage pool, set the REUSEDELAY parameter to the
number of days during which you want to be able to revert to the original
server, if necessary.
For example, if you want to be able to revert to the original server for up to
30 days after the upgrade to V7.1, set the REUSEDELAY parameter to 31 days.
Issue the following administrative command:
update stgpool sequential_access_storage_pool reusedelay=31
b. For each copy storage pool, set the RECLAIM parameter to 100 (meaning
100%). Issue the following administrative command:
update stgpool copy_storage_pool reclaim=100
c. If you typically use a DELETE VOLHISTORY command to delete database
backups, ensure that the command does not delete database backups too
frequently. The interval between backups should be at least the same
number of days that you set for the REUSEDELAY period for sequential-access
storage pools. For example, to delete database backups every 45 days, issue
the following administrative command:
delete volhist type=dbbackup todate=-45
d. For important clients that use the server, verify that the value for the
schedlogretention client option is set to retain the client schedule log for a
sufficient time. Update the option for clients if needed.
The entries in the client schedule log might be useful if the server must
revert to the original version. If the retention period for the schedule log is
too short, the schedule log information might be deleted too soon.
For example, to prune the log every 45 days and save the log entries, add
the following option:
schedlogretention 45 S
AIX HPUX Linux Solaris Add the option to the dsm.sys file
within a server stanza.
Windows Add the option to the client options file, dsm.opt.

140 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 2: Disabling sessions

In preparation for the upgrade, prevent activity on the server by disabling new
sessions. Cancel any existing sessions.

About this task

The commands in the following procedure are Tivoli Storage Manager

administrative commands.

Procedure
1. Prevent all clients, storage agents, and other servers from starting new sessions
with the server. Use the commands:
disable sessions client
disable sessions server
For more information about these commands and other Tivoli Storage Manager
administrative commands, see the Administrator's Reference.
2. Verify whether any sessions exist, and notify the users that the server is going
to be stopped. To check for existing sessions, use the command:
query session
3. Cancel sessions that are still running. Use the command:
cancel session all

Scenario 2: Backing up storage pools and the server database

Immediately before upgrading the server, back up primary storage pools to copy
storage pools, and perform a full database backup.

Before you begin

Back up storage pools and the server database by using Tivoli Storage Manager
administrative commands:

Procedure
1. Back up primary storage pools to copy storage pools by using the BACKUP
STGPOOL command:
backup stgpool primary_pool copy_stg

where primary_pool specifies the primary storage pool and copy_stg specifies the
copy storage pool. If you have been performing regular backups of the storage
pools, this step backs up only the data that was added to the primary storage
pools since they were last backed up.
2. Back up the database. The preferred method is to use a snapshot backup. A
snapshot backup is a full database backup that does not interrupt any
scheduled database backups. Issue the command:
backup db type=dbsnapshot devclass=device_class_name

The device class that you specify must exist and have volumes that are
available to it. For example, to perform a snapshot backup of your database to
the TAPECLASS device class by using scratch volumes, enter:
backup db type=dbsnapshot devclass=tapeclass

To use specific volumes instead of scratch volumes, specify the volume names
in the command.

Chapter 5. Scenario 2: Same system, network method 141

Upgrading the server from V5 to V7.1

Tip: Consider making two copies of the backup to protect the backup from
media failures. Ensure that at least one full database backup is available onsite.
If you must restore the database after a failed upgrade, having an onsite
backup database saves time.

Scenario 2: Moving the NODELOCK file

To ensure that licensing information is updated during the upgrade process, move
the NODELOCK file from the server instance directory to another directory.

About this task

The NODELOCK file contains the licensing information from the previous Tivoli
Storage Manager installation. This licensing information is replaced when the
upgrade is complete.

Procedure
1. In the server instance directory of your installation, locate the NODELOCK file.
2. Move the NODELOCK file to another directory. For example, you can save it to a
directory where you are saving configuration files from the previous release.

Scenario 2: Backing up configuration information

Before you install the new version, back up critical files and information for each
server instance. Store the files in a safe place, on a different system from the
system that is being upgraded or on offline media, such as a CD. The files are
required after the installation of the new software version is complete. You also
need these files if you must revert to the previous version after the upgrade.

Procedure
1. Back up device configuration information to another directory by using the
following Tivoli Storage Manager administrative command:
backup devconfig filenames=file_name

where file_name specifies the file in which to store device configuration

information.
2. Back up volume history information to another directory by using the
following Tivoli Storage Manager administrative command:
backup volhistory filenames=file_name

where file_name specifies the file in which to store volume history information.
Ensure that the volume history includes information about the database backup
that you completed in the preceding steps. For example, issue the following
command:
query volhistory type=dbsnapshot

Review the query output to verify that the time stamp for the database backup
matches the actual time of the backup.
3. Save copies of the following files, which are in the server instance directory:
v Server options file, typically named dsmserv.opt
v dsmserv.dsk

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.

142 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

4. In the server instance directory, look for the accounting log file, dsmaccnt.log.
If the file exists, save a copy.
5. Back up any scripts that were used to complete daily housekeeping for the
server. Examine the scripts for changes that are needed after the upgrade.
6. Store the device configuration file, the volume history file, the server options
file, and the other files in a safe place. Ensure that the files are stored on a
different system from the system that is being upgraded, or on offline media.

Scenario 2: Creating a summary of database contents

Create a summary of the contents of the original database. After the upgrade, you
can use the same commands to compare the results and to confirm that the
database contents are intact.

Procedure

Run commands that give a summary of information about your database contents.
For example, issue commands that summarize the file spaces that are being
protected, and save the results. For a list of commands, see “Sample commands to
run for validation of the database upgrade” on page 546.
Related reference:
“Sample commands to run for validation of the database upgrade” on page 546

Scenario 2: Stopping the server before installing the upgrade

Stop all server processes and unmount any tapes that are mounted. Then, stop the
server.

Procedure

Use Tivoli Storage Manager administrative commands to stop the server:

1. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the following commands:
query process
cancel process process_number

Allow time for the processes to be stopped. Some processes, such as storage
pool migration, might take some time to stop.
For more information about the QUERY PROCESS and CANCEL PROCESS commands
and other Tivoli Storage Manager administrative commands, see the
Administrator's Reference.
2. After all sessions and processes are stopped, determine whether any tapes are
mounted. Unmount any tapes that are mounted. Use the following commands:
query mount
dismount volume volume_name
3. Stop the server. Use the following command:
halt

Chapter 5. Scenario 2: Same system, network method 143

Upgrading the server from V5 to V7.1

Scenario 2: Installing the upgrade utilities

You must install the upgrade utilities on the system. The installation package for
the utilities must be downloaded from a website.

Before you begin

The preferred method is to install the latest available version of the upgrade
utilities. For more information about selecting the version, see “Determining the
appropriate level for a V5 server before an upgrade” on page 36.

Procedure

Use the procedure for your operating system:

v AIX “Scenario 2: Installing the upgrade utilities on AIX systems”
v HPUX “Scenario 2: Installing the upgrade utilities on HP-UX systems” on
page 146
v Linux “Scenario 2: Installing the upgrade utilities on Linux systems” on page
147
v Solaris “Scenario 2: Installing the upgrade utilities on Oracle Solaris systems”
on page 148
v Windows “Scenario 2: Installing the upgrade utilities on Microsoft Windows
systems” on page 150
Related concepts:
“DSMUPGRD upgrade utilities” on page 16

Scenario 2: Installing the upgrade utilities on AIX systems

AIX

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The
5.5.x.x number must be the same as or later than the level of the V5
server that you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-AIX.tar.gz
The numbers at the beginning of the package name identify the release
level of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.

144 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

2. Log in with the root user ID.

3. Ensure that the system has the following file sets installed:
xlC.rte 8.0.0.5, or later
gsksa.rte 7.0.4.11
You can use the following commands to check for these file sets:
lslpp -L xlC.rte

lslpp -L gsksa.rte

If needed, you can obtain the gsksa.rte file set from any of the regular V5.5
maintenance packages for the AIX server. The maintenance packages are
available on the FTP downloads site: ftp://public.dhe.ibm.com/storage/tivoli-
storage-management/maintenance/server/v5r5/AIX/
4. Extract the contents of the upgrade utilities package. If you downloaded a
language package, also extract the contents of that package.
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Access the System Management Interface Tool (SMIT).
a. Enter smitty install_update
b. Select Install and Update Software > Install and Update from ALL
Available Software.
7. Select the INPUT device. Specify the directory location of the upgrade utilities
package on the system.
8. Select Software to Install. Press F4 or Esc+4 for the list of available file sets in
the directory.
9. Select the file sets for the upgrade utilities, the device driver, and optionally
the language package. The file set for the upgrade utilities is
tivoli.tsmupg.server. Optional language packages include messages for
languages other than US English.
10. Set COMMIT software updates to Yes. Press F4 or Esc+4.
11. Set SAVE replaced files to No.
12. Ensure that the default settings for the options in the window for all the
selected file sets show success.
13. Press Enter, and respond to the ARE YOU SURE? question by pressing Enter
again. The installation begins.
14. When the installation is complete, exit the SMIT program.
15. Optional: If you installed a language package, ensure that the locale
environment variable is set to use it. Enter the following command to set the
locale environment variable for messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.

Chapter 5. Scenario 2: Same system, network method 145

Upgrading the server from V5 to V7.1

16. After the upgrade utilities are installed, continue at “Scenario 2: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 149.

Scenario 2: Installing the upgrade utilities on HP-UX systems

HPUX

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.gz
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
gzip -dc package_name.tar.gz | tar -xvf -
4. Navigate to the directory that corresponds to the processor architecture of the
operating system.
5. Install the upgrade utilities and the device driver. Use the source argument (-s)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
swinstall -s /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin.

6. Optional: Install the language package.
a. Extract the contents of the package.
gzip -d package_name.img.gz
b. Install the package. For example, if the directory is /tmp/TSM, issue the
command:
swinstall -s /tmp/TSM/package_name.img package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

146 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Scenario 2: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 149.

Scenario 2: Installing the upgrade utilities on Linux systems

Linux

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Open the directory for your operating system and download the package.
The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.bz2
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the commands:
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
4. Navigate to the directory that corresponds to the processor architecture of the
operating system, for example, x86_64.
5. Install the upgrade utilities and the device driver. Use the following command:
rpm -ivh package_name.rpm
The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by
default.
6. Optional: Install the language package.
a. Extract the contents of the downloaded package.
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
b. Install the package for the language that you want to use.

Chapter 5. Scenario 2: Same system, network method 147

Upgrading the server from V5 to V7.1

rpm -ivh package_name.rpm

c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Scenario 2: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 149.

Scenario 2: Installing the upgrade utilities on Oracle Solaris

systems
Solaris

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

About this task

Restriction: Do not install the utilities in the installation directory of the server that
must be upgraded. Install the utilities package in its own directory.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.Z
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Change to the directory where the upgrade utilities package was downloaded.
4. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
uncompress -c package_name.tar.Z | tar -xvf -

148 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

5. Navigate to the directory that corresponds to the processor architecture of the

operating system.
6. Install the upgrade utilities and the device driver. Use the source argument (-d)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
pkgadd -d . /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by

default.
7. Optional: Install the language package.
a. Extract the contents of the downloaded package.
uncompress package_name.pkg.Z
b. Install the package for the language that you want to use. Use the source
argument (-d) to specify the directory where the package was extracted. For
example, if the directory is /tmp/TSM, issue the command:
pkgadd -d /tmp/TSM package_name.pkg package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
8. After the upgrade utilities are installed, continue at “Scenario 2: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems.”

Scenario 2: Setting environment variables for the upgrade

utilities on AIX, HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

After installing the upgrade utility package, you must set environment variables in
the shell from which you will run the utilities. An environment variable describes
the operating environment of a process, such as the home directory or terminal in
use.

About this task

The DSMSERV_DIR variable specifies the installed location of the upgrade utilities. By
default, the location is the following directory:

AIX

/usr/tivoli/tsm/upgrade/bin

HPUX Linux Solaris

/opt/tivoli/tsm/upgrade/bin

Chapter 5. Scenario 2: Same system, network method 149

Upgrading the server from V5 to V7.1

Procedure

Use the appropriate command for your system to set the environment variable for
running the utilities. If the shell is in the ksh or bash family, enter the following
command to set the DSMSERV_DIR variable:
export DSMSERV_DIR=upgrade_utilities_directory

If your shell is in the csh family, use the following command:

setenv DSMSERV_DIR upgrade_utilities_directory

where upgrade_utilities_directory is the directory where the upgrade utilities are

installed.

What to do next

After you set the environment variables, continue at “Scenario 2: Preparing the
database of a V5 server for upgrade” on page 151.

Scenario 2: Installing the upgrade utilities on Microsoft

Windows systems
Windows

Install the upgrade utilities on the system. The package to install is available for
download from the FTP downloads site. The upgrade utilities are used to prepare
and extract the database from the original server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/WIN
b. Open the 5.5.x.x directory. The 5.5.x.x number must be the same as or
later than the level of the V5 server that you are upgrading.
c. Select the package and download it to a convenient location on the server
system. The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-Windows.exe
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, install the
language package that your installation requires.
2. Log on with an administrator ID.
3. Run the executable package for the upgrade utilities.
The default location for the installation of the utilities is based on the location
where the V5 server was last installed. For example, if the V5 server was
installed using the default path, C:\Program Files\Tivoli\TSM\server, the
upgrade utilities are installed in C:\Program Files\Tivoli\TSM\upgrade.

What to do next

After the upgrade utilities are installed, continue at “Scenario 2: Preparing the
database of a V5 server for upgrade” on page 151.

150 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Tip: When you use the upgrade utilities, if you have multiple servers running on
the system, you must use the -k option to specify the name of the Windows
registry key from which to retrieve information about the server being upgraded.
The default value for the option is SERVER1. Use the -o option with the DSMUPGRD
command to specify the location of the server options file.

Scenario 2: Preparing the database of a V5 server for upgrade

Before you extract the data from the database, you must prepare the server
database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a
single system, you must repeat this task for each server.

Procedure
1. Ensure that you have completed all preparation steps.
2. Log in using the root user ID on the system that has the original server. Log on
with the administrator ID on a Windows system.
3. Change to the instance directory for the server that you are upgrading. The
instance directory is the directory that contains the files such as dsmserv.dsk for
the server.

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.
4. Prepare the database. Direct the output of the process to a file for monitoring.
AIX
From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

HPUX Linux Solaris

From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

Windows
From the instance directory for the server that you are upgrading, issue
the following command to run the process and direct the output to the
file called prepare.out:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd"
preparedb 1>>prepare.out 2>&1

If multiple servers exist on the system, issue the command from the
instance directory for the server that you want to prepare. Specify the
registry key for that server. For example, if the server is SERVER2:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" -k server2
preparedb 1>>prepare.out 2>&1
5. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation. From the instance directory for the
server that you are upgrading, issue the following command to monitor the
process:
tail -f prepare.out

Chapter 5. Scenario 2: Same system, network method 151

Upgrading the server from V5 to V7.1

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
6. Ensure that the prepare operation is completed successfully before you continue
to the next step. If the prepare operation fails, you might need to restart the V5
server to fix the problem and run the prepare operation again. If the server that
is being upgraded is a V5.3 or V5.4 server, you might need to restore the
database by using a backup before you can restart the server to correct the
problem.
Related reference:
“DSMUPGRD PREPAREDB (Prepare a V5 database for upgrade)” on page 523

Scenario 2: Uninstalling the V5 program before installing V7.1

For best results when you are upgrading the server to V7.1 on the same system
where the V5 server is located, uninstall the V5 server program. Then, install the
V7.1 server program.

Procedure

Use the procedure for your operating system:

v AIX “Scenario 2: Uninstalling the V5 program on AIX systems”
v HPUX “Scenario 2: Uninstalling the V5 program on HP-UX systems” on page
153
v Linux “Scenario 2: Uninstalling the V5 program on Linux systems” on page
153
v Solaris “Scenario 2: Uninstalling the V5 program on Oracle Solaris systems”
on page 154
v Windows “Scenario 2: Uninstalling the V5 program on Microsoft Windows
systems” on page 154

Scenario 2: Uninstalling the V5 program on AIX systems

AIX

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
v For a V5.4 or V5.5 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license.aix5.rte64
/usr/sbin/installp -ug tivoli.tsm.devices.aix5.rte
/usr/sbin/installp -ug tivoli.tsm.server.aix5.rte64
v For a V5.3 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license
/usr/sbin/installp -ug tivoli.tsm.devices
/usr/sbin/installp -ug tivoli.tsm.server

152 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

What to do next

After the V5 server program is uninstalled, continue at “Scenario 2: Installing the

V7.1 server” on page 155.

Scenario 2: Uninstalling the V5 program on HP-UX systems

HPUX

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
v For a V5.4 or V5.5 server, issue the following commands:
swremove TIVsmS64IA.server
swremove TIVsmS64IA.license
swremove TIVsmDD64_IA11_23.tsmscsi
v For a V5.3 server, issue the following commands:
swremove TIVsmS64.server
swremove TIVsmS64.license
swremove TIVsmDD64_HP11_11.tsmscsi

What to do next

After the V5 server program is uninstalled, continue at “Scenario 2: Installing the

V7.1 server” on page 155.

Scenario 2: Uninstalling the V5 program on Linux systems

Linux

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
1. To determine the Tivoli Storage Manager packages that are installed, issue the
following command:
rpm -qa | grep TIVsm
2. Remove the server, server license, and device driver packages. Issue the
following commands:
rpm -e TIVsm-server
rpm -e TIVsm-license
rpm -e TIVsm-tsmscsi

What to do next

After the V5 server program is uninstalled, continue at “Scenario 2: Installing the

V7.1 server” on page 155.

Chapter 5. Scenario 2: Same system, network method 153

Upgrading the server from V5 to V7.1

Scenario 2: Uninstalling the V5 program on Oracle Solaris

systems
Solaris

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure

Issue the following commands:

/usr/sbin/pkgrm TIVsmS
/usr/sbin/pkgrm TIVsmSlic
/usr/sbin/pkgrm TIVsmSdev

What to do next

After the V5 server program is uninstalled, continue at “Scenario 2: Installing the

V7.1 server” on page 155.

Scenario 2: Uninstalling the V5 program on Microsoft

Windows systems
Windows

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

About this task

Do not remove registry entries for the server.

Procedure
1. Click Start > Control Panel > Add or Remove Programs.
2. Select the Tivoli Storage Manager server component, and click Remove. Repeat
for the license and the device driver.
If you see any messages that suggest that you restart the system, ignore them
until the selected Tivoli Storage Manager components are removed.

What to do next

After the V5 server program is uninstalled, continue at “Scenario 2: Installing the

V7.1 server” on page 155.

154 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 2: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

Take the following actions:

v Ensure that you have completed all upgrade preparation steps, including the
database backup. The server that you are upgrading will not be available until
after the installation and upgrade steps are completed.
v Ensure that you retain the installation media from the V5 base release of the
installed server. If you installed Tivoli Storage Manager from a DVD, ensure that
the DVD is available. If you installed Tivoli Storage Manager from a
downloaded package, ensure that the downloaded files are available. If the
upgrade fails, and the server license module is uninstalled, the installation
media from the server base release are required to reinstall the license.

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

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

Procedure
1. Log on to the system.
AIX HPUX Linux Solaris Log in by using the root user ID.
Windows Log on as an administrator. You must be logged on to the system
with the administrative user ID that was used to install the V5 server.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
AIX HPUX Linux Solaris

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:

Chapter 5. Scenario 2: Same system, network method 155

Upgrading the server from V5 to V7.1

v Tivoli Storage Manager: http://www.ibm.com/support/

docview.wss?uid=swg24035122
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035635
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The
path must contain no more than 128 characters. Ensure that you
extract the installation files to an empty directory. Do not extract to
a directory that contains previously extracted files, or any other
files.
Also, ensure that you have executable permission for the package
file.
c. If necessary, change the file permissions by issuing the following
command:
chmod a+x package_name.bin
where package_name is like the following example:

AIX

7.1.0.000-TIV-TSMSRV-AIX.bin

HPUX

7.1.0.000-TIV-TSMSRV-HP-UX.bin

Linux

7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin
7.1.0.000-TIV-TSMSRV-Linuxs390x.bin

Solaris

7.1.0.000-TIV-TSMSRV-SolarisSPARC.bin

In the examples, 7.1.0.000 represents the product release level.

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

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

Windows

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035121
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035636
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035638
b. Change to the directory where you placed the executable file.
In the next step, the files are extracted to the current directory. The
path must contain no more than 128 characters. Ensure that you

156 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

extract the installation files to an empty directory. Do not extract to

a directory that contains previously extracted files, or any other
files.
c. To extract the installation files, double-click the executable file:
package_name.exe
where package_name is like this example:
7.1.0.000-TIV-TSMSRV-Windows.exe
The package is large. Therefore, the extraction takes some time.
4. AIX HPUX To ensure that the Tivoli Storage Manager
Solaris
wizards work correctly, verify that the following command is enabled:
AIX lsuser
HPUX Solaris logins
By default, the command is enabled.
5. If you plan to install the server by using the graphical wizard of IBM
Installation Manager, review the following information and verify that your
system meets the requirements:
v Verify that all required RPM files are installed. For a list of
AIX
required RPM files and instructions about installing RPM files, see the
section about installing Tivoli Storage Manager by using the installation
wizard in the Installation Guide.
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the
installation wizard.
v WindowsThe user ID that you use during installation must be a user with
local Administrator authority.
v Solaris Ensure that the LD_LIBRARY_PATH_64 environment variable is not
set.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
AIX HPUX Linux Solaris

./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

Windows

install.bat -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

6. If you use the installation wizard, complete the following steps to begin the
installation:

Chapter 5. Scenario 2: Same system, network method 157

Upgrading the server from V5 to V7.1

Option Description
Installing from a downloaded package file: 1. Change to the directory where you
downloaded the package file.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat

Installing from DVD media: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat
Windows Or, in the directory where the
installation files were extracted,
double-click the install.bat file.

7. If you are installing the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
8. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
9. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
10. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
11. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.

158 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

12. HPUX Linux Solaris To prevent server failures during interaction

with DB2, tune the kernel parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
13. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
14. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.
Related concepts:
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555

Scenario 2: Creating the directories and the user ID for the upgraded
server instance
Create the directories that the server instance needs for database and recovery logs,
and create the user ID that will own the server instance.

Before you begin

Review the information about planning space for the server before you complete
this task. See “Worksheet for planning space for the V7.1 server” on page 42.

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

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

Restriction: In the user ID, only lowercase letters (a-z), numerals

(0-9), and the underscore character (_) can be used. The user ID and
group name must comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a
numeral.
v The user ID and group name cannot be user, admin, guest, public,
local, or any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The
following examples show how to create this user ID and group by
using operating system commands:
AIX

# mkgroup id=1001 tsmsrvrs

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

HPUX

Chapter 5. Scenario 2: Same system, network method 159

Upgrading the server from V5 to V7.1

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

Linux

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

Solaris

# groupadd tsmsrvrs
# useradd -d /export/home/tsminst1 -m -g tsmsrvrs
-s /bin/ksh tsminst1
# passwd tsminst1
b. Log out and then log in to your system by using the new user ID
and password. Use an interactive login program, such as telnet, so
that you are prompted for the password and can change it if
necessary.
c. If a configuration profile does not exist for the user ID, create the
file. For example, create a .profile file if you are using the Korn
shell (ksh).
Windows
Identify the user account that will own the Tivoli Storage Manager
server instance. When the server is started as a Windows service, this is
the account that the service will log on to. The user account must have
administrative authority on the system. One user account can own
more than one server instance.
You can create a user account, or use an existing account.
If you have multiple servers on one system and want to run each
server with a different user account, create a user account in this step.
a. Create the user ID.

Restriction: The user ID can contain only lowercase letters (a-z),

numerals (0-9), and the underscore character (_). The user ID must
be 30 characters or less, and cannot start with ibm, sql, sys, or a
numeral. The user ID and group name cannot be user, admin, guest,
public, local, or any SQL reserved word.
Use the following command to create the user ID:
net user user_ID * /add

You are prompted to create and verify a password for the new user
ID.
b. Issue the following operating system commands to add the new
user ID to the Administrators groups:
net localgroup Administrators user_ID /add
net localgroup DB2ADMNS user_ID /add
c. Log in to your system, by using the new user ID and password.
d. For all directories that were created for the server instance, ensure
that the user ID for the server instance has read/write access. The
directories to check include the instance directory and all database
and log directories.

160 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

2. Create the directories that the server requires. Ensure that you are logged in
under the new user ID that you created.
You need a unique, empty directory for each item in the following table. Create
the database directories, the active log directory, and the archive log directory
on different physical volumes. For space requirements, see “Worksheet for
planning space for the V7.1 server” on page 42.
AIX HPUX Linux Solaris

Table 39. Worksheet for creating required directories

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

Windows

Table 40. Worksheet for creating required directories

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

Chapter 5. Scenario 2: Same system, network method 161

Upgrading the server from V5 to V7.1

Table 40. Worksheet for creating required directories (continued)

Example commands for
Item creating the directories Your directories
Optional: Secondary mkdir k:\tsm\archlogfailover
archive log directory,
which is the failover
location for the archive
log

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
3. Create additional logical volumes and mount the volumes on the directories
that were created in the previous step.

What to do next

Continue the upgrade process by using one of the following topics:

“Scenario 2: Upgrading the server by using the upgrade wizard”
“Scenario 2: Upgrading the server manually by using utilities” on page 164
Related tasks:
“Planning space for the upgrade process and the upgraded server” on page 37
Related reference:
“Server naming best practices” on page 70

Scenario 2: Upgrading the server by using the upgrade wizard

The wizard offers a guided approach to upgrading a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Start the wizard on the system where you installed the V7.1 server program.

Before you begin

You must complete all preceding steps to prepare for the upgrade, to install the
upgrade utilities, to install the V7.1 server program, and to create the directories
and user ID for the server instance.

Procedure
1. Ensure that the following requirements are met.
AIX HPUX Linux Solaris

v The system must have the X Window client. You must also be
running an X Window server on your desktop.
v The system must have one of the following protocols enabled. Ensure
that the port that the protocol uses is not blocked by a firewall.
– Secure Shell (SSH). Ensure that the port is set to the default value,
22. Also, ensure that the SSH daemon service has access rights for
connecting to the system by using localhost.
– Remote shell (rsh).
– Remote Execution Protocol (REXEC).

162 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

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

v The system where you installed the V7.1 server program must have
the Windows server message block (SMB) protocol enabled. SMB is
the interface that is used by File and Print Sharing (also known as
CIFS). To use the SMB protocol, you must ensure that File and Print
Sharing is enabled, and that port 445 is not blocked by your firewall.
v If the V5 server is on a different system than the V7.1 server, that
system must also have SMB enabled.
v You must be able to log on to the system that has SMB enabled by
using either the user ID that you created for the server instance, or
another user ID that exists on the system. When you use the wizard,
you must provide the user ID and password to access the system.
2. Windows If the system is running on Windows Server 2008, complete the
following steps to disable User Account Control:
a. Ensure that the Remote Registry in Windows Services is started, and ports
445, 137, and 139 are unblocked in the firewall.
b. Configure both the framework server and the targets as members of a
Windows domain. Use a user account in that domain, or in a trusted
domain, when you connect to the target.
c. Connect to the target workstation by enabling and using the built-in
administrator account. To enable the built-in administrator account, click
Control Panel > Administrative Tools > Local Security Policy > Security
Settings > Local Policies > Security Options. Double-click the Accounts:
Administrator account status section. Select Enable and click OK.
d. Click Control Panel > Administrative Tools > Local Security Policy >
Security Settings > Local Policies > Security Options. Double-click the
User Account Control: Run all administrators in Admin Approval Mode
section. Select Disable and click OK.
3. Start the upgrade wizard, dsmupgdx, from the V7.1 server installation directory.
AIX HPUX Linux Solaris
Log in using the root user ID. Issue the command:
/opt/tivoli/tsm/server/bin/dsmupgdx

Windows
Open a new Command Prompt window, and issue the command:
"c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe"
4. Follow the instructions to complete the upgrade. The upgrade wizard can be
stopped and restarted, but the server will not be operational until the entire
upgrade process is complete.

Important: Read all messages that appear for each phase of the upgrade
process, in the message display area within the wizard. Informational messages
might show actions that occurred during the process that are important to you.

What to do next

To complete the upgrade, perform the steps described in Chapter 10, “Taking the
first steps after upgrade,” on page 323.

Chapter 5. Scenario 2: Same system, network method 163

Upgrading the server from V5 to V7.1

Scenario 2: Upgrading the server manually by using utilities

Use the utilities to upgrade the server by using a command interface.

Before you begin

Complete all preceding steps to prepare for the upgrade. Ensure that you have
installed the upgrade utilities, installed the V7.1 server program, and created the
directories and user ID for the server instance.

Procedure

Complete the following steps:

1. “Scenario 2: Creating and formatting the new database”
2. “Scenario 2: Moving the server database over a network” on page 169
3. “Scenario 2: Creating a Windows service for the server instance” on page 170
4. “Scenario 2: Configuring the system for database backup” on page 171

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.
Related concepts:
“DSMUPGRD upgrade utilities” on page 16

Scenario 2: Creating and formatting the new database

Create the server instance and format files for an empty V7.1 database.

Procedure
1. Log on to the system where you installed the V7.1 program.
AIX HPUX Linux Solaris
Log in by using the root user ID. Verify the following items:
v The home directory for the user, /home/tsminst1, exists. If there is
no home directory, you must create it.
The instance directory stores the following core files that are
generated by the Tivoli Storage Manager server:
– The server options file, dsmserv.opt
– The server key database file, cert.kdb, and the .arm files, which
are used by clients and other servers to import the Secure
Sockets Layer certificates of the server
– Device configuration file, if the DEVCONFIG server option does not
specify a fully qualified name
– Volume history file, if the VOLUMEHISTORY server option does not
specify a fully qualified name
– Volumes for DEVTYPE=FILE storage pools, if the directory for
the device class is not fully specified, or not fully qualified
– User exits
– Trace output, if it is not fully qualified
v A shell configuration file, for example, .profile, exists in the home
directory. The root user and instance user ID must have write

164 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

permission to this file. For more information, go to the DB2

Information Center (http://pic.dhe.ibm.com/infocenter/db2luw/
v10r5), and search for information about Linux and UNIX
environment variable settings.
Windows
Log on as an administrator.
2. Create a Tivoli Storage Manager instance by using the db2icrt command.
AIX HPUX Linux Solaris
Enter the following command on one line. For the instance name,
specify the user ID that you created to own the instance:
AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

instance_name instance_name

For example, if the user ID for this instance is tsminst1, use the
following command to create the instance:

AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

tsminst1 tsminst1

Remember: From this point on, use this new user ID when you
configure the Tivoli Storage Manager server. Log out of the root user
ID, and log in using the user ID that is the instance owner.
Windows
Enter the following command on one line. The user account that you
specify becomes the user ID that owns the V7.1 server; this ID is the
instance user ID.
db2icrt -s ese -u user_account instance_name

For example, if the user account is tsminst1 and the server instance is
Server1, enter the following command:
db2icrt -s ese -u tsminst1 server1

The database service for the server instance logs on to the user
account that is specified in this command.

Use the registry key name of the V5 server as the instance name for
the V7.1 server. You are prompted to enter the password for the user
account.
The instance name that you specify on this db2icrt command is the
name that you later specify with the -k option on the DSMSERV
LOADFORMAT command, when you create and format the database and
recovery log.
3. Log on to the system by using the user ID that owns the V7.1 server instance
(the instance user ID).
4. Copy the configuration files to the instance directory that you created for the
new server. The files are the configuration files that you saved from the
original V5 server:
v Device configuration
v Server options file, which is typically named dsmserv.opt

Chapter 5. Scenario 2: Same system, network method 165

Upgrading the server from V5 to V7.1

For example, if you created the instance directory that is shown in the
example in the step to create directories for the V7.1 server, copy the files into
the following directory:
AIX HPUX Linux Solaris /tsminst1
Windowsd:\tsm\server1
Ensure that the user ID that owns the V7.1 server (the instance user ID) has
ownership or read/write permission to the files that you copied.
5. Edit the server options file.
a. Remove any options that are not supported for V7.1. For the list of deleted
options, see Table 29 on page 67.
b. Verify that the server options file contains at least one VOLUMEHISTORY
option and at least one DEVCONFIG option. By specifying these options, you
ensure that a volume history file and a device configuration file are
generated and updated automatically. If you must restore the database,
these files are required.
c. Check whether the server options file includes the TXNGROUPMAX option
with a value, and if it does, what the value is. You might want to change
the current value because the default value for this option changed from
256 to 4096, starting in V6. The increased value can improve the
performance for data movement operations such as storage pool migration
and storage pool backup.
v If the server options file does not include this option, the server
automatically uses the new default value of 4096.
v If the server options file includes a value for this option, the server uses
that specified value. If the specified value is less than 4096, consider
increasing the value, or removing the option so that the new default
value is applied.
6. Change the default path for the database.
AIX HPUX Linux Solaris
Change the default path for the database to be the same as the
instance directory for the server. Issue the command:
db2 update dbm cfg using dftdbpath instance_directory

For example:
db2 update dbm cfg using dftdbpath /tsminst1

Windows
Change the default path for the database to be the drive where the
instance directory for the server is located. Complete the following
steps:
a. Click Start > Programs > IBM DB2 > DB2TSM1 > Command
Line Tools > Command Line Processor.
b. Enter quit to exit the command line processor.
A window with a command prompt opens, with the environment
correctly set up to successfully issue the commands in the next
steps.
c. From the command prompt in that window, issue the following
command to set the environment variable for the server instance
that you are working with:
set db2instance=instance_name

166 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

The instance_name is the same as the instance name that you

specified when you issued the db2icrt command. For example, to
set the environment variable for the Server1 server instance, issue
the following command:
set db2instance=server1
d. Issue the command to set the default drive:
db2 update dbm cfg using dftdbpath instance_location

For example, if the instance directory is d:\tsm\server1, the

instance location is drive d:. Enter the command:
db2 update dbm cfg using dftdbpath d:
7. Modify the library path to use the version of the IBM Global Security Kit
(GSKit) that is installed with the Tivoli Storage Manager server:
AIX Issue the following command:
export LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
AIX HPUX Linux You must update the following files
Solaris
to set the library path when DB2 or the Tivoli Storage Manager server is
started:
v instance_directory/sqllib/usercshrc
v instance_directory/sqllib/userprofile
For the instance_directory/sqllib/usercshrc file, add the following lines:
v AIX

setenv LIBPATH /usr/opt/ibm/gsk8_64/lib64:$LIBPATH

v HPUX Solaris

setenv LD_LIBRARY_PATH /opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

v Linux

setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

For the instance_directory/sqllib/userprofile file, add the following lines:
v AIX

LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
export LIBPATH
v HPUX Solaris

LD_LIBRARY_PATH=/opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
v Linux

LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Verify the library path settings and ensure that the GSKit version is 8.0.14.14
or later. Issue the following commands:
v AIX

echo $LIBPATH
gsk8capicmd_64 -version
gsk8ver_64
v HPUX Linux Solaris

echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64

Chapter 5. Scenario 2: Same system, network method 167

Upgrading the server from V5 to V7.1

If the GSKit version is not 8.0.14.14 or later, you must reinstall the Tivoli
Storage Manager server. The reinstallation ensures that the correct GSKit
version is available.
8. Change to the instance directory that you created for the server.
9. Create and format the database and recovery logs. In the command, specify
the directories that you created for the database and logs. The directories must
be empty.
AIX HPUX Linux Solaris

For example, to get an active log size of 16 GB (16384 MB, the default
size), issue the following command, on one line:
/opt/tivoli/tsm/server/bin/dsmserv loadformat \
dbdir=/tsmdb001,/tsmdb002,/tsmdb003,/tsmdb004 \
activelogsize=16384 activelogdirectory=/tsmlog \
mirrorlogdirectory=/tsmlogmirror archlogdirectory=/tsmarchlog

Windows

For example, to get an active log size of 16 GB (16384 MB, the default
size) for the Server1 server instance, issue the following command, on
one line:
"c:\Program Files\Tivoli\TSM\server\dsmserv" loadformat
dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog
If the server that you are upgrading is not Server1, you must use the
-k option. The -k option specifies the instance name for running this
utility. For example, if the system has more than one server instance
and the instance that you are upgrading is Server2, issue the
command:
"c:\Program Files\Tivoli\TSM\server\dsmserv" -k server2
loadformat dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog

Important: The server instance that you specify must have already
been through all preceding steps for the upgrade process, including
the creation of the database instance (db2icrt command).
10. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39
Related reference:
DSMSERV LOADFORMAT (Format a database)
“Deleted server commands, utilities, and options” on page 65

168 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 2: Moving the server database over a network

Move the database by starting the insertion process for the V7.1 server to accept
the server database. Then, start the extraction process for the V5 server to extract
and send the database.

Before you begin

Ensure that the V5 server and the V7.1 server are not running.

Procedure
1. Start the insertion process on the V7.1 server to accept the database. To monitor
the process, direct the output of the process to a file. For example, start the
server, allowing 60 minutes (the default time) for the other server to contact the
V7.1 server and directing the process output to insert.out, by using this
command:
AIX HPUX Linux Solaris

nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \

sesswait=60 >insert.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\server\dsmserv" insertdb

sesswait=60 1>>insert.out 2>&1

The server starts and waits up to 60 minutes to be contacted by the original

server. Some time might pass during which no messages are issued. During
this time, DB2 operations are running in the background. Optional: To verify
that operations are continuing as expected, monitor the CPU and I/O usage for
the server process and the corresponding DB2 process.
2. Monitor the output of the DSMSERV INSERTDB process. Verify that the DSMSERV
INSERTDB process has issued the following message before continuing to the
next step:
ANR1336I INSERTDB: Ready for connections from the source server

Issue the following command to monitor the process output in the insert.out
file:
tail -f insert.out

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
3. Start the extraction from the original server. Specify the TCP/IP address and
port for the V7.1 server. Direct the output of the process to a file for
monitoring. For example, enter the following command on one line:
AIX

nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 &

HPUX Linux Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 &

Windows

Chapter 5. Scenario 2: Same system, network method 169

Upgrading the server from V5 to V7.1

"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" extractdb hladdress=127.0.0.1

lladdress=1500 1>>extract.out 2>&1
4. Monitor the processes for errors and warning messages, and for items that you
might need to act on. From the instance directory for the server that you are
upgrading, issue the following command to monitor the extraction process:
tail -f extract.out

The length of time that the process runs depends on the size of the database,
the hardware being used, and the network.
5. Examine the process outputs for the extraction and insertion processes to find
the messages that indicate the success or failure of the operations.

Process Success message Failure message

Extraction ANR1382I EXTRACTDB: Process 1, ANR1396E EXTRACTDB: Process 1,
database extract, has database extract, has completed
completed. with errors.
Insertion ANR1395I INSERTDB: Process 1, ANR1396E INSERTDB: Process 1,
database insert, has completed. database insert, has completed
with errors.

Related reference:
“DSMUPGRD EXTRACTDB (Extract data from a V5 server database)” on page 529

“DSMSERV INSERTDB (Move a server database into an empty database)” on page

538

Scenario 2: Creating a Windows service for the server

instance
Windows

A Windows service is created for the Tivoli Storage Manager V7.1 server
automatically if you use the upgrade wizard (dsmupgdx). If you do not use the
wizard, you must create the Windows service for the Tivoli Storage Manager
server manually.

Procedure
1. Change to the installation directory for the server program. By default, the
directory is C:\Program Files\Tivoli\TSM\console. If you installed the server
in a different directory, change to the console subdirectory of the server
installation directory.
2. Install the Windows service by using the Tivoli Storage Manager server
instance name and password in the service name. Issue the following
command:
install "TSM server_instance_name"
"C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
instance_owner instance_owner_password

where:
"TSM server_instance_name" is the name of the service that is being
installed.
server_instance_name is the instance name that was specified when you
issued the db2icrt command.

170 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

instance_owner is the instance owner account; this account will own the
service.
instance_owner_password is the password for the instance owner account.
Example
To install the Windows service for the server1 server instance, enter the
following command on one line. The example uses rudy as the instance
owner and s21ret as the password for the instance owner account.
install "TSM server1" "C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
rudy s21ret
3. Optional: Manually change the service to an automatic startup type by using
Windows administrative tools (Administrative Tools > Services).
Related tasks:
“Starting the server on Windows systems” on page 331

Scenario 2: Configuring the system for database backup

The database manager and the Tivoli Storage Manager API must be configured so
that the database manager can back up the server database. The configuration is
completed for you automatically if you use the upgrade wizard (dsmupgdx). If you
do not use the wizard, you must complete the configuration manually.

Procedure
v “Scenario 2: Configuring the system for database backup on AIX, HP-UX, Linux,
and Oracle Solaris systems”
v “Scenario 2: Configuring the system for database backup on Microsoft Windows
systems” on page 173

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Scenario 2: Configuring the system for database backup on AIX,

HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

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

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

Chapter 5. Scenario 2: Same system, network method 171

Upgrading the server from V5 to V7.1

In the following commands, replace the example values with your actual values.
The examples use tsminst1 for the server instance user ID, /tsminst1 for the Tivoli
Storage Manager server instance directory, and /home/tsminst1 as the home
directory of the server instance user.

Procedure
1. Set the Tivoli Storage Manager API environment-variable configuration for the
database instance:
a. Log in by using the tsminst1 user ID.
b. When user tsminst1 is logged in, ensure that the DB2 environment is
correctly initialized. The DB2 environment is initialized by running the
/home/tsminst1/sqllib/db2profile script, which normally runs
automatically from the profile of the user ID. Ensure that the .profile file
exists in the home directory of the instance user, for example,
/home/tsminst1/.profile. If .profile does not run the db2profile script,
add the following lines:
if [ -f /home/tsminst1/sqllib/db2profile ]; then
. /home/tsminst1/sqllib/db2profile
fi
c. In the instance_directory/sqllib/userprofile file, add the following lines:
DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
DSMI_DIR=server_bin_directory/dbbkapi
DSMI_LOG=server_instance_directory
export DSMI_CONFIG DSMI_DIR DSMI_LOG
d. In the instance_directory/sqllib/usercshrc file, add the following lines:
setenv DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
setenv DSMI_DIR=server_bin_directory/dbbkapi
setenv DSMI_LOG=server_instance_directory
2. Log out and log in again as tsminst1, or issue this command:
. ~/.profile

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

The value for SERVERNAME must be consistent in the tsmdbmgr.opt and dsm.sys
files.
4. Locate the Tivoli Storage Manager API dsm.sys configuration file. By default,
the dsm.sys file is in the following location:

server_bin_directory/dbbkapi/dsm.sys
5. As root user, add the following lines to the dsm.sys configuration file:
servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
errorlogname /tsminst1
nodename $$_TSMDBMGR_$$

where
v servername matches the servername value in the tsmdbmgr.opt file.

172 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

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

where port_number specifies the port that you use for shared memory.
b. In the dsm.sys configuration file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport port_number

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port that you use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Scenario 2: Configuring the system for database backup on

Microsoft Windows systems
Windows

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

Chapter 5. Scenario 2: Same system, network method 173

Upgrading the server from V5 to V7.1

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

In the following commands, the examples use server1 for the database instance
and d:\tsmserver1 for the Tivoli Storage Manager server directory. When you
issue the commands, replace these values with your actual values.

Procedure
1. Create a file that is named tsmdbmgr.env in the d:\tsmserver1 directory with
the following contents:
DSMI_CONFIG=server_instance_directory\tsmdbmgr.opt
DSMI_LOG=server_instance_directory
2. Set the DSMI_ api environment-variable configuration for the database instance:
a. Open a DB2 command window. One method is to go to the C:\Program
Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage
Manager in a different location, go to the db2\bin subdirectory in your main
installation directory. Then, issue the following command:
db2cmd
b. Issue the following command:
db2set -i server1 DB2_VENDOR_INI=d:\tsmserver1\tsmdbmgr.env
c. Create a file that is named tsmdbmgr.opt in the d:\tsmserver1 directory
with the following contents:
*************************************************
nodename $$_TSMDBMGR_$$
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
passwordaccess generate
errorlogname d:\tsmserver1
where
v nodename specifies the node name that the client API uses to connect to
the server during a database backup. To ensure that the database can be
backed up, this value must be $$_TSMDBMGR_$$.
v commmethod specifies the client API that is used to contact the server for
database backup. This value can be tcpip or sharedmem. For more
information about shared memory, see Step 3.
v tcpserveraddr specifies the server address that the client API uses to
contact the server for database backup. To ensure that the database can be
backed up, this value must be localhost.
v tcpport is the port number that the client API uses to contact the server
for database backup. Ensure that you enter the same tcpport value that is
specified in the dsmserv.opt server options file.
v passwordaccess is required to ensure that the backup node can connect to
the server.
v errorlogname is the error log where the client API logs errors that are
encountered during a database backup. This log is typically in the server
instance directory. However, this log can be placed in any location where
the instance user ID has write-permission.
3. Optional: Configure the server to back up the database by using shared
memory. In this way, you might be able to reduce the processor load and
improve throughput. Complete the following steps:

174 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

a. Review the dsmserv.opt file. If the following lines are not in the file, add
them:
commmethod sharedmem
shmport port_number

where port_number specifies the port to use for shared memory.

b. In the tsmdbmgr.opt file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport 1500

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port to use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Chapter 5. Scenario 2: Same system, network method 175

176 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 6. Scenario 3: New system, media method
Use this procedure if you are upgrading the Tivoli Storage Manager server on a
different system than your V5 server, and you are using the media method to
move the data.

Procedure

The procedure for upgrading the server includes the following tasks:
1. “Scenario 3: Preparing for the upgrade”
2. “Scenario 3: Installing the upgrade utilities” on page 186
3. Upgrading the server, by using one of the following methods:
v “Scenario 3: Upgrading the server by using the upgrade wizard” on page 194
v “Scenario 3: Upgrading the server manually by using utilities” on page 202
4. The following tasks are completed after the upgrade:
a. “Verifying access to storage pools on disk” on page 323
b. “Setting up Solaris services for the server instance” on page 324
c. “Configuring server options for server database maintenance” on page 324
d. “Starting the server instance after the upgrade” on page 325
e. “Registering licenses” on page 334
f. “Backing up the database after upgrading the server” on page 335
g. “Verifying the upgraded server” on page 336
h. “Changing the host name for the Tivoli Storage Manager server” on page
336
i. “Updating automation” on page 338
j. “Monitoring the upgraded server” on page 339
k. “Removing GSKit Version 7 after upgrading to Tivoli Storage Manager
V7.1” on page 340

Scenario 3: Preparing for the upgrade

Prepare for the upgrade by checking requirements, preparing the space that is
required, backing up the server, and modifying certain server settings.

About this task

Follow the preparation steps carefully to protect your server and its data.

Important: It is possible, after the upgrade to V7.1 is complete, that conditions

might cause the need to temporarily revert to the previous version of the server.
Successfully reverting to the previous version of the server is possible only if you
have completed all preparation steps. To understand why it is important to
complete all preparation steps, review the procedure for reverting an upgraded
server to its previous version.

Procedure
1. “Scenario 3: Checking the prerequisites for the upgrade” on page 178
2. “Scenario 3: Preparing space for the upgrade process” on page 181

© Copyright IBM Corp. 2009, 2013 177

Upgrading the server from V5 to V7.1

3. “Scenario 3: Modifying the server before the upgrade” on page 182

4. “Scenario 3: Disabling sessions” on page 183
5. “Scenario 3: Backing up storage pools and the server database” on page 184
6. “Scenario 3: Moving the NODELOCK file” on page 184
7. “Scenario 3: Backing up configuration information” on page 185
8. “Scenario 3: Creating a summary of database contents” on page 185
9. “Scenario 3: Stopping the server before installing the upgrade” on page 186
Related tasks:
“Reverting from V7.1 to the previous V5 server version” on page 351

Scenario 3: Checking the prerequisites for the upgrade

Check your system against requirements for the server.

Procedure
1. Ensure that the server that you plan to upgrade is at the V5.5 release level, and
that the latest interim fix is installed. For example, if the server is at V5.5.6,
install the latest interim fix for V5.5.6. Take the following actions:
a. Select the appropriate server level. For detailed guidelines, see
“Determining the appropriate level for a V5 server before an upgrade” on
page 36. If the server is at an appropriate level, no action is required.
b. If the server is not at an appropriate level, download the appropriate server
fix pack and the latest interim fix from the FTP downloads site at
ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server/. Locate the appropriate version of Tivoli Storage
Manager and install it.
2. Ensure that the system where the V5 server is located meets the minimum
requirements. Review the information in “Hardware and software requirements
for the V5 server system that is being upgraded” on page 17 to determine
whether you must update your system before you continue.
3. Ensure that the system where you plan to install the V7.1 server meets
requirements for the operating system type and level. For the latest information
about system requirements, see Tivoli Storage Manager Supported Operating
Systems (http://www.ibm.com/support/docview.wss?uid=swg21243309).
If you are upgrading Tivoli Storage Manager to a different operating system, a
limited set of migration paths is available. For instructions about migrating a
server that is running on a z/OS operating system, see Part 3, “Migrating Tivoli
Storage Manager V5 servers on z/OS systems to V7.1 on AIX or Linux on
System z,” on page 437. For instructions about migrating a server that is
running on an AIX, HP-UX, or Solaris operating system, see Part 2, “Migrating
Tivoli Storage Manager V5 servers on AIX, HP-UX, or Solaris systems to V7.1
on Linux,” on page 355.
Some platforms that were supported for earlier versions of the server are not
supported for V7.1. If the server that you want to upgrade is running on one of
these platforms, you cannot upgrade your server to V7.1 on the same platform.
You must install your V7.1 server on a system that is a specific supported
platform, depending on the original platform. For required platforms, see the
following table.
Table 41. Required platforms for upgrading from V5 to V7.1
Platform for V5 server Required platform for upgrade to V7.1
HP-UX running on a PA-RISC system HP-UX running on an Intel Itanium system

178 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 41. Required platforms for upgrading from V5 to V7.1 (continued)

Platform for V5 server Required platform for upgrade to V7.1
Linux running on an Itanium system (IA64) Linux running on an x86_64 system
Linux running on an x86_32 system Linux running on an x86_64 system
Solaris running on an x86_64 system Linux running on an x86_64 system
Windows running on an Itanium system Windows running on an x86_64 system
(IA64)

If you are upgrading from Tivoli Storage Manager V5 to V7.1 on a new system,
restrictions apply. Ensure that you install the V7.1 server in a compatible
hardware and software environment, as described in the following table.
Table 42. Requirements for upgrading from V5 to V7.1 on a new system
V5 server V7.1 server Comments
AIX running on an IBM AIX running on an IBM
POWER system POWER system
HP-UX running on an HP-UX running on an
Itanium system Itanium system
HP-UX running on a HP-UX running on an HP-UX running on PA-RISC
PA-RISC system Itanium system is not supported for V7.1
servers.
Linux running on an IBM Linux running on an IBM
POWER system POWER system
Linux running on an Itanium Linux running on an x86_64 Linux running on Itanium is
system (IA64) system not supported for V7.1
servers.
Linux running on an x86_32 Linux running on an x86_64 Linux running on x86_32 is
system system not supported for V7.1
servers.
Linux on System z Linux on System z

Chapter 6. Scenario 3: New system, media method 179

Upgrading the server from V5 to V7.1

Table 42. Requirements for upgrading from V5 to V7.1 on a new system (continued)
V5 server V7.1 server Comments
Solaris running on an x86_64 Operating system depends A V7.1 server cannot be
system on the migration method installed on a Solaris x86_64
system. However, you can
migrate a V5 server that is
running on a Solaris x86_64
operating system to V7.1 on
a Linux x86_64 operating
system. For instructions, see
Part 2, “Migrating Tivoli
Storage Manager V5 servers
on AIX, HP-UX, or Solaris
systems to V7.1 on Linux,”
on page 355.

Alternatively, you can

migrate the Solaris x86_64
system by installing a V7.1
server on any operating
system that is supported for
V7.1. Then, use Tivoli
Storage Manager server
EXPORT and IMPORT
commands to move the
server from the V5 source
system to the V7.1 target
system.
Windows running on an Windows running on an Windows running on
Itanium system (IA64) x86_64 system Itanium is not supported for
V7.1 servers.
Windows running on an Windows running on an Windows running on x86_32
x86_32 system x86_64 system is not supported for V7.1
servers.
z/OS AIX or Linux on System z See the section on migrating
from V5 on z/OS to V7.1 on
AIX or Linux on System z.

4. Verify that the system memory meets the server requirements. If you plan to
run multiple instances of the V7.1 server on the system, each instance requires
the memory that is listed for one server. Multiply the memory for one server by
the number of instances that are planned for the system.
For specific information about memory requirements, see the section for your
operating system:
Table 43. Memory requirements for the V7.1 system
Operating system Memory requirements
AIX “Server requirements on AIX systems” on
page 21
HP-UX “Server requirements on HP-UX systems” on
page 24
Linux “Server requirements on Linux systems” on
page 26
Solaris “Server requirements on Solaris systems” on
page 31

180 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 43. Memory requirements for the V7.1 system (continued)

Operating system Memory requirements
Windows “Server requirements on Microsoft Windows
systems” on page 33

5. Ensure that the system has enough disk storage for the database and recovery
logs. Review the planning information for requirements and guidance.
If you are adding new hardware for the server, such as new disk storage for
the database, ensure that the hardware is installed and running.
6. Ensure that the new system can access the storage devices that are used on the
original system. This includes disk and tape devices that are used to store client
data.
You might need to leave a storage device attached to the original system to
perform the database extraction. Then move the storage device to the new
system.
Related concepts:
“Hardware and software requirements for upgrading to the V7.1 server” on page
17

Scenario 3: Preparing space for the upgrade process

Determine the amount and type of space that is required for the upgrade process
before beginning the process.

Procedure
1. Verify that the system has the amount of space that was estimated in the
planning step. Use the planning worksheet that you completed with your
information. See “Worksheet for planning space for the V7.1 server” on page
42.
2. Ensure that you have space available for storing the database and the manifest
file that the extraction process creates.
a. Identify the device class to which you will extract the original database. The
definition must exist in the server database, not just in the device
configuration file. View information about devices classes by issuing the
command:
query devclass format=detailed
The device class must be a sequential device class that has volumes or space
available. Define a new device class if necessary. The device class type
cannot be NAS or CENTERA.

Important: You must confirm now that the definition that is in the server
database for the device class is correct. After you prepare the database for
upgrade (by completing the Prepare Database phase in the upgrade wizard,
or by using the DSMUPGRD PREPAREDB utility), you cannot update this device
class definition. For example, check the path for a FILE device class. If you
copied the original server to a different system to extract the data, the path
might be different on the current system.
b. Ensure that space or volumes are available in the selected device class. The
amount of space that you need is about the same as the current size of the
original database.
For example, if the device class is FILE, ensure that the directory has
sufficient space for your environment. If the device class is TAPE, ensure
that sufficient scratch volumes are available for your environment.

Chapter 6. Scenario 3: New system, media method 181

Upgrading the server from V5 to V7.1

Ensure that the instance user ID that you create for the upgraded server has
access permission to the location of the extracted data.
c. Check that the access permissions are correct for the location that you plan
to specify for the manifest file.
The user ID that will run the database preparation and extraction utilities
(DSMUPGRD PREPAREDB and DSMUPGRD EXTRACTDB) must have write access to
this file. This is typically the root user ID.
When the data is later inserted into the V7.1 database, the instance user ID
that you use for the upgraded server must have access permission for the
manifest file.
The manifest file is typically less than 1 KB.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39

Scenario 3: Modifying the server before the upgrade

A command must be run on the server to prevent one type of problem during the
upgrade process. Some modifications to typical server settings can be useful to
prepare for the upgrade.

Procedure
1. From a Tivoli Storage Manager administrative command line, issue the
command:
convert ussfilespace

This command fixes a problem that might exist in older Tivoli Storage Manager
databases. If the problem does not exist in your database, the command is
completed and you might see error ANR2034E. This error can be ignored. For
more information, see Technote 1408895 (http://www.ibm.com/support/
docview.wss?uid=swg21408895). If the problem exists in your database, the
command might take some time to run.

Important: Do not skip this step. If your database has the problem and you do
not run this command now, the DSMUPGRD PREPAREDB utility fails when you run
it. You must then restart the V5 server and run the CONVERT USSFILESPACE
command before you continue the upgrade process.
2. Review the steps for reverting to the earlier version of the server in the section,
“Reverting from V7.1 to the previous V5 server version” on page 351.
If you must revert to the earlier version after the upgrade to V7.1, the results of
the reversion will be better if you understand the steps and prepare for the
possibility now.
3. Make the following adjustments to settings on your server and clients. These
adjustments must be done to make it possible for you to revert to the original
server after the upgrade, if problems occur.
a. For each sequential-access storage pool, set the REUSEDELAY parameter to the
number of days during which you want to be able to revert to the original
server, if necessary.
For example, if you want to be able to revert to the original server for up to
30 days after the upgrade to V7.1, set the REUSEDELAY parameter to 31 days.
Issue the following administrative command:
update stgpool sequential_access_storage_pool reusedelay=31

182 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

b. For each copy storage pool, set the RECLAIM parameter to 100 (meaning
100%). Issue the following administrative command:
update stgpool copy_storage_pool reclaim=100
c. If you typically use a DELETE VOLHISTORY command to delete database
backups, ensure that the command does not delete database backups too
frequently. The interval between backups should be at least the same
number of days that you set for the REUSEDELAY period for sequential-access
storage pools. For example, to delete database backups every 45 days, issue
the following administrative command:
delete volhist type=dbbackup todate=-45
d. For important clients that use the server, verify that the value for the
schedlogretention client option is set to retain the client schedule log for a
sufficient time. Update the option for clients if needed.
The entries in the client schedule log might be useful if the server must
revert to the original version. If the retention period for the schedule log is
too short, the schedule log information might be deleted too soon.
For example, to prune the log every 45 days and save the log entries, add
the following option:
schedlogretention 45 S
AIX HPUX Linux Solaris Add the option to the dsm.sys file
within a server stanza.
Windows Add the option to the client options file, dsm.opt.

Scenario 3: Disabling sessions

In preparation for the upgrade, prevent activity on the server by disabling new
sessions. Cancel any existing sessions.

About this task

The commands in the following procedure are Tivoli Storage Manager

administrative commands.

Procedure
1. Prevent all clients, storage agents, and other servers from starting new sessions
with the server. Use the commands:
disable sessions client
disable sessions server
For more information about these commands and other Tivoli Storage Manager
administrative commands, see the Administrator's Reference.
2. Verify whether any sessions exist, and notify the users that the server is going
to be stopped. To check for existing sessions, use the command:
query session
3. Cancel sessions that are still running. Use the command:
cancel session all

Chapter 6. Scenario 3: New system, media method 183

Upgrading the server from V5 to V7.1

Scenario 3: Backing up storage pools and the server database

Immediately before upgrading the server, back up primary storage pools to copy
storage pools, and perform a full database backup.

Before you begin

Back up storage pools and the server database by using Tivoli Storage Manager
administrative commands:

Procedure
1. Back up primary storage pools to copy storage pools by using the BACKUP
STGPOOL command:
backup stgpool primary_pool copy_stg

where primary_pool specifies the primary storage pool and copy_stg specifies the
copy storage pool. If you have been performing regular backups of the storage
pools, this step backs up only the data that was added to the primary storage
pools since they were last backed up.
2. Back up the database. The preferred method is to use a snapshot backup. A
snapshot backup is a full database backup that does not interrupt any
scheduled database backups. Issue the command:
backup db type=dbsnapshot devclass=device_class_name

The device class that you specify must exist and have volumes that are
available to it. For example, to perform a snapshot backup of your database to
the TAPECLASS device class by using scratch volumes, enter:
backup db type=dbsnapshot devclass=tapeclass

To use specific volumes instead of scratch volumes, specify the volume names
in the command.

Tip: Consider making two copies of the backup to protect the backup from
media failures. Ensure that at least one full database backup is available onsite.
If you must restore the database after a failed upgrade, having an onsite
backup database saves time.

Scenario 3: Moving the NODELOCK file

To ensure that licensing information is updated during the upgrade process, move
the NODELOCK file from the server instance directory to another directory.

About this task

The NODELOCK file contains the licensing information from the previous Tivoli
Storage Manager installation. This licensing information is replaced when the
upgrade is complete.

Procedure
1. In the server instance directory of your installation, locate the NODELOCK file.
2. Move the NODELOCK file to another directory. For example, you can save it to a
directory where you are saving configuration files from the previous release.

184 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 3: Backing up configuration information

Before you install the new version, back up critical files and information for each
server instance. Store the files in a safe place, on a different system from the
system that is being upgraded or on offline media, such as a CD. The files are
required after the installation of the new software version is complete. You also
need these files if you must revert to the previous version after the upgrade.

Procedure
1. Back up device configuration information to another directory by using the
following Tivoli Storage Manager administrative command:
backup devconfig filenames=file_name

where file_name specifies the file in which to store device configuration

information.
2. Back up volume history information to another directory by using the
following Tivoli Storage Manager administrative command:
backup volhistory filenames=file_name

where file_name specifies the file in which to store volume history information.
Ensure that the volume history includes information about the database backup
that you completed in the preceding steps. For example, issue the following
command:
query volhistory type=dbsnapshot

Review the query output to verify that the time stamp for the database backup
matches the actual time of the backup.
3. Save copies of the following files, which are in the server instance directory:
v Server options file, typically named dsmserv.opt
v dsmserv.dsk

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.
4. In the server instance directory, look for the accounting log file, dsmaccnt.log.
If the file exists, save a copy.
5. Back up any scripts that were used to complete daily housekeeping for the
server. Examine the scripts for changes that are needed after the upgrade.
6. Store the device configuration file, the volume history file, the server options
file, and the other files in a safe place. Ensure that the files are stored on a
different system from the system that is being upgraded, or on offline media.

Scenario 3: Creating a summary of database contents

Create a summary of the contents of the original database. After the upgrade, you
can use the same commands to compare the results and to confirm that the
database contents are intact.

Procedure

Run commands that give a summary of information about your database contents.
For example, issue commands that summarize the file spaces that are being
protected, and save the results. For a list of commands, see “Sample commands to
run for validation of the database upgrade” on page 546.
Related reference:

Chapter 6. Scenario 3: New system, media method 185

Upgrading the server from V5 to V7.1

“Sample commands to run for validation of the database upgrade” on page 546

Scenario 3: Stopping the server before installing the upgrade

Stop all server processes and unmount any tapes that are mounted. Then, stop the
server.

Procedure

Use Tivoli Storage Manager administrative commands to stop the server:

1. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the following commands:
query process
cancel process process_number

Allow time for the processes to be stopped. Some processes, such as storage
pool migration, might take some time to stop.
For more information about the QUERY PROCESS and CANCEL PROCESS commands
and other Tivoli Storage Manager administrative commands, see the
Administrator's Reference.
2. After all sessions and processes are stopped, determine whether any tapes are
mounted. Unmount any tapes that are mounted. Use the following commands:
query mount
dismount volume volume_name
3. Stop the server. Use the following command:
halt

Scenario 3: Installing the upgrade utilities

You must install the upgrade utilities on the system where the V5 server is located.
The installation package for the utilities must be downloaded from a website.

Before you begin

The preferred method is to install the latest available version of the upgrade
utilities. For more information about selecting the version, see “Determining the
appropriate level for a V5 server before an upgrade” on page 36.

Procedure

Use the procedure for your operating system:

v AIX “Scenario 3: Installing the upgrade utilities on AIX systems” on page
187
v HPUX “Scenario 3: Installing the upgrade utilities on HP-UX systems” on
page 188
v Linux “Scenario 3: Installing the upgrade utilities on Linux systems” on page
189
v Solaris “Scenario 3: Installing the upgrade utilities on Oracle Solaris systems”
on page 191
v Windows“Scenario 3: Installing the upgrade utilities on Microsoft Windows
systems” on page 193
Related concepts:
“DSMUPGRD upgrade utilities” on page 16
186 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 3: Installing the upgrade utilities on AIX systems

AIX

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The
5.5.x.x number must be the same as or later than the level of the V5
server that you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-AIX.tar.gz
The numbers at the beginning of the package name identify the release
level of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Ensure that the system has the following file sets installed:
xlC.rte 8.0.0.5, or later
gsksa.rte 7.0.4.11
You can use the following commands to check for these file sets:
lslpp -L xlC.rte

lslpp -L gsksa.rte

If needed, you can obtain the gsksa.rte file set from any of the regular V5.5
maintenance packages for the AIX server. The maintenance packages are
available on the FTP downloads site: ftp://public.dhe.ibm.com/storage/tivoli-
storage-management/maintenance/server/v5r5/AIX/
4. Extract the contents of the upgrade utilities package. If you downloaded a
language package, also extract the contents of that package.
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Access the System Management Interface Tool (SMIT).
a. Enter smitty install_update
b. Select Install and Update Software > Install and Update from ALL
Available Software.
7. Select the INPUT device. Specify the directory location of the upgrade utilities
package on the system.
8. Select Software to Install. Press F4 or Esc+4 for the list of available file sets in
the directory.

Chapter 6. Scenario 3: New system, media method 187

Upgrading the server from V5 to V7.1

9. Select the file sets for the upgrade utilities, the device driver, and optionally
the language package. The file set for the upgrade utilities is
tivoli.tsmupg.server. Optional language packages include messages for
languages other than US English.
10. Set COMMIT software updates to Yes. Press F4 or Esc+4.
11. Set SAVE replaced files to No.
12. Ensure that the default settings for the options in the window for all the
selected file sets show success.
13. Press Enter, and respond to the ARE YOU SURE? question by pressing Enter
again. The installation begins.
14. When the installation is complete, exit the SMIT program.
15. Optional: If you installed a language package, ensure that the locale
environment variable is set to use it. Enter the following command to set the
locale environment variable for messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
16. After the upgrade utilities are installed, continue at “Scenario 3: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 192

Scenario 3: Installing the upgrade utilities on HP-UX systems

HPUX

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.gz
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.

188 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

d. Optional: To install messages in a language other than English, open the

LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
gzip -dc package_name.tar.gz | tar -xvf -
4. Navigate to the directory that corresponds to the processor architecture of the
operating system.
5. Install the upgrade utilities and the device driver. Use the source argument (-s)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
swinstall -s /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin.

6. Optional: Install the language package.
a. Extract the contents of the package.
gzip -d package_name.img.gz
b. Install the package. For example, if the directory is /tmp/TSM, issue the
command:
swinstall -s /tmp/TSM/package_name.img package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Scenario 3: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 192

Scenario 3: Installing the upgrade utilities on Linux systems

Linux

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/

Chapter 6. Scenario 3: New system, media method 189

Upgrading the server from V5 to V7.1

b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Open the directory for your operating system and download the package.
The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.bz2
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the commands:
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
4. Navigate to the directory that corresponds to the processor architecture of the
operating system, for example, x86_64.
5. Install the upgrade utilities and the device driver. Use the following command:
rpm -ivh package_name.rpm
The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by
default.
6. Optional: Install the language package.
a. Extract the contents of the downloaded package.
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
b. Install the package for the language that you want to use.
rpm -ivh package_name.rpm
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Scenario 3: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 192

190 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 3: Installing the upgrade utilities on Oracle Solaris

systems
Solaris

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

About this task

Restriction: Do not install the utilities in the installation directory of the server that
must be upgraded. Install the utilities package in its own directory.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.Z
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Change to the directory where the upgrade utilities package was downloaded.
4. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
uncompress -c package_name.tar.Z | tar -xvf -
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Install the upgrade utilities and the device driver. Use the source argument (-d)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
pkgadd -d . /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by

default.
7. Optional: Install the language package.
a. Extract the contents of the downloaded package.
uncompress package_name.pkg.Z
b. Install the package for the language that you want to use. Use the source
argument (-d) to specify the directory where the package was extracted. For
example, if the directory is /tmp/TSM, issue the command:

Chapter 6. Scenario 3: New system, media method 191

Upgrading the server from V5 to V7.1

pkgadd -d /tmp/TSM package_name.pkg package_name

c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
8. After the upgrade utilities are installed, continue at “Scenario 3: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems”

Scenario 3: Setting environment variables for the upgrade

utilities on AIX, HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

After installing the upgrade utility package, you must set environment variables in
the shell from which you will run the utilities. An environment variable describes
the operating environment of a process, such as the home directory or terminal in
use.

About this task

The DSMSERV_DIR variable specifies the installed location of the upgrade utilities. By
default, the location is the following directory:

AIX

/usr/tivoli/tsm/upgrade/bin

HPUX Linux Solaris

/opt/tivoli/tsm/upgrade/bin

Procedure

Use the appropriate command for your system to set the environment variable for
running the utilities. If the shell is in the ksh or bash family, enter the following
command to set the DSMSERV_DIR variable:
export DSMSERV_DIR=upgrade_utilities_directory

If your shell is in the csh family, use the following command:

setenv DSMSERV_DIR upgrade_utilities_directory

where upgrade_utilities_directory is the directory where the upgrade utilities are

installed.

192 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

What to do next

After you set the environment variables, continue the upgrade process using one of
the following topics:
v “Scenario 3: Upgrading the server by using the upgrade wizard” on page 194
v “Scenario 3: Upgrading the server manually by using utilities” on page 202

Scenario 3: Installing the upgrade utilities on Microsoft

Windows systems
Windows

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/WIN
b. Open the 5.5.x.x directory. The 5.5.x.x number must be the same as or
later than the level of the V5 server that you are upgrading.
c. Select the package and download it to a convenient location on the server
system. The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-Windows.exe
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, install the
language package that your installation requires.
2. Log on with an administrator ID.
3. Run the executable package for the upgrade utilities.
The default location for the installation of the utilities is based on the location
where the V5 server was last installed. For example, if the V5 server was
installed using the default path, C:\Program Files\Tivoli\TSM\server, the
upgrade utilities are installed in C:\Program Files\Tivoli\TSM\upgrade.

Restriction: Do not install the utilities in the same directory as the original
server that must be upgraded. Install the utilities package in its own directory.

What to do next

After the upgrade utilities are installed, continue the upgrade process using one of
the following topics:
v “Scenario 3: Upgrading the server by using the upgrade wizard” on page 194
v “Scenario 3: Upgrading the server manually by using utilities” on page 202

Tip: When you use the upgrade utilities, if you have multiple servers running
on the system, you must use the -k option to specify the name of the Windows
registry key from which to retrieve information about the server being
upgraded. The default value for the option is SERVER1.

Chapter 6. Scenario 3: New system, media method 193

Upgrading the server from V5 to V7.1

Scenario 3: Upgrading the server by using the upgrade wizard

The wizard offers a guided approach to upgrading a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Start the wizard on the system where you installed the V7.1 server program.

Before you begin

You must complete all preceding steps to prepare for the upgrade and to install the
upgrade utilities. The V7.1 server must be installed, and directories and the user ID
must be created before you start the upgrade wizard.

Procedure

Complete the following steps:

1. Scenario 3: Installing the V7.1 server
2. Scenario 3: Creating the directories and the user ID for the upgraded server
instance
3. “Scenario 3: Starting the upgrade wizard” on page 201

Scenario 3, wizard: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

Procedure
1. Log on to the system.
AIX HPUX Linux Solaris Log in by using the root user ID.
Windows Log on as an administrator. You must be logged on to the system
with the administrative user ID that was used to install the V5 server.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.

194 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

3. If you are downloading the package from one of the download sites, complete
the following steps:
AIX HPUX Linux Solaris

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

AIX

7.1.0.000-TIV-TSMSRV-AIX.bin

HPUX

7.1.0.000-TIV-TSMSRV-HP-UX.bin

Linux

7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin
7.1.0.000-TIV-TSMSRV-Linuxs390x.bin

Solaris

7.1.0.000-TIV-TSMSRV-SolarisSPARC.bin

In the examples, 7.1.0.000 represents the product release level.

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

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

Windows

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035121
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035636

Chapter 6. Scenario 3: New system, media method 195

Upgrading the server from V5 to V7.1

v System Storage Archive Manager: http://www.ibm.com/

support/docview.wss?uid=swg24035638
b. Change to the directory where you placed the executable file.
In the next step, the files are extracted to the current directory. The
path must contain no more than 128 characters. Ensure that you
extract the installation files to an empty directory. Do not extract to
a directory that contains previously extracted files, or any other
files.
c. To extract the installation files, double-click the executable file:
package_name.exe
where package_name is like this example:
7.1.0.000-TIV-TSMSRV-Windows.exe
The package is large. Therefore, the extraction takes some time.
4. AIX HPUX Solaris To ensure that the Tivoli Storage Manager
wizards work correctly, verify that the following command is enabled:
AIX lsuser
HPUX Solaris logins
By default, the command is enabled.
5. If you plan to install the server by using the graphical wizard of IBM
Installation Manager, review the following information and verify that your
system meets the requirements:
v AIX Verify that all required RPM files are installed. For a list of
required RPM files and instructions about installing RPM files, see the
section about installing Tivoli Storage Manager by using the installation
wizard in the Installation Guide.
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the
installation wizard.
v Windows The user ID that you use during installation must be a user with
local Administrator authority.
v Solaris Ensure that the LD_LIBRARY_PATH_64 environment variable is not
set.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
AIX HPUX Linux Solaris

./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

Windows

install.bat -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

6. If you use the installation wizard, complete the following steps to begin the
installation:

196 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Option Description
Installing from a downloaded package file: 1. Change to the directory where you
downloaded the package file.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat

Installing from DVD media: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat
Windows Or, in the directory where the
installation files were extracted,
double-click the install.bat file.

7. If you are installing the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
8. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
9. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
10. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
11. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.

Chapter 6. Scenario 3: New system, media method 197

Upgrading the server from V5 to V7.1

12. HPUX Linux Solaris To prevent server failures during interaction

with DB2, tune the kernel parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
13. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
14. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.
Related concepts:
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555

Scenario 3, wizard: Creating the directories and the user ID

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

Before you begin

Review the information about planning space for the server before you complete
this task. See “Worksheet for planning space for the V7.1 server” on page 42.

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

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

Restriction: In the user ID, only lowercase letters (a-z), numerals

(0-9), and the underscore character (_) can be used. The user ID and
group name must comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a
numeral.
v The user ID and group name cannot be user, admin, guest, public,
local, or any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The
following examples show how to create this user ID and group by
using operating system commands:
AIX

# mkgroup id=1001 tsmsrvrs

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

HPUX

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

198 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Linux

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

Solaris

# groupadd tsmsrvrs
# useradd -d /export/home/tsminst1 -m -g tsmsrvrs
-s /bin/ksh tsminst1
# passwd tsminst1
b. Log out and then log in to your system by using the new user ID
and password. Use an interactive login program, such as telnet, so
that you are prompted for the password and can change it if
necessary.
c. If a configuration profile does not exist for the user ID, create the
file. For example, create a .profile file if you are using the Korn
shell (ksh).
Windows
Identify the user account that will own the Tivoli Storage Manager
server instance. When the server is started as a Windows service, this is
the account that the service will log on to. The user account must have
administrative authority on the system. One user account can own
more than one server instance.
You can create a user account, or use an existing account.
If you have multiple servers on one system and want to run each
server with a different user account, create a user account in this step.
a. Create the user ID.

Restriction: The user ID can contain only lowercase letters (a-z),

numerals (0-9), and the underscore character (_). The user ID must
be 30 characters or less, and cannot start with ibm, sql, sys, or a
numeral. The user ID and group name cannot be user, admin, guest,
public, local, or any SQL reserved word.
Use the following command to create the user ID:
net user user_ID * /add

You are prompted to create and verify a password for the new user
ID.
b. Issue the following operating system commands to add the new
user ID to the Administrators groups:
net localgroup Administrators user_ID /add
net localgroup DB2ADMNS user_ID /add
c. Log in to your system, by using the new user ID and password.
d. For all directories that were created for the server instance, ensure
that the user ID for the server instance has read/write access. The
directories to check include the instance directory and all database
and log directories.
2. Create the directories that the server requires. Ensure that you are logged in
under the new user ID that you created.
You need a unique, empty directory for each item in the following table. Create
the database directories, the active log directory, and the archive log directory

Chapter 6. Scenario 3: New system, media method 199

Upgrading the server from V5 to V7.1

on different physical volumes. For space requirements, see “Worksheet for

planning space for the V7.1 server” on page 42.
AIX HPUX Linux Solaris

Table 44. Worksheet for creating required directories

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

Windows

Table 45. Worksheet for creating required directories

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

200 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
3. Create additional logical volumes and mount the volumes on the directories
that were created in the previous step.
Related tasks:
“Planning space for the upgrade process and the upgraded server” on page 37
Related reference:
“Server naming best practices” on page 70

Scenario 3: Starting the upgrade wizard

The wizard offers a guided approach to upgrading a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Start the wizard on the system where you installed the V7.1 server program.

Before you begin

You must complete all preceding steps to prepare for the upgrade, to install the
upgrade utilities, to install the V7.1 server program, and to create the directories
and user ID for the server instance.

Procedure
1. Ensure that the following requirements are met.
AIX HPUX Linux Solaris

v The system where you installed the V7.1 server program must have
the X Window client. You must also be running an X Window server
on your desktop.
v The systems must have one of the following protocols enabled.
Ensure that the port that the protocol uses is not blocked by a
firewall.
– Secure Shell (SSH). Ensure that the port is set to the default value,
22. Also, ensure that the SSH daemon service has access rights for
connecting to the system by using localhost.
– Remote shell (rsh).
– Remote Execution Protocol (REXEC).
v You must be able to log in to the V7.1 system with the user ID that
you created for the server instance, using the SSH, RSH, or REXEC
protocol. When using the wizard, you must provide this user ID and
password to access that system.
Windows

v The system where you installed the V7.1 server program must have
the Windows server message block (SMB) protocol enabled. SMB is
the interface that is used by File and Print Sharing (also known as
CIFS). To use the SMB protocol, you must ensure that File and Print
Sharing is enabled, and that port 445 is not blocked by your firewall.
v If the V5 server is on a different system than the V7.1 server, that
system must also have SMB enabled.
v You must be able to log on to the system that has SMB enabled by
using either the user ID that you created for the server instance, or

Chapter 6. Scenario 3: New system, media method 201

Upgrading the server from V5 to V7.1

another user ID that exists on the system. When you use the wizard,
you must provide the user ID and password to access the system.
2. WindowsIf the system is running on Windows Server 2008, complete the
following steps to disable User Account Control:
a. Ensure that the Remote Registry in Windows Services is started, and ports
445, 137, and 139 are unblocked in the firewall.
b. Configure both the framework server and the targets as members of a
Windows domain. Use a user account in that domain, or in a trusted
domain, when you connect to the target.
c. Connect to the target workstation by enabling and using the built-in
administrator account. To enable the built-in administrator account, click
Control Panel > Administrative Tools > Local Security Policy > Security
Settings > Local Policies > Security Options. Double-click the Accounts:
Administrator account status section. Select Enable and click OK.
d. Click Control Panel > Administrative Tools > Local Security Policy >
Security Settings > Local Policies > Security Options. Double-click the
User Account Control: Run all administrators in Admin Approval Mode
section. Select Disable and click OK.
3. Start the upgrade wizard, dsmupgdx, from the V7.1 server installation directory.
AIX HPUX Linux Solaris
Log in using the root user ID. Issue the command:
/opt/tivoli/tsm/server/bin/dsmupgdx

Windows
Open a new Command Prompt window, and issue the command:
"c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe"
4. Follow the instructions to complete the upgrade. The upgrade wizard can be
stopped and restarted, but the server will not be operational until the entire
upgrade process is complete.

Important: Read all messages that appear for each phase of the upgrade
process, in the message display area within the wizard. Informational messages
might show actions that occurred during the process that are important to you.

What to do next

To complete the upgrade, perform the steps described in Chapter 10, “Taking the
first steps after upgrade,” on page 323.

Scenario 3: Upgrading the server manually by using utilities

Use the utilities to upgrade the server by using a command interface.

Before you begin

Complete all preceding steps to prepare for the upgrade and to install the upgrade
utilities.

Procedure

Complete the following steps:

1. “Scenario 3: Preparing the database of a V5 server for upgrade” on page 203
2. “Scenario 3: Extracting the data to media” on page 204
202 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

3. Scenario 3: Installing the V7.1 server

4. Scenario 3: Creating the directories and the user ID for the upgraded server
instance
5. “Scenario 3: Creating and formatting the new database” on page 212
6. “Scenario 3: Loading the extracted data into the new database” on page 216
7. “Scenario 3: Creating a Windows service for the server instance” on page 218
8. “Scenario 3: Configuring the system for database backup” on page 219

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.
Related concepts:
“The manifest file for the data extraction to media” on page 531
“DSMUPGRD upgrade utilities” on page 16

Scenario 3: Preparing the database of a V5 server for upgrade

Before you extract the data from the database, you must prepare the server
database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a
single system, you must repeat this task for each server.

Procedure
1. Ensure that you have completed all preparation steps.
2. Log in using the root user ID on the system that has the original server. Log on
with the administrator ID on a Windows system.
3. Change to the instance directory for the server that you are upgrading. The
instance directory is the directory that contains the files such as dsmserv.dsk for
the server.

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.
4. Prepare the database. Direct the output of the process to a file for monitoring.
AIX
From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

HPUX Linux Solaris

From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

Windows
From the instance directory for the server that you are upgrading, issue
the following command to run the process and direct the output to the
file called prepare.out:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd"
preparedb 1>>prepare.out 2>&1

Chapter 6. Scenario 3: New system, media method 203

Upgrading the server from V5 to V7.1

If multiple servers exist on the system, issue the command from the
instance directory for the server that you want to prepare. Specify the
registry key for that server. For example, if the server is SERVER2:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" -k server2
preparedb 1>>prepare.out 2>&1
5. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation. From the instance directory for the
server that you are upgrading, issue the following command to monitor the
process:
tail -f prepare.out

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
6. Ensure that the prepare operation is completed successfully before you continue
to the next step. If the prepare operation fails, you might need to restart the V5
server to fix the problem and run the prepare operation again. If the server that
is being upgraded is a V5.3 or V5.4 server, you might need to restore the
database by using a backup before you can restart the server to correct the
problem.
Related reference:
“DSMUPGRD PREPAREDB (Prepare a V5 database for upgrade)” on page 523

Scenario 3: Extracting the data to media

You can extract the data from the original server database to sequential media. The
sequential media can be tape, or disk space that is defined with the FILE device
class.

Procedure
1. Log in using the root user ID on the system that has the original server. Log on
with the administrator ID on a Windows system.
2. Ensure that the device that you want to use to store the extracted data is
available. The server database and the device configuration file must contain a
valid device class definition for the device.
3. From the instance directory for the server that you are upgrading, issue the
command to start the extraction. Direct the output of the process to a file for
monitoring. For example, issue the following command on one line:
AIX

nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

devclass=file manifest=./manifest.txt >extract.out 2>&1 &

HPUX Linux Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

devclass=file manifest=./manifest.txt >extract.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" extractdb

devclass=file manifest=.\manifest.txt 1>>extract.out 2>&1

Tip: Messages that are issued during the extract operation are not saved in the
server activity log. Direct the output of the utility to a file, as shown in the
examples, to record the messages.
204 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

4. Monitor the process for errors and warning messages, and for items that you
might need to take action on. A message near the end of the process output
indicates success or failure of the operation:
Success message: ANR1382I EXTRACTDB: Process 1, database extract, has
completed.
Failure message: ANR1396E EXTRACTDB: Process 1, database extract, has
completed with errors.
For example, from the instance directory for the server that you are upgrading,
issue the following command to monitor the process:
tail -f extract.out
The length of time that the process runs depends on the size of the database.
The time will be approximately as much as the time required for a full backup
of the database.

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
Related concepts:
“The manifest file for the data extraction to media” on page 531
Related tasks:
“Scenario 3: Preparing space for the upgrade process” on page 181
Related reference:
“DSMUPGRD EXTRACTDB (Extract data from a V5 server database)” on page 529

Scenario 3, manual: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

Procedure
1. Log on to the system.
AIX HPUX Linux Solaris Log in by using the root user ID.
Windows Log on as an administrator. You must be logged on to the system
with the administrative user ID that was used to install the V5 server.

Chapter 6. Scenario 3: New system, media method 205

Upgrading the server from V5 to V7.1

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

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

AIX

7.1.0.000-TIV-TSMSRV-AIX.bin

HPUX

7.1.0.000-TIV-TSMSRV-HP-UX.bin

Linux

7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin
7.1.0.000-TIV-TSMSRV-Linuxs390x.bin

Solaris

7.1.0.000-TIV-TSMSRV-SolarisSPARC.bin

In the examples, 7.1.0.000 represents the product release level.

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

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

206 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Windows

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035121
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035636
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035638
b. Change to the directory where you placed the executable file.
In the next step, the files are extracted to the current directory. The
path must contain no more than 128 characters. Ensure that you
extract the installation files to an empty directory. Do not extract to
a directory that contains previously extracted files, or any other
files.
c. To extract the installation files, double-click the executable file:
package_name.exe
where package_name is like this example:
7.1.0.000-TIV-TSMSRV-Windows.exe
The package is large. Therefore, the extraction takes some time.
4. AIX HPUX Solaris To ensure that the Tivoli Storage Manager
wizards work correctly, verify that the following command is enabled:
AIX lsuser
HPUX Solaris logins
By default, the command is enabled.
5. If you plan to install the server by using the graphical wizard of IBM
Installation Manager, review the following information and verify that your
system meets the requirements:
v Verify that all required RPM files are installed. For a list of
AIX
required RPM files and instructions about installing RPM files, see the
section about installing Tivoli Storage Manager by using the installation
wizard in the Installation Guide.
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the
installation wizard.
v The user ID that you use during installation must be a user with
Windows
local Administrator authority.
v Solaris Ensure that the LD_LIBRARY_PATH_64 environment variable is not
set.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
AIX HPUX Linux Solaris

./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

Windows

Chapter 6. Scenario 3: New system, media method 207

Upgrading the server from V5 to V7.1

install.bat -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

6. If you use the installation wizard, complete the following steps to begin the
installation:

Option Description
Installing from a downloaded package file: 1. Change to the directory where you
downloaded the package file.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat

Installing from DVD media: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat
Windows Or, in the directory where the
installation files were extracted,
double-click the install.bat file.

7. If you are installing the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
8. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
9. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
10. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.

208 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

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

http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.
12. HPUX Linux To prevent server failures during interaction
Solaris
with DB2, tune the kernel parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
13. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
14. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.
Related concepts:
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555

Scenario 3, manual: Creating the directories and the user ID

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

Before you begin

Review the information about planning space for the server before you complete
this task. See “Worksheet for planning space for the V7.1 server” on page 42.

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

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

Restriction: In the user ID, only lowercase letters (a-z), numerals

(0-9), and the underscore character (_) can be used. The user ID and
group name must comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a
numeral.
v The user ID and group name cannot be user, admin, guest, public,
local, or any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The
following examples show how to create this user ID and group by
using operating system commands:
AIX

# mkgroup id=1001 tsmsrvrs

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

Chapter 6. Scenario 3: New system, media method 209

Upgrading the server from V5 to V7.1

HPUX

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

Linux

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

Solaris

# groupadd tsmsrvrs
# useradd -d /export/home/tsminst1 -m -g tsmsrvrs
-s /bin/ksh tsminst1
# passwd tsminst1
b. Log out and then log in to your system by using the new user ID
and password. Use an interactive login program, such as telnet, so
that you are prompted for the password and can change it if
necessary.
c. If a configuration profile does not exist for the user ID, create the
file. For example, create a .profile file if you are using the Korn
shell (ksh).
Windows
Identify the user account that will own the Tivoli Storage Manager
server instance. When the server is started as a Windows service, this is
the account that the service will log on to. The user account must have
administrative authority on the system. One user account can own
more than one server instance.
You can create a user account, or use an existing account.
If you have multiple servers on one system and want to run each
server with a different user account, create a user account in this step.
a. Create the user ID.

Restriction: The user ID can contain only lowercase letters (a-z),

numerals (0-9), and the underscore character (_). The user ID must
be 30 characters or less, and cannot start with ibm, sql, sys, or a
numeral. The user ID and group name cannot be user, admin, guest,
public, local, or any SQL reserved word.
Use the following command to create the user ID:
net user user_ID * /add

You are prompted to create and verify a password for the new user
ID.
b. Issue the following operating system commands to add the new
user ID to the Administrators groups:
net localgroup Administrators user_ID /add
net localgroup DB2ADMNS user_ID /add
c. Log in to your system, by using the new user ID and password.

210 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

d. For all directories that were created for the server instance, ensure
that the user ID for the server instance has read/write access. The
directories to check include the instance directory and all database
and log directories.
2. Create the directories that the server requires. Ensure that you are logged in
under the new user ID that you created.
You need a unique, empty directory for each item in the following table. Create
the database directories, the active log directory, and the archive log directory
on different physical volumes. For space requirements, see “Worksheet for
planning space for the V7.1 server” on page 42.
AIX HPUX Linux Solaris

Table 46. Worksheet for creating required directories

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

Windows

Table 47. Worksheet for creating required directories

Example commands for
Item creating the directories Your directories
The instance directory for mkdir d:\tsm\server1
the server, which will
contain files for this
server instance, including
the server options file
The database directories mkdir d:\tsm\db001
mkdir e:\tsm\db002
mkdir f:\tsm\db003
mkdir g:\tsm\db004
Active log directory mkdir h:\tsm\log
Archive log directory mkdir i:\tsm\archlog

Chapter 6. Scenario 3: New system, media method 211

Upgrading the server from V5 to V7.1

Table 47. Worksheet for creating required directories (continued)

Example commands for
Item creating the directories Your directories
Optional: Directory for mkdir j:\tsm\logmirror
the log mirror for the
active log
Optional: Secondary mkdir k:\tsm\archlogfailover
archive log directory,
which is the failover
location for the archive
log

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
3. Create additional logical volumes and mount the volumes on the directories
that were created in the previous step.
Related tasks:
“Planning space for the upgrade process and the upgraded server” on page 37
Related reference:
“Server naming best practices” on page 70

Scenario 3: Creating and formatting the new database

Create the server instance and format files for an empty V7.1 database.

Procedure
1. Log on to the system where you installed the V7.1 program.
AIX HPUX Linux Solaris
Log in by using the root user ID. Verify the following items:
v The home directory for the user, /home/tsminst1, exists. If there is
no home directory, you must create it.
The instance directory stores the following core files that are
generated by the Tivoli Storage Manager server:
– The server options file, dsmserv.opt
– The server key database file, cert.kdb, and the .arm files, which
are used by clients and other servers to import the Secure
Sockets Layer certificates of the server
– Device configuration file, if the DEVCONFIG server option does not
specify a fully qualified name
– Volume history file, if the VOLUMEHISTORY server option does not
specify a fully qualified name
– Volumes for DEVTYPE=FILE storage pools, if the directory for
the device class is not fully specified, or not fully qualified
– User exits
– Trace output, if it is not fully qualified
v A shell configuration file, for example, .profile, exists in the home
directory. The root user and instance user ID must have write
permission to this file. For more information, go to the DB2

212 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Information Center (http://pic.dhe.ibm.com/infocenter/db2luw/

v10r5), and search for information about Linux and UNIX
environment variable settings.
Windows
Log on as an administrator.
2. Create a Tivoli Storage Manager instance by using the db2icrt command.
AIX HPUX Linux Solaris
Enter the following command on one line. For the instance name,
specify the user ID that you created to own the instance:
AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

instance_name instance_name

For example, if the user ID for this instance is tsminst1, use the
following command to create the instance:

AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

tsminst1 tsminst1

Remember: From this point on, use this new user ID when you
configure the Tivoli Storage Manager server. Log out of the root user
ID, and log in using the user ID that is the instance owner.
Windows
Enter the following command on one line. The user account that you
specify becomes the user ID that owns the V7.1 server; this ID is the
instance user ID.
db2icrt -s ese -u user_account instance_name

For example, if the user account is tsminst1 and the server instance is
Server1, enter the following command:
db2icrt -s ese -u tsminst1 server1

The database service for the server instance logs on to the user
account that is specified in this command.

Use the registry key name of the V5 server as the instance name for
the V7.1 server. You are prompted to enter the password for the user
account.
The instance name that you specify on this db2icrt command is the
name that you later specify with the -k option on the DSMSERV
LOADFORMAT command, when you create and format the database and
recovery log.
3. Log on to the system by using the user ID that owns the V7.1 server instance
(the instance user ID).
4. Copy the configuration files to the instance directory that you created for the
new server. The files are the configuration files that you saved from the
original V5 server:
v Device configuration
v Server options file, which is typically named dsmserv.opt

Chapter 6. Scenario 3: New system, media method 213

Upgrading the server from V5 to V7.1

For example, if you created the instance directory that is shown in the
example in the step to create directories for the V7.1 server, copy the files into
the following directory:
AIX HPUX Linux Solaris /tsminst1
Windowsd:\tsm\server1
Ensure that the user ID that owns the V7.1 server (the instance user ID) has
ownership or read/write permission to the files that you copied.
5. Edit the server options file.
a. Remove any options that are not supported for V7.1. For the list of deleted
options, see Table 29 on page 67.
b. Verify that the server options file contains at least one VOLUMEHISTORY
option and at least one DEVCONFIG option. By specifying these options, you
ensure that a volume history file and a device configuration file are
generated and updated automatically. If you must restore the database,
these files are required.
c. Check whether the server options file includes the TXNGROUPMAX option
with a value, and if it does, what the value is. You might want to change
the current value because the default value for this option changed from
256 to 4096, starting in V6. The increased value can improve the
performance for data movement operations such as storage pool migration
and storage pool backup.
v If the server options file does not include this option, the server
automatically uses the new default value of 4096.
v If the server options file includes a value for this option, the server uses
that specified value. If the specified value is less than 4096, consider
increasing the value, or removing the option so that the new default
value is applied.
6. Change the default path for the database.
AIX HPUX Linux Solaris
Change the default path for the database to be the same as the
instance directory for the server. Issue the command:
db2 update dbm cfg using dftdbpath instance_directory

For example:
db2 update dbm cfg using dftdbpath /tsminst1

Windows
Change the default path for the database to be the drive where the
instance directory for the server is located. Complete the following
steps:
a. Click Start > Programs > IBM DB2 > DB2TSM1 > Command
Line Tools > Command Line Processor.
b. Enter quit to exit the command line processor.
A window with a command prompt opens, with the environment
correctly set up to successfully issue the commands in the next
steps.
c. From the command prompt in that window, issue the following
command to set the environment variable for the server instance
that you are working with:
set db2instance=instance_name

214 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

The instance_name is the same as the instance name that you

specified when you issued the db2icrt command. For example, to
set the environment variable for the Server1 server instance, issue
the following command:
set db2instance=server1
d. Issue the command to set the default drive:
db2 update dbm cfg using dftdbpath instance_location

For example, if the instance directory is d:\tsm\server1, the

instance location is drive d:. Enter the command:
db2 update dbm cfg using dftdbpath d:
7. Modify the library path to use the version of the IBM Global Security Kit
(GSKit) that is installed with the Tivoli Storage Manager server:
AIX Issue the following command:
export LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
AIX HPUX Linux You must update the following files
Solaris
to set the library path when DB2 or the Tivoli Storage Manager server is
started:
v instance_directory/sqllib/usercshrc
v instance_directory/sqllib/userprofile
For the instance_directory/sqllib/usercshrc file, add the following lines:
v AIX

setenv LIBPATH /usr/opt/ibm/gsk8_64/lib64:$LIBPATH

v HPUX Solaris

setenv LD_LIBRARY_PATH /opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

v Linux

setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

For the instance_directory/sqllib/userprofile file, add the following lines:
v AIX

LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
export LIBPATH
v HPUX Solaris

LD_LIBRARY_PATH=/opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
v Linux

LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Verify the library path settings and ensure that the GSKit version is 8.0.14.14
or later. Issue the following commands:
v AIX

echo $LIBPATH
gsk8capicmd_64 -version
gsk8ver_64
v HPUX Linux Solaris

echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64

Chapter 6. Scenario 3: New system, media method 215

Upgrading the server from V5 to V7.1

If the GSKit version is not 8.0.14.14 or later, you must reinstall the Tivoli
Storage Manager server. The reinstallation ensures that the correct GSKit
version is available.
8. Change to the instance directory that you created for the server.
9. Create and format the database and recovery logs. In the command, specify
the directories that you created for the database and logs. The directories must
be empty.
AIX HPUX Linux Solaris

For example, to get an active log size of 16 GB (16384 MB, the default
size), issue the following command, on one line:
/opt/tivoli/tsm/server/bin/dsmserv loadformat \
dbdir=/tsmdb001,/tsmdb002,/tsmdb003,/tsmdb004 \
activelogsize=16384 activelogdirectory=/tsmlog \
mirrorlogdirectory=/tsmlogmirror archlogdirectory=/tsmarchlog

Windows

For example, to get an active log size of 16 GB (16384 MB, the default
size) for the Server1 server instance, issue the following command, on
one line:
"c:\Program Files\Tivoli\TSM\server\dsmserv" loadformat
dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog
If you have already created the first server instance on the system
(server1) and are creating more, then you must use the -k option. The
-k option specifies the instance name for running this utility. For
example, if the instance name for the server is server2, issue the
command:
"c:\Program Files\Tivoli\TSM\server\dsmserv" -k server2
loadformat dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog
10. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39
Related reference:
DSMSERV LOADFORMAT (Format a database)
“Deleted server commands, utilities, and options” on page 65

Scenario 3: Loading the extracted data into the new database

After you format an empty database by using the DSMSERV LOADFORMAT utility, load
the data that you extracted from the original server database.

Before you begin

Ensure that the following requirements are met before you begin to load the data:
v The manifest file from the DSMUPGRD EXTRACTDB operation must be available.
v The server options file must contain an entry for the device configuration file.
v The device configuration file must have information about the device class that
is specified in the manifest file.

216 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

v The media that contains the extracted database must be available to the V7.1
server. The device must be physically attached to the system. The permissions
must be set to grant access to the media for the user ID that owns the V7.1
server instance.

Procedure
1. Verify that the V7.1 server can access the extracted data.
v If the extracted data is on tape, the tape drive must be physically attached to
the system.
v If the extracted data was stored by using a FILE or DISK device class,
complete the following steps:
a. Log on to the system by using the root user ID.
b. Ensure that the user ID that owns the V7.1 server (the instance user ID)
has ownership or read/write permission for the extracted files.
2. Log on with the instance user ID on the system where you installed the V7.1
server.
3. Copy the manifest file that was created by the extraction process to the V7.1
system. Ensure that the instance user ID has ownership or read/write
permission for the manifest file.
4. On the V7.1 server, complete the following steps:
a. Verify that the server options file from the V5 server includes the DEVCONFIG
option, and that the option specifies the full path of the device
configuration file.
b. Verify that the device configuration file from the V5 server is available in
the location that is specified by the DEVCONFIG option.
c. Verify that the permissions on the device configuration file allow read
access for the instance user ID.
5. Verify that the contents of the device configuration file are correct. The device
class that was used for the extraction step is recorded in the manifest file, and
that device class must exist and be valid on the V7.1 system.
a. Verify entries for FILE device classes. For example, paths might be different
on the system.
b. Verify entries for tape and other devices. For example, the device names
might have changed.
6. Verify the contents of the manifest file and edit the file if necessary:
a. Ensure that the device names in the manifest file are valid for the V7.1
system. Device names for the same device might be different on V5 and V7
systems.
b. Ensure that the manifest file contains a list of volumes to be used when the
extracted data is loaded into the new database. For example, if the manifest
file contains a list of volumes that belong to a FILE device class, ensure that
the fully qualified path to the volumes is correct for the system.
7. Issue the DSMSERV INSERTDB command to load an extracted server database into
the prepared, empty V7.1 database. Direct the output of the process to a file for
monitoring. For example, enter the following command on one line:
AIX HPUX Linux Solaris

nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \

manifest=./manifest.txt >insert.out 2>&1 &

Windows

Chapter 6. Scenario 3: New system, media method 217

Upgrading the server from V5 to V7.1

"c:\Program Files\Tivoli\TSM\server\dsmserv" insertdb \

manifest=.\manifest.txt 1>>insert.out 2>&1
8. Monitor the process for error messages, warning messages, and any items that
you might need to address. The system displays interim statistics about the
process of loading the database. However, there might be time periods when
no messages are issued. During this time, DB2 operations are running in the
background. The length of time that the process runs depends on the size of
the database. For more information, see “Example: Estimating the upgrade time
based on the database size” on page 43.
Optional: Verify that the database is being loaded by monitoring the processor
and I/O usage for the server process and the corresponding DB2 process. For
example, issue the following command to monitor the process:
tail -f insert.out

Tip: Windows On Windows systems, use the tail command or an equivalent

utility with which you can monitor the contents of a file as it changes. For
example, the Windows Server 2003 Resource Kit Tools includes the tail
command, which can be used as shown in the preceding example.
A message in the output of the DSMSERV INSERTDB command indicates the status
of the operation:
Success message: ANR1395I INSERTDB: Process 1, database insert, has
completed.
Failure message: ANR1396E INSERTDB: Process 1, database insert, has
completed with errors.
9. If you used a tape device, after the insertion operation is complete remove or
check out from the library the tape that holds the extracted data. Prevent the
tape from being reused until you are sure that you do not need to run the
insertion operation again.
Related concepts:
“The manifest file for the data extraction to media” on page 531
Related reference:
“DSMSERV INSERTDB (Move a server database into an empty database)” on page
538

Scenario 3: Creating a Windows service for the server

instance
Windows

A Windows service is created for the Tivoli Storage Manager V7.1 server
automatically if you use the upgrade wizard (dsmupgdx). If you do not use the
wizard, you must create the Windows service for the Tivoli Storage Manager
server manually.

Procedure
1. Change to the installation directory for the server program. By default, the
directory is C:\Program Files\Tivoli\TSM\console. If you installed the server
in a different directory, change to the console subdirectory of the server
installation directory.
2. Install the Windows service by using the Tivoli Storage Manager server
instance name and password in the service name. Issue the following
command:

218 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

install "TSM server_instance_name"

"C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
instance_owner instance_owner_password

where:
"TSM server_instance_name" is the name of the service that is being
installed.
server_instance_name is the instance name that was specified when you
issued the db2icrt command.
instance_owner is the instance owner account; this account will own the
service.
instance_owner_password is the password for the instance owner account.
Example
To install the Windows service for the server1 server instance, enter the
following command on one line. The example uses rudy as the instance
owner and s21ret as the password for the instance owner account.
install "TSM server1" "C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
rudy s21ret
3. Optional: Manually change the service to an automatic startup type by using
Windows administrative tools (Administrative Tools > Services).
Related tasks:
“Starting the server on Windows systems” on page 331

Scenario 3: Configuring the system for database backup

The database manager and the Tivoli Storage Manager API must be configured so
that the database manager can back up the server database. The configuration is
completed for you automatically if you use the upgrade wizard (dsmupgdx). If you
do not use the wizard, you must complete the configuration manually.

Procedure
v “Scenario 3: Configuring the system for database backup on AIX, HP-UX, Linux,
and Oracle Solaris systems”
v “Scenario 3: Configuring the system for database backup on Microsoft Windows
systems” on page 222

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Scenario 3: Configuring the system for database backup on AIX,

HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

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

Chapter 6. Scenario 3: New system, media method 219

Upgrading the server from V5 to V7.1

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, replace the example values with your actual values.
The examples use tsminst1 for the server instance user ID, /tsminst1 for the Tivoli
Storage Manager server instance directory, and /home/tsminst1 as the home
directory of the server instance user.

Procedure
1. Set the Tivoli Storage Manager API environment-variable configuration for the
database instance:
a. Log in by using the tsminst1 user ID.
b. When user tsminst1 is logged in, ensure that the DB2 environment is
correctly initialized. The DB2 environment is initialized by running the
/home/tsminst1/sqllib/db2profile script, which normally runs
automatically from the profile of the user ID. Ensure that the .profile file
exists in the home directory of the instance user, for example,
/home/tsminst1/.profile. If .profile does not run the db2profile script,
add the following lines:
if [ -f /home/tsminst1/sqllib/db2profile ]; then
. /home/tsminst1/sqllib/db2profile
fi
c. In the instance_directory/sqllib/userprofile file, add the following lines:
DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
DSMI_DIR=server_bin_directory/dbbkapi
DSMI_LOG=server_instance_directory
export DSMI_CONFIG DSMI_DIR DSMI_LOG
d. In the instance_directory/sqllib/usercshrc file, add the following lines:
setenv DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
setenv DSMI_DIR=server_bin_directory/dbbkapi
setenv DSMI_LOG=server_instance_directory
2. Log out and log in again as tsminst1, or issue this command:
. ~/.profile

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

The value for SERVERNAME must be consistent in the tsmdbmgr.opt and dsm.sys
files.
4. Locate the Tivoli Storage Manager API dsm.sys configuration file. By default,
the dsm.sys file is in the following location:

server_bin_directory/dbbkapi/dsm.sys
5. As root user, add the following lines to the dsm.sys configuration file:

220 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
errorlogname /tsminst1
nodename $$_TSMDBMGR_$$

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

where port_number specifies the port that you use for shared memory.
b. In the dsm.sys configuration file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport port_number

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port that you use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Chapter 6. Scenario 3: New system, media method 221

Upgrading the server from V5 to V7.1

Scenario 3: Configuring the system for database backup on

Microsoft Windows systems
Windows

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, the examples use server1 for the database instance
and d:\tsmserver1 for the Tivoli Storage Manager server directory. When you
issue the commands, replace these values with your actual values.

Procedure
1. Create a file that is named tsmdbmgr.env in the d:\tsmserver1 directory with
the following contents:
DSMI_CONFIG=server_instance_directory\tsmdbmgr.opt
DSMI_LOG=server_instance_directory
2. Set the DSMI_ api environment-variable configuration for the database instance:
a. Open a DB2 command window. One method is to go to the C:\Program
Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage
Manager in a different location, go to the db2\bin subdirectory in your main
installation directory. Then, issue the following command:
db2cmd
b. Issue the following command:
db2set -i server1 DB2_VENDOR_INI=d:\tsmserver1\tsmdbmgr.env
c. Create a file that is named tsmdbmgr.opt in the d:\tsmserver1 directory
with the following contents:
*************************************************
nodename $$_TSMDBMGR_$$
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
passwordaccess generate
errorlogname d:\tsmserver1
where
v nodename specifies the node name that the client API uses to connect to
the server during a database backup. To ensure that the database can be
backed up, this value must be $$_TSMDBMGR_$$.
v commmethod specifies the client API that is used to contact the server for
database backup. This value can be tcpip or sharedmem. For more
information about shared memory, see Step 3 on page 223.
v tcpserveraddr specifies the server address that the client API uses to
contact the server for database backup. To ensure that the database can be
backed up, this value must be localhost.

222 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

v tcpport is the port number that the client API uses to contact the server
for database backup. Ensure that you enter the same tcpport value that is
specified in the dsmserv.opt server options file.
v passwordaccess is required to ensure that the backup node can connect to
the server.
v errorlogname is the error log where the client API logs errors that are
encountered during a database backup. This log is typically in the server
instance directory. However, this log can be placed in any location where
the instance user ID has write-permission.
3. Optional: Configure the server to back up the database by using shared
memory. In this way, you might be able to reduce the processor load and
improve throughput. Complete the following steps:
a. Review the dsmserv.opt file. If the following lines are not in the file, add
them:
commmethod sharedmem
shmport port_number

where port_number specifies the port to use for shared memory.

b. In the tsmdbmgr.opt file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport 1500

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port to use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Chapter 6. Scenario 3: New system, media method 223

224 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 7. Scenario 4: New system, network method
Use this procedure if you are upgrading the Tivoli Storage Manager server on a
different system than your V5 server, and you are using the network method to
move the data.

Procedure

The procedure for upgrading the server includes the following tasks:
1. “Scenario 4: Preparing for the upgrade”
2. “Scenario 4: Installing the upgrade utilities” on page 233
3. Upgrading the server, by using one of the following methods:
v “Scenario 4: Upgrading the server by using the upgrade wizard” on page 241
v “Scenario 4: Upgrading the server manually by using utilities” on page 250
4. The following tasks are completed after the upgrade:
a. “Verifying access to storage pools on disk” on page 323
b. “Setting up Solaris services for the server instance” on page 324
c. “Configuring server options for server database maintenance” on page 324
d. “Starting the server instance after the upgrade” on page 325
e. “Registering licenses” on page 334
f. “Backing up the database after upgrading the server” on page 335
g. “Verifying the upgraded server” on page 336
h. “Changing the host name for the Tivoli Storage Manager server” on page
336
i. “Updating automation” on page 338
j. “Monitoring the upgraded server” on page 339
k. “Removing GSKit Version 7 after upgrading to Tivoli Storage Manager
V7.1” on page 340

Scenario 4: Preparing for the upgrade

Prepare for the upgrade by checking requirements, preparing the space that is
required, backing up the server, and modifying certain server settings.

About this task

Follow the preparation steps carefully to protect your server and its data.

Important: It is possible, after the upgrade to V7.1 is complete, that conditions

might cause the need to temporarily revert to the previous version of the server.
Successfully reverting to the previous version of the server is possible only if you
have completed all preparation steps. To understand why it is important to
complete all preparation steps, review the procedure for reverting an upgraded
server to its previous version.

Procedure
1. “Scenario 4: Checking the prerequisites for the upgrade” on page 226
2. “Scenario 4: Preparing space for the upgrade process” on page 229

© Copyright IBM Corp. 2009, 2013 225

Upgrading the server from V5 to V7.1

3. “Scenario 4: Modifying the server before the upgrade” on page 229

4. “Scenario 4: Disabling sessions” on page 230
5. “Scenario 4: Backing up storage pools and the server database” on page 231
6. “Scenario 4: Moving the NODELOCK file” on page 232
7. “Scenario 4: Backing up configuration information” on page 232
8. “Scenario 4: Creating a summary of database contents” on page 233
9. “Scenario 4: Stopping the server before installing the upgrade” on page 233
Related tasks:
“Reverting from V7.1 to the previous V5 server version” on page 351

Scenario 4: Checking the prerequisites for the upgrade

Check your system against requirements for the server.

Procedure
1. Ensure that the server that you plan to upgrade is at the V5.5 release level, and
that the latest interim fix is installed. For example, if the server is at V5.5.6,
install the latest interim fix for V5.5.6. Take the following actions:
a. Select the appropriate server level. For detailed guidelines, see
“Determining the appropriate level for a V5 server before an upgrade” on
page 36. If the server is at an appropriate level, no action is required.
b. If the server is not at an appropriate level, download the appropriate server
fix pack and the latest interim fix from the FTP downloads site at
ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server/. Locate the appropriate version of Tivoli Storage
Manager and install it.
2. Ensure that the system where the V5 server is located meets the minimum
requirements. Review the information in “Hardware and software requirements
for the V5 server system that is being upgraded” on page 17 to determine
whether you must update your system before you continue.
3. Ensure that the system where you plan to install the V7.1 server meets
requirements for the operating system type and level. For the latest information
about system requirements, see Tivoli Storage Manager Supported Operating
Systems (http://www.ibm.com/support/docview.wss?uid=swg21243309).
If you are upgrading Tivoli Storage Manager to a different operating system, a
limited set of migration paths is available. For instructions about migrating a
server that is running on a z/OS operating system, see Part 3, “Migrating Tivoli
Storage Manager V5 servers on z/OS systems to V7.1 on AIX or Linux on
System z,” on page 437. For instructions about migrating a server that is
running on an AIX, HP-UX, or Solaris operating system, see Part 2, “Migrating
Tivoli Storage Manager V5 servers on AIX, HP-UX, or Solaris systems to V7.1
on Linux,” on page 355.
Some platforms that were supported for earlier versions of the server are not
supported for V7.1. If the server that you want to upgrade is running on one of
these platforms, you cannot upgrade your server to V7.1 on the same platform.
You must install your V7.1 server on a system that is a specific supported
platform, depending on the original platform. For required platforms, see the
following table.
Table 48. Required platforms for upgrading from V5 to V7.1
Platform for V5 server Required platform for upgrade to V7.1
HP-UX running on a PA-RISC system HP-UX running on an Intel Itanium system

226 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 48. Required platforms for upgrading from V5 to V7.1 (continued)

Platform for V5 server Required platform for upgrade to V7.1
Linux running on an Itanium system (IA64) Linux running on an x86_64 system
Linux running on an x86_32 system Linux running on an x86_64 system
Solaris running on an x86_64 system Linux running on an x86_64 system
Windows running on an Itanium system Windows running on an x86_64 system
(IA64)

If you are upgrading from Tivoli Storage Manager V5 to V7.1 on a new system,
restrictions apply. Ensure that you install the V7.1 server in a compatible
hardware and software environment, as described in the following table.
Table 49. Requirements for upgrading from V5 to V7.1 on a new system
V5 server V7.1 server Comments
AIX running on an IBM AIX running on an IBM
POWER system POWER system
HP-UX running on an HP-UX running on an
Itanium system Itanium system
HP-UX running on a HP-UX running on an HP-UX running on PA-RISC
PA-RISC system Itanium system is not supported for V7.1
servers.
Linux running on an IBM Linux running on an IBM
POWER system POWER system
Linux running on an Itanium Linux running on an x86_64 Linux running on Itanium is
system (IA64) system not supported for V7.1
servers.
Linux running on an x86_32 Linux running on an x86_64 Linux running on x86_32 is
system system not supported for V7.1
servers.
Linux on System z Linux on System z

Chapter 7. Scenario 4: New system, network method 227

Upgrading the server from V5 to V7.1

Table 49. Requirements for upgrading from V5 to V7.1 on a new system (continued)
V5 server V7.1 server Comments
Solaris running on an x86_64 Operating system depends A V7.1 server cannot be
system on the migration method installed on a Solaris x86_64
system. However, you can
migrate a V5 server that is
running on a Solaris x86_64
operating system to V7.1 on
a Linux x86_64 operating
system. For instructions, see
Part 2, “Migrating Tivoli
Storage Manager V5 servers
on AIX, HP-UX, or Solaris
systems to V7.1 on Linux,”
on page 355.

Alternatively, you can

migrate the Solaris x86_64
system by installing a V7.1
server on any operating
system that is supported for
V7.1. Then, use Tivoli
Storage Manager server
EXPORT and IMPORT
commands to move the
server from the V5 source
system to the V7.1 target
system.
Windows running on an Windows running on an Windows running on
Itanium system (IA64) x86_64 system Itanium is not supported for
V7.1 servers.
Windows running on an Windows running on an Windows running on x86_32
x86_32 system x86_64 system is not supported for V7.1
servers.
z/OS AIX or Linux on System z See the section on migrating
from V5 on z/OS to V7.1 on
AIX or Linux on System z.

4. Verify that the system memory meets the server requirements. If you plan to
run multiple instances of the V7.1 server on the system, each instance requires
the memory that is listed for one server. Multiply the memory for one server by
the number of instances that are planned for the system.
For specific information about memory requirements, see the section for your
operating system:
Table 50. Memory requirements for the V7.1 system
Operating system Memory requirements
AIX “Server requirements on AIX systems” on
page 21
HP-UX “Server requirements on HP-UX systems” on
page 24
Linux “Server requirements on Linux systems” on
page 26
Solaris “Server requirements on Solaris systems” on
page 31

228 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 50. Memory requirements for the V7.1 system (continued)

Operating system Memory requirements
Windows “Server requirements on Microsoft Windows
systems” on page 33

5. Ensure that the system has enough disk storage for the database and recovery
logs. Review the planning information for requirements and guidance.
If you are adding new hardware for the server, such as new disk storage for
the database, ensure that the hardware is installed and running.
6. Ensure that the new system can access the storage devices that are used on the
original system. This includes disk and tape devices that are used to store client
data.
Related concepts:
“Hardware and software requirements for upgrading to the V7.1 server” on page
17

Scenario 4: Preparing space for the upgrade process

Determine the amount and type of space that is required for the upgrade process
before beginning the process.

Procedure

Verify that the system has the amount of space that was estimated in the planning
step. Use the planning worksheet that you completed with your information. See
“Worksheet for planning space for the V7.1 server” on page 42.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39

Scenario 4: Modifying the server before the upgrade

A command must be run on the server to prevent one type of problem during the
upgrade process. Some modifications to typical server settings can be useful to
prepare for the upgrade.

Procedure
1. From a Tivoli Storage Manager administrative command line, issue the
command:
convert ussfilespace

This command fixes a problem that might exist in older Tivoli Storage Manager
databases. If the problem does not exist in your database, the command is
completed and you might see error ANR2034E. This error can be ignored. For
more information, see Technote 1408895 (http://www.ibm.com/support/
docview.wss?uid=swg21408895). If the problem exists in your database, the
command might take some time to run.

Important: Do not skip this step. If your database has the problem and you do
not run this command now, the DSMUPGRD PREPAREDB utility fails when you run
it. You must then restart the V5 server and run the CONVERT USSFILESPACE
command before you continue the upgrade process.
2. Review the steps for reverting to the earlier version of the server in the section,
“Reverting from V7.1 to the previous V5 server version” on page 351.

Chapter 7. Scenario 4: New system, network method 229

Upgrading the server from V5 to V7.1

If you must revert to the earlier version after the upgrade to V7.1, the results of
the reversion will be better if you understand the steps and prepare for the
possibility now.
3. Make the following adjustments to settings on your server and clients. These
adjustments must be done to make it possible for you to revert to the original
server after the upgrade, if problems occur.
a. For each sequential-access storage pool, set the REUSEDELAY parameter to the
number of days during which you want to be able to revert to the original
server, if necessary.
For example, if you want to be able to revert to the original server for up to
30 days after the upgrade to V7.1, set the REUSEDELAY parameter to 31 days.
Issue the following administrative command:
update stgpool sequential_access_storage_pool reusedelay=31
b. For each copy storage pool, set the RECLAIM parameter to 100 (meaning
100%). Issue the following administrative command:
update stgpool copy_storage_pool reclaim=100
c. If you typically use a DELETE VOLHISTORY command to delete database
backups, ensure that the command does not delete database backups too
frequently. The interval between backups should be at least the same
number of days that you set for the REUSEDELAY period for sequential-access
storage pools. For example, to delete database backups every 45 days, issue
the following administrative command:
delete volhist type=dbbackup todate=-45
d. For important clients that use the server, verify that the value for the
schedlogretention client option is set to retain the client schedule log for a
sufficient time. Update the option for clients if needed.
The entries in the client schedule log might be useful if the server must
revert to the original version. If the retention period for the schedule log is
too short, the schedule log information might be deleted too soon.
For example, to prune the log every 45 days and save the log entries, add
the following option:
schedlogretention 45 S
AIX HPUX Linux Solaris Add the option to the dsm.sys file
within a server stanza.
Windows Add the option to the client options file, dsm.opt.

Scenario 4: Disabling sessions

In preparation for the upgrade, prevent activity on the server by disabling new
sessions. Cancel any existing sessions.

About this task

The commands in the following procedure are Tivoli Storage Manager

administrative commands.

Procedure
1. Prevent all clients, storage agents, and other servers from starting new sessions
with the server. Use the commands:
disable sessions client
disable sessions server

230 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

For more information about these commands and other Tivoli Storage Manager
administrative commands, see the Administrator's Reference.
2. Verify whether any sessions exist, and notify the users that the server is going
to be stopped. To check for existing sessions, use the command:
query session
3. Cancel sessions that are still running. Use the command:
cancel session all

Scenario 4: Backing up storage pools and the server database

Immediately before upgrading the server, back up primary storage pools to copy
storage pools, and perform a full database backup.

Before you begin

Back up storage pools and the server database by using Tivoli Storage Manager
administrative commands:

Procedure
1. Back up primary storage pools to copy storage pools by using the BACKUP
STGPOOL command:
backup stgpool primary_pool copy_stg

where primary_pool specifies the primary storage pool and copy_stg specifies the
copy storage pool. If you have been performing regular backups of the storage
pools, this step backs up only the data that was added to the primary storage
pools since they were last backed up.
2. Back up the database. The preferred method is to use a snapshot backup. A
snapshot backup is a full database backup that does not interrupt any
scheduled database backups. Issue the command:
backup db type=dbsnapshot devclass=device_class_name

The device class that you specify must exist and have volumes that are
available to it. For example, to perform a snapshot backup of your database to
the TAPECLASS device class by using scratch volumes, enter:
backup db type=dbsnapshot devclass=tapeclass

To use specific volumes instead of scratch volumes, specify the volume names
in the command.

Tip: Consider making two copies of the backup to protect the backup from
media failures. Ensure that at least one full database backup is available onsite.
If you must restore the database after a failed upgrade, having an onsite
backup database saves time.

Chapter 7. Scenario 4: New system, network method 231

Upgrading the server from V5 to V7.1

Scenario 4: Moving the NODELOCK file

To ensure that licensing information is updated during the upgrade process, move
the NODELOCK file from the server instance directory to another directory.

About this task

The NODELOCK file contains the licensing information from the previous Tivoli
Storage Manager installation. This licensing information is replaced when the
upgrade is complete.

Procedure
1. In the server instance directory of your installation, locate the NODELOCK file.
2. Move the NODELOCK file to another directory. For example, you can save it to a
directory where you are saving configuration files from the previous release.

Scenario 4: Backing up configuration information

Before you install the new version, back up critical files and information for each
server instance. Store the files in a safe place, on a different system from the
system that is being upgraded or on offline media, such as a CD. The files are
required after the installation of the new software version is complete. You also
need these files if you must revert to the previous version after the upgrade.

Procedure
1. Back up device configuration information to another directory by using the
following Tivoli Storage Manager administrative command:
backup devconfig filenames=file_name

where file_name specifies the file in which to store device configuration

information.
2. Back up volume history information to another directory by using the
following Tivoli Storage Manager administrative command:
backup volhistory filenames=file_name

where file_name specifies the file in which to store volume history information.
Ensure that the volume history includes information about the database backup
that you completed in the preceding steps. For example, issue the following
command:
query volhistory type=dbsnapshot

Review the query output to verify that the time stamp for the database backup
matches the actual time of the backup.
3. Save copies of the following files, which are in the server instance directory:
v Server options file, typically named dsmserv.opt
v dsmserv.dsk

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.
4. In the server instance directory, look for the accounting log file, dsmaccnt.log.
If the file exists, save a copy.
5. Back up any scripts that were used to complete daily housekeeping for the
server. Examine the scripts for changes that are needed after the upgrade.

232 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

6. Store the device configuration file, the volume history file, the server options
file, and the other files in a safe place. Ensure that the files are stored on a
different system from the system that is being upgraded, or on offline media.

Scenario 4: Creating a summary of database contents

Create a summary of the contents of the original database. After the upgrade, you
can use the same commands to compare the results and to confirm that the
database contents are intact.

Procedure

Run commands that give a summary of information about your database contents.
For example, issue commands that summarize the file spaces that are being
protected, and save the results. For a list of commands, see “Sample commands to
run for validation of the database upgrade” on page 546.
Related reference:
“Sample commands to run for validation of the database upgrade” on page 546

Scenario 4: Stopping the server before installing the upgrade

Stop all server processes and unmount any tapes that are mounted. Then, stop the
server.

Procedure

Use Tivoli Storage Manager administrative commands to stop the server:

1. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the following commands:
query process
cancel process process_number

Allow time for the processes to be stopped. Some processes, such as storage
pool migration, might take some time to stop.
For more information about the QUERY PROCESS and CANCEL PROCESS commands
and other Tivoli Storage Manager administrative commands, see the
Administrator's Reference.
2. After all sessions and processes are stopped, determine whether any tapes are
mounted. Unmount any tapes that are mounted. Use the following commands:
query mount
dismount volume volume_name
3. Stop the server. Use the following command:
halt

Scenario 4: Installing the upgrade utilities

You must install the upgrade utilities on the system where the V5 server is located.
The installation package for the utilities must be downloaded from a website.

Before you begin

The preferred method is to install the latest available version of the upgrade
utilities. For more information about selecting the version, see “Determining the
appropriate level for a V5 server before an upgrade” on page 36.

Chapter 7. Scenario 4: New system, network method 233

Upgrading the server from V5 to V7.1

Procedure

Use the procedure for your operating system:

v AIX “Scenario 4: Installing the upgrade utilities on AIX systems”
v HPUX “Scenario 4: Installing the upgrade utilities on HP-UX systems” on
page 236
v Linux “Scenario 4: Installing the upgrade utilities on Linux systems” on page
237
v Solaris “Scenario 4: Installing the upgrade utilities on Oracle Solaris systems”
on page 238
v “Scenario 4: Installing the upgrade utilities on Microsoft Windows
Windows
systems” on page 240
Related concepts:
“DSMUPGRD upgrade utilities” on page 16

Scenario 4: Installing the upgrade utilities on AIX systems

AIX

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The
5.5.x.x number must be the same as or later than the level of the V5
server that you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-AIX.tar.gz
The numbers at the beginning of the package name identify the release
level of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Ensure that the system has the following file sets installed:
xlC.rte 8.0.0.5, or later
gsksa.rte 7.0.4.11
You can use the following commands to check for these file sets:
lslpp -L xlC.rte

lslpp -L gsksa.rte

234 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

If needed, you can obtain the gsksa.rte file set from any of the regular V5.5
maintenance packages for the AIX server. The maintenance packages are
available on the FTP downloads site: ftp://public.dhe.ibm.com/storage/tivoli-
storage-management/maintenance/server/v5r5/AIX/
4. Extract the contents of the upgrade utilities package. If you downloaded a
language package, also extract the contents of that package.
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Access the System Management Interface Tool (SMIT).
a. Enter smitty install_update
b. Select Install and Update Software > Install and Update from ALL
Available Software.
7. Select the INPUT device. Specify the directory location of the upgrade utilities
package on the system.
8. Select Software to Install. Press F4 or Esc+4 for the list of available file sets in
the directory.
9. Select the file sets for the upgrade utilities, the device driver, and optionally
the language package. The file set for the upgrade utilities is
tivoli.tsmupg.server. Optional language packages include messages for
languages other than US English.
10. Set COMMIT software updates to Yes. Press F4 or Esc+4.
11. Set SAVE replaced files to No.
12. Ensure that the default settings for the options in the window for all the
selected file sets show success.
13. Press Enter, and respond to the ARE YOU SURE? question by pressing Enter
again. The installation begins.
14. When the installation is complete, exit the SMIT program.
15. Optional: If you installed a language package, ensure that the locale
environment variable is set to use it. Enter the following command to set the
locale environment variable for messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
16. After the upgrade utilities are installed, continue at “Scenario 4: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 239.

Chapter 7. Scenario 4: New system, network method 235

Upgrading the server from V5 to V7.1

Scenario 4: Installing the upgrade utilities on HP-UX systems

HPUX

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.gz
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
gzip -dc package_name.tar.gz | tar -xvf -
4. Navigate to the directory that corresponds to the processor architecture of the
operating system.
5. Install the upgrade utilities and the device driver. Use the source argument (-s)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
swinstall -s /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin.

6. Optional: Install the language package.
a. Extract the contents of the package.
gzip -d package_name.img.gz
b. Install the package. For example, if the directory is /tmp/TSM, issue the
command:
swinstall -s /tmp/TSM/package_name.img package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:

236 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

v The locale is installed on the system.

v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Scenario 4: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 239.

Scenario 4: Installing the upgrade utilities on Linux systems

Linux

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Open the directory for your operating system and download the package.
The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.bz2
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the commands:
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
4. Navigate to the directory that corresponds to the processor architecture of the
operating system, for example, x86_64.
5. Install the upgrade utilities and the device driver. Use the following command:
rpm -ivh package_name.rpm
The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by
default.
6. Optional: Install the language package.
a. Extract the contents of the downloaded package.
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
b. Install the package for the language that you want to use.
rpm -ivh package_name.rpm

Chapter 7. Scenario 4: New system, network method 237

Upgrading the server from V5 to V7.1

c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Scenario 4: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems” on page 239.

Scenario 4: Installing the upgrade utilities on Oracle Solaris

systems
Solaris

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

About this task

Restriction: Do not install the utilities in the installation directory of the server that
must be upgraded. Install the utilities package in its own directory.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.Z
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Change to the directory where the upgrade utilities package was downloaded.
4. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
uncompress -c package_name.tar.Z | tar -xvf -

238 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

5. Navigate to the directory that corresponds to the processor architecture of the

operating system.
6. Install the upgrade utilities and the device driver. Use the source argument (-d)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
pkgadd -d . /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by

default.
7. Optional: Install the language package.
a. Extract the contents of the downloaded package.
uncompress package_name.pkg.Z
b. Install the package for the language that you want to use. Use the source
argument (-d) to specify the directory where the package was extracted. For
example, if the directory is /tmp/TSM, issue the command:
pkgadd -d /tmp/TSM package_name.pkg package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
8. After the upgrade utilities are installed, continue at “Scenario 4: Setting
environment variables for the upgrade utilities on AIX, HP-UX, Linux, and
Oracle Solaris systems.”

Scenario 4: Setting environment variables for the upgrade

utilities on AIX, HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

After installing the upgrade utility package, you must set environment variables in
the shell from which you will run the utilities. An environment variable describes
the operating environment of a process, such as the home directory or terminal in
use.

About this task

The DSMSERV_DIR variable specifies the installed location of the upgrade utilities. By
default, the location is the following directory:

AIX

/usr/tivoli/tsm/upgrade/bin

HPUX Linux Solaris

/opt/tivoli/tsm/upgrade/bin

Chapter 7. Scenario 4: New system, network method 239

Upgrading the server from V5 to V7.1

Procedure

Use the appropriate command for your system to set the environment variable for
running the utilities. If the shell is in the ksh or bash family, enter the following
command to set the DSMSERV_DIR variable:
export DSMSERV_DIR=upgrade_utilities_directory

If your shell is in the csh family, use the following command:

setenv DSMSERV_DIR upgrade_utilities_directory

where upgrade_utilities_directory is the directory where the upgrade utilities are

installed.

What to do next

After you set the environment variables, continue the upgrade process using one of
the following topics:
v “Scenario 4: Upgrading the server by using the upgrade wizard” on page 241
v “Scenario 4: Upgrading the server manually by using utilities” on page 250

Scenario 4: Installing the upgrade utilities on Microsoft

Windows systems
Windows

Install the upgrade utilities on the system where the V5 server is located. The
package to install is available for download from the FTP downloads site. The
upgrade utilities are used to prepare and extract the database from the original
server.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/WIN
b. Open the 5.5.x.x directory. The 5.5.x.x number must be the same as or
later than the level of the V5 server that you are upgrading.
c. Select the package and download it to a convenient location on the server
system. The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-Windows.exe
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, install the
language package that your installation requires.
2. Log on with an administrator ID.
3. Run the executable package for the upgrade utilities.
The default location for the installation of the utilities is based on the location
where the V5 server was last installed. For example, if the V5 server was
installed using the default path, C:\Program Files\Tivoli\TSM\server, the
upgrade utilities are installed in C:\Program Files\Tivoli\TSM\upgrade.

Restriction: Do not install the utilities in the same directory as the original
server that must be upgraded. Install the utilities package in its own directory.

240 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

What to do next

After the upgrade utilities are installed, continue the upgrade process using one of
the following topics:
v “Scenario 4: Upgrading the server by using the upgrade wizard”
v “Scenario 4: Upgrading the server manually by using utilities” on page 250

Tip: When you use the upgrade utilities, if you have multiple servers running
on the system, you must use the -k option to specify the name of the Windows
registry key from which to retrieve information about the server being
upgraded. The default value for the option is SERVER1.

Scenario 4: Upgrading the server by using the upgrade wizard

The wizard offers a guided approach to upgrading a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Start the wizard on the system where you installed the V7.1 server program.

Before you begin

You must complete all preceding steps to prepare for the upgrade and to install the
upgrade utilities. The V7.1 server must be installed, and directories and the user ID
must be created before you start the upgrade wizard.

Procedure

Complete the following steps:

1. Scenario 4: Installing the V7.1 server
2. Scenario 4: Creating the directories and the user ID for the upgraded server
instance
3. “Scenario 4: Starting the upgrade wizard” on page 248

Scenario 4, wizard: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

Chapter 7. Scenario 4: New system, network method 241

Upgrading the server from V5 to V7.1

Procedure
1. Log on to the system.
AIX HPUX Linux Solaris Log in by using the root user ID.
Windows Log on as an administrator. You must be logged on to the system
with the administrative user ID that was used to install the V5 server.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
AIX HPUX Linux Solaris

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

AIX

7.1.0.000-TIV-TSMSRV-AIX.bin

HPUX

7.1.0.000-TIV-TSMSRV-HP-UX.bin

Linux

7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin
7.1.0.000-TIV-TSMSRV-Linuxs390x.bin

Solaris

7.1.0.000-TIV-TSMSRV-SolarisSPARC.bin

242 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

In the examples, 7.1.0.000 represents the product release level.

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

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

Windows

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035121
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035636
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035638
b. Change to the directory where you placed the executable file.
In the next step, the files are extracted to the current directory. The
path must contain no more than 128 characters. Ensure that you
extract the installation files to an empty directory. Do not extract to
a directory that contains previously extracted files, or any other
files.
c. To extract the installation files, double-click the executable file:
package_name.exe
where package_name is like this example:
7.1.0.000-TIV-TSMSRV-Windows.exe
The package is large. Therefore, the extraction takes some time.
4. AIX HPUX To ensure that the Tivoli Storage Manager
Solaris
wizards work correctly, verify that the following command is enabled:
AIX lsuser
HPUX Solaris logins
By default, the command is enabled.
5. If you plan to install the server by using the graphical wizard of IBM
Installation Manager, review the following information and verify that your
system meets the requirements:
v AIX Verify that all required RPM files are installed. For a list of
required RPM files and instructions about installing RPM files, see the
section about installing Tivoli Storage Manager by using the installation
wizard in the Installation Guide.
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the
installation wizard.
v The user ID that you use during installation must be a user with
Windows
local Administrator authority.
v Solaris Ensure that the LD_LIBRARY_PATH_64 environment variable is not
set.

Chapter 7. Scenario 4: New system, network method 243

Upgrading the server from V5 to V7.1

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
AIX HPUX Linux Solaris

./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

Windows

install.bat -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

6. If you use the installation wizard, complete the following steps to begin the
installation:

Option Description
Installing from a downloaded package file: 1. Change to the directory where you
downloaded the package file.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat

Installing from DVD media: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat
Windows Or, in the directory where the
installation files were extracted,
double-click the install.bat file.

7. If you are installing the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
8. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.

244 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

9. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
10. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
11. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.
12. HPUX Linux Solaris To prevent server failures during interaction
with DB2, tune the kernel parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
13. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
14. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.
Related concepts:
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555

Scenario 4, wizard: Creating the directories and the user ID

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

Before you begin

Review the information about planning space for the server before completing this
task. See “Worksheet for planning space for the V7.1 server” on page 42.

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

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

Restriction: In the user ID, only lowercase letters (a-z), numerals

(0-9), and the underscore character (_) can be used. The user ID and
group name must comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a
numeral.
v The user ID and group name cannot be user, admin, guest, public,
local, or any SQL reserved word.

Chapter 7. Scenario 4: New system, network method 245

Upgrading the server from V5 to V7.1

For example, create user ID tsminst1 in group tsmsrvrs. The

following examples show how to create this user ID and group by
using operating system commands:
AIX

# mkgroup id=1001 tsmsrvrs

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

HPUX

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

Linux

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

Solaris

# groupadd tsmsrvrs
# useradd -d /export/home/tsminst1 -m -g tsmsrvrs
-s /bin/ksh tsminst1
# passwd tsminst1
b. Log out and then log in to your system by using the new user ID
and password. Use an interactive login program, such as telnet, so
that you are prompted for the password and can change it if
necessary.
c. If a configuration profile does not exist for the user ID, create the
file. For example, create a .profile file if you are using the Korn
shell (ksh).
Windows
Identify the user account that will own the Tivoli Storage Manager
server instance. When the server is started as a Windows service, this is
the account that the service will log on to. The user account must have
administrative authority on the system. One user account can own
more than one server instance.
You can create a user account, or use an existing account.
If you have multiple servers on one system and want to run each
server with a different user account, create a user account in this step.
a. Create the user ID.

Restriction: The user ID can contain only lowercase letters (a-z),

numerals (0-9), and the underscore character (_). The user ID must
be 30 characters or less, and cannot start with ibm, sql, sys, or a
numeral. The user ID and group name cannot be user, admin, guest,
public, local, or any SQL reserved word.
Use the following command to create the user ID:
net user user_ID * /add

You are prompted to create and verify a password for the new user
ID.

246 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

b. Issue the following operating system commands to add the new

user ID to the Administrators groups:
net localgroup Administrators user_ID /add
net localgroup DB2ADMNS user_ID /add
c. Log in to your system, by using the new user ID and password.
d. For all directories that were created for the server instance, ensure
that the user ID for the server instance has read/write access. The
directories to check include the instance directory and all database
and log directories.
2. Create the directories that the server requires. Ensure that you are logged in
under the new user ID that you created.
You need a unique, empty directory for each item in the following table. Create
the database directories, the active log directory, and the archive log directory
on different physical volumes. For space requirements, see “Worksheet for
planning space for the V7.1 server” on page 42.
AIX HPUX Linux Solaris

Table 51. Worksheet for creating required directories

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

Windows

Table 52. Worksheet for creating required directories

Example commands for
Item creating the directories Your directories
The instance directory for mkdir d:\tsm\server1
the server, which will
contain files for this
server instance, including
the server options file

Chapter 7. Scenario 4: New system, network method 247

Upgrading the server from V5 to V7.1

Table 52. Worksheet for creating required directories (continued)

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

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
3. Create additional logical volumes and mount the volumes on the directories
that were created in the previous step.
Related tasks:
“Planning space for the upgrade process and the upgraded server” on page 37
Related reference:
“Server naming best practices” on page 70

Scenario 4: Starting the upgrade wizard

The wizard offers a guided approach to upgrading a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Start the wizard on the system where you installed the V7.1 server program.

Before you begin

You must complete all preceding steps to prepare for the upgrade, to install the
upgrade utilities, to install the V7.1 server program, and to create the directories
and user ID for the server instance.

Procedure
1. Ensure that the following requirements are met.
AIX HPUX Linux Solaris

v The system where you installed the V7.1 server program must have
the X Window client. You must also be running an X Window server
on your desktop.
v The systems must have one of the following protocols enabled.
Ensure that the port that the protocol uses is not blocked by a
firewall.

248 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

– Secure Shell (SSH). Ensure that the port is set to the default value,
22. Also, ensure that the SSH daemon service has access rights for
connecting to the system by using localhost.
– Remote shell (rsh).
– Remote Execution Protocol (REXEC).
v You must be able to log in to the V7.1 system with the user ID that
you created for the server instance, using the SSH, RSH, or REXEC
protocol. When using the wizard, you must provide this user ID and
password to access that system.
Windows

v The system where you installed the V7.1 server program must have
the Windows server message block (SMB) protocol enabled. SMB is
the interface that is used by File and Print Sharing (also known as
CIFS). To use the SMB protocol, you must ensure that File and Print
Sharing is enabled, and that port 445 is not blocked by your firewall.
v If the V5 server is on a different system than the V7.1 server, that
system must also have SMB enabled.
v You must be able to log on to the system that has SMB enabled by
using either the user ID that you created for the server instance, or
another user ID that exists on the system. When you use the wizard,
you must provide the user ID and password to access the system.
2. Windows If the system is running on Windows Server 2008, complete the
following steps to disable User Account Control:
a. Ensure that the Remote Registry in Windows Services is started, and ports
445, 137, and 139 are unblocked in the firewall.
b. Configure both the framework server and the targets as members of a
Windows domain. Use a user account in that domain, or in a trusted
domain, when you connect to the target.
c. Connect to the target workstation by enabling and using the built-in
administrator account. To enable the built-in administrator account, click
Control Panel > Administrative Tools > Local Security Policy > Security
Settings > Local Policies > Security Options. Double-click the Accounts:
Administrator account status section. Select Enable and click OK.
d. Click Control Panel > Administrative Tools > Local Security Policy >
Security Settings > Local Policies > Security Options. Double-click the
User Account Control: Run all administrators in Admin Approval Mode
section. Select Disable and click OK.
3. Start the upgrade wizard, dsmupgdx, from the V7.1 server installation directory.
AIX HPUX Linux Solaris
Log in using the root user ID. Issue the command:
/opt/tivoli/tsm/server/bin/dsmupgdx

Windows
Open a new Command Prompt window, and issue the command:
"c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe"
4. Follow the instructions to complete the upgrade. The upgrade wizard can be
stopped and restarted, but the server will not be operational until the entire
upgrade process is complete.

Chapter 7. Scenario 4: New system, network method 249

Upgrading the server from V5 to V7.1

Important: Read all messages that appear for each phase of the upgrade
process, in the message display area within the wizard. Informational messages
might show actions that occurred during the process that are important to you.

What to do next

To complete the upgrade, perform the steps described in Chapter 10, “Taking the
first steps after upgrade,” on page 323.

Scenario 4: Upgrading the server manually by using utilities

Use the utilities to upgrade the server by using a command interface.

Before you begin

Complete all preceding steps to prepare for the upgrade and to install the upgrade
utilities.

Procedure

Complete the following steps:

1. “Scenario 4: Preparing the database of a V5 server for upgrade”
2. Scenario 4: Installing the V7.1 server
3. Scenario 4: Creating the directories and the user ID for the upgraded server
instance
4. “Scenario 4: Creating and formatting the new database” on page 259
5. “Scenario 4: Moving the server database over a network” on page 263
6. “Scenario 4: Creating a Windows service for the server instance” on page 265
7. “Scenario 4: Configuring the system for database backup” on page 265

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.
Related concepts:
“DSMUPGRD upgrade utilities” on page 16

Scenario 4: Preparing the database of a V5 server for upgrade

Before you extract the data from the database, you must prepare the server
database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a
single system, you must repeat this task for each server.

Procedure
1. Ensure that you have completed all preparation steps.
2. Log in using the root user ID on the system that has the original server. Log on
with the administrator ID on a Windows system.
3. Change to the instance directory for the server that you are upgrading. The
instance directory is the directory that contains the files such as dsmserv.dsk for
the server.

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.

250 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

4. Prepare the database. Direct the output of the process to a file for monitoring.
AIX
From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

HPUX Linux Solaris

From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

Windows
From the instance directory for the server that you are upgrading, issue
the following command to run the process and direct the output to the
file called prepare.out:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd"
preparedb 1>>prepare.out 2>&1

If multiple servers exist on the system, issue the command from the
instance directory for the server that you want to prepare. Specify the
registry key for that server. For example, if the server is SERVER2:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" -k server2
preparedb 1>>prepare.out 2>&1
5. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation. From the instance directory for the
server that you are upgrading, issue the following command to monitor the
process:
tail -f prepare.out

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
6. Ensure that the prepare operation is completed successfully before you continue
to the next step. If the prepare operation fails, you might need to restart the V5
server to fix the problem and run the prepare operation again. If the server that
is being upgraded is a V5.3 or V5.4 server, you might need to restore the
database by using a backup before you can restart the server to correct the
problem.
Related reference:
“DSMUPGRD PREPAREDB (Prepare a V5 database for upgrade)” on page 523

Chapter 7. Scenario 4: New system, network method 251

Upgrading the server from V5 to V7.1

Scenario 4, manual: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

Procedure
1. Log on to the system.
AIX HPUX Linux Solaris Log in by using the root user ID.
Windows Log on as an administrator. You must be logged on to the system
with the administrative user ID that was used to install the V5 server.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
AIX HPUX Linux Solaris

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035122
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035635
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The
path must contain no more than 128 characters. Ensure that you
extract the installation files to an empty directory. Do not extract to
a directory that contains previously extracted files, or any other
files.

252 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Also, ensure that you have executable permission for the package
file.
c. If necessary, change the file permissions by issuing the following
command:
chmod a+x package_name.bin
where package_name is like the following example:

AIX

7.1.0.000-TIV-TSMSRV-AIX.bin

HPUX

7.1.0.000-TIV-TSMSRV-HP-UX.bin

Linux

7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin
7.1.0.000-TIV-TSMSRV-Linuxs390x.bin

Solaris

7.1.0.000-TIV-TSMSRV-SolarisSPARC.bin

In the examples, 7.1.0.000 represents the product release level.

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

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

Windows

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035121
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035636
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035638
b. Change to the directory where you placed the executable file.
In the next step, the files are extracted to the current directory. The
path must contain no more than 128 characters. Ensure that you
extract the installation files to an empty directory. Do not extract to
a directory that contains previously extracted files, or any other
files.
c. To extract the installation files, double-click the executable file:
package_name.exe
where package_name is like this example:
7.1.0.000-TIV-TSMSRV-Windows.exe
The package is large. Therefore, the extraction takes some time.
4. AIX HPUX Solaris To ensure that the Tivoli Storage Manager
wizards work correctly, verify that the following command is enabled:
AIX lsuser

Chapter 7. Scenario 4: New system, network method 253

Upgrading the server from V5 to V7.1

HPUX Solaris logins

By default, the command is enabled.
5. If you plan to install the server by using the graphical wizard of IBM
Installation Manager, review the following information and verify that your
system meets the requirements:
v Verify that all required RPM files are installed. For a list of
AIX
required RPM files and instructions about installing RPM files, see the
section about installing Tivoli Storage Manager by using the installation
wizard in the Installation Guide.
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the
installation wizard.
v WindowsThe user ID that you use during installation must be a user with
local Administrator authority.
v Solaris Ensure that the LD_LIBRARY_PATH_64 environment variable is not
set.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
AIX HPUX Linux Solaris

./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

Windows

install.bat -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

6. If you use the installation wizard, complete the following steps to begin the
installation:

Option Description
Installing from a downloaded package file: 1. Change to the directory where you
downloaded the package file.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat

254 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Option Description
Installing from DVD media: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat
Windows Or, in the directory where the
installation files were extracted,
double-click the install.bat file.

7. If you are installing the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
8. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
9. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
10. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
11. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.
12. HPUX Linux Solaris To prevent server failures during interaction
with DB2, tune the kernel parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
13. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
14. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.
Related concepts:
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555

Chapter 7. Scenario 4: New system, network method 255

Upgrading the server from V5 to V7.1

Scenario 4, manual: Creating the directories and the user ID

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

Before you begin

Review the information about planning space for the server before you complete
this task. See “Worksheet for planning space for the V7.1 server” on page 42.

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

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

Restriction: In the user ID, only lowercase letters (a-z), numerals

(0-9), and the underscore character (_) can be used. The user ID and
group name must comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a
numeral.
v The user ID and group name cannot be user, admin, guest, public,
local, or any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The
following examples show how to create this user ID and group by
using operating system commands:
AIX

# mkgroup id=1001 tsmsrvrs

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

HPUX

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

Linux

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

Solaris

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

256 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

b. Log out and then log in to your system by using the new user ID
and password. Use an interactive login program, such as telnet, so
that you are prompted for the password and can change it if
necessary.
c. If a configuration profile does not exist for the user ID, create the
file. For example, create a .profile file if you are using the Korn
shell (ksh).
Windows
Identify the user account that will own the Tivoli Storage Manager
server instance. When the server is started as a Windows service, this is
the account that the service will log on to. The user account must have
administrative authority on the system. One user account can own
more than one server instance.
You can create a user account, or use an existing account.
If you have multiple servers on one system and want to run each
server with a different user account, create a user account in this step.
a. Create the user ID.

Restriction: The user ID can contain only lowercase letters (a-z),

numerals (0-9), and the underscore character (_). The user ID must
be 30 characters or less, and cannot start with ibm, sql, sys, or a
numeral. The user ID and group name cannot be user, admin, guest,
public, local, or any SQL reserved word.
Use the following command to create the user ID:
net user user_ID * /add

You are prompted to create and verify a password for the new user
ID.
b. Issue the following operating system commands to add the new
user ID to the Administrators groups:
net localgroup Administrators user_ID /add
net localgroup DB2ADMNS user_ID /add
c. Log in to your system, by using the new user ID and password.
d. For all directories that were created for the server instance, ensure
that the user ID for the server instance has read/write access. The
directories to check include the instance directory and all database
and log directories.
2. Create the directories that the server requires. Ensure that you are logged in
under the new user ID that you created.
You need a unique, empty directory for each item in the following table. Create
the database directories, the active log directory, and the archive log directory
on different physical volumes. For space requirements, see “Worksheet for
planning space for the V7.1 server” on page 42.
AIX HPUX Linux Solaris

Chapter 7. Scenario 4: New system, network method 257

Upgrading the server from V5 to V7.1

Table 53. Worksheet for creating required directories

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

Windows

Table 54. Worksheet for creating required directories

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

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

258 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

3. Create additional logical volumes and mount the volumes on the directories
that were created in the previous step.
Related tasks:
“Planning space for the upgrade process and the upgraded server” on page 37
Related reference:
“Server naming best practices” on page 70

Scenario 4: Creating and formatting the new database

Create the server instance and format files for an empty V7.1 database.

Procedure
1. Log on to the system where you installed the V7.1 program.
AIX HPUX Linux Solaris
Log in by using the root user ID. Verify the following items:
v The home directory for the user, /home/tsminst1, exists. If there is
no home directory, you must create it.
The instance directory stores the following core files that are
generated by the Tivoli Storage Manager server:
– The server options file, dsmserv.opt
– The server key database file, cert.kdb, and the .arm files, which
are used by clients and other servers to import the Secure
Sockets Layer certificates of the server
– Device configuration file, if the DEVCONFIG server option does not
specify a fully qualified name
– Volume history file, if the VOLUMEHISTORY server option does not
specify a fully qualified name
– Volumes for DEVTYPE=FILE storage pools, if the directory for
the device class is not fully specified, or not fully qualified
– User exits
– Trace output, if it is not fully qualified
v A shell configuration file, for example, .profile, exists in the home
directory. The root user and instance user ID must have write
permission to this file. For more information, go to the DB2
Information Center (http://pic.dhe.ibm.com/infocenter/db2luw/
v10r5), and search for information about Linux and UNIX
environment variable settings.
Windows
Log on as an administrator.
2. Create a Tivoli Storage Manager instance by using the db2icrt command.
AIX HPUX Linux Solaris
Enter the following command on one line. For the instance name,
specify the user ID that you created to own the instance:
AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

instance_name instance_name

For example, if the user ID for this instance is tsminst1, use the
following command to create the instance:

Chapter 7. Scenario 4: New system, network method 259

Upgrading the server from V5 to V7.1

AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

tsminst1 tsminst1

Remember: From this point on, use this new user ID when you
configure the Tivoli Storage Manager server. Log out of the root user
ID, and log in using the user ID that is the instance owner.
Windows
Enter the following command on one line. The user account that you
specify becomes the user ID that owns the V7.1 server; this ID is the
instance user ID.
db2icrt -s ese -u user_account instance_name

For example, if the user account is tsminst1 and the server instance is
Server1, enter the following command:
db2icrt -s ese -u tsminst1 server1

The database service for the server instance logs on to the user
account that is specified in this command.

Use the registry key name of the V5 server as the instance name for
the V7.1 server. You are prompted to enter the password for the user
account.
The instance name that you specify on this db2icrt command is the
name that you later specify with the -k option on the DSMSERV
LOADFORMAT command, when you create and format the database and
recovery log.
3. Log on to the system by using the user ID that owns the V7.1 server instance
(the instance user ID).
4. Copy the configuration files to the instance directory that you created for the
new server. The files are the configuration files that you saved from the
original V5 server:
v Device configuration
v Server options file, which is typically named dsmserv.opt
For example, if you created the instance directory that is shown in the
example in the step to create directories for the V7.1 server, copy the files into
the following directory:
AIX HPUX Linux Solaris /tsminst1
Windowsd:\tsm\server1
Ensure that the user ID that owns the V7.1 server (the instance user ID) has
ownership or read/write permission to the files that you copied.
5. Edit the server options file.
a. Remove any options that are not supported for V7.1. For the list of deleted
options, see Table 29 on page 67.
b. Verify that the server options file contains at least one VOLUMEHISTORY
option and at least one DEVCONFIG option. By specifying these options, you
ensure that a volume history file and a device configuration file are
generated and updated automatically. If you must restore the database,
these files are required.

260 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

c. Check whether the server options file includes the TXNGROUPMAX option
with a value, and if it does, what the value is. You might want to change
the current value because the default value for this option changed from
256 to 4096, starting in V6. The increased value can improve the
performance for data movement operations such as storage pool migration
and storage pool backup.
v If the server options file does not include this option, the server
automatically uses the new default value of 4096.
v If the server options file includes a value for this option, the server uses
that specified value. If the specified value is less than 4096, consider
increasing the value, or removing the option so that the new default
value is applied.
6. Change the default path for the database.
AIX HPUX Linux Solaris
Change the default path for the database to be the same as the
instance directory for the server. Issue the command:
db2 update dbm cfg using dftdbpath instance_directory

For example:
db2 update dbm cfg using dftdbpath /tsminst1

Windows
Change the default path for the database to be the drive where the
instance directory for the server is located. Complete the following
steps:
a. Click Start > Programs > IBM DB2 > DB2TSM1 > Command
Line Tools > Command Line Processor.
b. Enter quit to exit the command line processor.
A window with a command prompt opens, with the environment
correctly set up to successfully issue the commands in the next
steps.
c. From the command prompt in that window, issue the following
command to set the environment variable for the server instance
that you are working with:
set db2instance=instance_name

The instance_name is the same as the instance name that you

specified when you issued the db2icrt command. For example, to
set the environment variable for the Server1 server instance, issue
the following command:
set db2instance=server1
d. Issue the command to set the default drive:
db2 update dbm cfg using dftdbpath instance_location

For example, if the instance directory is d:\tsm\server1, the

instance location is drive d:. Enter the command:
db2 update dbm cfg using dftdbpath d:
7. Modify the library path to use the version of the IBM Global Security Kit
(GSKit) that is installed with the Tivoli Storage Manager server:
AIX Issue the following command:
export LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH

Chapter 7. Scenario 4: New system, network method 261

Upgrading the server from V5 to V7.1

AIX HPUX Linux Solaris You must update the following files
to set the library path when DB2 or the Tivoli Storage Manager server is
started:
v instance_directory/sqllib/usercshrc
v instance_directory/sqllib/userprofile
For the instance_directory/sqllib/usercshrc file, add the following lines:
v AIX

setenv LIBPATH /usr/opt/ibm/gsk8_64/lib64:$LIBPATH

v HPUX Solaris

setenv LD_LIBRARY_PATH /opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

v Linux

setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

For the instance_directory/sqllib/userprofile file, add the following lines:
v AIX

LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
export LIBPATH
v HPUX Solaris

LD_LIBRARY_PATH=/opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
v Linux

LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Verify the library path settings and ensure that the GSKit version is 8.0.14.14
or later. Issue the following commands:
v AIX

echo $LIBPATH
gsk8capicmd_64 -version
gsk8ver_64
v HPUX Linux Solaris

echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64
If the GSKit version is not 8.0.14.14 or later, you must reinstall the Tivoli
Storage Manager server. The reinstallation ensures that the correct GSKit
version is available.
8. Change to the instance directory that you created for the server.
9. Create and format the database and recovery logs. In the command, specify
the directories that you created for the database and logs. The directories must
be empty.
AIX HPUX Linux Solaris

For example, to get an active log size of 16 GB (16384 MB, the default
size), issue the following command, on one line:
/opt/tivoli/tsm/server/bin/dsmserv loadformat \
dbdir=/tsmdb001,/tsmdb002,/tsmdb003,/tsmdb004 \
activelogsize=16384 activelogdirectory=/tsmlog \
mirrorlogdirectory=/tsmlogmirror archlogdirectory=/tsmarchlog

Windows

262 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

For example, to get an active log size of 16 GB (16384 MB, the default
size) for the Server1 server instance, issue the following command, on
one line:
"c:\Program Files\Tivoli\TSM\server\dsmserv" loadformat
dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog
If you have already created the first server instance on the system
(server1) and are creating more, then you must use the -k option. The
-k option specifies the instance name for running this utility. For
example, if the instance name for the server is server2, issue the
command:
"c:\Program Files\Tivoli\TSM\server\dsmserv" -k server2
loadformat dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog
10. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39
Related reference:
DSMSERV LOADFORMAT (Format a database)
“Deleted server commands, utilities, and options” on page 65

Scenario 4: Moving the server database over a network

Move the database by starting the insertion process for the V7.1 server to accept
the server database. Then, start the extraction process for the V5 server to extract
and send the database.

Before you begin

Ensure that the V5 server and the V7.1 server are not running.

Procedure
1. Verify that there is a good network connection between the two systems.
2. Start the insertion process on the V7.1 server to accept the database. To monitor
the process, direct the output of the process to a file. For example, start the
server, allowing 60 minutes (the default time) for the other server to contact the
V7.1 server and directing the process output to insert.out, by using this
command:
AIX HPUX Linux Solaris

nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \

sesswait=60 >insert.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\server\dsmserv" insertdb

sesswait=60 1>>insert.out 2>&1

The server starts and waits up to 60 minutes to be contacted by the original

server. Some time might pass during which no messages are issued. During
this time, DB2 operations are running in the background. Optional: To verify

Chapter 7. Scenario 4: New system, network method 263

Upgrading the server from V5 to V7.1

that operations are continuing as expected, monitor the CPU and I/O usage for
the server process and the corresponding DB2 process.
3. Monitor the output of the DSMSERV INSERTDB process. Verify that the DSMSERV
INSERTDB process has issued the following message before continuing to the
next step:
ANR1336I INSERTDB: Ready for connections from the source server

Issue the following command to monitor the process output in the insert.out
file:
tail -f insert.out

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
4. Start the extraction from the original server. Specify the TCP/IP address and
port for the V7.1 server. Direct the output of the process to a file for
monitoring. For example, enter the following command on one line:
AIX

nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 &

HPUX Linux Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" extractdb hladdress=127.0.0.1

lladdress=1500 1>>extract.out 2>&1
5. Monitor the processes for errors and warning messages, and for items that you
might need to act on. From the instance directory for the server that you are
upgrading, issue the following command to monitor the extraction process:
tail -f extract.out

The length of time that the process runs depends on the size of the database,
the hardware being used, and the network.
6. Examine the process outputs for the extraction and insertion processes to find
the messages that indicate the success or failure of the operations.

Process Success message Failure message

Extraction ANR1382I EXTRACTDB: Process 1, ANR1396E EXTRACTDB: Process 1,
database extract, has database extract, has completed
completed. with errors.
Insertion ANR1395I INSERTDB: Process 1, ANR1396E INSERTDB: Process 1,
database insert, has completed. database insert, has completed
with errors.

Related reference:
“DSMUPGRD EXTRACTDB (Extract data from a V5 server database)” on page 529

“DSMSERV INSERTDB (Move a server database into an empty database)” on page

538

264 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Scenario 4: Creating a Windows service for the server

instance
Windows

A Windows service is created for the Tivoli Storage Manager V7.1 server
automatically if you use the upgrade wizard (dsmupgdx). If you do not use the
wizard, you must create the Windows service for the Tivoli Storage Manager
server manually.

Procedure
1. Change to the installation directory for the server program. By default, the
directory is C:\Program Files\Tivoli\TSM\console. If you installed the server
in a different directory, change to the console subdirectory of the server
installation directory.
2. Install the Windows service by using the Tivoli Storage Manager server
instance name and password in the service name. Issue the following
command:
install "TSM server_instance_name"
"C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
instance_owner instance_owner_password

where:
"TSM server_instance_name" is the name of the service that is being
installed.
server_instance_name is the instance name that was specified when you
issued the db2icrt command.
instance_owner is the instance owner account; this account will own the
service.
instance_owner_password is the password for the instance owner account.
Example
To install the Windows service for the server1 server instance, enter the
following command on one line. The example uses rudy as the instance
owner and s21ret as the password for the instance owner account.
install "TSM server1" "C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
rudy s21ret
3. Optional: Manually change the service to an automatic startup type by using
Windows administrative tools (Administrative Tools > Services).
Related tasks:
“Starting the server on Windows systems” on page 331

Scenario 4: Configuring the system for database backup

The database manager and the Tivoli Storage Manager API must be configured so
that the database manager can back up the server database. The configuration is
completed for you automatically if you use the upgrade wizard (dsmupgdx). If you
do not use the wizard, you must complete the configuration manually.

Procedure
v “Scenario 4: Configuring the system for database backup on AIX, HP-UX, Linux,
and Oracle Solaris systems” on page 266
v “Scenario 4: Configuring the system for database backup on Microsoft Windows
systems” on page 268

Chapter 7. Scenario 4: New system, network method 265

Upgrading the server from V5 to V7.1

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Scenario 4: Configuring the system for database backup on AIX,

HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

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

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, replace the example values with your actual values.
The examples use tsminst1 for the server instance user ID, /tsminst1 for the Tivoli
Storage Manager server instance directory, and /home/tsminst1 as the home
directory of the server instance user.

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

266 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

2. Log out and log in again as tsminst1, or issue this command:

. ~/.profile

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

The value for SERVERNAME must be consistent in the tsmdbmgr.opt and dsm.sys
files.
4. Locate the Tivoli Storage Manager API dsm.sys configuration file. By default,
the dsm.sys file is in the following location:

server_bin_directory/dbbkapi/dsm.sys
5. As root user, add the following lines to the dsm.sys configuration file:
servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
errorlogname /tsminst1
nodename $$_TSMDBMGR_$$

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

where port_number specifies the port that you use for shared memory.
b. In the dsm.sys configuration file, locate the following lines:

Chapter 7. Scenario 4: New system, network method 267

Upgrading the server from V5 to V7.1

commmethod tcpip
tcpserveraddr localhost
tcpport port_number

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port that you use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Scenario 4: Configuring the system for database backup on

Microsoft Windows systems
Windows

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, the examples use server1 for the database instance
and d:\tsmserver1 for the Tivoli Storage Manager server directory. When you
issue the commands, replace these values with your actual values.

Procedure
1. Create a file that is named tsmdbmgr.env in the d:\tsmserver1 directory with
the following contents:
DSMI_CONFIG=server_instance_directory\tsmdbmgr.opt
DSMI_LOG=server_instance_directory
2. Set the DSMI_ api environment-variable configuration for the database instance:
a. Open a DB2 command window. One method is to go to the C:\Program
Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage
Manager in a different location, go to the db2\bin subdirectory in your main
installation directory. Then, issue the following command:
db2cmd
b. Issue the following command:
db2set -i server1 DB2_VENDOR_INI=d:\tsmserver1\tsmdbmgr.env
c. Create a file that is named tsmdbmgr.opt in the d:\tsmserver1 directory
with the following contents:
*************************************************
nodename $$_TSMDBMGR_$$
commmethod tcpip

268 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

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

where port_number specifies the port to use for shared memory.

b. In the tsmdbmgr.opt file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport 1500

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port to use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Chapter 7. Scenario 4: New system, network method 269

270 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 8. Clustered environments: Upgrade procedures
To upgrade a Tivoli Storage Manager server from V5 to V7.1 in a clustered
environment, you must complete planning, preparation, installation, and
configuration tasks. The procedures vary, depending on the operating system.

About this task

Follow the procedure for your operating system:

Operating system Procedure

AIX “Upgrading the server to V7.1 in an AIX
clustered environment”
Windows “Upgrading the server to V7.1 in a Windows
clustered environment” on page 273

Upgrading the server to V7.1 in an AIX clustered environment

AIX

To upgrade Tivoli Storage Manager from V5.5 to V7.1 in a clustered environment

on an AIX operating system, you must mount all shared resources on the primary
node. Install the V7.1 server on the primary node and upgrade each instance.
Then, install the V7.1 server on each secondary node.

Before you begin

If you are planning an in-place upgrade on the same system, ensure that you retain
the installation media from the base release of the installed V5 server. If you
installed Tivoli Storage Manager from a DVD, ensure that the DVD is available. If
you installed Tivoli Storage Manager from a downloaded package, ensure that the
downloaded files are available. If the upgrade fails, and the server license module
is uninstalled, the installation media from the V5 server base release are required
to reinstall the license.

Procedure
1. Mount all shared resources on the primary node. If your environment includes
multiple instances of Tivoli Storage Manager, shared resources for all instances
must be accessible to the primary node during the upgrade.
2. Select a scenario for upgrading the server:
v Chapter 4, “Scenario 1: Same system, media method,” on page 91
v Chapter 5, “Scenario 2: Same system, network method,” on page 135
v Chapter 6, “Scenario 3: New system, media method,” on page 177
v Chapter 7, “Scenario 4: New system, network method,” on page 225
3. On the primary node, for each instance, prepare the system for the upgrade.
Complete the steps for your scenario:
v “Scenario 1: Preparing for the upgrade” on page 91
v “Scenario 2: Preparing for the upgrade” on page 135
v “Scenario 3: Preparing for the upgrade” on page 177

© Copyright IBM Corp. 2009, 2013 271

v “Scenario 4: Preparing for the upgrade” on page 225
4. If you are upgrading Tivoli Storage Manager on the same system, complete
the following steps on the primary node:
a. “Installing the upgrade utilities on AIX systems” on page 287
b. “Setting environment variables for the upgrade utilities on AIX, HP-UX,
Linux, and Oracle Solaris systems” on page 292
c. “Uninstalling the V5 program before installing V7.1” on page 295
d. “Installing the V7.1 server” on page 297
5. If you are upgrading Tivoli Storage Manager on a different system, complete
the following steps on the primary node:
a. “Installing the upgrade utilities on AIX systems” on page 287
b. “Setting environment variables for the upgrade utilities on AIX, HP-UX,
Linux, and Oracle Solaris systems” on page 292
c. “Installing the V7.1 server” on page 297
6. For each instance, complete the following steps:
a. “Preparing the database of a V5 server for upgrade” on page 294
b. “Creating the directories and the user ID for the upgraded server instance”
on page 302
c. “Upgrading the server by using the upgrade wizard” on page 305
Ensure that you upgrade the server for each instance. Do not configure the
server instance to start automatically following a system restart. Upon
completion of the upgrade wizard, the instance is started.
7. Adjust the cluster start and stop scripts to use the correct instance directories.
Each instance requires its own set of scripts. Tivoli Storage Manager V7.1 uses
a different start and stop script framework than V5.5. Use the following V7
framework:
/opt/tivoli/tsm/server/bin/startserver
/opt/tivoli/tsm/server/bin/stopserver
8. Test the start and stop scripts to ensure that they work as expected.
9. On the primary node, stop all server instances.
10. For each secondary node, install the V7.1 server. Follow the instructions in
“Installing the V7.1 server” on page 297.
11. For each secondary node, adjust the cluster start and stop scripts to use the
correct instance directories. Each instance requires its own set of scripts. Use
the following V7 framework:
/opt/tivoli/tsm/server/bin/startserver
/opt/tivoli/tsm/server/bin/stopserver
12. If the DB2 instance directory is shared between the nodes in the cluster,
continue with Chapter 10, “Taking the first steps after upgrade,” on page 323.
13. If the DB2 instance directory is not shared between the nodes in the cluster,
for each secondary node, complete the following steps:
a. Create the directories and the user ID for the upgraded server instance.
Follow the instructions in “Creating the directories and the user ID for the
upgraded server instance” on page 302.
b. Mount all shared resources for all server instances on the secondary node.
c. As root user, run the configuration wizard:
/opt/tivoli/tsm/server/bin/dsmicfgx
Specify the correct instance directory for each server instance. Select the
box to indicate that the server instance is being configured for a secondary

272 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
node of a cluster. By selecting this box, you create the required database
instances and catalog the database in each instance.
d. Test the start and stop scripts to ensure that they work as expected.
e. Complete the verification and configuration steps, as described in
Chapter 10, “Taking the first steps after upgrade,” on page 323.

Upgrading the server to V7.1 in a Windows clustered environment

Windows

To upgrade the Tivoli Storage Manager server from V5.5 to V7.1 in a clustered
environment on a Windows system, plan the upgrade. Then, install the V7.1 server
on all nodes in the cluster. Finally, run the upgrade wizard, which inserts the new
database and configures the system.

Before you begin

If you are planning an in-place upgrade on the same system, ensure that you retain
the installation media from the base release of the installed V5 server. If you
installed Tivoli Storage Manager from a DVD, ensure that the DVD is available. If
you installed Tivoli Storage Manager from a downloaded package, ensure that the
downloaded files are available. If the upgrade fails, and the server license module
is uninstalled, the installation media from the V5 server base release are required
to reinstall the license.

Procedure
1. Plan the upgrade and prepare the system, as described in “Planning the
upgrade and preparing the system.”
2. Run the upgrade wizard, as described in “Installing the V7.1 server and
running the upgrade wizard” on page 274.

Planning the upgrade and preparing the system

Windows

Before you upgrade the server from V5.5 to V7.1 in a clustered environment on a
Windows system, select an upgrade scenario and prepare the system.

Procedure
1. Select a scenario for upgrading the server:
v Chapter 4, “Scenario 1: Same system, media method,” on page 91
v Chapter 5, “Scenario 2: Same system, network method,” on page 135
v Chapter 6, “Scenario 3: New system, media method,” on page 177
v Chapter 7, “Scenario 4: New system, network method,” on page 225
2. If the Tivoli Storage Manager server is installed on a Windows Server 2012
operating system, install the failover cluster automation server and the failover
cluster command interface. To install these components, issue the following
commands from Windows 2.0 PowerShell on each node in the cluster:
Install-WindowsFeature -Name RSAT-Clustering-AutomationServer
Install-WindowsFeature -Name RSAT-Clustering-CmdInterface
3. If you are upgrading on a new system, set up the nodes for the cluster and
create a resource group.

Chapter 8. Clustered environments: Upgrade procedures 273

4. On the primary node, for each instance, prepare the system for the upgrade.
Complete the steps for your scenario:
v “Scenario 1: Preparing for the upgrade” on page 91
v “Scenario 2: Preparing for the upgrade” on page 135
v “Scenario 3: Preparing for the upgrade” on page 177
v “Scenario 4: Preparing for the upgrade” on page 225
5. Install the upgrade utilities on the V5 system. For instructions, see “Installing
the upgrade utilities on Microsoft Windows systems” on page 293.
6. For each server instance, prepare the database of the V5 server as described in
“Preparing the database of a V5 server for upgrade” on page 294.
7. If you are upgrading on the same system, delete the V5.5 cluster resources:
a. Ensure that the primary node owns the cluster resources.
b. Record the values of the TCP/IP address and the network name of the
server items in the group by using Microsoft Failover Cluster Manager.
c. Delete the Tivoli Storage Manager resource and the network name.
8. If you are upgrading on the same system, uninstall the V5.5 server. For each
node in the cluster, uninstall the V5.5 server, server license, and device driver.
Do not remove the database, recovery log, server options file, or any other
related files or directories. Follow the instructions in “Uninstalling the V5
program on Microsoft Windows systems” on page 297.
9. Edit the V5.5 server options file:
a. Remove any options that are not supported for V7.1. For a list of deleted
options, see “Deleted server commands, utilities, and options” on page 65.
b. Ensure that the server options file contains at least one VOLUMEHISTORY
option and at least one DEVCONFIG option. A volume history file and a device
configuration file are required when you restore the database.
c. Determine whether the server options file includes the TXNGROUPMAX option
with a value. If the option is included and the value is less than 4096,
consider increasing the value, or removing the option so that the server uses
the new default value. The increased value can improve the performance for
data movement operations such as storage pool migration and storage pool
backup.

What to do next

After you plan the upgrade and prepare the system, complete the steps in
“Installing the V7.1 server and running the upgrade wizard.”

Installing the V7.1 server and running the upgrade wizard

Windows

To complete the upgrade, you must install the V7.1 server on all nodes in the
cluster. Then, run the upgrade wizard, which inserts the new database and
configures the system.

Procedure
1. Install the Tivoli Storage Manager V7.1 server on all nodes. For instructions, see
“Installing the V7.1 server” on page 297.

274 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
2. On the primary node, create the user ID for the upgraded server instance. The
user ID for the instance must be defined to the domain controller. For
instructions, see “Creating the directories and the user ID for the upgraded
server instance” on page 302.
3. On the primary node, create the directories for the upgraded server instance.
Ensure that all database and recovery log directories are on a shared disk in the
resource group. For instructions, see “Creating the directories and the user ID
for the upgraded server instance” on page 302. Create the directories that the
server instance requires for database and recovery logs, as identified in the
table in that section.
4. On the primary node, start the upgrade wizard by clicking Start > All
Programs > Tivoli Storage Manager > Upgrade Wizard.
Follow the steps in the upgrade wizard:
a. When you are prompted to enter the instance name, enter the name of the
instance that you are reclustering.
b. When you are prompted to enter the instance user ID, enter the user ID in
this format: domain\userid.
c. When you are prompted to select the nodes for the cluster, select the
primary node and any other nodes that you want to include.
d. When you are prompted to specify directories for the instance, database,
and logs, specify directories that are on a shared disk.
e. When you are prompted to specify cluster network information, select a
public network connection.
f. Review the selections in the Summary panel. If they are correct, click Next
to format and insert the database.
5. If the system includes more than one server instance to be upgraded, run the
upgrade wizard for each instance.
After you have followed the steps in the upgrade wizard, the upgrade is
complete and the system is configured.
6. Optional: If the upgrade was done on the existing system, delete the Tivoli
Storage Manager V5.5 database files.

What to do next

If a native device driver is available on Windows for the tape drives or medium
changers that you plan to use, use the native device driver. If a native device
driver is not available on Windows for the tape drives or medium changers that
you plan to use, install the Tivoli Storage Manager device driver by issuing the
dpinst.exe /a command. The dpinst.exe file is in the device driver directory. The
default directory is C:\Program Files\Tivoli\TSM\device\drivers.

Complete the verification and configuration steps, as described in Chapter 10,

“Taking the first steps after upgrade,” on page 323.

Chapter 8. Clustered environments: Upgrade procedures 275

276 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 9. General procedures for upgrading a server to V7.1
Utilities and a wizard are provided to assist in the upgrade of the IBM Tivoli
Storage Manager server. This general set of procedures can be used for any
upgrade scenario. You can instead select the scenario that matches your upgrade
plan and use the set of procedures that is specifically for that scenario.

Procedure

The procedure for upgrading the server includes the following tasks:
1. “Preparing for the upgrade”
2. “Installing the upgrade utilities on the original server” on page 287
3. “Preparing the database of a V5 server for upgrade” on page 294
4. Same-system upgrade only: “Uninstalling the V5 program before installing
V7.1” on page 295
5. “Installing the V7.1 server” on page 297
6. “Creating the directories and the user ID for the upgraded server instance” on
page 302
7. Upgrading the server by using one of the following methods:
v “Upgrading the server by using the upgrade wizard” on page 305
v “Upgrading the server manually by using utilities” on page 307
8. The following tasks are completed after the upgrade:
a. “Verifying access to storage pools on disk” on page 323
b. “Setting up Solaris services for the server instance” on page 324
c. “Configuring server options for server database maintenance” on page 324
d. “Starting the server instance after the upgrade” on page 325
e. “Registering licenses” on page 334
f. “Backing up the database after upgrading the server” on page 335
g. “Verifying the upgraded server” on page 336
h. “Changing the host name for the Tivoli Storage Manager server” on page
336
i. “Updating automation” on page 338
j. “Monitoring the upgraded server” on page 339
k. “Removing GSKit Version 7 after upgrading to Tivoli Storage Manager
V7.1” on page 340

Preparing for the upgrade

Prepare for the upgrade by checking requirements, preparing the space that is
required, backing up the server, and modifying certain server settings.

About this task

Follow the preparation steps carefully to protect your server and its data.

Important: It is possible, after the upgrade to V7.1 is complete, that conditions

might cause the need to temporarily revert to the previous version of the server.
Successfully reverting to the previous version of the server is possible only if you

© Copyright IBM Corp. 2009, 2013 277

Upgrading the server from V5 to V7.1

have completed all preparation steps. To understand why it is important to

complete all preparation steps, review the procedure for reverting an upgraded
server to its previous version.

Procedure

To prepare for the upgrade, complete the following steps:

1. “Checking the prerequisites for the upgrade”
2. “Preparing space for the upgrade process” on page 281
3. “Modifying the server before the upgrade” on page 282
4. “Disabling sessions” on page 284
5. “Backing up storage pools and the server database” on page 284
6. “Moving the NODELOCK file” on page 285
7. “Backing up configuration information” on page 285
8. “Creating a summary of database contents” on page 286
9. “Stopping the server before installing the upgrade” on page 286
Related tasks:
“Reverting from V7.1 to the previous V5 server version” on page 351

Checking the prerequisites for the upgrade

Check your system against requirements for the server.

Before you begin

Requirement: If you are upgrading the Tivoli Storage Manager server on the same
system, the system must meet the minimum requirements for both the V5 and V7.1
servers.

Procedure
1. Ensure that the server that you plan to upgrade is at the V5.5 release level, and
that the latest interim fix is installed. For example, if the server is at V5.5.6,
install the latest interim fix for V5.5.6. Take the following actions:
a. Select the appropriate server level. For detailed guidelines, see
“Determining the appropriate level for a V5 server before an upgrade” on
page 36. If the server is at an appropriate level, no action is required.
b. If the server is not at an appropriate level, download the appropriate server
fix pack and the latest interim fix from the FTP downloads site at
ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server/. Locate the appropriate version of Tivoli Storage
Manager and install it.
2. Ensure that the system where the V5 server is located meets the minimum
requirements. Review the information in “Hardware and software requirements
for the V5 server system that is being upgraded” on page 17 to determine
whether you must update your system before you continue.
3. Ensure that the system where you plan to install the V7.1 server meets
requirements for the operating system type and level. For the latest information
about system requirements, see Tivoli Storage Manager Supported Operating
Systems (http://www.ibm.com/support/docview.wss?uid=swg21243309).
If you are upgrading Tivoli Storage Manager to a different operating system, a
limited set of migration paths is available. For instructions about migrating a
server that is running on a z/OS operating system, see Part 3, “Migrating Tivoli

278 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Storage Manager V5 servers on z/OS systems to V7.1 on AIX or Linux on

System z,” on page 437. For instructions about migrating a server that is
running on an AIX, HP-UX, or Solaris operating system, see Part 2, “Migrating
Tivoli Storage Manager V5 servers on AIX, HP-UX, or Solaris systems to V7.1
on Linux,” on page 355.
Some platforms that were supported for earlier versions of the server are not
supported for V7.1. If the server that you want to upgrade is running on one of
these platforms, you cannot upgrade your server to V7.1 on the same platform.
You must install your V7.1 server on a system that is a specific supported
platform, depending on the original platform. For required platforms, see the
following table.
Table 55. Required platforms for upgrading from V5 to V7.1
Platform for V5 server Required platform for upgrade to V7.1
HP-UX running on a PA-RISC system HP-UX running on an Intel Itanium system
Linux running on an Itanium system (IA64) Linux running on an x86_64 system
Linux running on an x86_32 system Linux running on an x86_64 system
Solaris running on an x86_64 system Linux running on an x86_64 system
Windows running on an Itanium system Windows running on an x86_64 system
(IA64)

If you are upgrading from Tivoli Storage Manager V5 to V7.1 on a new system,
restrictions apply. Ensure that you install the V7.1 server in a compatible
hardware and software environment, as described in the following table.
Table 56. Requirements for upgrading from V5 to V7.1 on a new system
V5 server V7.1 server Comments
AIX running on an IBM AIX running on an IBM
POWER system POWER system
HP-UX running on an HP-UX running on an
Itanium system Itanium system
HP-UX running on a HP-UX running on an HP-UX running on PA-RISC
PA-RISC system Itanium system is not supported for V7.1
servers.
Linux running on an IBM Linux running on an IBM
POWER system POWER system
Linux running on an Itanium Linux running on an x86_64 Linux running on Itanium is
system (IA64) system not supported for V7.1
servers.
Linux running on an x86_32 Linux running on an x86_64 Linux running on x86_32 is
system system not supported for V7.1
servers.
Linux on System z Linux on System z

Chapter 9. General procedures for upgrading a server to V7.1 279

Upgrading the server from V5 to V7.1

Table 56. Requirements for upgrading from V5 to V7.1 on a new system (continued)
V5 server V7.1 server Comments
Solaris running on an x86_64 Operating system depends A V7.1 server cannot be
system on the migration method installed on a Solaris x86_64
system. However, you can
migrate a V5 server that is
running on a Solaris x86_64
operating system to V7.1 on
a Linux x86_64 operating
system. For instructions, see
Part 2, “Migrating Tivoli
Storage Manager V5 servers
on AIX, HP-UX, or Solaris
systems to V7.1 on Linux,”
on page 355.

Alternatively, you can

migrate the Solaris x86_64
system by installing a V7.1
server on any operating
system that is supported for
V7.1. Then, use Tivoli
Storage Manager server
EXPORT and IMPORT
commands to move the
server from the V5 source
system to the V7.1 target
system.
Windows running on an Windows running on an Windows running on
Itanium system (IA64) x86_64 system Itanium is not supported for
V7.1 servers.
Windows running on an Windows running on an Windows running on x86_32
x86_32 system x86_64 system is not supported for V7.1
servers.
z/OS AIX or Linux on System z See the section on migrating
from V5 on z/OS to V7.1 on
AIX or Linux on System z.

4. Verify that the system memory meets the server requirements.

v If you plan to upgrade the server on the same system, and use the network
method for moving the database, you must ensure that the system memory
is sufficient.
When you run the process that extracts the database from the existing server
and inserts the database for the new server, the net effect is that two servers
are running.
v If you plan to run multiple instances of the V7.1 server on the system, each
instance requires the memory that is listed for one server. Multiply the
memory for one server by the number of instances that are planned for the
system.
For specific information about memory requirements, see the section for your
operating system:

280 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 57. Memory requirements for the V7.1 system

Operating system Memory requirements
AIX “Server requirements on AIX systems” on
page 21
HP-UX “Server requirements on HP-UX systems” on
page 24
Linux “Server requirements on Linux systems” on
page 26
Solaris “Server requirements on Solaris systems” on
page 31
Windows “Server requirements on Microsoft Windows
systems” on page 33

5. Ensure that the system has enough disk storage for the database and recovery
logs. Review the planning information for requirements and guidance.
If you are adding new hardware for the server, such as new disk storage for
the database, ensure that the hardware is installed and running.
If you plan to upgrade the server on the same system, you can take one of two
approaches:
v Ensure that the system has enough disk storage for storing database and
recovery logs for both the original server and the new V7.1 server. Both are
stored on disk storage during the upgrade process.
v After you back up the V5 database and extract the data to media, reconfigure
the disk subsystem that is used for the database storage. Then, insert the
data to the new database from the media. You must take this approach if you
do not have enough disk space for both servers.
6. If you are moving the server to a new system, ensure that the new system can
access the storage devices that are used on the original system. These storage
devices include the disk and tape devices that are used to store client data.
If you are moving the database by using the media method, it might be
necessary to leave a storage device attached to the original system to extract the
database. Then, move the storage device to the new system.
Related concepts:
“Hardware and software requirements for upgrading to the V7.1 server” on page
17

Preparing space for the upgrade process

The amount and type of space that is required for the upgrade process depends on
whether you are upgrading to the new version on the same system or a different
system. Another factor is whether you will be using the media method or the
network method for moving data into the new database.

Procedure
1. Verify that the system has the amount of space that was estimated in the
planning step. Use the planning worksheet that you completed with your
information. See “Worksheet for planning space for the V7.1 server” on page
42.
2. If you plan to extract the original server database to media for later insertion
into the new database, ensure that you have space available for storing the
database and the manifest file that the extraction process creates.

Chapter 9. General procedures for upgrading a server to V7.1 281

Upgrading the server from V5 to V7.1

a. Identify the device class to which you will extract the original database. The
definition must exist in the server database, not just in the device
configuration file. View information about devices classes by issuing the
command:
query devclass format=detailed
The device class must be a sequential device class that has volumes or space
available. Define a new device class if necessary. The device class type
cannot be NAS or CENTERA.

Important: You must confirm now that the definition that is in the server
database for the device class is correct. After you prepare the database for
upgrade (by completing the Prepare Database phase in the upgrade wizard,
or by using the DSMUPGRD PREPAREDB utility), you cannot update this device
class definition. For example, check the path for a FILE device class. If you
copied the original server to a different system to extract the data, the path
might be different on the current system.
b. Ensure that space or volumes are available in the selected device class. The
amount of space that you need is about the same as the current size of the
original database.
For example, if the device class is FILE, ensure that the directory has
sufficient space for your environment. If the device class is TAPE, ensure
that sufficient scratch volumes are available for your environment.
Ensure that the instance user ID that you create for the upgraded server has
access permission to the location of the extracted data.
c. Check that the access permissions are correct for the location that you plan
to specify for the manifest file.
The user ID that will run the database preparation and extraction utilities
(DSMUPGRD PREPAREDB and DSMUPGRD EXTRACTDB) must have write access to
this file. This is typically the root user ID.
When the data is later inserted into the V7.1 database, the instance user ID
that you use for the upgraded server must have access permission for the
manifest file.
The manifest file is typically less than 1 KB.
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39

Modifying the server before the upgrade

A command must be run on the server to prevent one type of problem during the
upgrade process. Some modifications to typical server settings can be useful to
prepare for the upgrade.

Procedure
1. From a Tivoli Storage Manager administrative command line, issue the
command:
convert ussfilespace

This command fixes a problem that might exist in older Tivoli Storage Manager
databases. If the problem does not exist in your database, the command is
completed and you might see error ANR2034E. This error can be ignored. For

282 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

more information, see Technote 1408895 (http://www.ibm.com/support/

docview.wss?uid=swg21408895). If the problem exists in your database, the
command might take some time to run.

Important: Do not skip this step. If your database has the problem and you do
not run this command now, the DSMUPGRD PREPAREDB utility fails when you run
it. You must then restart the V5 server and run the CONVERT USSFILESPACE
command before you continue the upgrade process.
2. Review the steps for reverting to the earlier version of the server in the section,
“Reverting from V7.1 to the previous V5 server version” on page 351.
If you must revert to the earlier version after the upgrade to V7.1, the results of
the reversion will be better if you understand the steps and prepare for the
possibility now.
3. Make the following adjustments to settings on your server and clients. These
adjustments must be done to make it possible for you to revert to the original
server after the upgrade, if problems occur.
a. For each sequential-access storage pool, set the REUSEDELAY parameter to the
number of days during which you want to be able to revert to the original
server, if necessary.
For example, if you want to be able to revert to the original server for up to
30 days after the upgrade to V7.1, set the REUSEDELAY parameter to 31 days.
Issue the following administrative command:
update stgpool sequential_access_storage_pool reusedelay=31
b. For each copy storage pool, set the RECLAIM parameter to 100 (meaning
100%). Issue the following administrative command:
update stgpool copy_storage_pool reclaim=100
c. If you typically use a DELETE VOLHISTORY command to delete database
backups, ensure that the command does not delete database backups too
frequently. The interval between backups should be at least the same
number of days that you set for the REUSEDELAY period for sequential-access
storage pools. For example, to delete database backups every 45 days, issue
the following administrative command:
delete volhist type=dbbackup todate=-45
d. For important clients that use the server, verify that the value for the
schedlogretention client option is set to retain the client schedule log for a
sufficient time. Update the option for clients if needed.
The entries in the client schedule log might be useful if the server must
revert to the original version. If the retention period for the schedule log is
too short, the schedule log information might be deleted too soon.
For example, to prune the log every 45 days and save the log entries, add
the following option:
schedlogretention 45 S
AIX HPUX Linux Solaris Add the option to the dsm.sys file
within a server stanza.
Windows Add the option to the client options file, dsm.opt.

Chapter 9. General procedures for upgrading a server to V7.1 283

Upgrading the server from V5 to V7.1

Disabling sessions
In preparation for the upgrade, prevent activity on the server by disabling new
sessions. Cancel any existing sessions.

About this task

The commands in the following procedure are Tivoli Storage Manager

administrative commands.

Procedure
1. Prevent all clients, storage agents, and other servers from starting new sessions
with the server. Use the commands:
disable sessions client
disable sessions server
For more information about these commands and other Tivoli Storage Manager
administrative commands, see the Administrator's Reference.
2. Verify whether any sessions exist, and notify the users that the server is going
to be stopped. To check for existing sessions, use the command:
query session
3. Cancel sessions that are still running. Use the command:
cancel session all

Backing up storage pools and the server database

Immediately before upgrading the server, back up primary storage pools to copy
storage pools, and perform a full database backup.

Before you begin

Back up storage pools and the server database by using Tivoli Storage Manager
administrative commands:

Procedure
1. Back up primary storage pools to copy storage pools by using the BACKUP
STGPOOL command:
backup stgpool primary_pool copy_stg

where primary_pool specifies the primary storage pool and copy_stg specifies the
copy storage pool. If you have been performing regular backups of the storage
pools, this step backs up only the data that was added to the primary storage
pools since they were last backed up.
2. Back up the database. The preferred method is to use a snapshot backup. A
snapshot backup is a full database backup that does not interrupt any
scheduled database backups. Issue the command:
backup db type=dbsnapshot devclass=device_class_name

The device class that you specify must exist and have volumes that are
available to it. For example, to perform a snapshot backup of your database to
the TAPECLASS device class by using scratch volumes, enter:
backup db type=dbsnapshot devclass=tapeclass

To use specific volumes instead of scratch volumes, specify the volume names
in the command.

284 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Tip: Consider making two copies of the backup to protect the backup from
media failures. Ensure that at least one full database backup is available onsite.
If you must restore the database after a failed upgrade, having an onsite
backup database saves time.

Moving the NODELOCK file

To ensure that licensing information is updated during the upgrade process, move
the NODELOCK file from the server instance directory to another directory.

About this task

The NODELOCK file contains the licensing information from the previous Tivoli
Storage Manager installation. This licensing information is replaced when the
upgrade is complete.

Procedure
1. In the server instance directory of your installation, locate the NODELOCK file.
2. Move the NODELOCK file to another directory. For example, you can save it to a
directory where you are saving configuration files from the previous release.

Backing up configuration information

Before you install the new version, back up critical files and information for each
server instance. Store the files in a safe place, on a different system from the
system that is being upgraded or on offline media, such as a CD. The files are
required after the installation of the new software version is complete. You also
need these files if you must revert to the previous version after the upgrade.

Procedure
1. Back up device configuration information to another directory by using the
following Tivoli Storage Manager administrative command:
backup devconfig filenames=file_name

where file_name specifies the file in which to store device configuration

information.
2. Back up volume history information to another directory by using the
following Tivoli Storage Manager administrative command:
backup volhistory filenames=file_name

where file_name specifies the file in which to store volume history information.
Ensure that the volume history includes information about the database backup
that you completed in the preceding steps. For example, issue the command:
query volhistory type=dbsnapshot

Review the query output to verify that the time stamp for the database backup
matches the actual time of the backup.
3. Save copies of the following files, which are in the server instance directory:
v Server options file, typically named dsmserv.opt
v dsmserv.dsk

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.

Chapter 9. General procedures for upgrading a server to V7.1 285

Upgrading the server from V5 to V7.1

4. In the server instance directory, look for the accounting log file, dsmaccnt.log.
If the file exists, save a copy.
5. Back up any scripts that were used to complete daily housekeeping for the
server. Examine the scripts for changes that are needed after the upgrade.
6. Store the device configuration file, the volume history file, the server options
file, and the other files in a safe place. Ensure that the files are stored on a
different system from the system that is being upgraded, or on offline media.

Creating a summary of database contents

Create a summary of the contents of the original database. After the upgrade, you
can use the same commands to compare the results and to confirm that the
database contents are intact.

Procedure

Run commands that give a summary of information about your database contents.
For example, issue commands that summarize the file spaces that are being
protected, and save the results. For a list of commands, see “Sample commands to
run for validation of the database upgrade” on page 546.
Related reference:
“Sample commands to run for validation of the database upgrade” on page 546

Stopping the server before installing the upgrade

Stop all server processes and unmount any tapes that are mounted. Then, stop the
server.

Procedure

Use Tivoli Storage Manager administrative commands to stop the server:

1. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the following commands:
query process
cancel process process_number

Allow time for the processes to be stopped. Some processes, such as storage
pool migration, might take some time to stop.
For more information about the QUERY PROCESS and CANCEL PROCESS commands
and other Tivoli Storage Manager administrative commands, see the
Administrator's Reference.
2. After all sessions and processes are stopped, determine whether any tapes are
mounted. Unmount any tapes that are mounted. Use the following commands:
query mount
dismount volume volume_name
3. Stop the server. Use the following command:
halt

286 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Installing the upgrade utilities on the original server

You must install the upgrade utilities on the system where the V5 server is located.
The installation package for the utilities must be downloaded from a website.

Before you begin

The preferred method is to install the latest available version of the upgrade
utilities. For more information about selecting the version, see “Determining the
appropriate level for a V5 server before an upgrade” on page 36.

Procedure

Use the procedure for your operating system:

v AIX “Installing the upgrade utilities on AIX systems”
v HPUX “Installing the upgrade utilities on HP-UX systems” on page 289
v Linux “Installing the upgrade utilities on Linux systems” on page 290
v Solaris “Installing the upgrade utilities on Oracle Solaris systems” on page
291
v Windows “Installing the upgrade utilities on Microsoft Windows systems” on
page 293

Installing the upgrade utilities on AIX systems

AIX

You must install the upgrade utilities on the system that has the original server
and its database. The package to install is available for download from the FTP
downloads site.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The
5.5.x.x number must be the same as or later than the level of the V5
server that you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-AIX.tar.gz
The numbers at the beginning of the package name identify the release
level of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Ensure that the system has the following file sets installed:
xlC.rte 8.0.0.5, or later
gsksa.rte 7.0.4.11

Chapter 9. General procedures for upgrading a server to V7.1 287

Upgrading the server from V5 to V7.1

You can use the following commands to check for these file sets:
lslpp -L xlC.rte

lslpp -L gsksa.rte

If needed, you can obtain the gsksa.rte file set from any of the regular V5.5
maintenance packages for the AIX server. The maintenance packages are
available on the FTP downloads site: ftp://public.dhe.ibm.com/storage/tivoli-
storage-management/maintenance/server/v5r5/AIX/
4. Extract the contents of the upgrade utilities package. If you downloaded a
language package, also extract the contents of that package.
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Access the System Management Interface Tool (SMIT).
a. Enter smitty install_update
b. Select Install and Update Software > Install and Update from ALL
Available Software.
7. Select the INPUT device. Specify the directory location of the upgrade utilities
package on the system.
8. Select Software to Install. Press F4 or Esc+4 for the list of available file sets in
the directory.
9. Select the file sets for the upgrade utilities, the device driver, and optionally
the language package. The file set for the upgrade utilities is
tivoli.tsmupg.server. Optional language packages include messages for
languages other than US English.
10. Set COMMIT software updates to Yes. Press F4 or Esc+4.
11. Set SAVE replaced files to No.
12. Ensure that the default settings for the options in the window for all the
selected file sets show success.
13. Press Enter, and respond to the ARE YOU SURE? question by pressing Enter
again. The installation begins.
14. When the installation is complete, exit the SMIT program.
15. Optional: If you installed a language package, ensure that the locale
environment variable is set to use it. Enter the following command to set the
locale environment variable for messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
16. After the upgrade utilities are installed, continue at “Setting environment
variables for the upgrade utilities on AIX, HP-UX, Linux, and Oracle Solaris
systems” on page 292.

288 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Installing the upgrade utilities on HP-UX systems

HPUX

You must install the upgrade utilities on the system that has the original server
and its database. The package to install is available for download from the FTP
downloads site.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.gz
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
gzip -dc package_name.tar.gz | tar -xvf -
4. Navigate to the directory that corresponds to the processor architecture of the
operating system.
5. Install the upgrade utilities and the device driver. Use the source argument (-s)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
swinstall -s /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin.

6. Optional: Install the language package.
a. Extract the contents of the package.
gzip -d package_name.img.gz
b. Install the package. For example, if the directory is /tmp/TSM, issue the
command:
swinstall -s /tmp/TSM/package_name.img package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.

Chapter 9. General procedures for upgrading a server to V7.1 289

Upgrading the server from V5 to V7.1

v The upgrade utilities support the locale.

v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Setting environment
variables for the upgrade utilities on AIX, HP-UX, Linux, and Oracle Solaris
systems” on page 292.

Installing the upgrade utilities on Linux systems

Linux

You must install the upgrade utilities on the system that has the original server
and its database. The package to install is available for download from the FTP
downloads site.

About this task

Restriction: Do not install the utilities in the installation directory for the original
server that must be upgraded. Install the utilities package in its own directory.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Open the directory for your operating system and download the package.
The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.bz2
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the commands:
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
4. Navigate to the directory that corresponds to the processor architecture of the
operating system, for example, x86_64.
5. Install the upgrade utilities and the device driver. Use the following command:
rpm -ivh package_name.rpm
The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by
default.
6. Optional: Install the language package.
a. Extract the contents of the downloaded package.
bunzip2 package_name.tar.bz2
tar xvf package_name.tar
b. Install the package for the language that you want to use.

290 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

rpm -ivh package_name.rpm

c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
7. After the upgrade utilities are installed, continue at “Setting environment
variables for the upgrade utilities on AIX, HP-UX, Linux, and Oracle Solaris
systems” on page 292.

Installing the upgrade utilities on Oracle Solaris systems

Solaris

You must install the upgrade utilities on the system that has the original server
and its database. The package to install is available for download from the FTP
downloads site.

About this task

Restriction: Do not install the utilities in the installation directory of the server that
must be upgraded. Install the utilities package in its own directory.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the directory that names the operating system that your V5
server runs on. From that directory, open the 5.5.x.x directory. The 5.5.x.x
number must be the same as or later than the level of the V5 server that
you are upgrading.
c. Select the package that matches your operating system, and download it to
a convenient location on the server system. The name of the package has
the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.Z
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Change to the directory where the upgrade utilities package was downloaded.
4. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
uncompress -c package_name.tar.Z | tar -xvf -

Chapter 9. General procedures for upgrading a server to V7.1 291

Upgrading the server from V5 to V7.1

5. Navigate to the directory that corresponds to the processor architecture of the

operating system.
6. Install the upgrade utilities and the device driver. Use the source argument (-d)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
pkgadd -d . /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by

default.
7. Optional: Install the language package.
a. Extract the contents of the downloaded package.
uncompress package_name.pkg.Z
b. Install the package for the language that you want to use. Use the source
argument (-d) to specify the directory where the package was extracted. For
example, if the directory is /tmp/TSM, issue the command:
pkgadd -d /tmp/TSM package_name.pkg package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.
8. After the upgrade utilities are installed, continue at “Setting environment
variables for the upgrade utilities on AIX, HP-UX, Linux, and Oracle Solaris
systems.”

Setting environment variables for the upgrade utilities on AIX,

HP-UX, Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

After installing the upgrade utility package, you must set environment variables in
the shell from which you will run the utilities. An environment variable describes
the operating environment of a process, such as the home directory or terminal in
use.

About this task

The DSMSERV_DIR variable specifies the installed location of the upgrade utilities. By
default, the location is the following directory:

AIX

/usr/tivoli/tsm/upgrade/bin

HPUX Linux Solaris

/opt/tivoli/tsm/upgrade/bin

292 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Procedure

Use the appropriate command for your system to set the environment variable for
running the utilities. If the shell is in the ksh or bash family, enter the following
command to set the DSMSERV_DIR variable:
export DSMSERV_DIR=upgrade_utilities_directory

If your shell is in the csh family, use the following command:

setenv DSMSERV_DIR upgrade_utilities_directory

where upgrade_utilities_directory is the directory where the upgrade utilities are

installed.

What to do next

After you set the environment variable, continue at “Preparing the database of a
V5 server for upgrade” on page 294.

Installing the upgrade utilities on Microsoft Windows systems

Windows

You must install the upgrade utilities on the system that has the original server
and its database. The package to install is available for download from the FTP
downloads site.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/WIN
b. Open the 5.5.x.x directory. The 5.5.x.x number must be the same as or
later than the level of the V5 server that you are upgrading.
c. Select the package and download it to a convenient location on the server
system. The name of the package has the following form:
5.5.x.x-TIV-TSMUPG-Windows.exe
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, install the
language package that your installation requires.
2. Log on with an administrator ID.
3. Run the executable package for the upgrade utilities.
The default location for the installation of the utilities is based on the location
where the V5 server was last installed. For example, if the V5 server was
installed using the default path, C:\Program Files\Tivoli\TSM\server, the
upgrade utilities are installed in C:\Program Files\Tivoli\TSM\upgrade.

Restriction: Do not install the utilities in the same directory as the original
server that must be upgraded. Install the utilities package in its own directory.

What to do next

After the upgrade utilities are installed, continue at “Preparing the database of a
V5 server for upgrade” on page 294.

Chapter 9. General procedures for upgrading a server to V7.1 293

Upgrading the server from V5 to V7.1

Tip: When you use the upgrade utilities, if you have multiple servers running on
the system, you must use the -k option to specify the name of the Windows
registry key from which to retrieve information about the server being upgraded.
The default value for the option is SERVER1.

If you are upgrading the server on the same system as the earlier version, and
using the network method to extract and insert the data into the V7.1 database, use
the -o option with the DSMUPGRD command to specify the location of the server
options file.

Preparing the database of a V5 server for upgrade

Before you extract the data from the database, you must prepare the server
database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a
single system, you must repeat this task for each server.

Before you begin

The upgrade utilities must be installed on the system where the database is
located.

About this task

Important: After you prepare a V5.3 or V5.4 database by using the DSMUPGRD
PREPAREDB utility, the version of the server database is V5.5. You can no longer use
that database to run with a V5.3 or V5.4 server program. After you upgrade the
server to V7.1, if you decide to revert to the earlier version, you must reinstall the
earlier version of the server code. Then, you must restore the backed-up server
database that matches that version.

Procedure
1. Ensure that you have completed all preparation steps.
2. Log in using the root user ID on the system that has the original server. Log on
with the administrator ID on a Windows system.
3. Change to the instance directory for the server that you are upgrading. The
instance directory is the directory that contains the files such as dsmserv.dsk for
the server.

Important: The dsmserv.dsk file is not available in Tivoli Storage Manager

V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.
4. Prepare the database. Direct the output of the process to a file for monitoring.
AIX
From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

HPUX Linux Solaris

From the instance directory for the server that you are upgrading, issue
the following command to run the process in the background and
direct the output to the file called prepare.out:
nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

294 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Windows
From the instance directory for the server that you are upgrading, issue
the following command to run the process and direct the output to the
file called prepare.out:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd"
preparedb 1>>prepare.out 2>&1

If multiple servers exist on the system, issue the command from the
instance directory for the server that you want to prepare. Specify the
registry key for that server. For example, if the server is SERVER2:
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" -k server2
preparedb 1>>prepare.out 2>&1
5. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation. From the instance directory for the
server that you are upgrading, issue the following command to monitor the
process:
tail -f prepare.out

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
6. Ensure that the prepare operation is completed successfully before you continue
to the next step. If the prepare operation fails, you might need to restart the V5
server to fix the problem and run the prepare operation again. If the server that
is being upgraded is a V5.3 or V5.4 server, you might need to restore the
database by using a backup before you can restart the server to correct the
problem.
Related reference:
“DSMUPGRD PREPAREDB (Prepare a V5 database for upgrade)” on page 523

Uninstalling the V5 program before installing V7.1

For best results when you are upgrading the server to V7.1 on the same system
where the V5 server is located, uninstall the V5 server program. Then, install the
V7.1 server program.

Uninstalling the V5 program on AIX systems

AIX

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
v For a V5.4 or V5.5 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license.aix5.rte64
/usr/sbin/installp -ug tivoli.tsm.devices.aix5.rte
/usr/sbin/installp -ug tivoli.tsm.server.aix5.rte64
v For a V5.3 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license
/usr/sbin/installp -ug tivoli.tsm.devices
/usr/sbin/installp -ug tivoli.tsm.server

Chapter 9. General procedures for upgrading a server to V7.1 295

Upgrading the server from V5 to V7.1

What to do next

After the V5 server program is uninstalled, continue at “Installing the V7.1 server”
on page 297.

Uninstalling the V5 program on HP-UX systems

HPUX

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
v For a V5.4 or V5.5 server, issue the following commands:
swremove TIVsmS64IA.server
swremove TIVsmS64IA.license
swremove TIVsmDD64_IA11_23.tsmscsi
v For a V5.3 server, issue the following commands:
swremove TIVsmS64.server
swremove TIVsmS64.license
swremove TIVsmDD64_HP11_11.tsmscsi

What to do next

After the V5 server program is uninstalled, continue at “Installing the V7.1 server”
on page 297.

Uninstalling the V5 program on Linux systems

Linux

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure
1. To determine the Tivoli Storage Manager packages that are installed, issue the
following command:
rpm -qa | grep TIVsm
2. Remove the server, server license, and device driver packages. Issue the
following commands:
rpm -e TIVsm-server
rpm -e TIVsm-license
rpm -e TIVsm-tsmscsi

What to do next

After the V5 server program is uninstalled, continue at “Installing the V7.1 server”
on page 297.

296 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Uninstalling the V5 program on Oracle Solaris systems

Solaris

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

Procedure

Issue the following commands:

/usr/sbin/pkgrm TIVsmS
/usr/sbin/pkgrm TIVsmSlic
/usr/sbin/pkgrm TIVsmSdev

What to do next

After the V5 server program is uninstalled, continue at “Installing the V7.1 server.”

Uninstalling the V5 program on Microsoft Windows systems

Windows

Uninstall the V5 server, server license, and device driver, if available. Do not
remove the database, recovery log, or any other related files or directories, such as
the server options file.

About this task

Do not remove registry entries for the server.

Procedure
1. Click Start > Control Panel > Add or Remove Programs.
2. Select the Tivoli Storage Manager server component, and click Remove. Repeat
for the license and the device driver.
If you see any messages that suggest that you restart the system, ignore them
until the selected Tivoli Storage Manager components are removed.

What to do next
After the V5 server program is uninstalled, continue at “Installing the V7.1 server.”

Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

If you are installing the V7.1 server on the same system as the V5 server, take the
following actions:
v Ensure that you have completed all upgrade preparation steps, including the
database backup. The server that you are upgrading will not be available until
after the installation and upgrade steps are completed.

Chapter 9. General procedures for upgrading a server to V7.1 297

Upgrading the server from V5 to V7.1

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

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

AIX HPUX If you plan to download the files, set the

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

About this task

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

Tip: The database (DB2) and the Global Security Kit are automatically installed
when you select the Tivoli Storage Manager server component.
For more information about storage agents, see the Storage Agent User's Guide.

Procedure
1. Log on to the system.
AIX HPUX Linux Solaris Log in by using the root user ID.
Log on as an administrator. You must be logged on to the system
Windows
with the administrative user ID that was used to install the V5 server.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:

298 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

AIX HPUX Linux Solaris

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

AIX

7.1.0.000-TIV-TSMSRV-AIX.bin

HPUX

7.1.0.000-TIV-TSMSRV-HP-UX.bin

Linux

7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin
7.1.0.000-TIV-TSMSRV-Linuxs390x.bin

Solaris

7.1.0.000-TIV-TSMSRV-SolarisSPARC.bin

In the examples, 7.1.0.000 represents the product release level.

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

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

Windows

a. Verify that you have enough space to store the installation files
when they are extracted from the product package. For space
requirements, see the download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035121
v Tivoli Storage Manager Extended Edition: http://
www.ibm.com/support/docview.wss?uid=swg24035636
v System Storage Archive Manager: http://www.ibm.com/
support/docview.wss?uid=swg24035638

Chapter 9. General procedures for upgrading a server to V7.1 299

Upgrading the server from V5 to V7.1

b. Change to the directory where you placed the executable file.

In the next step, the files are extracted to the current directory. The
path must contain no more than 128 characters. Ensure that you
extract the installation files to an empty directory. Do not extract to
a directory that contains previously extracted files, or any other
files.
c. To extract the installation files, double-click the executable file:
package_name.exe
where package_name is like this example:
7.1.0.000-TIV-TSMSRV-Windows.exe
The package is large. Therefore, the extraction takes some time.
4. AIX HPUX To ensure that the Tivoli Storage Manager
Solaris
wizards work correctly, verify that the following command is enabled:
AIX lsuser
HPUX Solaris logins
By default, the command is enabled.
5. If you plan to install the server by using the graphical wizard of IBM
Installation Manager, review the following information and verify that your
system meets the requirements:
v AIX Verify that all required RPM files are installed. For a list of
required RPM files and instructions about installing RPM files, see the
section about installing Tivoli Storage Manager by using the installation
wizard in the Installation Guide.
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the
installation wizard.
v Windows The user ID that you use during installation must be a user with
local Administrator authority.
v Solaris Ensure that the LD_LIBRARY_PATH_64 environment variable is not
set.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
AIX HPUX Linux Solaris

./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

Windows

install.bat -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"

6. If you use the installation wizard, complete the following steps to begin the
installation:

300 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Option Description
Installing from a downloaded package file: 1. Change to the directory where you
downloaded the package file.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat

Installing from DVD media: 1. Insert the DVD into the DVD drive.
Tip: Ensure that the installation files are
visible on the DVD drive.
2. Start the installation wizard by issuing
the following command:
AIX HPUX Linux

Solaris

./install.sh

Windows

install.bat
Windows Or, in the directory where the
installation files were extracted,
double-click the install.bat file.

7. If you are installing the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
8. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
9. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
10. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
11. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.

Chapter 9. General procedures for upgrading a server to V7.1 301

Upgrading the server from V5 to V7.1

12. HPUX Linux Solaris To prevent server failures during interaction

with DB2, tune the kernel parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
13. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
14. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.

Windows
What to do next

If a native device driver is available on Windows for the tape drives or medium
changers that you plan to use, use the native device driver. If a native device
driver is not available on Windows for the tape drives or medium changers that
you plan to use, install the Tivoli Storage Manager device driver by issuing the
dpinst.exe /a command. The dpinst.exe file is in the device driver directory. The
default directory is C:\Program Files\Tivoli\TSM\device\drivers.
Related concepts:
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555

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

Before you begin

Review the information about planning space for the server before you complete
this task. See “Worksheet for planning space for the V7.1 server” on page 42.

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

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

Restriction: In the user ID, only lowercase letters (a-z), numerals

(0-9), and the underscore character (_) can be used. The user ID and
group name must comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a
numeral.
v The user ID and group name cannot be user, admin, guest, public,
local, or any SQL reserved word.

302 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

For example, create user ID tsminst1 in group tsmsrvrs. The

following examples show how to create this user ID and group by
using operating system commands:
AIX

# mkgroup id=1001 tsmsrvrs

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

HPUX

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

Linux

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

Solaris

# groupadd tsmsrvrs
# useradd -d /export/home/tsminst1 -m -g tsmsrvrs
-s /bin/ksh tsminst1
# passwd tsminst1
b. Log out and then log in to your system by using the new user ID
and password. Use an interactive login program, such as telnet, so
that you are prompted for the password and can change it if
necessary.
c. If a configuration profile does not exist for the user ID, create the
file. For example, create a .profile file if you are using the Korn
shell (ksh).
Windows
Identify the user account that will own the Tivoli Storage Manager
server instance. When the server is started as a Windows service, this is
the account that the service will log on to. The user account must have
administrative authority on the system. One user account can own
more than one server instance.
You can create a user account, or use an existing account.
If you have multiple servers on one system and want to run each
server with a different user account, create a user account in this step.
a. Create the user ID.

Restriction: The user ID can contain only lowercase letters (a-z),

numerals (0-9), and the underscore character (_). The user ID must
be 30 characters or less, and cannot start with ibm, sql, sys, or a
numeral. The user ID and group name cannot be user, admin, guest,
public, local, or any SQL reserved word.
Use the following command to create the user ID:
net user user_ID * /add

You are prompted to create and verify a password for the new user
ID.

Chapter 9. General procedures for upgrading a server to V7.1 303

Upgrading the server from V5 to V7.1

b. Issue the following operating system commands to add the new

user ID to the Administrators groups:
net localgroup Administrators user_ID /add
net localgroup DB2ADMNS user_ID /add
c. Log in to your system, by using the new user ID and password.
d. For all directories that were created for the server instance, ensure
that the user ID for the server instance has read/write access. The
directories to check include the instance directory and all database
and log directories.
2. Create the directories that the server requires. Ensure that you are logged in
under the new user ID that you created.
You need a unique, empty directory for each item in the following table. Create
the database directories, the active log directory, and the archive log directory
on different physical volumes. For space requirements, see “Worksheet for
planning space for the V7.1 server” on page 42.
AIX HPUX Linux Solaris

Table 58. Worksheet for creating required directories

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

Windows

Table 59. Worksheet for creating required directories

Example commands for
Item creating the directories Your directories
The instance directory for mkdir d:\tsm\server1
the server, which will
contain files for this
server instance, including
the server options file

304 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Table 59. Worksheet for creating required directories (continued)

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

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
3. Create additional logical volumes and mount the volumes on the directories
that were created in the previous step.

What to do next

Continue the upgrade process by using one of the following topics:

“Upgrading the server by using the upgrade wizard”
“Upgrading the server manually by using utilities” on page 307
Related tasks:
“Planning space for the upgrade process and the upgraded server” on page 37
Related reference:
“Server naming best practices” on page 70

Upgrading the server by using the upgrade wizard

The wizard offers a guided approach to upgrading a server. By using the wizard,
you can avoid some configuration steps that are complex when done manually.
Start the wizard on the system where you installed the V7.1 server program.

Before you begin

You must complete all preceding steps to prepare for the upgrade, to install the
upgrade utilities, to install the V7.1 server program, and to create the directories
and user ID for the server instance.

Procedure
1. Ensure that the following requirements are met:
AIX HPUX Linux Solaris

Chapter 9. General procedures for upgrading a server to V7.1 305

Upgrading the server from V5 to V7.1

v The system where you installed the V7.1 server program must have
the X Window client. You must also be running an X Window server
on your desktop.
v The system must have one of the following protocols enabled. Ensure
that the port that the protocol uses is not blocked by a firewall.
– Secure Shell (SSH). Ensure that the port is set to the default value,
22. Also, ensure that the SSH daemon service has access rights for
connecting to the system by using localhost.
– Remote shell (rsh).
– Remote Execution Protocol (REXEC).
If the V5 server is on a different system than the V7.1 server, that
system must also have one of the protocols enabled.
v You must be able to log in to the V7.1 system with the user ID that
you created for the server instance, by using the SSH, rsh, or REXEC
protocol. When you use the wizard, you must provide this user ID
and password to access that system.
Windows

v The system where you installed the V7.1 server program must have
the Windows server message block (SMB) protocol enabled. SMB is
the interface that is used by File and Print Sharing (also known as
CIFS). To use the SMB protocol, you must ensure that File and Print
Sharing is enabled, and that port 445 is not blocked by your firewall.
v If the V5 server is on a different system than the V7.1 server, that
system must also have SMB enabled.
v You must be able to log on to the system that has SMB enabled by
using either the user ID that you created for the server instance, or
another user ID that exists on the system. When you use the wizard,
you must provide the user ID and password to access the system.
2. Windows If the system is running on Windows Server 2008, complete the
following steps to disable User Account Control:
a. Ensure that the Remote Registry in Windows Services is started, and ports
445, 137, and 139 are unblocked in the firewall.
b. Configure both the framework server and the targets as members of a
Windows domain. Use a user account in that domain, or in a trusted
domain, when you connect to the target.
c. Connect to the target workstation by enabling and using the built-in
administrator account. To enable the built-in administrator account, click
Control Panel > Administrative Tools > Local Security Policy > Security
Settings > Local Policies > Security Options. Double-click the Accounts:
Administrator account status section. Select Enable and click OK.
d. Click Control Panel > Administrative Tools > Local Security Policy >
Security Settings > Local Policies > Security Options. Double-click the
User Account Control: Run all administrators in Admin Approval Mode
section. Select Disable and click OK.
3. Start the upgrade wizard, dsmupgdx, from the V7.1 server installation directory.
AIX HPUX Linux Solaris
Log in using the root user ID. Issue the command:
/opt/tivoli/tsm/server/bin/dsmupgdx

Windows
Open a new Command Prompt window, and issue the command:
306 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

"c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe"
4. Follow the instructions to complete the upgrade. The upgrade wizard can be
stopped and restarted, but the server will not be operational until the entire
upgrade process is complete.

Important: Read all messages that appear for each phase of the upgrade
process, in the message display area within the wizard. Informational messages
might show actions that occurred during the process that are important to you.

What to do next

To complete the upgrade, perform the steps described in Chapter 10, “Taking the
first steps after upgrade,” on page 323.
Related tasks:
“Upgrading the server manually by using utilities”

Upgrading the server manually by using utilities

Use the utilities to upgrade the server by using a command interface.

Before you begin

Complete all preceding steps to prepare for the upgrade. Ensure that you have
installed the upgrade utilities, installed the V7.1 server program, and created the
directories and user ID for the server instance.

Procedure

Complete the following steps:

1. “Creating and formatting the new database” on page 308
2. Use one of the following methods to move the database:
v “Moving the server database using media” on page 312
v “Moving the server database over a network” on page 316
3. “Creating a Windows service for the server instance” on page 318
4. “Configuring the system for database backup” on page 318

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.
Related concepts:
“DSMUPGRD upgrade utilities” on page 16

Chapter 9. General procedures for upgrading a server to V7.1 307

Upgrading the server from V5 to V7.1

Creating and formatting the new database

Create the server instance and format files for an empty V7.1 database.

Procedure
1. Log on to the system where you installed the V7.1 program.
AIX HPUX Linux Solaris
Log in by using the root user ID. Verify the following items:
v The home directory for the user, /home/tsminst1, exists. If there is
no home directory, you must create it.
The instance directory stores the following core files that are
generated by the Tivoli Storage Manager server:
– The server options file, dsmserv.opt
– The server key database file, cert.kdb, and the .arm files, which
are used by clients and other servers to import the Secure
Sockets Layer certificates of the server
– Device configuration file, if the DEVCONFIG server option does not
specify a fully qualified name
– Volume history file, if the VOLUMEHISTORY server option does not
specify a fully qualified name
– Volumes for DEVTYPE=FILE storage pools, if the directory for
the device class is not fully specified, or not fully qualified
– User exits
– Trace output, if it is not fully qualified
v A shell configuration file, for example, .profile, exists in the home
directory. The root user and instance user ID must have write
permission to this file. For more information, go to the DB2
Information Center (http://pic.dhe.ibm.com/infocenter/db2luw/
v10r5), and search for information about Linux and UNIX
environment variable settings.
Windows
Log on as an administrator.
2. Create a Tivoli Storage Manager instance by using the db2icrt command.
AIX HPUX Linux Solaris
Enter the following command on one line. For the instance name,
specify the user ID that you created to own the instance:
AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

instance_name instance_name

For example, if the user ID for this instance is tsminst1, use the
following command to create the instance:

AIX HPUX Linux Solaris

/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u

tsminst1 tsminst1

Remember: From this point on, use this new user ID when you
configure the Tivoli Storage Manager server. Log out of the root user
ID, and log in using the user ID that is the instance owner.

308 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Windows
Enter the following command on one line. The user account that you
specify becomes the user ID that owns the V7.1 server; this ID is the
instance user ID.
db2icrt -s ese -u user_account instance_name

For example, if the user account is tsminst1 and the server instance is
Server1, enter the following command:
db2icrt -s ese -u tsminst1 server1

The database service for the server instance logs on to the user
account that is specified in this command.

Use the registry key name of the V5 server as the instance name for
the V7.1 server. You are prompted to enter the password for the user
account.
The instance name that you specify on this db2icrt command is the
name that you later specify with the -k option on the DSMSERV
LOADFORMAT command, when you create and format the database and
recovery log.
3. Log on to the system by using the user ID that owns the V7.1 server instance
(the instance user ID).
4. Copy the configuration files to the instance directory that you created for the
new server. The files are the configuration files that you saved from the
original V5 server:
v Device configuration
v Server options file, which is typically named dsmserv.opt
For example, if you created the instance directory that is shown in the
example in the step to create directories for the V7.1 server, copy the files into
the following directory:
AIX HPUX Linux Solaris /tsminst1
Windows d:\tsm\server1
Ensure that the user ID that owns the V7.1 server (the instance user ID) has
ownership or read/write permission to the files that you copied.
5. Edit the server options file.
a. Remove any options that are not supported for V7.1. For the list of deleted
options, see Table 29 on page 67.
b. Verify that the server options file contains at least one VOLUMEHISTORY
option and at least one DEVCONFIG option. By specifying these options, you
ensure that a volume history file and a device configuration file are
generated and updated automatically. If you must restore the database,
these files are required.
c. Check whether the server options file includes the TXNGROUPMAX option
with a value, and if it does, what the value is. You might want to change
the current value because the default value for this option changed from
256 to 4096, starting in V6. The increased value can improve the
performance for data movement operations such as storage pool migration
and storage pool backup.
v If the server options file does not include this option, the server
automatically uses the new default value of 4096.

Chapter 9. General procedures for upgrading a server to V7.1 309

Upgrading the server from V5 to V7.1

v If the server options file includes a value for this option, the server uses
that specified value. If the specified value is less than 4096, consider
increasing the value, or removing the option so that the new default
value is applied.
6. Change the default path for the database.
AIX HPUX Linux Solaris
Change the default path for the database to be the same as the
instance directory for the server. Issue the command:
db2 update dbm cfg using dftdbpath instance_directory

For example:
db2 update dbm cfg using dftdbpath /tsminst1

Windows
Change the default path for the database to be the drive where the
instance directory for the server is located. Complete the following
steps:
a. Click Start > Programs > IBM DB2 > DB2TSM1 > Command
Line Tools > Command Line Processor.
b. Enter quit to exit the command line processor.
A window with a command prompt opens, with the environment
correctly set up to successfully issue the commands in the next
steps.
c. From the command prompt in that window, issue the following
command to set the environment variable for the server instance
that you are working with:
set db2instance=instance_name

The instance_name is the same as the instance name that you

specified when you issued the db2icrt command. For example, to
set the environment variable for the Server1 server instance, issue
the following command:
set db2instance=server1
d. Issue the command to set the default drive:
db2 update dbm cfg using dftdbpath instance_location

For example, if the instance directory is d:\tsm\server1, the

instance location is drive d:. Enter the command:
db2 update dbm cfg using dftdbpath d:
7. Modify the library path to use the version of the IBM Global Security Kit
(GSKit) that is installed with the Tivoli Storage Manager server:
AIX Issue the following command:
export LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
AIX HPUX Linux Solaris You must update the following files
to set the library path when DB2 or the Tivoli Storage Manager server is
started:
v instance_directory/sqllib/usercshrc
v instance_directory/sqllib/userprofile
For the instance_directory/sqllib/usercshrc file, add the following lines:
v AIX

310 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

setenv LIBPATH /usr/opt/ibm/gsk8_64/lib64:$LIBPATH

v HPUX Solaris

setenv LD_LIBRARY_PATH /opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

v Linux

setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

For the instance_directory/sqllib/userprofile file, add the following lines:
v AIX

LIBPATH=/usr/opt/ibm/gsk8_64/lib64:$LIBPATH
export LIBPATH
v HPUX Solaris

LD_LIBRARY_PATH=/opt/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
v Linux

LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Verify the library path settings and ensure that the GSKit version is 8.0.14.14
or later. Issue the following commands:
v AIX

echo $LIBPATH
gsk8capicmd_64 -version
gsk8ver_64
v HPUX Linux Solaris

echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64
If the GSKit version is not 8.0.14.14 or later, you must reinstall the Tivoli
Storage Manager server. The reinstallation ensures that the correct GSKit
version is available.
8. Change to the instance directory that you created for the server.
9. Create and format the database and recovery logs. In the command, specify
the directories that you created for the database and logs. The directories must
be empty.
AIX HPUX Linux Solaris

For example, to get an active log size of 16 GB (16384 MB, the default
size), issue the following command, on one line:
/opt/tivoli/tsm/server/bin/dsmserv loadformat \
dbdir=/tsmdb001,/tsmdb002,/tsmdb003,/tsmdb004 \
activelogsize=16384 activelogdirectory=/tsmlog \
mirrorlogdirectory=/tsmlogmirror archlogdirectory=/tsmarchlog

Windows

For example, to get an active log size of 16 GB (16384 MB, the default
size) for the Server1 server instance, issue the following command, on
one line:
"c:\Program Files\Tivoli\TSM\server\dsmserv" loadformat
dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog

Chapter 9. General procedures for upgrading a server to V7.1 311

Upgrading the server from V5 to V7.1

If the server that you are upgrading is not Server1, you must use the
-k option. The -k option specifies the instance name for running this
utility. For example, if the system has more than one server instance
and the instance that you are upgrading is Server2, issue the
command:
"c:\Program Files\Tivoli\TSM\server\dsmserv" -k server2
loadformat dbdir=d:\tsm\db001,e:\tsm\db002,f:\tsm\db003,g:\tsm\db004
activelogsize=16384 activelogdirectory=h:\tsm\log
mirrorlogdirectory=j:\tsm\logmirror archlogdirectory=i:\tsm\archlog

Important: The server instance that you specify must have already
been through all preceding steps for the upgrade process, including
the creation of the database instance (db2icrt command).
10. Monitor the process for errors and warning messages. The final message
indicates success or failure of the operation.

What to do next

Continue the upgrade process by following the instructions in one of the following
topics:
“Moving the server database using media”
“Moving the server database over a network” on page 316
Related tasks:
“Estimating total space requirements for the upgrade process and upgraded
server” on page 39
Related reference:
DSMSERV LOADFORMAT (Format a database)
“Deleted server commands, utilities, and options” on page 65

Moving the server database using media

Use media to move the server database if the V7.1 server is installed on a different
system and no network connection is available. Also, use the media method if the
server system does not have enough space for both databases, or if you want to
test the upgrade process and set up a test server.

About this task

The process creates a manifest file during the data extraction, which contains
information about the media that is used to store the data. The process requires the
manifest file for loading the data into the new database.

Procedure
1. “Extracting the data to media” on page 313
2. “Loading the extracted data into the new database” on page 314
Related concepts:
“The manifest file for the data extraction to media” on page 531

312 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Extracting the data to media

You can extract the data from the original server database to sequential media. The
sequential media can be tape, or disk space that is defined with the FILE device
class.

Procedure
1. Log in using the root user ID on the system that has the original server. Log on
with the administrator ID on a Windows system.
2. Ensure that the device that you want to use to store the extracted data is
available. The server database and the device configuration file must contain a
valid device class definition for the device.
3. From the instance directory for the server that you are upgrading, issue the
command to start the extraction. Direct the output of the process to a file for
monitoring. For example, issue the following command on one line:
AIX

nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

devclass=file manifest=./manifest.txt >extract.out 2>&1 &

HPUX Linux Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

devclass=file manifest=./manifest.txt >extract.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" extractdb

devclass=file manifest=.\manifest.txt 1>>extract.out 2>&1

Tip: Messages that are issued during the extract operation are not saved in the
server activity log. Direct the output of the utility to a file, as shown in the
examples, to record the messages.
4. Monitor the process for errors and warning messages, and for items that you
might need to take action on. A message near the end of the process output
indicates success or failure of the operation:
Success message: ANR1382I EXTRACTDB: Process 1, database extract, has
completed.
Failure message: ANR1396E EXTRACTDB: Process 1, database extract, has
completed with errors.
For example, from the instance directory for the server that you are upgrading,
issue the following command to monitor the process:
tail -f extract.out
The length of time that the process runs depends on the size of the database.
The time will be approximately as much as the time required for a full backup
of the database.

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
Related concepts:
“The manifest file for the data extraction to media” on page 531
Related tasks:
“Preparing space for the upgrade process” on page 281

Chapter 9. General procedures for upgrading a server to V7.1 313

Upgrading the server from V5 to V7.1

Related reference:
“DSMUPGRD EXTRACTDB (Extract data from a V5 server database)” on page 529

Loading the extracted data into the new database

After you format an empty database by using the DSMSERV LOADFORMAT utility, load
the data that you extracted from the original server database.

Before you begin

Ensure that the following requirements are met before you begin to load the data:
v The manifest file from the DSMUPGRD EXTRACTDB operation must be available.
v The server options file must contain an entry for the device configuration file.
v The device configuration file must have information about the device class that
is specified in the manifest file.
v The media that contains the extracted database must be available to the V7.1
server. The device must be physically attached to the system. The permissions
must be set to grant access to the media for the user ID that owns the V7.1
server instance.

Procedure

Complete the following steps:

1. Verify that the V7.1 server can access the extracted data.
v If the extracted data is on tape, the tape drive must be physically attached
to the system.
v If the extracted data was stored by using a FILE or DISK device class,
complete the following steps:
a. Log on to the system by using the root user ID.
b. Ensure that the user ID that owns the V7.1 server (the instance user ID)
has ownership or read/write permission for the extracted files.
2. Ensure that the instance user ID has ownership or read/write permission for
the manifest file that was created by the extraction process.
3. Log on with the instance user ID on the system where you installed the V7.1
server.
4. If the V7.1 server is on a different system than the original server, copy the
manifest file that was created by the extraction process to the V7.1 system.
5. On the V7.1 server, complete the following steps:
a. Verify that the server options file from the V5 server includes the
DEVCONFIG option, and that the option specifies the full path of the device
configuration file.
b. Verify that the device configuration file from the V5 server is available in
the location that is specified by the DEVCONFIG option.
c. Verify that the permissions on the device configuration file allow read
access for the instance user ID.
6. Verify that the contents of the device configuration file are correct. The device
class that was used for the extraction step is recorded in the manifest file, and
that device class must exist and be valid on the V7.1 system.
a. Verify entries for FILE device classes. For example, paths might be
different on the system.

314 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

b. Verify entries for tape and other devices. For example, the device names
might have changed.
7. Verify the contents of the manifest file and edit the file if necessary:
a. Ensure that the device names in the manifest file are valid for the V7.1
system. Device names for the same device might be different on V5 and
V7 systems.
b. Ensure that the manifest file contains a list of volumes to be used when
the extracted data is loaded into the new database. For example, if the
manifest file contains a list of volumes that belong to a FILE device class,
ensure that the fully qualified path to the volumes is correct for the
system.
8. Issue the DSMSERV INSERTDB command to load an extracted server database
into the prepared, empty V7.1 database. Direct the output of the process to a
file for monitoring. For example, enter the following command on one line:
AIX HPUX Linux Solaris

nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \

manifest=./manifest.txt >insert.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\server\dsmserv" insertdb \

manifest=.\manifest.txt 1>>insert.out 2>&1
9. Monitor the process for error messages, warning messages, and any items that
you might need to address. The system displays interim statistics about the
process of loading the database. However, there might be time periods when
no messages are issued. During this time, DB2 operations are running in the
background. The length of time that the process runs depends on the size of
the database. For more information, see “Example: Estimating the upgrade
time based on the database size” on page 43.
Optional: Verify that the database is being loaded by monitoring the processor
and I/O usage for the server process and the corresponding DB2 process. For
example, issue the following command to monitor the process:
tail -f insert.out

Tip: Windows On Windows systems, use the tail command or an equivalent

utility with which you can monitor the contents of a file as it changes. For
example, the Windows Server 2003 Resource Kit Tools includes the tail
command, which can be used as shown in the preceding example.
A message in the output of the DSMSERV INSERTDB command indicates the
status of the operation:
Success message: ANR1395I INSERTDB: Process 1, database insert, has
completed.
Failure message: ANR1396E INSERTDB: Process 1, database insert, has
completed with errors.
10. If you used the media method to upgrade the system and used a tape device,
after the data is loaded into the database, remove or check out from the
library the tape that holds the extracted data. Prevent the tape from being
reused until you are sure that you do not need to run the database-loading
operation again.

Chapter 9. General procedures for upgrading a server to V7.1 315

Upgrading the server from V5 to V7.1

What to do next

Continue the upgrade process by completing the steps in “Creating a Windows

service for the server instance” on page 318.
Related concepts:
“The manifest file for the data extraction to media” on page 531
Related reference:
“DSMSERV INSERTDB (Move a server database into an empty database)” on page
538

Moving the server database over a network

Move the database by starting the insertion process for the V7.1 server to accept
the server database. Then, start the extraction process for the V5 server to extract
and send the database.

Before you begin

Ensure that the V5 server and the V7.1 server are not running.

Procedure
1. Verify that there is a good network connection between the two systems.
2. On the V7.1 server, complete the following steps:
a. Verify that the server options file from the V5 server includes the DEVCONFIG
option, and that the option specifies the full path of the device
configuration file.
b. Verify that the device configuration file from the V5 server is available in
the location that is specified by the DEVCONFIG option.
c. Verify that the permissions on the device configuration file allow read
access for the instance user ID.
3. Start the insertion process on the V7.1 server to accept the database. To monitor
the process, direct the output of the process to a file. For example, start the
server, allowing 60 minutes (the default time) for the other server to contact the
V7.1 server and directing the process output to insert.out, by using this
command:
AIX HPUX Linux Solaris

nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \

sesswait=60 >insert.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\server\dsmserv" insertdb

sesswait=60 1>>insert.out 2>&1

The server starts and waits up to 60 minutes to be contacted by the original

server. Some time might pass during which no messages are issued. During
this time, DB2 operations are running in the background. Optional: To verify
that operations are continuing as expected, monitor the CPU and I/O usage for
the server process and the corresponding DB2 process.
4. Monitor the output of the DSMSERV INSERTDB process. Verify that the DSMSERV
INSERTDB process has issued the following message before continuing to the
next step:
ANR1336I INSERTDB: Ready for connections from the source server

316 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Issue the following command to monitor the process output in the insert.out
file:
tail -f insert.out

Tip: On Windows systems, use the tail command or an equivalent utility with
which you can monitor the contents of a file as it changes. For example, the
Windows Server 2003 Resource Kit Tools includes the tail command, which
can be used as shown in the preceding example.
5. Start the extraction from the original server. Specify the TCP/IP address and
port for the V7.1 server. Direct the output of the process to a file for
monitoring. For example, enter the following command on one line:
AIX

nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 &

HPUX Linux Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 &

Windows

"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" extractdb hladdress=127.0.0.1

lladdress=1500 1>>extract.out 2>&1
6. Monitor the processes for errors and warning messages, and for items that you
might need to act on. From the instance directory for the server that you are
upgrading, issue the following command to monitor the extraction process:
tail -f extract.out

The length of time that the process runs depends on the size of the database,
the hardware being used, and the network.
7. Examine the process outputs for the extraction and insertion processes to find
the messages that indicate the success or failure of the operations.

Process Success message Failure message

Extraction ANR1382I EXTRACTDB: Process 1, ANR1396E EXTRACTDB: Process 1,
database extract, has database extract, has completed
completed. with errors.
Insertion ANR1395I INSERTDB: Process 1, ANR1396E INSERTDB: Process 1,
database insert, has completed. database insert, has completed
with errors.

Related reference:
“DSMUPGRD EXTRACTDB (Extract data from a V5 server database)” on page 529

“DSMSERV INSERTDB (Move a server database into an empty database)” on page

538

Chapter 9. General procedures for upgrading a server to V7.1 317

Upgrading the server from V5 to V7.1

Creating a Windows service for the server instance

Windows

A Windows service is created for the Tivoli Storage Manager V7.1 server
automatically if you use the upgrade wizard (dsmupgdx). If you do not use the
wizard, you must create the Windows service for the Tivoli Storage Manager
server manually.

Procedure
1. Change to the installation directory for the server program. By default, the
directory is C:\Program Files\Tivoli\TSM\console. If you installed the server
in a different directory, change to the console subdirectory of the server
installation directory.
2. Install the Windows service by using the Tivoli Storage Manager server
instance name and password in the service name. Issue the following
command:
install "TSM server_instance_name"
"C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
instance_owner instance_owner_password

where:
"TSM server_instance_name" is the name of the service that is being
installed.
server_instance_name is the instance name that was specified when you
issued the db2icrt command.
instance_owner is the instance owner account; this account will own the
service.
instance_owner_password is the password for the instance owner account.
Example
To install the Windows service for the server1 server instance, enter the
following command on one line. The example uses rudy as the instance
owner and s21ret as the password for the instance owner account.
install "TSM server1" "C:\Program Files\Tivoli\TSM\server\dsmsvc.exe"
rudy s21ret
3. Optional: Manually change the service to an automatic startup type by using
Windows administrative tools (Administrative Tools > Services).
Related tasks:
“Starting the server on Windows systems” on page 331

Configuring the system for database backup

The database manager and the Tivoli Storage Manager API must be configured so
that the database manager can back up the server database. The configuration is
completed for you automatically if you use the upgrade wizard (dsmupgdx). If you
do not use the wizard, you must complete the configuration manually.

Procedure
v “Configuring the system for database backup on AIX, HP-UX, Linux, and Oracle
Solaris systems” on page 319
v “Configuring the system for database backup on Microsoft Windows systems”
on page 321

318 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Configuring the system for database backup on AIX, HP-UX,

Linux, and Oracle Solaris systems
AIX HPUX Linux Solaris

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

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

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, replace the example values with your actual values.
The examples use tsminst1 for the server instance user ID, /tsminst1 for the Tivoli
Storage Manager server instance directory, and /home/tsminst1 as the home
directory of the server instance user.

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

Chapter 9. General procedures for upgrading a server to V7.1 319

Upgrading the server from V5 to V7.1

2. Log out and log in again as tsminst1, or issue this command:

. ~/.profile

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

The value for SERVERNAME must be consistent in the tsmdbmgr.opt and dsm.sys
files.
4. Locate the Tivoli Storage Manager API dsm.sys configuration file. By default,
the dsm.sys file is in the following location:

server_bin_directory/dbbkapi/dsm.sys
5. As root user, add the following lines to the dsm.sys configuration file:
servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
errorlogname /tsminst1
nodename $$_TSMDBMGR_$$

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

where port_number specifies the port that you use for shared memory.
b. In the dsm.sys configuration file, locate the following lines:

320 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

commmethod tcpip
tcpserveraddr localhost
tcpport port_number

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port that you use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

Configuring the system for database backup on Microsoft

Windows systems
Windows

If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, the examples use server1 for the database instance
and d:\tsmserver1 for the Tivoli Storage Manager server directory. When you
issue the commands, replace these values with your actual values.

Procedure
1. Create a file that is named tsmdbmgr.env in the d:\tsmserver1 directory with
the following contents:
DSMI_CONFIG=server_instance_directory\tsmdbmgr.opt
DSMI_LOG=server_instance_directory
2. Set the DSMI_ api environment-variable configuration for the database instance:
a. Open a DB2 command window. One method is to go to the C:\Program
Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage
Manager in a different location, go to the db2\bin subdirectory in your main
installation directory. Then, issue the following command:
db2cmd
b. Issue the following command:
db2set -i server1 DB2_VENDOR_INI=d:\tsmserver1\tsmdbmgr.env
c. Create a file that is named tsmdbmgr.opt in the d:\tsmserver1 directory
with the following contents:
*************************************************
nodename $$_TSMDBMGR_$$
commmethod tcpip

Chapter 9. General procedures for upgrading a server to V7.1 321

Upgrading the server from V5 to V7.1

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

where port_number specifies the port to use for shared memory.

b. In the tsmdbmgr.opt file, locate the following lines:
commmethod tcpip
tcpserveraddr localhost
tcpport 1500

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port to use for shared memory.

What to do next

After you configure the system for database backup, complete the upgrade. Follow
the instructions in Chapter 10, “Taking the first steps after upgrade,” on page 323.

322 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 10. Taking the first steps after upgrade
Verify that the server was upgraded successfully and can operate normally. The
verification steps include starting the server, registering licenses, and backing up
the database. Also, configure available server options.

Procedure

Complete the tasks that are described in the following sections:

1. “Verifying access to storage pools on disk”
2. “Setting up Solaris services for the server instance” on page 324
3. “Configuring server options for server database maintenance” on page 324
4. “Starting the server instance after the upgrade” on page 325
5. “Registering licenses” on page 334
6. “Backing up the database after upgrading the server” on page 335
7. “Verifying the upgraded server” on page 336
8. “Changing the host name for the Tivoli Storage Manager server” on page 336
9. “Updating automation” on page 338
10. “Monitoring the upgraded server” on page 339
11. “Removing GSKit Version 7 after upgrading to Tivoli Storage Manager V7.1”
on page 340

What to do next

After you upgrade the server to V7.1, you can authenticate passwords with the
LDAP directory server, or authenticate passwords with the IBM Tivoli Storage
Manager server. Passwords that are authenticated with the LDAP directory server
can provide enhanced system security. For details, see the section about managing
passwords and logon procedures in the Administrator's Guide.

Verifying access to storage pools on disk

For all disk space that was used for storage pools (device types of FILE or DISK)
by the V5 server, verify that the user ID that owns the upgraded server instance
has ownership or read/write permission. Also ensure that the instance user ID has
access to all devices that are used, including raw logical devices.

Procedure
1. Display information about FILE device classes and DISK volumes.
AIX HPUX Linux Solaris In each path that is listed for the FILE
device class or DISK volume, run the following command:
ls -l
Windows In each directory that is listed for the FILE device class or DISK
volume, run the following command:
dir /Q
2. Verify that the owner of the FILE device class or DISK volume is the server
instance owner and that permissions are set to allow the owner to read and
write the files.

© Copyright IBM Corp. 2009, 2013 323

Upgrading the server from V5 to V7.1

Setting up Solaris services for the server instance

Solaris

If you are running a Tivoli Storage Manager server on a Solaris system, you can
use the Solaris Service Management Facility (SMF) to set up and control the Tivoli
Storage Manager server as a service.

About this task

For more information, see Technote 7021102 (http://www.ibm.com/support/

docview.wss?uid=swg27021102).

Configuring server options for server database maintenance

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

About this task

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

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

Procedure
1. Modify the server options.
AIX HPUX Linux Solaris Edit the server options file,
dsmserv.opt, in the server instance directory. Follow these guidelines when you
edit the server options file:
v To activate an option, remove the asterisk at the beginning of the line.
v Create an option on any line.
v Enter only one option per line. The entire option with its value must be on
one line.
v If you have multiple entries for an option in the file, the server uses the last
entry.
v To view available server options, see the sample file, dsmserv.opt.smp, in the
/opt/tivoli/tsm/server/bin directory.
Windows Edit the server options file, dsmserv.opt, in the server instance
directory by using a text editor. Follow these guidelines when you edit the
server options file:
v To activate an option, remove the asterisk at the beginning of the line.
v Create an option on any line.
v Enter only one option per line. The entire option with its value must be on
one line.

324 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

v If you have multiple entries for an option in the file, the server uses the last
entry.
v To view available server options, see the sample file, dsmserv.opt.smp, in the
c:\Program Files\Tivoli\TSM directory.
2. If you plan to use data deduplication, enable the ALLOWREORGINDEX server
option. Add the following option and value to the server options file:
allowreorgindex yes
3. Set the REORGBEGINTIME and REORGDURATION server options to control when
reorganization starts and how long it runs. Select a time and duration so that
reorganization runs when you expect that the server is least busy. These server
options control both table and index reorganization processes.
a. Set the time for reorganization to start by using the REORGBEGINTIME server
option. Specify the time by using the 24-hour system. For example, to set
the start time for reorganization as 8:30 p.m., specify the following option
and value in the server options file:
reorgbegintime 20:30
b. Set the interval during which the server can start reorganization. For
example, to specify that the server can start reorganization for four hours
after the time set by the REORGBEGINTIME server option, specify the following
option and value in the server options file:
reorgduration 4
4. If the server was running while you updated the server options file, stop and
restart the server.

Starting the server instance after the upgrade

You can select different methods for starting the Tivoli Storage Manager server,
depending on the operating system on which the server is installed.

Procedure

Follow the instructions for your operating system:

v AIX HPUX Linux To start the server on AIX, HP-UX,
Solaris
Linux, or Solaris, follow the instructions in “Starting the server on AIX, HP-UX,
Linux, and Oracle Solaris systems.”
v Windows To start the server on Windows, follow the instructions in “Starting
the server on Windows systems” on page 331.

Starting the server on AIX, HP-UX, Linux, and Oracle Solaris

systems
AIX HPUX Linux Solaris

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

Procedure

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

v To start the server by using the instance user ID, complete the following steps:
1. Ensure that you set access permissions and user limits correctly, as described
in “Verifying access rights and user limits” on page 326.

Chapter 10. Taking the first steps after upgrade 325

Upgrading the server from V5 to V7.1

2. Start the server as described in “Starting the server from the instance user
ID” on page 328.
v To start the server by using the root user ID, complete the following steps:
1. Ensure that you set access permissions and user limits correctly, as described
in “Verifying access rights and user limits.”
2. Authorize the root user ID and start the server, as described in “Starting the
server from the root user ID” on page 329.
v AIX HPUX To start the server automatically, follow the steps
Solaris
in “Automatically starting servers on AIX, HP-UX, or Solaris” on page 329.
v Linux To start the server automatically, follow the steps in “Automatically
starting servers on Linux systems” on page 330.
For information about other options for starting the server, see the Administrator's
Guide.
Related concepts:
“Startup of server instances (AIX, HP-UX, Linux, Solaris)” on page 8

Verifying access rights and user limits

AIX Linux HPUX Solaris

Before you start the Tivoli Storage Manager server on an AIX, HP-UX, Linux, or
Solaris operating system, verify access rights and user limits.

About this task

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

Procedure
1. Verify that the server instance user ID has permissions to start the server.
2. For the server instance that you plan to start, ensure that you have authority to
read and write files in the server instance directory. Verify that the dsmserv.opt
file exists in the server instance directory, and that the file includes parameters
for the server instance.
3. If the server is attached to a tape drive, medium changer, or removable media
device, and you plan to start the server by using the instance user ID, grant
read/write access to the instance user ID for these devices. To set permissions,
take one of the following actions:
v If the system is dedicated to Tivoli Storage Manager and only the Tivoli
Storage Manager administrator has access, make the device special file
world-writable:
chmod +w /dev/rmtX
v If the system has multiple users, you can restrict access by making the Tivoli
Storage Manager instance user ID the owner of the special device files:
chmod u+w /dev/rmtX
v If multiple user instances are running on the same system, change the group
name, for example TAPEUSERS, and add each Tivoli Storage Manager
instance user ID to that group. Then, change the ownership of the device
special files to belong to the group TAPEUSERS, and make them group
writable:

326 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

chmod g+w /dev/rmtX

4. Linux If you are using the Tivoli Storage Manager device driver and the
autoconf utility, use the -a option to grant read/write access to the instance
user ID.
5. HPUX Linux To prevent server failures during interaction
Solaris
with DB2, tune the kernel parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
6. Verify the following user limits based on the guidelines in the table.
Table 60. User limit (ulimit) values
User limit type Standard value Command to query value
Maximum size of core files Unlimited ulimit -Hc
created
Maximum size of a data Unlimited ulimit -Hd
segment for a process
Maximum file size Unlimited ulimit -Hf
Maximum number of open 65536 ulimit -Hn
files
Maximum amount of Unlimited ulimit -Ht
processor time in seconds

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

Tip: If you plan to start the server automatically by using a script, you can set
the user limits in the script.
7. Verify the system-wide value for the maximum number of open files. The
system-wide value must be equal to or greater than the user limit for the
maximum number of open files.
8. Ensure that the user limit of maximum user processes (nproc) is set to the
minimum suggested value of 16384.
a. To verify the current user limit, issue the following command by using the
instance user ID:
ulimit -Hu

For example:
[user@Machine ~]$ ulimit -Hu
16384
b. If the limit of maximum user processes is not set to 16384, set the value to
16384:
AIX Add a line to /etc/security/limits.
HPUX Linux Solaris Add a line to /etc/security/limits.conf.
Linux If the server is installed on the Red Hat Enterprise Linux 6
operating system, set the user limit by editing the /etc/security/limits.d/
90-nproc.conf file in the /etc/security/limits.d directory. This file
overrides the settings in the /etc/security/limits.conf file.

Tip: The default value for the user limit of maximum user processes has
changed on some distributions and versions of the Linux operating system.

Chapter 10. Taking the first steps after upgrade 327

Upgrading the server from V5 to V7.1

The default value is 1024. If you do not change the value to the minimum
suggested value of 16384, the server might fail or hang.

Starting the server from the instance user ID

AIX HPUX Linux Solaris

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

Before you begin

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

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

Tip: For instructions about updating the user ID login script to run the
db2profile script automatically, see the DB2 documentation.
3. Start the server by issuing the following command from the server instance
directory:
/usr/bin/dsmserv

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

Alternatively, if you set up the Tivoli Storage Manager server as a

Solaris
service by using the Solaris Service Management Facility (SMF), you can start
the service by issuing the svcadm enable command. For instructions, see
Technote 7021102 (http://www.ibm.com/support/
docview.wss?uid=swg27021102).

Example

In this example, the name for the instance of the Tivoli Storage Manager server is
tsminst1 and the instance directory is /tsminst1. To start tsminst1, issue the
following commands:
cd /tsminst1
/opt/tivoli/tsm/server/bin/dsmserv

To start the server in the background, issue the following commands:

cd /tsminst1
/opt/tivoli/tsm/server/bin/dsmserv -q &

328 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Starting the server from the root user ID

AIX HPUX Linux Solaris

The standard way to start the server is by using the instance user ID. However, in
some cases, it might be necessary to use another user ID to start the server. For
example, you might want to use the root user ID to ensure that the server can
access specific devices.

Before you begin

For instructions about starting the server from the root user ID, see the
Administrator's Guide.

Automatically starting servers on AIX, HP-UX, or Solaris

AIX HPUX Solaris

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

Before you begin

Ensure that access rights and user limits are set correctly. Follow the instructions in
“Verifying access rights and user limits” on page 326.

About this task

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

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

Procedure

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

Example
Automatically starting a server instance
In this example, the instance user ID is tsminst1; the server instance
directory is /home/tsminst1/tsminst1; the run level is 3; and the process ID
is tsm1. The following entry is added to the /etc/inittab file, on one line:

Chapter 10. Taking the first steps after upgrade 329

Upgrading the server from V5 to V7.1

tsm1:3:once:/opt/tivoli/tsm/server/bin/rc.dsmserv -u tsminst1
-i /home/tsminst1/tsminst1 -q >/dev/console 2>&1
Automatically starting several server instances
This example uses the following instance user IDs:
v tsminst1
v tsminst2
This example uses the following instance directories:
v /home/tsminst1/tsminst1
v /home/tsminst2/tsminst2
This example uses the following process IDs:
v tsm1
v tsm2
The run level is 3. In this example, the following entries are added to the
/etc/inittab file. Each entry is on one line.
tsm1:3:once:/opt/tivoli/tsm/server/bin/rc.dsmserv -u tsminst1
-i /home/tsminst1/tsminst1 -q >/dev/console 2>&1
tsm2:3:once:/opt/tivoli/tsm/server/bin/rc.dsmserv -u tsminst2
-i /home/tsminst2/tsminst2 -q >/dev/console 2>&1
Related reference:
“Server startup script: rc.dsmserv” on page 544

Automatically starting servers on Linux systems

Linux

To automatically start a Tivoli Storage Manager server on a Linux operating

system, use the dsmserv.rc script.

Before you begin

Ensure that kernel parameters are set correctly. For instructions, see the section
about tuning kernel parameters in the Installation Guide.

Ensure that the Tivoli Storage Manager server instance runs under the instance
owner user ID.

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

About this task

The dsmserv.rc script is in the server installation directory, for example,

/opt/tivoli/tsm/server/bin.

The dsmserv.rc script can be used either to start the server manually or to start the
server automatically by adding entries to the /etc/rc.d/init.d directory. The
script works with Linux utilities such as CHKCONFIG and SERVICE.

Procedure

For each server instance that you want to automatically start, complete the
following steps:

330 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

1. Place a copy of the dsmserv.rc script in the /init.d directory, for example,
/etc/rc.d/init.d.
Ensure that you make any changes in the copy of the script. Do not change the
original script.
2. Rename the script copy so that it matches the name of the server instance
owner, for example, tsminst1.
The script was created under the assumption that the server instance directory
is home_directory/tsminst1, for example: /home/tsminst1/tsminst1.
3. If the server instance directory is not home_directory/tsminst1, locate the
following line in the script copy:
instance_dir="${instance_home}/tsminst1"

Change the line so that it points to your server instance directory, for example:
instance_dir="/tsminst1"
4. Use tools such as the CHKCONFIG utility to configure the run level in which the
server automatically starts. Specify a value that corresponds to a multiuser
mode, with networking turned on. Typically, the run level to use is 3 or 5,
depending on the operating system and its configuration. For more information
about multiuser mode and run levels, see the documentation for your operating
system.
5. Optional: You can start or stop the server by issuing one of the following
commands:
v To start the server:
service tsminst1 start
v To stop the server:
service tsminst1 stop

Example

In this example, the instance owner is tsminst1 and the server instance directory is
/home/tsminst1/tsminst1. The dsmserv.rc script copy is named tsminst1, and the
CHKCONFIG utility is used to configure the script to start at run levels 3, 4, and 5.
cp /opt/tivoli/tsm/server/bin/dsmserv.rc /etc/rc.d/init.d/tsminst1
chkconfig --list tsminst1
service tsminst1 supports chkconfig, but is not referenced in
any runlevel (run ’chkconfig --add tsminst1’)
chkconfig --add tsminst1
chkconfig --list tsminst1
tsminst1 0:off 1:off 2:off 3:off 4:off 5:off 6:off
chkconfig --level 345 tsminst1 on
chkconfig --list tsminst1
tsminst1 0:off 1:off 2:off 3:on 4:on 5:on 6:off

Starting the server on Windows systems

Windows

You can start the Tivoli Storage Manager server as a Windows service, which is the
preferred method, or in the foreground.

About this task

On the Windows operating system, you must close all applications before you log
off. As a production server, Tivoli Storage Manager must be available to clients 24
hours a day. At many sites, it is a security exposure to leave an administrator ID

Chapter 10. Taking the first steps after upgrade 331

Upgrading the server from V5 to V7.1

logged on at an unattended computer. The solution is to run the server as a

Windows service. When you run the server as a service, it can be configured to
start automatically when the system is restarted.

Alternatively, if you plan to configure the server or use it in a test environment,

you might want to start the server in the foreground. When you start the server in
the foreground, Tivoli Storage Manager provides a special administrator user ID
that is named SERVER_CONSOLE. All server messages are displayed directly on
the screen. The messages can be useful for debugging startup problems.

If you install a Tivoli Storage Manager server and run it in the foreground, you
must stop the server in the foreground before you start the server as a service.
Similarly, if you start the server as a Windows service, you must stop the server
before you can successfully start it in the foreground.

Procedure

Select one of the following methods for starting the server:

v To start the server by using Windows services, follow the instructions in
“Starting the server by using Windows services.”
v To start the server in the foreground, follow the instructions in “Starting the
server in the foreground” on page 333.
Related concepts:
“Startup of server instances (Windows)” on page 9
Appendix E, “Services associated with the Tivoli Storage Manager server,” on page
555

Starting the server by using Windows services

Windows

If you are running Tivoli Storage Manager on a Windows operating system, you
can start the server as a service.

Before you begin

You must configure the options for starting the server as a service. Complete the
following steps:
1. From the Windows Start menu, click Run, type services.msc, and click OK.
2. In the Services window, select the server instance that you want to start as a
service, and click Properties. For example, select TSM INST1, and click
Properties.
3. To ensure that the server service starts automatically, click the General tab.
From the Startup type list, select Automatic.
4. To set the user for starting the server service, complete the following actions:
a. Click the Log On tab.
b. Select This account, and browse for the user ID that owns the server DB2
instance and has permissions for starting the server.
c. In the Select User window, in the Enter the object name to select field,
enter the user ID.
d. Click Check Names.
e. Click OK.

332 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

If the server service is configured to run under the Local System account, you must
explicitly grant the Local System account access to the Tivoli Storage Manager
database. To grant database access to the Local System account, complete the
following steps:
1. Log on with the user ID that was used to create the Tivoli Storage Manager
server database. This is the user ID that was used to run the DSMSERV FORMAT
utility to initialize the server database. Alternatively, if you configured the
server with the dsmicfgx configuration wizard, this is the user ID that was used
to create the instance.
2. Open a DB2 command window by taking one of the following actions:
v If the Tivoli Storage Manager server is installed on Windows Server 2008 or
Windows Server 2008 R2, click Start > All Programs > IBM DB2 DB2TSM1
> DB2 Command Window - Administrator.
v If the Tivoli Storage Manager server is installed on Windows Server 2012,
open the Start window, and click DB2 Command Window - Administrator.
3. In the DB2 command window, enter the following commands:
set DB2INSTANCE=server1
db2 connect to TSMDB1
db2 grant dbadm with dataaccess with accessctrl on database to user system
db2 grant secadm on database to user system

Tip: When the server service is configured to run under the Local System
account, the database can be accessed by any administrator on the system. In
addition, any administrator who can log on to the system can run the Tivoli
Storage Manager server.

Procedure

To start the server as a Windows service, complete the following steps:

1. Log on to the Tivoli Storage Manager server under an account in the
Administrators group.
2. From the Windows Start menu, click Run, type services.msc, and click OK.
3. In the Services window, select the server instance that you want to start, and
click Start.

What to do next

Because the server service can issue requests that require action, it is important to
monitor server activity with the Operations Center or the administrative client.

To view start and stop completion messages that are logged in the Windows
application log, use the Event Viewer tool in the Administrative Tools folder.

Starting the server in the foreground

Windows

To directly interact with a Tivoli Storage Manager server, start the server in the
foreground. For example, if you want to enter commands, start the server in the
foreground.

Procedure
1. Change to the directory where the server is installed. For example, change to
the c:\program files\tivoli\tsm\server directory.
2. Enter the following command:

Chapter 10. Taking the first steps after upgrade 333

Upgrading the server from V5 to V7.1

dsmserv -k instance_name

where instance_name specifies the Tivoli Storage Manager server instance.

Registering licenses
Immediately register any Tivoli Storage Manager licensed functions that you
purchased so that you do not lose data after you begin to use the server.

Before you begin

Verify that the server instance directory of your installation does not include a
NODELOCK file. The NODELOCK file contains the previous licensing information for
your installation. This licensing information is replaced when the upgrade is
complete. If the directory includes a NODELOCK file, move the file to another
directory.

Procedure
1. AIX HPUX Linux Register the licenses for the Tivoli
Solaris
Storage Manager server components that are installed on your system by
issuing the REGISTER LICENSE command:
register license file=installation_directory/server/bin/component_name.lic

where installation_directory specifies the directory in which you installed the

component, and component_name specifies the abbreviation for the component.

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

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

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

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

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

Restriction: You cannot register licenses for Tivoli Storage Manager for Mail,
Tivoli Storage Manager for Databases, Tivoli Storage Manager for ERP, and
Tivoli Storage Manager for Space Management.
2. Register the licenses for the Tivoli Storage Manager server
Windows
components that are installed on your system by issuing the REGISTER LICENSE
command:
register license file=installation_directory\server\component_name.lic

where installation_directory specifies the directory in which you installed the

component, and component_name specifies the abbreviation for the component.

For example, if you installed the server in the default directory, c:\Program
Files\Tivoli\TSM, register the license by issuing the following command:
register license file=c:\Program Files\Tivoli\TSM\server\tsmbasic.lic

334 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

For example, if you installed Tivoli Storage Manager Extended Edition in the
c:\Program Files\Tivoli\TSM directory, issue the following command:
register license file=c:\Program Files\Tivoli\TSM\server\tsmee.lic

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

c:\Program Files\Tivoli\TSM directory, issue the following command:
register license file=c:\Program Files\Tivoli\TSM\server\dataret.lic

Restriction: You cannot register licenses for Tivoli Storage Manager for Mail,
Tivoli Storage Manager for Databases, Tivoli Storage Manager for ERP, and
Tivoli Storage Manager for Space Management.

Backing up the database after upgrading the server

After you successfully upgrade the server, perform a full backup of its database as
soon as possible.

Procedure
1. Complete the following steps:
a. If you did not use the upgrade wizard (dsmupgdx) to upgrade the server,
ensure that you have completed the steps to manually configure the system
for database backups.
b. If you used the media method for upgrade and used a tape device, remove
or check out from the library the tape that was used to hold the extracted
data. Prevent the tape from being reused until you are sure that the
upgraded server is running properly and you do not need to repeat the
database insertion step.
2. Select the device class to be used for automatic backups of the database. Issue
the following command from a IBM Tivoli Storage Manager administrative
command line.
set dbrecovery device_class_name

The device class that you specify is used by the database manager for all
automatic database backups.
3. Back up the database.
backup db devclass=device_class_name type=full

The device class can be the same as or different from the device class that you
specified with the SET DBRECOVERY command. If the device class is different, you
receive a warning message, but the backup operation continues.
Related tasks:
“Configuring the system for database backup” on page 318

Chapter 10. Taking the first steps after upgrade 335

Upgrading the server from V5 to V7.1

Verifying the upgraded server

Verify the operation of the server. If the server was installed on a new system as
part of the upgrade, check and update connections to storage devices and other
components.

Procedure
1. Monitor the messages that the server issues as it starts. Watch for error and
warning messages.
2. If the server is running on a new system as a result of the upgrade, check the
following items:
a. Ensure that all of the original server's storage devices are accessible to the
upgraded server.
b. Compare the device names on the new system with the names for the
devices on the original system. Update definitions for the devices on the
server if needed. For example, update path definitions.
c. Update the network address that is used by backup-archive clients, storage
agents, library client servers, and other servers for communicating with the
upgraded server.
Optionally, instead of making these updates, consider whether you can use
the network address of the original system as the address of the new
system. You might also be able to update domain name service (DNS) to
point to the new system instead of the original system. Consult your
network administrator.
3. Verify that you can connect to the server using an administrative client as you
did for the earlier version of the server.
4. Run commands to get a summary of information in the database. Compare the
summary with the results for the same commands before the upgrade.
5. Perform backups for typical client nodes and verify that the backups work as
expected.
6. Verify that operations such as LAN-free data movement and library sharing
work correctly.
7. After you are satisfied that the server is performing as expected and you will
not need to revert to the previous version of the server, remember to return any
settings that you changed to prepare for the upgrade back to the original
values.
Related reference:
“Sample commands to run for validation of the database upgrade” on page 546

Changing the host name for the Tivoli Storage Manager server
If you must change the host name of the Tivoli Storage Manager V7.1 server,
ensure that you also update the database configuration. If you fail to update the
database configuration, the Tivoli Storage Manager server might not start.

336 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Changing the host name for a server running on AIX, HP-UX,

Linux, or Solaris systems
AIX HPUX Linux Solaris

To change the host name of a Tivoli Storage Manager server running on an AIX,
HP-UX, Linux, or Solaris system, several steps are required.

Procedure

Change the host name by completing the following steps:

1. Stop any Tivoli Storage Manager servers that are running on the system.
2. Change the host name by using the procedures that are defined for your
operating system.
3. From the root user ID on the system, issue the following command:
db2set -g DB2SYSTEM=newhostname
where newhostname is the new host name for the server.

Tip: The db2set command is in the /opt/tivoli/tsm/db2/adm directory.

4. Verify that the DB2SYSTEM value was changed by issuing the following
command:
db2set -all

This command shows all configuration settings that are used by the database.
5. In the instance directory/sqllib directory, locate the db2nodes.cfg file. The
file contains an entry that shows the previous host name, for example:
0 tsmmon TSMMON 0
a. Update the entry with the new host name. The entry is similar to the
following entry:
0 tsmnew newhostname 0
b. Save and close the changed file.

Changing the host name for a server running on Windows

Windows

To change the host name of a Tivoli Storage Manager server running on a

Windows system, back up the database, stop the server, edit the DB2 configuration
file, and restart the server.

Procedure

Use the following steps to change a host name when the Tivoli Storage Manager
server is installed.
1. Back up the Tivoli Storage Manager database.
2. Stop the Tivoli Storage Manager server.
3. Change the startup service of the Tivoli Storage Manager server to manual
startup:
a. In the Windows Services Management Console, select TSM Server service.
b. Right-click the service and click Properties.
c. In the Startup Type field, select Manual.

Chapter 10. Taking the first steps after upgrade 337

Upgrading the server from V5 to V7.1

4. Issue the following commands from the DB2 command prompt window to
update the DB2SYSTEM registry variable, turn off extended security, and
verify the settings:
db2set -g DB2SYSTEM=new_host_name
db2set -g DB2_EXTSECURITY=NO
db2set -all

Tip: The DB2_EXTSECURITY parameter is reset to YES when you restart the
system.
5. Check for the presence of the db2nodes.cfg file. Depending on your version of
Windows, the db2nodes.cfg file might be in one of the following directories:
v Windows 2008 or later:
C:\ProgramData\IBM\DB2\DB2TSM1\<DB2 Instance name>
v Other versions of Windows:
C:\Documents and Settings\All Users\Application Data\IBM\DB2\DB2TSM1\
<DB2 Instance name>

Tip: The db2nodes.cfg file is a hidden file. Ensure that you show all files by
going to Windows Explorer and selecting Tools > Folder Options and
specifying to view hidden files.
If the db2nodes.cfg file does not exist on your system, proceed to the next
step. If the file does exist, issue the following command to update the host
name:
db2nchg /n:0 /i:<instance> /h:<new host name>
6. Change the Windows host name, as described in the documentation for the
Windows system that you are using.
7. Restart the server.
8. Update the security settings by running the following command:
db2extsec -a new_host_name\DB2ADMNS -u new_host_name\DB2USERS
9. Start the Tivoli Storage Manager server.
10. Reset the startup service for Tivoli Storage Manager server to be automatic:
a. In the Windows Services Management Console, select TSM Server service.
b. Right-click the service and click Properties.
c. In the Startup Type field, select Automatic.

Updating automation
After an upgrade, administrative schedules that were defined in V5 might not
work without modification because of changes in command syntax. Implement and
verify changes to any automation or scripts that were identified as needing
modification in the planning process.

About this task

Important: Ensure that automation includes a backup of the database. Back up the
database at least once per day.

338 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

Monitoring the upgraded server

When you start to use the upgraded server in production operation, monitor the
space that is used by the server to ensure that the amount of space is adequate.
Adjust the space if needed.

Procedure

To monitor the V7.1 server and make any required adjustments, complete the
following steps:
1. Monitor the active log to ensure that the size is correct for the workload that is
handled by the server instance.
When the server workload reaches its typical expected level, the space that is
used by the active log is 80% - 90% of the space that is available to the active
log directory. At that point, you might need to increase the amount of space.
Whether you must increase the space depends on the types of transactions in
the server workload. Transaction characteristics affect how the active log space
is used.
The following transaction characteristics can affect the space usage in the active
log:
v The number and size of files in backup operations
– Clients such as file servers that back up large numbers of small files can
cause large numbers of transactions that are completed quickly. The
transactions might use a large amount of space in the active log, but for a
short time.
– Clients such as a mail server or a database server that back up large
chunks of data in a few transactions can cause small numbers of
transactions that take a long time. The transactions might use a small
amount of space in the active log, but for a long time.
v Network connection types
– Backup operations that occur over fast network connections cause
transactions that are completed more quickly. The transactions use space
in the active log for a shorter time.
– Backup operations that occur over relatively slower connections cause
transactions that take a longer time to be completed. The transactions use
space in the active log for a longer time.
If the server is handling transactions with a wide variety of characteristics, the
space that is used for the active log might increase and decrease significantly
over time. For such a server, you might need to ensure that the active log
typically has a smaller percentage of its space used. The extra space allows the
active log to grow for transactions that take a long time.
2. Monitor the archive log to ensure that space is always available.

Remember: If the archive log becomes full, and the archive failover log
becomes full, the active log can become full, and the server stops. The goal is to
make enough space available to the archive log so that it never uses all
available space.
You are likely to notice the following pattern:
a. Initially, the archive log grows rapidly as typical client-backup operations
occur.
b. Database backups occur regularly, either as scheduled or done manually.

Chapter 10. Taking the first steps after upgrade 339

Upgrading the server from V5 to V7.1

c. After full database backups occur, log pruning occurs automatically. The
space that is used by the archive log decreases when the pruning occurs.
d. Normal client operations continue, and the archive log grows again.
e. Database backups occur regularly, and log pruning occurs as often as full
database backups occur.
With this pattern, the archive log grows initially, decreases, and then might
grow again. Over time, as normal operations continue, the amount of space
that is used by the archive log should reach a relatively constant level.
If the archive log continues to grow, consider taking one or both of these
actions:
v Add space to the archive log. You might need to move the archive log to a
different file system.
For information about moving the archive log, see the Administrator's Guide.
v Increase the frequency of full database backups so that log pruning occurs
more frequently.
3. If you defined a directory for the archive failover log, determine whether any
logs are stored in that directory during normal operations. If the failover log
space is being used, consider increasing the size of the archive log. The goal is
to use the archive failover log only under unusual conditions, not in normal
operation.
Related concepts:
“Recovery log space requirements” on page 39
“Database operations” on page 4

Removing GSKit Version 7 after upgrading to Tivoli Storage Manager

V7.1
Windows

The Tivoli Storage Manager installation wizard upgrades GSKit Version 8 and later.
GSKit Version 7 is not removed or upgraded when you upgrade to Tivoli Storage
Manager Version 7.1, even if it was installed with an earlier version of Tivoli
Storage Manager.

About this task

If you no longer need GSKit Version 7 and want to free up space on your system,
you can remove it after the upgrade to Tivoli Storage Manager Version 7.1.

Attention: Removing GSKit Version 7 might affect other programs on your

system that rely on it.

Procedure
1. Back up your registry.
a. Click Start, and then click Run.
b. Type Regedit. Click OK.
c. To save a copy of your registry, select File > Export.
d. If you must later restore the registry, select File > Import.
For additional details, see your Windows documentation.

340 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Upgrading the server from V5 to V7.1

2. Locate the directory where the GSKit is installed. The default directory is
C:\Program Files\IBM\gsk7\.
3. Remove the GSKit installation directory, gsk7, and all subfiles and directories.
Right-click the folder and click Delete.
4. Remove the GSKit Version 7 registry key and all subkeys and values.
Attention: Removing the wrong key can cause system problems such as not
being able to restart the workstation.
a. Click Start, and then click Run.
b. Type Regedit. Click OK.
c. The GSKit registry key is located in this directory: HKEY_LOCAL_MACHINE\
SOFTWARE\IBM. Right-click the registry key, HKEY_LOCAL_MACHINE\SOFTWARE\
IBM\GSK7, and click Delete.

Chapter 10. Taking the first steps after upgrade 341

Upgrading the server from V5 to V7.1

342 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 11. Troubleshooting the database upgrade
Review this section for tips to troubleshoot common problems. A procedure that
explains how to return to the previous version of the server is also included.

About this task

For the latest information about issues that might occur during an upgrade and
how to resolve them, go to the IBM Tivoli Storage Manager support site:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.

Server upgrade phase: warnings about unsupported server options

When running the upgrade wizard or one of the upgrade utilities, warning
messages about server options that are not supported are issued.

Symptoms

Warning messages about the server options appear, but the process continues.

Causes

The server options file includes options that are not valid for a V5.5 server. For
example, the options file might include some options that are valid only for a V5.4
or earlier server.

If you already updated the server options file to add options that are valid only for
a V7.1 server, you might also see warning messages during upgrade processes.

Resolving the problem

You can ignore the warning messages until after the upgrade process is complete.

After the upgrade process is complete, and before starting the V7.1 server, edit the
server options file and remove any options that are not valid for V7.1.

Database extraction phase: connection refusal message

When using the network method to move the V5 server database to the V7 server
database, connection refusal messages are received when starting the extraction
operation.

Symptoms

You might see the following messages:

ANR8214E Session open with host_address failed due to connection refusal.
ANR0454E Session rejected by server server_name, reason: Communication Failure.

Causes

A connection refusal message usually means that the system is trying to connect to
a host or port where no process is listening for a connection.

© Copyright IBM Corp. 2009, 2013 343

Troubleshooting the database upgrade

Resolving the problem

Before trying the extraction process again, check the following items:
v Ensure that the TCP/IP communication method is enabled for the target server.
The communication method is set using the COMMMETHOD option in the server
options file. TCP/IP is the default setting for the server communication method,
but the server options file for the target server might have a different value.
Check whether the server options file for the target server has COMMMETHOD NONE,
or has only COMMMETHOD SHMEM specified. Remove COMMMETHOD NONE if it appears in
the server options file. Add COMMMETHOD TCPIP if it is not in the server options
file.
v Ensure that the values that you specified with the HLADDRESS and LLADDRESS
parameters on the DSMSERV EXTRACTDB command are correct. The LLADDRESS
parameter must match the value that is specified for the TCPPORT option in the
server options file for the target server.
v Before issuing the DSMSERV EXTRACTDB command again, ensure that you wait for
the DSMSERV INSERTDB process to issue the following message:
ANR1336I INSERTDB: Ready for connections from the source server

Database formatting phase: failure with rc=499

Windows

When the upgrade wizard is used to upgrade a Tivoli Storage Manager server on
Windows from V5 to V7.1, the system fails to format the new database.

Symptoms

The database formatting operation fails with the return code rc=499.

Causes

This issue might be caused by a Sophos antivirus program. If a Sophos antivirus

program is installed on the system that is being upgraded, the program might scan
the Tivoli Storage Manager instance database during the upgrade. The scanning
operation can affect the creation of database files.

Resolving the problem

To diagnose the problem, review the dsmupgdx.trc file in the c:\Program

Files\Tivoli\TSM directory. If you see the rc=499 message, the database was not
correctly formatted. The following example shows trace output with the rc=499
message:
timestamp com.tivoli.dsm.ServerConfig.ServerDB$FormatThread.run(): Issuing cmd:
"C:\Program Files\Tivoli\TSM\Server\dsmserv" -k Server1 LOADFORMAT dbfile=\
"C:\Program Files\Tivoli\TSM\server1\dbfile.1\" activelogdir=\"D:\ActiveLog\"
archlogdir=\"E:\ArchiveLog\" activelogsize=16384 >Format.Out 2>&1 on id tsminst1
timestamp com.tivoli.dsm.ServerConfig.ProcessMonitor.run(): enter, Monitoring file
C:\Program Files\Tivoli\TSM\server1\Format.Out
timestamp 2012 com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File
C:\Program Files\Tivoli\TSM\server1\Format.Out not created yet.
timestamp com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File C:\Program Files
\Tivoli\TSM\server1\Format.Out now being read. ...
timestamp com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File C:\Program Files
\Tivoli\TSM\server1\Format.Out now being read.
timestamp com.tivoli.dsm.ServerConfig.ServerDB$FormatThread.run(): Format rc: 9994
timestamp com.tivoli.dsm.ServerConfig.ServerDB$FormatThread.run(): format stderr:

344 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Troubleshooting the database upgrade

timestamp com.tivoli.dsm.ServerConfig.ProcessMonitor.cancel(): enter

timestamp com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File C:\Program
Files\Tivoli\TSM\server1\Format.Out now being read.
timestamp com.tivoli.dsm.ServerConfig.ProcessMonitor.run(): exit
timestamp com.tivoli.dsm.ServerConfig.ProcessMonitor.cancel(): exit
timestamp com.tivoli.dsm.ConfigWizard.DoFormatPanel.signalEvent(): enter,
event=formatDone, rc=499

If the dsmupgdx.trc file is not available, review the db2diaglog file to see whether
the following error is reported:
Invalid collation ID

The following sample db2diaglog file indicates a failure to format the database:
timestamp LEVEL: Severe
PID : 2304 TID : 2008 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000 DB : TSMDB1
APPHDL : 0-8 APPID: *LOCAL.SERVER1.121107195909
AUTHID : TSMINST1
EDUID : 2008 EDUNAME: db2agent (TSMDB1) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 20
sqlerrmc: Invalid collation ID
sqlerrp : SQLNQB6E
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0xFFFFFF9C (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

If you determine that the database was not correctly formatted, and if the Sophos
antivirus program is installed, complete the following steps:
1. To ensure that the antivirus program does not affect the database formatting
operation, complete one of the following steps:
v Configure the antivirus program to ensure that it does not scan the Tivoli
Storage Manager instance database or files.
v Disable the antivirus program for a limited time so that it does not affect the
database formatting process.

Remember: Before you reconfigure or disable the antivirus program, review

the antivirus documentation so that you are aware of potential risks and how
to mitigate them.
2. Run the upgrade wizard again.
3. If you disabled the antivirus program, reenable it.

Database insertion phase: ANR1338E messages from the upgrade

utility
One or more ANR1338E messages about constraint violations or other data
problems are issued during the database insertion phase, when running the
upgrade wizard or the DSMSERV INSERTDB upgrade utility.

Symptoms

The messages about constraint violations appear, and processing continues. Data
that has a problem is not inserted into the V7 database.

Chapter 11. Troubleshooting the database upgrade 345

Troubleshooting the database upgrade

Causes

The insertion process encountered one or more problems with values from the V5
database that were being inserted into the V7 database. The values did not meet
constraints for a data type or data format, or were not valid for some other reason.

Resolving the problem

Because some data was not inserted into the database, the database is in an
inconsistent state.

Attention: Do not start the server until the data problems are investigated. Data
damage might occur if you start the server. Contact IBM Support to get assistance
in determining the extent of the problem, and what action to take next.

The IBM Support team will require you to provide the constrnt.log file, which
contains details about the problems.

Database insertion phase: ANR1525I messages with no apparent

progress
The DSMSERV INSERTDB utility repeatedly issues status message ANR1525I with no
sign that any progress is being made.

Symptoms

You might see messages such as the following set while the insertion process is
running.
ANR1524I INSERTDB: Beginning database update phase.
ANR1525I INSERTDB: Updated 0 of 25,185,883 database entries in 0:23:10.
ANR1525I INSERTDB: Updated 0 of 25,185,883 database entries in 0:53:13.
ANR1525I INSERTDB: Updated 0 of 25,185,883 database entries in 1:23:16.
ANR1525I INSERTDB: Updated 0 of 25,185,883 database entries in 1:53:19.
ANR1525I INSERTDB: Updated 0 of 25,185,883 database entries in 2:23:22.

The count of updated database entries might not increase for a long time.

Causes

In the database update phase of the DSMSERV INSERTDB utility, information from
multiple sets of source tables are merged into a smaller number of target tables.
Each operation that merges multiple source tables into one target table is a single,
long-running DB2 UPDATE operation. An UPDATE operation does not provide status
until it completes. Because the status is not updated until completion, the
ANR1525I message repeatedly shows an unchanging value for the number of
entries that have been updated.

After each set of tables is merged into one target table, the ANR1525I message
changes to reflect the progress up to that point. However, the merge operation for
each set of tables can take a considerable amount of time, during which the status
remains the same. This lack of change in status is not the sign of a problem. The
repeated issuance of the ANR1525I message is an indication that the DSMSERV
INSERTDB utility is still running, even if the statistics that the messages report do
not change.

346 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Troubleshooting the database upgrade

Resolving the problem

After the DSMSERV INSERTDB utility enters the database update phase, most of the
remaining work is done by DB2. You can use only indirect methods to determine if
the operation is progressing. One such method is to use a system monitor, such as
topas on AIX, to confirm that the DB2 db2sysc process is operating. The use of
processor resource and I/O to the database directories by the db2sysc process are
good indications that the update phase is progressing.

Database insertion phase: problems with restarting the upgrade

process
After the upgrade process fails at the database insertion step, restarting the process
results in errors.

Symptoms
When you try to restart the process, by using either the upgrade wizard (dsmupgdx)
or commands, you receive messages that the database already exists, or that
directories are not empty.

Causes

The problem occurs because a database instance was already created, despite the
failure. Directories that you specified in the wizard or with the DSMSERV LOADFORMAT
command might no longer be empty because the failed process started to write
information in these directories. To do the formatting operation again, the
directories must be empty.

Resolving the problem

Try the following actions to resolve the problem.

AIX HPUX Linux Solaris

1. Ensure that you are logged in with the same user ID that you were
using when the insertion operation failed. This should be the user ID
that you created specifically for the server instance that you were
upgrading when the failure occurred.
Attention: Ensure that you are using the correct user ID. The database
that is owned by the user ID that you log in with now is the database
that will be destroyed in the following step. Do not take the following
steps when you are logged in with a user ID that owns a valid,
working V7 server instance.
2. Remove the database instance that was created.
dsmserv removedb TSMDB1

Alternate method: If the DSMSERV REMOVEDB command fails for some

reason, use the DB2 command to drop the database. Issue the following
commands:
db2start
db2 drop db tsmdb1
3. To reuse the database and log directories that you specified in the failed
attempt to create the server instance, verify that each directory is now
empty.

Chapter 11. Troubleshooting the database upgrade 347

Troubleshooting the database upgrade

4. Restart the upgrade wizard for the server instance that you are
upgrading.
If you are using commands, restart at the step in which you issue the
DSMSERV LOADFORMAT command.
Windows

1. Remove the database instance that was created. Issue the command:
dsmserv removedb -k server_instance_name TSMDB1

The server_instance_name is the name of the registry key for the server
instance that you were upgrading when the failure occurred. For
example, if you were upgrading Server2, issue the command:
dsmserv removedb -k server2 TSMDB1

Attention: Ensure that you specify the name of the server instance for
which the process failed. The database for the specified server instance
is destroyed by issuing this command.

Alternate method: If the DSMSERV REMOVEDB command fails for some

reason, use the DB2 command to drop the database:
a. Click Start > Programs > IBM DB2 > DB2TSM1 > Command Line
Tools > Command Line Processor.
b. Enter quit to exit the command-line processor.
A window with a command prompt opens, with the environment
properly set up to successfully issue the commands in the next
steps.
c. From the command prompt in that window, issue the following
command to set the environment variable for the server instance
that you are working with:
set db2instance=server_instance_name

For example, to set the environment variable for the Server1 server
instance, issue the following command:
set db2instance=server1
d. Issue the command to drop the database:
db2 drop db tsmdb1
2. To reuse the database and log directories that you specified in the failed
attempt to create the server instance, verify that each directory is now
empty.
3. Restart the upgrade wizard for the server instance that you are
upgrading.
If you are using commands, restart at the step in which you issue the
DSMSERV LOADFORMAT command.

348 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Troubleshooting the database upgrade

Server startup phase: error ANR0162W

Windows

After the Tivoli Storage Manager server is upgraded from V5 to V7.1 on Windows,
the server instance fails to start.

Symptoms

The server startup fails with error message ANR0162W.

Causes

This issue might be caused by a Sophos antivirus program. If a Sophos antivirus

program is installed on the system that is being upgraded, the antivirus program
might scan the Tivoli Storage Manager instance database during the upgrade. The
scanning operation can affect the startup of the server instance.

Resolving the problem

To diagnose the problem, attempt to start the server. To start the server from the
default directory, C:\Program Files\Tivoli\TSM\server, issue the following
command:
dsmserv -k server_instance

where server_instance is the name of the server instance. Server1 is the default for
the first instance of the Tivoli Storage Manager server.

If the server fails to start, the output includes message ANR0162W, as in the
following example:
C:\Program Files\Tivoli\TSM\server>dsmserv -k server1
ANR7800I DSMSERV generated at 02:08:06 on Jul 26 2012.
Tivoli Storage Manager for Windows
Version 7, Release 3, Level 2.000
Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 2011.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR0900I Processing options file c:\Program Files\Tivoli\TSM\server1\dsmserv.opt.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
...
ANR0984I Process 1 for AUDIT LICENSE started in the BACKGROUND at 13:14:09.
ANR2820I Automatic license audit started as process 1.
ANR2560I Schedule manager started.
ANR0162W Supplemental database diagnostic information: -1:42884:-440
([IBM][CLI Driver][DB2/NT64] SQL0440N No authorized routine named "COLLATIONNAME"
of type "FUNCTION" having compatible arguments was found. SQLSTATE=42884).
ANR0162W Supplemental database diagnostic information: -1:42884:-440
([IBM][CLI Driver][DB2/NT64]
...
ANR0171I tbtbl.c(14146): Error detected on x:y, database in evaluation mode.
...
ANR9999D_3937368011 LmLcAuditThread(lmlcaud.c:864) Thread<31>: Error in committing
audit license transaction.
ANR9999D Thread<31> issued message 9999 from:
ANR9999D Thread<31> 000007FEE95CE599 OutDiagToCons()+159
ANR9999D Thread<31> 000007FEE95C7FFC outDiagfExt()+fc
ANR9999D Thread<31> 000007FEE91EC95B LmLcAuditThread()+13fb

Chapter 11. Troubleshooting the database upgrade 349

Troubleshooting the database upgrade

ANR9999D Thread<31> 000007FEE8DE6384 startThread()+124

ANR9999D Thread<31> 0000000071F41D9F endthreadex()+43
ANR9999D Thread<31> 0000000071F41E3B endthreadex()+df
ANR9999D Thread<31> 0000000076C2BE3D BaseThreadInitThunk()+d
ANR9999D Thread<31> 0000000076E36A51 RtlUserThreadStart()+21
...
ANR0369I Stopping the database manager because of a server shutdown.
ANR0991I Server shutdown complete.

If you determine that the server instance failed to start, and the Sophos antivirus
program is installed, complete the following steps:
1. To ensure that the antivirus program does not affect the startup of the server
instance, complete one of the following steps:
v Configure the antivirus program to ensure that it does not scan the Tivoli
Storage Manager instance database or files.
v Disable the antivirus program for a limited time so that the server instance
can be started.

Remember: Before you reconfigure or disable the antivirus program, review

the antivirus program documentation so that you are aware of potential risks
and how to mitigate them.
2. Start the server instance again.
3. If you disabled the antivirus program, reenable it.

Server startup phase: warnings about unsupported server options

When you start the V7.1 server, you receive warning messages about server
options that are not supported. However, the options do not appear in the list of
server options that were deleted for V7.1.

Symptoms

ANR0902W messages about the server options appear, but the server starts.

Causes

V5 releases tolerated the presence of some server options that were not supported
by the server. The V7.1 server flags such options by issuing warning messages.

The list of server options that were deleted for V7.1 contains options that were
deleted since V5.5 was released. If the server option that causes a warning on your
system is not in the list of deleted server options, the option was likely deleted in
some earlier release, for example, V5.4.

Resolving the problem

You can ignore the error, or update the server options file and restart the server.
Related reference:
“Deleted server commands, utilities, and options” on page 65

350 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Troubleshooting the database upgrade

Postupgrade phase: dsmserv.dsk file no longer available

After running the upgrade wizard or one of the upgrade utilities, you cannot
locate the dsmserv.dsk file.

Symptoms

The dsmserv.dsk file is no longer in the default directory for the server.

Causes

The dsmserv.dsk file is not used in Tivoli Storage Manager V7.1.

Resolving the problem

No action is required. However, if you are planning to upgrade the server from V5
to V7.1, you might want to save the dsmserv.dsk file in case you need to revert to
Tivoli Storage Manager V5.

Postupgrade phase: VARY command fails

After completing an upgrade of Tivoli Storage Manager server, the VARY command
fails.

Symptoms

You are unable to use this command to bring a random access storage pool online
for the Tivoli Storage Manager server.

Causes

This issue can have various causes. One possible cause is that the user ID that is
running the server does not have write access to the server disks.

Resolving the problem

Ensure that the user ID that will be used to run the server has write access to the
server disks. Then, run the VARY command again.

Reverting from V7.1 to the previous V5 server version

If you must revert the Tivoli Storage Manager server to the previous version after
an upgrade, you must have a full database backup and the server installation
media from your original version, and key configuration files. By carefully
following the preparation steps before you upgrade the server, it might be possible
to revert to the previous version of the server with minimal loss of data.

Before you begin

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

Chapter 11. Troubleshooting the database upgrade 351

Troubleshooting the database upgrade

v The dsmserv.dsk file

About this task

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

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

Steps for reverting to the previous server version

Procedure

On the system where the V7.1 server is installed, complete the following steps:
1. Back up the V7.1 database and save the contents of the instance directory,
including the volume history file, the device configuration file, and server
options file. Keep these files in case you must return to the V7.1 server.
2. Remove the database from the database manager, then delete the database and
recovery log directories.
a. Manually remove the database. Issue the command:
dsmserv removedb tsmdb1
You can also use the following command to remove the database:
db2 drop db tsmdb1
b. If you must reuse the space that is occupied by the database and recovery
log directories, you can now delete these directories.
3. Use the installation program to uninstall the V7.1 server. Uninstallation
removes the server and the database manager software with their directories.
For instructions about uninstalling the server, see the Installation Guide.
4. Reinstall the version of the server program that you were using before the
upgrade to V7.1. This version must match the version that your server was
running when you created the database backup that you will restore in a later
step.
For example, if the server was at version 5.4.4.0 before the upgrade, and you
intend to use the database backup that was in use on this server, you must
install the V5.4.0.0 server program. After that, you must install the V5.4.4.0 fix
pack to be able to restore the database backup.
a. Reinstall the base version of the server that was in use before the upgrade
to V7.1.
b. Reinstall any fix packs that were installed on the base server version
before the upgrade to V7.1.
5. Copy the following files to the directory for server information:
v Device configuration file
v Volume history file
v The dsmserv.dsk file
v The server options file (typically, dsmserv.opt)
6. Format the database by using the DSMSERV FORMAT utility. For details, see the
information for the version of the server that you are reinstalling. Information
for V5.5 is available at this information center: http://
publib.boulder.ibm.com/infocenter/tivihelp/v1r1
Information for V5.4 and V5.3 is available in the same information center. In
the navigation pane, scroll down and expand Previous versions.
7. Restore the database by using the backup that was created in the preparation
steps before the upgrade.

352 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Troubleshooting the database upgrade

8. If you enabled data deduplication for any FILE-type storage pools that existed
before the upgrade, or if you moved data that existed before the upgrade into
new storage pools while using the V7.1 server, you must complete additional
recovery steps. See “Additional recovery steps if you created new storage
pools or enabled data deduplication.”
9. If the REUSEDELAY setting on storage pools is less than the age of the database
that you restored, restore volumes on any sequential-access storage pools that
were reclaimed after that database backup. Use the RESTORE VOLUME command.
If you do not have a backup of a storage pool, audit the reclaimed volumes
by using the AUDIT VOLUME command, and specifying the FIX=YES parameter
to resolve inconsistencies. Use the command:
audit volume volume_name fix=yes
10. If client backup or archive operations were performed by using the V7.1
server, you might need to audit the storage pool volumes on which the data
was stored.
11. If you were using active-data pools before upgrading to V7.1, recreate them.
The amount of time required to recreate the active-data pools might be
significant, depending on the number and size of the active-data pools to be
recreated.

Additional recovery steps if you created new storage pools or

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

About this task

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

Perform these steps after the server is restored to V5.

Procedure
v For each storage pool for which you enabled the data deduplication function,
restore the entire storage pool by using the RESTORE STGPOOL command. To
complete this task, you must have a complete backup of the storage pool, which
must have been created before the upgrade to V7.1.
v For storage pools that you created after the upgrade, review the following
information to determine what action to take.
Data that was moved from existing V5 storage pools into the new storage pools
might be lost because the new storage pools no longer exist in your restored V5
server. Possible recovery depends on the type of storage pool:
– If data was moved from V5 DISK-type storage pools into a new storage pool,
space that was occupied by the data that was moved was probably reused.
Therefore, you must restore the original V5 storage pools by using the storage
pool backups that were created before the upgrade to V7.1.

Chapter 11. Troubleshooting the database upgrade 353

Troubleshooting the database upgrade

If no data was moved from V5 DISK-type storage pools into a new storage
pool, audit the storage pool volumes in these DISK-type storage pools.
– If data was moved from V5 sequential-access storage pools into a new storage
pool, that data might exist and be usable in storage pool volumes on the
restored V5 server. The data might be usable if the REUSEDELAY parameter for
the storage pool was set to a value that prevented reclamation while the
server was running as a V7.1 server. If any volumes were reclaimed while the
server was running as a V7.1 server, restore those volumes from storage pool
backups that were created before the upgrade to V7.1.

354 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Part 2. Migrating Tivoli Storage Manager V5 servers on AIX,
HP-UX, or Solaris systems to V7.1 on Linux
An IBM Tivoli Storage Manager V5 server that runs on an AIX, HP-UX, or Solaris
operating system can be migrated to V7.1 on a Linux x86_64 operating system.

About this task

Depending on your hardware and software environment, this migration procedure

might be useful for achieving server consolidation, load balancing, or
standardization on the Linux operating system.

© Copyright IBM Corp. 2009, 2013 355

356 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 12. Migration overview
Before you migrate the server, review the migration options, migration roadmap,
the scenarios for migration, and related information.

You can use one of the following migration options:

v Follow the cross-platform migration procedure, starting with the “Migration
roadmap.”
v Follow the cross-platform migration procedure, starting with the “Migration
roadmap,” and facilitate the process by using Migration Engine from Butterfly
Software.
Migration Engine from Butterfly Software automates the process of migrating
backup data from one or more Tivoli Storage Manager V5 servers to a Tivoli
Storage Manager V6 server. Migration Engine from Butterfly Software also
provides planning options for migration and real-time reports about migration
progress. Only IBM Software Services and IBM Business Partners are authorized
to use Migration Engine from Butterfly Software. For more information, contact
IBM Software Services or your IBM Business Partner.

Migration roadmap
The migration roadmap provides links to information to help you plan, prepare,
and complete the migration process.

To plan the migration, complete the following steps:

1. Review the migration scenarios. See “Scenarios for migrating a server from an
AIX, HP-UX, or Solaris system to V7.1 on Linux” on page 358.
2. Become familiar with the commands and utilities that you can use during the
migration process. See “Utilities and commands for data migration” on page
363.
3. Review the guidelines for moving data that cannot be accessed or is not
readable by the target system. See “Data movement” on page 363.
4. Review the information about migrating devices. See “Device availability” on
page 364.
5. Review the guidelines about protecting client data and the server during the
migration process. See “Protection for client data and the server during the
process” on page 364.
6. Select the migration method to use, and plan for the hardware, software, and
storage space requirements for your server and environment. See Chapter 13,
“Planning the migration,” on page 365.

To prepare for the migration, see Chapter 14, “Preparing for the migration,” on
page 373.

To migrate the system, see Chapter 15, “Migrating the server database to the V7.1
server,” on page 385.

To prepare the system for operation, see Chapter 16, “Taking the first steps after
migration,” on page 425.

© Copyright IBM Corp. 2009, 2013 357

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Scenarios for migrating a server from an AIX, HP-UX, or Solaris

system to V7.1 on Linux
Several scenarios are available for migrating a Tivoli Storage Manager server from
V5 on an AIX, HP-UX, or Solaris operating system to V7.1 on a Linux x86_64
operating system. In addition to migrating the server, you must migrate data from
the V5 database to the V7.1 database.

Review the scenarios so that you can select the one that works best in your
hardware and software environment.

The following scenarios are available:

v Migration scenario 1: Media method, upgrade wizard
v Migration scenario 2: Media method, command line
v Migration scenario 3: Network method, upgrade wizard
v Migration scenario 4: Network method, command line

To migrate the server database, you can use one of the following methods:
Media method
You extract data from the original database to media, and then load the
data into the new database.
Network method
You simultaneously extract data from the original database and load the
data into the new database over a network connection.

For information about when to use the media method and when to use the
network method, see “Comparison of methods for moving data to the V7.1
database” on page 15.

To migrate the server, you can use the upgrade wizard or the command line:
Upgrade wizard
The wizard guides you through the process. You can avoid some steps that
are complex when done manually.
Command line
You issue administrative commands to upgrade the system manually.

Migration scenario 1: Media method, upgrade wizard

The following figure illustrates how to migrate a server by using the media
method and the upgrade wizard.

358 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migrate to V7 by using the media method

Migrate by using the upgrade wizard

2. Install the V7 server.

Configure new devices. Create

3. the user ID and directories for
the V7 server.

1. Preparation tasks. Upgrade the server

to V5.5.6 or later. Migrate data to tape
devices. Back up the database. Install
the upgrade utilities.

4. Start the upgrade wizard. Use the

wizard to configure the V7 server
and upgrade the V5 database.

5. Complete postmigration tasks.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager
server server

Figure 9. Migration scenario 1

For information about selecting an appropriate level for a V5 server before a

migration, see “Determining the appropriate level for a V5 server before an
upgrade” on page 36.

Migration scenario 2: Media method, command line

The following figure illustrates how to migrate a server by using the media
method and the command line.

Chapter 12. Migration overview 359

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migrate to V7 by using the media method

Migrate by using the command line

4. Install the V7 server.

5. Configure new devices. Create the user

ID and directories for the V7 server.

1. Preparation tasks. Upgrade the

server to V5.5.6 or later. Migrate data
to tape devices. Back up the
database. Install the upgrade utilities.

6. Create the server instance and database.

Run the db2icrt command and the
2. Prepare the database of the V5 server.
Run the DSMUPGRD PREPAREDB utility.
DSMSERV LOADFORMAT utility.

3. Extract the V5 database to external 7. Insert data from media into the new
database. Run the DSMSERV
media. Run the DSMUPGRD INSERTDB utility.
EXTRACTDB utility.

8. Configure the system for database backup.

9. Complete postmigration tasks.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager
server server

Figure 10. Migration scenario 2

For information about selecting an appropriate level for a V5 server before a

migration, see “Determining the appropriate level for a V5 server before an
upgrade” on page 36.

360 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migration scenario 3: Network method, upgrade wizard

The following figure illustrates how to migrate a server by using the network
method and the upgrade wizard.

Migrate to V7 by using the network method

Migrate by using the upgrade wizard

2. Install the V7 server.

3. Create the user ID and directories for

the V7 server.

1. Preparation tasks. Upgrade the

server to V5.5.6 or later. Migrate data
4. Start the upgrade wizard. Use the
wizard to configure the V7 server
to tape devices. Back up the and upgrade the V5 database.
database. Install the upgrade utilities.

5. Complete postmigration tasks.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager
server server

Figure 11. Migration scenario 3

For information about selecting an appropriate level for a V5 server before a

migration, see “Determining the appropriate level for a V5 server before an
upgrade” on page 36.

Migration scenario 4: Network method, command line

The following figure illustrates how to migrate a server by using the network
method and the command line.

Chapter 12. Migration overview 361

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migrate to V7 by using the network method

Migrate by using the command line

3. Install the V7 server.

4. Create the user ID and directories for the

V7 server.

1. Preparation tasks. Upgrade the server

to V5.5.6 or later. Migrate data to tape
devices. Back up the database. Install
the upgrade utilities.

5. Create the server instance and the

database. Run the db2icrt command and
the DSMSERV LOADFORMAT utility.

2. Prepare the V5 database. Run the

DSMUPGRD PREPAREDB utility.

6. Start the insertion for the new server. Run

the DSMSERV INSERTDB utility.

7. Start the extraction process. Run the

DSMUPGRD EXTRACTDB utility.
8. Configure the system for database backup.

9. Complete postmigration tasks.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager
server server

Figure 12. Migration scenario 4

For information about selecting an appropriate level for a V5 server before a

migration, see “Determining the appropriate level for a V5 server before an
upgrade” on page 36.

362 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

The migration process

You can use utilities and commands to facilitate the migration process. Restrictions
apply to the movement of data during the migration process and to device
availability afterward. During the migration process, you must protect client data
and the server.

Utilities and commands for data migration

Tivoli Storage Manager provides utilities and commands to help you move data
from a V5 system that is running on AIX, HP-UX, or Solaris to V7.1 on Linux
x86_64.

You can use the following utilities for data migration:

DSMUPGRD QUERYDB
The DSMUPGRD QUERYDB utility displays information about the database and
recovery log for a V5 server.
DSMUPGRD PREPAREDB
The DSMUPGRD PREPAREDB utility prepares the database for migration by
verifying that all premigration tasks are completed.
DSMUPGRD EXTRACTDB
The DSMUPGRD EXTRACTDB utility extracts data from the server database.
DSMSERV LOADFORMAT
The DSMSERV LOADFORMAT utility formats an empty database in preparation
for inserting extracted data into the empty database.
DSMSERV INSERTDB
The DSMSERV INSERTDB utility moves extracted data into a new database.

Many of the utilities and commands that are used for server upgrade are also used
for server migration. For more information, see Appendix B, “Utilities, scripts, and
commands for server upgrade and migration,” on page 521.

You can run commands to validate the database upgrade. For more information,
see “Sample commands to run for validation of the database upgrade” on page
546.

Data movement
As part of the migration process, you must move data from the source system to
the target system. As you plan the data movement, be aware of the preferred
method for migrating data and the restrictions that apply.

The most reliable way to move data to the new system is to migrate the data to a
non-GENERICTAPE tape device. The tape device must be accessible to both V5
and V7.1 systems.

The following restrictions apply to data movement:

v Raw logical volumes that are used on a V5 system will not be available on a
V7.1 system. Raw logical volumes cannot be used on Linux systems.
v Data that is stored on GENERICTAPE devices will not be available on a V7.1
system. GENERICTAPE devices cannot be used on Linux systems.
v Volumes that are stored on DISK and FILE devices might not be available on a
V7.1 system, depending on target system restrictions.

Chapter 12. Migration overview 363

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

v A device driver that is required to access a specific type of storage hardware

might not be compatible with a V7.1 system.
v Storage hardware that is attached to a V5 system might not be compatible with a
V7.1 system.

After the server migration, you are not required to maintain the data on tape
devices. You can move the data from tape devices to any DISK or FILE devices
that are compatible with the V7.1 system.

Device availability
Devices that are used on a V5 system might not be accessible to a V7.1 server
database.

If a device cannot be accessed, you must plan to migrate the data from the V5
device to a device that is accessible to a V7.1 server database.

For a list of devices and operating systems that you can use, see the following
websites:
AIX HPUX IBM Tivoli Storage Manager Supported Devices
Solaris
website for AIX, HP-UX, Solaris, and Windows systems (http://www.ibm.com/
software/sysmgmt/products/support/
IBM_TSM_Supported_Devices_for_AIXHPSUNWIN.html)
Linux IBM Tivoli Storage Manager Supported Devices website for Linux
systems (http://www.ibm.com/software/sysmgmt/products/support/
IBM_TSM_Supported_Devices_for_Linux.html)

Protection for client data and the server during the process
To protect client data and the server, you must complete several tasks during the
preparation phase. Plan to back up or migrate some types of data to
non-GENERICTAPE tape devices and back up the server database.

Backing up data is required to ensure that you can revert to the previous Tivoli
Storage Manager version if necessary.

For information about backup tasks, see the following topics:

v “Backing up or migrating data stored on DISK and FILE devices” on page 375
v “Migrating data that is stored on GENERICTAPE devices” on page 376
v “Moving backup sets that are stored on FILE devices” on page 376
v “Backing up the server database” on page 377
v “Creating a summary of database contents” on page 377

Tip: When you back up the database, make two copies to protect the backup from
media failures. Ensure that at least one full database backup is available onsite. If
you must restore the database, you can save time by having a backup that is
immediately available.

Do not uninstall the V5 server until you verify that the migration to V7.1 was
successful.

For more information about protecting the database, see “Database protection and
recovery” on page 5.

364 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 13. Planning the migration
Plan the migration carefully to minimize the time during which the Tivoli Storage
Manager system will be unavailable. During the migration, you must install the
new software and move the contents of the V5 server database into the new V7.1
database.

About this task

Tivoli Storage Manager V5 servers can be upgraded directly to V7.1. However,

Tivoli Storage Manager V7.1 servers cannot be used with V5 clients or with other
servers in the system that are at V5. Unless all V5 clients and V5 servers can be
upgraded at the same time, consider upgrading the server to a level that can be
used with V5 clients and V5 servers. Then, upgrade all servers and clients to V7.1
when possible. For information about the levels of the Tivoli Storage Manager
server that can be used with V5 clients and V5 servers, see the following technotes:
IBM Tivoli Storage Manager Server-Client Compatibility and Upgrade
Considerations
(http://www.ibm.com/support/docview.wss?uid=swg21053218)
Storage-agent and library-client compatibility with the IBM Tivoli Storage
Manager server
(http://www.ibm.com/support/docview.wss?uid=swg21302789)

When you move data from a V5 server database to a V7.1 database, a large
amount of system processing capacity is used. The move also requires a large
amount of I/O activity.

In your planning, consider testing the migration process on nonproduction

systems. Testing provides information about how long the migration of the server
database will take, which helps you plan for the time that the server will be
unavailable. Some databases might take much longer than others to migrate.

Testing also gives you more information about the size of the new database
compared to the original, giving you more precise information about database
storage needs.

If you have multiple servers, consider migrating one server first to determine how
the migration process will work for your data. Use the results of the first migration
process to plan for migrating the remaining servers.

Procedure

To plan the migration, complete the following steps:

1. Select a migration scenario. For more information, see “Scenarios for migrating
a server from an AIX, HP-UX, or Solaris system to V7.1 on Linux” on page 358.
2. Review the hardware and software requirements. For more information, see
“Hardware and software requirements for the V5 and V7.1 servers” on page
366.
3. Complete the following tasks:
a. “Estimating database and recovery log requirements” on page 366
b. “Estimating the time required for migration” on page 367

© Copyright IBM Corp. 2009, 2013 365

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

c. “Planning data movement” on page 368

d. “Planning for upgrading multiple servers and components” on page 368
e. “Preparing for operational changes” on page 368
f. “Estimating storage and device requirements” on page 369
4. To help you plan the migration, review the following information:
v “Performance tips for the V5 database extraction process” on page 369
v “Performance tips for inserting data into the V7.1 database” on page 370
v “Reference information for planning the migration” on page 371
5. Optional: Test the migration process in a limited or nonproduction
environment.

Hardware and software requirements for the V5 and V7.1 servers

Review the hardware and software requirements for the V5 and V7.1 servers.

During the migration process, you must upgrade the V5 server to V5.5.6 or later.
To optimize the migration process and avert potential issues, consider upgrading
the V5 server to the latest available level and installing the latest interim fix for
that level. Follow the guidelines in “Determining the appropriate level for a V5
server before an upgrade” on page 36. For information about the V5.5 server, see
the Tivoli Storage Manager V5.5 Information Center at http://
publib.boulder.ibm.com/infocenter/tivihelp/v1r1.

For information about hardware and software requirements for a V7.1 server on
Linux x86_64, see “Server requirements for Linux on x86_64 systems” on page 26.
For the latest information about hardware and software requirements, see the
Tivoli Storage Manager Supported Operating Systems technote
(http://www.ibm.com/support/docview.wss?uid=swg21243309).

A manual tape drive or a tape library with at least one tape drive must be
installed. The tape device must be supported on both the source and target
operating systems.

Estimating database and recovery log requirements

Estimate the space requirements for the migration process, and the space
requirements for the server databases and recovery log for the V7.1 server. The
space requirements for a cross-platform migration from V5 to V7.1 are similar to
the space requirements for an upgrade from V5 to V7.1 on the same operating
system.

Procedure
1. Estimate the space requirements for the V5 server system. For details, see
“Space requirements for the V5 server system” on page 37.
2. Estimate the space requirements for the V7.1 server system. For details, see
“Space requirements for the V7 server system” on page 38.
3. Estimate the total space for the migration process and the V7.1 server. For
details, see “Estimating total space requirements for the upgrade process and
upgraded server” on page 39.
4. Optional: Use a worksheet to plan the amount and location of space for the
V7.1 server. For details, see “Worksheet for planning space for the V7.1 server”
on page 42.

366 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Estimating the time required for migration

The V5 server is not available for use during migration operations. To help plan
for the amount of time that the server will be unavailable, estimate the migration
time. The time that is required to complete the migration of a V5 server depends
on several factors.

About this task

The following factors can affect the migration time:

v The size of the database that is being migrated.
v The number and speed of system processors.
v The configuration of storage devices. If new hardware is being introduced, time
is required to define the new devices to the server, test the configuration, and
adjust storage pools.
v The method for moving the data from the V5 database to the V7 database:
media or network. The network method for data movement overlaps the
extraction time with the insertion time. Using the network method might help
reduce the total time that is required for the migration because of the overlap.
v The type of workload that the server has handled. A workload that consists of
large numbers of small files, or files with long file names, can cause a relatively
longer migration time.

Procedure

When you estimate the time it might take to migrate the system, consider the data
that is available for upgrade operations from Tivoli Storage Manager V5 to V6 on
the same operating system. This information might help you estimate the time that
is required for a cross-platform migration.

For example, in benchmark environments in IBM labs, upgrade operations

achieved 5 - 10 GB per hour by using the network method. This rate is based on
the amount of space that is used by the V5 database, not the allocated space for
the database. Your environment might produce different results. Results are
dependent on system configuration. If you use the media method, the rate is
decreased.

Estimate the time that is required to migrate your system based on the amount of
data in the server database.

Results

Your estimate might be higher than the actual time that is required. Because of the
way that databases are structured, the amount of data that the extraction utility
extracts might be much less than the total amount of space that is used by the
database.

What to do next

Test migration operations for Tivoli Storage Manager servers that are used by
essential systems.

Chapter 13. Planning the migration 367

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Planning data movement

Any data that is stored on DISK or FILE devices must be migrated or backed up to
non-GENERICTAPE tape devices before the migration begins. Data that is stored
on GENERICTAPE devices must be migrated to non-GENERICTAPE tape devices.

About this task

As you plan the data movement, ensure that you have tape volumes available for
backing up and storing data:
v At a minimum, tape volumes must be available to back up the primary storage
pool.
v The tape devices must be accessible to both the V5 and the V7 system.
v The tape devices must be usable on both the V5 and the V7 system. For
information about the devices that can be used, see the website for your
operating system:
– AIX HPUX Solaris Supported Devices for AIX, HP-UX, Solaris,
and Windows systems (http://www.ibm.com/software/sysmgmt/products/
support/IBM_TSM_Supported_Devices_for_AIXHPSUNWIN.html)
– Linux Supported Devices for Linux systems (http://www.ibm.com/
software/sysmgmt/products/support/
IBM_TSM_Supported_Devices_for_Linux.html)
v To optimize the process, tape volumes should be available to create a second,
onsite backup of the primary storage pool. By creating one backup storage pool
offsite and another onsite, you fulfill disaster recovery requirements for offsite
storage. At the same time, volumes from the second pool are available onsite to
restore data immediately after migration.

Planning for upgrading multiple servers and components

If your environment includes multiple servers and storage agents, evaluate the
compatibility of the current versions with an upgraded V7.1 server. Plan to
upgrade one server first in a test environment. Then, stage the upgrade of more
servers and storage agents.

Before you begin

For information about storage-agent and library client compatibility with Tivoli
Storage Manager V7.1 servers, see Technote 1302789 (http://www.ibm.com/
support/docview.wss?uid=swg21302789).

Preparing for operational changes

As you migrate your system from V5 to V7.1, the method for backing up and
monitoring the server database changes.

Procedure

Verify the operating procedures, scripts, and administrative schedules that you use
for server operations:
v Plan to back up the server database regularly by using administrative schedules,
a maintenance script, or your own scripts. Back up the server database at least
once per day. For best results, consider scheduling more frequent backups for

368 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

the V7.1 database than you did for the V5 database. To ensure that archive log
space is pruned, consider scheduling more full database backups and fewer
incremental backups.
For more information about scheduling database backups, see the section about
backing up the database in the Administrator's Guide.
v Understand how database and recovery log space is used, and how monitoring
will change.
v Verify scripts and administrative schedules. Starting with the Tivoli Storage
Manager V7 server, new commands were added, some commands were
changed, and some commands that were no longer needed were deleted. These
changes will affect your automated operations. For information about new and
changed commands, see “Command and option changes” on page 51.
v Verify the SELECT commands that you use regularly. Some parameters and
syntax that were previously allowed are not accepted by the database manager
program. For information about SELECT command updates, see “Changes to the
SELECT command” on page 68. To resolve problems that are related to SELECT
commands, see Technote 1380830 (http://www.ibm.com/support/
docview.wss?uid=swg21380830).
v If you use products from independent software vendors to interface with the
server, ensure that the products are compatible with the V7.1 server.

What to do next

To use the new functions that are available in Tivoli Storage Manager V7.1, install
the latest version of the IBM Tivoli Storage Manager Operations Center.

Estimating storage and device requirements

Estimate the amount of space that will be required for data storage on the new
Tivoli Storage Manager V7.1 system. Plan the devices to be used for storage.

Procedure

To plan for storage and devices, complete the following steps:

1. Estimate the storage requirements for the new Tivoli Storage Manager V7.1
system. For details, see the section that describes estimating space needs for
sequential-access storage pools in the Administrator's Guide.
2. Plan the device requirements for the new Tivoli Storage Manager V7.1 system.
For instructions, see the section about configuring and managing storage
devices in the Administrator's Guide.

Performance tips for the V5 database extraction process

Review the performance tips for the V5 database extraction process so that you can
minimize the time that is required for the migration. In this way, you can reduce
the time that the Tivoli Storage Manager server is unavailable.

The speed of the extraction process is typically limited by the speed of I/O to the
destination for the extracted data. The length of time that the process runs also
depends on the size of the database. The time is approximately as long as the time
required for a full backup of the database.

Do not reorganize the Tivoli Storage Manager V5 database before the migration.
The extraction process achieves faster throughput when the source database does

Chapter 13. Planning the migration 369

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

not contain long sequences of pages that are allocated to a single database table.
Follow this guideline for both the media method and the network method.

The following performance tips depend on the method that you choose for moving
the data from the V5 database:
Media method
If you are using the media method, and are extracting the data to tape, use
a high-speed tape device. For example, select a device with a transfer rate
of at least 1000 MB per second.
Network method
If you are using the network method, use a high-speed link. If you are
migrating a database that is larger than 2 - 3 GB, use at least a 1-gigabit
(Gb) Ethernet network.

Performance tips for inserting data into the V7.1 database

The process for inserting the V5 extracted data into the V7.1 database is the
longest-running part of a migration process, and is the most sensitive to the
configuration of the system.

On a system that meets only the minimum requirements, the insertion process
runs, but performance might be slow. For better performance, set up the system as
described in the following tips:
Processors
The insertion process is designed to use multiple processors or cores. The
insertion process typically performs better on a system with a relatively
small number of fast processors. If the system has many slow processors,
you might experience reduced performance levels.
Disk storage
The insertion process is designed to use high-bandwidth disk storage
subsystems. The speed of the process is dependent on the disk storage that
is used.
For best performance, use multiple LUNs that map to multiple
independent disks, or that map to redundant arrays of independent disks
(RAIDs) with a large stripe size (for example, 128 KB). Use a different file
system on each LUN.
The following table shows an example of good usage of LUNs.
Table 61. Example of LUN usage
LUN Usage
1 Active log
2 Archive log
3, 4, 5 Database directories
6 Extracted V5 database, which is required only if the media method
is used to extract the V5 database to a sequential device class

If the disk storage is supplied by a virtualization device (high-end storage

controller, or a SAN virtualization device), ensure that none of the virtual
LUNs are on the same physical disk drive. Ensure that the directories are
on different physical disk drives within the virtualization device.

370 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Reference information for planning the migration

Information about new, changed, and deleted administrative commands, server
options, and server messages can help you plan the migration.

For more information, see “Reference information for planning” on page 51.

Chapter 13. Planning the migration 371

372 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 14. Preparing for the migration
To prepare a system for a server migration from V5 to V7.1, you must complete
several steps. Ensure that you verify the prerequisites for the migration and
upgrade the V5 server to V5.5.6 or later. Then, prepare data that is stored on DISK,
FILE, and GENERICTAPE devices for migration and back up the server database.

Preparing space for the migration process

Verify that you have sufficient space on the V7.1 system for the migration process.

Procedure
1. Verify that the system has the amount of space that was estimated in the
planning step. If you used a worksheet to plan the space requirements, refer to
the worksheet. For more information, see “Worksheet for planning space for the
V7.1 server” on page 42.
2. If you plan to extract the original server database to media for later insertion
into the new database, ensure that you have enough storage space. Storage
space is required for the database and the manifest file that the extraction
process creates. Complete the following steps:
a. Identify the device class to which you will extract the original database. The
definition must exist in the server database, not only in the device
configuration file.
The device class must be sequential, and the device class type must be tape.
The tape device must be compatible with the V5 and the V7.1 system.
Define a new device class if necessary.
b. Ensure that space or volumes are available in the selected device class. The
amount of space that you need is about the same as the current size of the
original database.
Ensure that the instance user ID that you create for the upgraded server has
access permission to the location of the extracted data.
c. Verify that the access permissions are correct for the location that you plan
to specify for the manifest file.
When the data is later inserted into the V7.1 database, the instance user ID
that you use for the upgraded server must have access permission for the
manifest file.
The manifest file might be less than 1 KB. However, for a complex
configuration, it might exceed 1 KB.

Upgrading the V5 server to V5.5.6 or later

Upgrade the V5 server to V5.5.6 or later so that you can use the utilities that help
to prepare the system for the migration.

Before you begin

The Tivoli Storage Manager server must not be running during installation of the
V5.5.6 or later fix pack.

© Copyright IBM Corp. 2009, 2013 373

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

To install a fix pack to the server, you must have the Tivoli Storage Manager
license package installed. The license package is provided when you purchase a
base release.

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

Procedure
1. Obtain the package file for the V5.5.6 or later fix pack from the Tivoli Storage
Manager FTP downloads site at ftp://public.dhe.ibm.com/storage/tivoli-
storage-management/maintenance/server/v5r5/MVS/LATEST.
2. For installation information, review the README.txt file, which is available in
the package file.
3. Install the fix pack.

What to do next

For more information about the Tivoli Storage Manager server V5.5 release, see the
Tivoli Storage Manager V5.5 information center at http://publib.boulder.ibm.com/
infocenter/tivihelp/v1r1/index.jsp.

Disabling sessions
In preparation for the migration, prevent activity on the server by disabling new
sessions. Cancel any existing sessions.

About this task

The commands in the following procedure are Tivoli Storage Manager
administrative commands.

Procedure

To disable sessions, complete the following steps:

1. Prevent all clients, storage agents, and other servers from starting new sessions
with the server. Use the commands:
disable sessions client
disable sessions server
For more information about the DISABLE SESSIONS command and other Tivoli
Storage Manager administrative commands, see the Administrator's Reference.
2. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the commands:
query process
cancel process process_number

where process_number specifies the number of the process. Allow time for the
processes to be stopped. Some processes, such as storage pool migration, might
require considerable time.
3. Verify whether sessions exist, and notify the users that the server will be
stopped. To detect existing sessions, use the command:

374 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

query session
4. Cancel sessions that are still running. Use the command:
cancel session all

Backing up or migrating data stored on DISK and FILE devices

Before you migrate the server, ensure that all data that is stored on DISK or FILE
devices is backed up or migrated to non-GENERICTAPE tape devices. This step is
required because data that is stored on DISK and FILE devices cannot be migrated
as part of the cross-platform migration.

Procedure
1. Create a copy storage pool for a tape device by issuing the DEFINE STGPOOL
command. For example, to create a copy storage pool named ltocopypool,
which is assigned to the LTOCLASS device class, issue the following command:
define stgpool ltocopypool ltoclass pooltype=copy
For more information about the DEFINE STGPOOL command and other Tivoli
Storage Manager administrative commands, see the Administrator's Reference.
2. Back up a primary storage pool on a DISK or FILE device by issuing the BACKUP
STGPOOL command. For example, to back up a primary storage pool named
primary_pool to a copy storage pool named ltocopypool, issue the following
command:
backup stgpool primary_pool ltocopypool
3. Vary any disk-based primary storage pool volumes offline by using the VARY
command. For example, to vary a storage pool named primary_disk_pool
offline, issue the following command:
vary offline primary_disk_pool
4. To mark the original volumes as destroyed, change the access mode of each
volume of primary storage pools to destroyed. Use the UPDATE VOLUME
command. For example, if the name of the primary storage pool is
primary_pool, mark the volumes in the pool as destroyed by issuing the
following command:
update volume * wherestgpool=primary_pool access=destroyed

Results
If you prefer to migrate the data, you can use the MIGRATE STGPOOL command, the
MOVE DATA command, or the MOVE NODEDATA command, depending on where the
data is stored and how you plan to move it.

What to do next

After the server is migrated to V7.1, you can move the data from tape back to a
storage pool that has faster access to data. For example, you can migrate the data
to a random-access storage pool that uses a DISK device class. You can also
migrate or restore the data to a storage pool that uses a FILE device class.

Chapter 14. Preparing for the migration 375

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migrating data that is stored on GENERICTAPE devices

Before you migrate the server, migrate all data that is stored on GENERICTAPE
devices to non-GENERICTAPE tape devices. This step is required because data that
is stored on GENERICTAPE devices cannot be migrated as part of the
cross-platform migration.

Procedure
1. Create a primary sequential-access storage pool on a non-GENERICTAPE tape
device by issuing the DEFINE STGPOOL command.
For example, to create a storage pool named ltopool that is assigned to the
LTOCLASS device class, issue the following command:
define stgpool ltopool ltoclass
For more information about creating storage pools, see the DEFINE STGPOOL
command in the Administrator's Reference.
2. To provide a location for the files that will be migrated, set up the next primary
storage pool. Use the UPDATE STGPOOL command.
For example, to update a primary storage pool named gentapepool by adding a
next storage pool named ltopool with a high migration threshold of 100, issue
the following command:
update stgpool gentapepool nextstgpool=ltopool highmig=100
For more information about setting up the next primary storage pool, see the
UPDATE STGPOOL command in the Administrator's Reference.
3. Migrate the data from the GENERICTAPE storage pool to the
non-GENERICTAPE storage pool by using the MIGRATE STGPOOL command. For
example, to migrate a storage pool named gentapepool to the next storage pool
and specify a low migration threshold of 0, issue the following command:
migrate stgpool gentapepool lowmig=0
For more information about migrating storage pools, see the section that
describes how to move data in the Administrator's Guide. Also, see the MIGRATE
STGPOOL command in the Administrator's Reference.

Moving backup sets that are stored on FILE devices

Before you migrate the server, move any backup sets that are stored on FILE
devices to the system where you plan to install the V7.1 server.

Procedure
1. Obtain a detailed list of the volumes that are associated with a backup set by
issuing the QUERY BACKUPSET command:
query backupset f=d
For more information about the QUERY BACKUPSET command and other Tivoli
Storage Manager administrative commands, see the Administrator's Reference.
2. Review the output to determine which backup sets are stored on FILE devices.
3. Copy the volumes that are associated with backup sets on FILE devices to the
target system. For example, copy the volumes to an FTP server on the target
system. The volumes must be copied to a location where they can be accessed
by the server instance user ID. If possible, retain the file structure that was
used on the source system. If it is not possible to retain the file structure from
the source system, copy the volumes to any location on the target system.

376 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Remember: If you cannot retain the file structure that was used on the source
system, you must complete more steps after the server migration. Use the
DELETE BACKUPSET command to remove the previous volume entries from the
database, and then the DEFINE BACKUPSET command to re-create the backup sets
by using the volumes in their new location.

Backing up the server database

Immediately before you migrate the Tivoli Storage Manager server, back up the
server database to a non-GENERICTAPE tape device.

Procedure

Run a snapshot backup, which provides a full backup of the database without
interrupting any scheduled backups. Use the following command:
backup db type=dbsnapshot devclass=device_class_name

where type specifies the type of database backup and device_class_name specifies the
name of the device class. The device class that you specify must exist and have
volumes that are available to it.

For example, to back up a database by using scratch volumes to a device that

belongs to the TAPECLASS device class, issue the command:
backup db type=dbsnapshot devclass=tapeclass

To use specific volumes instead of scratch volumes, specify the volume names in
the command.

Tip: To protect the backup from media failures, make two copies of the backup.
Ensure that at least one full database backup is available onsite. If you must restore
the original database, having an onsite backup saves time because it is
immediately available.

For more information about backing up databases, see the BACKUP DB command in
the Administrator's Reference.

Creating a summary of database contents

Create a summary of the contents of the original database. After the upgrade, you
can use the same commands to compare the results and to confirm that the
database contents are intact.

Procedure

Run commands that give a summary of information about your database contents.
For example, issue commands that summarize the file spaces that are being
protected, and save the results. For a list of commands, see “Sample commands to
run for validation of the database upgrade” on page 546.

Chapter 14. Preparing for the migration 377

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Modifying the server to prevent potential issues

To prevent potential issues during and after the migration, modify the V5 server.

Before you begin

Before you modify the server, review the steps for reverting to the earlier version
of the server in the section, “Reverting from V7.1 to the previous V5 server
version” on page 435.

Procedure
1. To prevent an issue with UNIX System Services file spaces, from a Tivoli
Storage Manager administrative command line, issue the command:
convert ussfilespace

This command fixes a problem that might exist in older Tivoli Storage Manager
databases. If the problem does not exist in your database, the command is
completed and you might see error ANR2034E. This error can be ignored. For
more information, see Technote 1408895 (http://www.ibm.com/support/
docview.wss?uid=swg21408895). If the problem exists in your database, the
command might take some time to run.

Important: If you do not run this command, the DSMUPGRD PREPAREDB utility
might fail. You must then restart the V5 server and run the CONVERT
USSFILESPACE command before you continue the upgrade process.
2. Make the following adjustments to settings on your server and clients. These
adjustments must be done so that you can revert your system to the original
server after the migration, if a problem occurs.
a. For each sequential-access storage pool on tape, use the UPDATE STGPOOL
command to set the REUSEDELAY parameter. Set the parameter to the number
of days during which you want to be able to revert to the original server, if
necessary.
For example, if you want to be able to revert to the original server for up to
30 days after the migration, set the REUSEDELAY parameter to 31 days:
update stgpool sequential_access_storage_pool reusedelay=31

where sequential_access_storage_pool specifies the name of the storage pool.

For more information about the UPDATE STGPOOL command and other Tivoli
Storage Manager administrative commands, see the Administrator's Reference.
b. For each copy storage pool on tape, use the QUERY STGPOOL command to
determine the value of the RECLAIM parameter. Note the value for future
reference. If you must revert to the V5 server at any time during the
migration process, it is useful to know the value of the RECLAIM parameter
so that you can restore the setting. Issue the following command:
query stgpool sequential_access_storage_pool format=detailed

where sequential_access_storage_pool specifies the name of the copy storage

pool. In the system output, the value of the RECLAIM parameter can be found
in the Reclamation Threshold field.
c. For each copy storage pool on tape, use the UPDATE STGPOOL command to set
the RECLAIM parameter to 100, meaning 100%. For example, issue the
following command:
update stgpool copy_storage_pool reclaim=100

378 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

where copy_storage_pool specifies the name of the copy storage pool.

d. For all tape volumes that were used by the V5 server, specify the read-only
access mode. Issue the following administrative command:
update volume tape_volume access=readonly

where tape_volume specifies the name of the tape volume.

e. For clients that play an essential role in your system, verify that the value
for the schedlogretention client option is set to retain the client schedule
log for a sufficient time.
The client schedule log can be useful if you must revert the system to the
original server. If the retention period for the schedule log is too short, the
schedule log information might be deleted too soon.
For example, to prune the log every 45 days and save the log entries, add
the following option:
schedlogretention 45 S

where 45 specifies the number of days and S specifies that the log entries
will be saved.
Add the schedlogretention client option to the dsm.sys file within a server
stanza.
For more information about pruning the log, see the schedlogretention
client option in the Backup-Archive Clients Installation and User's Guide.

Stopping the server before the migration

On the Tivoli Storage Manager V5.5.6 or later server, stop all server processes.
Then, unmount any tapes that are mounted and stop the server.

Procedure

Use Tivoli Storage Manager administrative commands to stop the server:

1. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the following commands:
query process
cancel process process_number

Allow time for the processes to be stopped. Some processes, such as storage
pool migration, might take some time to stop.
For more information about the QUERY PROCESS and CANCEL PROCESS commands
and other Tivoli Storage Manager administrative commands, see the
Administrator's Reference.
2. After all sessions and processes are stopped, determine whether any tapes are
mounted. Unmount any tapes that are mounted. Use the following commands:
query mount
dismount volume volume_name
3. Stop the server. Use the following command:
halt

Chapter 14. Preparing for the migration 379

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Installing the upgrade utilities

You must install the upgrade utilities on the system where the V5 server is located.
The upgrade utilities prepare and extract data from a V5 server database for
insertion into an empty V7 server database.

Procedure

Use the procedure for your operating system:

v AIX “Installing the upgrade utilities on AIX systems”
v HPUX “Installing the upgrade utilities on HP-UX systems” on page 381
v Solaris “Installing the upgrade utilities on Oracle Solaris systems” on page
382

Installing the upgrade utilities on AIX systems

AIX

You must install the V5.5.6 or later upgrade utilities on the system that has the
original server and its database. The package to install is available for download
from the FTP downloads site.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the AIX directory. From that directory, open the V5.5.6 or later
directory. The level must be the same as or later than the level of the V5
server that you are upgrading.
c. Download the package to a convenient location on the server system. The
name of the package has the following form:
5.5.x.x-TIV-TSMUPG-AIX.tar.gz
The numbers at the beginning of the package name identify the release
level of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Ensure that the system has the following file sets installed:
xlC.rte 8.0.0.5, or later
gsksa.rte 7.0.4.11
You can use the following commands to check for these file sets:
lslpp -L xlC.rte

lslpp -L gsksa.rte

If needed, you can obtain the gsksa.rte file set from any of the regular V5.5
maintenance packages for the AIX server. The maintenance packages are
available on the FTP downloads site: ftp://public.dhe.ibm.com/storage/tivoli-
storage-management/maintenance/server/v5r5/AIX/

380 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

4. Extract the contents of the upgrade utilities package. If you downloaded a

language package, also extract the contents of that package.
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Access the System Management Interface Tool (SMIT).
a. Enter smitty install_update
b. Select Install and Update Software > Install and Update from ALL
Available Software.
7. Select the INPUT device. Specify the directory location of the upgrade utilities
package on the system.
8. Select Software to Install. Press F4 or Esc+4 for the list of available file sets in
the directory.
9. Select the file sets for the upgrade utilities, the device driver, and optionally
the language package. The file set for the upgrade utilities is
tivoli.tsmupg.server. Optional language packages include messages for
languages other than US English.
10. Set COMMIT software updates to Yes. Press F4 or Esc+4.
11. Set SAVE replaced files to No.
12. Ensure that the default settings for the options in the window for all the
selected file sets show success.
13. Press Enter, and respond to the ARE YOU SURE? question by pressing Enter
again. The installation begins.
14. When the installation is complete, exit the SMIT program.
15. Optional: If you installed a language package, ensure that the locale
environment variable is set to use it. Enter the following command to set the
locale environment variable for messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.

Installing the upgrade utilities on HP-UX systems

HPUX

You must install the V5.5.6 or later upgrade utilities on the system that has the
original server and its database. The package to install is available for download
from the FTP downloads site.

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the HP-UX directory. From that directory, open the V5.5.6 or later
directory. The level must be the same as or later than the level of the V5
server that you are upgrading.

Chapter 14. Preparing for the migration 381

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

c. Download the package to a convenient location on the server system. The

name of the package has the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.gz
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
gzip -dc package_name.tar.gz | tar -xvf -
4. Navigate to the directory that corresponds to the processor architecture of the
operating system.
5. Install the upgrade utilities and the device driver. Use the source argument (-s)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
swinstall -s /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin.

6. Optional: Install the language package.
a. Extract the contents of the package.
gzip -d package_name.img.gz
b. Install the package. For example, if the directory is /tmp/TSM, issue the
command:
swinstall -s /tmp/TSM/package_name.img package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.

Installing the upgrade utilities on Oracle Solaris systems

Solaris

You must install the V5.5.6 or later upgrade utilities on the system that has the
original server and its database. The package to install is available for download
from the FTP downloads site.

About this task

Restriction: Do not install the utilities in the installation directory for the original
server that must be upgraded. Install the utilities package in its own directory.

382 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Procedure
1. Obtain the upgrade utilities package from the FTP downloads site.
a. Go to ftp://public.dhe.ibm.com/storage/tivoli-storage-management/
maintenance/server-upgrade/v5r5/
b. Navigate to the Solaris directory. From that directory, open the V5.5.6 or
later directory. The level must be the same as or later than the level of the
V5 server that you are upgrading.
c. Download the package to a convenient location on the server system. The
name of the package has the following form:
5.5.x.x-TIV-TSMUPG-platform.tar.Z
The numbers at the beginning of the package name identify the release level
of the upgrade utilities package.
d. Optional: To install messages in a language other than English, open the
LANG directory, and download a language package. Translated messages are
available in the usual set of languages for a V5 server.
2. Log in with the root user ID.
3. Change to the directory where the upgrade utilities package was downloaded.
4. Extract the contents of the upgrade utilities package. For example, from the
directory where you saved the download package, issue the command:
uncompress -c package_name.tar.Z | tar -xvf -
5. Navigate to the directory that corresponds to the processor architecture of the
operating system.
6. Install the upgrade utilities and the device driver. Use the source argument (-d)
to specify the directory where the package was extracted. For example, if the
directory is /tmp/TSM, issue the command:
pkgadd -d . /tmp/TSM package_name

The utilities are installed in the directory /opt/tivoli/tsm/upgrade/bin by

default.
7. Optional: Install the language package.
a. Extract the contents of the downloaded package.
uncompress package_name.pkg.Z
b. Install the package for the language that you want to use. Use the source
argument (-d) to specify the directory where the package was extracted. For
example, if the directory is /tmp/TSM, issue the command:
pkgadd -d /tmp/TSM package_name.pkg package_name
c. Enter the following command to set the locale environment variable for
messages:
export LC_MESSAGES=xxxx

where xxxx is the locale that you want to use. For example, use it_IT for
Italian. The upgrade utilities run with the locale that you specify if the
following statements are true:
v The locale is installed on the system.
v The upgrade utilities support the locale.
v The language package that you installed for the upgrade utilities matches
the locale.

Chapter 14. Preparing for the migration 383

384 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 15. Migrating the server database to the V7.1 server
Migrate the server database by using the scenario that works best for your
hardware and software environment. The original server cannot be running while
the data is being extracted from the server database.

Before you begin

For an overview of migration scenarios, see “Scenarios for migrating a server from
an AIX, HP-UX, or Solaris system to V7.1 on Linux” on page 358.

About this task

Follow the instructions for your selected scenario:

v “Migration scenario 1: Using the media method and the upgrade wizard”
v “Migration scenario 2: Using the media method and the command line” on page
391
v “Migration scenario 3: Using the network method and the upgrade wizard” on
page 406
v “Migration scenario 4: Using the network method and the command line” on
page 412

Migration scenario 1: Using the media method and the upgrade wizard
Use this procedure if you are upgrading the server by using the media method
and the upgrade wizard. By applying the media method, you extract data from the
original database to media, and then load the data into the new database. By using
the wizard, you simplify the configuration process.

Procedure

To migrate the system by using Migration scenario 1, complete the following steps:
1. Ensure that you have completed the planning tasks. See Chapter 13, “Planning
the migration,” on page 365.
2. Ensure that you have completed the preparation tasks. See Chapter 14,
“Preparing for the migration,” on page 373.
3. Complete the tasks that are described in the following topics:
a. “Migration scenario 1: Installing the V7.1 server” on page 386
b. “Migration scenario 1: Setting up devices” on page 388
c. “Migration scenario 1: Creating the user ID and directories for the server
instance” on page 389
d. “Migration scenario 1: Running the upgrade wizard” on page 390

What to do next

After you complete the planning, preparation, and migration steps, complete the
post migration tasks. See Chapter 16, “Taking the first steps after migration,” on
page 425.

© Copyright IBM Corp. 2009, 2013 385

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migration scenario 1: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

About this task

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

Tip: The database (DB2) and the Global Security Kit are automatically installed
when you select the Tivoli Storage Manager server component.
For more information about storage agents, see the Storage Agent User's Guide.

Procedure
1. Log in to the system by using the root user ID.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
a. Verify that you have enough space to store the installation files when they
are extracted from the product package. For space requirements, see the
download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035122

386 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

v Tivoli Storage Manager Extended Edition: http://www.ibm.com/

support/docview.wss?uid=swg24035635
v System Storage Archive Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The path must
contain no more than 128 characters. Ensure that you extract the
installation files to an empty directory. Do not extract to a directory that
contains previously extracted files, or any other files. Also, ensure that you
have executable permission for the package file.
c. If necessary, change the file permissions by issuing the following
command:
chmod a+x package_name.bin
where package_name is like the following example:
7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin

In the examples, 7.1.0.000 represents the product release level. The package
is large, so the download takes some time.
d. Extract the installation files by issuing the following command:
./package_name.bin
where package_name is like the following example:
7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin

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

4. If you plan to install the server by using the graphical interface of the IBM
Installation Manager, verify that the operating system is set to the language
that you require. By default, the language of the operating system is the
language of the installation wizard.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
5. If you use the installation wizard, complete the following steps to begin the
installation:

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

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

Chapter 15. Migrating the server database to the V7.1 server 387
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

6. If you install the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
7. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
8. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
9. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
10. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.
11. To prevent server failures during interaction with DB2, tune the kernel
parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
12. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
13. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.

Migration scenario 1: Setting up devices

Set up the storage devices that you plan to use with the V7.1 server. Ensure that
you set access permissions correctly for users and groups.

Procedure

To set up storage devices, follow these instructions:

v If the devices that you plan to use are controlled by the IBM device driver,
complete the following steps:
1. Install the IBM device driver and configure devices. Follow the instructions
in the IBM Tape Device Drivers Installation and User's Guide at
http://www.ibm.com/support/docview.wss?uid=ssg1S7002972.
2. To set access permissions, complete one of the following actions:
– If the system is dedicated to Tivoli Storage Manager and only the Tivoli
Storage Manager administrator has access, make the device special files
readable and writable to all users. Issue the following command:
chmod a+rw /dev/IBMtapex

where x is a number that is assigned to a device. For example, a device

drive can be named /dev/IBMtape0, where 0 is the device number.
– Restrict access to a group by creating a group and adding each instance
user ID for Tivoli Storage Manager to that group. Then, change the
388 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

ownership of the device special files to belong to the group, and make the
device special files readable and writable to the group. Issue the following
command:
chmod g+rw /dev/IBMtapex

where x is a number that is assigned to a device.

v If the devices that you plan to use are controlled by the Tivoli Storage Manager
device driver, complete the following steps:
1. Log in as the root user.
2. Grant read and write access.
– To grant read and write access to all users, issue the following command:
/opt/tivoli/tsm/devices/bin/autoconf -a
– To grant read and write access to only the group, issue the following
command:
/opt/tivoli/tsm/devices/bin/autoconf -g
For more information about setting up devices, see the section about attaching
devices to the server in the Administrator's Guide.

Migration scenario 1: Creating the user ID and directories for

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

Before you begin

To review the information about planning space for the server, see “Estimating
database and recovery log requirements” on page 366.

Procedure
1. Create a user ID and group that will be the owner of the Tivoli Storage
Manager server instance. You will use this user ID when you create the server
instance in a later step.

Restriction: In the user ID, only lowercase letters (a-z), numerals (0-9), and the
underscore character (_) can be used. The user ID and group name must
comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a numeral.
v The user ID and group name cannot be user, admin, guest, public, local, or
any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The following
examples show how to create this user ID and group by using operating
system commands:
# groupadd tsmsrvrs
# useradd -d /home/tsminst1 -m -g tsmsrvrs -s /bin/bash tsminst1
# passwd tsminst1
2. Log out and log in to your system again by using the new user ID and
password. Use an interactive login program, such as telnet, so that you are
prompted for the password and can change it if necessary.
3. If a configuration profile does not exist for the user ID, create the file. For
example, create a .profile file if you are using the Korn shell (ksh).

Chapter 15. Migrating the server database to the V7.1 server 389
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

4. Ensure that you are logged in with the user ID that you created. Then, create
the directories that the server requires.
Unique, empty directories are required for each item that is shown in the
following table. Create the database directories, the active log directory, and the
archive log directory on different physical volumes. For space requirements, see
“Worksheet for planning space for the V7.1 server” on page 42.
Table 62. Worksheet for creating required directories
Example commands for
Item creating the directories Your directories
The instance directory mkdir /home/user_ID/tsminst1
for the server, which will
contain files for this
server instance, including
the server options file
The database directories mkdir /home/user_ID/tsmdb001
mkdir /home/user_ID/tsmdb002
mkdir /home/user_ID/tsmdb003
mkdir /home/user_ID/tsmdb004
Active log directory mkdir /home/user_ID/tsmlog
Archive log directory mkdir /home/user_ID/
tsmarchlog
Optional: Directory for mkdir /home/user_ID/
the log mirror for the tsmlogmirror
active log
Optional: Secondary mkdir /home/user_ID/
archive log directory, tsmarchlogfailover
which is the failover
location for the archive
log

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
5. Create more logical volumes and mount the volumes on the directories that
were created in the previous step.

Migration scenario 1: Running the upgrade wizard

The wizard offers a guided approach to upgrading a server. Start the wizard on
the system where you installed the V7.1 server program.

Before you begin

Before you start the upgrade wizard, complete all preceding steps to prepare for
the upgrade. Ensure that you backed up the server database and configuration
files. Also, ensure that you installed the V7.1 server program, and created the
directories and user ID for the server instance.

Procedure
1. Verify that the following requirements are met:
v The system where you installed the V7.1 server program must have the X
Window client. You also must be running an X Window server on your
desktop.

390 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

v The system must have one of the following protocols enabled. Ensure that
the port that the protocol uses is not blocked by a firewall.
– Secure Shell (SSH). Ensure that the port is set to the default value, 22.
Also, ensure that the SSH daemon service has access rights for connecting
to the system by using localhost.
– Remote shell (rsh).
– Remote Execution Protocol (REXEC).
The V5 server also must have one of the protocols enabled.
v You must be able to log in to the V7.1 system with the user ID that you
created for the server instance by using the SSH, rsh, or REXEC protocol.
When you use the wizard, you must provide this user ID and password to
access that system.
2. Start the upgrade wizard, dsmupgdx, from the V7.1 server installation directory.
Log in by using the root user ID and issue this command:
/opt/tivoli/tsm/server/bin/dsmupgdx
3. Follow the instructions to complete the upgrade. The upgrade wizard can be
stopped and restarted, but the server will not be operational until the entire
upgrade process is complete. Read all messages that are displayed for each
phase of the upgrade process in the message display area within the wizard.
Informational messages might require your attention.

Migration scenario 2: Using the media method and the command line
Use this procedure if you are migrating the server database by using the media
method and the command line. By applying the media method, you extract data
from the original database to media and load the data into the new database. By
using the command line, you issue administrative commands to upgrade the
system manually.

Procedure

To migrate the system by using Migration scenario 2, complete the following steps:
1. Ensure that you have completed the planning tasks. See Chapter 13, “Planning
the migration,” on page 365.
2. Ensure that you have completed the preparation tasks. See Chapter 14,
“Preparing for the migration,” on page 373.
3. Complete the tasks that are described in the following topics:
a. “Migration scenario 2: Preparing the database of the V5 server” on page 392
b. “Migration scenario 2: Extracting the data to media” on page 393
c. “Migration scenario 2: Installing the V7.1 server” on page 393
d. “Migration scenario 2: Setting up devices” on page 396
e. “Migration scenario 2: Configuring devices” on page 397
f. “Migration scenario 2: Creating the user ID and directories for the server
instance” on page 398
g. “Migration scenario 2: Creating the server instance and database” on page
400
h. “Migration scenario 2: Loading the extracted data into the V7.1 database”
on page 402
i. “Migration scenario 2: Configuring the system for database backup” on page
404

Chapter 15. Migrating the server database to the V7.1 server 391
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

What to do next

After you complete the planning, preparation, and migration steps, complete the
post migration tasks. See Chapter 16, “Taking the first steps after migration,” on
page 425.

Migration scenario 2: Preparing the database of the V5 server

Before you extract the data from the V5 server database, you must prepare the
database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a
single system, you must repeat this task for each server.

Before you begin

The upgrade utilities must be installed on the V5 system.

Procedure
1. Ensure that you completed the initial preparation steps. For instructions, see
Chapter 14, “Preparing for the migration,” on page 373.
2. Log in by using the root user ID on the V5 system.
3. Change to the instance directory for the server that you are upgrading. The
instance directory is the directory that contains the files such as dsmserv.dsk for
the server.
4. Prepare the database. Direct the output of the process to a file for monitoring.
From the instance directory for the server that you are upgrading, issue the
following command to run the process in the background and direct the output
to the file called prepare.out:
AIX
nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

HPUX Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

5. Monitor the process for errors and warning messages. The final message
indicates the success or failure of the operation. From the instance directory for
the server that you are upgrading, issue the following command to monitor the
process:
tail -f prepare.out

What to do next

Ensure that the prepare operation is completed successfully before you continue to
the next step. If the prepare operation fails, you might have to restart the V5 server
to fix the problem and run the prepare operation again. If the server that is being
upgraded is a V5.3 or V5.4 server, you might have to restore the database by using
a backup. Then, you can restart the server to correct the problem.

392 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migration scenario 2: Extracting the data to media

Use the DSMUPGRD utility to extract data from the V5 server database and store it on
a tape device.

Procedure
1. Log in by using the root user ID on the system that has the V5 server.
2. Ensure that the storage device is available. The server database and the device
configuration file must contain a valid device class definition for the device.
3. From the instance directory for the server that you are upgrading, issue the
command to start the extraction. Direct the output of the process to a file for
monitoring. For example, issue the following command on one line:
AIX

nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

devclass=tape manifest=./manifest.txt >extract.out 2>&1 &

HPUX Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

devclass=tape manifest=./manifest.txt >extract.out 2>&1 &

Tip: Messages that are issued during the extract operation are not saved in the
server activity log. Direct the output of the utility to a file, as shown in the
examples, to record the messages.
4. Monitor the process for errors and warning messages, and for items that might
require attention. A message near the end of the process output indicates the
success or failure of the operation:
Success message: ANR1382I EXTRACTDB: Process 1, database extract, has
completed.
Failure message: ANR1396E EXTRACTDB: Process 1, database extract, has
completed with errors.
For example, from the instance directory for the server that you are upgrading,
issue the following command to monitor the process:
tail -f extract.out
The length of time that the process runs depends on the database size. The time
is approximately the length of time that is required for a full database backup.

Migration scenario 2: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

Chapter 15. Migrating the server database to the V7.1 server 393
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

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

About this task

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

Tip: The database (DB2) and the Global Security Kit are automatically installed
when you select the Tivoli Storage Manager server component.
For more information about storage agents, see the Storage Agent User's Guide.

Procedure
1. Log in to the system by using the root user ID.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
a. Verify that you have enough space to store the installation files when they
are extracted from the product package. For space requirements, see the
download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035122
v Tivoli Storage Manager Extended Edition: http://www.ibm.com/
support/docview.wss?uid=swg24035635
v System Storage Archive Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The path must
contain no more than 128 characters. Ensure that you extract the
installation files to an empty directory. Do not extract to a directory that
contains previously extracted files, or any other files. Also, ensure that you
have executable permission for the package file.
c. If necessary, change the file permissions by issuing the following
command:
chmod a+x package_name.bin
where package_name is like the following example:
7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin

394 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

In the examples, 7.1.0.000 represents the product release level. The package
is large, so the download takes some time.
d. Extract the installation files by issuing the following command:
./package_name.bin
where package_name is like the following example:
7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin

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

4. If you plan to install the server by using the graphical interface of the IBM
Installation Manager, verify that the operating system is set to the language
that you require. By default, the language of the operating system is the
language of the installation wizard.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
5. If you use the installation wizard, complete the following steps to begin the
installation:

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

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

6. If you install the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
7. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
8. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.

Chapter 15. Migrating the server database to the V7.1 server 395
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

9. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
10. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.
11. To prevent server failures during interaction with DB2, tune the kernel
parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
12. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
13. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.

Migration scenario 2: Setting up devices

Set up the storage devices that you plan to use with the V7.1 server. Ensure that
you set access permissions correctly for users and groups.

Procedure

To set up storage devices, follow these instructions:

v If the devices that you plan to use are controlled by the IBM device driver,
complete the following steps:
1. Install the IBM device driver and configure devices. Follow the instructions
in the IBM Tape Device Drivers Installation and User's Guide at
http://www.ibm.com/support/docview.wss?uid=ssg1S7002972.
2. To set access permissions, complete one of the following actions:
– If the system is dedicated to Tivoli Storage Manager and only the Tivoli
Storage Manager administrator has access, make the device special files
readable and writable to all users. Issue the following command:
chmod a+rw /dev/IBMtapex

where x is a number that is assigned to a device. For example, a device

drive can be named /dev/IBMtape0, where 0 is the device number.
– Restrict access to a group by creating a group and adding each instance
user ID for Tivoli Storage Manager to that group. Then, change the
ownership of the device special files to belong to the group, and make the
device special files readable and writable to the group. Issue the following
command:
chmod g+rw /dev/IBMtapex

where x is a number that is assigned to a device.

v If the devices that you plan to use are controlled by the Tivoli Storage Manager
device driver, complete the following steps:
1. Log in as the root user.
2. Grant read and write access.
– To grant read and write access to all users, issue the following command:
/opt/tivoli/tsm/devices/bin/autoconf -a

396 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

– To grant read and write access to only the group, issue the following
command:
/opt/tivoli/tsm/devices/bin/autoconf -g
For more information about setting up devices, see the section about attaching
devices to the server in the Administrator's Guide.

Migration scenario 2: Configuring devices

On the Tivoli Storage Manager V7.1 server, configure the devices that you plan to
use. Obtain the library device names and the drive device names for the V7.1
server. Then, update the manifest file with these names.

Procedure

Complete the following steps to configure the devices:

1. Obtain the library serial numbers from the manifest file on the V5 system.

Tip: The manifest file was created in an earlier step, “Migration scenario 2:
Extracting the data to media” on page 393.
The following example is from the manifest file on a V5 server:
DEFINE LIBRARY LTO_LIB LIBTYPE=SCSI WWN="500143800329CAD8"
SERIAL="DEC91503HW" SHARED=NO AUTOLABEL=NO RESETDRIVE=NO

In the preceding example, the library serial number is DEC91503HW.

2. Obtain the library device names:
v If the devices are controlled by the Tivoli Storage Manager device driver,
take the following actions:
a. On the V7 system, issue the command:
cat /dev/tsmscsi/lbinfo
In the output, look for any library serial numbers that you identified in
Step 1.
The output is similar to the following example:
Index Minor Host CHN ID LUN Type Vendor_ID Device_Serial_Number product_ID Rev.
000 006 001 000 003 001 008 HP DEC91503HW MSL G3 Series 5.80

In the sample output, the library serial number is DEC91503HW and the
index number is 000.
b. Use the index number to define the library name.
A library name has the following format:
/dev/tsmscsi/lbx

where x is the index number without leading zeros. If the index number
is 000, remove only the first two leading zeros. In this example, the index
number is 000. When the first two leading zeros are removed, the number
becomes 0, and the library name is defined as /dev/tsmscsi/lb0.
v If the devices are controlled by IBM tape device drivers, obtain library device
names by following the instructions in the IBM Tape Device Drivers Installation
and User's Guide:
http://www.ibm.com/support/docview.wss?uid=ssg1S7002972
The names of library devices that are controlled by an IBM device driver on
a Linux system have the following format:
/dev/IBMchangerx

Chapter 15. Migrating the server database to the V7.1 server 397
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

where x is an integer. For example, a library device can be named

/dev/IBMchanger0.
3. Obtain the serial numbers for the drive devices from the manifest file on the V5
system. The following example is from the manifest file of a V5 server:
DEFINE DRIVE LTO_LIB LTO_DRIVE ELEMENT=1 ONLINE=Yes
WWN="500143800329CAD9" SERIAL="HU171200NG"
In the preceding example, the serial number is HU171200NG.
4. Obtain the names of the device drives:
v If the devices are controlled by the Tivoli Storage Manager device driver,
take the following actions:
a. On the V7 system, issue the following command:
cat /dev/tsmscsi/mtinfo

In the output, look for the device serial numbers that you identified in
Step 3.
The output is similar to the following example:
Index Minor Host CHN ID LUN Type Vendor_ID Device_Serial_Number Product_ID Rev.
000 005 001 000 003 000 001 HP HU171200NG Ultrium 4-SCSI H68W

In the sample output, the index number is 000.

b. Use the index number from the output in Step 4a to define the name of
the device drive. The name of a device drive has the following format:
/dev/tsmscsi/mtx

where x is the index number without leading zeros. In this example, the
index number is 000. After you remove the leading zeros, the number is
0, and the name of the device drive is defined as /dev/tsmscsi/mt0.
v If the devices are controlled by IBM tape device drivers, obtain drive device
names by following the instructions in the IBM Tape Device Drivers Installation
and User's Guide:
http://www.ibm.com/support/docview.wss?uid=ssg1S7002972
Names of device drives that are controlled by IBM tape device drivers have
the following format:
/dev/IBMtapex

where x is a number that is assigned to a device. For example, a device drive

can be named /dev/IBMtape0, where 0 is the device number.
5. Update the manifest file with the library device names and drive device names,
and save the file.

Migration scenario 2: Creating the user ID and directories for

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

Before you begin

To review the information about planning space for the server, see “Estimating
database and recovery log requirements” on page 366.

398 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Procedure
1. Create a user ID and group that will be the owner of the Tivoli Storage
Manager server instance. You will use this user ID when you create the server
instance in a later step.

Restriction: In the user ID, only lowercase letters (a-z), numerals (0-9), and the
underscore character (_) can be used. The user ID and group name must
comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a numeral.
v The user ID and group name cannot be user, admin, guest, public, local, or
any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The following
examples show how to create this user ID and group by using operating
system commands:
# groupadd tsmsrvrs
# useradd -d /home/tsminst1 -m -g tsmsrvrs -s /bin/bash tsminst1
# passwd tsminst1
2. Log out and log in to your system again by using the new user ID and
password. Use an interactive login program, such as telnet, so that you are
prompted for the password and can change it if necessary.
3. If a configuration profile does not exist for the user ID, create the file. For
example, create a .profile file if you are using the Korn shell (ksh).
4. Ensure that you are logged in with the user ID that you created. Then, create
the directories that the server requires.
Unique, empty directories are required for each item that is shown in the
following table. Create the database directories, the active log directory, and the
archive log directory on different physical volumes. For space requirements, see
“Worksheet for planning space for the V7.1 server” on page 42.
Table 63. Worksheet for creating required directories
Example commands for
Item creating the directories Your directories
The instance directory mkdir /home/user_ID/tsminst1
for the server, which will
contain files for this
server instance, including
the server options file
The database directories mkdir /home/user_ID/tsmdb001
mkdir /home/user_ID/tsmdb002
mkdir /home/user_ID/tsmdb003
mkdir /home/user_ID/tsmdb004
Active log directory mkdir /home/user_ID/tsmlog
Archive log directory mkdir /home/user_ID/
tsmarchlog
Optional: Directory for mkdir /home/user_ID/
the log mirror for the tsmlogmirror
active log
Optional: Secondary mkdir /home/user_ID/
archive log directory, tsmarchlogfailover
which is the failover
location for the archive
log

Chapter 15. Migrating the server database to the V7.1 server 399
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
5. Create more logical volumes and mount the volumes on the directories that
were created in the previous step.

Migration scenario 2: Creating the server instance and

database
Create the server instance and format files for an empty V7.1 database. Later, you
can migrate data from the V5 server database to the new V7.1 database.

Procedure
1. Log in to the system where you installed the V7.1 program by using the root
user ID.
Verify the following items:
v The home directory for the user, /home/tsminst1, exists. If there is
no home directory, you must create it.
v The instance directory stores the following core files that are
generated by the Tivoli Storage Manager server:
– The server options file, dsmserv.opt
– The server key database file, cert.kdb, and the .arm files, which
are used by clients and other servers to import the Secure
Sockets Layer certificates of the server
– The device configuration file, if the DEVCONFIG server option does
not specify a fully qualified name
– The volume history file, if the VOLUMEHISTORY server option does
not specify a fully qualified name
– Volumes for storage pools of the FILE device type, if the
directory for the device class is not fully specified, or not fully
qualified
– User exits
– Trace output, if it is not fully qualified
v A shell configuration file, for example, a .profile file, exists in the
home directory. The root user and instance user ID must have write
permission to this file. For more information about the shell
configuration file, go to the DB2 information center at:
http://pic.dhe.ibm.com/infocenter/db2luw/v10r5. Search for
information about Linux and UNIX environment variable settings.
2. Create a Tivoli Storage Manager instance by using the db2icrt command.
Enter the following command on one line. For the instance name, specify the
user ID that you created to own the instance:
/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u
user_id instance_name

For example, if the user ID for this instance is tsminst1, use the following
command to create the instance:
/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u
tsminst1 tsminst1

400 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Remember: From this point on, use this new user ID when you configure the
Tivoli Storage Manager server. Log out of the root user ID, and log in by
using the user ID that is the instance owner.
3. Log in to the system by using the user ID that owns the V7.1 server instance
(the instance user ID).
4. Copy the configuration files to the instance directory that you created for the
new server. The files are the configuration files that you saved from the
original V5 server:
v The device configuration file
v The server options file, which is typically named dsmserv.opt
For example, if you created the instance directory that is shown in the
example in the step to create directories, copy the files into the following
directory:
/tsminst1
Ensure that the instance user ID has ownership or read/write permission to
the files that you copied.
5. Edit the server options file.
a. Remove any options that are not supported for V7.1. For the list of deleted
options, see Table 29 on page 67.
b. Verify that the server options file contains at least one VOLUMEHISTORY
option and at least one DEVCONFIG option. By specifying these options, you
ensure that a volume history file and a device configuration file are
generated and updated automatically. If you must restore the database,
these files are required.
c. Verify that the server options file includes the TXNGROUPMAX option with a
value, and if it does, what the value is. You might want to change the
current value because the default value for this option changed from 256
to 4096, starting in V6. The increased value can improve the performance
for data movement operations such as storage pool migration and storage
pool backup.
v If the server options file does not include this option, the server
automatically uses the new default value, 4096.
v If the specified value is less than 4096, consider increasing the value, or
removing the option so that, when the server is restarted, the new
default value is applied.
6. Change the default path for the database to be the same as the instance
directory for the server. Issue the command:
db2 update dbm cfg using dftdbpath instance_directory

For example:
db2 update dbm cfg using dftdbpath /tsminst1
7. Modify the library path to use the version of the IBM Global Security Kit
(GSKit) that is installed with the Tivoli Storage Manager server.
You must update the following files to set the library path when DB2 or the
Tivoli Storage Manager server is started:
v instance_directory/sqllib/usercshrc
v instance_directory/sqllib/userprofile
For the instance_directory/sqllib/usercshrc file, add the following line:
setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

Chapter 15. Migrating the server database to the V7.1 server 401
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

For the instance_directory/sqllib/userprofile file, add the following lines:

LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH

Verify the library path settings and ensure that the GSKit version is 8.0.14.14
or later. Issue the following commands from the instance home directory, for
example, /home/tsminst1:
echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64
If the GSKit version is not 8.0.14.14 or later, you must reinstall the Tivoli
Storage Manager server. The reinstallation ensures that the correct GSKit
version is available.
8. Change to the instance directory that you created for the server.
9. Create and format the database and recovery logs by using the DSMSERV
LOADFORMAT command. In the command, specify the directories that you
created for the database and logs. The directories must be empty.
For example, to get an active log size of 16 GB or 16384 MB, which is the
default size, issue the following command, on one line:
/opt/tivoli/tsm/server/bin/dsmserv loadformat \
dbdir=/tsmdb001,/tsmdb002,/tsmdb003,/tsmdb004 \
activelogsize=16384 activelogdirectory=/tsmlog \
mirrorlogdirectory=/tsmlogmirror archlogdirectory=/tsmarchlog
For more information about creating and formatting a database, see
Appendix B, “Utilities, scripts, and commands for server upgrade and
migration,” on page 521.
10. Monitor the process for errors and warning messages. The final message
indicates the success or failure of the operation.

Migration scenario 2: Loading the extracted data into the V7.1

database
After you format an empty database by using the DSMSERV LOADFORMAT utility, load
the data that you extracted from the original server database.

Before you begin

Ensure that the following requirements are met before you begin to load the data:
v The manifest file from the DSMUPGRD EXTRACTDB operation must be available.
v The server options file must contain an entry for the device configuration file.
v The device configuration file must have information about the device class that
is specified in the manifest file.
v The media that contains the extracted database must be available to the V7.1
server. The device must be physically attached to the system. The permissions
must be set to grant access to the media for the user ID that owns the V7.1
server instance.

Procedure

Complete the following steps:

1. Verify that the V7.1 server can access the extracted data. The tape drive that is
used for the extracted data must be physically attached to the V7.1 system.
2. Ensure that the instance user ID has ownership or read/write permission for
the manifest file that was created by the extraction process.

402 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

3. Log in with the instance user ID on the system where you installed the V7.1
server.
4. Copy the manifest file that was created by the extraction process to the V7.1
system.
5. On the V7.1 server, complete the following steps:
a. Verify that the server options file from the V5 server includes the
DEVCONFIG option, and that the option specifies the full path of the device
configuration file.
b. Verify that the device configuration file from the V5 server is available in
the location that is specified by the DEVCONFIG option.
c. Verify that the permissions on the device configuration file allow read
access for the instance user ID.
6. Verify that the contents of the device configuration file are correct. The device
class that was used for the extraction step is recorded in the manifest file, and
that device class must exist and be valid on the V7.1 system. Verify entries for
tape. For example, the device names might have changed.
7. Verify the contents of the manifest file and edit the file if necessary:
a. Ensure that the device names in the manifest file are valid for the V7.1
system. Device names for the same device might be different on V5 and
V7.1 systems.
b. Ensure that the manifest file contains a list of volumes to be used when
the extracted data is loaded into the new database.
8. To load an extracted server database into the prepared, empty V7.1 database,
issue the DSMSERV INSERTDB command. Direct the output of the process to a
file for monitoring. For example, enter the following command on one line:
nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \
manifest=./manifest.txt >insert.out 2>&1 &
For more information about loading an extracted database into a new
database, see Appendix B, “Utilities, scripts, and commands for server
upgrade and migration,” on page 521.
9. Monitor the process for error messages, warning messages, and any items that
might require your attention. The system displays interim statistics about the
process of loading the database. However, there might be time periods when
no messages are issued. During this time, DB2 operations are running in the
background. The length of time that the process runs depends on the size of
the database. For more information, see “Example: Estimating the upgrade
time based on the database size” on page 43.
Optional: Verify that the database is being loaded by monitoring the processor
and I/O usage for the server process and the corresponding DB2 process. For
example, issue the following command to monitor the process:
tail -f insert.out
A message in the output of the DSMSERV INSERTDB command indicates the
status of the operation:
v Success message: ANR1395I INSERTDB: Process 1, database insert, has
completed.
v Failure message: ANR1396E INSERTDB: Process 1, database insert, has
completed with errors.
10. If you used the media method to upgrade the system, after the data is loaded
into the database, remove or check out from the library the tape that holds the
extracted data. Prevent the tape from being reused until you are sure that you
do not need to run the database-loading operation again.

Chapter 15. Migrating the server database to the V7.1 server 403
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migration scenario 2: Configuring the system for database

backup
If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

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

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, replace the example values with your actual values.
The examples use tsminst1 for the server instance user ID, /tsminst1 for the Tivoli
Storage Manager server instance directory, and /home/tsminst1 as the home
directory of the server instance user.

Procedure
1. Set the Tivoli Storage Manager API environment-variable configuration for the
database instance:
a. Log in by using the tsminst1 user ID.
b. When user tsminst1 is logged in, ensure that the DB2 environment is
correctly initialized. The DB2 environment is initialized by running the
/home/tsminst1/sqllib/db2profile script, which normally runs
automatically from the profile of the user ID. Ensure that the .profile file
exists in the home directory of the instance user, for example,
/home/tsminst1/.profile. If .profile does not run the db2profile script,
add the following lines:
if [ -f /home/tsminst1/sqllib/db2profile ]; then
. /home/tsminst1/sqllib/db2profile
fi
c. In the instance_directory/sqllib/userprofile file, add the following lines:
DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
DSMI_DIR=server_bin_directory/dbbkapi
DSMI_LOG=server_instance_directory
export DSMI_CONFIG DSMI_DIR DSMI_LOG
d. In the instance_directory/sqllib/usercshrc file, add the following lines:
setenv DSMI_CONFIG=server_instance_directory/tsmdbmgr.opt
setenv DSMI_DIR=server_bin_directory/dbbkapi
setenv DSMI_LOG=server_instance_directory
2. Log out and log in again as tsminst1, or issue this command:
. ~/.profile

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

404 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

SERVERNAME TSMDBMGR_TSMINST1

The value for SERVERNAME must be consistent in the tsmdbmgr.opt and dsm.sys
files.
4. Locate the Tivoli Storage Manager API dsm.sys configuration file. By default,
the dsm.sys file is in the following location:

server_bin_directory/dbbkapi/dsm.sys
5. As root user, add the following lines to the dsm.sys configuration file:
servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
errorlogname /tsminst1
nodename $$_TSMDBMGR_$$

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

where port_number specifies the port to use for shared memory.

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

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

Chapter 15. Migrating the server database to the V7.1 server 405
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

where port_number specifies the port to use for shared memory.

Migration scenario 3: Using the network method and the upgrade

wizard
Use this procedure if you are migrating the server by using the network method
and the upgrade wizard. By applying the network method, you simultaneously
extract data from the original database and load the data into the new database
over a network connection. By using the wizard, you simplify the configuration
process.

Procedure

To migrate the system by using Migration scenario 3, complete the following steps:
1. Ensure that you have completed the planning tasks. See Chapter 13, “Planning
the migration,” on page 365.
2. Ensure that you have completed the preparation tasks. See Chapter 14,
“Preparing for the migration,” on page 373.
3. Complete the tasks that are described in the following topics:
a. “Migration scenario 3: Installing the V7.1 server”
b. “Migration scenario 3: Setting up devices” on page 409
c. “Migration scenario 3: Creating the user ID and directories for the server
instance” on page 410
d. “Migration scenario 3: Running the upgrade wizard” on page 411

What to do next

After you complete the planning, preparation, and migration steps, complete the
post migration tasks. See Chapter 16, “Taking the first steps after migration,” on
page 425.

Migration scenario 3: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

About this task

By using the Tivoli Storage Manager installation software, you can install the
following Tivoli Storage Manager components:
406 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

v server
v server languages
v license
v devices
v Operations Center
v storage agent

Tip: The database (DB2) and the Global Security Kit are automatically installed
when you select the Tivoli Storage Manager server component.
For more information about storage agents, see the Storage Agent User's Guide.

Procedure
1. Log in to the system by using the root user ID.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
a. Verify that you have enough space to store the installation files when they
are extracted from the product package. For space requirements, see the
download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035122
v Tivoli Storage Manager Extended Edition: http://www.ibm.com/
support/docview.wss?uid=swg24035635
v System Storage Archive Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The path must
contain no more than 128 characters. Ensure that you extract the
installation files to an empty directory. Do not extract to a directory that
contains previously extracted files, or any other files. Also, ensure that you
have executable permission for the package file.
c. If necessary, change the file permissions by issuing the following
command:
chmod a+x package_name.bin
where package_name is like the following example:
7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin

In the examples, 7.1.0.000 represents the product release level. The package
is large, so the download takes some time.
d. Extract the installation files by issuing the following command:
./package_name.bin
where package_name is like the following example:
7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin

Chapter 15. Migrating the server database to the V7.1 server 407
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

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

4. If you plan to install the server by using the graphical interface of the IBM
Installation Manager, verify that the operating system is set to the language
that you require. By default, the language of the operating system is the
language of the installation wizard.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
5. If you use the installation wizard, complete the following steps to begin the
installation:

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

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

6. If you install the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
7. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
8. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
9. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
10. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.

408 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

11. To prevent server failures during interaction with DB2, tune the kernel
parameters.
For instructions, see the section about tuning kernel parameters in the
Installation Guide.
12. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
13. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.

Migration scenario 3: Setting up devices

Set up the storage devices that you plan to use with the V7.1 server. Ensure that
you set access permissions correctly for users and groups.

Procedure

To set up storage devices, follow these instructions:

v If the devices that you plan to use are controlled by the IBM device driver,
complete the following steps:
1. Install the IBM device driver and configure devices. Follow the instructions
in the IBM Tape Device Drivers Installation and User's Guide at
http://www.ibm.com/support/docview.wss?uid=ssg1S7002972.
2. To set access permissions, complete one of the following actions:
– If the system is dedicated to Tivoli Storage Manager and only the Tivoli
Storage Manager administrator has access, make the device special files
readable and writable to all users. Issue the following command:
chmod a+rw /dev/IBMtapex

where x is a number that is assigned to a device. For example, a device

drive can be named /dev/IBMtape0, where 0 is the device number.
– Restrict access to a group by creating a group and adding each instance
user ID for Tivoli Storage Manager to that group. Then, change the
ownership of the device special files to belong to the group, and make the
device special files readable and writable to the group. Issue the following
command:
chmod g+rw /dev/IBMtapex

where x is a number that is assigned to a device.

v If the devices that you plan to use are controlled by the Tivoli Storage Manager
device driver, complete the following steps:
1. Log in as the root user.
2. Grant read and write access.
– To grant read and write access to all users, issue the following command:
/opt/tivoli/tsm/devices/bin/autoconf -a
– To grant read and write access to only the group, issue the following
command:
/opt/tivoli/tsm/devices/bin/autoconf -g
For more information about setting up devices, see the section about attaching
devices to the server in the Administrator's Guide.

Chapter 15. Migrating the server database to the V7.1 server 409
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migration scenario 3: Creating the user ID and directories for

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

Before you begin

To review the information about planning space for the server, see “Estimating
database and recovery log requirements” on page 366.

Procedure
1. Create a user ID and group that will be the owner of the Tivoli Storage
Manager server instance. You will use this user ID when you create the server
instance in a later step.

Restriction: In the user ID, only lowercase letters (a-z), numerals (0-9), and the
underscore character (_) can be used. The user ID and group name must
comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a numeral.
v The user ID and group name cannot be user, admin, guest, public, local, or
any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The following
examples show how to create this user ID and group by using operating
system commands:
# groupadd tsmsrvrs
# useradd -d /home/tsminst1 -m -g tsmsrvrs -s /bin/bash tsminst1
# passwd tsminst1
2. Log out and log in to your system again by using the new user ID and
password. Use an interactive login program, such as telnet, so that you are
prompted for the password and can change it if necessary.
3. If a configuration profile does not exist for the user ID, create the file. For
example, create a .profile file if you are using the Korn shell (ksh).
4. Ensure that you are logged in with the user ID that you created. Then, create
the directories that the server requires.
Unique, empty directories are required for each item that is shown in the
following table. Create the database directories, the active log directory, and the
archive log directory on different physical volumes. For space requirements, see
“Worksheet for planning space for the V7.1 server” on page 42.
Table 64. Worksheet for creating required directories
Example commands for
Item creating the directories Your directories
The instance directory mkdir /home/user_ID/tsminst1
for the server, which will
contain files for this
server instance, including
the server options file
The database directories mkdir /home/user_ID/tsmdb001
mkdir /home/user_ID/tsmdb002
mkdir /home/user_ID/tsmdb003
mkdir /home/user_ID/tsmdb004

410 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Table 64. Worksheet for creating required directories (continued)

Example commands for
Item creating the directories Your directories
Active log directory mkdir /home/user_ID/tsmlog
Archive log directory mkdir /home/user_ID/
tsmarchlog
Optional: Directory for mkdir /home/user_ID/
the log mirror for the tsmlogmirror
active log
Optional: Secondary mkdir /home/user_ID/
archive log directory, tsmarchlogfailover
which is the failover
location for the archive
log

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
5. Create more logical volumes and mount the volumes on the directories that
were created in the previous step.

Migration scenario 3: Running the upgrade wizard

The wizard offers a guided approach to upgrading a server. Start the wizard on
the system where you installed the V7.1 server program.

Before you begin

Before you start the upgrade wizard, complete all preceding steps to prepare for
the upgrade. Ensure that you backed up the server database and configuration
files. Also, ensure that you installed the V7.1 server program, and created the
directories and user ID for the server instance.

Procedure
1. Verify that the following requirements are met:
v The system where you installed the V7.1 server program must have the X
Window client. You also must be running an X Window server on your
desktop.
v The system must have one of the following protocols enabled. Ensure that
the port that the protocol uses is not blocked by a firewall.
– Secure Shell (SSH). Ensure that the port is set to the default value, 22.
Also, ensure that the SSH daemon service has access rights for connecting
to the system by using localhost.
– Remote shell (rsh).
– Remote Execution Protocol (REXEC).
The V5 server also must have one of the protocols enabled.
v You must be able to log in to the V7.1 system with the user ID that you
created for the server instance by using the SSH, rsh, or REXEC protocol.
When you use the wizard, you must provide this user ID and password to
access that system.
2. Start the upgrade wizard, dsmupgdx, from the V7.1 server installation directory.
Log in by using the root user ID and issue this command:

Chapter 15. Migrating the server database to the V7.1 server 411
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

/opt/tivoli/tsm/server/bin/dsmupgdx
3. Follow the instructions to complete the upgrade. The upgrade wizard can be
stopped and restarted, but the server will not be operational until the entire
upgrade process is complete. Read all messages that are displayed for each
phase of the upgrade process in the message display area within the wizard.
Informational messages might require your attention.

Migration scenario 4: Using the network method and the command line
Use this procedure if you are migrating the server database by using the network
method and the command line. By applying the network method, you
simultaneously extract data from the original database and load the data into the
new database over a network connection. By using administrative commands, you
migrate the system manually.

Procedure

To migrate the system by using Migration scenario 4, complete the following steps:
1. Ensure that you have completed the planning tasks. See Chapter 13, “Planning
the migration,” on page 365.
2. Ensure that you have completed the preparation tasks. See Chapter 14,
“Preparing for the migration,” on page 373.
3. Complete the tasks that are described in the following topics:
a. “Migration scenario 4: Preparing the database of the V5 server”
b. “Migration scenario 4: Installing the V7.1 server” on page 413
c. “Migration scenario 4: Setting up devices” on page 416
d. “Migration scenario 4: Creating the user ID and directories for the server
instance” on page 417
e. “Migration scenario 4: Creating the server instance and database” on page
418
f. “Migration scenario 4: Moving the server database over a network” on page
420
g. “Migration scenario 4: Configuring the system for database backup” on
page 422

What to do next

After you complete the planning, preparation, and migration steps, complete the
post migration tasks. See Chapter 16, “Taking the first steps after migration,” on
page 425.

Migration scenario 4: Preparing the database of the V5 server

Before you extract the data from the V5 server database, you must prepare the
database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a
single system, you must repeat this task for each server.

Before you begin

The upgrade utilities must be installed on the V5 system.

412 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Procedure
1. Ensure that you completed the initial preparation steps. For instructions, see
Chapter 14, “Preparing for the migration,” on page 373.
2. Log in by using the root user ID on the V5 system.
3. Change to the instance directory for the server that you are upgrading. The
instance directory is the directory that contains the files such as dsmserv.dsk for
the server.
4. Prepare the database. Direct the output of the process to a file for monitoring.
From the instance directory for the server that you are upgrading, issue the
following command to run the process in the background and direct the output
to the file called prepare.out:
AIX
nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

HPUX Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

5. Monitor the process for errors and warning messages. The final message
indicates the success or failure of the operation. From the instance directory for
the server that you are upgrading, issue the following command to monitor the
process:
tail -f prepare.out

What to do next

Ensure that the prepare operation is completed successfully before you continue to
the next step. If the prepare operation fails, you might have to restart the V5 server
to fix the problem and run the prepare operation again. If the server that is being
upgraded is a V5.3 or V5.4 server, you might have to restore the database by using
a backup. Then, you can restart the server to correct the problem.

Migration scenario 4: Installing the V7.1 server

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

About this task

By using the Tivoli Storage Manager installation software, you can install the
following Tivoli Storage Manager components:
v server
Chapter 15. Migrating the server database to the V7.1 server 413
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

v server languages
v license
v devices
v Operations Center
v storage agent

Tip: The database (DB2) and the Global Security Kit are automatically installed
when you select the Tivoli Storage Manager server component.
For more information about storage agents, see the Storage Agent User's Guide.

Procedure
1. Log in to the system by using the root user ID.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
a. Verify that you have enough space to store the installation files when they
are extracted from the product package. For space requirements, see the
download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035122
v Tivoli Storage Manager Extended Edition: http://www.ibm.com/
support/docview.wss?uid=swg24035635
v System Storage Archive Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The path must
contain no more than 128 characters. Ensure that you extract the
installation files to an empty directory. Do not extract to a directory that
contains previously extracted files, or any other files. Also, ensure that you
have executable permission for the package file.
c. If necessary, change the file permissions by issuing the following
command:
chmod a+x package_name.bin
where package_name is like the following example:
7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin

In the examples, 7.1.0.000 represents the product release level. The package
is large, so the download takes some time.
d. Extract the installation files by issuing the following command:
./package_name.bin
where package_name is like the following example:
7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin

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

414 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

4. If you plan to install the server by using the graphical interface of the IBM
Installation Manager, verify that the operating system is set to the language
that you require. By default, the language of the operating system is the
language of the installation wizard.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
5. If you use the installation wizard, complete the following steps to begin the
installation:

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

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

6. If you install the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.
7. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
8. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
9. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
10. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.
11. To prevent server failures during interaction with DB2, tune the kernel
parameters.

Chapter 15. Migrating the server database to the V7.1 server 415
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

For instructions, see the section about tuning kernel parameters in the
Installation Guide.
12. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
13. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.

Migration scenario 4: Setting up devices

Set up the storage devices that you plan to use with the V7.1 server. Ensure that
you set access permissions correctly for users and groups.

Procedure
To set up storage devices, follow these instructions:
v If the devices that you plan to use are controlled by the IBM device driver,
complete the following steps:
1. Install the IBM device driver and configure devices. Follow the instructions
in the IBM Tape Device Drivers Installation and User's Guide at
http://www.ibm.com/support/docview.wss?uid=ssg1S7002972.
2. To set access permissions, complete one of the following actions:
– If the system is dedicated to Tivoli Storage Manager and only the Tivoli
Storage Manager administrator has access, make the device special files
readable and writable to all users. Issue the following command:
chmod a+rw /dev/IBMtapex

where x is a number that is assigned to a device. For example, a device

drive can be named /dev/IBMtape0, where 0 is the device number.
– Restrict access to a group by creating a group and adding each instance
user ID for Tivoli Storage Manager to that group. Then, change the
ownership of the device special files to belong to the group, and make the
device special files readable and writable to the group. Issue the following
command:
chmod g+rw /dev/IBMtapex

where x is a number that is assigned to a device.

v If the devices that you plan to use are controlled by the Tivoli Storage Manager
device driver, complete the following steps:
1. Log in as the root user.
2. Grant read and write access.
– To grant read and write access to all users, issue the following command:
/opt/tivoli/tsm/devices/bin/autoconf -a
– To grant read and write access to only the group, issue the following
command:
/opt/tivoli/tsm/devices/bin/autoconf -g
For more information about setting up devices, see the section about attaching
devices to the server in the Administrator's Guide.

416 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Migration scenario 4: Creating the user ID and directories for

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

Before you begin

To review the information about planning space for the server, see “Estimating
database and recovery log requirements” on page 366.

Procedure
1. Create a user ID and group that will be the owner of the Tivoli Storage
Manager server instance. You will use this user ID when you create the server
instance in a later step.

Restriction: In the user ID, only lowercase letters (a-z), numerals (0-9), and the
underscore character (_) can be used. The user ID and group name must
comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a numeral.
v The user ID and group name cannot be user, admin, guest, public, local, or
any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The following
examples show how to create this user ID and group by using operating
system commands:
# groupadd tsmsrvrs
# useradd -d /home/tsminst1 -m -g tsmsrvrs -s /bin/bash tsminst1
# passwd tsminst1
2. Log out and log in to your system again by using the new user ID and
password. Use an interactive login program, such as telnet, so that you are
prompted for the password and can change it if necessary.
3. If a configuration profile does not exist for the user ID, create the file. For
example, create a .profile file if you are using the Korn shell (ksh).
4. Ensure that you are logged in with the user ID that you created. Then, create
the directories that the server requires.
Unique, empty directories are required for each item that is shown in the
following table. Create the database directories, the active log directory, and the
archive log directory on different physical volumes. For space requirements, see
“Worksheet for planning space for the V7.1 server” on page 42.
Table 65. Worksheet for creating required directories
Example commands for
Item creating the directories Your directories
The instance directory mkdir /home/user_ID/tsminst1
for the server, which will
contain files for this
server instance, including
the server options file
The database directories mkdir /home/user_ID/tsmdb001
mkdir /home/user_ID/tsmdb002
mkdir /home/user_ID/tsmdb003
mkdir /home/user_ID/tsmdb004

Chapter 15. Migrating the server database to the V7.1 server 417
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Table 65. Worksheet for creating required directories (continued)

Example commands for
Item creating the directories Your directories
Active log directory mkdir /home/user_ID/tsmlog
Archive log directory mkdir /home/user_ID/
tsmarchlog
Optional: Directory for mkdir /home/user_ID/
the log mirror for the tsmlogmirror
active log
Optional: Secondary mkdir /home/user_ID/
archive log directory, tsmarchlogfailover
which is the failover
location for the archive
log

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
5. Create more logical volumes and mount the volumes on the directories that
were created in the previous step.

Migration scenario 4: Creating the server instance and

database
Create the server instance and format files for an empty V7.1 database.

Procedure
1. Log in to the system where you installed the V7.1 program by using the root
user ID.
Verify the following items:
v The home directory for the user, /home/tsminst1, exists. If there is
no home directory, you must create it.
v The instance directory stores the following core files that are
generated by the Tivoli Storage Manager server:
– The server options file, dsmserv.opt
– The server key database file, cert.kdb, and the .arm files, which
are used by clients and other servers to import the Secure
Sockets Layer certificates of the server
– The device configuration file, if the DEVCONFIG server option does
not specify a fully qualified name
– The volume history file, if the VOLUMEHISTORY server option does
not specify a fully qualified name
– Volumes for storage pools of the FILE device type, if the
directory for the device class is not fully specified, or not fully
qualified
– User exits
– Trace output, if it is not fully qualified
v A shell configuration file, for example, a .profile file, exists in the
home directory. The root user and instance user ID must have write
permission to this file. For more information about the shell

418 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

configuration file, go to the DB2 information center at:

http://pic.dhe.ibm.com/infocenter/db2luw/v10r5. Search for
information about Linux and UNIX environment variable settings.
2. Create a Tivoli Storage Manager instance by using the db2icrt command.
Enter the following command on one line. For the instance name, specify the
user ID that you created to own the instance:
/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u
user_id instance_name

For example, if the user ID for this instance is tsminst1, use the following
command to create the instance:
/opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u
tsminst1 tsminst1

Remember: From this point on, use this new user ID when you configure the
Tivoli Storage Manager server. Log out of the root user ID, and log in by
using the user ID that is the instance owner.
3. Log in to the system by using the user ID that owns the V7.1 server instance
(the instance user ID).
4. Copy the server options file from the V5 server to the instance directory that
you created for the V7.1 server. The server options file is typically named
dsmserv.opt. For example, if you created the instance directory that is shown
in the example for creating directories, copy the file into the following
directory:
/tsminst1
Ensure that the instance user ID has ownership of or read/write permission
for the server options file.
5. Edit the server options file.
a. Remove any options that are not supported for V7.1. For the list of deleted
options, see Table 29 on page 67.
b. Verify that the server options file contains at least one VOLUMEHISTORY
option and at least one DEVCONFIG option. By specifying these options, you
ensure that a volume history file and a device configuration file are
generated and updated automatically. If you must restore the database,
these files are required.
c. Verify that the server options file includes the TXNGROUPMAX option with a
value, and if it does, what the value is. You might want to change the
current value because the default value for this option changed from 256
to 4096, starting in V6. The increased value can improve the performance
for data movement operations such as storage pool migration and storage
pool backup.
v If the server options file does not include this option, the server
automatically uses the new default value, 4096.
v If the specified value is less than 4096, consider increasing the value, or
removing the option so that, when the server is restarted, the new
default value is applied.
6. Change the default path for the database to be the same as the instance
directory for the server. Issue the command:
db2 update dbm cfg using dftdbpath instance_directory

For example:
db2 update dbm cfg using dftdbpath /tsminst1

Chapter 15. Migrating the server database to the V7.1 server 419
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

7. Modify the library path to use the version of the IBM Global Security Kit
(GSKit) that is installed with the Tivoli Storage Manager server.
You must update the following files to set the library path when DB2 or the
Tivoli Storage Manager server is started:
v instance_directory/sqllib/usercshrc
v instance_directory/sqllib/userprofile
For the instance_directory/sqllib/usercshrc file, add the following line:
setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH

For the instance_directory/sqllib/userprofile file, add the following lines:

LD_LIBRARY_PATH=/usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH

Verify the library path settings and ensure that the GSKit version is 8.0.14.14
or later. Issue the following commands from the instance home directory, for
example, /home/tsminst1:
echo $LD_LIBRARY_PATH
gsk8capicmd_64 -version
gsk8ver_64
If the GSKit version is not 8.0.14.14 or later, you must reinstall the Tivoli
Storage Manager server. The reinstallation ensures that the correct GSKit
version is available.
8. Change to the instance directory that you created for the server.
9. Create and format the database and recovery logs by using the DSMSERV
LOADFORMAT command. In the command, specify the directories that you
created for the database and logs. The directories must be empty.
For example, to get an active log size of 16 GB or 16384 MB, which is the
default size, issue the following command, on one line:
/opt/tivoli/tsm/server/bin/dsmserv loadformat \
dbdir=/tsmdb001,/tsmdb002,/tsmdb003,/tsmdb004 \
activelogsize=16384 activelogdirectory=/tsmlog \
mirrorlogdirectory=/tsmlogmirror archlogdirectory=/tsmarchlog
For more information about creating and formatting a database, see
Appendix B, “Utilities, scripts, and commands for server upgrade and
migration,” on page 521.
10. Monitor the process for errors and warning messages. The final message
indicates the success or failure of the operation.

Migration scenario 4: Moving the server database over a

network
Move the database by starting the insertion process for the V7.1 server to accept
the server database. Then, start the extraction process for the V5 server to extract
and send the database.

Before you begin

Ensure that the Tivoli Storage Manager V5 server and V7.1 server are not running.

Procedure

To move the server database over a network, complete the following steps:
1. Verify that there is a good network connection between the two systems.

420 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

2. Start the insertion process on the V7.1 server to accept the database. Use the
DSMSERV INSERTDB command. To monitor the process, direct the output of the
process to a file. For example, to start the server, allow the default time of 60
minutes for the V5 server to contact the V7.1 server, and direct the process
output to the insert.out file, use this command:
nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \
sesswait=60 >insert.out 2>&1 &
For more information about inserting data, see Appendix B, “Utilities, scripts,
and commands for server upgrade and migration,” on page 521.

The server starts and waits up to 60 minutes to be contacted by the original

server. Some time might pass during which no messages are issued. During
this time, DB2 operations are running in the background. Optional: To verify
that operations are continuing as expected, monitor the processor and I/O
usage for the server process and the corresponding DB2 process.
3. Monitor the output of the DSMSERV INSERTDB process. Verify that the DSMSERV
INSERTDB process issues the following message before you continue to the next
step:
ANR1336I INSERTDB: Ready for connections from the source server

Issue the following command to monitor the process output in the insert.out
file:
tail -f insert.out
4. Start the data extraction from the original server by using the DSMUPGRD
EXTRACTDB command. Issue the command from the V5 server directory. Specify
the TCP/IP address and port for the V7.1 server. Direct the output of the
process to a file for monitoring. For example, enter the following command on
one line:
AIX

nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

hladdress=9.11.25.124 lladdress=1500 >extract.out 2>&1 &

HPUX Solaris

nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \

hladdress=9.11.25.124 lladdress=1500 >extract.out 2>&1 &
For more information about extracting data, see Appendix B, “Utilities, scripts,
and commands for server upgrade and migration,” on page 521.
5. Monitor the processes for errors and warning messages, and for items that
might require attention. From the instance directory for the server that you are
upgrading, issue the following command to monitor the extraction process:
tail -f extract.out

The length of time that the process runs depends on the size of the database,
the hardware, and the network.
6. Examine the process outputs for the extraction and insertion processes to find
the messages that indicate the success or failure of the operations.

Process Success message Failure message

Extraction ANR1382I EXTRACTDB: Process 1, ANR1396E EXTRACTDB: Process 1,
database extract, has database extract, has completed
completed. with errors.

Chapter 15. Migrating the server database to the V7.1 server 421
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Process Success message Failure message

Insertion ANR1395I INSERTDB: Process 1, ANR1396E INSERTDB: Process 1,
database insert, has completed. database insert, has completed
with errors.

Migration scenario 4: Configuring the system for database

backup
If you did not use the upgrade wizard, you must complete the configuration for
the database backup manually.

About this task

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

Complete the following steps before you issue either the BACKUP DB or the RESTORE
DB command.

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

In the following commands, replace the example values with your actual values.
The examples use tsminst1 for the server instance user ID, /tsminst1 for the Tivoli
Storage Manager server instance directory, and /home/tsminst1 as the home
directory of the server instance user.

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

422 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

2. Log out and log in again as tsminst1, or issue this command:

. ~/.profile

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

The value for SERVERNAME must be consistent in the tsmdbmgr.opt and dsm.sys
files.
4. Locate the Tivoli Storage Manager API dsm.sys configuration file. By default,
the dsm.sys file is in the following location:

server_bin_directory/dbbkapi/dsm.sys
5. As root user, add the following lines to the dsm.sys configuration file:
servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
errorlogname /tsminst1
nodename $$_TSMDBMGR_$$

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

where port_number specifies the port to use for shared memory.

b. In the dsm.sys configuration file, locate the following lines:

Chapter 15. Migrating the server database to the V7.1 server 423
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

commmethod tcpip
tcpserveraddr localhost
tcpport port_number

Replace the specified lines with the following lines:

commmethod sharedmem
shmport port_number

where port_number specifies the port to use for shared memory.

424 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 16. Taking the first steps after migration
Verify that the server was migrated and can operate normally. The steps include
starting the server, registering licenses, and backing up the database. After you
complete those steps, you can begin operations and monitor the migrated server.

Procedure

Complete the following tasks:

1. “Configuring server options for server database maintenance”
2. “Starting the server” on page 426
3. “Verifying the migration results” on page 426
4. “Registering licenses” on page 427
5. “Updating device path information” on page 428
6. “Backing up the database” on page 428
7. “Changing the host name for the Tivoli Storage Manager server” on page 429
8. “Updating the tcpserveraddress option” on page 430
9. “Setting the IP address of the server” on page 430
10. “Migrating data from tape to DISK or FILE devices” on page 431
11. “Restoring backup sets” on page 432
12. “Updating automation” on page 433
13. “Beginning operations and monitoring the server” on page 433

What to do next

After you migrate the server to V7.1, you can authenticate passwords with the
LDAP directory server, or authenticate passwords with the Tivoli Storage Manager
server. Passwords that are authenticated with the LDAP directory server can
provide enhanced system security. For details, see the section about managing
passwords and logon procedures in the Administrator's Guide.

Configuring server options for server database maintenance

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

About this task

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

Procedure
1. Modify the server options.

© Copyright IBM Corp. 2009, 2013 425

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

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

Tip: By using SAN discovery, the server can automatically correct the special
file name for a device if it was changed for a specified tape device.

Starting the server

To verify that the upgrade was successful, start the server.

Procedure

To start the server, follow the instructions for Linux operating systems in “Starting
the server on AIX, HP-UX, Linux, and Oracle Solaris systems” on page 325.

Verifying the migration results

After the migration, verify the operation of the V7.1 server. Monitor the server for
error and warning messages, verify that storage devices are accessible to the server,
and conduct tests to ensure that the system is operating as planned.

Procedure
1. Monitor the messages that the server issues as it starts. Watch for error and
warning messages.
2. Verify the following items:

426 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

a. Ensure that the storage devices of the original server are accessible to the
upgraded server.
b. Compare the device names on the new system with the names for the
devices on the original system. Update definitions for the devices on the
server if needed. For example, update path definitions. For instructions, see
“Updating device path information” on page 428.
c. Update the network address that is used by backup-archive clients, storage
agents, library client servers, and other servers for communicating with the
upgraded server.
Optionally, instead of making these updates, consider whether you can use
the network address of the original system as the address of the new
system. You might also be able to update domain name service (DNS) to
point to the new system instead of the original system. Consult your
network administrator.
3. Verify that you can connect to the server by using an administrative client as
you did for the earlier version of the server.
4. Run commands to get a summary of information in the database. Compare the
summary with the results for the same commands before the database
migration.

Tip: For more information about the commands that are run before a database
migration, see “Creating a summary of database contents” on page 377.
5. Perform backups for typical client nodes and verify that the backups work as
expected.
6. Verify that operations such as LAN-free data movement and library sharing
work correctly.

What to do next

If the server is operating as expected and you must not revert to the previous
version, return any settings that you changed to prepare for the migration back to
the original values.

Registering licenses
Immediately register any Tivoli Storage Manager licensed functions that you
purchased so that you do not lose data after you begin to use the server.

Procedure

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

where installation_directory specifies the directory in which you installed the

component, and component_name specifies the abbreviation for the component.

For example, if you installed the server in the default directory, /opt/tivoli/tsm,
register the license by issuing the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmbasic.lic

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

Chapter 16. Taking the first steps after migration 427

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

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

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

Restriction: You cannot register licenses for Tivoli Storage Manager for Mail, Tivoli
Storage Manager for Databases, Tivoli Storage Manager for ERP, and Tivoli Storage
Manager for Space Management.

Updating device path information

If the storage area network (SAN) discovery function is not enabled, update the
device path information for all drives and libraries. This step is required to ensure
that storage devices can be accessed by the new system.

About this task

The SANDISCOVERY server option is available to automatically correct a special file

name for a device if the file name changed because of changes in a SAN
environment. If the SANDISCOVERY server option is set to OFF, update the device
path information manually.

For instructions to update device path information, see the UPDATE PATH command
in the Administrator's Reference.

If the SANDISCOVERY server option is set to ON, device path information for drives
and libraries should be updated automatically when the V7.1 server is started.

Backing up the database

After you migrate the data, perform a full backup of the database as soon as
possible. Also, back up the volume history.

Procedure
1. Complete the following steps:
a. If you did not use the instance configuration wizard to configure the server,
ensure that you have completed the steps to manually configure the system
for database backups.
b. If you used the media method for upgrade and used a tape device, remove
or check out from the library the tape that was used to hold the extracted
data. Prevent the tape from being reused until you are sure that the V7.1
server is operating correctly and you do not need to repeat the database
insertion step.
2. Select the device class to be used for automatic backups of the database. From
the Tivoli Storage Manager administrative command line, issue the following
command:
set dbrecovery device_class_name

where device_class_name is the name of the device class to be used by the

database manager for all automatic database backups.
For more information about selecting a device class for automatic backups, see
the SET DBRECOVERY command in the Administrator's Reference.
3. Back up the database by issuing the following command:
backup db devclass=device_class_name type=full

428 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

where device_class_name is the name of the device class. You can specify the
device class to be the same as or different from the device class that you
specified with the SET DBRECOVERY command. If the device class is different, you
receive a warning message, but the backup operation continues.
For more information about backing up the database, see the BACKUP DB
command in the Administrator's Reference.
4. Back up the volume history by issuing the following command:
backup volhistory filenames=file_name

where file_name is the name of the file where volume history information will
be stored.
For more information about backing up volume history, see the BACKUP
VOLHISTORY command in the Administrator's Reference.

Changing the host name for the Tivoli Storage Manager server
If you must change the host name of the Tivoli Storage Manager V7.1 server,
ensure that you also update the database configuration. If you fail to update the
database configuration, the Tivoli Storage Manager server might not start.

Procedure

Change the host name by completing the following steps:

1. Stop any Tivoli Storage Manager servers that are running on the system.
2. Change the host name by using the procedures that are defined for your
operating system.
3. From the root user ID on the system, issue the following command:
db2set -g DB2SYSTEM=newhostname
where newhostname is the new host name for the server.

Tip: The db2set command is in the /opt/tivoli/tsm/db2/adm directory.

4. Verify that the DB2SYSTEM value was changed by issuing the following
command:
db2set -all

This command shows all configuration settings that are used by the database.
5. In the instance directory/sqllib directory, locate the db2nodes.cfg file. The
file contains an entry that shows the previous host name, for example:
0 tsmmon TSMMON 0
a. Update the entry with the new host name. The entry is similar to the
following entry:
0 tsmnew newhostname 0
b. Save and close the changed file.

Chapter 16. Taking the first steps after migration 429

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

Updating the tcpserveraddress option

To ensure that all clients and servers in the system can access the V7.1 server, you
must update the tcpserveraddress client option.

About this task

Set the tcpserveraddress option for all Tivoli Storage Manager clients that access
the migrated server, and for all servers that communicate with the migrated server.
The tcpserveraddress option must be set to the TCP/IP address of the migrated
Tivoli Storage Manager server.

For instructions, see the Backup-Archive Clients Installation and User's Guide.

Setting the IP address of the server

If you plan to use server-to-server communications, ensure that other servers in the
system can communicate with the V7.1 server. Update the high-level IP address of
the V7.1 server and set the IP addresses of the other servers in the system
accordingly.

Procedure

To update IP addresses for server-to-server communications, use Tivoli Storage

Manager administrative commands:
1. Update the IP address of the V7.1 server by using the SET SERVERHLADDRESS
command. For example, to set the IP address to 9.230.99.66, issue the following
command:
set serverhladdress 9.230.99.66
For more information about the SET SERVERHLADDRESS command and other
Tivoli Storage Manager administrative commands, see the Administrator's
Reference.
2. For each Tivoli Storage Manager server that will communicate with the V7.1
server, update the HLAddress parameter by issuing the UPDATE SERVER
command. For example, to set the server IP address to 9.230.99.66, issue the
following command:
update server server2 hladdress=9.230.99.66
3. If you are sharing libraries, complete the following steps:
a. Verify that the V7.1 server is operating as expected. For details, see
“Verifying the migration results” on page 426.

In the following three substeps, you are required to define the V7.1 server
for the library manager server and delete the V5 server definition. As a
result, you will not be able to revert to the V5 system.
b. On the library client server, define the V7.1 server for the library manager
server. For example, to define a server with an IP address of 9.230.99.66 and
a low-level address of 1500, issue the following command:
define server new_server_name serverpass=new_server_pass
hla=9.230.99.66_address lla=1500

where new_server_name specifies the name of the V7.1 server.

c. On the library client server, update the shared library by using the UPDATE
LIBRARY command:
update library library_name primarylibmanager=new_server_name

430 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

where library_name specifies the name of the shared library and

new_server_name specifies the name of the V7.1 server.
d. On the library client server, delete the previous library manager server
definition by using the DELETE SERVER command:
delete server v5_server_name

where v5_server_name specifies the name of the Tivoli Storage Manager V5

server.
e. On the library client server, set the password for communication between
servers by using the SET SERVERPASSWORD command:
set serverpassword lc_password

where lc_password specifies a password for the library client server.

f. On the library client server, reset the server verification key by using the
UPDATE SERVER command:
update server * forcesync=yes
g. Optional: On the library client server, verify that the library client server can
communicate with the library manager server by using the AUDIT LIBRARY
command:
audit library library_name checklabel=barcode

where library_name specifies the name of the shared library.

4. If you plan to use LAN-free data movement, configure the storage agent to
ensure that it can communicate with the V7.1 server. Use the DSMSTA
SETSTORAGESERVER command. For example, issue the following command:
dsmsta setstorageserver myname=storagnt mypassword=fun4me
myhladdress=agent.example.com servername=new_server_name
serverpassword=new_server_password
hladdress=high_level_address lladdress=low_level_address

In this example, the following variables are used:

v new_server_name specifies the name of the V7.1 server.
v new_server_password specifies the password for the V7.1 server.
v high_level_address specifies the high-level address of the V7.1 server.
v low_level_address specifies the low-level address of the V7.1 server.

Migrating data from tape to DISK or FILE devices

After the server migration, you can move the data from a tape device to a DISK or
FILE device. In this way, you might be able to provide faster access to the data.

Procedure
1. If you are moving data to a FILE device, define a FILE device class by using
the Tivoli Storage Manager administrative command DEFINE DEVCLASS. For
example, to define a device class named FILECLASS with a FILE device type and
a maximum capacity of 50 MB, issue the following command:
define devclass fileclass devtype=file maxcapacity=50m

For more information about the DEFINE DEVCLASS command and other Tivoli
Storage Manager administrative commands, see the Administrator's Reference.
2. Define a storage pool by using the Tivoli Storage Manager administrative
command DEFINE STGPOOL.

Chapter 16. Taking the first steps after migration 431

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

v For example, if you are moving data to a DISK device, to define a primary
storage pool named BACKUPPOOL, issue the following command:
define stgpool backuppool disk cache=yes nextstgpool=prog2

In this example, caching is enabled and PROG2 is specified as the primary

storage pool to which files are migrated.
v For example, if you are moving data to a FILE device, to define a primary
storage pool named FILEPOOL, issue the following command:
define stgpool filepool fileclass nextstgpool=prog3

In this example, PROG3 is specified as the primary storage pool to which files
are migrated.
3. Define a volume by using the administrative command DEFINE VOLUME. For
example, to define a volume of 4 MB named /home/tsminst1/jamesvol.dsm in a
storage pool named BACKUPPOOL, issue the following command:
define volume backuppool /home/tsminst1/jamesvol.dsm formatsize=4
4. To migrate data from tape to a DISK device, use the Tivoli Storage Manager
administrative commands MOVE DATA or MOVE NODEDATA, depending on where
the data is stored and how you want to move it. For example, to move files
from a storage pool volume named STGVOL.1 to storage pool BACKUPPOOL, issue
the following command:
move data stgvol.1 stgpool=backuppool
5. To migrate data from tape to a FILE device, use the Tivoli Storage Manager
administrative commands UPDATE STGPOOL and MIGRATE STGPOOL. For example,
to migrate data from the storage pool named LTOPOOL to the FILEPOOL storage
pool, issue the following commands:
update stgpool ltopool nextstgpool=filepool highmig=100
migrate stgpool ltopool lowmig=0

Restoring backup sets

If you copied backup sets to a temporary location before the migration, you might
want to move the backup sets to another location after the migration. You must
remove existing entries in the server database and then re-create the backup sets in
their new location.

Procedure
1. Delete the backup set entries from the server database by issuing the Tivoli
Storage Manager administrative command DELETE BACKUPSET. For example, to
delete a backup set entry named PERS_DATA.3099, issue the following command:
delete backupset pers_data.3099
For more information about the DELETE BACKUPSET command and other Tivoli
Storage Manager administrative commands, see the Administrator's Reference.
2. Re-create a backup set by issuing the Tivoli Storage Manager administrative
command DEFINE BACKUPSET. For example, to define the PERS_DATA backup
set that belongs to client node JANE, issue the following command:
define backupset jane pers_data devclass=agadm
volumes=vol1,vol2 retention=50
description="sector 7 base image"

432 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

In this example, volumes VOL001 and VOL002 contain the data for the backup
set. The backup set is retained on the server for 50 days. The volumes are to be
read by a device that is assigned to the AGADM device class. A description,
sector 7 base image, is included.

Updating automation
After you migrate the data, you might need to modify administrative schedules
that were defined in V5 because of changes in command syntax. Implement and
verify changes to any automation or scripts that were identified as requiring
modification in the planning process.

About this task

Important: Ensure that automation includes a backup of the database. Back up the
database at least once per day.

Beginning operations and monitoring the server

When you start running the Tivoli Storage Manager V7.1 server, monitor the space
that is used by the server. Ensure that the amount of space is adequate.

Procedure

To monitor the V7.1 server and make any required adjustments, complete the
following steps:
1. Monitor the active log to ensure that the size is correct for the workload that is
handled by the server instance.
When the server workload reaches its typical expected level, the space that is
used by the active log is 80% - 90% of the space that is available to the active
log directory. At that point, you might need to increase the amount of space.
Whether you must increase the space depends on the types of transactions in
the server workload. Transaction characteristics affect how the active log space
is used.
The following transaction characteristics can affect the space usage in the active
log:
v The number and size of files in backup operations
– Clients such as file servers that back up large numbers of small files can
cause large numbers of transactions that are completed quickly. The
transactions might use a large amount of space in the active log, but for a
short time.
– Clients such as a mail server or a database server that back up large
chunks of data in a few transactions can cause small numbers of
transactions that take a long time. The transactions might use a small
amount of space in the active log, but for a long time.
v Network connection types
– Backup operations that occur over fast network connections cause
transactions that are completed more quickly. The transactions use space
in the active log for a shorter time.
– Backup operations that occur over relatively slower connections cause
transactions that take a longer time to be completed. The transactions use
space in the active log for a longer time.

Chapter 16. Taking the first steps after migration 433

Migrating V5 servers on AIX, HP-UX, or Solaris systems to V7.1 on Linux

If the server is handling transactions with a wide variety of characteristics, the

space that is used for the active log might increase and decrease significantly
over time. For such a server, you might need to ensure that the active log
typically has a smaller percentage of its space used. The extra space allows the
active log to grow for transactions that take a long time.
2. Monitor the archive log to ensure that space is always available.

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

434 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 17. Troubleshooting the migration of a V5 server from
AIX, HP-UX, or Solaris
In case you encounter issues during or after the migration, instructions are
available for reverting the server to its previous version.

Reverting from V7.1 to the previous V5 server version

If you follow the steps in the migration procedure, you can revert to the V5 server
at any point along the migration path.

Before you begin

Requirement: The V5 server must remain installed on the original system

throughout the migration process.

Procedure

To restore the V5 server, complete the following steps:

1. On the V5 system, for each sequential-access storage pool on tape, set the
REUSEDELAY parameter to the number of days during which you want to be able
to revert to the V7.1 server, if necessary.
For example, if you want to be able to revert to the V7.1 server for up to 30
days after you revert to V5, set the REUSEDELAY parameter to 31 days. Issue the
following administrative command:
update stgpool sequential_access_storage_pool reusedelay=31

where sequential_access_storage_pool specifies the name of the storage pool. By

specifying the REUSEDELAY parameter, you can help prevent backup-archive
client data loss.
For more information about the UPDATE STGPOOL command and other Tivoli
Storage Manager administrative commands, see the Administrator's Reference.
2. For all tape volumes that were used by the V5 server, specify readwrite access
mode. Issue the following administrative command:
update volume tape_volume access=readwrite

where tape_volume specifies the name of the tape volume.

3. For each copy storage pool that was used by the V5 server, change the value of
the RECLAIM parameter from 100 to the value that was set before the migration.
Issue the following administrative command:
update stgpool copy_storage_pool reclaim=reclaim_value

where copy_storage_pool is the name of the copy storage pool and reclaim_value
is the reclamation value that was used before the migration.
4. Start the V5 server by issuing the following administrative command:
./dsmserv

© Copyright IBM Corp. 2009, 2013 435

436 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Part 3. Migrating Tivoli Storage Manager V5 servers on z/OS
systems to V7.1 on AIX or Linux on System z
An IBM Tivoli Storage Manager V5 server that runs on a z/OS system can be
migrated to a V7.1 server that runs on AIX or Linux on System z. During the
migration, IBM Tivoli Storage Manager for z/OS Media must be installed on the
V5 server to ensure continued access to data stored on the z/OS system.

About this task

The cross-platform migration offers the following advantages:

v Client data that is stored on the z/OS system can be accessed from the Tivoli
Storage Manager V7.1 server through Tivoli Storage Manager for z/OS Media.
You can retain existing storage hardware that uses Fiber Connector (FICON®)
channel technology.
v The Tivoli Storage Manager V7.1 system can be expanded by using either z/OS
or UNIX storage systems.

The process for migrating the Tivoli Storage Manager server from a z/OS
operating system to AIX or Linux on System z is similar to the upgrade process
from Tivoli Storage Manager V5 to V7.1 on the same operating system. For the
cross-platform migration, you must complete additional steps to ensure that data
on z/OS systems can be accessed from the Tivoli Storage Manager V7.1 server.

© Copyright IBM Corp. 2009, 2013 437

438 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 18. Migration overview
Before starting the cross-platform migration, review the migration road map, the
scenarios for migration, and related information so that you can plan the migration
process.

Migration road map

The migration road map provides links to information to help you plan, prepare,
and complete the migration process.

To plan and prepare for the migration process, complete the following steps:
1. Review information about the Tivoli Storage Manager for z/OS Media product.
For details, see the Tivoli Storage Manager for z/OS Media Installation and
Configuration Guide.
2. Review the migration scenarios: Scenarios for migrating a server from a z/OS
system to AIX or Linux on System z.
3. Familiarize yourself with the major phases in the migration process: “The
migration process” on page 443.
4. Read about the changes that can be expected in the system following the
migration: “Operational changes and requirements” on page 453.
5. Review the guidelines for planning the migration: Chapter 19, “Planning the
migration,” on page 455.
6. Select the migration method to use, and plan for the hardware, software, and
storage space requirements for your server and environment.
7. Complete the preparation steps: Chapter 20, “Preparing for the migration,” on
page 473.

To migrate and configure the system, complete the following steps:

1. Follow the migration instructions: Chapter 21, “Migrating the z/OS server
database to the V7.1 server,” on page 491.
2. Configure the z/OS media server devices: Chapter 22, “Configuring the z/OS
media server devices on the new server,” on page 497.
3. Complete the migration process: Chapter 23, “Taking the first steps after the
migration,” on page 499.

Scenarios for migrating a server from a z/OS system to AIX or Linux

on System z
You can migrate the server by using the media method, the network method, or a
hybrid upgrade-migration method.

With the media method, you extract data from the original database to media, and
then load the data into the new database. The following figure illustrates the
media method.

© Copyright IBM Corp. 2009, 2013 439

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Migrate to a V7 system using

the media method
1. Install the V7 server.

3. Upgrade Tivoli Storage Manager to

V5.5.6 or later.
2. Create the directories and the user ID for the
new server instance.

4. Install Tivoli Storage Manager for

z/OS Media.

10. Create and format the database. Run the db2icrt

command and the DSMSERV LOADFORMAT utility.
5. Define a server to correspond to Tivoli
Storage Manager for z/OS Media.

6. Analyze the V5 server. Run the

ZMSPREPARE command.
11. Load the extracted data into the new database.
Run the DSMSERV INSERTDB utility.

12. Configure the system for a database backup.

7. Back up the V5 database to tape.

13. Configure the z/OS media server devices.

8. Prepare the V5 database. Run the

DSMUPGRD PREPARE utility.

14. Re-create disk-based storage pools.

9. Extract the V5 database to external media.
Run the DSMUPGRD EXTRACTDB utility.

15. Complete post-migration steps.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager for
for z/OS server AIX or Linux server

Figure 13. Migrating the server by using the media method

For information about selecting an appropriate level for a V5 server before a

migration, see “Determining the appropriate level for a V5 server before an
upgrade” on page 36.

440 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

With the network method, you simultaneously extract data from the original
database and load the data into the new database. The following figure illustrates
the network method.

Chapter 18. Migration overview 441

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Migrate to a V7 system using

the network method
1. Install the V7 server.

3. Upgrade Tivoli Storage Manager to

V5.5.6 or later.
2. Create the directories and the user ID for the
new server instance.

4. Install
Media.
Tivoli Storage Manager for z/OS

9.Create and format the database. Run the db2icrt

command and the DSMSERV LOADFORMAT utility.
5. Define a server to correspond to Tivoli
Storage Manager for z/OS Media.

6. Analyze the V5 server. Run the

ZMSPREPARE command.
10. Ensure that the server can receive the database.
Run the DSMSERV INSERTDB utility.

12. Configure the system for a database backup.

7. Back up the V5 database to tape.

13. Configure the z/OS media server devices.

8. Prepare the V5 database. Run the

DSMUPGRD PREPARE utility.

14. Re-create disk-based storage pools.

Extract and move the database. Run
11. the DSMUPGRD EXTRACTDB utility.

15. Complete post-migration steps.

Version 5 Tivoli Version 7 Tivoli

Storage Manager Storage Manager for
for z/OS server AIX or Linux server

Figure 14. Migrating the server by using the network method

For information about selecting an appropriate level for a V5 server before a

migration, see “Determining the appropriate level for a V5 server before an
upgrade” on page 36.

442 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Expert users might want to use a third option, the hybrid upgrade-migration
method, for migrating the server. The hybrid upgrade-migration method uses a
combination of export and import operations along with standard V7 upgrade
methods. For information about the hybrid upgrade-migration method, and for a
comparison of all three options, see “Comparison of database migration methods”
on page 452.

After completing the cross-platform migration steps, you have more flexibility in
terms of data storage. You can select from the following main options:
v You can continue to use the z/OS system for data storage. In this case, the data
is stored on tape volumes, and the contents are accessed by using FICON
attached storage devices.
v You can gradually move the data from the z/OS storage system, and use the
V7.1 system on AIX or Linux on System z for data storage.
Related concepts:
“Migration process overview” on page 444
“Key tasks in the migration process” on page 446
“Comparison of database migration methods” on page 452

Tivoli Storage Manager for z/OS Media overview

With IBM Tivoli Storage Manager for z/OS Media, you can use a Tivoli Storage
Manager V7.1 system to access data that is stored on a z/OS system.

The Tivoli Storage Manager for z/OS Media server gives the Tivoli Storage
Manager server access to sequential storage media on the z/OS system. The z/OS
media server manages the tape storage that was used by the Tivoli Storage
Manager V5 server on the z/OS system.

Only Tivoli Storage Manager V7.1 servers that are running on AIX or Linux on
System z operating systems can work with Tivoli Storage Manager for z/OS
Media.

For more information, go to the Tivoli Storage Manager V6.3 Information Center at
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3 and see the section about
integrating storage from Tivoli Storage Manager for z/OS Media.
Related concepts:
“Migration process overview” on page 444

The migration process

Migrating from Tivoli Storage Manager V5 running on z/OS to V7.1 on AIX or
Linux on System z requires considerable planning. Before you begin, familiarize
yourself with the migration overview, the key tasks in the migration process, and
the utilities that are used for migration.

Chapter 18. Migration overview 443

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Migration process overview

Before starting the migration process, be aware of the restrictions that apply, and
review the descriptions of system operations before and after the migration.

The following restrictions apply to the migration:

v The V5 server running on z/OS can be migrated only to an AIX or Linux on
System z system.
v Client data that is stored in server storage pools on tape can remain on the
existing z/OS system, but database information must be migrated. Client data
that is stored on random-access disks or existing FILE storage pools must be
moved to tape before the migration begins.
Before the migration, the Tivoli Storage Manager V5 server uses FICON attached
storage devices to access z/OS storage media.

The following figure illustrates operations before the migration.

zSeries

z/OS LPAR

Tivoli Storage
Manager
server

LAN
z/OS FICON
attachment
Tivoli Storage
Manager backup-
archive client

z/OS storage media

Figure 15. Operations before the migration

After you migrate your system to a V7.1 server on AIX, the Tivoli Storage Manager
V7.1 server uses Tivoli Storage Manager for z/OS Media to access z/OS storage
media.

The following figure illustrates the system after migration to a V7.1 server on AIX.

444 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

High speed connection

LAN pSeries AIX zSeries z/OS

Tivoli Storage
Manager
server
Media
server

DB2

z/OS FICON
attachment

Tivoli Storage
Manager
backup-archive
client

z/OS storage media

Figure 16. Operations after migration to a V7.1 server running on AIX

After you migrate your system to a V7.1 server on Linux on System z, the Tivoli
Storage Manager V7.1 server uses Tivoli Storage Manager for z/OS Media to
access z/OS storage media.

The following figure illustrates the system after the migration to a V7.1 server on
Linux on System z.

Chapter 18. Migration overview 445

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

zSeries
Hipersocket

LAN Linux on System z LPAR z/OS LPAR

Tivoli Storage
Manager
server
Media
server

DB2

z/OS FICON
attachment

Tivoli Storage
Manager
backup-archive
client

z/OS storage media

Figure 17. Operations after migration to a V7.1 server running on Linux on System z

Related concepts:
“Key tasks in the migration process”
“Device migration” on page 448
“Comparison of database migration methods” on page 452

Key tasks in the migration process

The migration process includes installing Tivoli Storage Manager for z/OS Media
on the V5 source server and installing Tivoli Storage Manager V7.1 on the target
server. Other tasks include backing up data, and then migrating data from the V5
source server to the V7.1 target server.
1. Prepare the system for migration.
a. On the target server, install Tivoli Storage Manager V7.1 and configure a
database instance.
b. On the source server, upgrade Tivoli Storage Manager to V5.5.6 or later.
c. On the source server, install Tivoli Storage Manager for z/OS Media.
d. On the source server, use the ZMSPREPARE command to analyze the server
and generate a report. The information in the report will help to identify the
steps that must be completed before migration.
e. Back up, move, or delete data that is stored on DISK or FILE storage pools.
Prevent new data from being stored on DISK or FILE storage pools.
f. Back up the source server database to tape.

446 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Important: Ensure that a full database backup is available onsite. A backup

is essential if the migration process is interrupted or rolled back. The backup
must be stored on tape because FILE volumes cannot be in use during the
migration process.
2. Move the data from the source database to the target database.
3. Complete device configuration and related tasks.
a. Add new devices to the target server as needed by the Tivoli Storage
Manager for z/OS Media server.
b. Define new DISK and FILE storage pools on the target server. Restore data
from the backups of the DISK and FILE storage pools that were on the
z/OS system.
c. If any z/OS DISK or FILE volumes were marked as destroyed, delete those
volumes.

Utilities and commands for data migration

Tivoli Storage Manager provides utilities and a command to help you move data
from a V5 system running on z/OS to the Tivoli Storage Manager V7.1 system
running on AIX or Linux on System z.

Use the following utilities for data migration:

DSMUPGRD EXTRACTDB
The DSMUPGRD EXTRACTDB utility extracts data from the server database.
DSMSERV INSERTDB
The DSMSERV INSERTDB utility moves extracted data into a new database.
DSMSERV LOADFORMAT
The DSMSERV LOADFORMAT utility formats an empty database in preparation
for inserting extracted data into the empty database.
DSMUPGRD PREPAREDB
The DSMUPGRD PREPAREDB utility prepares the database for migration by
verifying that all premigration tasks are completed.

Use the following command for data migration:

ZMSPREPARE
The ZMSPREPARE command analyzes the V5 server and provides data to
help you identify steps to be completed before the migration.

Many of the utilities and commands that are used for server upgrade are also used
for server migration. For more information, see Appendix B, “Utilities, scripts, and
commands for server upgrade and migration,” on page 521.
Related reference:
“ZMSPREPARE (Prepare a server on a z/OS system for migration)” on page 541
Related information:
DSMUPGRD EXTRACTDB
DSMUPGRD PREPAREDB (Prepare a server database for upgrade)

Chapter 18. Migration overview 447

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Device migration
You must migrate devices to ensure that the Tivoli Storage Manager V7.1 server
running on AIX or Linux on System z can access files stored on a z/OS system. An
overview of device migration is provided.

The process for device migration varies, depending on the device type and the
type of data that is stored:
v Migrate tape devices by using utilities.
v Migrate data that is stored on disks and data that is written to FILE device
classes by completing manual steps. The manual steps include backing up data
and deleting the volumes and pools that are no longer required.

Backing up primary storage pools on disk

Ensure that you have tape volumes available for backing up data that is stored by
using DISK or FILE devices:
v At a minimum, tape volumes must be available for backing up the primary
storage pool.
v To optimize the process, create a second, onsite backup of the primary storage
pool. By creating one backup storage pool offsite and another onsite, you fulfill
disaster recovery requirements for offsite storage. At the same time, volumes
from the second pool are available onsite to restore data immediately after
migration.

After the disk primary storage pool volumes are backed up, mark them as
destroyed. By taking this step, you will make it possible to implement backup and
restore procedures that minimize migration time. In addition, it will be easier to
revert to the V5 system if necessary.

Backing up non-primary storage pools on disk

For copy storage pools and active-data storage pools that are written to FILE
device classes, you will back up or reassign the data to new storage pools. Then,
you will delete the data on disks.

For non-storage pool data that is written to FILE device classes, you will remove
the following types of data: database backups, database snapshots, database
memory dumps, recovery plan files, export volumes, and backup sets. You will not
remove sequential storage pool volumes.

Conversion of z/OS device classes

As part of the migration process, the DSMSERV INSERTDB utility converts z/OS
device classes into AIX or Linux on System z device classes. The conversion of
device classes takes place in the following way:
v The DISK device class is mapped to the predefined DISK device class for the
AIX or Linux on System z server.
v All device classes with the device type SERVER are converted to the AIX or
Linux on System z equivalent.
v FILE device class attributes that are specific to the z/OS operating system are
discarded during migration because the newly installed z/OS media server does
not support the previously used FILE device type. Instead, new FILE device
classes must be defined after the migration to use sequential FILE storage via
the z/OS media server.

448 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

v Tape and FILE device classes are set up to use the z/OS media server in the
following way:
– Tape device classes that are not configured for LAN-free access are updated
to use the z/OS media server. The DSMSERV INSERTDB utility defines a new
library and path for each device class, and sets up the libraries to access the
z/OS media server.
– Tape device classes that are configured for LAN-free access do not remain
configured for LAN-free access. These tape device classes all have shared or
external libraries that are associated with them. The libraries are deleted and
replaced with libraries and paths that support access through the z/OS media
server. After the migration, tape device classes that were configured for
LAN-free access use the z/OS media server to communicate by using a LAN.
The Tivoli Storage Manager storage agent facilitates this communication.
– Device class attributes that are common across z/OS, AIX, and Linux on
System z platforms are preserved.
– Device class attributes that are used only for z/OS are carried over into new
device class attributes used by the z/OS media server.
– Device class attributes that are used on AIX and Linux on System z systems,
but that did not exist on the z/OS system, are set to usable default values.

Role of Tivoli Storage Manager for z/OS Media

After the migration, Tivoli Storage Manager for z/OS Media takes over the
management of tape data that was stored on the V5 server running on z/OS. For
this reason, you must install Tivoli Storage Manager for z/OS Media on the V5
server during the preparation phase. In addition, you must use the DEFINE SERVER
command to define a new server on the V5 server to correspond to the z/OS
media server. The new server is used during the migration phase to access
upgrade media. After the migration is complete, the server is used to access client
data stored on tape.

The following graphic illustrates how Tivoli Storage Manager uses the z/OS media
server to access z/OS storage media.

Chapter 18. Migration overview 449

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

AIX or z/OS
Linux on System z

Tivoli Storage
Manager server Media
server

DB2

FICON
Fibre Channel Protocol attachment
attachment

Local Fibre Channel z/OS media server

Protocol storage media storage media

Figure 18. Role of z/OS media server in the migrated system

Status of tape volumes

The DSMSERV INSERTDB utility changes the status of all tape volumes whose status is
FILLING to FULL. This change is required because the z/OS media server cannot
append to tape volumes that were originally written by Tivoli Storage Manager
running on z/OS.

Backup sets
Review the backup set information to understand which backup sets defined on
the V5 server before the migration are usable after the migration.

Backup sets that use tape devices are migrated automatically.

Backup sets that use FILE device classes are not migrated. Backup sets that use
FILE device classes cannot be regenerated, moved, or accessed after the migration.

During the migration process, you can use the ZMSPREPARE command to generate a
list of backup sets that use FILE device classes. After that, you can use the DELETE
BACKUPSET command to delete each backup set that uses a FILE device class.
Related reference:
“ZMSPREPARE (Prepare a server on a z/OS system for migration)” on page 541

450 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Effects of migration on storage agents

After the system is migrated, a storage agent that is installed on a Tivoli Storage
Manager client can send data to and receive data from storage devices that are
attached to a z/OS media server.

LAN-free data movement to and from z/OS storage devices is not possible.
Instead, the storage agent that is installed on the Tivoli Storage Manager client
communicates with the z/OS media server by using a LAN. Client data can be
read or written by using z/OS media server file or tape storage without the data
passing through the Tivoli Storage Manager server. The following figure illustrates
the communication channels.

Tivoli Storage
Manager
backup- z/OS
archive client media
DB2 server
Storage
agent
Tivoli Storage
Manager server
Client data

Metadata

FICON

LAN
Client data

Tape library
z/OS FICON
SAN channel-attached
tape drives

Figure 19. Storage agent communicating with the z/OS media server by using a LAN

Requirement: To connect to a V7.1 server in a system that uses the z/OS media
server, storage agents must be at V7.1. If you have storage agents at earlier
versions, upgrade them to V7.1 as part of the migration process.

For more information about data movement in a z/OS media server environment,
see the Storage Agent User's Guide.

Chapter 18. Migration overview 451

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Protection for client data and the server during the process
To protect client data and the server, ensure that you back up storage pools and
the server database before starting the migration process. You will need these files
if you must revert to the previous Tivoli Storage Manager version.

The server migration instructions provide detailed information about the backup
tasks that must be completed. The two main backup tasks are listed here:
v “Backing up configuration information” on page 474
v “Backing up the server database” on page 488

Tip: When you back up the database, make two copies to protect the backup from
media failures. Ensure that at least one full database backup is available onsite. If
you must restore the database after a failed upgrade, having an onsite backup
saves time.

For more information about protecting the database, see “Database protection and
recovery” on page 5.

Important: Do not uninstall the V5 server on the z/OS system until you verify
that the migration to V7.1 was successful.

Comparison of database migration methods

You can move the V5 database to the new V7.1 system by using the media
method, the network method, or the hybrid upgrade-migration method. The
hybrid upgrade-migration method combines database migration with export and
import operations.

Comparison of the media and network methods

The standard way to migrate the database is to use the media method or the
network method:
Media method
You must extract data from the original database to media, and later load
the data into the new database.
Use this method if you cannot connect the V5 system and the V7.1 system
by using a high speed network.
Network method
You must simultaneously extract data from the original database and load
the data into the new database.
Use this method if your system requires maximum performance from the
upgrade utility, and the systems are connected by a high speed network.

With either method, the original server cannot be running while the data is being
extracted. You can expect the Tivoli Storage Manager server to be unavailable for
hours or days. The downtime depends on several factors, including the size of the
database and the performance of the disk system that contains the previous
database and new database.

452 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Hybrid upgrade-migration method

If it is important to migrate the system with a minimum of downtime, you might

want to use the hybrid upgrade-migration method. This method uses a
combination of export and import operations, along with the standard upgrade
methods. It requires detailed planning.

Before you decide to employ the hybrid upgrade-migration method, estimate the
time that it takes to migrate the data by using one of the standard methods versus
the hybrid method. The standard method applicable to your situation might take
less time than the hybrid upgrade-migration method.

For a general description of the hybrid upgrade-migration method, see the white
paper in the Tivoli Storage Manager wiki at https://www.ibm.com/
developerworks/community/wikis/home/wiki/Tivoli Storage
Manager/page/Tivoli Storage Manager Version 6 Hybrid Upgrade Migration
Method.
Related concepts:
“Scenarios for migrating a server from a z/OS system to AIX or Linux on System
z” on page 439

Operational changes and requirements

To prepare for changes in the Tivoli Storage Manager system following the
migration, review the operational changes and requirements.

For a general description of operational changes following an upgrade to V7.1, see

“Operation changes” on page 4. For a description of changes that are specific to a
migration from z/OS to a system running on AIX or Linux on System z, see the
following topics.

Automated message response systems

The z/OS operating system includes an automated message response feature. If
you set up automated message responses for the V5 server and its messages with
the ANR prefix, you might want to do the same for the newly installed z/OS
media server and its messages with the ANZ prefix.

For a list of ANZ messages, see the section that describes Tivoli Storage Manager
for z/OS Media messages in the Tivoli Storage Manager V6.3 Information Center
at http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3.

Performance considerations
Migration to the Tivoli Storage Manager V7.1 server running on AIX or Linux on
System z can result in different network throughput requirements as compared to
the V5 system on z/OS. After the migration, you might see an increase in the
amount of data transferred over networks connected to the Tivoli Storage Manager
server. To optimize server performance, review the guidelines in this section and
plan the migration accordingly.

Before setting up a network connection between the Tivoli Storage Manager server
and the z/OS media server, consider the following points:
v For client connections used to back up, archive, restore, and retrieve data, the
V7.1 server generally requires the same network bandwidth as the V5 server

Chapter 18. Migration overview 453

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

running on a z/OS system. This is based on the assumption that the migrated
V7.1 server protects the same clients as the V5 system.
v More network bandwidth is required for operations that store or retrieve data
by using the z/OS media server than for operations that use a local disk or tape.
v To optimize performance, use dedicated networks for connections between the
V7.1 server and the z/OS media server. Use technologies that optimize network
performance and efficiency, such as jumbo frames and HiperSockets™.
HiperSockets can be used for connections between Linux and z/OS logical
partitions located on the same System z central processor complex.
v To increase the network bandwidth between the V7.1 server and the z/OS media
server, consider setting up multiple interfaces specified on a single server
definition. You can use a comma-delimited expression for the TCP/IP address,
as in this example:
define server ...
hladdress=10.10.48.1,10.10.56.1
lladdress=1500...

If this method is used, data can be stored or retrieved by using any available
network interface. You are not required to distribute storage requirements over
several device classes. This method increases the available network bandwidth
and supports network connection failover and load balancing.
v To optimize network performance when using the z/OS media server, ensure
that both the z/OS and the Tivoli Storage Manager server systems can use a
large TCP/IP window size. On z/OS, this means that the TCPIP.PROFILE
TCPCONFIG statement includes the TCPMAXRCVBUFRSIZE parameter, which is set to
the default value of 256 K or greater. On AIX, this means that the network
tuning parameter rfc1323 is set to 1, which is not the default value. On Linux,
this means that the kernel parameter net.ipv4.tcp_window_scaling is set to the
default value of 1.
v To reduce network bandwidth requirements, store backup and archive data to a
V7.1 server local disk pool. Then use storage pool backup and storage pool
migration to copy and move the data to z/OS media server tape storage. This
method requires less network bandwidth than backing up or archiving the data
directly to the z/OS media server FILE device class storage, and then moving
the data to z/OS tape storage.
v If you store the data by using the z/OS media server, the single-session backup
throughput might be 80% of the throughput expected when storing the data by
using local storage devices. For example, assume that the throughput for
backing up a large amount of data is 30 MB per second for a V5 server running
on a z/OS system. Following the migration to the V7.1 server running on AIX or
Linux on System z with a z/OS media server, the throughput might be reduced
to 80%, or 24 MB per second.
v Consider using the Tivoli Storage Manager storage agent installed on the client
system with the LAN-free communication method to back up or archive data to
the z/OS media server directly. This method might reduce the network
bandwidth requirements on the V7.1 server and increase backup throughput.

454 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 19. Planning the migration
Planning for the migration to Tivoli Storage Manager V7.1 is important because, in
addition to installing the new software, you must move the contents of the V5
server database into the V7.1 server database.

About this task

Tivoli Storage Manager V5 servers can be upgraded directly to V7.1. However,

Tivoli Storage Manager V7.1 servers cannot be used with V5 clients or with other
servers in the system that are at V5. Unless all V5 clients and V5 servers can be
upgraded at the same time, consider upgrading the server to a level that can be
used with V5 clients and V5 servers. Then, upgrade all servers and clients to V7.1
when possible. For information about the levels of the Tivoli Storage Manager
server that can be used with V5 clients and V5 servers, see the following technotes:
IBM Tivoli Storage Manager Server-Client Compatibility and Upgrade
Considerations
(http://www.ibm.com/support/docview.wss?uid=swg21053218)
Storage-agent and library-client compatibility with the IBM Tivoli Storage
Manager server
(http://www.ibm.com/support/docview.wss?uid=swg21302789)

When you move data from a V5 server database to a V7.1 database, a large
amount of system processing capacity is used. The move also requires a large
amount of I/O activity.

In your planning, consider testing the migration process on nonproduction

systems. Testing provides information about how long the migration of the server
database takes, which will help you to plan for the time that the server will be
unavailable. Some databases might take much longer than others to migrate.

Testing also gives you more information about the size of the new database
compared to the original, giving you more precise information about database
storage needs.

If you have multiple servers, consider migrating one server first, to determine how
the migration process will work for your data. Use the results of the first migration
process to plan for migrating the remaining servers.

Hardware and software requirements for the V5 and V7.1 servers

Before you start the migration process, ensure that the system meets hardware and
software requirements for the V5 server and the V7.1 server.

During the migration process, you must upgrade the V5 server on z/OS to V5.5.6
or later. Follow the guidelines in “Determining the appropriate level for a V5
server before an upgrade” on page 36. Tivoli Storage Manager V5.5 servers on
z/OS are supported at z/OS V1R7, z/OS V1R8, or later.

For information about hardware and software requirements for a V7.1 server that
is running on AIX, see “Server requirements on AIX systems” on page 21.

© Copyright IBM Corp. 2009, 2013 455

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

For information about hardware and software requirements for a V7.1 server that
is running on Linux on System z, see “Server requirements for Linux on System z
systems” on page 29.

For the latest information about hardware and software requirements, see the
Tivoli Storage Manager Supported Operating Systems technote at
http://www.ibm.com/support/docview.wss?uid=swg21243309.

Compatibility with other components and versions

You can install other products that deploy and use DB2 products on the same
system as the Tivoli Storage Manager Version 7.1 server running on AIX or Linux
on System z.

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

456 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

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

To segregate resources and provide more

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

Estimating database and recovery log requirements

Estimate the space requirements for the migration process, and the space
requirements for the server databases and recovery log for the V7.1 server. The
space requirements for a cross-platform migration from V5 to V7 are similar to the
space requirements for an upgrade from V5 to V7 on the same operating system.

Procedure
1. Estimate the space requirements for the V5 server system. For details, see
“Space requirements for the V5 server system” on page 37.
2. Estimate the space requirements for the V7.1 server system. For details, see
“Space requirements for the V7 server system” on page 38.
3. Estimate the total space for the migration process and the V7.1 server. For
details, see “Estimating total space requirements for the upgrade process and
upgraded server” on page 39. If you are planning to migrate the data by using
the media method, review the information under Chapter 6, “Scenario 3: New
system, media method,” on page 177. If you are planning to migrate the data
by using the network method, review the information under Chapter 7,
“Scenario 4: New system, network method,” on page 225.
4. Optional: Use a worksheet to plan the amount and location of space for the
V7.1 server. For details, see “Worksheet for planning space for the V7.1 server”
on page 42.

Chapter 19. Planning the migration 457

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Planning data movement from FILE and DISK devices

The V7.1 server cannot access data that is stored by using DISK or FILE devices on
the z/OS server. This restriction means that data that is stored on DISK or FILE
devices must be backed up to tape before the migration begins.

About this task

Ensure that you have tape volumes available for backing up data that is stored by
using DISK or FILE devices:
v At a minimum, tape volumes must be available for backing up the primary
storage pool.
v To optimize the process, tape volumes should be available to create a second,
onsite backup of the primary storage pool. By creating one backup storage pool
offsite and another onsite, you fulfill disaster recovery requirements for offsite
storage. At the same time, volumes from the second pool are available onsite to
restore data immediately after migration.

As the first step in the preparation process, you will run the ZMSPREPARE command.
The ZMSPREPARE command will be used to identify all DISK and FILE device type
storage pools and the volumes and amount of data that must be backed up to
tape.

Any backup sets on FILE storage must be deleted.

Related reference:
“ZMSPREPARE (Prepare a server on a z/OS system for migration)” on page 541

Estimating storage and device requirements

Estimate the amount of space that will be required for data storage in the new
Tivoli Storage Manager V7.1 system. Plan the devices to be used for storage.

Procedure
1. Estimate the storage requirements for the new Tivoli Storage Manager V7.1
system. For instructions, see the section that describes estimating space needs
for sequential-access storage pools in the Administrator's Guide.
2. Plan the device requirements for the new Tivoli Storage Manager V7.1 system.
For instructions, see the section about configuring and managing storage
devices in the Administrator's Guide.

Estimating the time required for migration

The V5 server is not available for use during migration operations. To help plan
for the amount of time that the server will be unavailable, estimate the migration
time. The time that is required to complete the migration of a V5 server depends
on multiple factors.

About this task

The following factors can affect the migration time:

v The size of the database that is being migrated.
v The number and speed of system processors.

458 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

v The configuration of storage devices. If new hardware is being introduced, time

is required to define the new devices to the server, test the configuration, and
adjust storage pools.
v The method that is chosen for moving the data from the V5 database to the V7
database (media or network). The network method for the data movement
overlaps the extraction time with the insertion time. Using the network method
might help reduce the total time that is required for the migration because of the
overlap.
v The type of workload that the server has handled. A workload that consists of
large numbers of small files, or files with long file names, can cause a relatively
longer migration time.

Procedure

When you estimate the time it might take to migrate the system, consider the data
that is available for upgrade operations from Tivoli Storage Manager V5 to V6 on
the same operating system. This information might help you estimate the time that
is required for a cross-platform migration.

For example, in benchmark environments in IBM labs, upgrade operations

achieved 5 - 10 GB per hour by using the network method. This rate is based on
the amount of space that is used by the V5 database, not the allocated space for
the database. Your environment might produce different results. Results are
dependent on system configuration. If you use the media method, the rate is
decreased.

Estimate the time that is required to migrate your system based on the amount of
data in the server database.

Results

Your estimate might be higher than the actual time that is required. Because of the
way that databases are structured, the amount of data that the extraction utility
extracts might be much less than the total amount of space that is used by the
database.

What to do next

Test migration operations for Tivoli Storage Manager servers that are used by
essential systems.

Example: Estimating the migration time based on the

database size
You can roughly estimate the time required for the migration based on the amount
of data in the V5 database. To this estimate, add the time required for additional
tasks, such as storage device configuration.

Procedure
1. To obtain details about the V5 database, issue a command.
v If the V5 server is running, issue the command:
query db format=detailed
v If the V5 server is not running, use the upgrade utility:
dsmupgrd querydb

Chapter 19. Planning the migration 459

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Here is an example of the output obtained when the server is running, and the
query db format=detailed command is issued:
Available Space (MB): 39,960
Assigned Capacity (MB): 37,992
Maximum Extension (MB): 1,968
Maximum Reduction (MB): 8,360
Page Size (bytes): 4,096
Total Usable Pages: 9,725,952
Used Pages: 7,584,387
Pct Util: 78.0
Max. Pct Util: 78.0
Physical Volumes: 10
Buffer Pool Pages: 8,192
Total Buffer Requests: 180,003
Cache Hit Pct.: 99.81
Cache Wait Pct.: 0.00
Backup in Progress?: No
Type of Backup In Progress:
Incrementals Since Last Full: 0
Changed Since Last Backup (MB): 67.63
Percentage Changed: 0.23
Last Complete Backup Date/Time: 05/18/11 23:16:26
Estimate of Recoverable Space (MB):
Last Estimate of Recoverable Space (MB):

Here is an example of the output obtained when the server is not running, and
the dsmupgrd querydb utility is run:
Available Space (MB): 39,960
Assigned Capacity (MB): 37,992
Maximum Extension (MB): 1,968
Maximum Reduction (MB): 8,360
Page Size (bytes): 4,096
Total Usable Pages: 9,725,952
Used Pages: 7,584,383
Pct Util: 78.0
Max. Pct Util: 78.0
Physical Volumes: 10
Buffer Pool Pages: 8,192
Total Buffer Requests: 179,946
Cache Hit Pct.: 99.81
Cache Wait Pct.: 0.00
Backup in Progress?: No
Type of Backup In Progress:
Incrementals Since Last Full: 0
Changed Since Last Backup (MB): 67.63
Percentage Changed: 0.23
Last Complete Backup Date/Time: 05/19/11 06:16:26
Estimate of Recoverable Space (MB):
Last Estimate of Recoverable Space (MB):

2. To calculate the amount of data in the database, use the results of the query
command. Multiply the number of used pages by the page size.
Using the results in the example, you can calculate the amount of data in this
database:
7,584,383 used pages × 4096 bytes/page = 31,065,632,768 bytes, or 28.9 GB
3. Estimate the time required for the upgrade operation by dividing the amount
of data by the expected rate.
For example, by using rates of 5 GB/hour and 10 GB/hour:
28.9 GB ÷ 5 GB/hour = 5.8 hours
28.9 GB ÷ 10 GB/hour = 2.9 hours
Related reference:
“DSMUPGRD QUERYDB (Display information about a V5 database)” on page 522

460 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Performance tips for the V5 database extraction process

Review the performance tips for the V5 database extraction process so that you can
minimize the time that is required for the migration. In this way, you can reduce
the time that the Tivoli Storage Manager server is unavailable.

The speed of the extraction process is typically limited by the speed of I/O to the
destination for the extracted data. The length of time that the process runs also
depends on the size of the database. The time will be approximately as long as the
time required for a full backup of the database.

Do not reorganize the Tivoli Storage Manager V5 database before the migration.
The extraction process can achieve faster throughput when the source database
does not contain long sequences of pages that are allocated to a single database
table. This tip applies to both the media method and the network method.

The following performance tips depend on the method that you choose for moving
the data from the V5 database.
Media method
If you are using the media method, consider the following tips:
v If you are extracting the data to tape, use a high-speed tape device. For
example, select a device with a transfer rate of at least 1000 MB per
second.
v If both the V5 database and the destination for the extracted data are on
a virtualization device (high-end storage controller, or a SAN
virtualization device), ensure that the two virtual LUNs are not on the
same physical disk drive. Ensure that the space for the V5 database and
the destination for the extracted data are on different physical disk
drives within the virtualization device.
v If it is not possible to provide different LUNs for the V5 database and
the extraction destination, the extraction process will take more time.
The slower speed of extraction might be acceptable, depending on the
size of the database and your requirements for the migration.
Network method
If you are using the network method, consider the following tip:
v Use a high-speed link. If you are migrating a database that is larger than
2 - 3 GB, use at least a 1-gigabit (Gb) Ethernet network.
Related concepts:
“Comparison of database migration methods” on page 452

Performance tips for inserting data into the V7.1 database

The process for inserting the V5 extracted data into the V7.1 database is the
longest-running part of a migration process, and is the most sensitive to the
configuration of the system.

On a system that meets only the minimum requirements, the insertion process will
run, but performance might be slow. For better performance, set up the system as
described in the following tips:
Processors
The insertion process is designed to use multiple processors or cores. The
insertion process typically performs better on a system with a relatively
small number of fast processors. If the system has many slow processors,
you might experience reduced performance levels.

Chapter 19. Planning the migration 461

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Disk storage
The insertion process is designed to use high-bandwidth disk storage
subsystems. The speed of the process is dependent on the disk storage that
is used.
For best performance, use multiple LUNs that map to multiple
independent disks, or that map to redundant arrays of independent disks
(RAIDs) with a large stripe size (for example, 128 KB). Use a different file
system on each LUN.
The following table shows an example of good usage of LUNs.
Table 67. Example of LUN usage
LUN Usage
1 Active log
2 Archive log
3, 4, 5 Database directories

If the disk storage is supplied by a virtualization device (high-end storage

controller, or a SAN virtualization device), ensure that none of the virtual
LUNs are on the same physical disk drive. Ensure that the directories in
use are on different physical disk drives within the virtualization device.

Planning for upgrading multiple servers and components

If your environment includes multiple servers and storage agents, evaluate the
compatibility of the versions being run with an upgraded V7.1 server. Plan to
upgrade one server first in a test environment. Then stage the upgrade of
additional servers and storage agents.

Before you begin

For information about storage-agent and library client compatibility with Tivoli
Storage Manager V7.1 servers, see Technote 1302789 (http://www.ibm.com/
support/docview.wss?uid=swg21302789).
Related tasks:
“Testing the upgrade process for a server” on page 47

Planning for changes to storage agents

To connect to a V7.1 server in a system that uses the z/OS media server, storage
agents must be at Version 7.1.

Procedure

If you have storage agents at earlier versions, upgrade them to V7.1 before you
upgrade the server to V7.1. Verify that LAN-free data movement works as
expected before you upgrade the server.
For the most recent information about supported levels of storage agents, go to the
following website: http://www.ibm.com/support/docview.wss?uid=swg21302789
Related concepts:
“Effects of migration on storage agents” on page 451

462 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Preparing for operational changes

As you migrate your system from V5 to V7.1, the method for backing up and
monitoring the server database changes.

Procedure

Verify the operating procedures, scripts, and administrative schedules that you use
for server operations:
v Plan to back up the server database regularly by using administrative schedules,
a maintenance script, or your own scripts. Back up the server database at least
once per day. For best results, consider scheduling more frequent backups for
the V7.1 database than you did for the V5 database. To ensure that archive log
space is pruned, consider scheduling more full database backups and fewer
incremental backups.
Review information about how database backups are performed automatically
for the V7.1 server. For details, see the Administrator's Guide.
v Understand how database and recovery log space is used, and how monitoring
will change.
v Verify scripts and administrative schedules. The V7.1 server adds new
commands, changes some commands, and deletes some commands that are no
longer needed. These changes will affect your automated operations. For
information about new and changed commands, see “Command and option
changes” on page 51.
v Verify the SELECT commands that you use regularly. Some parameters and
syntax that were previously allowed are not accepted by the database manager
program. For information about SELECT command updates, see “Changes to the
SELECT command” on page 68. To resolve problems that are related to SELECT
commands, see Technote 1380830 (http://www.ibm.com/support/
docview.wss?uid=swg21380830).
v If you use products from independent software vendors to interface with the
server, ensure that the products are compatible with the V7.1 server.

Reference information for planning

Information about updated commands and server options, and the migration of
device classes and library attributes, can help you plan the migration process.

General reference information for Tivoli Storage Manager

upgrades and migrations

General reference information is provided. You can review the changes in

commands, options, and utilities that were implemented since V5 and learn about
server naming practices. For more information, see “Reference information for
planning” on page 51.

Utilities, scripts, and commands

For more information about the available utilities, scripts, and commands, see
Appendix B, “Utilities, scripts, and commands for server upgrade and migration,”
on page 521.

Chapter 19. Planning the migration 463

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Migration of device and library attributes

Review device class information to understand how z/OS device classes are
mapped to an equivalent used by an AIX or Linux on System z system. Review the
library and path information to understand how new libraries and paths are
defined to ensure that existing device classes can use the z/OS media server. The
DSMSERV INSERTDB utility maps the device classes and defines the libraries and
paths.

Device class migration

The following tables describe how each z/OS device type is mapped to its
equivalent on an AIX or Linux on System z system.
Table 68. 3590 device class attributes
Used on AIX and
Attribute Used on z/OS Linux on System z Notes
DEVTYPE Yes Yes The value is always
3590.
LIBRARY Yes (optional) Yes (required) The LIBRARY device
class is replaced with
a new library that
provides access
through the z/OS
media server. If no
library was specified
on the V5 system, a
new library is
defined to provide
access through the
z/OS media server.
ESTCAPACITY Yes Yes The value is
preserved.
MAXCAPACITY Yes No The value is
discarded.
FORMAT Yes Yes The value is
preserved.
PREFIX Yes Yes The value is
preserved.
MOUNTRETENTION Yes Yes The value is
preserved.
MOUNTWAIT Yes Yes The value is
preserved.
MOUNTLIMIT Yes Yes The value is
preserved.
COMPRESSION Yes New The value is
preserved.
EXPIRATION Yes New The value is
preserved.
RETENTION Yes New The value is
preserved.
PROTECTION Yes New The value is
preserved.

464 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Table 68. 3590 device class attributes (continued)

Used on AIX and
Attribute Used on z/OS Linux on System z Notes
UNIT Yes New The value is
preserved.

Table 69. 3592 device class attributes

Used on AIX and
Attribute Used on z/OS Linux on System z Notes
DEVTYPE Yes Yes The value is always
3592.
LIBRARY Yes (optional) Yes (required) The LIBRARY device
class is replaced with
a new library that
provides access
through the z/OS
media server. If no
library was specified
on the V5 system, a
new library is
defined to provide
access through the
z/OS media server.
ESTCAPACITY Yes Yes The value is
preserved.
MAXCAPACITY Yes No The value is
discarded.
WORM Yes Yes The value is
preserved.
SCALEDCAPACITY No Yes The default value of
100 is used.
DRIVEENCRYPTION No Yes A value of ALLOW is
used. The ALLOW
value makes it
possible for the
remote z/OS system
to control the use of
drive encryption.
FORMAT Yes Yes The value is
preserved.
PREFIX Yes Yes The value is
preserved.
MOUNTRETENTION Yes Yes The value is
preserved.
MOUNTWAIT Yes Yes The value is
preserved.
MOUNTLIMIT Yes Yes The value is
preserved.
COMPRESSION Yes New The value is
preserved.
EXPIRATION Yes New The value is
preserved.

Chapter 19. Planning the migration 465

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Table 69. 3592 device class attributes (continued)

Used on AIX and
Attribute Used on z/OS Linux on System z Notes
RETENTION Yes New The value is
preserved.
PROTECTION Yes New The value is
preserved.
UNIT Yes New The value is
preserved.

Table 70. ECARTRIDGE device class attributes

Used on AIX and
Attribute Used on z/OS Linux on System z Notes
DEVTYPE Yes Yes The value is always
ECARTRIDGE.
LIBRARY Yes (optional) Yes (required) The library is
replaced with a new
library that provides
access through the
z/OS media server. If
no library was
specified on the V5
system, a new library
is defined to provide
access through the
z/OS media server.
ESTCAPACITY Yes Yes The value is
preserved.
MAXCAPACITY Yes No The value is
discarded.
WORM No Yes The default value of
NO is used.
DRIVEENCRYPTION No Yes A value of ALLOW is
used. The ALLOW
value makes it
possible for the
remote z/OS system
to control the use of
drive encryption.
FORMAT Yes Yes The value is
preserved.
PREFIX Yes Yes The value is
preserved.
MOUNTRETENTION Yes Yes The value is
preserved.
MOUNTWAIT Yes Yes The value is
preserved.
MOUNTLIMIT Yes Yes The value is
preserved.
COMPRESSION Yes New The value is
preserved.

466 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Table 70. ECARTRIDGE device class attributes (continued)

Used on AIX and
Attribute Used on z/OS Linux on System z Notes
EXPIRATION Yes New The value is
preserved.
RETENTION Yes New The value is
preserved.
PROTECTION Yes New The value is
preserved.
UNIT Yes New The value is
preserved.

Table 71. FILE device class attributes

Used on AIX and
Attribute Used on z/OS Linux on System z Notes
DEVTYPE Yes Yes The value is always
FILE.
LIBRARY No New A new library is not
defined to provide
access to FILE device
classes through the
z/OS media server.
The reason is that the
media server does
not support previous
FILE device classes.
LIBRARY is specified
only on new FILE
device classes, and is
not added for device
classes that existed
on the V5 server.
MOUNTLIMIT Yes Yes The value is
preserved.
PREFIX Yes Yes The value is
preserved.
DIRECTORY No Yes This attribute is not
set.
SHARED No Yes The default value of
NO is used.
UNIT Yes No The value is
discarded.
VOLSER Yes No The value is
discarded.
PRIMARYALLOC No New This attribute is not
set for FILE device
classes that are
migrated from the V5
server. This attribute
is used only for new
FILE classes that are
added.

Chapter 19. Planning the migration 467

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Table 71. FILE device class attributes (continued)

Used on AIX and
Attribute Used on z/OS Linux on System z Notes
SECONDARYALLOC No New This attribute is not
set for FILE device
classes that are
migrated from the V5
server. This attribute
is used only for new
FILE classes that are
added.
MAXCAPACITY Yes Yes The value is
preserved.

Table 72. SERVER device class attributes.

Remember: Device classes with a device type of SERVER are the same across z/OS, AIX,
and Linux on System z. All device classes with a device type of SERVER are preserved
as-is.
Used on AIX and
Attribute Used on z/OS Linux on System z Notes
DEVTYPE Yes Yes The value is always
SERVER.
SERVERNAME Yes Yes The value is
preserved.
MOUNTLIMIT Yes Yes The value is
preserved.
MOUNTRETENTION Yes Yes The value is
preserved.
PREFIX Yes Yes The value is
preserved.
RETRYPERIOD Yes Yes The value is
preserved.
RETRYINTERVAL Yes Yes The value is
preserved.
MAXCAPACITY Yes Yes The value is
preserved.

Library and path migration

On the z/OS system, libraries and paths are used to enable LAN-free access of
media by using storage agents that run on AIX or Linux on System z systems.
Because LAN-free access is not supported for servers migrated from z/OS, all
libraries and paths are deleted during migration. Then, new libraries and paths are
created to allow access to media through the z/OS media server.

The DSMSERV INSERTDB utility defines new libraries and paths so that existing
device classes can use the z/OS media server. For each device class, one new
library is defined by using the same name as the device class:
DEFINE LIBRARY <devclass_name> LIBTYPE=ZOSMEDIA

One new path is defined:

468 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

DEFINE PATH <server_name><devclass_name>SRCTYPE=SERVER DESTTYPE=LIBRARY

ZOSMEDIASERVER=<media_server_name>ONLINE=YES

Migration of server options

During the upgrade process, the ZMSPREPARE command analyzes the Tivoli Storage
Manager server options file and provides recommendations. The recommendations
are designed to help you migrate server options to the server options file of the
V7.1 system and to the server options file of the z/OS media server.

The ZMSPREPARE command makes recommendations based on the following table.

Before you migrate server options, review the table.

Remember: The set of server options that is available on a V5 server is different

from the set of options that is available on a V7.1 server. Similarly, the set of server
options that is available on a z/OS system is different from the set of server
options that is available on an AIX or Linux on System z system.
Table 73. z/OS platform-specific server options
Used on AIX or
Linux on Used on z/OS
Option name System z media server Notes
COMMMETHOD Yes No This option specifies the communication method to be
used by the server. z/OS systems support only the TCPIP
and V7TCPIP communication methods. Both of these
communication methods are also supported by AIX and
Linux on System z systems.
DELETIONEXIT No No This option specifies a user exit that receives control when
a tape volume is deleted from the database. This server
option is not compatible with AIX and Linux on System z
systems. For this reason, any existing entry for this server
option must be removed.
DYNALLOCOFFLN No Yes This option makes it possible for Tivoli Storage Manager
for z/OS Media to select an offline device if no other
devices are available.
FILEEXIT Yes No This option specifies a file to which enabled events are
routed. The specified file name must be verified to ensure
that it works on the V7.1 system.
FILETEXTEXIT Yes No This option specifies a file to which enabled events are
routed. The specified file name must be verified to ensure
that it works on the V7.1 system.
HTTPTCPPORT No No This option specifies the HTTP port number for the HTTP
communication method for IBM TCP/IP. This option is
not available in Tivoli Storage Manager V7.1.
LFVOLUMEFORMATCOUNT No No This option specifies the number of volumes that the
Tivoli Storage Manager server formats automatically for
LAN-free operations if the storage pool does not contain
formatted volumes. This option is not available in Tivoli
Storage Manager V7.1.
LICENSES No No This option specifies the terms of a licensing agreement.
AIX and Linux on System z systems use a different
licensing mechanism from the one specified by this
option. For this reason, new licenses must be registered on
the V7.1 server. Any existing entry for this server option
must be removed.
MESSAGEFORMAT Yes Yes This option specifies whether a message number is
displayed in all lines of a multi-line message or only on
the first line.

Chapter 19. Planning the migration 469

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Table 73. z/OS platform-specific server options (continued)

Used on AIX or
Linux on Used on z/OS
Option name System z media server Notes
MSGHIGHLIGHT No No This option specifies the message severity level for
highlighting. Any existing entry must be removed when
migrating the server options file to AIX or Linux on
System z systems.
MSGSUPPRESS No Yes This option specifies the level of messages to be
suppressed. Any existing entry must be removed when
migrating the server options file to AIX or Linux on
System z systems. Any existing entry should be copied to
the z/OS media server server options file.
OAMCALL No Yes This option specifies whether Tivoli Storage Manager for
z/OS Media allocation should access the OAM database
to determine if a required tape is in the automated tape
library.
ROUTECODE No Yes This option specifies the routing code for Tivoli Storage
Manager messages. Any existing entry must be removed
when migrating the server options file to AIX or Linux on
System z systems. Any existing entry should be copied to
the z/OS media server server options file.
TAPEDELEXIT No Yes This option specifies the name of an exit program that is
called when a tape volume is deleted from the Tivoli
Storage Manager for z/OS Media pool of managed tape
volumes.
TCPADDR No Yes This option specifies the home IP address that Tivoli
Storage Manager for z/OS Media will use to listen for
incoming connections.
TCPADMINPORT Yes No This option specifies the port number on which the server
TCP/IP communication driver is to wait for requests for
sessions other than client sessions. This option should be
included in the AIX or Linux for System z server options
file.
TCPBUFSIZE Yes No This option specifies the size of the buffer used for
TCP/IP send requests. The default value used by AIX and
Linux on System z systems is 16, compared to 32, which is
used by z/OS. Any existing value should be reconsidered
in light of the fact that the V7.1 server will run on a
different operating system.
TCPNAME No Yes This option specifies the name of the started address space
for TCP/IP. Any existing entry must be removed when
migrating the server options file to AIX or Linux on
System z. Any existing entry should be copied to the
z/OS media server server options file.
TCPPORT Yes Yes This option specifies the port number on which the
TCP/IP communication driver of the server is to wait for
requests for client sessions. This option should be
migrated to the V7.1 server only after ensuring that the
specified port will be available on the V7.1 server.
Similarly, this option should be migrated to the z/OS
media server only after ensuring that the specified port
will be available on that server. It might not be useful for
clients to contact the z/OS media server on the existing
port. For this reason, the port specified for this server
option might need to be different from the port of the
Tivoli Storage Manager server that is being migrated from
the z/OS system.

470 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Table 73. z/OS platform-specific server options (continued)

Used on AIX or
Linux on Used on z/OS
Option name System z media server Notes
TCPWINDOWSIZE Yes No This option specifies, in KB, the amount of receive data
that can be buffered at one time on a TCP/IP connection.
The option is used for tuning. Any existing value should
be reconsidered in light of the fact that the V7.1 server
will run on a different operating system.
TECBEGINEVENTLOGGING Yes No This option specifies whether event logging for the Tivoli
receiver should begin when the server starts.
TECHOSTNAME Yes No This option specifies the host name or IP address for the
Tivoli event server.
TECPORT Yes No This option specifies the TCP/IP port address on which
the Tivoli event server is listening.
UNIQUETDPTECEVENTS Yes No This option generates a unique Tivoli Enterprise Console
event class for each Tivoli Storage Manager message,
including client, server, and Tivoli Data Protection agent
messages.
UNIQUETECEVENTS Yes No This option generates a unique Tivoli Enterprise Console
event class for each Tivoli Storage Manager message.
USEREXIT Yes No This option specifies a user-defined exit that will be given
control to manage an event. The syntax of this option
differs on different operating systems. This option
specifies a user exit that is loaded by the server. For this
reason, any existing value should be reconsidered in light
of the fact that a z/OS exit does not work on an AIX or
Linux for System z operating system.

Related reference:
“Command and option changes” on page 51

Chapter 19. Planning the migration 471

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

472 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 20. Preparing for the migration
To prepare for the migration from IBM Tivoli Storage Manager V5 on z/OS to V7.1
on AIX or Linux on System z, you must complete several steps. Ensure that you
install and configure the V7.1 server and prepare the database of the V5 server for
migration.

Preparing space for the migration process

Verify that you have sufficient space on the V7.1 system for the migration process.

Procedure
1. Verify that the system has the amount of space that was estimated in the
planning step. Use the planning work sheet that you filled in with your
information.
2. If you plan to extract the original server database to media for later insertion
into the new database, ensure that you have enough storage space. Storage
space is required for the database and the manifest file that the extraction
process creates.
a. Identify the device class to which you will extract the original database. The
definition must exist in the server database, not just in the device
configuration file.
The device class must be sequential, and the device class type must be tape.
Define a new device class if necessary.
b. Ensure that space or volumes are available in the selected device class. The
amount of space that you need is about the same as the current size of the
original database.
Ensure that the instance user ID that you create for the upgraded server has
access permission to the location of the extracted data.
c. Check that the access permissions are correct for the location that you plan
to specify for the manifest file.
The user ID that will run the database preparation and extraction utilities
(DSMUPGRD PREPAREDB and DSMUPGRD EXTRACTDB) must have write access to
this file.
When the data is later inserted into the V7.1 database, the instance user ID
that you use for the upgraded server must have access permission for the
manifest file.
The manifest file might be less than 1 KB. However, for a complex
configuration, it might exceed 1 KB.
Related tasks:
“Estimating database and recovery log requirements” on page 457

© Copyright IBM Corp. 2009, 2013 473

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Backing up configuration information

Before you install the new version, you must back up critical files and information
for each server instance. Store the files in a safe place because they are needed
after the installation of the new software version is completed. You also need these
files if you must revert to the previous version after the upgrade.

Procedure
1. Back up device configuration information to another directory by using the
following Tivoli Storage Manager administrative command:
backup devconfig filenames=file_name

where file_name specifies the file in which to store device configuration

information.
2. Back up volume history information to another directory. Ensure that the
volume history includes information about the database backup that you
completed in the preceding steps. For example, issue the following command:
query volhistory type=dbbackup
3. Make a copy of the server options file.
4. Optional: Make a copy of the accounting log file.
5. Back up any scripts that were used for daily housekeeping for the server.
Examine the scripts for changes that are needed after the upgrade.
6. Store the device configuration file, the volume history file, the server options
file, and the other files in a safe place. Select a location that is not on the
system that is being upgraded.

Installing and configuring the V7.1 server

In preparation for migration of the V5 server from the z/OS system, install and
complete an initial configuration of the V7.1 server.

Installing the V7.1 server on AIX or Linux systems

You can install the server by using the installation wizard, console mode, or silent
mode.

Before you begin

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

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

About this task

By using the Tivoli Storage Manager installation software, you can install the
following Tivoli Storage Manager components:

474 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

v server
v server languages
v license
v devices
v Operations Center
v storage agent

Tip: The database (DB2) and the Global Security Kit are automatically installed
when you select the Tivoli Storage Manager server component.
For more information about storage agents, see the Storage Agent User's Guide.

Procedure
1. Log in to the system by using the root user ID.
2. If you are obtaining the package from an IBM download site, download the
appropriate package file from one of the following websites:
v For a new release, go to Passport Advantage at http://www.ibm.com/
software/lotus/passportadvantage/. Passport Advantage is the only
website from which you can download a licensed package file.
v For a maintenance fix, go to the Tivoli Storage Manager support site at
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager.
3. If you are downloading the package from one of the download sites, complete
the following steps:
a. Verify that you have enough space to store the installation files when they
are extracted from the product package. For space requirements, see the
download document for your product:
v Tivoli Storage Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035122
v Tivoli Storage Manager Extended Edition: http://www.ibm.com/
support/docview.wss?uid=swg24035635
v System Storage Archive Manager: http://www.ibm.com/support/
docview.wss?uid=swg24035637
b. Download the package file to the directory of your choice. The path must
contain no more than 128 characters. Ensure that you extract the
installation files to an empty directory. Do not extract to a directory that
contains previously extracted files, or any other files.
Also, ensure that you have executable permission for the package file.
c. If necessary, change the file permissions by issuing the following
command:
chmod a+x package_name.bin
where package_name is like the following example:

AIX

7.1.0.000-TIV-TSMSRV-AIX.bin

Linux

7.1.0.000-TIV-TSMSRV-Linuxx86_64.bin
7.1.0.000-TIV-TSMSRV-Linuxs390x.bin

In the examples, 7.1.0.000 represents the product release level.

Chapter 20. Preparing for the migration 475

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

d. Extract the installation files by issuing the following command:

./package_name.bin

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

4. AIX To ensure that the Tivoli Storage Manager wizards work correctly,
verify that the following command is enabled:
lsuser
By default, the command is enabled.
5. If you plan to install the server by using the graphical wizard of IBM
Installation Manager, review the following information and verify that your
system meets the requirements:
v AIX Verify that all required RPM files are installed. For a list of
required RPM files and instructions about installing RPM files, see the
section about installing Tivoli Storage Manager by using the installation
wizard in the Installation Guide.
v Verify that the operating system is set to the language that you require. By
default, the language of the operating system is the language of the
installation wizard.

On test servers only: Use the following command to bypass prerequisite

checks such as the operating system and the required memory. Do not issue
this command on a production server.
./install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
6. If you are using the installation wizard, complete the following steps to begin
the installation:

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

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

7. If you are installing the server by using the wizard, follow these instructions:
a. In the IBM Installation Manager window, click the Install icon; do not
click the Update or Modify icon.
b. Select the components to install. You must install the license package. If
you select the storage agent, you must accept the Tivoli Storage Manager
for Storage Area Networks license.

476 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

8. Alternatively, install the server in console mode. Review the information about
installing the server in console mode and then complete the installation
procedure, as described in the Installation Guide.
9. Alternatively, to install the server in silent mode, follow the instructions for an
installation in silent mode in the Installation Guide. Review the information
about installing the server in silent mode. Then, complete Steps 1 and 2 of the
installation procedure.
10. Correct any errors that are detected during the installation process. To view
installation log files, from the Installation Manager tool, click File > View Log.
To collect log files, from the Installation Manager tool, click Help > Export
Data for Problem Analysis.
11. Obtain any applicable fixes by going to the following website:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
Tivoli_Storage_Manager. Click Fixes (downloads) and apply any applicable
fixes.
12. To prevent server failures during interaction with DB2, tune the kernel
parameters. For instructions, see the section about tuning kernel parameters in
the Installation Guide.
13. Optional: To install an additional language package, use the modify function
of the IBM Installation Manager.
14. Optional: To upgrade to a newer version of a language package, use the
update function of the IBM Installation Manager.

Creating the directories and the user ID for the server

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

Before you begin

Review the information about planning space for the server before completing this
task.

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

Restriction: In the user ID, only lowercase letters (a-z), numerals (0-9), and
the underscore character (_) can be used. The user ID and group name must
comply with the following rules:
v The length must be 8 characters or less.
v The user ID and group name cannot start with ibm, sql, sys, or a numeral.
v The user ID and group name cannot be user, admin, guest, public, local, or
any SQL reserved word.
For example, create user ID tsminst1 in group tsmsrvrs. The following
examples show how to create this user ID and group by using operating
system commands:
AIX

# mkgroup id=1001 tsmsrvrs

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

Chapter 20. Preparing for the migration 477

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Linux

# groupadd tsmsrvrs
# useradd -d /home/tsminst1 -m -g tsmsrvrs -s /bin/bash tsminst1
# passwd tsminst1
b. Log out and then log in to your system by using the new user ID and
password. Use an interactive login program, such as telnet, so that you are
prompted for the password and can change it if necessary.
c. If a configuration profile does not exist for the user ID, create the file. For
example, create a .profile file if you are using the Korn shell (ksh).
2. Create the directories that the server requires. Ensure that you are logged in
under the new user ID that you created.
You need a unique, empty directory for each item in the following table. Create
the database directories, the active log directory, and the archive log directory
on different physical volumes. For space requirements, see “Worksheet for
planning space for the V7.1 server” on page 42.
Table 74. Worksheet for creating required directories
Example commands for
Item creating the directories Your directories
The instance directory for mkdir /home/user_ID/tsminst1
the server, which will
contain files for this
server instance, including
the server options file
The database directories mkdir /home/user_ID/tsmdb001
mkdir /home/user_ID/tsmdb002
mkdir /home/user_ID/tsmdb003
mkdir /home/user_ID/tsmdb004
Active log directory mkdir /home/user_ID/tsmlog
Archive log directory mkdir /home/user_ID/
tsmarchlog
Optional: Directory for mkdir /home/user_ID/
the log mirror for the tsmlogmirror
active log
Optional: Secondary mkdir /home/user_ID/
archive log directory, tsmarchlogfailover
which is the failover
location for the archive
log

When a server is initially created by using the DSMSERV FORMAT utility or the
configuration wizard, a server database and recovery log are created. In
addition, files are created to hold database information that is used by the
database manager.
3. Create additional logical volumes and mount the volumes on the directories
that were created in the previous step.
Related tasks:
“Preparing space for the migration process” on page 473
Related reference:
“Server naming best practices” on page 70

478 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Preparing the V5 server on z/OS for migration

To prepare the V5 server for migration, ensure that the server is upgraded to
V5.5.6 or later. Then, on the V5.5.6 or later server, install the z/OS media server.
Issue the ZMSPREPARE command to identify additional steps that must be completed
before data migration. Then, back up data.

About this task

To protect your server and its data, follow the preparation steps carefully.

Important: It is possible, after the upgrade to V7.1 is complete, that conditions

might cause the need to temporarily revert to the previous version of the server.
Successfully reverting to the previous version of the server is possible only if you
completed all preparation steps.

Modifying the server before the migration

A command must be run on the server to prevent one type of problem during the
migration process. Some modifications to typical server settings are necessary to
prepare for the migration.

Procedure
1. From a Tivoli Storage Manager administrative command line, issue the
command:
convert ussfilespace

This command fixes a problem that might exist in older Tivoli Storage Manager
databases. If the problem does not exist in your database, the command is
completed and you might see error ANR2034E. This error can be ignored. For
more information, see Technote 1408895 (http://www.ibm.com/support/
docview.wss?uid=swg21408895). If the problem exists in your database, the
command might take some time to run.

Important: Do not skip this step. If your database has the problem and you do
not run this command now, the DSMUPGRD PREPAREDB utility fails when you run
it. You must then restart the V5 server and run the CONVERT USSFILESPACE
command before you continue the upgrade process.
2. Review the steps for reverting to the earlier version of the server in the section,
“Reverting from V7.1 to the previous V5 server version” on page 351.
If you must revert to the earlier version after the upgrade to V7.1, the results of
the reversion will be better if you understand the steps and prepare for the
possibility now.
3. Make the following adjustments to settings on your server and clients. These
adjustments must be done to make it possible for you to revert to the original
server after the upgrade, if problems occur.
a. For each sequential-access storage pool, set the REUSEDELAY parameter to the
number of days during which you want to be able to revert to the original
server, if necessary.
For example, if you want to be able to revert to the original server for up to
30 days after the upgrade to V7.1, set the REUSEDELAY parameter to 31 days.
Issue the following administrative command:
update stgpool sequential_access_storage_pool reusedelay=31

Chapter 20. Preparing for the migration 479

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

b. For each copy storage pool, set the RECLAIM parameter to 100 (meaning
100%). Issue the following administrative command:
update stgpool copy_storage_pool reclaim=100
c. If you typically use a DELETE VOLHISTORY command to delete database
backups, ensure that the command does not delete database backups too
frequently. The interval between backups should be at least the same
number of days that you set for the REUSEDELAY period for sequential-access
storage pools. For example, to delete database backups every 45 days, issue
the following administrative command:
delete volhist type=dbbackup todate=-45
d. For important clients that use the server, verify that the value for the
schedlogretention client option is set to retain the client schedule log for a
sufficient time. Update the option for clients if needed.
The entries in the client schedule log might be useful if the server must
revert to the original version. If the retention period for the schedule log is
too short, the schedule log information might be deleted too soon.
For example, to prune the log every 45 days and save the log entries, add
the following option:
schedlogretention 45 S

Upgrading the V5 server to V5.5.6

To prepare the Tivoli Storage Manager V5 server for the upgrade, ensure that
Tivoli Storage Manager V5.5.6 or later is installed.

Before you begin

Upgrade the V5 server to V5.5.6 or later so that you can use the ZMSPREPARE
command and other tools that help to prepare the system for the migration.

The Tivoli Storage Manager server must not be running during installation of the
fix pack.

To install a fix pack to the server, you must have the Tivoli Storage Manager
license package installed. The license package is provided when you purchase a
base release.

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

Procedure
1. Obtain the package file for the V5.5.6 or later fix pack from the Tivoli Storage
Manager FTP downloads site at ftp://public.dhe.ibm.com/storage/tivoli-
storage-management/maintenance/server/v5r5/MVS/LATEST.
2. For installation information, review the README.txt file, which is available in
the V5.5.6 or later package file.
3. Install the V5.5.6 or later fix pack.

480 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

What to do next

For more information about the Tivoli Storage Manager server V5.5 release, see the
Tivoli Storage Manager V5.5 information center at http://publib.boulder.ibm.com/
infocenter/tivihelp/v1r1/index.jsp.

Installing Tivoli Storage Manager for z/OS Media

To install Tivoli Storage Manager for z/OS Media, use the appropriate installation
commands. Then, complete the configuration tasks.

Procedure
1. To install Tivoli Storage Manager for z/OS Media, go to the Tivoli Storage
Manager V6.3 Information Center at http://pic.dhe.ibm.com/infocenter/
tsminfo/v6r3. Follow the installation instructions in the IBM Tivoli Storage
Manager for z/OS Media Installation and Configuration Guide.
2. To configure Tivoli Storage Manager for z/OS Media, go to the Tivoli Storage
Manager V6.3 Information Center at http://pic.dhe.ibm.com/infocenter/
tsminfo/v6r3. Follow the configuration instructions in the IBM Tivoli Storage
Manager for z/OS Media Installation and Configuration Guide.
Related concepts:
“Tivoli Storage Manager for z/OS Media overview” on page 443

Defining a server that corresponds to the z/OS media server

On the V5 system, create a server definition that corresponds to the z/OS media
server. The z/OS media server will be used during the DSMSERV INSERTDB step to
access upgrade media on tape. After the migration is complete, the z/OS media
server will be used to access client data that is stored on tape.

About this task

On the V5 server, issue the DEFINE SERVER command. Ensure that the following
parameters are set:
v The SERVER_NAME parameter must specify the user ID that is used to run the
Tivoli Storage Manager V5 server.
v The SERVERPASSWORD parameter must specify the password that is used to log on
to the z/OS media server.
v The HLADDRESS parameter must specify the IP address of the z/OS media server.
v The LLADDRESS parameter must specify the port number of the z/OS media
server.

Here is an example:
define server tsmserv serverpassword=yourlife hladdress=9.115.20.97 lladdress=1555

For details, see the DEFINE SERVER section in the Administrator's Reference.

Chapter 20. Preparing for the migration 481

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Disabling sessions
In preparation for the migration, prevent activity on the server by disabling new
sessions. Cancel any existing sessions.

About this task

The commands in the following procedure are Tivoli Storage Manager

administrative commands.

Procedure
1. Prevent all clients, storage agents, and other servers from starting new sessions
with the server. Use the commands:
disable sessions client
disable sessions server
2. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the commands:
query process
cancel process process_number

Allow time for the processes to be stopped. Some processes, such as storage
pool migration, might take some time to stop.
3. Verify whether any sessions exist, and notify the users that the server is going
to be stopped. To check for existing sessions, use the command:
query session
4. Cancel sessions that are still running. Use the command:
cancel session all

Analyzing the Tivoli Storage Manager server by using

ZMSPREPARE
To analyze the Tivoli Storage Manager V5 server in preparation for the migration,
use the ZMSPREPARE command. The ZMSPREPARE command provides information that
is useful for completing the steps that you must take before data migration can
begin.

About this task

The report that is generated by the ZMSPREPARE command includes information

about the following items:
v Storage pool volumes that are located on FILE and DISK device classes and that
must either be converted to tape or deleted
v Sequential volumes that are recorded in the volume history and that are located
on FILE storage, but not including storage pool volumes
v Backup sets that are located on FILE storage
v Invalid device classes
v Server options that might require an update
v Date and time of the most recent backup of the Tivoli Storage Manager server
database

Requirement: Run the ZMSPREPARE command to ensure that all prerequisites are
met before data migration begins.

482 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Procedure
1. On the V5 server, run the ZMSPREPARE command from the administrative client
command line. For more information about the ZMSPREPARE command, see
“ZMSPREPARE (Prepare a server on a z/OS system for migration)” on page
541. The output from the ZMSPREPARE command shows the following types of
information:
Disk-based storage pools.

Storage Storage Device Estimated Pct Volumes

Pool Name Pool Type Class Name Capacity Util are not
marked
destroyed
----------- ----------- ---------- ---------- ----- ---------
ADPPOOL Active-Data FILE 551 G 19.6 0
DISKPOOL Primary DISK 731 G 38.5 10
FILEMIGPOOL Primary FILE 851 G 20.8 12
FROM-POMPE- Primary FROM-POMP- 561 G 22.1 0
II2-VV EII2-VV
LONGFNPOOL Primary FILE 61 G 1.5 0

**************************************************
FILE device type backup sets.

Node Name Backup Set Name Data Type Date/Time

--------------- --------------- --------------- --------------------
CLIENT115 TEST.99790852 File 08/19/11 13:20:25

Retention Device Description Has Table

Period Class Name of Conten-
ts (TOC)?
--------- ---------- --------------- ----------
365 FILE No Description No

**************************************************
Sequential volumes with a device type of FILE.

Date/Time Volume Type Device Class Volume Name

-------------------- -------------- ------------ ---------------------
08/19/11 13:36:45 EXPORT FILE SVTSMS1.S3785800.EXP
08/19/11 13:36:45 EXPORT FILE SVTSMS1.S3785873.EXP
08/19/11 13:36:45 EXPORT FILE SVTSMS1.S3785947.EXP
08/19/11 13:36:45 EXPORT FILE SVTSMS1.S3786028.EXP
08/19/11 13:36:45 EXPORT FILE SVTSMS1.S3786094.EXP
08/19/11 13:36:45 EXPORT FILE SVTSMS1.S3786158.EXP

**************************************************
Convert server options file.
( Yes/No/Consult documentation/ Unknown option )

Line Option Include in V7 server Include in media server

Number options file? options file?
------ -------------- ------------------------ ------------------------
1 MSGWAITALL No No
6 TCPPORT Consult Consult
7 TCPNAME No Consult
8 TCPADMINPORT Yes No
9 HTTPTCPPORT No No
14 VOLUMEHISTORY Consult No
15 DEVCONFIG Consult No
22 TCPBUFSIZE Consult No
35 USELARGEBUFFE- No No
RS
48 LICENSE No No
49 LICENSE No No
54 LFVOLUMEFORMA- No No
TCOUNT
60 LFVOLUMEFORMA- No No

Chapter 20. Preparing for the migration 483

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

TCOUNT
73 LICENSE No No
74 LICENSE No No

**************************************************
No unsupported device classes are found.

**************************************************

Last
Complete
Backup
Date/Time
---------
08/18/11
13:52:-
35

**************************************************
2. Make appropriate changes to your system environment by using the report
generated by the ZMSPREPARE command. Based on the report, you might need to
complete one or more of the following tasks:
v Back up the disk-based primary storage pools that are identified by the
ZMSPREPARE command to copy storage pools on tape. For details, see “Backing
up data from disk-based primary storage pools” on page 485. Update the
storage pool volumes so that ACCESS=DESTROYED and delete the volumes of
disk-based backup storage pools. For details, see “Removing volumes of
disk-based copy storage pools.” To view volume names in the storage pools
that require handling, use the ZMSPREPARE FORMAT=DETAILED command.
v Update identified server options. For details, see “Creating the Tivoli Storage
Manager server options file” on page 486.
v Remove or change invalid device classes.
v Remove sequential volumes with a device type of FILE such as database
backups, exports, and backup sets. For details, see “Identifying and deleting
FILE backup sets” on page 486.
Related reference:
“ZMSPREPARE (Prepare a server on a z/OS system for migration)” on page 541

Removing volumes of disk-based copy storage pools

Before you migrate the Tivoli Storage Manager V5.5 server on z/OS to V7.1, delete
all disk-based storage pool volumes or mark them as destroyed.

About this task

You can mark volumes of primary storage pools as destroyed, but destroyed is not
a valid access mode for volumes of disk-based copy storage pools. For this reason,
you must delete volumes of disk-based copy storage pools before you migrate
your data.

Procedure
1. By using the output of the ZMSPREPARE command, determine if the copy storage
pool must be migrated from the V5.5 server to the V7.1 server or if it can be
recreated on the V7.1 server after the migration.
2. If you must migrate the copy storage pool to V7.1, recreate the copy storage
pool on the V5.5 system from the primary storage pool by using the BACKUP

484 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

STGPOOL command. The reason for taking this step is that copies of copy pools
are not permitted in Tivoli Storage Manager.
3. If the primary storage pool is also disk-based, back up the primary storage pool
to a tape-based copy storage pool as described in “Backing up data from
disk-based primary storage pools.”
4. Delete the volumes of the disk-based copy storage pools by using the DELETE
VOLUME command.
For details, see the DELETE VOLUME section in the Administrator's Reference.
Related reference:
“ZMSPREPARE (Prepare a server on a z/OS system for migration)” on page 541

Backing up data from disk-based primary storage pools

Disk-based primary storage pools will not be available after the migration.
Therefore, you must create a tape copy storage pool for each disk-based primary
storage pool that does not have one. Then, back up all data from disk-based
primary storage pools to tape copy storage pools.

About this task

After the migration, you can restore the storage pools by using this backup.

Procedure
1. Create a tape copy storage pool. Issue the DEFINE STGPOOL command. Specify
the following parameters:
v The POOL_NAME parameter specifies the name of the storage pool to be
defined.
v The DEVICE_CLASS_NAME parameter specifies the name of the sequential access
device class to which this copy storage pool is assigned.
v The POOLTYPE=COPY parameter specifies that you want to define a storage
pool.
Here is an example:
define stgpool tapepool2 dc480 pooltype=copy
For details, see the DEFINE STGPOOL section in the Administrator's Reference.
2. Back up a primary storage pool. Issue the BACKUP STGPOOL command. For
example, to back up a primary storage pool named PRIMARY_POOL to a copy
storage pool named COPYSTG, issue the following command:
backup stgpool primary_pool copystg
For details, see the BACKUP STGPOOL section in the Administrator's Reference.
3. Change the access mode of each volume of disk-based primary storage pools to
destroyed so that no files can be written to or read from volumes in the storage
pool. Use the UPDATE VOLUME command. For more information about changing
the access mode of storage pools, see the Administrator's Guide. For more
information about the UPDATE VOLUME command, see the Administrator's
Reference.

Chapter 20. Preparing for the migration 485

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Identifying and deleting FILE backup sets

Backup sets that use FILE device classes cannot be regenerated, moved, or accessed
after you migrate your data. For this reason, delete any backup sets that use FILE
device classes.

Procedure
1. Determine which backup sets use FILE device classes. Review the report
generated by the ZMSPREPARE command.
2. Delete any backup sets that use FILE device classes. For details, see the section
on deleting backup sets in the Administrator's Guide.
Related tasks:
“Analyzing the Tivoli Storage Manager server by using ZMSPREPARE” on page
482

Creating the Tivoli Storage Manager server options file

To create a server options file, start by using the options file from the Tivoli
Storage Manager V5 server and make appropriate changes for the V7.1 server.

Procedure
1. Move the options file that is used by the Tivoli Storage Manager V5 server to
the Tivoli Storage Manager V7.1 server instance directory. Ensure that the file is
owned by the Tivoli Storage Manager server instance owner and that it has
valid permissions for that owner ID.
2. Determine whether changes are required in the options file and make the
required changes:
a. Review the report generated by the ZMSPREPARE command. The Convert
server options file section lists options that are in the V5 options file, but
that might not transfer to the V7.1 file.
b. Use the information in the Convert server options file section to
determine whether to include a server option in the V7.1 file.

Results

For general information about server options, see the Administrator's Reference. For
information about new and changed server options since V5, see “Command and
option changes” on page 51.
Related tasks:
“Analyzing the Tivoli Storage Manager server by using ZMSPREPARE” on page
482

Running the ZMSPREPARE command again to verify

prerequisites
After you have run the ZMSPREPARE command once and have made any required
changes in your environment, run the ZMSPREPARE command again to ensure that
all migration prerequisites are met.

About this task

Important: It is mandatory to run the ZMSPREPARE command to ensure that all

prerequisites are met before data migration begins.

486 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Procedure
1. On the V5 server, run the ZMSPREPARE command from the administrative client
command line. For more information about the ZMSPREPARE command, see
“ZMSPREPARE (Prepare a server on a z/OS system for migration)” on page
541.
2. Review the report generated by the ZMSPREPARE command to ensure that all
migration prerequisites are met. If all migration prerequisites are met, the
report is similar to the following one. Verify the following items:
v The Volumes are not marked destroyed value is 0 for all storage pools.
v For backup sets, this message is displayed: No FILE device type backup
sets are found.
v For sequential volumes, this message is displayed: No sequential volumes
with a device type of FILE were found.
v A value is displayed in the Last Complete Backup Date/Time column.
Preferably, the time is recent.
tsm: EZU11>zmsprepare
Disk-based storage pools.

Storage Storage Device Estimated Pct Volumes

Pool Name Pool Type Class Name Capacity Util are not
marked
destroyed
----------- ----------- ---------- ---------- ----- ---------
ARCHIVEPOOL Primary DISK 0.0 M 0.0 0
BACKUPPOOL Primary DISK 10.0 M 0.5 0
FILE Primary FILE 4 G 0.0 0
SPACEMGPOOL Primary DISK 0.0 M 0.0 0

**************************************************
No FILE device type backup sets are found.

**************************************************
No sequential volumes with a device type of FILE were found.

**************************************************
Convert server options file.
( Yes/No/Consult documentation/ Unknown option )

Line Option Include in V7 server Include in media server

Number options file? options file?
------ -------------- ------------------------ ------------------------
1 COMMMETHOD Yes No
2 TCPPORT Consult Consult
8 DEVCONFIG Consult No
9 LICENSE No No
10 LICENSE No No

**************************************************
No unsupported device classes are found.

**************************************************

Last
Complete
Backup
Date/Time
---------

Chapter 20. Preparing for the migration 487

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

09/26/20-
11 09:5-
9:15

**************************************************
3. If any migration prerequisites are not met, make appropriate changes in your
system environment and run the ZMSPREPARE command again. Repeat this step
as required until all migration prerequisites are met.
Related reference:
“ZMSPREPARE (Prepare a server on a z/OS system for migration)” on page 541

Backing up the server database

Immediately before you migrate the server, perform a full database backup to a
tape device class.

About this task

Back up the database by using the following command. Run either a full or
snapshot backup.
backup db type=type devclass=device_class_name

The device class that you specify must exist and have volumes that are available to
it. For example, to perform a snapshot backup of your database to the TAPECLASS
device class by using scratch volumes, enter:
backup db type=dbsnapshot devclass=tapeclass

To use specific volumes instead of scratch volumes, specify the volume names in
the command.

Tip: To protect the backup from media failures, make two copies of the backup.
Ensure that at least one full database backup is available onsite. If you must restore
the database after a failed upgrade, having an onsite backup database saves time.

Stopping the server before the migration

On the Tivoli Storage Manager V5 server that is running on z/OS, stop all server
processes. Then, unmount any tapes that are mounted and stop the server.

Procedure

Use Tivoli Storage Manager administrative commands to stop the server:

1. Determine whether server processes are running. Either cancel processes, or
allow them to complete. Use the following commands:
query process
cancel process process_number

Allow time for the processes to be stopped. Some processes, such as storage
pool migration, might take some time to stop.
For more information about the QUERY PROCESS and CANCEL PROCESS commands
and other Tivoli Storage Manager administrative commands, see the
Administrator's Reference.
2. After all sessions and processes are stopped, determine whether any tapes are
mounted. Unmount any tapes that are mounted. Use the following commands:

488 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

query mount
dismount volume volume_name
3. Stop the server. Use the following command:
halt

Preparing the database of a V5 server for migration

Before you extract the data from the database, you must prepare the server
database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a
single system, you must repeat this task for each server.

Procedure
1. Ensure that you have completed all preparation steps.
2. Log in as administrator to the V5 server system.
3. Prepare the database by using the DSMUPGRD PREPAREDB utility. To use the
DSMUPGRD PREPAREDB utility on z/OS, you must submit a batch job by using JCL,
as in the following example:
//PREPARE JOB ,REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
//* SETPROG APF,ADD,DSN=SVTSMS1.TSM556.LINKLIB,VOL=TS405B
//*
//TIVSMDB EXEC PGM=DSMUPGRD,
// PARM=’POSIX(ON)/PREPAREDB MEDIASERVER=TUCMVSTT’
//STEPLIB DD DSN=SVTSMS1.TSM556.LINKLIB,DISP=SHR
//OPT DD DSN=SVTSMS1.TSM556.OPTIONS,DISP=SHR
//DSMAMENG DD DSN=SVTSMS1.TSM556.MESSAGES(ANRMENU),DISP=SHR
//HLPAMENG DD DSN=SVTSMS1.TSM556.HELP(ANRHENU),DISP=SHR
//DSK DD DSN=SVTSMS1.TSM556.DISKLOG,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
4. Monitor the job output for errors and warning messages. The job output can be
found on the MVS™ console.

What to do next

Before you migrate the V5 server database, ensure that the prepare operation is
completed successfully. If the prepare operation fails, you might need to restart the
V5 server to fix the problem and run the prepare operation again.
Related reference:
“DSMUPGRD PREPAREDB (Prepare a V5 database for upgrade)” on page 523

Chapter 20. Preparing for the migration 489

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

490 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 21. Migrating the z/OS server database to the V7.1
server
Migrate the database of the IBM Tivoli Storage Manager V5 server that is running
on z/OS to the V7.1 server.

Before you begin

Decide on a method for moving the database: the media method or the network
method. For information about the advantages of each method, see “Comparison
of database migration methods” on page 452.

With either method, the original server cannot be running while the data is being
extracted.

About this task

To move the database by using the media method, follow the instructions in
“Migrating a V5 z/OS server by using the media method.”

To move the database by using the network method, follow the instructions in
“Migrating a V5 z/OS server by using the network method” on page 494.

Migrating a V5 z/OS server by using the media method

To migrate a V5 z/OS server by using the media method, prepare the V5 database
for migration and extract the data to media. Then create and format the new
database and load the extracted data into the new database.

Creating and formatting the new database

Create the server instance and format files for an empty V7.1 database.

Procedure
1. To define the database, run the DSMICFGX wizard, as you would when
installing Tivoli Storage Manager.
2. Using the Tivoli Storage Manager instance owner ID, run the following
command:
dsmserv removedb tsmdb1
3. To format the database, use the DSMSERV LOADFORMAT utility with appropriate
parameters.

Results

If you complete these steps, there is no need to configure the system for database
backup after the migration.

© Copyright IBM Corp. 2009, 2013 491

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Extracting the data to media

Extract the data from the original V5 server database to sequential media.

Procedure
1. Log in as administrator to the Tivoli Storage Manager V5 server system by
using the administrative console.
2. Ensure that the device that you want to use to store the extracted data is
available. The server database and the device configuration file must contain a
valid device class definition for the device.
3. To start the extraction, use the DSMUPGRD EXTRACTDB utility. To use the DSMUPGRD
EXTRACTDB utility on z/OS, you must submit a batch job by using JCL, as in the
following example:
//EXTRMED JOB ,REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
//* SETPROG APF,ADD,DSN=SVTSMS1.COLLIN.TSM556.LINKLIB,VOL=TS405B
//*
//TIVSMDB EXEC PGM=DSMUPGRD,
// PARM=’POSIX(ON)/EXTRACTDB DEVCLASS=ECARTRIDGE MAN=//SVTSMS1.MED.MFST’
//STEPLIB DD DSN=SVTSMS1.TSM556.LINKLIB,DISP=SHR
//OPT DD DSN=SVTSMS1.TSM556.OPTIONS,DISP=SHR
//DSMAMENG DD DSN=SVTSMS1.TSM556.MESSAGES(ANRMENU),DISP=SHR
//HLPAMENG DD DSN=SVTSMS1.TSM556.HELP(ANRHENU),DISP=SHR
//DSK DD DSN=SVTSMS1.TSM556.DISKLOG,DISP=SHR
//SYSPRINT DD SYSOUT=*

For information about the DSMUPGRD EXTRACTDB command, see “DSMUPGRD

EXTRACTDB (Extract data from a V5 server database)” on page 529.
4. Monitor the job output for errors and warning messages. The job output can be
found on the MVS console. A message near the end of the process output
indicates success or failure of the operation:
Success message: ANR1382I EXTRACTDB: Process 1, database extract, has
completed.
Failure message: ANR1396E EXTRACTDB: Process 1, database extract, has
completed with errors.
The length of time that the process runs depends on the size of the database.
The time is approximately as long as the time required for a full backup of the
database.

Moving tape to another tape library

If you are using tape devices that are directly attached to the V7.1 server, instead
of tape devices that are managed by the z/OS media server, you might need to
move the tapes.

About this task

This step is required only if you plan to run the DSMSERV INSERTDB command to
transfer the V5 server data to tape devices that are directly attached to the V7.1
server. In this case, you might need to move the tapes to another tape library
before the data can be inserted into the DB2 database. For more information, see
the technical documentation for your tape library.

492 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Loading the extracted data into the new database

Load the data that you extracted from the V5 server database into the V7.1 server
database.

Before you begin

Ensure that the following requirements are met before you begin to load the data:
v A new, empty database must be prepared on the V7.1 server by using the
DSMSERV LOADFORMAT command.
v The manifest file from the DSMUPGRD EXTRACTDB operation must be available.
v The server options file must contain an entry for the device configuration file.
v The media that contains the extracted database must be available to the V7.1
server. The permissions must be set to grant access to the media for the user ID
that owns the V7.1 server instance.
v The MANIFEST parameter must be specified to indicate that data will be read from
external media.

Procedure
1. On the V5 server, start the z/OS media server. The V7.1 server will access
extracted data volumes through the z/OS media server.
2. Log on by using the Tivoli Storage Manager server instance user ID to the
system where you installed the V7.1 server.
3. Copy the manifest file that was created by the extraction process on the V5
system to the V7.1 system. Ensure that the instance user ID has ownership or
read/write permission for the manifest file.
4. Verify the contents of the manifest file and edit the file if necessary:
a. Ensure that the device names are valid for the V7.1 system. In particular,
ensure that the definitions for accessing the media server are correct. If you
are not using a media server, ensure that device names for accessing devices
on the V7.1 system are correct.
b. Ensure that the manifest file contains a list of volumes to be used when the
extracted data is loaded into the new database.
5. To load an extracted server database into the empty V7.1 database, issue the
DSMSERV INSERTDB command. Direct the output of the process to a file for
monitoring. For example, enter the following command on one line:
AIX Linux

nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \

manifest=./manifest.txt >insert.out 2>&1 &
6. Monitor the process output for error messages, warning messages, and any
items that you might need to address. The system displays interim statistics
about the operation. However, there might be time periods when no messages
are issued. During this time, DB2 operations are running in the background.
The length of time that the process runs depends on the size of the database.
For more information, see “Estimating the time required for migration” on page
458.
Optional: Verify that the data-loading process is continuing; monitor the
processor and I/O usage for the server process and the corresponding DB2
process. A message in the process output of the DSMSERV INSERTDB command
indicates the status of the operation:
Success message: ANR1395I INSERTDB: Process 1, database insert, has
completed.

Chapter 21. Migrating the z/OS server database to the V7.1 server 493
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Failure message: ANR1396E INSERTDB: Process 1, database insert, has

completed with errors.
The success message must be displayed before you continue with the next step.
7. If you used the media method for upgrade and used a tape device, after the
insertion operation is complete, protect the tape that holds the extracted data.
For example, remove the tape or check it out from the library. Prevent the tape
from being reused until you are sure that you do not need to run the insertion
operation again.
Related information:
DSMUPGRD EXTRACTDB

Migrating a V5 z/OS server by using the network method

To migrate a V5 server running on z/OS to a V7.1 server running on AIX or Linux
on System z, several steps are required. Prepare the database of the V5 server for
migration, and create and format the new database. Then, move the V5 server
database over the network to the V7.1 server database.

Creating and formatting the new database

Create the server instance and format files for an empty V7.1 database.

Procedure
1. To define the database, run the DSMICFGX wizard, as you would when
installing Tivoli Storage Manager.
2. Using the Tivoli Storage Manager instance owner ID, run the following
command:
dsmserv removedb tsmdb1
3. To format the database, use the DSMSERV LOADFORMAT utility with appropriate
parameters.

Results

If you complete these steps, there is no need to configure the system for database
backup after the migration.

Moving the server database over a network

To move the server database over a network, first start the DSMSERV INSERTDB
utility on the V7.1 server to ensure that the server can receive the database. Then,
on the V5 server, extract the database and send it over the network to the V7.1
server by using the DSMSERV EXTRACTDB utility.

Before you begin

Ensure that the Tivoli Storage Manager V5 server and V7.1 server are not running.

Procedure
1. Verify that there is a good network connection between the two systems.
2. Start the DSMSERV INSERTDB process on the V7.1 server to receive the database.
The process must be started by the Tivoli Storage Manager instance owner user
ID. To monitor the process, direct the output of the process to a file. For

494 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

example, start the server, allowing 60 minutes (the default time) for the other
server to contact the V7.1 server and directing the process output to
insert.out, by using this command:
nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \
sesswait=60 >insert.out 2>&1 &

The server starts and waits up to 60 minutes to be contacted by the original

server.
3. Monitor the output of the process. Some time might pass during which no
messages are issued. During this time, DB2 operations are running in the
background. Optional: To verify that operations are continuing as expected,
monitor the CPU and I/O usage for the server process and the corresponding
DB2 process. Before continuing to the next step, verify that the DSMSERV
INSERTDB process has issued the following message:
ANR1336I INSERTDB: Ready for connections from the source server
4. Start the DSMSERV EXTRACTDB process on the V5 server. Specify the TCP/IP
address and port for the V7.1 server on the PARM card. Submit a batch job by
using JCL, as in the following example:
//EXTRACT JOB ,REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
//*
//TIVSMDB EXEC PGM=DSMUPGRD,
// PARM=’POSIX(ON)/EXTRACTDB HLADDRESS=9.11.125.129 LLADDRESS=1500’
//STEPLIB DD DSN=SVTSMS1.TSM556.LINKLIB,DISP=SHR
//OPT DD DSN=SVTSMS1.TSM556.OPTIONS,DISP=SHR
//DSMAMENG DD DSN=SVTSMS1.TSM556.MESSAGES(ANRMENU),DISP=SHR
//HLPAMENG DD DSN=SVTSMS1.TSM556.HELP(ANRHENU),DISP=SHR
//DSK DD DSN=SVTSMS1.TSM556.DISKLOG,DISP=SHR
5. Monitor the processes for errors and warning messages, and for items that you
might need to address. The job output can be found on the MVS console.
6. To find the messages that indicate the success or failure of the operations,
examine the process outputs for the extraction and insertion processes.

Process Success message Failure message

Extraction ANR1382I EXTRACTDB: Process 1, ANR1396E EXTRACTDB: Process 1,
database extract, has database extract, has completed
completed. with errors.
Insertion ANR1395I INSERTDB: Process 1, ANR1396E INSERTDB: Process 1,
database insert, has completed. database insert, has completed
with errors.

Chapter 21. Migrating the z/OS server database to the V7.1 server 495
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

496 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 22. Configuring the z/OS media server devices on the
new server
On the IBM Tivoli Storage Manager V7.1 server, configure devices that you plan to
use with z/OS media server storage.

About this task

For details, see the section on configuring the Tivoli Storage Manager server to use
z/OS media server storage in the Administrator's Guide.

© Copyright IBM Corp. 2009, 2013 497

498 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 23. Taking the first steps after the migration
After you migrate the system, configure the server options, start the server, verify
the migration results, and complete other tasks to ensure that the system operates
as expected.

Procedure

Complete the tasks that are described in the following topics:

1. “Configuring server options for the migrated server”
2. “Starting the server” on page 501
3. “Verifying the migration results” on page 501
4. “Recreating disk-based storage pools that were moved to tape” on page 502
5. “Registering licenses” on page 503
6. “Backing up the database” on page 504
7. “Updating automation” on page 504
8. “Updating configuration of storage agents” on page 505
9. “Beginning operations and monitoring the servers” on page 505
10. “Migrating data from z/OS media volumes to other devices” on page 507

What to do next

After you migrate the system to V7.1, you can authenticate passwords with the
LDAP directory server, or authenticate passwords with the IBM Tivoli Storage
Manager server. Passwords that are authenticated with the LDAP directory server
can provide enhanced system security. For details, see the section about managing
passwords and logon procedures in the Administrator's Guide.

Configuring server options for the migrated server

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

Verify the settings of several other server options.

About this task

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

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

© Copyright IBM Corp. 2009, 2013 499

Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

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

Option name Instructions

DEVCONFIG Ensure that the file name that is specified by the DEVCONFIG option
works on the V7.1 system. Ensure that the path exists and that the
syntax is correct for the V7.1 operating system.
LANGUAGE Ensure that the language that is specified by the LANGUAGE option is
appropriate. Specify en_US or another language that is available
for the server.

For a list of available languages, see the section about installing

server language packages in the Appendix.
VOLUMEHISTORY Ensure that the file name that is specified by the VOLUMEHISTORY
option works on the V7.1 system. Ensure that the path exists and
that the syntax is correct for the V7.1 operating system.
Important: The V7.1 server uses a different format for volume
history information than the V5 server. For this reason, back up the
volume history when the migration completes. The VOLUMEHISTORY
option was optional in V5, but is required for database backup and
restore purposes in V7.1.

5. If the server was running while you updated the server options file, stop and
restart the server.

500 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Starting the server

To verify that the server instance is correctly set up, start the instance.

Procedure

To start the server instance, follow the instructions in “Starting the server on AIX,
HP-UX, Linux, and Oracle Solaris systems” on page 325.

Verifying the migration results

Verify the operation of the server. If the server was installed on a new system as
part of the upgrade, check and update connections to storage devices and other
components.

Procedure
1. Monitor the messages that the server issues as it starts. Watch for error and
warning messages.
2. If the server is running on a new system as a result of the upgrade, check the
following items:
a. Ensure that all of the original server's storage devices are accessible to the
upgraded server.
b. Compare the device names on the new system with the names for the
devices on the original system. Update definitions for the devices on the
server if needed. For example, update path definitions.
c. Update the network address that is used by backup-archive clients, storage
agents, library client servers, and other servers for communicating with the
upgraded server.
Optionally, instead of making these updates, consider whether you can use
the network address of the original system as the address of the new
system. You might also be able to update domain name service (DNS) to
point to the new system instead of the original system. Consult your
network administrator.
3. Verify that you can connect to the server using an administrative client as you
did for the earlier version of the server.
4. Run commands to get a summary of information in the database. Compare the
summary with the results for the same commands before the upgrade.
5. Perform backups for typical client nodes and verify that the backups work as
expected.
6. Verify that operations such as LAN-free data movement and library sharing
work correctly.
7. After you are satisfied that the server is performing as expected and you will
not need to revert to the previous version of the server, remember to return any
settings that you changed to prepare for the upgrade back to the original
values.

Chapter 23. Taking the first steps after the migration 501
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Recreating disk-based storage pools that were moved to tape

The process for recreating disk-based storage pools differs, depending on whether
you deleted the original storage pools or marked them as destroyed.

Recreating deleted storage pools

If you backed up and then deleted storage pools in preparation for the migration,
define new storage pools. These steps are necessary to ensure that data that you
backed up can be restored and used by the Tivoli Storage Manager V7.1 system.

About this task

Use the DEFINE STGPOOL command to define storage pools on the Tivoli Storage
Manager V7.1 server. Alternatively, define tape storage pools on the z/OS media
server. Complete one of the following steps:
v To define storage pools on the Tivoli Storage Manager V7.1 system, run the
DEFINE STGPOOL command.
For details, see the DEFINE STGPOOL command in the Administrator's Reference.
v Define storage pools on the z/OS media server.
For details, see the IBM Tivoli Storage Manager for z/OS Media Installation and
Configuration Guide.

Recreating storage pool volumes marked as destroyed

If you backed up storage pool volumes and then marked them as destroyed,
complete the following steps to ensure that data that you backed up can be
restored and used by the V7.1 system.

Procedure
1. Update the definitions of FILE device classes that write to disk by running the
UPDATE DEVCLASS command. For device classes that were migrated from Tivoli
Storage Manager V5.5 on z/OS to Tivoli Storage Manager V7.1, update the
DIRECTORY parameter to indicate where storage pool volumes are to be written.
If required, update the MAXCAPACITY parameter. For more information about the
UPDATE DEVCLASS command, see the Administrator's Reference.
2. For all disk-based storage pools and FILE storage pools that do not
automatically allocate new volumes, define storage pool volumes. Use the
DEFINE VOLUME command. For more information about the DEFINE VOLUME
command, see the Administrator's Reference.

Restoring data from backed-up storage pools

Restore the backed-up storage pools to the primary DISK and FILE storage pools
on the Tivoli Storage Manager V7.1 system.

About this task

To restore data from backed-up storage pools, on the Tivoli Storage Manager V7.1
system, run the RESTORE STGPOOL command. To specify the name of the new
storage pool to which to restore the files, use the NEWSTGPOOL parameter.

For details, see the RESTORE STGPOOL command in the Administrator's Reference.

Tip: It might be necessary to temporarily increase the value of the MAXSCR

parameter for some FILE storage pools to ensure that data is restored. The reason

502 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

is that storage pool volumes with the ACCESS=DESTROYED attribute applied count
against the MAXSCR parameter. Do not delete storage pool volumes that are marked
as destroyed before you restore the data to the storage pool because the deletion
also deletes corresponding data in the copy pool backup.

Cleaning up by deleting z/OS DISK and FILE volumes that

were marked as destroyed
After you restore the primary storage pools from their backup on tape, you can
delete DISK and FILE volumes that were marked as destroyed. These DISK and
FILE storage pool volumes were used by the V5 system that was running on z/OS
and are no longer required.

About this task

Do not delete storage pool volumes that are marked as destroyed before restoring
the data to the storage pool because delete processing also deletes corresponding
data in the copy pool backup.

To delete storage pool volumes, run the DELETE VOLUME command. If you are
deleting several volumes, delete the volumes one at a time.

For details, see the DELETE VOLUME command in the Administrator's Reference.

Registering licenses
Immediately register any Tivoli Storage Manager licensed functions that you
purchased so that you do not lose data after you begin to use the server.

Before you begin

Verify that the server instance directory of your installation does not include a
NODELOCK file. The NODELOCK file contains the previous licensing information for
your installation. This licensing information is replaced when the upgrade is
complete. If the directory includes a NODELOCK file, move the file to another
directory.

Procedure

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

where installation_directory specifies the directory in which you installed the

component, and component_name specifies the abbreviation for the component.

For example, if you installed the server in the default directory, /opt/tivoli/tsm,
register the license by issuing the following command:
register license file=/opt/tivoli/tsm/server/bin/tsmbasic.lic

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

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

/opt/tivoli/tsm directory, issue the following command:
Chapter 23. Taking the first steps after the migration 503
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

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

Restriction: You cannot register licenses for Tivoli Storage Manager for Mail, Tivoli
Storage Manager for Databases, Tivoli Storage Manager for ERP, and Tivoli Storage
Manager for Space Management.

Backing up the database

After migrating data, perform a full backup of the database as soon as possible.
Also back up the volume history.

Procedure
1. Complete the following steps:
a. If you did not use the instance configuration wizard to configure the server,
ensure that you have completed the steps to manually configure the system
for database backups.
b. If you used the media method for upgrade and used a tape device, remove
or check out from the library the tape that was used to hold the extracted
data. Prevent the tape from being reused until you are sure that the V7.1
server is running properly and you do not need to repeat the database
insertion step.
2. Select the device class to be used for automatic backups of the database. From
the Tivoli Storage Manager administrative command line, issue the following
command:
set dbrecovery device_class_name

The device class that you specify is used by the database manager for all
automatic database backups.
3. Back up the database.
backup db devclass=device_class_name type=full

You can specify the device class to be the same as or different from the device
class that you specified with the SET DBRECOVERY command. If the device class
is different, you receive a warning message, but the backup operation
continues.
4. Back up the volume history.
backup volhistory filenames=file_name

Updating automation
After you migrate your data, you might need to modify administrative schedules
that were defined in V5 because of changes in command syntax. Implement and
verify changes to any automation or scripts that were identified as requiring
modification in the planning process.

About this task

Important: Ensure that automation includes a backup of the database. Back up the
database at least once per day.

504 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

Updating configuration of storage agents

After you migrate your data, verify that data can be transferred from storage
agents to the z/OS media server. If necessary, reconfigure storage agents to ensure
that data can be transferred.

About this task

Storage agents are used to ensure that client systems can write data directly to, and
read data directly from, storage devices attached to the z/OS media server. A
storage agent that is installed on a client system must be set up to communicate
with the z/OS media server by using the LAN.

Procedure
1. Verify that data can be transferred from the storage agent to the z/OS media
server.
For information about how to verify the data transfer, see the Storage Agent
User's Guide.
2. If you detect an issue with data transfer, update the configuration of the
storage agent.
For information about how to configure a storage agent for z/OS media server
access, see the Storage Agent User's Guide.

Beginning operations and monitoring the servers

When you start running the Tivoli Storage Manager V7.1 server, monitor the space
used by the server to ensure that the amount of space is adequate. On the V5
server, where the z/OS media server is installed, you can continue to use z/OS
tools to monitor activity on the system.

Procedure

To monitor the V7.1 server and make any required adjustments, complete the
following steps:
1. Monitor the active log to ensure that the size is correct for the workload that is
handled by the server instance.
When the server workload reaches its typical expected level, the space that is
used by the active log is 80% - 90% of the space that is available to the active
log directory. At that point, you might need to increase the amount of space.
Whether you must increase the space depends on the types of transactions in
the server workload. Transaction characteristics affect how the active log space
is used.
The following transaction characteristics can affect the space usage in the active
log:
v The number and size of files in backup operations
– Clients such as file servers that back up large numbers of small files can
cause large numbers of transactions that are completed quickly. The
transactions might use a large amount of space in the active log, but for a
short time.
– Clients such as a mail server or a database server that back up large
chunks of data in a few transactions can cause small numbers of
transactions that take a long time. The transactions might use a small
amount of space in the active log, but for a long time.

Chapter 23. Taking the first steps after the migration 505
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

v Network connection types

– Backup operations that occur over fast network connections cause
transactions that are completed more quickly. The transactions use space
in the active log for a shorter time.
– Backup operations that occur over relatively slower connections cause
transactions that take a longer time to be completed. The transactions use
space in the active log for a longer time.
If the server is handling transactions with a wide variety of characteristics, the
space that is used for the active log might increase and decrease significantly
over time. For such a server, you might need to ensure that the active log
typically has a smaller percentage of its space used. The extra space allows the
active log to grow for transactions that take a long time.
2. Monitor the archive log to ensure that space is always available.

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

What to do next

After the migration, you can continue to use z/OS tools to monitor activity on the
V5 system where the z/OS media server is running.

For information about monitoring activity on the V5 system, see the section on
monitoring the server in a system running on z/OS. This information can be found
in the Tivoli Storage Manager V5.5 information center at http://
publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp.

506 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Migrating V5 servers on z/OS systems to V7 on AIX or Linux systems

If you are using the Tivoli Storage Manager V5 TSO administrative client, you
might want to change to a newer administrative client. You can adapt your z/OS
tools to use the z/OS UNIX System Services (USS) 6.1.4 administrative client. The
z/OS USS 6.1.4 administrative client is not available for download from the client
FTP site, but can be obtained by ordering the following fix packs:
v UK62472 for the USS Backup-Archive client
v UK62473 for the USS API client

To order fix packs, go to the IBM Passport Advantage website at

http://www.ibm.com/software/lotus/passportadvantage/.

Migrating data from z/OS media volumes to other devices

After migration, data can be moved from z/OS media volumes to other devices.

Before you begin

To move data from z/OS media volumes to other devices, use one or both of the
following methods:
v Direct incoming new data to storage pools on the AIX or Linux on System z
system. Then, allow existing data that is stored on the z/OS system to naturally
expire.
v Actively move data from z/OS media volumes to storage pools on the AIX or
Linux on System z system. To move the data, use the MOVE DATA or MOVE
NODEDATA command.

About this task

For more information about the MOVE DATA and MOVE NODEDATA commands, see the
Administrator's Reference.

Chapter 23. Taking the first steps after the migration 507
508 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Chapter 24. Troubleshooting the migration of a V5 server from
a z/OS system to AIX or Linux on System z
Review this section for tips to troubleshoot common problems that might occur
after the migration. A procedure that explains how to return to the previous
version of the server is also included.

Reverting to the V5 server running on z/OS after a migration

If you must revert the IBM Tivoli Storage Manager server to a previous version
after migration, you must have a full database backup from the V5 system. In
addition, you must have the server installation media for your original version and
key configuration files. If you carefully follow the preparation steps before you
upgrade the server, it might be possible to revert to the previous version with
minimal loss of data.

About this task

The V5 server running on z/OS can be put back into production at any point
along the migration path. Depending on the amount of progress made, different
actions are required to revert to the original server:
v To revert to the V5 server before data is moved to the V7.1 system, see
“Reverting to the V5 server before data is moved to the V7.1 server.”
v To revert to the V5 server before DISK or FILE volumes are deleted, see
“Reverting to the V5 server before volumes are deleted.”
v To revert to the V5 server after the original database is deleted, see “Reverting to
the V5 server after the V5 database is deleted” on page 510.

Reverting to the V5 server before data is moved to the V7.1

server
If you completed the preparation steps for migration, but did not move data, you
can revert to the V5 system. You must restart the z/OS server and update relevant
volumes.

Procedure
1. Restart the V5 server running on the z/OS system.
2. Change the access state of DISK and FILE volumes from destroyed to
READWRITE.

Reverting to the V5 server before volumes are deleted

If you completed all preparation steps for migration, but did not delete DISK or
FILE volumes, you can revert to the V5 server by completing the following steps.

Procedure
1. Restart the V5 server running on the z/OS system.
2. Change the access state of DISK and FILE volumes from destroyed to
READWRITE.

© Copyright IBM Corp. 2009, 2013 509

Troubleshooting the migration

Reverting to the V5 server after the V5 database is deleted

To revert to the V5 server system after you have deleted the database, you must
restore the V5 database from its backup copies. After the database is recovered, it
might be necessary to restore the contents of DISK and FILE volumes.

Before you begin

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

About this task

Tip: The REUSEDELAY parameter can be used to extend the amount of time one can
wait before reverting to the original V5 server running on a z/OS system. To
extend the amount of time, specify the REUSEDELAY parameter for all sequential
storage pools during the preparation phase. Specify the parameter before the final
database backup is made and before the migration begins.

For more information about setting the REUSEDELAY parameter, see “Modifying the
server before the migration” on page 479.

Restriction: Files backed up or archived to the server after the server is migrated
to the V7.1 system will be lost if the server is reverted to V5. You cannot use
EXPORT or IMPORT commands to recover these files because V7.1 export data cannot
be imported by a V5 server.

Steps for reverting to the previous server version

To revert to the previous server version, you must back up the V7.1 database,
uninstall the V7.1 server, reinstall the V5 server program, and restore the database
from the backup.

Procedure
1. Back up the V7.1 database and save the contents of the instance directory,
including the volume history file, the device configuration file, and server
options file. Keep these files in case you must revert to the V7.1 server.
2. Remove the database from the database manager, and then delete the database
and recovery log directories.
a. Manually remove the database. Issue the command:
dsmserv removedb tsmdb1
You can also use the following command to remove the database:
db2 drop db tsmdb1
b. If you must reuse the space that is occupied by the database and recovery
log directories, you can now delete these directories.
3. Use the installation program to uninstall the V7.1 server. Uninstallation
removes the server and the database manager software with their directories.
For instructions about uninstalling the server, see the Installation Guide.

510 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Troubleshooting the migration

4. Reinstall the version of the server program that you were using before the
upgrade to V7.1. This version must match the version that your server was
running when you created the database backup that you will restore in a later
step.
For example, if the server was at version 5.5.6.0 before the upgrade, and you
intend to use the database backup that was in use on this server, you must
install the V5.5.0.0 server program and then the V5.5.6.0 fix pack to be able to
restore the database backup.
a. Reinstall the base version of the server that was in use before the upgrade
to V7.1.
b. Reinstall any fix packs that were installed on the base server version
before the upgrade to V7.1.
5. Copy the following files to the directory for server information:
v Device configuration file
v Volume history file
v Server options file
6. Format the database by using the DSMSERV FORMAT utility. For details, see
the information for the version of the server that you are reinstalling.
Information for V5.5 is available at this information center:
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1
Information for V5.4 and V5.3 is available in the same information center. In
the navigation pane, scroll down and expand Previous versions.
7. Restore the database by using the backup that was created in the preparation
steps before the upgrade.
8. If you enabled data deduplication for any FILE-type storage pools that existed
before the upgrade, or if you moved data that existed before the upgrade into
new storage pools while using the V7.1 server, you must complete additional
recovery steps. See “Additional recovery steps if you created new storage
pools or enabled data deduplication” on page 512.
9. If the REUSEDELAY setting on storage pools is less than the age of the database
that you restored, restore volumes on any sequential-access storage pools that
were reclaimed after that database backup. Use the RESTORE VOLUME command.
If you do not have a backup of a storage pool, audit the reclaimed volumes
by using the AUDIT VOLUME command, specifying the FIX=YES parameter to
resolve inconsistencies. Use the command:
audit volume volume_name fix=yes
10. If client backup or archive operations were performed by using the V7.1
server, you might need to audit the storage pool volumes on which the data
was stored.
11. If you were using active-data pools before upgrading to V7.1, you must
recreate them.
The amount of time required to recreate the active-data pools might be
significant, depending on the number and size of the active-data pools to be
recreated.

Chapter 24. Troubleshooting 511

Troubleshooting the migration

Additional recovery steps if you created new storage pools or

enabled data deduplication
If you created storage pools, enabled data deduplication for any FILE-type storage
pools, or did both while your server was running as a V7.1 server, you must
complete additional steps to revert the server to the previous version.

About this task

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

Complete these steps after the server is restored to V5.

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

512 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Part 4. Appendixes

© Copyright IBM Corp. 2009, 2013 513

514 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Appendix A. Tivoli support information
You can find support information for Tivoli and other IBM products from various
sources.

From the IBM Support Portal at http://www.ibm.com/support/entry/portal/, you

can select the products that you are interested in and search for a wide variety of
relevant information.

Communities and other learning resources

In addition to product documentation, many forms of assistance are available to
help you get started as you deploy and use the Tivoli Storage Manager family of
products. These resources can also help you to solve problems that you might
have.

You can use forums, wikis, and other social media tools to ask questions, talk to
experts, and learn from others.

User groups
Tivoli Global Storage Virtual User Group
Access this user group at http://www.tivoli-ug.org/storage.
This group makes it possible for individuals from many different industries
and types of organizations to share information and work directly with the
IBM product experts. Local chapters also exist where members meet in
person to share experiences and hear from guest speakers.
ADSM.ORG
Access this mailing list at http://adsm.org.
This independently managed Storage Management discussion forum
started when Tivoli Storage Manager was known as ADSTAR Distributed
Storage Manager (ADSM). The members of this forum have many years of
experience with Tivoli Storage Manager in almost every type of IT
environment.
To subscribe to the forum, send an email to [email protected]. The
body of the message must contain the following text: SUBSCRIBE ADSM-L
your_first_name your_family_name.

Tivoli Storage Manager community on Service Management

Connect

Access Service Management Connect at http://www.ibm.com/developerworks/

servicemanagement. In the Storage Management community of Service
Management Connect, you can connect with IBM in the following ways:
v Become involved with transparent development, an ongoing, open engagement
between users and IBM developers of Tivoli products. You can access early
designs, sprint demonstrations, product roadmaps, and prerelease code.
v Connect one-on-one with the experts to collaborate and network about Tivoli
and the Tivoli Storage Manager community.
v Read blogs to benefit from the expertise and experience of others.

© Copyright IBM Corp. 2009, 2013 515

v Use wikis and forums to collaborate with the broader user community.

Tivoli Storage Manager wiki on developerWorks®

Access this wiki at https://www.ibm.com/developerworks/servicemanagement/

sm/index.html.

Find the latest best practices, white papers, and links to videos and other
resources. When you log on, you can comment on content, or contribute your own
content.

Tivoli Support Technical Exchange

Find information about upcoming Tivoli Support Technical Exchange webcasts at

http://www.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html.
Replays of previous webcasts are also available.

Learn from technical experts who share their knowledge and then answer your
questions. The sessions are designed to address specific technical issues and
provide in-depth but narrowly focused training.

Other social media sites

LinkedIn
You can join groups on LinkedIn, a social media site for professionals. For
example:
v Tivoli Storage Manager Professionals: http://www.linkedin.com/
groups/Tivoli-Storage-Manager-Professionals-54572
v TSM: http://www.linkedin.com/groups?gid=64540
Twitter
Follow @IBMStorage on Twitter to see the latest news about storage and
storage software from IBM.

Tivoli education resources

Use these education resources to help you increase your Tivoli Storage Manager
skills:
Tivoli Education and Certification website
View available education at http://www.ibm.com/software/tivoli/
education.
Use the Search for Training link to find local and online offerings of
instructor-led courses for Tivoli Storage Manager.
Education Assistant
Access resources at http://publib.boulder.ibm.com/infocenter/ieduasst/
tivv1r0/index.jsp.
Scroll to view the list of available training videos. Recorded product
demonstrations are also available on a YouTube channel.

516 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Searching knowledge bases
If a problem occurs while you are using one of the Tivoli Storage Manager family
of products, you can search several knowledge bases.

Begin by searching the Tivoli Storage Manager Information Center at

http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1. Within the information center,
you can enter words, phrases, or message numbers in the Search field to find
relevant topics.

Searching the Internet

If you cannot find an answer to your question in the Tivoli Storage Manager
information center, search the Internet for the information that might help you
resolve the problem.

To search multiple Internet resources, go to the IBM support website at

http://www.ibm.com/support/entry/portal/. You can search for information
without signing in.

Sign in using your IBM ID and password if you want to customize the site based
on your product usage and information needs. If you do not already have an IBM
ID and password, click Sign in at the top of the page and follow the instructions
to register.

From the support website, you can search various resources:

v IBM technotes.
v IBM downloads.
v IBM Redbooks® publications.
v IBM Authorized Program Analysis Reports (APARs). Select the product and click
Downloads to search the APAR list.

Using IBM Support Assistant

IBM Support Assistant is a complimentary software product that can help you with
problem determination. It is available for some Tivoli Storage Manager and Tivoli
Storage FlashCopy Manager products.

IBM Support Assistant helps you gather support information when you must 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

You can find more information and download the IBM Support Assistant web page
at http://www.ibm.com/software/support/isa.

You can also install the stand-alone IBM Support Assistant application on any
workstation. You can then enhance the application by installing product-specific
plug-in modules for the IBM products that you use. Find add-ons for specific
products at http://www.ibm.com/support/docview.wss?uid=swg27012689.

Appendix A. Tivoli support information 517

Finding product fixes
A product fix to resolve a software problem might be available from the IBM
software support website.

Procedure

Determine what fixes are available by checking the IBM software support website
at http://www.ibm.com/support/entry/portal/.
If you previously customized the site based on your product usage:
1. Click the link for the product, or a component for which you want to
find a fix.
2. Click Downloads, and then click Search for recommended fixes.
If you have not previously customized the site:
Click Downloads and search for the product.

Receiving notification of product fixes

You can receive notifications about fixes, flashes, upgrades, and other news about
IBM products.

Procedure
1. From the support page at http://www.ibm.com/support/entry/portal/, click
Sign in and sign in using your IBM ID and password. If you do not have an
ID and password, click register now and complete the registration process.
2. Click Manage all my subscriptions in the Notifications pane.
3. Click the Subscribe tab, and then click Tivoli.
4. Select the products for which you want to receive notifications and click
Continue.
5. Specify your notification preferences and click Submit.

Contacting IBM Software Support

You can contact IBM Software Support if you have an active IBM subscription and
support contract, and if you are authorized to submit problems to IBM.

Procedure
1. Ensure that you have completed the following prerequisites:
a. Set up a subscription and support contract.
b. Determine the business impact of the problem.
c. Describe the problem and gather background information.
2. Follow the instructions in “Submitting the problem to IBM Software Support”
on page 520.

518 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Setting up and managing support contracts
You can set up and manage your Tivoli support contracts by enrolling in IBM
Passport Advantage. The type of support contract that you need depends on the
type of product you have.

Procedure

Enroll in IBM Passport Advantage in one of the following ways:

v Online: Go to the Passport Advantage website at http://www.ibm.com/
software/lotus/passportadvantage/, click How to enroll, and follow the
instructions.
v By telephone: For critical, system-down, or high-severity issues, you can call
1-800-IBMSERV (1-800-426-7378) in the United States. For the telephone number
to call in your country, go to the IBM Software Support Handbook web page at
http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html
and click Contacts.

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you must understand and assess the business impact of the problem
you are reporting.

Severity level Description

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.

Describing the problem and gathering background information

When explaining a problem to IBM, it is helpful to 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 using a workaround for this problem? If so, be prepared to explain it
when you report the problem.

Appendix A. Tivoli support information 519

Submitting the problem to IBM Software Support
You can submit the problem to IBM Software Support online or by telephone.
Online
Go to the IBM Software Support website at http://www.ibm.com/
support/entry/portal/Open_service_request/Software/
Software_support_(general). Sign in to access IBM Service Requests and
enter your information into the problem submission tool.
By telephone
For critical, system-down, or severity 1 issues, you can call 1-800-IBMSERV
(1-800-426-7378) in the United States. For the telephone number to call in
your country, go to the IBM Software Support Handbook web page at
http://www14.software.ibm.com/webapp/set2/sas/f/handbook/
home.html and click Contacts.

520 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Appendix B. Utilities, scripts, and commands for server
upgrade and migration
Utilities and commands are available to upgrade or migrate a V5 server to V7.1. A
script is available for starting multiple servers.

© Copyright IBM Corp. 2009, 2013 521

DSMUPGRD QUERYDB (Display information about a V5 database)
Use the DSMUPGRD QUERYDB utility to display information about the database and
recovery log for a V5 server. You can use the information to estimate the amount
of storage that will be required for the database and recovery log when the server
is upgraded to V7.1.

Syntax
-k Server1
DSMUPGRD QUERYDB
-quiet -o options_file -k key_name

Parameters
AIX HPUX Linux Solaris z/OS -quiet
Specifies that messages to the console are suppressed. This parameter is
optional.
-o options_file
Specifies an options file to use. This parameter is optional.
Windows -k key_name
Specifies the name of the Windows registry key from which to retrieve
information about the server. The default is SERVER1. This parameter is
optional.

Examples

Obtain information about the database:

dsmupgrd querydb

522 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
DSMUPGRD PREPAREDB (Prepare a V5 database for upgrade)
Use the DSMUPGRD PREPAREDB utility to prepare a server database for upgrade to
V7.1. You must run this utility before using the DSMUPGRD EXTRACTDB utility.

Syntax
-k Server1
DSMUPGRD PREPAREDB
-quiet -o options_file -k key_name

MEDIASERVER-=-media_server_name

Parameters
AIX HPUX Linux Solaris-quietz/OS
Specifies that messages to the console are suppressed. This parameter is
optional.
-o options_file
Specifies an options file to use. This parameter is optional.
Windows -k key_name
Specifies the name of the Windows registry key from which to retrieve
information about the server. The default is SERVER1. This parameter is
optional.
z/OS MEDIASERVER
Specifies the name of the server to be used as the z/OS media server. The
server must have been defined by using the DEFINE SERVER command before
using the DSMUPGRD PREPAREDB utility.

Example
dsmupgrd preparedb

Appendix B. Utilities, scripts, and commands 523

DELETE VOLHISTORY (Delete sequential volume history information)
z/OS

The DELETE VOLHISTORY command is used to delete volume history file records that
are no longer needed (for example, records for obsolete database backup volumes).
In a migration from z/OS to AIX or Linux on System z, issue this command on the
V5 server to specify the device class of volumes that must be deleted to prepare for
the migration.

When you delete records for volumes that are not in storage pools (for example,
database backup or export volumes), the volumes return to scratch status even if
IBM Tivoli Storage Manager acquired them as private volumes. Scratch volumes of
device type FILE are deleted. When you delete the records for storage pool
volumes, the volumes remain in the Tivoli Storage Manager database. When you
delete records for recovery plan file objects from a source server, the objects on the
target server are marked for deletion.

Use the DELETE BACKUPSET command to delete specified backup set volume
information in the volume history file. Do not use this DELETE VOLHISTORY
command to delete backup set volume information in the volume history file.

For users of DRM, the database backup expiration should be controlled with the
SET DRMDBBACKUPEXPIREDAYS command instead of this DELETE VOLHISTORY
command. Using the DELETE VOLHISTORY command removes the Tivoli Storage
Manager record of the volume. This can cause volumes to be lost that were
managed by the MOVE DRMEDIA command. The standard way to manage the
automatic expiration of DRM database backup volumes is by using the SET
DRMDBBACKUPEXPIREDAYS command.

The DELETE VOLHISTORY command can be used to specify the device class of
volumes that are to be deleted for migration purposes. The command can be used
before migration of a Tivoli Storage Manager V5 server running on z/OS to a V7
server running on AIX or Linux on System Z. The device class must have a device
type of FILE, and can be specified only if the ZMSPREPARE parameter is set to YES.

Notes:
1. Volumes for the most recent database backup series are not deleted.
2. Existing volume history files are not automatically updated with this command.
3. You can use the DEFINE SCHEDULE command to periodically delete volume
history records.

Privilege class

To issue this command, you must have system privilege.

Syntax
TOTime = 23:59:59
DELete VOLHistory TODate = date
TOTime = time

524 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Type = All
DBBackup
DEVclass = class_name
DBSnapshot
DEVclass = class_name
DBDump
DBRpf
EXPort
DELETELatest = No
RPFile
DELETELatest = No
Yes
DELETELatest = No
RPFSnapshot
DELETELatest = No
Yes
STGNew
STGReuse
STGDelete

No
ZMSPREPARE = Yes DEVClass = class_name

Parameters
TODate (Required)
Specifies the date to use to select sequential volume history information to be
deleted. Tivoli Storage Manager deletes only those records with a date on or
before the date you specify. You can specify the date by using one of the
following values:

Value Description Example

MM/DD/YYYY A specific date 01/23/1999
TODAY The current date TODAY
TODAY-days or -days The current date minus days TODAY–30 or –30.
specified. The maximum
number of days that you can To delete records that are 30 or more
specify is 9999. days old, specify TODAY-30 or -30.

TOTime
Specifies that you want to delete records created on or before this time on the
specified date. This parameter is optional. The default is the end of the day
(23:59:59). You can specify the time by using one of the following values:

Value Description Example

HH:MM:SS A specific time on the 12:30:22
specified date
NOW The current time on the NOW
specified date

Appendix B. Utilities, scripts, and commands 525

Value Description Example
NOW+HH:MM or The current time plus hours NOW+03:00 or +03:00.
+HH:MM and minutes on the specified
date If you issue the DELETE VOLHISTORY
command at 9:00 with
TOTIME=NOW+03:00 or
TOTIME=+03:00, Tivoli Storage
Manager deletes records with a time
of 12:00 or earlier on the specified
date.
NOW-HH:MM or The current time minus hours NOW-03:30 or -03:30.
-HH:MM and minutes on the specified
date If you issue the DELETE VOLHISTORY
command at 9:00 with
TOTIME=NOW-3:30 or
TOTIME=-3:30, Tivoli Storage
Manager deletes records with a time
of 5:30 or earlier on the specified
date.

Type (Required)
Specifies the type of records, which also meet the date and time criteria, to
delete from the volume history file. Possible values are:
All
Specifies to delete all records.

Note: The DELETE VOLHISTORY command does not delete records of remote
volumes.
DBBackup
Specifies to delete only records that contain information about volumes
used for database full and incremental backups, that is, with volume types
of BACKUPFULL and BACKUPINCR, and that meet the specified date and
time criteria. The latest database full and incremental backup series will
not be deleted.
DEVclass=class_name
Specifies the device class name that was used to create the database
backups. This optional parameter can be used to delete database
backups created by using a server-to-server virtual volume device
class. The type of the device class must be SERVER. This parameter
can be used only to delete volume history entries of type
BACKUPFULL, BACKUPINCR, or DBSNAPSHOT.
A full, incremental, or snapshot database backup volume is eligible to
be deleted if all of the following conditions are met:
v The device class that was used to create the database backup volume
matches the specified device class.
v The volume was created on or before the specified date and time.
v The volume is not part of the latest full plus incremental database
backup series if the specified volume type is DBBackup, or snapshot
database backup series if the volume type is DBSnapshot.
DBSnapshot
Specifies to delete only records that contain information about volumes
used for snapshot database backups, and that meet the specified date and
time criteria. The latest snapshot database backup will not be deleted.

526 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
DEVclass=classname
Specifies the device class name that was used to create the database
backups. This optional parameter can be used to delete database
backups created by using a server-to-server virtual volume device
class. The type of the device class must be SERVER. This parameter
can be used only to delete volume history entries of type
BACKUPFULL, BACKUPINCR, or DBSNAPSHOT.
A full, incremental, or snapshot database backup volume is eligible to
be deleted if all of the following conditions are met:
v The device class that was used to create the database backup volume
matches the specified device class.
v The volume was created on or before the specified date and time.
v The volume is not part of the latest full plus incremental database
backup series if the specified volume type is DBBackup, or snapshot
database backup series if the volume type is DBSnapshot.
DBRpf
Specifies to delete only records that contain information about full and
incremental database backup volumes and recovery plan file volumes.
EXPort
Specifies to delete only records that contain information about export
volumes.
RPFile
Specifies to delete only records that contain information about recovery
plan file objects that are stored on a target server and that meet the
specified date and time criteria.
DELETELatest
Specifies whether the latest recovery plan file is eligible for deletion.
This optional parameter can be used to delete the latest recovery plan
files created by using a server-to-server virtual volume device class.
This parameter can be used only to delete volume history entries of
type RPFILE (for instance, those recovery plan files that were created
by using the DEVCLASS parameter with the PREPAREcommand). If this
parameter is not specified, the latest RPFILE entries are not deleted.
No Specifies that the latest RPFILE file is not deleted.
Yes Specifies that the latest RPFILE file is deleted if it meets the
specified date and time criteria.
RPFSnapshot
Specifies to delete only records that contain information about recovery
plan file objects that were created assuming snapshot database backups,
that are stored on a target server, and that meet the specified date and time
criteria. The latest RPFSNAPSHOT file will not be deleted unless it meets the
specified date and time criteria, and the DELETELATEST parameter is set to
Yes.
DELETELatest
Specifies whether the latest recovery plan file is eligible for deletion.
This optional parameter can be used to delete the latest recovery plan
files created by using a server-to-server virtual volume device class.
This parameter can be used only to delete volume history entries of
type RPFSNAPSHOT (for instance, those recovery plan files that were

Appendix B. Utilities, scripts, and commands 527

created by using the DEVCLASS parameter with the PREPARE command).
If this parameter is not specified, the latest RPFSNAPSHOT entries are
not deleted.
No Specifies that the latest RPFSNAPSHOT file is not deleted.
Yes Specifies that the latest RPFSNAPSHOT file is deleted if it meets
the specified date and time criteria.
STGNew
Specifies to delete only records that contain information about new
sequential access storage volumes.
STGReuse
Specifies to delete only records that contain information about reused
sequential storage pool volumes.
STGDelete
Specifies to delete only records that contain information about deleted
sequential storage pool volumes.
ZMSPREPARE
Specifies whether the DELETE VOLHISTORY command is being used to delete
sequential volumes that are stored in a FILE device class. The deletion takes
place before migrating a Tivoli Storage Manager V5 server that is running on
z/OS to a V7 server that is running on AIX or Linux on System z.
No Specifies that the DELETE VOLHISTORY command is not being used to
prepare for a migration. This is the default value.
Yes
Specifies that the DELETE VOLHISTORY command is being used to prepare for
a migration.
DEVclass=class_name
Specifies the device class name that was used to create the volumes
that are being deleted. The device class type must be FILE.

Example: Delete recovery plan file information

Delete all recovery plan file information created on or before 03/28/2005.

delete volhistory type=rpfile todate=03/28/2005

528 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
DSMUPGRD EXTRACTDB (Extract data from a V5 server database)
Use the DSMUPGRD EXTRACTDB utility to extract data from a server database. The data
can be inserted into a version 7.1 server database either later or at the same time as
the extraction process.

Prerequisite

Before using this utility, you must use the DSMUPGRD PREPAREDB utility on the
existing database.

Syntax
-k Server1
DSMUPGRD EXTRACTDB
-quiet -o options_file -k key_name

A: Extract to media
B: Extract and transmit by using a network

EVentbasedused = Yes

EVentbasedused = Never

A: Extract to media:

DEVclass = device_class_name MANifest = file_name

SCRatch = Yes

SCRatch = Yes ,
No (1)
VOLumenames = volume_name

B: Extract and transmit by using a network:

HLAddress = ip_address LLAddress = tcp_port

Notes:
1 You must specify VOLUMENAMES if you specify SCRATCH=NO.

Parameters
AIX HPUX Linux Solaris z/OS -quiet
Specifies that messages to the console are suppressed. This parameter is
optional.
-o options_file
Specifies an options file to use. This parameter is optional.
Windows -k key_name
Specifies the name of the Windows registry key from which to retrieve
information about the server. The default is SERVER1. This parameter is
optional.
Appendix B. Utilities, scripts, and commands 529
DEVclass
Specifies a sequential device class to use for storing the extracted data. This
parameter is required if you want to extract the database to media.

Restriction: You cannot use a device class with a device type of NAS or
CENTERA.

Restriction: z/OS For a Tivoli Storage Manager server running on a z/OS

system, you cannot use a device class with a device type of FILE.
MANifest
Specifies the location of the manifest file. Use a fully qualified file name, or
place in a local directory. For example: ./manifest.txt
This parameter is required if you want to extract the database to media.
EVentbasedused
Specifies whether event-based archive retention was ever in use on the server.
Event-based archive retention supports the retention of an archived object to be
based on an external event. The default value for this parameter is YES.
Possible values are:
Yes
Specifies that event-based archive retention was in use on the server. The
default is YES. If you are not sure whether event-based archive retention
was in use, accept the default.
Overriding the default might cause archive objects to expire prematurely
after the upgrade, if event-based archive retention was ever used. Using
the default value ensures correct results.
Never
Specifies that event-based archive retention was never in use on the server.

Attention: Specifying EVENTBASEDUSED=NEVER might improve the

performance of the upgrade operation. However, do not use this value if
there is any chance that event-based archive retention was ever used on the
server. If event-based archive retention was ever used on the server,
specifying EVENTBASEDUSED=NEVER can result in archive files expiring
prematurely after the upgrade completes.
SCRatch
Specifies whether scratch volumes can be used to store the data. This
parameter is optional. The default value is YES. Possible values are:
Yes
Specifies that scratch volumes can be used.
If you specify SCRATCH=YES and also specify volumes with the VOLUMENAMES
parameter, the specified volumes are used first. Scratch volumes are used
only if the specified volumes do not have enough space to contain the
extracted data.
If the device type for the device class is FILE, the names for the scratch
volumes are generated based on a time stamp.
No Specifies that scratch volumes cannot be used. If you specify this value,
you must also specify volumes by using the VOLUMENAMES parameter.
If the volumes that you specify with the VOLUMENAMES parameter do not
have enough space to contain the extracted data, the process fails.

530 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
VOLumenames
Specifies the volumes to use to store the extracted database. To specify
multiple volumes, separate the names with commas and without intervening
spaces.
HLAddress
Specifies either the numeric IP address or the domain name of the V7.1 server.
This parameter is required if you want to extract and simultaneously transmit
the data to the V7.1 server by using the network.
If the V5 server and the V7.1 server are on the same system, you can specify
localhost.
LLAddress
Specifies the low-level address of the V7.1 server. This address is the same as
the value that is specified with the TCPPORT server option for the V7.1 server.
This parameter is required if you want to extract and simultaneously transmit
the data to the V7.1 server by using the network.

Examples

Extract and transmit the data to a server by using the network:

dsmupgrd extractdb hladdress=xyz.company.com lladdress=1555

Extract and store the data on media:

dsmupgrd extractdb devclass=tapeclass manifest=keepthis.txt

The manifest file for the data extraction to media

During the data extraction to media, the DSMUPGRD utility creates a manifest file.
The manifest file contains information about the volumes and device classes that
are used for storing the extracted data.

The manifest file is required by the data insertion process when you are using
media to move the database to the V7.1 server. You specify the name of the
manifest file when you run the DSMSERV INSERTDB utility.

AIX HPUX Linux In the manifest file, the device

Solaris Windows
configuration section contains information about the configuration settings of the
source server device. You might need to edit settings, such as device names and
drive element numbers, before you use the manifest file with the DSMSERV INSERTDB
utility, especially if the utility is run on a different system.

A manifest file has content that is similar to the following example:

* Version 2 manifest file for EXTRACTDB
DEVCLASS=3584L2
STREAMS=1
VOLUMENAMES000=L12345
* Device Configuration Information
DEFINE DEVCLASS 3584L2 DEVTYPE=LTO FORMAT=DRIVE MOUNTLIMIT=DRIVES MOUNTWAIT=60
MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=3584L2 WORM=NO DRIVEENCRYPTION=ALLOW
SET SERVERNAME MOKSHA
DEFINE LIBRARY 3584L2 LIBTYPE=SCSI SERIAL="00000002267304AB" SHARED=YES
AUTOLABEL=YES RESETDRIVE=YES
DEFINE DRIVE 3584L2 3584L2_DRV1 ELEMENT=265 ONLINE=Yes WWN="500507630F18BA09"
SERIAL="0007859130"
DEFINE PATH MOKSHA 3584L2 SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=/dev/IBMchanger5 ONLINE=YES
DEFINE PATH MOKSHA 3584L2_DRV1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=3584L2 DEVICE=/dev/IBMtape20 ONLINE=YES

z/OS The device configuration section contains device configuration

information for the source server. Device configuration statements are based on
definitions from the source server, but the statements are transformed into the

Appendix B. Utilities, scripts, and commands 531

format required by a server running on AIX or Linux on System z. The device
configuration section is set up to use a z/OS media server for media access.

A manifest file for an upgrade to an AIX or a Linux on System z system has

content similar to the following example:
* Version 2 manifest file for EXTRACTDB
DEVCLASS=TAPE3592
STREAMS=1
VOLUMENAMES000=JJY010,JJY011,JJY012
/* Device Configuration */
DEFINE LIBRARY 3592LIB LIBTYPE=ZOSMEDIA
DEFINE DEVCLASS 3592CLASS DEVTYPE=3592 ESTCAPACITY=314572800K PREFIX=ADSM
MOUNTLIMIT=2 MOUNTRETENTION=60 MOUNTWAIT=60 COMPRESSION=Yes UNIT=C06M5N03 WORM=No
PROTECTION=No FORMAT=Drive LIBRARY=3592LIB
DEFINE PATH MVSTS 3592LIB SRCTYPE=SERVER DESTTYPE=LIBRARY
ZOSMEDIASERVER=TUCMVSTS ONLINE=YES
DEFINE DEVCLASS FILE DEVTYPE=File MAXCAPACITY=2097152K PREFIX=SVTSMS1
MOUNTLIMIT=20
DEFINE DEVCLASS FROM-MVSTT DEVTYPE=File MAXCAPACITY=2097152K PREFIX=SVTSMS1
MOUNTLIMIT=100
DEFINE DEVCLASS TO-MVSTT DEVTYPE=Server SERVERNAME=TUCMVSTT
MAXCAPACITY=2097152K PREFIX=ADSM MOUNTLIMIT=50 RETRYPERIOD=10 RETRYINTERVAL=30
DEFINE SERVER TUCMVSTT COMMMETHOD=TCPIP HLADDRESS=tucmvstt.storage.tucson.ibm.com
LLADDRESS=2533 NODENAME=MVSTS SERVERPASSWORD=18bf4d36c185
DEFINE SERVER PURGE COMMMETHOD=TCPIP HLADDRESS=purge.storage.tucson.ibm.com
LLADDRESS=1500 SERVERPASSWORD=180fb66e028d
DEFINE SERVER STA_PURGE COMMMETHOD=TCPIP HLADDRESS=purge.storage.tucson.ibm.com
LLADDRESS=1502 SERVERPASSWORD=18909a64694f303df677
DEFINE SERVER TUCMVSTS COMMMETHOD=TCPIP HLADDRESS=9.11.92.48 LLADDRESS=2556
SERVERPASSWORD=184feb8740bb139271
SET SERVERNAME MVSTS
SET SERVERPASSWORD 1891a1cefdcaf489d86c66af54

Related reference:
“DSMUPGRD EXTRACTDB (Extract data from a V5 server database)” on page 529

“DSMSERV INSERTDB (Move a server database into an empty database)” on page

538

532 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
DSMUPGRD EXTEND DB (Extend the size of the database)
Use this utility on a V5 database to extend its size. Use this utility only when an
error occurs during the upgrade process that indicates that you need additional
database space to continue.

Prerequisite

Use the DSMFMT utility to format a new volume to be used for extending the
database. For information about how to use the DSMFMT utility, see the version
5.5 information center: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1

Syntax
-k Server1
DSMUPGRD EXTEND DB
-quiet -o options_file -k key_name

volume_name megabytes

Parameters
AIX HPUX Linux Solaris z/OS -quiet
Specifies that messages to the console are suppressed. This parameter is
optional.
AIX HPUX Linux Solaris Windows -o options_file
z/OS
Specifies an options file to use. This parameter is optional.
Windows -k key_name
Specifies the name of the Windows registry key from which to retrieve
information about the server. The default is SERVER1. This parameter is
optional.
volume_name (Required)
Specifies the name to be used for the new database extension volume.
megabytes (Required)
Specifies the size of the new volume in megabytes. The size must be a multiple
of 4 MB, and it must be 1 MB less than the size of the volume specified in the
volume_name parameter. For example, if the volume is 5 MB, specify a value of
4.

Appendix B. Utilities, scripts, and commands 533

DSMUPGRD EXTEND LOG (Extend the size of the recovery log)
Use this utility on a V5 server to extend the size of the recovery log when the
ANR9999D LOGSEG message was issued during the upgrade process, which
indicates that you need additional log space to continue with the upgrade process.

Issue this command if you receive an ANR9999D LOGSEG message. This indicates
that your log space has been overcommitted and your server terminates with a
LOGSEG871 error. After the server is running, you can do the following:
v Back up the database, which frees the recovery log space.
v Adjust the size of the recovery log, the database backup trigger full percentage,
or both to allow for successful future database backups.

Prerequisite

Use the DSMFMT utility to format a new volume to be used for extending the
recovery log. For information about how to use the DSMFMT utility, see the
version 5.5 information center: http://publib.boulder.ibm.com/infocenter/tivihelp/
v1r1

Syntax
-k Server1
DSMUPGRD
-quiet -o options_file -k key_name

EXTEND LOG volume_name megabytes

Parameters
AIX HPUX Linux Solaris z/OS -quiet
Specifies that messages to the console are suppressed. This parameter is
optional.
AIX HPUX Linux Solaris Windows z/OS -o options_file
Specifies an options file to use. This parameter is optional.
Windows -k key_name
Specifies the name of the Windows registry key from which to retrieve
information about the server. The default is SERVER1. This parameter is
optional.
volume_name (Required)
Specifies the name to be used for the new recovery log extension volume
megabytes (Required)
Specifies the size of the new volume in megabytes. The size must be a multiple
of 4 MB, and it must be 1 MB less than the size of the volume specified in the
volume_name parameter. For example, if the volume is 5 MB, specify a value of
4.

534 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
DSMUPGRD UPDATE (Create backup registry entries for a V5 server
instance)
Windows

Use this utility to create registry entries for a V5 server instance if a problem in the
upgrade process has removed the entries when they are still needed. For example,
you can use this utility if you are upgrading a V5 server to V7.1 on the same
system, and accidentally ran the DSMSERV LOADFORMAT utility before running the
DSMUPGRD PREPAREDB utility.

Run this utility from the instance directory for the V5 database (where files such as
dsmserv.dsk are stored for the server). The utility recreates the original registry
entries for the V5 server, but stores the entries in a backup location to avoid
overwriting the entries that were added by V7.1.

Syntax
-k Server1
DSMUPGRD UPDATE
-k key_name

Parameters
-k key_name
Specifies the name of the Windows registry key in which to store information
about the server. The default is Server1.

Example

Run the utility to recreate registry entries for the server instance, Server2.
"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" -k server2 update

Appendix B. Utilities, scripts, and commands 535

DSMSERV LOADFORMAT (Format a database)
Use the DSMSERV LOADFORMAT utility to format an empty database on the V7.1 server
in preparation for inserting data from an extracted V5 database.

Set the DB2CODEPAGE system environment variable to 819 for each server
instance. Before you issue the DSMSERV LOADFORMAT command, log on to the system
as the server instance owner and issue this command:
db2set -i instance_name DB2CODEPAGE=819

For example: AIX HPUX Linux Solaris

db2set -i tsminst1 DB2CODEPAGE=819

Windows

db2set -i server1 DB2CODEPAGE=819

AIX HPUX Linux Solaris Windows

Syntax
-k Server1
DSMSERV
-u user_name -i instance_dir -k key_name

LOADFORMAT
-o options_file -noexpire -quiet

,
ACTIVELOGSize = 16384
DBDir = directory
DBFile = file ACTIVELOGSize = megabytes

ACTIVELOGDir = directory ARCHLogdir = directory

ARCHFailoverlogdir = directory MIRRorlogdir = directory

Parameters
AIX HPUX Linux -u user_name
Solaris
Specifies a user name to switch to before initializing the server. This parameter
is optional.
AIX HPUX Linux Solaris -i instance_dir
Specifies an instance directory to use. This directory becomes the current
working directory of the server. This parameter is optional.
Windows -k key_name
Specifies the name of a Windows registry key that is used to store information
about this server. Use this parameter only to install additional servers on the

536 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
same system. After you install a server by using this parameter, you must
always start it with the value of this parameter. The default is SERVER1.
-o options_file
Specifies an options file to use. This parameter is optional.
-noexpire
Specifies that expiration processing is suppressed when starting. This
parameter is optional.
-quiet
Specifies that messages to the console are suppressed. This parameter is
optional.
DBDir
Specifies the relative path names of one or more directories that are used to
store database objects. Directory names must be separated by commas but
without spaces. You can specify up to 128 directory names. You must specify
either the DBDIR or the DBFILE parameter.
DBFile
Specifies the name of a file that contains the relative path names of one or
more directories that are used to store database objects. Each directory name
must be on a separate line in the file. You can specify up to 128 directory
names. You must specify either the DBDIR or the DBFILE parameter.
ACTIVELOGSize
Specifies the size of the active log in megabytes. This parameter is optional.
The minimum value is 2048 MB (2 GB); the maximum is 131,072 MB (128 GB).
If you specify an odd number, the value is rounded up to the next even
number. The default is 16384 MB.
ACTIVELOGDirectory (Required)
Specifies the directory in which the Tivoli Storage Manager server writes and
stores active log files. There is only one active log location. The name must be
a fully qualified directory name. The directory must exist, it must be empty,
and it must be accessible by the user ID of the database manager. The
maximum number of characters is 175.
ARCHLogdirectory (Required)
Specifies the directory for the archive log files. The name must be a fully
qualified directory name. The maximum number of characters is 175.
ARCHFailoverlogdirectory
Specifies the directory to be used as an alternative storage location if the
ARCHLOGDIRECTORY directory is full. This parameter is optional. The
maximum number of characters is 175.
MIRRorlogdirectory
Specifies the directory in which the server mirrors the active log (those files in
the ACTIVELOGDIRECTORY directory). This parameter is optional. The
directory must be a fully qualified directory name. The maximum number of
characters is 175.

Example: Format a database

AIX Linux

dsmserv format dbdir=/tsmdb001 activelogsize=8192

activelogdir=/activelog archlogdir=/archlog
archfailoverlogdir=/archfaillog mirrorlogdir=/mirrorlog

Appendix B. Utilities, scripts, and commands 537

DSMSERV INSERTDB (Move a server database into an empty
database)
Use the DSMSERV INSERTDB utility to move a server database into a new database.
The database can be extracted from the original server and inserted into a new
database on the new server by using a network connection between the two
servers. The database can also be inserted from media that contains the extracted
database.

Tip: AIX If the server is installed on an AIX Version 6.1 operating system, to
improve system performance, consider selecting the time zone specification that is
associated with the Portable Operating System Interface (POSIX). The alternative
time zone specification, based on the Olson database, might affect system
performance. For information about setting time zone specifications, see the
documentation for the AIX operating system. If the server is installed on AIX
Version 7.1, this issue does not occur.

Before you use the DSMSERV INSERTDB utility, complete the planning and
preparation tasks, such as backing up the database and saving configuration
information. Ensure that you meet all requirements before you move the server
database. For planning and preparation information, see the upgrade or migration
procedure for your operating system.

Requirements for insertion by using media

Before you run the utility to insert the server database into an empty database,
ensure that your system meets the following requirements.
v The manifest file from the DSMUPGRD EXTRACTDB operation must be available.
v If the manifest file does not contain device configuration information, or if you
are specifying the CONFIGINFO=DEVCONFIG parameter, both of the following
statements must be true:
– The server options file must contain an entry for the device configuration file.
– The device configuration file must have information about the device class
that is specified in the manifest file.
v The media that contains the extracted database must be available to the V7
server. Also, the permissions must be set to grant access to the media for the
user ID that owns the V7 server instance.

Syntax
-k Server1
DSMSERV
-u user_name -i instance_dir -k key_name

INSERTDB
-o options_file -noexpire -quiet

PREview = No
A: Insert from media
B: Insert over a network PREview = Yes
No

538 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
A: Insert from media:

CONFiginfo = MANifest

DEVclass = device_class_name CONFiginfo = MANifest
DEVconfig

MANifest = file_name

B: Insert over a network:

SESSWait = 60

SESSWait = minutes

Parameters
AIX HPUX Linux Solaris -u user_name
Specifies a user name to switch to before initializing the server. This parameter
is optional.
AIX HPUX Linux Solaris -i instance_dir
Specifies an instance directory to use. This directory becomes the current
working directory of the server. This parameter is optional.
Windows -k key_name
Specifies the name of the Windows registry key from which to retrieve
information about the server. This parameter is optional. The default is
SERVER1.
-o options_file
Specifies an options file to use. This parameter is optional.
-noexpire
Specifies that expiration processing is suppressed when starting. This
parameter is optional.
-quiet
Specifies that messages to the console are suppressed. This parameter is
optional.
DEVclass
Specifies a sequential-access device class. You can specify any device class
except for the DISK device class. The definition for the device class must exist
in either the manifest file or the device configuration file.
This parameter is optional and is used only when the database that you want
to insert into the empty V7 database was extracted to media. If the database is
on media and you do not specify a device class, the device class that is
identified in the manifest file is used.

Restriction: You cannot use a device class with a device type of NAS or
CENTERA.
MANifest
Specifies the location of the manifest file. Use a fully qualified file name, or
place in a local directory. For example: ./manifest.txt

Appendix B. Utilities, scripts, and commands 539

This parameter is required when the database that you want to insert into the
empty V7 database was extracted to media.
CONFiginfo
Specifies the source of the device configuration information that is used by the
DSMSERV INSERTDB operation. The default value for this parameter is
MANIFEST. Possible values are as follows:
MANifest
Specifies that device configuration information is read from the manifest
file. If the manifest file does not have device configuration information, the
device configuration file is used instead.
DEVConfig
Specifies that device configuration information is read from the device
configuration file.
SESSWait
Specifies the number of minutes that the V7 server waits to be contacted by the
original server. The default value is 60 minutes.
Use this parameter only if the data that is inserted into the empty V7 database
is transmitted from the source server with a network connection.
PREview
Specifies whether to preview the insertion operation. This parameter is
optional. The default value is NO.
Use the PREVIEW=YES parameter to test a database. When you use this
parameter, the operation includes all steps of the process, except for the actual
insertion of data into the new database. When you preview the insertion
operation, you can quickly verify that the source database is readable. You can
also identify any data constraint violations that might prevent an upgraded
database from being put into production.

540 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
ZMSPREPARE (Prepare a server on a z/OS system for migration)
z/OS

Use the ZMSPREPARE command to view information about data that must be backed
up from disk to tape to prepare to migrate the server to the z/OS media server.

The ZMSPREPARE command also reports on the following items:

v Copy and active-data storage pools that must be deleted or marked as destroyed
v Sequential volumes that are recorded in the volume history and that are located
on FILE storage, but not including storage pool volumes
v Backup sets that are located on FILE storage
v Invalid device classes
v Server options that require an update
v Date and time of the most recent Tivoli Storage Manager server database backup
This command can be issued only on a z/OS server.

Privilege class

Any administrator can issue this command.

Syntax
STGpool = * Format = Standard
ZMSPRepare
STGpool = pool_name Format = Standard
Detailed

Parameters
STGpool
Specifies the storage pools to be listed.
Format
Specifies the format of the output. The following values are possible:
Standard
Specifies that summary data is displayed.
Detailed
Specifies that detailed data is displayed.

Example: View data for all storage pools in standard format

View data for all storage pools in standard format. Issue the following command:
zmsprepare stgpool=* Format=Standard

Appendix B. Utilities, scripts, and commands 541

Disk-based Storage Pools...
Storage Storage Device Estimated Pct Volumes
Pool Name Pool Type Class Name Capacity Util not mark-
ed destr-
oyed
----------- ----------- ---------- ---------- ----- ---------
ARCHIVEPOOL Primary DISK 0.0 M 0.0 0
BACKUPPOOL Primary DISK 12.0 M 0.0 1
HFSPOOL Primary HFSCLASS 0.0 M 0.0 2
SPACEMGPOOL Primary DISK 0.0 M 0.0 0

**************************************************
No FILE device type Backup Sets found.
**************************************************
Sequential volumes with a device type of FILE...
Date/Time Volume Type Device Class Volume Name
-------------------- -------------- ------------ ------------------------------
04/22/2011 13:20:09 BACKUPFULL FILE USER3.S3503609.DBB
04/22/2011 13:20:30 EXPORT FILE USER3.S3503630.EXP
**************************************************
Server options file conversion guidance.
( Yes/No/Consult documentation )
Line Option Include in V7 server Include in media server
Number options file? options file?
------ -------------- ------------------------ ------------------------
19 COMMOPENTIMEO- No No
UT
24 COMMMETHOD Yes No
104 TCPNAME No Yes
109 DELETIONEXIT No No
137 VOLUMEHISTORY Consult No
163 DEVCONFIG Consult No
167 TCPPORT Consult Consult
**************************************************

Last
Complete
Backup
Date/Time
03/15/11 15:51:21

Example: View data for all storage pools in detailed format

View data for all storage pools in detailed format. Issue the following command:
zmsprepare stgpool=* Format=Detailed

The output is similar to that of the previous example, except for the storage pool
section, which includes a list of any volumes not marked DELETED:

542 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Disk-based Storage Pools...
Storage Pool Name: ARCHIVEPOOL
Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 0.0 M
Pct Util: 0.0
Volumes not marked destroyed: 0
Copy Storage Pools:
Volume Name:

Storage Pool Name: BACKUPPOOL

Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 12.0 M
Pct Util: 0.0
Volumes not marked destroyed: 1
Copy Storage Pools:
Volume Name: STGVOL1 Read/Write

Storage Pool Name: HFSPOOL

Storage Pool Type: Primary
Device Class Name: HFSCLASS
Estimated Capacity: 0.0 M
Pct Util: 0.0
Volumes not marked destroyed: 2
Copy Storage Pools:
Volume Name: /u/tsm/tsm1/hfsvol1 Read/Write
/u/tsm/tsm2/hfsvol2 Read/Write

Storage Pool Name: SPACEMGPOOL

Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 0.0 M
Pct Util: 0.0
Volumes not marked destroyed: 0
Copy Storage Pools:
Volume Name:

Appendix B. Utilities, scripts, and commands 543

Server startup script: rc.dsmserv
AIX HPUX Solaris

You can use the rc.dsmserv script in your system startup to automatically start a
server instance under a specific user ID.

Syntax
rc.dsmserv -u user_name
-U user_name -i instance_dir

Parameters
-u user_name
Specifies the Tivoli Storage Manager instance user ID for which the
environment is set up. The server will run under this user ID.
-U user_name
Specifies the Tivoli Storage Manager instance user ID for which the
environment is set up. The server will run under the user ID of the invoker of
the command.
-i instance_dir
Specifies an instance directory, which becomes the working directory of the
server.

544 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Server startup script: dsmserv.rc
Linux

You can use the dsmserv.rc script to stop a server instance, or manually or
automatically start a server.

Prerequisites

Before you issue the DSMSERV.RC command, complete the following steps:
1. Ensure that the Tivoli Storage Manager server instance runs under a non-root
user ID with the same name as the instance owner.
2. Copy the dsmserv.rc script to the /etc/rc.d/init.d directory. The dsmserv.rc
script is in the server installation directory, for example, /opt/tivoli/tsm/
server/bin.
3. Rename the script so that it matches the name of the server instance owner, for
example, tsminst1.
4. Use tools such as the CHKCONFIG utility to configure the run level in which the
server automatically starts. Specify a value that corresponds to a multiuser
mode, with networking turned on. Typically, the run level to use is 3 or 5,
depending on the operating system and its configuration. For details about run
levels, see the documentation for your operating system.

Syntax
dsmserv.rc
start
stop
status
restart

Parameters
start
Starts the server.
stop
Stops the server.
status
Shows the status of the server. If the status is started, the process ID of the
server process is also shown.
restart
Stops the server and starts it again.

Appendix B. Utilities, scripts, and commands 545

Sample commands to run for validation of the database upgrade
Run commands before and after you upgrade a server to get a summary of
information about the contents of the server database. Comparing the results of the
commands before and after the upgrade can help confirm that all data transferred
correctly. Samples provide a set of commands to start with.

The following commands show examples for getting summary information for
some specific types of objects:
File spaces
select node_name, count(*) as "Number of Filespaces" from filespaces
group by node_name order by 2
Nodes select platform_name, count(*) as "Number of Nodes" from nodes group
by platform_name
Backed-up files
select node_name,sum(num_files) as "Number of Backup Files" from
occupancy where type=’Bkup’ group by node_name
Archived files
select node_name,sum(num_files) as "Number of Archive Files" from
occupancy where type=’Arch’ group by node_name
Management classes
select count(*) as "Number of Management Classes" from mgmtclasses
Server scripts
select count(*) as "Number of Server Scripts" from script_names
Storage pools
select count(*) as "Number of Storage Pools" from stgpools

The following example shows a more complete set of commands. You can run this
set of commands as a script from a Tivoli Storage Manager server command line.
Redirect the output to a file to save the results.
select node_name, count(*) as "Number of Filespaces" from filespaces group by node_name order by 2
select platform_name, count(*) as "Number of Nodes" from nodes group by platform_name
select count(*) as "Number of Administrators" from admins
select node_name,sum(num_files) as "Number of Backup Files" from occupancy where type=’Bkup’
group by node_name
select node_name,sum(num_files) as "Number of Archive Files" from occupancy where type=’Arch’
group by node_name
select count(*) as "Number of Schedule Associations" from associations
select count(*) as "Number of Backupsets" from backupsets
select count(*) as "Number of Client Option Sets" from cloptsets
select count(*) as "Number of Collocation Groups" from collocgroup
select count(*) as "Number of Archive CopyGroups" from ar_copygroups
select count(*) as "Number of Backup CopyGroups" from bu_copygroups
select count(*) as "Number of Data Movers" from datamovers
select count(*) as "Number of Device Classes" from devclasses
select count(*) as "Number of Domains" from domains
select count(*) as "Number of Drives" from drives
select count(*) as "Number of Libraries" from libraries
select count(*) as "Number of Library Volumes" from libvolumes
select count(*) as "Number of Volumes" from volumes
select count(*) as "Number of Management Classes" from mgmtclasses
select count(*) as "Number of Node Groups" from nodegroup
select count(*) as "Number of Device Paths" from paths
select count(*) as "Number of Policy Sets" from policysets
select count(*) as "Number of Client Schedules" from client_schedules
select count(*) as "Number of Admin Schedules" from admin_schedules
select count(*) as "Number of Server Scripts" from scripts
select count(*) as "Number of Servers Defined" from servers
select count(*) as "Number of Servers Groups Defined" from server_group
select count(*) as "Number of Storage Pools Defined" from stgpools

546 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Appendix C. Installing server language packages
AIX HPUX Linux Solaris Windows

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

Server language locales

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

AIX HPUX Linux Solaris This language package is automatically

installed for the following default language option for Tivoli Storage Manager
server messages and help:
v AIX LANGUAGE en_US
v HPUXLANGUAGE AMENG
The following system locale must be installed on the system when you use
LANGUAGE AMENG:
HPUX en_US.iso88591
v Linux LANGUAGE en_US
v LANGUAGE AMENG
Solaris The following system locale must be installed on the system when
you use LANGUAGE AMENG:
Solaris en_US

Windows This language package is automatically installed for the following

default language option for Tivoli Storage Manager server messages and help:
LANGUAGE AMENG.

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

You can use the languages that are shown: AIX

Table 75. Server languages for AIX

Language LANGUAGE option value
Chinese, Simplified zh_CN
Chinese, Simplified (UTF-8) ZH_CN
Chinese, Traditional (Big5) Zh_TW
Chinese, Traditional (UTF-8) ZH_TW
Chinese, Traditional (euc_tw) zh_TW
English en_US
English (UTF-8) EN_US

© Copyright IBM Corp. 2009, 2013 547

Table 75. Server languages for AIX (continued)
Language LANGUAGE option value
French fr_FR
French (UTF-8) FR_FR
German de_DE
German (UTF-8) DE_DE
Italian it_IT
Italian (UTF-8) IT_IT
Japanese, EUC ja_JP
Japanese, PC Ja_JP
Japanese, UTF8 JA_JP
Korean ko_KR
Korean (UTF-8) KO_KR
Portuguese, Brazilian pt_BR
Portuguese, Brazilian (UTF-8) PT_BR
Russian ru_RU
Russian (UTF-8) RU_RU
Spanish es_ES
Spanish (UTF-8) ES_ES
Notes:
v For more information about setting the LANGUAGE option, see the Administrator's
Reference.

HPUX

Table 76. Server languages for HP-UX

Language LANGUAGE option value
Chinese, Simplified zh_CN.hp15CN
zh_CN.utf8
Chinese, Traditional zh_TW.big5
zh_TW.eucTW
zh_TW.utf8
English AMENG (default)
en_US.utf8
French fr_FR.iso88591
fr_FR.utf8
German de_DE.iso88591
de_DE.utf8
Italian it_IT.iso88591
it_IT.utf8
Japanese ja_JP.eucJP
ja_JP.utf8

548 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Table 76. Server languages for HP-UX (continued)
Language LANGUAGE option value
Korean ko_KR.eucKR
ko_KR.utf8
Portuguese, Brazilian pt_PT.iso88591
pt_PT.utf8
Russian ru_RU.iso88595
ru_RU.utf8
Spanish es_ES.iso88591
es_ES.utf8
Notes: For more information about setting the LANGUAGE option, see the Administrator's
Reference.

Linux

Table 77. Server languages for Linux

LANGUAGE LANGUAGE option value
Chinese, Simplified zh_CN
zh_CN.gb18030
zh_CN.utf8
Chinese, Traditional Big5 / Zh_TW
zh_TW
zh_TW.utf8
English, United States en_US
en_US.utf8
French fr_FR
fr_FR.utf8
German de_DE
de_DE.utf8
Italian it_IT
it_IT.utf8
Japanese ja_JP
ja_JP.utf8
Korean ko_KR
ko_KR.utf8
Portuguese, Brazilian pt_BR
pt_BR.utf8
Russian ru_RU
ru_RU.utf8
Spanish es_ES
es_ES.utf8
Notes: For more information about setting the LANGUAGE option, see the Administrator's
Reference.

Appendix C. Installing server language packages 549

Solaris

Table 78. Server languages for Solaris

Language LANGUAGE option value
Chinese, Simplified zh
zh_CN.UTF-8
Chinese, Traditional zh_TW
zh_TW.BIG5
zh_TW.UTF-8
English AMENG (default)
en_US.UTF-8
French fr_FR.ISO8859-1
fr_FR.UTF-8
German de_DE.ISO8859-1
de_DE.UTF-8
Italian it_IT.ISO8859-1
it_IT.UTF-8
Japanese ja
ja_JP.UTF-8
Korean ko
ko_KR.UTF-8
Portuguese, Brazilian pt_BR.ISO8859-1
pt_BR.UTF-8
Russian ru_RU.ISO8859-5
ru_RU.UTF-8
Spanish es_ES.ISO8859-1
es_ES.UTF-8
Notes:
v LANGUAGE AMENG requires system locale en_US.
v For more information about setting the LANGUAGE option, see the Administrator's
Reference.

Windows

Table 79. Server languages for Windows

Language LANGUAGE option value
Chinese, Simplified chs
Chinese, Traditional cht
English ameng
French fra
German deu
Italian ita
Japanese (Shift-JIS) jpn
Korean kor

550 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Table 79. Server languages for Windows (continued)
Language LANGUAGE option value
Portuguese, Brazilian ptb
Russian rus
Spanish esp
Notes: For more information about setting the LANGUAGE option, see the Administrator's
Reference.

Restriction: AIX Linux Solaris Windows For Operations Center users,

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

Configuring a language package

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

About this task

AIX HPUX Linux Solaris To set support for a certain locale,

complete one of the following tasks:
v Set the LANGUAGE option in the server options file to the name of the locale that
you want to use. For example:
AIX To use the it_IT locale, set the LANGUAGE option to it_IT.
Linux
See “Server language locales” on page 547.
HPUX To use the it_IT.iso88591 locale, set the LANGUAGE option to
it_IT.iso88591. See “Server language locales” on page 547.
SolarisTo use the it_IT.ISO8859-1 locale, set the LANGUAGE option to
it_IT.ISO8859-1. See “Server language locales” on page 547.
v AIX HPUX Linux Solaris If you are starting the server in the
foreground, set the LC_ALL environment variable to match the value that is set in
the server options file. For example, to set the environment variable for Italian,
enter the following value:
export LC_ALL=it_IT

Windows 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 ita locale, set the
LANGUAGE option to ita. See “Server language locales” on page 547.

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

Appendix C. Installing server language packages 551

552 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Appendix D. HP-UX system resource requirements
HPUX

Semaphores, shared memory, and processes are HP-UX system resources that
might require special configuration and tuning for the Tivoli Storage Manager
server.

Estimating required semaphore resources

HPUX

IBM Tivoli Storage Manager uses semaphore resources to control its internal
operations.

About this task

To estimate the total number of semaphores that the server may need, use the
following formula:
semaphores = 60 + (2 x maxSessions)

Where maxSessions is the maximum number of concurrent client sessions.

For example, if you expect to have up to 15 client sessions active at the same time,
Tivoli Storage Manager needs approximately 90 semaphores.

Note: If you have other applications that use semaphores, you must account for
their requirements also when adjusting your kernel configuration.

After you have estimated the number of semaphores, ensure that your kernel
configuration contains the correct value. See “Viewing and modifying the kernel
configuration” on page 554 for details.

Estimating required process resources

HPUX

IBM Tivoli Storage Manager uses standard HP-UX processes for concurrent server
operations.

About this task

To estimate the total number of processes that the server may need, you can use
the following formula:
processes = 60 + (2 x maxSessions)

Where maxSessions is the maximum number of concurrent client sessions.

For example, assume that you will have up to 15 client sessions active at the same
time. You can calculate that IBM Tivoli Storage Manager needs approximately 90

© Copyright IBM Corp. 2009, 2013 553

processes to control its internal operations. You will also need to account for all of
the other HP-UX processes that might be running concurrently on your system
when computing the total requirements for your HP-UX kernel resources.

After you have estimated the required number of processes, ensure that your
kernel configuration contains the correct value. See “Viewing and modifying the
kernel configuration” for details.

Estimating required number of threads per process

HPUX

The HP-UX default setting for the maximum number of threads allowed in each
process is 64 threads.

When Tivoli Storage Manager is running a high workload or participating in

LAN-free data movement, this setting might be too low. To prevent thread creation
errors in the Tivoli Storage Manager server, increase the HP-UX maximum number
of threads per process to 500.

See “Viewing and modifying the kernel configuration” for details.

Viewing and modifying the kernel configuration

HPUX

To view or modify your existing kernel configuration, use either the SAM utility
program on HP-UX Version 11iv2 or System Management Homepage (SMH) on
HP-UX Version 11iv3, or edit the configuration file directly. Base the kernel values
on the recommendations of the DB2OSCONF utility.

About this task

Start either SAM or SMH, then select:

1. Kernel Configuration
2. Configurable Parameters
A list of parameters, whose values you can change, is displayed. The list includes:
v semmns The maximum number of semaphores
v shmmax The maximum amount of available shared memory
v nproc The maximum number of processes
v max_thread_proc The maximum number of threads allowed in each process
See your HP-UX documentation for details about changing configurable kernel
parameters.

554 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Appendix E. Services associated with the Tivoli Storage
Manager server
Windows

When you start the Tivoli Storage Manager server as a service, other services
automatically start. These services are associated with the database manager, DB2.

The following services are associated with the Tivoli Storage Manager server.

Service name Purpose Comments

TSM Server_instance The service for the Tivoli Storage Set the start and stop options for this
Manager server instance that is service to start and stop the server
named Server_instance. instance automatically.

For example: TSM Server1 Each server instance runs as a

separate service.
DB2 - DB2TSM1 - SERVER_INSTANCE The DB2 service for the server This service is automatically started
instance that is named when the service for the Tivoli
Server_instance. Storage Manager server instance is
started. The DB2 service is not
For example: DB2 - DB2TSM1 - stopped automatically when you stop
SERVER1 the service for the server.

The system has one of these services

for each server-instance service that is
started on the system.
DB2 Governor (DB2TSM1) A DB2 service that is created at Do not change the options for this
installation time, and is required for service.
all server instances.
DB2 License Server (DB2TSM1) A DB2 service that is created at Do not change the options for this
installation time, and is required for service.
all server instances.
DB2 Management Server (DB2TSM1) A DB2 service that is created at Do not change the options for this
installation time, and is required for service.
all server instances.
DB2 Remote Command Server A DB2 service that is created at Do not change the options for this
(DB2TSM1) installation time, and is required for service.
all server instances.

Servers upgraded from V6.1.0 or V6.1.1: On a system that is running the Tivoli
Storage Manager V6.1.0 or V6.1.1 server program, an additional service named DB2
- DB2TSM1 - DB2TSM-0 is displayed in the list of services. When the V6.1.0 or V6.1.1
server program is upgraded to a later version, that service is renamed to DB2 -
DB2TSM1 - DB2TSM. This service does not affect the operation of the Tivoli Storage
Manager server instances that you configure. DB2TSM is a nonfunctional DB2
instance.

© Copyright IBM Corp. 2009, 2013 555

556 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Appendix F. Accessibility features for the Tivoli Storage
Manager product family
Accessibility features help users who have a disability, such as restricted mobility
or limited vision to use information technology products successfully.

Accessibility features

The IBM Tivoli Storage Manager family of products includes the following
accessibility features:
v Keyboard-only operation using standard operating-system conventions
v Interfaces that support assistive technology such as screen readers

The command-line interfaces of all products in the product family are accessible.

Tivoli Storage Manager Operations Center provides the following additional

accessibility features when you use it with a Mozilla Firefox browser on a
Microsoft Windows system:
v Screen magnifiers and content zooming
v High contrast mode

The Operations Center and the Tivoli Storage Manager Server can be installed in
console mode, which is accessible.

The Tivoli Storage Manager Information Center is enabled for accessibility. For
information center accessibility information, see “Accessibility features in the
information center” ( http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1/topic/
com.ibm.help.ic.doc/iehs36_accessibility.html).

Vendor software

The Tivoli Storage Manager product family includes certain vendor software that is
not covered under the IBM license agreement. IBM makes no representation about
the accessibility features of these products. Contact the vendor for the accessibility
information about its products.

IBM and accessibility

See the IBM Human Ability and Accessibility Center (http://www.ibm.com/able)

for information about the commitment that IBM has to accessibility.

© Copyright IBM Corp. 2009, 2013 557

558 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.

© Copyright IBM Corp. 2009, 2013 559

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who want to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample

560 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows: © (your company name) (year). Portions of
this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.
_enter the year or years_.

If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.

Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at http://www.ibm.com/legal/copytrade.shtml.

LTO and Ultrium are trademarks of HP, IBM Corp. and Quantum in the U.S. and
other countries.

Intel and Itanium are registered trademarks of Intel Corporation or its subsidiaries
in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United

States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software
Offerings”) may use cookies or other technologies to collect product usage
information, to help improve the end user experience, to tailor interactions with
the end user or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings
can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific
information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect
personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer
the ability to collect personally identifiable information from end users via cookies
and other technologies, you should seek your own legal advice about any laws
applicable to such data collection, including any requirements for notice and
consent.

For more information about the use of various technologies, including cookies, for
these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy and

Notices 561
IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details the
section entitled “Cookies, Web Beacons and Other Technologies” and the “IBM
Software Products and Software-as-a-Service Privacy Statement” at
http://www.ibm.com/software/info/product-privacy.

562 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Glossary
A glossary is available with terms and definitions for the IBM Tivoli Storage Manager family of products.

You can view the glossary in the Tivoli Storage Manager information center at http://pic.dhe.ibm.com/
infocenter/tsminfo/v7r1.

To view glossaries for other IBM products, see http://www.ibm.com/software/globalization/

terminology/.

© Copyright IBM Corp. 2009, 2013 563

564 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
Index
A backups (continued)
upgrade scenario 1 129
access upgrade scenario 2 171
storage pools on disk 323 upgrade scenario 3 219
access permissions upgrade scenario 4 265
setting backups before migration from AIX, HP-UX, or Solaris
devices 388 server database 377
access rights backups before upgrade
setting configuration information
before server startup 326 general upgrade procedures 285
accessibility features 557 upgrade scenario 1 99
activating the server 325 upgrade scenario 2 142
active log upgrade scenario 3 185
monitoring after upgrade 339 upgrade scenario 4 232
space requirements 39 database
active log mirror general upgrade procedures 284
space requirements 39 upgrade scenario 1 98
AIX clustered environment upgrade scenario 2 141
upgrading from V5.5 to V7.1 271 upgrade scenario 3 184
archive failover log upgrade scenario 4 231
monitoring after upgrade 339 storage pools
space requirements 39 general upgrade procedures 284
archive log upgrade scenario 1 98
monitoring after upgrade 339 upgrade scenario 2 141
space requirements 39 upgrade scenario 3 184
auditing the database 3 upgrade scenario 4 231
automatic starting, server 329, 330 backups before z/OS migration
automation configuration information 474
implementation 338 server database 488
after migration from AIX, HP-UX, or Solaris 433 storage pools 448
after z/OS migration 504 Butterfly software 357
planning 50

B C
client data
backing up configuration information 474 protecting during migration 452
backup sets protection
before and after migration 450 migrating V5 servers from AIX, HP-UX, or Solaris 364
deleting 486 client nodes
moving settings changes for upgrade
before migration from AIX, HP-UX, or Solaris 376 general upgrade procedures 282
restoring upgrade scenario 1 96
after migration from AIX, HP-UX, or Solaris 432 upgrade scenario 2 139
backups upgrade scenario 3 182
API configuration for database upgrade scenario 4 229
general upgrade procedures 318 upgrade planning 47
upgrade scenario 1 129 clustered environment
upgrade scenario 2 171 upgrade from V5.5 to 7.1 274
upgrade scenario 3 219 upgrade from V5.5 to V7.1 273
upgrade scenario 4 265 upgrade planning 273
before upgrade upgrading from V5.5 to V7.1 271
z/OS storage pools 485 clustered environments
database upgrading to V7.1 271
after migration from AIX, HP-UX, or Solaris 428 commands
after upgrade 335 administrative 10
after z/OS migration 504 changes in V7 51
automatic 5 deleted 65
protection 5 migrating V5 servers from AIX, HP-UX, or Solaris 363
recovery 5 new 51
volume history file 5 overview 521
database manager configuration 318 SELECT 68

© Copyright IBM Corp. 2009, 2013 565

commands (continued) database (continued)
SET DBRECOVERY 504 backup configuration
SET DBRECOVERY command 428 migrating V5 servers from AIX, HP-UX, or Solaris 404
updated 57 backups
validating database upgrade 546 after migration from AIX, HP-UX, or Solaris 428, 433
VARY 351 after upgrade 335
ZMSPREPARE 541 after z/OS migration 504
compatibility, server with other DB2 products 35 automatic 5
components recovery 5
available for installation 46 backups before upgrade
compatibility with earlier versions 46 general upgrade procedures 284
configuration upgrade scenario 1 98
API, Tivoli Storage Manager upgrade scenario 2 141
general upgrade procedures 318 upgrade scenario 3 184
upgrade scenario 1 129 upgrade scenario 4 231
upgrade scenario 2 171 changes in V7.1 3
upgrade scenario 3 219 configuration for backup
upgrade scenario 4 265 migrating V5 servers from AIX, HP-UX, or Solaris 422
database backups contents summary before migration 377
general upgrade procedures 318 contents summary before upgrade
upgrade scenario 1 129 general upgrade procedures 286
upgrade scenario 2 171 upgrade scenario 1 99
upgrade scenario 3 219 upgrade scenario 2 143
upgrade scenario 4 265 upgrade scenario 3 185
z/OS media server 481 upgrade scenario 4 233
configuration information creation
backups before upgrade general upgrade procedures 308
general upgrade procedures 285 upgrade scenario 1 122
upgrade scenario 1 99 upgrade scenario 2 164
upgrade scenario 2 142 upgrade scenario 3 212
upgrade scenario 3 185 upgrade scenario 4 259
upgrade scenario 4 232 z/OS migration 491, 494
backups before z/OS migration 474 data movement from FILE and DISK devices 458
Console language support 547 migrating V5 servers from AIX, HP-UX, or Solaris 368
copy storage pools data movement from GENERICTAPE devices
removing disk-based volumes 484 migrating V5 servers from AIX, HP-UX, or Solaris 368
cross-platform migration to Linux x86_64 database
See migration of V5 servers from AIX, HP-UX, or Solaris moving data, network method 15
customer support description 3
contacting 518 estimating recovery log requirements 457
before migration from AIX, HP-UX, or Solaris 366
estimating space requirements 457
D before migration from AIX, HP-UX, or Solaris 366
extending 533
data
extraction
DISK devices
description 529
migrating V5 servers from AIX, HP-UX, or Solaris 375
device class, definition 121, 204, 313
FILE devices
DSMUPGRD EXTRACTDB 529
migrating V5 servers from AIX, HP-UX, or Solaris 375
loading extracted data 126, 216, 314
GENERICTAPE devices
manifest file 531
migrating V5 servers from AIX, HP-UX, or Solaris 376
message output 121, 204, 313
migrating from tape to DISK
performance 44
after server migration from AIX, HP-UX, or Solaris 431
performance tips 461
migrating from tape to FILE
to media 121, 313, 492
after server migration from AIX, HP-UX, or Solaris 431
formatting
movement
general upgrade procedures 308
migrating V5 servers from AIX, HP-UX, or Solaris 363
migrating V5 servers from AIX, HP-UX, or Solaris 400,
data deduplication
418
after migrating servers from AIX, HP-UX, or Solaris 425
upgrade scenario 1 122
data movement
upgrade scenario 2 164
before migration from AIX, HP-UX, or Solaris 375, 376
upgrade scenario 3 212
database
upgrade scenario 4 259
administration 4
formatting empty 536
audits 3
loading data
automatic backups 5
migrating V5 servers from AIX, HP-UX, or Solaris 402
backing up
loading data, media method
before migration from AIX, HP-UX, or Solaris 377
general upgrade procedures 314

566 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
database (continued) DB2 technology 3
loading data, media method (continued) deployment engine
upgrade scenario 1 126 backup 335
upgrade scenario 3 216 device classes
z/OS migration 493 migration from z/OS 464
location 4 device configuration information
manager backups before upgrade
See database manager general upgrade procedures 285
monitoring upgrade scenario 1 99
extraction 121, 204, 313 upgrade scenario 2 142
moving upgrade scenario 3 185
comparison of methods 452 upgrade scenario 4 232
moving data, media method 15 backups before z/OS migration 474
general upgrade procedures 312 conversion of z/OS device classes 448
upgrade scenario 1 121 migrating V5 servers from AIX, HP-UX, or Solaris 364
upgrade scenario 3 204 z/OS migration 497
z/OS migration 492 device path information
moving data, network method updating
general upgrade procedures 316 after migration from AIX, HP-UX, or Solaris 428
migrating V5 servers from AIX, HP-UX, or Solaris 420 device requirements
upgrade scenario 2 169 migrating V5 servers from AIX, HP-UX, or Solaris 369
upgrade scenario 4 263 migration from z/OS 458
z/OS migration 494 devices
operations 4 configuration
performance tips migrating V5 servers from AIX, HP-UX, or Solaris 388
inserting data into V7 database 461 configuring
preparation migrating V5 servers from AIX, HP-UX, or Solaris 397
before migration from AIX, HP-UX, or Solaris 392, 412 directories
preparation for migration from z/OS 489 creating for server instance
preparation for upgrade migrating V5 servers from AIX, HP-UX, or Solaris 389
general upgrade procedures 294 disability 557
upgrade scenario 1 107 disabling sessions 284
upgrade scenario 2 151 upgrade scenario 1 97
upgrade scenario 3 203 upgrade scenario 2 141
upgrade scenario 4 250 upgrade scenario 3 183
protection changes 5 upgrade scenario 4 230
recovery changes 5 disaster recovery manager 5
recovery logs 4 disk space, requirements 39
restoration 5 drives
server instance creation updating device path information
general upgrade procedures 308 after migration from AIX, HP-UX, or Solaris 428
upgrade scenario 1 122 DSMSERV INSERTDB 346
upgrade scenario 2 164 DSMSERV LOADFORMAT utility 536
space 4 DSMSERV_CONFIG environment variable
SQL queries 3 setting for upgrade utilities
updates overview 3 upgrade scenario 2 149
validating upgrade 546 DSMSERV_DIR environment variable
database backups obsolete for V7.1 9
planning 12, 463 setting for upgrade utilities
migrating V5 servers from AIX, HP-UX, or Solaris 368 general upgrade procedures 292
database extraction upgrade scenario 1 106
performance tips upgrade scenario 2 149
migrating V5 servers from AIX, HP-UX, or Solaris 369 upgrade scenario 3 192
database insertion upgrade scenario 4 239
performance tips dsmupgdx
migrating V5 servers from AIX, HP-UX, or Solaris 370 See upgrade wizard description
database manager DSMUPGRD EXTEND DB utility
backup configuration extend V5 database 533
general upgrade procedures 318 DSMUPGRD EXTEND LOG utility
upgrade scenario 1 129 extend V5 server log 534
upgrade scenario 2 171 DSMUPGRD EXTRACTDB utility
upgrade scenario 3 219 extract V5 database 529
upgrade scenario 4 265 DSMUPGRD PREPAREDB utility
overview 3 prepare V5 database 523
updates overview 3 DSMUPGRD QUERYDB utility
database manager (DB2TSM1) 555 display V5 database information 522
DB2 products, compatibility with the server 35, 456 display V5 server information 522

Index 567
DSMUPGRD UPDATE utility 535
DSMUPGRD upgrade utilities
I
See upgrade utilities IBM Support Assistant 517
IBM Tivoli Storage Manager for z/OS Media
See z/OS media server
index reorganization
E after migrating servers from AIX, HP-UX, or Solaris 425
environment variables installation
changes in V7.1 9 component availability 46
setting for upgrade utilities location 9
general upgrade procedures 292 logs 9
upgrade scenario 1 106 server
upgrade scenario 2 149 migrating V5 servers from AIX, HP-UX, or Solaris 386
upgrade scenario 3 192 migration from z/OS 474
upgrade scenario 4 239 upgrade scenario 1 111
upgrade utilities 9 upgrade scenario 2 155
V7.1 server 9 upgrade scenario 3 194, 205
estimating upgrade scenario 4 241, 252
performance 42 installing z/OS media server 481
threads per process (HP-UX) 554 instance user ID 7
upgrade duration 42 Internet, searching for problem resolution 517, 518
upgrade space requirements 39 IP address
extending updating
database 533 after migration from AIX, HP-UX, or Solaris 430
logs, archive 534

F K
kernel configuration, viewing and modifying 554
failover archive log keyboard 557
See archive failover log knowledge bases, searching 517
file set names 9
files
location 9
missing 351
L
naming 9 LANGUAGE option 547, 551
volume history 5 language packages 547
fixes, obtaining 518 language support 551
languages
set 551
libraries
G updating device path information
GSKit after migration from AIX, HP-UX, or Solaris 428
removing Version 7 340 library attributes
migration from z/OS 464
library clients, upgrading 47
H library manager, upgrading 47
hardware requirements license information
migrating V5 servers from AIX, HP-UX, or Solaris 366 updating
overview 19 general upgrade procedures 285
planning 12 NODELOCK file 285
V5 server 17 upgrade scenario 1 98
V7.1 server upgrade scenario 2 142
AIX 21 upgrade scenario 3 184
HP-UX 24 upgrade scenario 4 232
Linux 26 licenses
Linux on System z 29 registering
Linux x86_64 26 after migration from AIX, HP-UX, or Solaris 427
Microsoft Windows 33 after upgrade 334
Oracle Solaris 31 registering after z/OS migration 503
z/OS migration 455 Linux x86_64
host name See also migration of V5 servers from AIX, HP-UX, or
changing Solaris
after migration from AIX, HP-UX, or Solaris 429 migrating
after upgrade 336, 337 Linux x86_64 357
hybrid upgrade-migration method 452 migration to 355
See migration of V5 servers from AIX, HP-UX, or Solaris
logs
extending, archive 534

568 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
logs (continued) migrating servers from z/OS (continued)
installation 9 path definition 464
recovery performance tips
location 39 database extraction 461
overview 4 database insertion 461
recovery log mode 5 planning 455
roll-forward mode preparation 473
See recovery log mode preparing server 541
space requirements, recovery 38 preparing V5 database 489
preparing V5 server 479
process overview 444
M recreating disk-based storage pools 502
recreating storage pool volumes 502
manifest file 531
reference information 463
manual upgrade
removing copy storage pool volumes 484
See upgrading using command interface
restoring storage pools 502
media method 15, 452, 491
restrictions 444
media server
reverting to V5 509
See z/OS media server
after V5 database is deleted 510
messages
before data is moved 509
extraction output 121, 204, 313
before volumes are deleted 509
server 70
scenarios 439
z/OS media server 453
server instance startup 501
migrating servers from z/OS 474, 491
settings changes 479
advantages 439
space preparation 473
analyzing v5 server 482
storage agents 451
backing up server database 488
storage requirements 458
before you start 443
time estimation example 459
commands 447
time requirements 458
compatibility with other products 456
upgrading multiple servers and components 462
configuration of z/OS media server devices 497
utilities 447
configuring
verifying results 501
server 474
verifying server options 499
creating server options file 486
migration commands
creating V7 database 491, 494
overview 521
data backup 485
migration of servers to Linux x86_64
data movement from FILE and DISK devices 458
See migration of V5 servers from AIX, HP-UX, or Solaris
database
migration of V5 servers from AIX, HP-UX, or Solaris 357, 364
preparation for migration from z/OS 479
advantages 355
database and recovery log requirements 457
automation
defining media server 481
updating 433
defining storage pools 502
backup sets
deleting backup sets 486
moving 376
deleting volumes marked as destroyed 503
restoring 432
device migration 448, 464
before you start 363
device requirements 458
client data
disabling sessions 482
protection 364
extracting data
commands 363
to media 492
data
first steps after migration 499
moving from tape devices 431
formatting V7 database 491, 494
data movement 363
hardware and software requirements 455
data movement from FILE and DISK devices 368
hybrid upgrade-migration method 452
data movement from GENERICTAPE devices 368
installing
data on DISK devices
server 474
backing up 375
installing V7 server 474
migrating 375
library definition 464
data on FILE devices
loading extracted data 493
backing up 375
major phases 446
migrating 375
media and network methods 491
data on GENERICTAPE devices 376
media method 452
migrating 376
moving data
database
media method 492
backing up 428
network method 494
moving by network method 420
moving tape to another tape library 492
database contents
network method 452
creating summary 377
operational changes 453, 463
database requirements 366
overview 437, 439

Index 569
migration of V5 servers from AIX, HP-UX, or Solaris 357, 364 migration of V5 servers from AIX, HP-UX, or Solaris 357, 364
(continued) (continued)
device path information server settings
updating 428 changing 378
device requirements 369 sessions
devices disabling 374
configuration 388 software requirements 366
configuring 397 space preparation 373
migrating 364 space requirements
directories monitoring 433
creating 389 stopping the server 379
hardware requirements 366 storage requirements 369
host name tcpserveraddress option
changing 429 updating 430
IP address time requirements 367
updating 430 troubleshooting 435
licenses upgrade utilities
registering 427 installing 380
media method 385 installing on AIX 380
media method, upgrade wizard 385 installing on HP-UX 381
method installing on Oracle Solaris 382
selecting 385 upgrading from V5 to V5.5.6 373
migration scenario 1 385 upgrading multiple servers and components 368
running upgrade wizard 390 user ID
migration scenario 2 creating 389
configuration for database backup 404 utilities 363
database creation 400 verifying results 426
database preparation 392 migration utilities
device configuration 397 overview 521
loading extracted data 402 monitoring
media method, command line 391 logs for the upgraded server 339
server installation 393 V5 server after z/OS migration 505
server instance creation 400 V7 server after migration from AIX, HP-UX, or
migration scenario 3 406 Solaris 433
running upgrade wizard 411 V7 server after z/OS migration 505
server installation 406 monitoring after z/OS migration
migration scenario 4 server 505
configuration for database backup 422 multiple components
database creation 418 migrating V5 servers from AIX, HP-UX, or Solaris 368
database preparation 412 upgrading from z/OS 462
moving server database 420 multiple DB2 copies 35
network method, command line 412 multiple server instances 7
server installation 413 multiple servers
server instance creation 418 migrating V5 servers from AIX, HP-UX, or Solaris 368
network method 385 upgrading 45
network method, upgrade wizard 406 upgrading from z/OS 462
operational changes 368 multiple servers, upgrading 46
performance tips
database extraction 369
database insertion 370
planning 365
N
names for server instance 70
reference 371
network method 15, 452
postmigration tasks 425
migrating servers from z/OS 494
preparation 373
NODELOCK file
recovery log requirements 366
deleting 334, 503
reverting to V5 435
renaming 334, 503
roadmap 357
scenarios 358
server 373
installation 386 O
monitoring 433 Operations Center
starting 426 overview xiii
server database options
backing up 377 after migration from z/OS
maintaining 425 verifying 499
server options changes in V7 51
configuring 425 deleted 65

570 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
options (continued) preparing for upgrade (continued)
new 51 space preparation
updated 57 general upgrade procedures 281
options for startup upgrade scenario 1 95
change current working directory 8 upgrade scenario 2 139
DSMSERV utility 8 upgrade scenario 3 181
switch user IDs 8 upgrade scenario 4 229
overview storage pool backups
Operations Center xiii general upgrade procedures 284
ownership upgrade scenario 1 98
storage pools on disk 323 upgrade scenario 2 141
upgrade scenario 3 184
upgrade scenario 4 231
P volume history backup
general upgrade procedures 285
Passport Advantage 519
upgrade scenario 1 99
paths
upgrade scenario 2 142
migration from z/OS 464
upgrade scenario 3 185
performance of network connections
upgrade scenario 4 232
migration from z/OS 453
preparing for z/OS migration
performance of upgrade processes
configuration information backup 474
estimating 42
preparing V5 server
tips
migrating servers from z/OS 480
extraction, V5 server 44
problem determination
insertion, V7.1 server 45
describing problem for IBM Software Support 519
permissions
determining business impact for IBM Software
storage pools on disk 323
Support 519
planning upgrade
submitting a problem to IBM Software 520
client nodes 47
process resources, server
client program 47
estimating total number 553
estimating time required 42, 43
using SAM with 11iv2 to view or change 554
multiple servers 45, 46
using SMH with 11iv3 to view or change 554
reference 51
publications
server 11
download xii
AIX clustered environment 271
Windows clustered environment 273
space requirements
upgrade process 37 R
V5 server system 37 recovery log
V7.1 server system 38 description 4
storage agents 45, 47 location 39
preparing for upgrade space requirements 38
configuration information backup recovery log mode 5
general upgrade procedures 285 registering licenses
upgrade scenario 1 99 REGISTER LICENSE command 503
upgrade scenario 2 142 registration
upgrade scenario 3 185 licenses
upgrade scenario 4 232 after migration from AIX, HP-UX, or Solaris 427
database after upgrade 334
general upgrade procedures 294 requirements for upgrade
upgrade scenario 1 107 V5 server
upgrade scenario 2 151 media method 37
upgrade scenario 3 203 network method 37
upgrade scenario 4 250 V7.1 server 17
database backup resource for HP system
general upgrade procedures 284 process considerations 553
upgrade scenario 1 98 semaphore considerations 553
upgrade scenario 2 141 reverting to previous server version 343
upgrade scenario 3 184
upgrade scenario 4 231
overview
general upgrade procedures 277
S
scenarios
upgrade scenario 1 91
migrating V5 servers from AIX, HP-UX, or Solaris 358
upgrade scenario 2 135
migration from z/OS 439
upgrade scenario 3 177
overview for upgrade 73
upgrade scenario 4 225
upgrade procedures
server operations 50
new system, media method 177

Index 571
scenarios (continued) server (continued)
upgrade procedures (continued) instances
new system, network method 225 multiple on single system 7
same system, media method 91 owner ID 7
same system, network method 135 owner, creating 297
scripts starting 8, 9
dsmserv.rc 330 messages 70
implementation 338 migrating V5 servers from AIX, HP-UX, or Solaris
after migration from AIX, HP-UX, or Solaris 433 verifying server operations 426
after z/OS migration 504 migration using network method 494
overview 521 new commands 51
rc.dsmserv 8, 329 new options 51
setting up environment 8 new utilities 51
starting servers automatically 329, 330 operation changes 4
SELECT command 68 options
semaphore resources, server changes in V7 51
estimating number of 553 deleted 65
using SAM with 11iv2 to view or change 554 new 51
using SMH with 11iv3 to view or change 554 updated 57
server options for startup
after migration from z/OS change current working directory 8
first steps 499 DSMSERV 8
starting instance 501 switch user IDs 8
verifying server operations 501 prerequisites verification
after upgrade general upgrade procedures 278
first steps 323 upgrade scenario 1 92
before migration upgrade scenario 2 136
determining appropriate fix pack level 36 upgrade scenario 3 178
prepare server on z/OS 541 upgrade scenario 4 226
before migration from AIX, HP-UX, or Solaris protecting during migration 452
planning 365 requirements verification
before migration from z/OS general upgrade procedures 278
planning 455 upgrade scenario 1 92
before upgrade upgrade scenario 2 136
determining appropriate fix pack level 36 upgrade scenario 3 178
prepare empty database 536 upgrade scenario 4 226
specify device class of volumes for deletion 524 reverting to V5
changing settings after migration from AIX, HP-UX, or Solaris 435
before migration from AIX, Linux, or Solaris 378 after migration from z/OS 509
commands after upgrade 351
administrative 10 after V5 database is deleted 510
changes in V7 51 before data is moved 509
deleted 65 before volumes are deleted 509
new 51 running as root 329
updated 57 setting up 325
compatibility settings changes for migration 479
DB2 products 35 settings changes for upgrade
earlier versions 46 general upgrade procedures 282
deleted commands 65 upgrade scenario 1 96
deleted options 65 upgrade scenario 2 139
deleted utilities 65 upgrade scenario 3 182
files upgrade scenario 4 229
location 9 Solaris service 324
naming 9 starting 331
installing automatic 329, 330
migrating V5 servers from AIX, HP-UX, or Solaris 386, changes in V7.1 8
393, 406, 413 from instance owner user ID 328
migration from z/OS 474 from root user ID 329
upgrade scenario 1 111 on AIX, HP-UX, Linux, Solaris 325
upgrade scenario 2 155 on Windows 9, 331
upgrade scenario 3 194, 205 using Windows services 332
upgrade scenario 4 241, 252 starting after migration from AIX, HP-UX, or Solaris 426
installing V7 starting after upgrade 325
migration from z/OS 474 starting instance 325
installing V7.1 stopping 488
general upgrade procedures 297 migrating V5 servers from AIX, HP-UX, or Solaris 379

572 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
server (continued) sessions (continued)
stopping before upgrade disabling before upgrade (continued)
general upgrade procedures 286 upgrade scenario 3 183
upgrade scenario 1 100 upgrade scenario 4 230
upgrade scenario 2 143 SET DBRECOVERY command 335, 428, 504
upgrade scenario 3 186 shared libraries, upgrading 47
upgrade scenario 4 233 software requirements
updated commands 57 migrating V5 servers from AIX, HP-UX, or Solaris 366
updated options 57 overview 19
updated utilities 57 V5 server 17
upgrade planning 11 V7.1 server
utilities AIX 21
changes in V7 51 HP-UX 24
deleted 65 Linux 26
new 51 Linux on System z 29
updated 57 Linux x86_64 26
Windows service 318 Microsoft Windows 33
upgrade scenario 1 128 Oracle Solaris 31
upgrade scenario 2 170 z/OS migration 455
upgrade scenario 3 218 software support
upgrade scenario 4 265 describing problem for IBM Software Support 519
server data determining business impact for IBM Software
protection Support 519
migrating V5 servers from AIX, HP-UX, or Solaris 364 submitting a problem 520
server database Software Support
See also database contacting 518
reorganization options 324, 499 Solaris services
server instance creating for server instances 324
creation space requirements
migrating V5 servers from AIX, HP-UX, or Solaris 400, active log 39
418 active log mirror 39
directories archive failover log 39
migrating V5 servers from AIX, HP-UX, or Solaris 389 archive log 39
server instance creation database 38
upgrade scenario 3 212 migrating V5 servers from AIX, HP-UX, or Solaris 373
upgrade scenario 4 259 planning worksheet 42
server instances recovery log 38, 39
owner 7 upgrade process
starting 8, 9 estimating 39
server options planning 37
deleted 65 V5 server
migrated from z/OS 469 media method 37
new 51 network method 37
updated 57 V7.1 server 17, 38
server utilities z/OS migration 473
deleted 65 specify device class of volumes for deletion
new 51 DELETE VOLHISTORY command 524
updated 57 SQL
services on Solaris systems changes to syntax in V7.1 68
creating for server instances 324 queries in V7.1 3
services on Windows systems SELECT command 68
creating for server instances 318 starting servers
upgrade scenario 1 128 after upgrade 325
upgrade scenario 2 170 automatically 329
upgrade scenario 3 218 autostart 8
upgrade scenario 4 265 changes in V7.1 8
database manager 9 multiple instances 8, 9
database manager (DB2TSM1) 555 Windows servers
DB2 555 services 331
server 555 Windows services 9
startup of server 9 starting servers automatically 330
sessions stopping server
disabling See server, stopping
before migration from AIX, HP-UX, or Solaris 374 stopping the server
disabling before upgrade 284, 482 migrating servers from z/OS 488
upgrade scenario 1 97 storage agents
upgrade scenario 2 141 migration from z/OS 451

Index 573
storage agents (continued) upgrade utilities (continued)
planning changes DSMUPGRD overview 16
migration from z/OS 462 environment variables, setting
upgrading 45, 47 general upgrade procedures 292
upgrading configuration 505 upgrade scenario 1 106
storage pool volumes upgrade scenario 2 149
recreating 502 upgrade scenario 3 192
storage pools upgrade scenario 4 239
backups before upgrade installing
general upgrade procedures 284 before migration from AIX, HP-UX, or Solaris 380
upgrade scenario 1 98 installing on AIX
upgrade scenario 2 141 before migration from AIX, HP-UX, or Solaris 380
upgrade scenario 3 184 general upgrade procedures 287
upgrade scenario 4 231 upgrade scenario 1 101
defining for z/OS migration 502 upgrade scenario 2 144
recreating upgrade scenario 3 187
z/OS migration 502 upgrade scenario 4 234
restoring as part of the z/OS migration 502 installing on HP-UX
verifying access 323 before migration from AIX, HP-UX, or Solaris 381
storage requirements general upgrade procedures 289
migrating V5 servers from AIX, HP-UX, or Solaris 369 upgrade scenario 1 102
migration from z/OS 458 upgrade scenario 2 146
support contract 519 upgrade scenario 3 188
support information 515 upgrade scenario 4 236
support subscription 519 installing on Linux
general upgrade procedures 290
upgrade scenario 1 103
T upgrade scenario 2 147
upgrade scenario 3 189
table reorganization
upgrade scenario 4 237
after migrating servers from AIX, HP-UX, or Solaris 425
installing on Oracle Solaris
tape devices
before migration from AIX, HP-UX, or Solaris 382
moving data after migration 431
general upgrade procedures 291
tcpserveraddress option
upgrade scenario 1 105
updating
upgrade scenario 2 148
after migration from AIX, HP-UX, or Solaris 430
upgrade scenario 3 191
testing
upgrade scenario 4 238
before upgrade 47
installing on Windows
threads 554
general upgrade procedures 293
Tivoli Storage Manager for z/OS Media
upgrade scenario 1 107
See z/OS media server
upgrade scenario 2 150
Tivoli Storage Manager server database
upgrade scenario 3 193
See database
upgrade scenario 4 240
translation features 547
logs, location 9
translations 547
moving data, methods 15
troubleshooting
overview 16, 521
common problems 343
usage for upgrade
migrating V5 servers from AIX, HP-UX, or Solaris 435
general upgrade procedures 307
migration from z/OS 509
upgrade scenario 1 120
upgrade scenario 2 164
upgrade scenario 3 202
U upgrade scenario 4 250
ulimits V5 database
setting BACKUP STGPOOL 485
before server startup 326 DSMUPGRD EXTEND DB 533
upgrade commands DSMUPGRD EXTRACTDB 529
overview 521 DSMUPGRD PREPAREDB 523
upgrade methods DSMUPGRD QUERYDB 522
overview 73 ZMSPREPARE 482
procedures V5 server
new system, media method 177 DSMUPGRD EXTEND LOG 534
new system, network method 225 DSMUPGRD QUERYDB 522
same system, media method 91 upgrade wizard
same system, network method 135 description 305
upgrade utilities logs 9
creating a test server 47 migrating V5 servers from AIX, HP-UX, or Solaris 390,
DSMSERV_DIR 9 411

574 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers
upgrade wizard (continued)
upgrade scenario 1 118
W
upgrade scenario 2 162 Windows clustered environment
upgrade scenario 3 194, 201 upgrade from V5.5 to 7.1 274
upgrade scenario 4 241, 248 upgrade from V5.5 to V7.1 273
upgrading multiple servers 46 Windows services
upgrading creating for server instances 318
comparison of methods 13 upgrade scenario 1 128
existing system, V5 server upgrade scenario 2 170
comparison with new system upgrade 13 upgrade scenario 3 218
new system, V7.1 server upgrade scenario 4 265
comparison with existing system upgrade 13 starting server 332
procedures Tivoli Storage Manager server 555
general purpose 277 wizards
new system, media method 177 See upgrade wizard description
new system, network method 225 worksheet
same system, media method 91 server space planning 42
same system, network method 135
process 12
server Z
overview 1 z/OS media server 439, 447
using command interface configuration 481
general upgrade procedures 307 data migration 482
upgrade scenario 1 120 defining 481
upgrade scenario 2 164 deleting backup sets 486
upgrade scenario 3 202 device migration 448
upgrade scenario 4 250 functionality 437
upgrading to V7 installation 481
reverting to V5 351 messages 453
upgrading to V7.1 server migrating data to other devices 507
general upgrade procedures 277 product overview 443
scenario procedures verifying migration prerequisites 486
new system, media method 177 ZMSPREPARE command
new system, network method 225 verify migration prerequisites 486
same system, media method 91 ZMSPREPARE command
same system, network method 135 preparing server on z/OS for migration 541
US English 551
user limits
setting
before server startup 326
utilities
See also upgrade utilities
changes in V7 51
deleted 65
DSMSERV LOADFORMAT 536
DSMUPGRD UPDATE 535
migrating V5 servers from AIX, HP-UX, or Solaris 363
new 51
updated 57

V
VARY command
troubleshooting 351
verifying upgrade
server operations 336
volume history information
backups before upgrade
general upgrade procedures 285
upgrade scenario 1 99
upgrade scenario 2 142
upgrade scenario 3 185
upgrade scenario 4 232
backups before z/OS migration 474
requirement for database recovery 5
volumes
deleting as part of the z/OS migration 503

Index 575
576 IBM Tivoli Storage Manager: Upgrade and Migration Guide for V5 Servers

Product Number: 5608-E01

5608-E02
5608-E03

Printed in USA