We are having discussions about upgrading to TSM v5.4. The question of
compatibility of server-to-server communications came up, and whether
we have to upgrade all tsm instances at the same time or can we
roll through them upgrading one at a time. In researching
this, I became confused (common state!).
Environment: TSM on AIX. We use server-to-server communications for
1) Library sharing (3494 and 3584) - library manager with library
clients.
2) Virtual Volumes - Some offsite copy pools and offsite db backups.
In the v5.4 Install Guide, I found the following comments . . . .
(ch 1, page 13 -> Compatibility with other versions of TSM)
When upgrading multiple servers participating in
library sharing to Version 5.3 and later, the servers
acting as library manager must be upgraded first to
maintain compatibility among the servers acting as
library clients or storage agents. When upgrading
multiple servers participating in server-to-server
to Version 5.3 or later, all servers must be upgraded
at the same time.
As a general rule, the Tivoli Storage Manager
server will normally support storage agents and
library clients at the same
version, release, and modification level down
to the modification level minus two.
This is confusing. It seems to say that you can have mixed levels as
long as the library manager is at the highest level, but also says that
servers "participating" in server-to-server must ALL be upgraded at
the same time.
q) Which is it . . . must all servers be upgraded together, or, can
the library manager instance be upgraded first, then the others
upgraded later.
Thanks
rick
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
|