- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Creating new datastore for file storage
Hi,
Just looking for advice and recommendations on setting up a new 1.6TB datastore within ESXi 4.1. I am adding this new datastore which is actually my 3rd one. This new datastore is going to be provisioned for our file server. Currently, our file server is a physical server and we simply want to move our data to a Windows 2008 VM with access to all this new storage once we get it copied over. In order to do this, when creating the new datastore would it be best to choose a 4MB or 8MB block size? I would like to utilize all this space for this one VM which will house all our data. Also, in the beginning of the wizard it asks which one of my two hosts to attach this new datastore to...does this really matter?
Just thinking...would it be best to create one or two virtual disks for this VM? Guess I'm just a little confused on setting all this up. Any help is appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
when creating the new datastore would it be best to choose a 4MB or 8MB block size?
For 1.6TB you need an 8 MB block size.
Also, in the beginning of the wizard it asks which one of my two hosts to attach this new datastore to...does this really matter?
I assume this is the wizard on your storage systems!? If you want to be able to run the VM on different hosts (vMotion, ...) then you need to present the LUN to all of these hosts.
... would it be best to create one or two virtual disks for this VM?
This would mainly depend on the workload and your storage system. However, for use as a file server I think one virtual disk would be sufficient.
André
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the quick reply! The first step of the wizard asks "On which host do you want to add the datastore?" I only have two hosts at the moment. It makes me pick one or the other. I was thinking the same as you as both need to see the datastore.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't know which storage system you have and how the wizard works. However, if it does not let you select both hosts, continue with the wizard selecting the first host and later find out where you can present the LUN to the second host.
André
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So when creating the VM capacity size, is it best to choose 1.6TB instead of 1.64TB which is the actual amount? Is it best to leave a little extra non allocated? Also, would you recommend thin provisioning this? Seems like thick provision in this case might be best??
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
BTW...I'm using vCenter for all this setup including wizards I have mentioned, etc...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would probably not use the whole disk space for the virtual disk, but leave at least 10% free. You also need to make sure the datastore where the virtual machine's base folder resides (the folder which includes the vmx file) has the appropriate block size too!
Regarding thick or thin provisioning. It does not make a huge difference in disk performance whether the disk is thin or thick provisioned, except you choose eagerzeroedthick by checking "Support clustering features such as Fault Tolerance" in the create virtual disk wizard. Since you mentioned this LUN is for this one VM only, I would prefer thick or eagerzeroedthick rather than thin.
BTW...I'm using vCenter for all this setup including wizards I have mentioned, etc...
At the moment I can't think of a wizard in vCenter which askes on which host a LUN should be presented!? Can you please clarify this and/or attach a screen shot please.
André.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is the screen shot...it is the first screen of the add new datastore wizard.
(the folder which includes the vmx file) has the appropriate block size too!
How do you do this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
BTW...I chose host-a to add the new datastore to it....however I see the new datastore from both hosts within the summary tab on each...so in the end I don't think it matters....??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Maybe I should read what's on the different screens in the wizards
Since the datastore is actually created by one of the hosts, you need to select on which one it will be done. However, as you saw, the datastore will show up on all hosts which have the LUN presented from the storage.
(the folder which includes the vmx file) has the appropriate block size too!
How do you do this?
If the VM was created on a datastore with e.g. a 1 MB block size, you can only add virtual disks up to ~256 GB to this VM, regardless of the block size of the datastore on which you are going to create this new virtual disk. This is because of the fact, that snapshots of virtual disks in ESXi 4.x will - by default - be located in the VM's base folder. In order to be able to attach larger virtual disks to such a VM, you need to migrate it to another datastore with the appropriate block size.
André
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok...so I created my datastore with 8MB block size but I haven't created the VM yet. So I should be ok...right, in regards to your last comment. I guess something else to consider is extra space for snapshots. Would need quite a bit of space to snapshot a 1TB worth of file server:) Also, do you recommend a round robin managed path for this datastore? Thanks so much for your expertise!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I guess something else to consider is extra space for snapshots. Would need quite a bit of space to snapshot a 1TB worth of file server:)
Yes the main reason to reserve some free disk space, is for snapshots. The size of the snapshots depend on the changes made while the snapshot exists. As a best practice, a snapshot should only exist as long as necessary, e.g. for risky software updates and/or image based backups. A snapshot (delta file) starts with only a few MB in size and grows depending on the changes. If you don't need all the 1.6TB for the file server right now, I'd recommend you leave >=20% free. Depending on the OS you plan to use, it should be easy to grow the virtual disk when needed.
Also, do you recommend a round robin managed path for this datastore?
If RR is supported by the storage vender, then go for it.
André
PS: For how snapshots work in ESXi, see http://kb.vmware.com/kb/1015180
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks so much for the information but I am still struggling with something. As far as creating the file server VM...would you recommend creating a C:\ drive of course for the OS on one VMDK and then creating a D:\ drive on a separate VMDK? Wasn't sure what the best practice would be for this. I thought maybe if the D:\ data drive was a separate VMDK you could potenitally point it to another VM if something happened to the original. Any thoughts or suggestions on this?
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using separate virtual disks has a few advantages. Besides the one you mentioned, it is also easier (and a lot faster) to resize/grow the OS disk in case it is necessary.
André
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok thanks for all the help!