November 6, 2013 at 3:05 pm
We have a sql server 2008 custer on Wndows server 2003 virtualized using VMWARE
We are in the process of adding raw disks to the cluster. When these disks are added to the Virtual Machine, there is a possibility of storing the mapping file with either the virtual machine or a datastore on SAN(recommended).
My question do we need separate datastores on the SAN to store mapping files for each raw disk, or can we use a single datastore on the SAN to store mapping files for all raw disks ?
November 7, 2013 at 8:19 am
you can use a single one, it's probably easier to store the mapping files with the VM. I have done this in the past.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 7, 2013 at 2:01 pm
Thanks for the reply
When you say easier to store with the VM, do you mean the same LUN that the .vmdk file is stored on
OR
Do you mean store with the VM when adding raw disks to the virtual machine
Since VMWARE recommends that the mapping file be stored on the SAN, Im guessing it would be the first option
December 5, 2013 at 3:50 am
Gerard Silveira (11/7/2013)
Thanks for the replyWhen you say easier to store with the VM, do you mean the same LUN that the .vmdk file is stored on
OR
Do you mean store with the VM when adding raw disks to the virtual machine
Sorry, missed this one.
I mean store the RAW disk mapping file in the same datastore you selected during the VM creation.
Gerard Silveira (11/7/2013)
Since VMWARE recommends that the mapping file be stored on the SAN, Im guessing it would be the first option
The datastore where your VM files reside is likely to be a SAN presented LUN anyway.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply