Re: ASM & split-mirrors
From: Matthew Zito <matt_at_crackpotideas.com>
Date: Sun, 3 Mar 2013 20:48:14 -0500
Message-ID: <CAJ7936yQFf-gsbZsVdW+M7sOKCYNHcd8eVBV5gbFMgZ-EeNN=w_at_mail.gmail.com>
ASM won't care - it only looks at the signature on the header of the disk (assuming your scan path is set to look at the right set of LUNs). You only run into issues when you do something like clone a lun, so the same device appears at both /dev/sda and sdb on the same server, as ASM won't know which LUN is the "real" one.
Matt
Date: Sun, 3 Mar 2013 20:48:14 -0500
Message-ID: <CAJ7936yQFf-gsbZsVdW+M7sOKCYNHcd8eVBV5gbFMgZ-EeNN=w_at_mail.gmail.com>
ASM won't care - it only looks at the signature on the header of the disk (assuming your scan path is set to look at the right set of LUNs). You only run into issues when you do something like clone a lun, so the same device appears at both /dev/sda and sdb on the same server, as ASM won't know which LUN is the "real" one.
Matt
On Sun, Mar 3, 2013 at 8:30 PM, Hubler, Daniel <daniel.hubler_at_aurora.org>wrote:
> That sounds pretty routine.
> Thanks.
> One thing is bothering me. . . . .
>
> When the LUNs are established on the TARGET side,
> they will have different names/identifiers than on the source side.
>
> That is, /dev/diska on the source side will become /dev/diskx on the
> target.
>
> How does that get reconciled within ASM?
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Mar 04 2013 - 02:48:14 CET