Before we perform a major upgrade on our TSM servers, we do a test upgrade.
We do a backup to disk, restore the backup to a test server (at the proper
aix/tsm versions), then perform the upgrade. Care must be taken not to
allow
server-to-server communications (bogus ip addresses in the hosts file),
Of course, when you start the test instance it gets all kinds of errors for
all the missing pools/drives/etc, but it proves the upgrade process and
gives
a good estimated time that theupgrade will take. Plus, it's great
practice!
Rick
Anker Lerret
<ADSM-L AT LERRET DOT US
> To
Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU
Dist Stor cc
Manager"
<[email protected] Subject
.EDU> TSM server 5.3.3.0->5.4.1.1...no
problem?
02/27/2008 03:50
PM
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
We're about to upgrade from TSM server 5.3.3.0 to 5.4.1.1 on 2 TSM
servers. I've read through the upgrade procedure. It looks simple
enough. We're already running 5.4.1.1 on another TSM server with no
problems, so I'm not too concerned about that. I've looked through the
listserv archives and no-one seems to have had major problems with this
upgrade. My problem? I just found out that our TSM guru will be on
vacation, so I'll be on my own. This will be my first TSM upgrade (though
I'm quite familiar with AIX upgrades). Should I worry? Should I
reschedule the upgrade? Have I missed anything?
My motto: What could POSSIBLY go wrong?
anker
Our configuration:
9117-550 with 2 LPARSs, each running an instance of TSM server
AIX 5.3, 5300-07-01-0748
ACSLS 7.1.0
Gresham EDT 8.0.0.0
STK SL8500 library with 14 T10K encrypted drives
700 TSM clients
just over a petabyte of data in the library (total of QUERY AUDITOCC)
-----------------------------------------
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.
|