User profiles and other object's that aren't capable of being put into an iASP are added as Monitored Resource Entries. Cluster services will keep those objects in-synch using the Administrative Domain.
Patrick Bingham | Principal Power Systems Engineer
Office: 402.965.2381 | Mobile: 402.212.2944 | Patrick.Bingham@xxxxxxxxxxxxx
Sirius Computer Solutions | www.siriuscom.com
14301 FNB Parkway, Suite 400, Omaha, NE 68154
-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Tuesday, May 21, 2013 11:48 AM
To: Midrange Systems Technical Discussion
Subject: RE: Migrate iTERA to PowerHA
And how do you replicate the user profiles, 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 46755
http://www.dekko.com
From: "Patrick.Bingham@xxxxxxxxxxxxx" <Patrick.Bingham@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 05/21/2013 12:35 PM
Subject: RE: Migrate iTERA to PowerHA
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Any object conversions would happen when the iASP is varied on with a
sysbase at the newer release.
Patrick Bingham | Principal Power Systems Engineer
Office: 402.965.2381 | Mobile: 402.212.2944
| Patrick.Bingham@xxxxxxxxxxxxx
Sirius Computer Solutions | www.siriuscom.com
14301 FNB Parkway, Suite 400, Omaha, NE 68154
-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Tuesday, May 21, 2013 11:30 AM
To: Midrange Systems Technical Discussion
Subject: Re: Migrate iTERA to PowerHA
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 46755 http://www.dekko.com
--
--
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 message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.
Thank you.
--
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 message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.
Thank you.
midrange.com
