Tivoli Header
Quick Start
You can install Tivoli Storage Manager Version 5.1 over a previous
version of ADSM or Tivoli Storage Manager. This is called a
"migrate install". A DSMSERV UPGRADEDB operation is
automatically performed during a migrate install.
The ADSM default installation directories changed for Tivoli Storage
Manager. If you have previously used Disaster Recovery Manager (DRM) to
create a disaster recovery plan file, that file refers to path names that may
no longer be valid. After you have installed Tivoli Storage Manager,
you should back up your storage pools and database and create a new disaster
recovery plan file. For the sequence and details of the procedure, see
the Tivoli Disaster Recovery Manager chapter in the Administrator's
Guide.

| To return to ADSM or an earlier version of Tivoli Storage Manager, after
a migrate install, you must have a full database backup of that original
version and the install code for the server of that original version.
- You cannot restore a prior version's backed up database onto the
latest version of the server. For instance, you cannot restore a
Version 4.2 database onto Tivoli Storage Manager Version
5.1. For instructions on how to rollback to a prior version of
the server see Appendix F, Removing the Tivoli Storage Manager Server.
Be aware of the results of returning to an earlier version of the
server:
- References to client files that were backed up, archived, or migrated to
the Tivoli Storage Manager Version 5.1 server will be lost.
- Some existing volumes may be overwritten or deleted during the Tivoli
Storage Manager Version 5.1 operation. If so, client files that
were on those volumes and that were migrated, reclaimed, moved (MOVE DATA
command), or deleted (DELETE VOLUME command) may no longer be accessible to
the earlier version of the server.
- Definitions, updates, and deletions of objects performed on the Version
5.1 server will be lost.
|
Device driver conflicts occur if you have Tivoli Storage Manager version
4.2 installed on AIX version 4.3.3 and wish to migrate to
AIX version 5.1. To resolve this, the Tivoli Storage Manager
device support for AIX version 5.1
(tivoli.tsm.devices.aix5.rte) must be
installed. To do this, follow these steps.
- Before migrating, record all Tivoli Storage Manager device
definitions.
- Uninstall the fileset
tivoli.tsm.devices.aix43.rte by using
the command:
+--------------------------------------------------------------------------------+
|installp -ug tivoli.tsm.devices.aix43.rte |
+--------------------------------------------------------------------------------+
This will also cause
tivoli.tsm.msg.[lang].devices to be
uninstalled, where [lang] is en_US and any other
"tivoli.devices" messages fileset that may be installed.
- Migrate to AIX version 5.1
- Install the filesets
tivoli.tsm.devices.5.rte and
tivoli.tsm.msg[lang].devices
- Redefine the devices.
This section describes some things you should consider before you perform a
migrate install.
- The dsmserv.dsk file points to the locations of the current
database and recovery log volumes. A migrate install 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 install 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 install. You must not move the database, recovery log,
and storage pool volumes.
- If you decide to return to the previous version of the server, you must
have a backup copy of your prior database, volume history, and device
configuration files. In the following example, the tape device class
named TAPECLASS is used for database backups.

+--------------------------------------------------------------------------------+
|backup db type=full devclass=tapeclass |
|backup devconfig filenames=devconfig.jan99 |
|backup volhistory filenames=volhistory.jan99 |
+--------------------------------------------------------------------------------+
- Note:
- This command retrieves database records into a database dump. This
process does not access the recovery log. Transactions held in the log
database are lost.
Store the output volumes and the device configuration and volume history
files in a safe location.
- During the migrate install, the following files are automatically copied
to the location of the new Tivoli Storage Manager installation:
- The dsmserv.dsk file
- The accounting log file (dsmaccnt.log)
If the environment variable DSMSERV_ACCOUNTING_DIR was set, you must reset
it. See Defining Environment Variables for details.
- The server options file dsmserv.opt
- Existing device configuration and volume history files if they are named
devconfig and volhist

| If these files are not named devconfig and volhist,
you should back up the files and save them in a temporary directory.
You can later edit the new server options file to include the names of these
files.
|
If the files are automatically copied, the server options file is
automatically updated.
You should also save in a temporary directory any existing runfile
scripts.
- Tivoli Storage Manager device definitions are not saved during a migrate
install. To install the new Tivoli Storage Manager drivers, you must
have the output from the following commands:
lsdev -Cc tape
lsdev -Cc library
This is not required for the IBM 3494, 3495, 3570, 3575, or 3590, which
use drivers supplied with the devices.

| During a migrate install, Fiber Channel Protocol definitions will be
lost. Save existing FCP definitions before a migrate install or else
they will have to be reinstalled.
|
- Stop the server if it is running by entering:

+--------------------------------------------------------------------------------+
|halt |
+--------------------------------------------------------------------------------+
If you started the server as a background process, connect to the server as
an administrative client and issue the HALT command. If you cannot
connect to the server with an administrative client, you must use the
kill command with the process ID number (pid) that is displayed at
initialization.
- Note:
- Before you issue the kill command, ensure that you know the
correct process ID for the server.
- If you have created scripts that have paths to
/usr/lpp/adsmserv/bin, change the paths to
/usr/tivoli/tsm/server/bin.
- Install the latest Tivoli Storage Manager server software (see Installing Tivoli Storage Manager).
- Note:
- Until the new version is installed and any required licenses are reregistered
(step 7), clients will not be able to connect to the server.
- Tivoli Storage Manager is shipped with sample command scripts that can be
loaded into the database and run from an administrative client, administrative
Web interface, or server console. They can also be included in
administrative command schedules. The sample scripts, in
scripts.smp, are primarily SELECT queries, but also include
scripts that define volumes for and extend the database and recovery log and
that back up storage pools.
- Note:
- The sample scripts may have been loaded when a previous version of ADSM or
Tivoli Storage Manager was installed. Loading the sample scripts again
at this point will overlay any existing scripts of the same name and any
modifications made to those scripts will be lost.
To load the sample scripts into the database, issue the following
command:
+--------------------------------------------------------------------------------+
|./dsmserv runfile /usr/tivoli/tsm/server/webimages/scripts.smp |
+--------------------------------------------------------------------------------+
- To use the Web administrative interface:
- Your browser must provide Java(TM) 1.1.6 support. See
System Requirements.
- Configure the HTTP communication method in your server options file
(dsmserv.opt).
+--------------------------------------------------------------------------------+
|commmethod http |
| httpport 1580 |
+--------------------------------------------------------------------------------+
- Start the server.

+--------------------------------------------------------------------------------+
|./dsmserv |
+--------------------------------------------------------------------------------+
- Your licenses from the previous version are no longer valid
and must be reregistered. See Registering Licenses.
- Note:
- The tivoli.tsm.license package is required to
register licenses. This package is installed when you install the
server package.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]