Paul,

If you go thru the reload method you create a new profile or partition with
all the required resources (vscsi, vnet, etc), map the NWS to those vscsi
(requires creation of server adapter on the hosting partition, of course)
and the IPL from the tape to restore.
Otherwise you can hot add both the server and client adapters thru DLPAR to
the partitions, map the NWS, and move the data to those new "disks" from
the DST menu (you also have to copy the LS, so one of those NWS will not be
added to the ASP yet).
Finally you change the Load Source Adapter on the profile, and then remove
all the not required hardware.
I think Larry wrote a more in depth guide on this matter a few months ago.

Best Regards,
Roberto

On Thu, Dec 3, 2015 at 4:01 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

Larry,

Option 1 "appears" much easier.
I may try both.

1) With each method, you must first create the NWS objects on the new
host, correct?
2) At what point in option 1 are the necessary HMC profile changes for
Pencor07, from physical to virtual?
3) Tape is not normally available on Pencor07, are there other options,
virtual tape possibly?
4) Is it Ok to use BRMS instead, we no longer use SAVE 21/RESTORE 21?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Thursday, December 03, 2015 12:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: Can a standard i5/OS V7R1 LPAR be migrated/converted to a
client NWS LPAR?

Why would Restore 21 not work?
- Create all the NWSSTG objects.
- Create NWSD objects
- Link them all
- Make the tape drive used for the SAVE 21 available.
- Restore.
I have done MANY of these with no issue.

Now if Pencor07 and Pencor06 live on the same physical server but each
have their own disks then there is a way to migrate Pencor07 as a Physical
partition into a Guest partition on Pencore06 without any restore at all.

1) Add virtual SCSI server adapters to Pencor06
2) Add virtual SCSI client adapters to Pencor07
- NOTE DO NOT remove any of the hardware RAID stuff at this point.
3) Create needed NWSSTG objects on Pencor06.
4) Create needed NWSD objects on Pencor06.
5) Link the above storage to the above NWSDs.
6) If you did 1 and 2 dynamically you should now see all the new disks on
PenCor07.
7) IPL Pencor07 to DST.
8) Use work with disks and copy disk unit data for the Load Source disk
unit to the first virtual disk unit created in PenCor06.
9) The system will IPL Back to the new disk unit.
10) ADD all the remaining virtual disks to PenCor07. DO NOT use "And
Balance" for this add.
11) Remove all the remaining physical disks from PenCor07. This will move
all that data from the physical to the virtual disks.
12) Wait for 11 to complete, then use operator panel functions in DST to
power down the partition.
13) Modify the partition profile to remove physical disk controllers and
designate the virtual scsi adapter for IPL.

Done. Now you have a virtual Pencor07 and some extra hardware laying
around.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/3/2015 11:34 AM, Steinmetz, Paul wrote:

I'm back to this old thread.
I want to take Pencor07, currently a sandbox LPAR, no important data,
which currently exists with all its own hardware, convert it to a new NWS
client LPAR which will be hosted by Pencor06.
I don't think Restore 21 will work.
Would it simply be easier to build the Pencor07New NWS from scratch on
Pencor06.
Except for all the current Pencor7 system configuration settings, there
is no data on Pencor07 of any importance.

I thought of another solution that might be easier.
Can a current NWS client be moved, renamed, and reconfigured to a new
host.
Could I copy current inactive NWS client Pencor08, from one host
Pencor07, to another host Pencor06.
Then I need a process to IPL/reconfigure this new client Pencor08Copy
from its new host Pencor06.

This is in preparation for my 2016 P7 to P8 migration, which will be
"collapsing" Pencor07 to a NWS client.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Monday, January 12, 2015 12:35 PM
To: Midrange Systems Technical Discussion
Subject: Re: Can a standard i5/OS V7R1 LPAR be migrated/converted to a
client NWS LPAR?

As Rob suggested you can use multiple hosts but I would only do that
transitionally *OR* if I really wanted to have storage mirrored between two
hosts. Uses a lot of disk but gives (in theory at least) a bit of extra
redundancy.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 1/12/2015 12:19 PM, Steinmetz, Paul wrote:

Larry,

I currently have 3 LPARS, 05, 06, 07, all with their own hardware.

This will only work if the new client (08) will be on the same current
host (05), which they are not, correct.
In my scenario, the new client (08) will be hosted from a different
LPAR (06) then the existing LPAR (05)

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of DrFranken
Sent: Monday, January 12, 2015 11:19 AM
To: Midrange Systems Technical Discussion
Subject: Re: Can a standard i5/OS V7R1 LPAR be migrated/converted to a
client NWS LPAR?

SAVE and REsTORE (option 21) is the documented 'it works' procedure.

BUT you can also:

Build the host partition.
Create the 'virtual' storage there to host the current 'physical'
partition. (CRTNWSSTG)
Add this 'virtual' storage to the 'physical' partition.
Use live disk migration to move all but the load source 'physical'
storage to 'virtual' storage.
IPL to DST for the load source migration (DEDICATED) Finally IPL to the
new 'virtual' load source with a new partition profile.

You might have an outage as low as an hour this way. I have done
several of these always successful.

You DO need twice (plus a little) the disk capacity available to pull
this off BUT you likely would have that because you wouldn't virtualize
unless you intended to build other partitions.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 1/12/2015 8:57 AM, Steinmetz, Paul wrote:

Can a standard i5/OS V7R1 LPAR be migrated/converted to a client NWS
LPAR?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.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 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 thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].