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



Thanks for that link, much appreciated.

On Wed, Dec 16, 2015 at 11:42 AM, Steve Pavlichek <spavlichek@xxxxxxxxxxx>
wrote:

Evan,
Check out the Redbook “IBM i and IBM Storwize Family: A Practical Guide to
Usage Scenarios”

http://www.redbooks.ibm.com/redpieces/abstracts/sg248197.html


-----Original Message-----
From: Evan Harris
Sent: Tuesday, December 15, 2015 1:59 PM
To: Midrange Systems Technical Discussion
Subject: Re: Disk Mirroring

Hi Larry

they report as 2145-050 but for some reason the i does not seem to
recognise that they are protected (I kind of thought the 050 signalled
this....)

Do you have any advice as to what commands we should be using on the V7k to
create the LUNs or to customise them after they are created and before we
use them in the i ?

On Wed, Dec 16, 2015 at 3:33 AM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

What type are those SAN LUNs reporting in as? 6B22-050? 2145-050?
Something else? (Something-109 comes to mind...)


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/15/2015 1:14 AM, Evan Harris wrote:

Hi Larry

that's where I got to, but for some reason the SAN LUNs don't show up as
protected and then the system wants to protect them.

I am presuming there is something the V7k administrator needs to in
order
for the disk to show up as protected; what configuration step could they
be
missing here - any clues ?

Any configuration on the i side we need to do in SST ?

Caveat: for reasons slightly beyond our control we are doing this
without
a
HMC on a single partition system.


On Tue, Dec 15, 2015 at 6:05 PM, DrFranken <midrange@xxxxxxxxxxxx>
wrote:

Evan,

When you start Mirroring you are starting it for an ASP.
Mirroring
will pair up all disks in that pool which are not already protected by
either Mirroring or RAID.

Once you start Mirroring on the ASP any disks added to it will
automatically be Mirrored UNLESS they are already protected either by
RAID
or by the storage subsystem (SAN or Host partition).

So the Secret is don't add the SAN LUNS to the system until
after
you have mirrored the SSDs. The SAN LUNS are supposed to me flagged as
already protected so you will be allowed to add them to the system
without
them being mirrored by IBM i.


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/14/2015 2:32 PM, Evan Harris wrote:

Hi guys

is it possible to start mirroring on a pair of disks without starting
mirrorign on every other disk in the system ? If so, what are the
steps
to
achieve this ?

I have a system which has a pair of SSDs in the base enclosure but the
rest
of the storage is intended to be provided by a SAN (V7000). The
problem
is
that starting mirroring keeps wanting to protect the SAN LUNs, or
adding
the LUNs to the ASP causes the system to want to configure mirroring
on
the
newly added disk units.

I've looked in the info centre and found a few different PDFs on Disk
management but primarily they talk about starting mirroring on the
disk
pool when I really just want to start it on a pair of disks and leave
all
the other disks without protection - at least as far as the i is
concerned.

The only thought at this point is to start RAID on the disks prior to
adding them to the ASP and then end RAID once they are added. But this
sure
seems like the long way around.

Is this possible ?

--

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.




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




--

Regards
Evan Harris
--
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.
--
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.





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