ASM redundancy

From Dirty Cache Wiki
Revision as of 14:10, 16 September 2021 by Bart (talk | contribs) (Created page with "Category:Best Practices = Oracle ASM reduncancy = Because enterprise storage arrays have excellent data protection, even in the case of disk (SSD) failures or even compo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Oracle ASM reduncancy

Because enterprise storage arrays have excellent data protection, even in the case of disk (SSD) failures or even component failures (CPU, storage nodes) there is usually no need to configure ASM normal or high redundancy. External redundancy is the recommended practice, with the exception of CRS (cluster resource) diskgroups.

Normal redundancy: Each chunk (ASM Allocation Unit) is copied to two different volumes.

High redundancy: Each chunk (ASM Allocation Unit) is copied to three different volumes.

Retrieved from "https://wiki.dirty-cache.com/index.php?title=ASM_redundancy&oldid=136"