Thanks for the responses.

Where I was coming from was initially we were going to use storage on a
DS8886 SAN connected to one of our mainframes and a second DS8886 in our DR
site.

This Redbook

http://www.redbooks.ibm.com/abstracts/sg248887.html?Open

in section 11.7

describes how you can connect a Power server to DS8K SAN natively, using
VIOS NPIV or VIOS VSCSI and boot from it.

Then it says in 11.8.2 if you boot from the SAN you can take advantage of
the features of the DS8000 copy features and replicate a copy of the LUNS
to another site where another Power box is located and boot from that. So
clearly it takes care of license numbers, devices etc.

And replication can be real time which is great for DR.

But our situation changed and we're now looking at two different data
centers where we don't have DS8K SANs but HPE 3PAR and so I was wondering
if I could use the same process to support DR.




On Thu, Nov 21, 2019, 7:33 AM Marco Facchinetti <marco.facchinetti@xxxxxxxxx>
wrote:

Or two VIOS on one SAN with two (FC/ETH/RAID CARD) of all. You save a lot
of money in disks, enclosure and licenses.


--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno mer 20 nov 2019 alle ore 18:44 Holger Scherer <hs@xxxxxxx> ha
scritto:

Tried this (boot replicated VIOS to other machine) with same hardware
(2*P7 boxes) and the result is not suitable
for DR purposes as you will run into lots of new devices due to serial
number (or maybe bus number) changes.

Better way is to have two VIOS on two SANs.

-h

Am 20.11.2019 um 11:12 schrieb DrFranken <midrange@xxxxxxxxxxxx>:


I have not tried to replicate the VIOS servers via the SAN but it
strikes me that this would not be a good idea. It seems unlikely to me
that
a replicated VIO server would be any level of happy at all if IPLed onto
another system. That said, I've not tried it either. Dang another thing
for the 'some day' list.....

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

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.