Re: Easiest Way to Clone LPAR configs from one HMC to another

Hmm, I know you can save while active the network storage spaces. So how
are you doing your restoration plan now that you have them built on the
host. I guess you could exclude the sav portion of the NWSSTG's to build
your host like you did, then recreate them all manually. I am not sure of
the time trade-off 'vs' having then to restore every slave lpar as well.

On Mon, Apr 23, 2012 at 4:57 PM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

We elected to do the Initial Full System Save of the host partition before
we created all the storage spaces. In the past I have found restoring a
system with a number of large storage spaces it took
FOOOORRRREEEEVVVVEEEERRRR and then some compared to the save time. We
needed to get at least a shell of each partition up.

I don't have the times handy, but copying a 128GB storage space was faster
than Installing LIC, The OS and PTFs.

On Mon, Apr 23, 2012 at 11:25 AM, Jack Kingsley <iseriesflorida@xxxxxxxxx

wrote:

First, have you saved your host LPAR on to tape(s)?? If you have and you
can import your sysplan I would image you could 01D ipl off that saved
tape, eventually you would have all the slave NWS/NWSSTG's and you would

be

good to go??

On Mon, Apr 23, 2012 at 8:32 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

Excellent, I love finding partners that actually know about the proper
code to add to orders!

I hear the fat finger argument, my fingers are at least a two keys
bigger than the ones I generally want to hit....

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/22/2012 6:46 PM, Kirk Goins wrote:

Thanks Jim,
The BP ( me and my very good sales rep ) did specify the feature

codes,

sysplan and rack layout to have the system built correctly andx

double

checked on the order. IBM did at least build the HW in the rack
correctly...

Host plus 5 guest really isn't too bad. Just some need to make the 2

system

as close as I can want ed to keep the fat fingering to a minimum:)


On Sat, Apr 21, 2012 at 11:55 AM, Jim Oberholtzer<
midrangel@xxxxxxxxxxxxxxxxx> wrote:

In order to get IBM to follow the system plan they are furnished,

the

order has to have the correct feature codes on it. Since very few
partners even know they can do that it is doubtful that feature

code

was

on the order. Furthermore the system has to be a brand new

system,

not

an MES upgrade (even if the hardware is completely replaced), so

I'm

not

surprised the hardware layout was not to your specifications.

Since the LPAR configuration is really stored on the FSP, your

best

bet

is to export the system plan and then import it, but 6 LPARs does

not

seem like that many to create manually. Two hours should do it

and

I'll

be faster in the long run by the time you get done setting up all

the

virtualization anyway.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/20/12 1:16 PM, Kirk Goins wrote:

> Normally I work on systems with just a few ( 2 or 3 ) LPARs

and

it's

pretty

> fast just to create the LPARs by hand. I know I could upload

a

sysplan

but

> have never had the time to play with that.
>
> So we just put together a 6 LPAR box ( 1 IBM i Host and 5

IBM i

Guests ).

> Now I get to do its twin next week. Assuming IBM didn't

follow

the SPT on

> the 2nd system like they didn't on the first... I was

wondering

if there

is

> a way save the LPAR config data and restore it to the 2nd HMC

and then

jsut

> make some tweaks? Can I export the say a SYSPLAN from the

HMC

and import

> it into SPT?
>

--
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
athttp://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.

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