To Virtualize or not to virtualize, that is the question

Posted on 2012-03-23
Last Modified: 2012-04-25
So lately, I have been getting more familiar and putting VMware into production at our sites.  With all of the benefits of VM's I am curious as to what downfalls there are?

For instance, having a VM makes it easy to take snapshots for patching, moving or migrating to new machines by just moving the system disks, and of course the ability to run a couple of servers off one box.

Am I missing something by having everything entirely running as VM's?  I simply think the fact that backing up the disks and having the ability to run them on a new machine is the easiest form of Bare Metal Restore there is.  Booting them to different devices is never as much of a headache as when trying to migrate a physical server to a new box.

If anyone has any caveats, please share. Thanks!
Question by:jhuntin
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
  • 2
  • 2

Expert Comment

ID: 37758531
I have been using VMWare ESX for several years in our production envirnment.  One of the strengths is also something to be careful about.  It is very easy to add new servers in a virtual environment.  Being able to add new servers without needing to add additional hardware is a huge plus.  

However, you will need to be careful to fall fall prey to server sprawl.  If you are not paying attention, you can fill up your hosts with new VMs.  This can cause problems with licensing for the OS, and using all of the spare capacity of your hosts.  If you have no spare capacity, then you will not be able to vmotion your VMs from a failed host.  This will prevent your high availibility expectations from being met.  Also, if you have used all your spare capacity with VMs of questionable value, then you will not be able to add another VM for an important project.  This could put that project behind schedule while waiting for additional hardware to be purchased and installed.

You could also be tempted to use your production system for testing servers.  You will need to take care to be sure to isolate your test systems/networks from your production systems.  You don't want a test server using all of your I/O and affect your production servers.

All in all, virtualizing your production environment is a great boon to IT departments the world over.  You just have to pay attention to what you do with the system and to not go overboard.
LVL 121

Accepted Solution

Andrew Hancock (VMware vExpert / EE MVE^2) earned 333 total points
ID: 37758562
DR is easier with virtualisation.

Biggest downfall is the single point of failure, all eggs in one basket scenario.

Most haveva single SAN, what do you do it it fails!

Design out the single point of failure and you will be fine.

Assisted Solution

awaggoner earned 167 total points
ID: 37758601
Agreed about single points of failure.  You don't want dozens of servers failing because one power supply goes out.

Spend the extra money to have redundant systems.  It will still cost less than buying all of the hardware for stand alone servers anyway.

Make sure you have enough spare capacity built in to survive the failure of any single point.  If you can't afford multiple SANs, then you can still configure your SAN with redundant power supplies, controllers, RAID w/ hot spares, network connectivity, etc.
LVL 121

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 333 total points
ID: 37758661
It does not matter if you have good quality SANs, last year we had 8 Clients SAN fail!

And one SAN was an HP EVA cost £250k, design in good resilience, DR. Design out the simgle points of failure, design and test DR, Invoke DR and test.

One business out for 18 hours until recovery, this is the scary side of virtualisation.

Use VSA technology with replicated volumes, e.g. HP Lefthand etc

Featured Post

Portable, direct connect server access

The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

Question has a verified solution.

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

In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
In this article, I will show you HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, using the VMware Host Client. The virtual machine has Windows Server 2016 instal…
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

617 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