Re: x using i as storage -- MIDRANGE-L

Subject: Re: x using i as storage
From: "Lukas Beeler" <lukas.beeler@xxxxxxxxxxxxxxxx>
Date: Wed, 6 Aug 2008 23:52:13 +0200
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Wed, Aug 6, 2008 at 11:27 PM, Pete Massiello
<pmassiello-ml@xxxxxxxxxxxx> wrote:

It was an HS21 (Intel Blade) in a BCH, with iSCSI connected to a
Power5+ 520 with the disks in the drawers of an EXP24.

Everytime i see talk about using the standalone machines as a SAN, the
following questions comes to my head:

"Why, God, why?"

I've seen my fair share of technical documentation about this topic,
and i've also seen all the marketing blurb, but i've never seen
something that i would consider an advantage over using a real SAN.

Plus most backup solutions promoted by IBM for this scenario would
break ESE databases and cause USN rollbacks in DCs.

Are there people running this in production? And if yes - why did you
decide to do so?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: x using i as storage , Pat Barber
RE: x using i as storage , Wilt, Charles

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.