Solved

To Virtualize or not to virtualize, that is the question

Posted on 2012-03-23
4
354 Views
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!
0
Comment
Question by:jhuntin
  • 2
  • 2
4 Comments
 
LVL 6

Expert Comment

by:awaggoner
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.
0
 
LVL 118

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE) 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.
0
 
LVL 6

Assisted Solution

by:awaggoner
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.
0
 
LVL 118

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE)
Andrew Hancock (VMware vExpert / EE MVE) 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
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

HOW TO: Upload an ISO image to a VMware datastore for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere Host Client, and checking its MD5 checksum signature is correct.  It's a good idea to compare checksums, because many installat…
In this article, I show you step by step with screenshots to assist you - HOW TO: Deploy and Install the VMware vCenter Server Appliance 6.5 (VCSA 6.5), with some helpful tips along the way.
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:

932 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

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now