Re: Migrating extant system to new hardware

Oh, and the little stuff, like changing your line descriptions from CMN02
to CMN01 or some such thing, is just something you can do after the
restore. No big deal. Either change the configuration object or wizard
yourself around in SST to change the resource name. (I've done it both
ways.) Like I always change TAPMLB01 resource to something to match what
I want.


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: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/20/2017 01:24 PM
Subject: Re: Migrating extant system to new hardware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I would restore OS and all from your tape.
There is a warning in the backup and recovery manual about restoring to a
different system.
Appendix D is the classic Bible on doing an unload/reload to a different
system.
The thing you are concerned about is:
<snip>
If you are restoring to a different system, or a
different logical partition, you must specify
ALWOBJDIF(*ALL) or ALWOBJDIF(*COMPATIBLE) on
the RSTxxx commands and SRM(*NONE) on the
Restore Configuration (RSTCFG) command.
</snip>
Or from the menu restore option pay attention to
<snip>
On the Specify Command Defaults display, enter the name of the tape drive
that you are using for the restore.
Set Prompt for command to N.
Set Message queue delivery to *NOTIFY.
Set Restore to different system to Y.
Set Spooled file data to *NEW.
</snip>
especially the "Restore to different system" prompt This will change the
defaults to match the commands above.
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_
71/rzarm/rzarmsteps2.htm


Failure to change SRM can <expletive deleted> up your system, big time.

Of course, BRMS prints a nice recovery checklist which I've actually used
to do unload/reload from P6 to P8.
Jim scoff's at the idea of using BRMS to do a planned unload/reload
because he's so comfortable doing these. And he may be right. Me? I
figure it was a good test of their recovery procedures.

Basically, just follow the fine manual. They did not write this manual
for people like Jim, Larry, Pete. They wrote it for the masses.



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: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/20/2017 12:56 PM
Subject: Re: Migrating extant system to new hardware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Ok, so it sounds like in the end what I want to do is to save everything
on
tape, install the same level OS on the target box, and do a restore from
physical tape.

Is there anything I should *omit* from the restore because these are two
different p-series boxes? Will my device setup be screwed up? (Aside from
changing IP address)?

On Wed, Dec 20, 2017 at 10:52 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Jack,

For example, certain tape libraries are incapable of being IPL'd from.

You

IPL from DVD. But you do not install one thing from the DVD. You

install

from your alternate installation device.
I "think" the OS must be the same. So you can't IPL from a 7.3 DVD and
use 7.1 tape in your alternate installation device. In fact, I think

I've

been burned by this.
Probably another good reason to keep a recent resave of your OS on
physical media. Might as well leave it in your DVD drive. I just may

do

that next time I go the the remote DC.


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: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/20/2017 12:38 PM
Subject: Re: Migrating extant system to new hardware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Again: "alternate IPL device" vs "alternate installation device".
Would that make a difference?

My head hurtz ... :)

On Wed, Dec 20, 2017 at 10:31 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Again: "alternate IPL device" vs "alternate installation device".
Would that make a difference?


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: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxx>,

Rob Berendt <rob@xxxxxxxxx>
Date: 12/20/2017 11:47 AM
Subject: Re: Migrating extant system to new hardware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I have never hit a limit of virtual optical total capacity of the

image

catalog and I have migrated multi-TB systems this way.

The biggest thing is having enough disk space.

The second is enough network to push it all.

The third is a place to boot the new system from whether that is an
image catalog on VIOS, a network based catalog on the existing system,
or a physical disk. DO NOTE I have seen in this thread references to
'far far away' and if you are trying to IPL from the network to

install

IBM i LIC using TFTP/NFS that is across the country that will with

high

probability fail across a WAN. It IS sensitive to latency. I do it
across the state of MI but that's on dedicated private fiber with 4ms
latency, It sometimes fails over the link to my home office with a

15ms

latency. So be warned.

- 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/20/2017 11:01 AM, Rob Berendt wrote:

<snip>
I have not researched inherent limit of virtual optical but I do

like

that

idea of backing everything
up and transmitting an image then installing raw from the image.

I've

never done that, but it really works?
Again, is there a limit to the size of the virt opt image?
</snip>

It's pretty darn big if there is a limit.
Keep in mind that virtual optical is an "image catalog". Very

important

term.
Each "image catalog" has multiple "image catalog entries".
I have one image catalog composed of 6 image catalog entries. Each

entry

is between 1-4GB. This is just the latest PTF cume and groups.
Name Size
CUME_1.bin 4,145,152K
CUME_4.bin 3,801,088K
CUME_5.bin 3,784,704K
CUME_3.bin 3,407,872K
CUME_6.bin 2,048,000K
CUME_2.bin 1,392,640K
I've done OS upgrades with a LOT more entries.

I think there's a limit of 1TB on each image catalog entry.

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_
73/rzamp/rzampother.htm

You might want to verify that for 7.1. Just change the dropdown on

the

left.

Rob Berendt

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you

received

this communication in error, please contact the sender and

delete/destroy

all copies of this communication immediately.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD