ADSM-L

Re: Recommendations for hardware replacement/upgrade

2007-01-10 12:09:38
Subject: Re: Recommendations for hardware replacement/upgrade
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 10 Jan 2007 12:08:22 -0500
Thanks for the feedback.

Yes, I realize you can't beat AIX for I/O bandwidth.  Unfortunately, it
comes down to $$$$$$   (doesn't it, always).

I agree it would be beneficial to break things up. However, this would
lead to even more contention for resources (tape, tape libraries) than we
already have.  We have enough issues juggling 4-TSM servers against 3-tape
libraries (1-3494    2-3583).

I hadn't really thought about running multiple TSM server instances on one
machine.  Not sure if it is worth the effort/risk!

As for databases, it sure would be nice if IBM would hurry up and release
V6 with the new and improved DB (my
statements/thoughts/assumptions...........not IBM's), since as you
suggest, finding the time window to perform auditdb's, is almost
impossible. I just did one to repair some problems. It ran 80-hours.




Roger Deschner <rogerd AT UIC DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/10/2007 10:07 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Recommendations for hardware replacement/upgrade






I/O bandwidth is the key. Since these new systems cannot match the I/O
bandwidth of the AIX pSeries systems they are replacing, count on having
to run MORE SERVERS to accomplish the same work.

Having said that, there's a silver lining. Most TSM systems could
benefit from subdivision. The database becomes more manageable.
Expiration Angst is reduced. You can run the Log in ROLLFORWARD mode
again. AUDIT DB once again becomes feasible. Opportunities open up for
having TSM servers back each other up. Now is a good time to do this,
ESPECIALLY if you are going to make the move with EXPORT TO SERVER.

A fallback plan, in case the new servers' performance doesn't measure up
to expectations, would be to initially plan each new server to have two
TSM server images and two databases running on it. Then when everything
bogs down, you can call Dell and bring in more machines, without having
to go through EXPORT all over again.

So, plan now on having more servers and more server images, partially to
compensate for the new systems' poorer I/O bandwidth, and take it as an
opportunity to do something that you probably should have considered for
a while. If the new systems simply don't work and you convince them to
go back to AIX pSeries, you'll still be ahead having divided your server
images.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu


On Tue, 9 Jan 2007, Bob Booth wrote:

>On Tue, Jan 09, 2007 at 09:59:20AM -0500, Zoltan Forray/AC/VCU wrote:
>> Windows is not in the picture. These are going to be RH Linux systems.
>>
>> We will probably perform EXPORT TO SERVER to move the clients, one by
one,
>> since we are probably going to move to new media types (3592 vs 3590) ,
as
>> well.
>
>Look for the type of system that will give you the most PCI-X bandwidth
you
>can get.  You are going to be pumping quite a bit of data across that
bus,
>with presumably 4Gb HBA's, some SCSI (?), networking...  TSM is all about
>I/O, to disk, tape, and the network.
>
>hth,
>
>bob
>