Caution....going into "2 year old" mode....

Why?
Why?
Why?

Ok, enough of that...

In what cases is this a problem?  I want to know, in what circumstances
I'm going down a path, that is different than I think.

For example, right now, our zLinux disaster recovery option is to find
a replacement processor (perhaps the next processor off of IBM's line),
and some disk (which may or may not be a DS6800, like we currently
have), restore and go.  Notice, no hot site, no testing.  We expect some
problems and we hope to solve them in a fairly quick fashion.
Managments target recovery time, 2 weeks.  (we are not there, yet)

But if me choosing method/path A over method/path B and with that
method/path, I'm going to have hundreds of hours of "fix it" stuff
related to minidisks....  That is something I need to know, perhaps
avoid, or worse case, document and schedule for.

Obviously, it isn't an absolute problem.  We went from MP3000 internal
dasd to DS6800 without any problems.  We went from IBM Ramac Dasd
Subsystem to DS6800 without any problem.

What options can be selected, or features used, that would expose
ourselfs to having zLinux knowing too much about the dasd subsystem?

Tom Duerbusch
THD Consulting

>>> [EMAIL PROTECTED] 2/20/2007 12:03 PM >>>
On Tuesday, 02/20/2007 at 10:01 CST, Stephen Frazier
<[EMAIL PROTECTED]> wrote:
> The point he was trying to make is that a lot of people think that it
is
true.
>
> [EMAIL PROTECTED] wrote:
> >> Life with Linux ended up less ideal, for various reasons (mostly
> >> political, imho). We now find that z/VM reveals way to much
details
> >> about the real system to the guest, and Linux code deals with
those
> >> details as if it were running on bare metal. And everyone thinks
that
> >> it is normal that you would need to upgrade all your Linux
virtual
> >> machines just because you moved their mini disks from one DASD
> >> subsystem to the other.
> >
> > The above is not true.  I migrated Suse 7, Suse8 and Suse 9 images
that
> > were on minidisks residing on a combination of MP3000 Internal
Dasd
and
> > Ramac Dasd Subsystem to DS6800.  3390 minidisks to 3390 minidisks.
> > Linux didn't know or cared a thing about it.

The truth, as always, is somewhere between "true" and "false".  I.e.,
"it
depends".  While z/VM can establish a virtual "box" that has the same
dimensions without regard to the underlying hardware, the color and
texture of the inside of the box will tend to follow that of the real
hardware.  Under certain lighting conditions the differences are very
apparent.  Under others, not so much.

It really depends on whether the guest needs a particular shade of
blue.
(Just trying to avoid the obligatory car or sports analogy.)

Alan Altmark
z/VM Development
IBM Endicott

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to