Re: Configuration of the SAN

Hi,

I see good comments in this thread. I've added some non-performance related thoughts below.

On Tue, 29 Mar 2005 14:51:07 -0500, Paul Drake <bdbafh_at_gmail.com> wrote: ...
> This is what I see as a HUGE reason for going with ASM:
>
> entire physical disks are turned over to oracle.
> The sysadmins, storage admins, everyone other than the people that
> were running connect-by queries against the +ASM instance are unable
> to tell what is going on under the hood.
> wonderful.
>

I think there are some additional planning aspects with SAN, for example,

What hosts will see the SAN? production, development, test, etc...

What LUNs should be allocated to what hosts?

Etc...

ASM would require an interface to SAN, e.g. raw disks, OCFS, ASMLib (yuck), and should be tested for vendor bugs and performance. Someone may need to be able to do connect-by queries if you want to effeciently manage recovery in ASM on a SAN. Maybe not so wonderful to do a simple file list of ASM.

Backup/Recovery strategy should include using SAN. It may not be as simple as RMAN backup and restore to tape, e.g. what about standby, clones, dev-refresh.

Any more?

HTH. Regards,

Mike Thomas

--
http://www.freelists.org/webpage/oracle-l