|
Can you now?
How would you do this:
LPARA on POWERX
LPARB on POWERY
Production normally runs on LPARA. LPARA and LPARB are both at 6.1. With
Mimix I can upgrade LPARB to 7.1. Then when I am ready I can switch from
LPARA to LPARB and upgrade LPARA to 7.1. When done, switch back to LPARA.
If I have geographic mirroring I am under the impression that the disk
images on SAN are identical. So, how do I upgrade from 6.1 to 7.1 while
production keeps rolling?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 05/22/2012 09:22 AM
Subject: Re: SAN Vendor support for IBM i?
Sent by: midrange-l-bounces@xxxxxxxxxxxx
If you get the right type of setups then you could do away with the
software replication and go with a geo-mirroring solution. An alternative
approach might be to utilize a san as your VTL, then have that san
replicated somewhere else.
On Tue, May 22, 2012 at 9:13 AM, <rob@xxxxxxxxx> wrote:
Sort of like when we buy one Power box we buy another to run Mimix on?SAN.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Richard Schoen <richard@xxxxxxxxxxxxxxx>
To: "midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>,
Date: 05/22/2012 08:41 AM
Subject: Re: SAN Vendor support for IBM i?
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Sure I would, but not if the disk cost is 2.5x a NetApp or equivalent
mix
Most of our customers are implementing a SAN or NAS where they want to
IBM i documents and Windows data, so that's the scenario I am used to<richard@xxxxxxxxxxxxxxx>
seeing.
However Matt didn't give us any true dollar comparisons, so the dollars
could still be considered reasonable for the IBM DS*** line of SANs. I
don't know.
We tried to configure a Blade Server a couple years ago and the IBM
hardware guys had a time trying to configure it correctly, so I haven't
had very good success with non-traditional IBM i setups :-)
There's also the hardware redundancy aspect.
If you buy one SAN it usually means two SANs for redundancy.
Cha-ching $$$$$$$
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 2
date: Tue, 22 May 2012 10:33:35 +1200
from: Evan Harris <auctionitis@xxxxxxxxx>
subject: Re: SAN Vendor support for IBM i?
Hi Richard
What is especially important or significant about IFS documents ?
Are you saying you would not consider putting the system i database on a
SAN ?
If so, why not ?
On Tue, May 22, 2012 at 10:17 AM, Richard Schoen
wrote:list
Out of curiousity why do you need a SAN for your i if not storing IFSstyle documents ?
What is it you're trying to accomplish ? IASP or something else ?
Maybe I missed it in the previous posts.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
--
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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.