I'm going to be deploying a new Microsoft Server 2008 R2 VM to be used as a file server. It will provide about 4TB of storage (currently 50% utilised). I've been thinking that I would deploy a ~20GB C: drive using a VMFS disk, and add my storage as additional disks (our practice is always to store data away from the C: drive).
Current intention is to carve out 4 x approx 1TB LUNs, make them into VMFS-based disks, then add them to the server as 😧 E: F: and G: drives ... and then make the storage available to my users as a single S: network drive via a centralised Microsoft DFS share.
Wondering whether y'all feel this is a valid approach. Should I be using a larger LUN size (e.g. 2 x 2TB) and/or using a completely different approach?
For windows 2008 R2, 20GB is way too small.
For more details, check this link http://geeksilver.wordpress.com/2010/07/06/watch-out-your-windows-2008-c-drive-space/
I would say, use PVSCSI, and RDM together to boost your speed. You may consider to use VMNET3 nic as well.
- Silver
My Vmware blog: http://geeksilverblog.com
Thanks for the tip re: C drive size under Server 2008 R2 ... looks like I will have to plan for 40GB C drives instead.
Also good tip re PVSCSI ... I found this article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101765... which suggests that under ESX 4.1 there's really no reason not to use it ... so we'll give that a try. The file server will be mostly a fairly idle file store, however on the few occasions when it gets hammered the PVSCSI will help it perform a bit better.
Thanks again.
No worries. There are quite few bits you need to pay attention when you try to use PVSCSI.
I have some posts for you to read if you want.
- Silver
My Vmware blog: http://geeksilverblog.com
For the 4 TB of space I suggest to use at least two vmdk and to do not "merge" them togher with dynamic disks.
If you enable DFS (for example on the DC), you can simple create a single namespace of your files.
Andre