5 Ways to Know You’re Ready for Virtualization

You've heard the hype, now it's time to measure if you really need to jump into the virtualization fray.

To help you avoid those opportunists who jump on new technologies like cockroaches pouncing on freshly fallen cake crumbs—gobbling up the sweet bits and running off into the dark when the lights come on, I’ve compiled 5 simple questions to ask yourself before taking the plunge. Remember all the “sky is falling” Year 2000 experts who convinced you to upgrade, replace, and heavily invest to rid yourself of this virtually (no pun intended) non-existent bug? Some of them are back as virtualization experts and this time they’re out for the rest of your blood. Giving blood voluntarily is a good thing but having it sucked from you by these buzzword-spewing, virtual vampires is painful and expensive.

Here are the 5 questions for you to answer before you voluntarily give up your virtual blood and valuable cash.

1. Is your current computing infrastructure (Servers, Storage, and Desktops) ready for a refresh?

If you bought all, or most, of your current hardware at the time and it’s been somewhere between 3 to 5+ years ago, you are a prime candidate for virtualization.

Instead of making a new investment in short life span hardware, make the leap into virtualized infrastructure and allow those dollars to stretch farther into the future. Increase the overall life of your computing infrastructure by investing in Blade server technology that is scalable and extensible. You’ll alleviate the need to rip and replace hardware every few years with this new technology.

2. Do you support a central location and satellite locations or remote users?

With broadband Internet connectivity and thin client hardware, you can significantly decrease remote support costs through virtualization. Keep your support centrally located with that virtual infrastructure while your remote users enjoy a relatively maintenance free environment. The money saved on support calls and downtime for remote users will more than compensate for initial cash layout for new hardware.

3. Do you have hardware, regardless of its age or condition, that is underutilized?

Simple performance tools exist to measure average utilization for your server systems—use them to get a quantitative analysis. Virtualization takes those underutilized systems and consolidates their workloads onto leveraged hardware and virtual machines. Server consolidation is the most often cited reason for server virtualization. Those underutilized systems use electricity, require cooling, need regular maintenance, and are probably costing money in vendor service contracts. Move those underutilized physical systems to virtual ones.

4. Are you spending too much money on desktop support?

If you’re spending more than 50% of the original desktop computer cost for maintenance and break/fix issues, you’re a good candidate for using virtualized desktops (VDI) or terminal services. Using thin client terminals and virtual desktops or terminal services, your desktop support maintenance will decrease. Most thin client hardware has no moving parts, which removes a large number of support calls for failed hardware issues. By moving to a virtual desktop solution or by using terminal services, you also decrease support issues related to viruses, rogue software installation, pirated software, spyware, and other user-induced software problems.

5. Are backup and restore issues driving you crazy?

Most companies develop disaster recovery plans after a disaster occurs. Fingers point in every direction and arguments ensue often ending in either job loss or creating strained working relationships between groups or departments. Virtualization doesn’t remove the need for backups but it does rid administrators of the constant battle for network bandwidth for those backups. Various backup methods are available for virtual machine infrastructure that requires no over the network traffic: Disk to disk backups, snapshots, and V2V (Virtual to Virtual) copies are some of the possibilities.

A ‘yes’ answer to any one of these questions may provide the impetus you need for the decision to pursue a virtualized infrastructure solution but a ‘no’ answer to all of them means you should seriously reconsider the move. Beware of anyone who has all the answers but asks you no questions—whether or not you see the fangs; you’d be wise to show them the door and not your neck.

Comments on "5 Ways to Know You’re Ready for Virtualization"



As one of those who spent nearly a decade in the trenches preparing for that “non-existent bug,” more aptly called a serious lack of forethought, I take serious umbrage at your flippancy.

While the NSF policy of replacing all their stuff that was not provable as Y2K compliant was ridiculous (A VCR with no year field in its clock, for instance, is inherently any-year compliant; fortunately they didn’t toss all their furniture and dishes as well) there were some extremely serious issues to be resolved.

I’ll grant you that there was a great deal of pontificating, and that the depredations of the “experts” are hard to overstate, but the blokes behind the scenes were, are and deserve better than a casual dismissal.

That Y2K was not the End of all Civilisation was not the proof of a negative (a logical impossibility) that you make it out to be, but rather was the result of countless person-years spent mitigating it.

We did our part, and we did it with little thanks, no impressive memorials erected in our collective honour and with the ignorant laughing in our faces.

Please laugh in some other direction.

Russ Bixby, Curmudgeon of the plains.

“Why is there an expiration date on buttermilk?”


I’m not being flippant to those of you who mitigated the problems nor to those who caused them with their naive short-sightedness. I am being so toward those who read a few articles or hyped-up books about the subject and became experts–touting their knowledge about what is and is not Y2K compliant. One such expert told us not to get on any elevators on Jan. 1, 2000–I sighed heavily and left the room.

I actually owe much to those of you who worked tirelessly on a solution–and to expiration dates on buttermilk.

Speaking of oxymorons–What do you call a bad lemon?


I accept your clarification, with the stipulation that such clarification was indeed required.

That said, I do apologise for my thin skin on this subject. I took a Hell of a lot of ribbing on 1st January 2000 and have taken much since, and it does eventually wear one down.

Ah, well; nusquam licitum inritus irritus attero.


Zen network engineer: “What’s the bandwidth of localhost?”

Thank you for the good writeup. It in fact was a amusement account it. Look advanced to more added agreeable from you! However, how could we communicate?

Leave a Reply