Re: ASM administrative guidelines
- From: "Jeffery Thomas" <jeffthomas24@xxxxxxxxx>
- To: oracle-l <Oracle-L@xxxxxxxxxxxxx>
- Date: Wed, 13 Feb 2008 08:25:38 -0500
I received a number of replies in private, and the consensus was just two
disk groups per cluster. Are there some inherent reasons for having only
two disk groups, other than for administrative simplicity? Are there
issues with having a large number of disk groups? For example, we may be
looking at EMC Snapview to perform our backups on a cluster that will have
multiple databases. Accordingly, we would have to segregate each database
so that each has its own set of disk groups, a minimum of 3 per database:
data, flash, and online redo logs.
Thanks,
Jeff
On Feb 7, 2008 10:45 AM, Jeffery Thomas <jeffthomas24@xxxxxxxxx> wrote:
> We are looking at migrating to 10gR2 RAC/ASM from 9i RAC/VERITAS. I've
> read various papers and
> purchased the Oracle ASM book from Oracle Press and have researched this
> stuff, but from a practical
> level, I was wondering what kind of admin guidelines that those of you in
> more mature ASM shops may
> have developed, or perhaps any paradigm shifts that you've made as a
> result of working with ASM.
>
> For example, have you changed your standards as per multiplexing control
> files and redo logs? Do you use
> OMF or have you devised any sort of naming scheme with respect to ASM file
> aliases? If you were to redo
> your ASM install, would you change anything on how you configured it or
> are administering it?
>
> Thanks,
> Jeff
>
Other related posts:
