|
Exactly.
But that raises an interesting point. Everything is on the SAN and the LUNs
are all replicated from production to DR. So in DR we can spin up the DR
instance off the replicated LUNs and with only some minor configuration
changes during startup to alter the host IP addresses to be in the DR
server network subnet it all comes up.
Now if the VIOS is on the SAN what would happen when that LUN was
replicated to the DR site and that replicated LUN was defined as the load
source? Or is the VIO configuration separate from the load source?
On Tue, Aug 30, 2022 at 3:53 AM Rob Berendt <rob@xxxxxxxxx> wrote:
Especially since the OP is already using SAN
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
Larry "DrFranken" Bolhuis
Sent: Monday, August 29, 2022 11:38 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>;
Marco Facchinetti <marco.facchinetti@xxxxxxxxx>
Subject: Re: [very long] Moving from physical FC adapter to VIOS (was: Re:
VTLs and backup time)
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.
On 8/29/2022 11:25 AM, Marco Facchinetti wrote:
The biggest debate will be internal or external disks for your IBM i.Ahh yes, however when presented the list of capabilities provided by SAN
that internal disk will never do, the majority of my customers go SAN.
Internal disk DOES have it's place but that place is shrinking daily!
- DrF
--
IBM Champion for Power Systems
www.iInTheCloud.com - Commercial IBM i and Power System Hosting
www.iDevCloud.com - Personal IBM i Hosting
www.Frankeni.com - IBM i and Power Systems Consulting.
--
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
As an Amazon Associate we earn from qualifying purchases.
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.