Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 655
  • Last Modified:

VMWare , use multiple volumes and datastores for vcenter and SQL?

Is it best practice to have vcenter and the SQL database files and the database logs all on separate volumes?

I need to show a co worker evidence of this best practice do you have a link?


 thanks
0
NAMEWITHELD12
Asked:
NAMEWITHELD12
  • 3
  • 3
  • 2
  • +3
5 Solutions
 
RickEpnetCommented:
How many VMware hosts do you have?
0
 
NAMEWITHELD12Author Commented:
16

thanks
0
 
Gareth GudgerCommented:
This is more of a SQL best practice than a VMware one. If possible it is best practice to keep the logs and databases on separate drives.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
NAMEWITHELD12Author Commented:
what about separate volumes or datastrores? is there any reason not to do this?
0
 
Gareth GudgerCommented:
Are you using local storage or shared storage?
0
 
RickEpnetCommented:
When it says drive is mean different spindles. If you have a raid 5 with 3 drives on it. It is not really going to make much of a difference if you put them on separate drives the big difference comes in then you put them on different set of spindles. You want your data abd logs on the fastest set of drive. Separate is better.

So if you have 2 volumes that are on different raid sets that would be best.
0
 
NAMEWITHELD12Author Commented:
this will be on a netapp san. So what I am going to go with is 3 separate sets of  spindles

1. for the C drive of the SQL spindle set 1

2. for the DB files D: drive spindle set 2

3. for the DB  log files E: drive spindle set 3
0
 
RickEpnetCommented:
In this case I do not think it is needed but you can put the Temp DB on another drive too.

Your Plan looks good.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you consult SQL DBAs and SQL Circles, they will advise to do this, but if you have a SAN, which all volumes and LUNs are on the same spindles, difficult todo, and these recommendations were in the days, when we did have SAN volumes spanning hundreds of spindles.
0
 
robocatCommented:
From a data recovery viewpoint, you should put database and logfiles onto different volumes, especially if you plan to use Netapp Snapmanager for SQL. This way, you can restore the database volume from a snapshot without losing the logfiles (needed for recovery).

If you're really paranoid, you can put the database and log volumes on different aggregates, allowing a full recovery up to the last database transaction, even if you lose an entire aggregate. In a vcenter context, this is not necessary because the vcenter database is not that critical.
0
 
compdigit44Commented:
In regards to SQL it is best to reseperate the server drives like the following example:
c:\ = OS
d:\ = Application Install Dir
e:\ = DB Files
f:\ = Log Files
G:\ = Backup
H:\  = Page Files

For the datastore try to break up your volume into high, medium and low IOPS usage.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 3
  • 3
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now