MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2012

Re: SystemMirror Was: Be sure to permanently apply all Licensed Internal Code PTFs beforeSAVSYS...



fixed

In your scenario you have a boat load of journal receivers and journals to
resync and to worry about as well.

On Wed, Oct 24, 2012 at 3:37 PM, Jack Kingsley <iseriesflorida@xxxxxxxxx>wrote:

If you running HA cluster you would break it, update your prod lpar to new
os or do your ptf work, when done re-establish it, once is syncs then
prodback looks like prod. This is assuming your not running slave lpars(i
on i), this would still be what they are prior.


On Wed, Oct 24, 2012 at 3:30 PM, <rob@xxxxxxxxx> wrote:

You believe, or know?

I've talked to guys who run Windows on servers stored on NetApp clusters.
If they upgrade SERVERA from Win2000 to Win7 it's down. Period. There's
no running SERVERA on this cluster while you upgrade SERVERA's OS
partition on the other cluster.

With Mimix, I would normally upgrade PRODBACK to 7.1 while PROD was still
running 6.1. Then switch from PROD to PRODBACK and upgrade PROD. When
that's done, switch back to PROD. Why that order? Save/restore previous
release concerns. Granted, I had already upgraded SANDBOX to 7.1 and
tested the applications on that first.


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: 10/24/2012 03:22 PM
Subject: Re: SystemMirror Was: Be sure to permanently apply all
Licensed Internal Code PTFs beforeSAVSYS...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Believe the best it would give you is, you break the cluster, do your ptf
work on prod, ipl prod, when your done now prod and prodback are the
same(once the resync is completed).

On Wed, Oct 24, 2012 at 3:16 PM, <rob@xxxxxxxxx> wrote:

PROD, DEV, PRODBACK, DEVBACK (not their real names) are all dedicated
lpars. No host/guest for those.
Some Domino lpars are guested.
However, whether or not they are hosted or not is irrelevant. Sure, if
PROD was guested under HOST and HOST was taken down then I had better
have
completed a Mimix switch from PROD to PRODBACK first (or my backup plan
is
my resume'). While I am running on PRODBACK I could upgrade PROD or
HOST
or both.

I believe SystemMirror is san with clustering available. However, you
can't upgrade the OS copy on one cluster and not on the other, right?
For
example, I have a lpar called PROD. In a SystemMirror solution it's
stored on the SAN. I can access that lpar from either BOX1 or BOX2.
What
I can't do is run on BOX1 on one copy of the cluster while BOX2 upgrades
i
or puts a cume on i on another copy on a cluster. Something I do with
Mimix once a quarter.

Don't get me wrong, there are some nice things about SystemMirror.
Flashcopy, and the unique hardware concerns I mentioned previously. But
if a bulk of my planned outages are PTF's and OS upgrades and it doesn't
address that, then it's not a solution to my problem.


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: 10/24/2012 02:52 PM
Subject: Re: SystemMirror Was: Be sure to permanently apply all
Licensed Internal Code PTFs beforeSAVSYS...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Rob, these dedicated lpars and or I on I as well. The system mirror is
san
with clustering, right.

On Wed, Oct 24, 2012 at 2:25 PM, <rob@xxxxxxxxx> wrote:

I looked at SystemMirror multiple times. I even discussed it with
IBMers
at the last COMMON.

It has no benefit for me.

This is how I picture SystemMirror working:
- You have BOX1 at location a
- You have BOX2 at location b
- Neither has any physical disk.
- They both use SAN storage.
- This SAN may, or may not, be replicated to another SAN. Depending
on
the size of your checkbook.
This may be an acceptable solution if your concerns include:
- Physical damage to BOX1 or BOX2.
- A hardware move of BOX1 or BOX2 to another location.
- A hardware upgrade of BOX1 or BOX2

What it didn't address is what about OS upgrades, ptf installation and
that ilk? The fact that you have redundant boxes but they both rely
upon
the same disk makes both boxes out of commission when you are
upgrading
the OS on that disk.

A bulk of my planned outages are to install PTF's. Since I had to
have
an
alternative solution to achieve this with minimal outages of my system
I
will use my alternative solution for everything.


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: "Graap, Kenneth" <Kenneth.Graap@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>,
Date: 10/24/2012 01:14 PM
Subject: RE: Be sure to permanently apply all Licensed Internal
Code PTFs beforeSAVSYS...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



That's sounds like a very good procedure!

I'm in the process of setting up an HA solution using SystemMirror for
IBMi... I'm looking forward to being able to offload backups to the
mirrored system.

Reply or Forwarded mail from: Kenneth E Graap


--
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.


--
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.


--
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.








Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact