Re: Hot Swap iSeries applications

wrote:

Help me explain, to a non-iSeries person, the limitations of HOT SWAPPING
on the iSeries.

I understand how system clustering and iASP works. That's what we are
doing now using PowerHA SystemMirror for i.

The main limitation in this environment though is that the DB is not
shared between 2 systems at the same time. iASP technology requires time
to reboot the DB on the other server and then telnet users lose their
sessions and have to sign on to the backup server to work again. This isn't
a HOT SWAP. Maybe you could call it a WARM SWAP.

Our System Architect keeps hammering me on this. He can't understand why
the IBM iSeries platform can't provide a HOT SWAP environment. He isn't
taking, "That is just how it works" as an answer either.

What does it take to have a cluster of 2 systems sharing a database
allowing a HOT SWAP to another server when the primary server fails?

I know it isn't iASP.

Can this be done using an object oriented MIMIX type DB replication
product and clustering?

Also, can there ever really be an environment on the iSeries platform that
can HOT SWAP telnet connected clients? Maybe using some kind of virtual
telnet addressing scheme on a frontend server.

Any help in explaining this will be greatly appreciated! If you can bail
me out, I'll even buy you a drink at the next Common Conference! <smile>

Kenneth
Kenneth E. Graap
NW Natural
System Administrator for IBM Power Systems
503.226.4211 x5537
http://www.linkedin.com/in/kennethgraap



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.