Rob,
Did you lose a screw there? No need to make yourself clear, because my comments weren't about upgrading, they were about if you want to run PowerHA, I wouldn't run it without being on V7R1.
Now for the upgrade, once you upgrade from one release to another and convert the objects, the older release, most likely wouldn't be able to work with them. With or without PowerHA, if you upgrade a machine and you convert the objects to a new format, the older release would have a problem as it wouldn't know the new format.
--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, May 21, 2013 1:22 PM
To: Midrange Systems Technical Discussion
Subject: RE: Migrate iTERA to PowerHA
How can I make myself clear? Let's say all your machines are running 7.1.
Now you want to upgrade to rNext. Let's say that rNext does some data conversions, similar to the ones we've seen in the past.
Does that help to explain it? But I think Mark Waterbury kind of explained that scenario.
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: Pete Massiello - ML <pmassiello-ml@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 05/21/2013 01:17 PM
Subject: RE: Migrate iTERA to PowerHA
Sent by: midrange-l-bounces@xxxxxxxxxxxx
If you are doing PowerHA, you need to be on V7R1, otherwise I wouldn't
even attempt as you will not have Async replication, and only Sync
replication.
Pete
--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, May 21, 2013 1:09 PM
To: Midrange Systems Technical Discussion
Subject: Re: Migrate iTERA to PowerHA
<snip>
I don't think to many folks use PowerHA at V5R4 so the answer to your
question is a bit different.
</snip>
I get that. I just tossed those out there as past examples of data
conversions occurring due to an OS upgrade.
The impression I am getting is: If you're running on #1, upgrade OS on
#2. Do your switch and quickly upgrade the OS on #1. Now, if it all goes
to heck on the new OS you could try switching back and hope that any data
conversions don't adversely affect anything.
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: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 05/21/2013 12:58 PM
Subject: Re: Migrate iTERA to PowerHA
Sent by: midrange-l-bounces@xxxxxxxxxxxx
PowerHA has an Administrative Domain that can copy 80% of the *SYSBAS.
The HA Assist (iCluster) product gets you about another 15% over that.
There are some objects no one can replicate at an application level.
So the answer to your question is yes, PowerHA gets all the things you
were thinking of.
Upgrades happen just as with any other upgrade, although once an iASP
has been taken to V7R1, it cannot be reattached to a V6R1 system.
I don't think to many folks use PowerHA at V5R4 so the answer to your
question is a bit different.
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On 5/21/2013 11:29 AM, rob@xxxxxxxxx wrote:
So this doesn't copy stuff like user profiles, object ownership and that
stuff?
I guess I can see leaving some of this stuff out of the iasp, like the
key
assigned to a vendor package. Stuff we already deal with in Mimix type
of
environments.
What about the object conversions I mentioned earlier: stream file
type1
to type2, STROBJCVN, etc. Any of that a factor during the upgrade?
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: Jim
Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx> To: Midrange Systems
Technical Discussion <midrange-l@xxxxxxxxxxxx>, Date: 05/21/2013 11:52
AM Subject: Re: Migrate iTERA to PowerHA Sent by:
midrange-l-bounces@xxxxxxxxxxxx With PowerHA all the customer data is
in an iASP leaving *SYSBAS to only the OS and LPP. (and stuff that has
to be there that the administrative domain or HA Assist replicate) So
you push the iASP over to the second system in the cluster, vary it on
and away you go. Now number 1 only has *SYSBAS attached. Upgrade/Apply
PTFs at your pleasure during working hours. When done bring the
cluster back and repeat with number two. Most folks actually have two
copies of the iASP in separate locations rather than just doing the
clustering described above. It's all part of clustering. Jim
Oberholtzer Chief Technical Architect Agile Technology Architects On
5/21/2013 10:29 AM, rob@xxxxxxxxx wrote:
I think this has been answered before so forgive my continuing
doubts.
But is this setup sort of like:
Power 7 #1
connected to SAN
Power 7 #2
You do some magic that says run on #2 now. Both #1 and #2 are using
the
same SAN but only one can be 'live' at a time?
How does one upgrade the OS? Wouldn't that require some outage?
Considering that part of the OS may be a conversion like changing
stream
files from TYPE1 to TYPE2 (remember that?), strobjcvn, all the
system
cross reference files, etc.
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 46755http://www.dekko.com
--
--
midrange.com
