jeff_browning
3 Argentum

Are these still good Oracle on VMW guidelines???

Jump to solution

Matt Kaberlein raised these questions today, which seemed like good ones to me:

Just wondering if the following are still good best practices guidelines at this point:

  • Dedicate specific datastores to specific Oracle data types and/or Oracle DBs?
  • Map VMDKs to separate datastores to increase isolation and performance parallelism?
  • Leave roughly 20% of available capacity on each datastore for ESX overhead if applicable (vMotion, VM snaps)?
Labels (1)
0 Kudos
1 Solution

Accepted Solutions
kmani
2 Bronze

Re: Are these still good Oracle on VMW guidelines???

Jump to solution

Yes all are valid, adding to Jeff. 20% is generally recommended for production workloads.


View solution in original post

0 Kudos
4 Replies
jeff_browning
3 Argentum

Re: Are these still good Oracle on VMW guidelines???

Jump to solution

I agree on everything except the 20% free space. Don would have to say if that’s still necessary, but I rather doubt it. VMFS has become much better behaved in recent releases. I doubt you need that much free space at this point. However, Don may comment further.

In terms of the isolation stuff, yes, certainly put separate Oracle databases on separate .vmdk files which are, in turn, on separate VMFS file systems. That way, you will be able to snap / clone each database individually. Otherwise, you waste IOPS and space (making additional copies of updated blocks in the non-used database).

0 Kudos
kmani
2 Bronze

Re: Are these still good Oracle on VMW guidelines???

Jump to solution

Yes all are valid, adding to Jeff. 20% is generally recommended for production workloads.


View solution in original post

0 Kudos
zhaos2
3 Zinc

Re: Are these still good Oracle on VMW guidelines???

Jump to solution

For the first question, a datastore is always an abstraction of the storage tier for oracle applications and, therefore, it’s a generally accepted best practice to create dedicated datastores if Oracle customers need to define individual service level guarantees for different database file (whether log or database files).

For the second question, are you saying you have different VMDK files from different Oracle virtual servers and need to map those vmdks to separate datastores? If yes, I guess what you’re saying is to separate different oracle databases by mapping them to different datastores, or maybe it’s different files from one database instead.  I think, whatever it is, different datastores consist of different LUNs from storage array finally.  So theoretically I believe that the mapping means more control from DBA or Storage Admin though it’s not a substitute for oracle performance.

zhaos2
3 Zinc

Re: Are these still good Oracle on VMW guidelines???

Jump to solution

For the third question, if you are migrating virtual machines between two ESX hosts that store the virtual machine swap files in different locations, vCenter  may require enough disk space to store two full sized copies of the virtual machine swap file.  If there is not enough space in the datastore, you will receive error message.

There are no Best practices for VM snap, it depends on your VM’s change rate.

0 Kudos