[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now


Suggestions for new ESXi & Server 2008 Setup

Posted on 2010-09-09
Medium Priority
Last Modified: 2013-11-21
I have just set up a new VMware ESXi 4.1 server. I am looking for suggestions so that my VMs run smoothly but aren't inefficiently using too much resources. If you were setting up the following VMs on this hardware as I am from scratch, how would you configure them?

**25 Users with 25 desktops in LAN office
**10 Users connect remotely to RDS 2008 Server
**25 users connecting to small SQL Express Database (500Mb)

Dell R710 running ESXi 4.1
Two 2.5GHz/Quad-Core Intel chips (8 cores total)
24Gb RAM
1.5TB Disk Space (six disk RAID5)

Production VM's:
1) Server Standard 2008 R2 - DC, File Server, SQL Express, Print Server, DNS, DHCP
2) Server Standard 2008 R2 - Remote Desktop Services (RDS) Role, for 10 users running apps: Office 2007, Quickbooks
3) Windows 7 Pro - Used as testing machine, just needs to be moderately fast
4) Vyatta router - this will take up minimal resources

What are your suggestions for RAM, Disk Space, CPU allocation for each VM that will allow them to run fast but not waste resources? How many cores should go to the servers? I plan on adding more VM's in the future so I want to be mindful of capacity. How much disk space should be allocated to system drives on the servers? Is it OK to set up these VM's to 'grow' as they need more data in the future? Basically how would you set this up from scratch.


p.s. I am NOT running Exchange, no need to size for that
Question by:goldylamont
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
LVL 16

Accepted Solution

Jon Brelie earned 1200 total points
ID: 33638619
The beauty of vmware is that you can adjust on the fly.  I would start with the following:

1. 1cpu, 4gb RAM
2. 1cpu, 4gb RAM
3. 1cpu, 1gb RAM
4. 1cpu, 1gb RAM.

You may need to add cpu, but my understanding of ESXi is that each system waits to execute an instruction until the number of cores they are assigned are available, so it is best to start low.  IE: if you have a VM assigned 4 cores, and only 3 are free, it has to wait until another is freed up.

You might find that you need to tweak RAM, particularly on the Terminal Server, but again-start low adn build your way up.  You can increase memory with a simple reboot.

Author Comment

ID: 33638765
Regarding RAM--my server has RAM optimized so that there are three physical chips for each CPU (6x4GB Chips for 2 CPU's). With this in mind does it matter how I allocate RAMs in VMs or are these independent as far as performance is concerned?

RAM Memory seems easier to play with since it can be changed with a reboot. However how flexible are changing CPU and Disk Space allocations after creating a VM? I've read that changing the CPU count can cause issues in a VM. I'm not sure about disk space.

What's a good size for my system partitions on the server? If I set up a separate partition for file storage on these VM's, can they be set to grow as needed?

LVL 16

Expert Comment

by:Jon Brelie
ID: 33638892
Growing a disk is easy.  Shrinking it, not so much.  Never had an issue with changing around CPU numbers.

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 33639697
Couple points:
1. For the VMs disk, always set it to use the real space and NOT to grow as needed. The main reason for NOT thin provisioning the disks (this is the correct term) is to avoid a possible issue where the server (host) runs out of disk space and in that case the VMs simply crash AND with a real chance of MAJOR corruption. So if you allocate 50GB to a VM, make sure you allocate the REAL 50GB when you create the VM.
2. Windows 7: several people mentioned 2vCPUs and at least 2GB RAM are required to make it run smoothly (follow @RonOglesby on Twitter).
3. I would start the RDS with 2 vCPUs and 4GB RAM.
4. Not sure what you are doing regarding disaster recovery in this case but with a single server, if it dies, ALL your VMs are dead. I would definitely considering a redundant setup, unless your business is ok with being with no computer access for a couple hours until you get all up and running again.

Cláudio Rodrigues
Microsoft MVP - Remote Desktop Services
Citrix CTP
LVL 16

Expert Comment

by:Jon Brelie
ID: 33640781
Actually thin provisioning is incredibly powerful in environments where you have multiple ESXi hosts and multiple storage paths.  IE, I can put a 600gb server thin provisioned on 300 gb worth of disk while I perform maintenance on the original host.

Granted there IS the possibility of over-provisioning, but good documentation and accurate reporting can overcome this problem.  I thin-provision everything.
LVL 31

Assisted Solution

by:Cláudio Rodrigues
Cláudio Rodrigues earned 800 total points
ID: 33641327
As in the Spiderman movie, "with power comes responsibility" and for that reason Thin provisioning, in some environments, may lead to HUGE disasters (and I have seen this happen first hand). :-)

This thread is a good one to read:

There are for sure drawbacks and it will indeed cause performance issues depending on the environment. May not be the case here at all but it is worth reading.
VMWare's take on it:

Cláudio Rodrigues
Microsoft MVP - Remote Desktop Services
Citrix CTP

Author Closing Comment

ID: 33758103
thanks guys, i have everything up and running now. i love it! I'm running 3 Server 2008R2, one Win7 and one WinXP and everything is FAST! :-D I only gave XP and Win7 1GB RAM each and they seem ok.

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question