IC53431: TSM 5.3 AND 5.4 SERVER INSTALLATION GUIDE INSTRUCTIONSARE INADEQUATE REGARDING MULTI SERVER INSTANCES FOR MIGRATE INSTALL.

APAR status

• Closed as documentation error.

Error description

• Problem Description:
  The TSM 5.4 IUG - Installation and Users Guide States for a
  migration install  (primarily intended for a single server
  instance):
  Migrating to Tivoli Storage Manager Version 5.4
     Before You Perform a Migrate Installation
         You can install Tivoli Storage Manager Version 5.4 over a
  previous version of Tivoli Storage Manager. This is called a
  migrate installation.
  .
  This section describes some things to consider before you
  perform a migrate installation.
          * The dsmserv.dsk file points to the locations of the
  current database and recovery log volumes. A migrate
  installation will not normally create a         new database,
  recovery log, and storage pool volumes. However, if dsmserv.dsk
  is not in the /usr/lpp/adsmserv/bin or
  /usr/tivoli/tsm/server/bin directory, the installation creates
  the following volumes in the /usr/tivoli/tsm/server/bin
  directory:
               - Database volume (db.dsm)
               - Recovery log volume (log.dsm)
               - Storage pool volumes (backup.dsm, archive.dsm,
  and spcmgmt.dsm)
  .
  To use your existing database, recovery log, and storage pool
  volumes, ensure that a copy of the dsmserv.dsk file is in
  /usr/tivoli/tsm/server/bin and the file system is mounted before
  you do a migrate installation. You must not move the database,
  recovery log, and storage pool volumes.
  .
  The above paragraph can be confusing as it alludes for multiple
  server instances that the dsmserv.dsk for each instance needs to
  be copied to the default install directory which would require
  multiple installs of the server software.
  ---
  In the TSM 5.4 IUG this is followed, a page later, by the note
  below, and in the TSM 5.3 IUG the above is preceeded, by a page,
  by the note below:
  .
  Note:.
  If you are running several instances of the server with a
  separate log and database, the upgrade database that is
  performed during the installation will have no effect. Enter the
  UPGRADEDB command for each database.
  .
  The Note should be changed to reflect a DSMSERV UPGRADEDB should
  be performed for any server instance whether single or multiple
  if the instance does not reside in the default installation
  path.  A suggested paragraph may be like the following:
  .
  Note: If you are running several instances of the server with a
  separate log and database, the upgrade database that is
  performed during the migration installation will have no effect
  on any instance not in the default installation path. Enter the
  DSMSERV command using the UPGRADEDB parameter for each server
  database not in the default installation path.
  .
  The Note should also either be placed in close proximity to the
  migrate install instructions are at least reference the page for
  the note regarding a migrate install for multiple server
  instances.
  .
  Customer/L2 Diagnostics (if applicable)
  None
  .
  *NOTE*
  Prior to TSM 5.3 the TSM Administration Reference Manual
  included the UPGRADEDB and it's syntax as a command. Beginning
  with TSM 5.3 the UPGRADEDB is shown as a parameter to the
  DSMSERV command.
  .
  Platforms affected:
  All TSM 5.3, 5.4.
   .
  Initial Impact: Low
  .
  Additional Keywords: multiple server instances migrate install
  upgradedb dsmserv
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: TSM AIX server administrators                *
  ****************************************************************
  * PROBLEM DESCRIPTION: The IBM Tivoli Storage Manager for      *
  *                      AIX Installation Guide, Installing IBM  *
  *                      Tivoli Storage Manager, Upgrading to    *
  *                      IBM Tivoli Storage Manager Version      *
  *                      5.4, is confusing because it is not     *
  *                      clear about upgrade information for     *
  *                      multiple server instances.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Need to clarify the upgrade information for
  multiple server instances.
  

Problem conclusion

• The following information will be updated in a techdoc, and
  also in the the IBM Tivoli Storage Manager for AIX
  Installation Guide.
  
  Chapter 1. Installing IBM Tivoli Storage Manager
  Upgrading to IBM Tivoli Storage Manager
  
  Before you perform an upgrade
  .
  .
  .
  A DSMSERV UPGRADEDB operation is automatically performed
  during an upgrade. If you are running several instances of the
  server with a separate log and database, the upgrade database
  that is performed during the installation will have no effect
  on any instance not in the default installation path. Enter
  the DSMSERV command using the UPGRADEDB parameter for each
  server database not in the installation path.
  
  ----------------------------------
  Performing an upgrade
  .
  .
  An upgrade will not normally create a new database,
  recovery log, and storage pool volumes. The dsmserv.dsk file
  points to the locations of the current database and recovery
  log volumes. However, if dsmserv.dsk is not in the
  /usr/lpp/adsmserv/bin or /usr/tivoli/tsm/server/bin
  directory, the installation creates the following
  volumes in the /usr/tivoli/tsm/server/bin directory:
  - Database volume (db.dsm)
  - Recovery log volume (log.dsm)
  - Storage pool volumes (backup.dsm, archive.dsm, and
  spcmgmt.dsm)
  
  To use your existing database, recovery log, and storage pool
  volumes, ensure that a copy of the dsmserv.dsk file is in
  /usr/tivoli/tsm/server/bin and the file system is mounted
  before you do an upgrade. If you are running several
  instances of the server, ensure that the dsmserv.dsk file
  is in the installation directory of each server instance and
  the file system is mounted before you do an upgrade. You must
  not move the database, recovery log, and storage pool
  volumes.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels