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



Rob:

18.5 hours seems really long for a BRMS recovery. So I'm guessing that
included the time to load LIC and initialize the system, then add the disk
to the ASP? (both of which would have caused the disk units (regardless of
type) to initialize?

So how long was the recovery from loading IBM i to finishing the RSTAUT?
That's more fair comparison of a BRMS recovery to a manual one.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Tuesday, December 23, 2014 6:34 AM
To: Midrange Systems Technical Discussion
Subject: RE: Will mixing 775 SSD and 177 SSD in a 5887 EXP24S I/O drawer be
a potential performnace issue

Did an unload/reload of a spinning disk Power 6 based lpar to a SSD guested
Power 8 lpar.
~8 hour save (LTO 4)
Did a BRMS recovery on to the new system.
Pretty much followed the BRMS recovery report to the 'T'.
About an 18.5 hour recovery doing it this way.
I can send you step by step log.

But, really, you have no HA Mimix like system?
We do. And we were swapped over to the other system while we did this.

Good test of system swapping.
Good test of your recovery procedures.

And I've done 11 of these lpars this way. Three of them twice. So, by the
time I did this lpar I had this process pretty much ironed out.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.