Re: Can a load source be migrated using the utility in DST from an actual physical disk in ASP1 to a virtualized disk in ASP2 or must the load source always be ASP1?

Yes, you can mix physical and virtual disk in an ASP.


________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Sent: Monday, June 27, 2016 12:39 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Can a load source be migrated using the utility in DST from an actual physical disk in ASP1 to a virtualized disk in ASP2 or must the load source always be ASP1?

This is an R&D LPAR, currently with all 10k spinny, 7 full copies of Production, each copy is 1tb, so 7+tb.
I already virtualized 3tb from Production to ASP2, made 1 copy of R&D all ASP2, which is all virtual, by RSTLIBBRM forcing to ASP2.
I need to control the which environment goes to spinny or to virtual SSD, doing this with the RSTLIBBRM to ASP2.

Can an ASP have a combination of 10k spinny and 1 vitual, then I probably could migrate the load source to virtual?

Paul



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roberto José Etcheverry Romero
Sent: Monday, June 27, 2016 12:20 PM
To: Midrange Systems Technical Discussion
Subject: Re: Can a load source be migrated using the utility in DST from an actual physical disk in ASP1 to a virtualized disk in ASP2 or must the load source always be ASP1?

Paul,

The one thing i don't really understand is this:
You are supposed to be able to set preference regarding whether to use SSD or SPINNY for libraries and objects. With that you shouldn't have to separate in ASPs to get your hot data onto the SSDs, did i miss a comment on why you can't just set the flag for the production libraries to stay on spinny and move the rest to the SSDs?

Best Regards,

Roberto

On Mon, Jun 27, 2016 at 1:11 PM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

Are you talking on the HOST or on the Client?.

LIC and Base IBMi reside in ASP1 of a LPAR no matter how that disk is
presented to the LPAR. By that I mean if you have Physical Disks
assigned, SAN LUNs assigned or Virtualized IBMi or VIOS Disks assigned
as the disk to an LPAR, LIC and Base IBMi goes in ASP1 ( System ASP ).
It sounds like you want to place SSDs in ASP2 of a HOST IBMi LPAR and
then create and present virtual disks from ASP2 of the HOST to a
Client IBMi LPAR. If that is your goal then YES you can do that. The Client will see just a bunch of disks.
When You install LIC and Base OS on the Client LPAR, you will have an ASP1.
Unless you have a specific need I would just run that whole LPAR with
just the system ASP. Underneath the covers, those ASP1 drives of the
Clientwill be carved out of your SSDs in ASP2 of the HOST.

Is this what you wnat or am I missing something?

On Mon, Jun 27, 2016 at 8:36 AM, Steinmetz, Paul
<PSteinmetz@xxxxxxxxxx>
wrote:

Can a load source be migrated using the utility in DST from an
actual physical disk in ASP1 to a virtualized disk in ASP2 or must
the load

source

always be ASP1?

If not, can I create another virtual, specifically for the load
source, and add it to ASP1.
ASP1 would then have a mixture of 10k spinny and 1 virtual.
ASP2 would be 100% virtual.

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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related questions.
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related questions.