Re: Converting TSM Platforms
2001-01-30 19:58:25
Hi. I'd try....to 1, upgrade on your existing machine....TSM to the
higher level...
on the new node have TSM installed (at the higher level)....
disable sessions (on the day of the move)
on the day of the move...move all your disk data to tape (should be
a daily process....)
backup the db on the old node...
do the physical move of disk...tape drives...
(try to keep your node the same, due to 3494
customization...(there's a node/host entry coupled with an ip address on the
3494
(who just doesn't allow just anyone to connect...))
restore the db on the new node...
I'd make sure that the AIX customization or DNS entries that you use
for backups are
the same across the move..
my thoughts..
Thanks Tim
Brecton Whitten <bwhitten AT UABMC DOT EDU>
01/30/2001 06:35 PM
Please respond to "ADSM: Dist Stor Manager"
<ADSM-L AT VM.MARIST DOT EDU>@SMTP@Exchange
To: ADSM-L AT VM.MARIST DOT EDU@SMTP@Exchange
cc:
Subject: Converting TSM Platforms
*SM admins,
We are currently planning to move our TSM
server from a 604e high node in an SP2 complex
to an H50 standalone. Both platforms have the same
number of CPU's and amount of memory ( 2 G ). The
big difference being MCA vs. PCI. We are on TSM 3.7.4
and are going to move up to TSM 4.1.2 ( AIX 4.3.3 ).
From combing the postings it appears that our best ( only ? )
choice for this migration is to export each node to tape then
import on the new platform. The problem we will have with
this is that we only have 2 3590 drives native attached in a
3494. We will have to export everything , disconnect the drives,
re-connect to the new platform, and then import. Our data is all
on tapes, we don't have enough DASD to keep more than 1
days data on disk ( therefore we also don't have enough to export
to FILE ). If anyone has any input or 'gotchas' , I would much
appreciate hearing from you.
Thanks,
Brec
Whitten
UAB
Hospital
|
|
|