Re: P8 to P9 migration -- MIDRANGE-L

Not sure how comparable this is but recently moved our workload from a P6
with spinning disks (not sure of the speed) to a P8 with IBM FlashSystem
V5030 SAN (migrated from SSD's).

Batch used to take 3 hours 20 minutes and now takes 1 hour 10 minutes.

Part of that of course due to faster box, faster disks and faster VTL (we
take a full database save before batch starts and we updated the VTL's from
IBM ProtecTier to DSI).

The business was pretty impressed.

Up till now we have been doing non BRMS FSS as part of the migration
process (for example going from SSD's to SANs we took a FSS and then
restored it to the SAN).

We plan to put a BRMS FSS into a weekly schedule.
Show quoted text

On Sat, Dec 4, 2021, 6:44 AM Rob Berendt <rob@xxxxxxxxx> wrote:

BRMS report
Lpar1 lpar2
1 - LIC Not recorded due to Alt-ipl vs alt-installation issues
2 - OS 27 27
4-BRMS 16 15
5-brms, 2 2 2
6-brms,init 2 2
10-Users 4 4
12-cfg 1 1
13-sys libs 2 2
16-sys/user dta 2:31 35

Not production lpars.
Lpar1 has test Infor-LX data on it.
Lpar2 has 3 test Domino servers on it.

What's the old rule of thumb? A restore should take twice as long as a
save?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steinmetz, Paul via MIDRANGE-L
Sent: Friday, December 3, 2021 12:17 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: P8 to P9 migration

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.

Sounds good.
How long was the total restore time for each LPAR for the migration?

I did P7 to P9 migration 3 years ago, using a similar process.
It's a good live test of a system restore.

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Friday, December 3, 2021 9:42 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: P8 to P9 migration

Moved a pair of lpars from a P8 8286-41A with 15k spinning disks to a P9
9009-42A with SSD's this week.
Lpar1:
Rclstg dropped from 1:00 to 0:03
Full BRMS save dropped from 2:03 to 1:03
Lpar2
Rclstg dropped from 0:13 to 0:01
Full BRMS save dropped from 0:36 to 0:11

Migration was done using a BRMS save. Hey, if you don't test your
restores then you don't have a save. Restores were done using the BRMS
recovery report.
All lpars are guested underneath internal disk hosted by an lpar of IBM i.
Migration was done under IBM i 7.4.
Media was a Data Domain 2500 VTL. With four "drives" in parallel.

Same subnet.
Only problems:

- Could not use the VTL as an alternate IPL device. However I
could use it as an alternate installation device.

- Had to change the resource name on the line descriptions. This
is a very minor issue.

- New license keys

P8 is still in use serving up other lpars (for now)
P9 has been in use and these were new lpars added to an existing situation.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com