RE: ASM - hardware mirroring vs. Oracle mirroring

From: Baumgartel, Paul <>
Date: Fri, 11 Apr 2008 15:47:56 -0400
Message-ID: <>

But isn't mirroring and striping most of what ASM does? Wasn't it intended to eliminate the need to purchase an expensive SAN?  

I understand that many people use ASM in conjunction with Symmetrix, etc., but I don't see how just pooling the storage and presenting it to the database is worth the effort (and the limitations, as there are certain operations in, e.g., RMAN, that aren't supported with ASM).  

Paul Baumgartel
Information Technology
Prime Services Databases Americas
One Madison Avenue
New York, NY 10010
Phone 212.538.1143  

[] On Behalf Of Bobak, Mark
Sent: Friday, April 11, 2008 9:59 AM
To:; Subject: RE: ASM - hardware mirroring vs. Oracle mirroring


Where in the documentation do you see Oracle having a bias towards ASM doing mirroring?  

I ask cause several Oracle folks I talked to, and an Oracle "best practices" presentation I saw a while ago, all say the same thing. That being, if you already have a well-designed SAN, use external redundancy in ASM, and let the SAN do all the mirroring and striping.  

That's where we're at, as well. SAN does all mirroring and striping. ASM just pools the storage and makes it available to the database.  


Mark J. Bobak
Senior Database Administrator, System & Product Technologies
789 E. Eisenhower, Parkway, P.O. Box 1346
Ann Arbor MI 48106-1346
+1.734.997.4059  or +1.800.521.0600 x 4059 <> <> <> 

ProQuest...Start here. 



[] On Behalf Of Schauss, Peter
Sent: Friday, April 11, 2008 9:34 AM To: Subject: ASM - hardware mirroring vs. Oracle mirroring I am starting to investigate ASM as a part of a potential to 10g upgrade on Solaris (SunOs 5.9). Oracle's documentation seems to have a bias toward having the ASM instance handle the mirroring while our UNIX support people would prefer to do it at the hardware level. Which is preferable and what factors would push a decision in one direction or the other? Thanks, Peter Schauss ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: ============================================================================== --
Received on Fri Apr 11 2008 - 14:47:56 CDT

Original text of this message