Table of Contents
Advertisement
you do not need to uninstall the previous server before applying new one, since
this is done automatically by the migration procedure.
When you upgrade multiple servers participating in library sharing to V5.3, the
servers acting as library manager must be upgraded first to maintain
compatibility among the servers acting as library clients or Storage Agents.
When you upgrade multiple servers participating in server-to-server
communication to V5.3, all servers must be upgraded at the same time.
Migration procedure
As a general rule, follow the recommendations in 22.1, "General upgrade
considerations" on page 692, that is, quiesce the server instance and then back
up the database and supporting files.
Apart from that, you should consider cleaning up the database by running the
expire inventory command. Also, If your server is currently at a release earlier
than V5.2, there might be additional steps you should take in preparation for
upgrading to V5.3, such as expiration of system object file spaces. If you do not
back up Windows clients or do not back up
you are not affected by this problem. For details about these steps see the
following IBM Web site:
http://www.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=1078582&uid=swg
21078582&loc=en_US&cs=utf-8&lang=en
Note: When migrating to Tivoli Storage Manager V5.3, the time necessary to
install the packages can be considerable, depending on the number of
Windows clients registered. The more Windows clients registered, the longer
it will take to install the package.
Once you have finished the preparation phase, you may start the migration
running the Tivoli Storage Manager setup wizard. Keep in mind that the base
level (that is, 5.3.2) must be installed first, and then you may apply the patch
(5.3.2.2).
702
IBM Tivoli Storage Manager Implementation Guide
system objects
on the Windows client,
Advertisement
Table of Contents
