× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



System names are for LPARs, not physical machines, so just move the current
S02 LPAR to the Power7 and create a new S02BU LPAR on the Power6. WRKDIRE,
IFS, etc. are all tied to the LPAR, not the underlying hardware, so they'll
come along for the ride.

Example: This past weekend we replaced our Power5 system with a used
Power6. 3 LPARs were moved. As we migrated DASD over, 2 of the 3 didn't
need anything more than reassigning resources. The 3rd, which used DASD in
the old CEC, had to be restored from tape since the Power6 CEC uses SAS
drives (Power5 is SCSI so the drives wouldn't migrate). Even the restore
was simple: Restore from tape, fix resource assignments for things like
Ethernet. Nothing else changed.

I would probably go with a high level plan along these lines: Configure
your Power7 with an LPAR with the name S02TEST or somesuch. Load it up &
test. When you're ready to do the production migration, blow S02TEST away
and restore S02 to the Power7 from tape. Power down the S02 LPAR on the
Power6. Get the Power7 S02 up & running. Then delete the S02 LPAR from
the Power6 & create SB02BU.

As long as the old S02 on the Power6 and the new S02 on the Power7 aren't
powered up at the same time there shouldn't be any issues.

Search the Infocenter for "Backup and Recvoery". Here's the page about
restoring to a different system:
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzarm/rzarmsteps2.htm

On Tue, Jun 5, 2012 at 4:52 PM, Graap, Kenneth
<Kenneth.Graap@xxxxxxxxxxxxx>wrote:

I'm wondering how to best handle the following situation:


1.) I have a Power6 V7R1 system configured with the name "S02" . It is
currently my Production System.

2.) I'm purchasing a new Power7 V7R1 system, which will eventually be
"S02" my Production System.

3.) I want to configure the Power7 system using iASP's in preparation
for a System Mirror implementation, while having it attached to the same
network as our production Power6 system. I'm assuming it needs to be named
something other than "S02".

4.) Once the Power7 system is configured and tested, I want to backup
Power6 application data and restore it to the Power7 system and rename it
"S02".

5.) I then want to scratch and configure the Power6 system into one
named S02BU and use it as a CBU/System Mirror for the Power7.

6.) I don't completely understand all the implications associated with
changing the system name of the Power7 once it becomes the Production
System.


I know that changing the System Name of an IBM i can be problematic,
especially when BRMS is installed. I also believe that there can be issues
with System Directory Names (WRKDIRE kind, not IFS directories) and even
the RDB (relational Database Directory).

How would you go about coordinating this name swapping game with the
intent of eventually having the Power6 named S02BU and the Power7 named S02
???

Thanx in advance... Any suggestions and tips will be greatly appreciated...

Kenneth
Kenneth E. Graap
System Administrator
503.226.4211 x5537
http://www.linkedin.com/in/kennethgraap

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

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.