| By Denny Lane | Article Rating: |
|
| October 24, 2008 05:15 AM EDT | Reads: |
1,959 |
Flexible, fluid, and fast-evolving, software has regularly outstripped the capacity of the hardware it runs on, which by its nature is more rigid and slower to change. For most computer users that difference might mean occasionally sluggish performance or an inability to use certain features, depending on what hardware/software combination they're using. When the software intelligence in question is virtualization, however, the stakes are much higher.
Since virtualization's foundational benefit is to operate multiple application servers on each physical server, virtualization gradually reintroduces single points of failure back into the IT infrastructure years after server-based architectures
minimized them. Distributed server architectures resist complete system failure by running critical applications on discrete physical servers. Server crashes could only take out one or two critical resources at a time, which is why distributed environments could tolerate servers' low reliability compared to the mainframes and minicomputers they replaced. The ensuing data center sprawl, however, brought server architectures full circle through virtualization. With five, six, seven, or more critical applications and databases on a single server, virtualized IT environments are even more vulnerable to catastrophic crashes than mainframe-minicomputer environments because they have the same concentration of resources but not the same hardware reliability.
None of this is any reason to shelve virtualization strategies, of course. Virtualization's benefits are too significant to ignore. Corporate IT managers have aggressively embraced virtualization to rein in data center sprawl. Almost 80% of companies surveyed by the Yankee Group are using some kind of server virtualization technology, and 85% of the money spent on virtualization software went to server consolidation projects. Implementing several virtual servers on a single physical server raises utilization rates from an average of 10% per box to as much as 80%, according to the Yankee Group's 2007 report on server virtualization. Virtualization's entrance didn't come a moment too soon, for image-conscious companies, either. Quoting a McKinsey & Co. study, the New York Times predicted that at their current pace, data centers will be the biggest producers of greenhouse gasses by 2020.
To realize its full potential, virtualization must go hand-in-hand with reliability strategies that consider its few weaknesses and address them with the right hardware and management tactics to reduce them.
No Built-in Virtual Reliability
Reliability and business continuity aren't front-of-brain in a virtualization discussion. Part of that omission can be attributed to virtualization's nature. The ease of setting up multiple application servers in a virtual environment can make virtualization look like its own reliability strategy. Implementing backup copies of applications on virtual servers means there's a copy in place and ready to go in case of a server crash. With backups ready to go, IT need never be caught flat-footed in the event of an application crash.
Published October 24, 2008 Reads 1,959
Copyright © 2008 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Denny Lane
Denny Lane is director of product marketing and management at Maynard, Mass.-based Stratus Technologies.
![]() |
mikedatl 10/22/08 02:03:16 PM EDT | |||
Fault tolerant servers are nice and some applications do warrant that. However, the VAST majority of applications running in a x86 environment can tolerate being down for 2 minutes which is as long as it takes for HA services built into most virtualization offerings to reboot the VM on another system with available resources. Built-in HA is available from all of the leading virtualization providers and covers 98% of your applications. For stuff that needs even more reliability with no downtime you have fault-tolerant servers from Stratus (which the author happens to work for) as well as the upcoming VMware FT (fault tolerance). Yes, I work for the later company. The point is to know your app first and know what you want for downtime. You'll find that most apps out there are just fine with a quick reboot if appropriately setup. |
||||
- Seeding the Cloud: The Future of Data Management
- Economy Drives Adoption of Virtual Lab Technology
- How PowerBuilder Got Its Groove Back
- PowerBuilder 12 .NET Review
- Will Cloud Computing Confuse Network Management?
- Are We Close to the Saturation Point for iPhone Apps?
- PowerBuilder UI Designer
- How to Create a Web-Architected PowerBuilder Application
- Is the Ladder We’re Climbing Resting on the Wrong Wall?
- Telcos Will Rule Cloud Computing in 2010 -Yankee Group
- The Real Cost of Passwords
- Online Training for PowerBuilder 11.5
- Why SOA Needs Cloud Computing - Part 1
- The Transition to Cloud Computing: What Does It Mean For You?
- Seeding the Cloud: The Future of Data Management
- Economy Drives Adoption of Virtual Lab Technology
- How PowerBuilder Got Its Groove Back
- A Rules Engine Built in PowerBuilder
- PowerBuilder 12 .NET Review
- Will Cloud Computing Confuse Network Management?
- Are We Close to the Saturation Point for iPhone Apps?
- PowerBuilder UI Designer
- How to Create a Web-Architected PowerBuilder Application
- Is the Ladder We’re Climbing Resting on the Wrong Wall?
- Where Are RIA Technologies Headed in 2008?
- PowerBuilder History - How Did It Evolve?
- The Top 250 Players in the Cloud Computing Ecosystem
- Custom Common Dialogs Using SetWindowsHookEx
- DDDW Tips and Tricks
- OLE - Extending the Capabilities of PowerBuilder
- DataWindow.NET How To: Data Entry Form
- Working with SOA & Web Services in PowerBuilder
- Sybase ASE 12.5 Performance and Tuning
- Book Excerpt: Sybase Adaptive Server Anywhere
- Office 2003 Toolbar: A New Look For Your Old PowerBuilder App
- Dynamically Creating DataWindow Objects


























