Skip to main content

Virtualisation in the server space

Recently I've had the chance to view VMWare ( and HP's ( entries in the virtualisation market - through VMWare's ESXi server and HP's Blade servers and SAN systems. Prior to this presentation I'd only looked into virtualisation a little bit, concerns for server redundancy and the like preventing me from spending a lot of time looking into it, and also, the size and scope of the organisation I work for is insufficient for such things - or so I had thought.

I have about 10 servers under my direct control and of these, 6 could be virtualised. Thinking about it going forward, in 3 to 5 years when these servers are due for replacement, buying 2 servers and a small SAN will cost less than the 6 new servers and provide the same services. At the end of the day, I think that's what it is all about - same services (or better), with uptime being up in the 5 nines range and cost-effective hardware/software. I've been a fan of VMWare's virtualisation stuff for several years, solely through the VMWare desktop range. Running multiple operating systems and applications on a single development machine was lots of fun. Back in the day (5 odd years ago) RAM was pricey and so was disk space so the VM's were pretty little.

Now you can run whole server instances in a file and then slip that file between servers depending on load requirements and whatever other fancy things you want to do - such as bringing one physical server down for updates and maintaining all your VM's on another server. Absolutely amazing stuff - especially when you combine it with blade technology and have dozens of servers sharing one big SAN all in the same rackspace. Truly incredible. Pretty complicated too I think as well, remembering where everything is going.

The new Blade servers from HP look very impressive too - they've done a lot of work on cooling and on cabling and everything is redundant with backup from at least one module exactly the same. Of course, when I saw those big fancy Blade servers I thought to myself - why virtualise? You could have a netboot install of a server ready to rock at a moment's notice and be back up and running in a very short time, especially if you combine the server with Microsoft's ASR technology and tape backup. There is so much chance for overkill it's every enterprise geek's wet dream. There were quite a few geeks at the presentation that looked like they were in their happy place that's for sure.

The most important thing I took away from it all was that virtualisation in the server space has come a long way since I last looked into it and the offerings from both VMWare and HP are quite spectacular. Given my quite low funds though - I'm now looking into Linux's XEN virtualisation. If you're more interested in this (any virtualisation for that matter) there is a lot of stuff on the interwebs. Mind you don't clog up your tubes! :-)


Popular posts from this blog

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years. These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful. The first one to be reviewed was OpenKM ( ). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgradin

Musings on System Administration

I was reading an article discussing forensic preparation for computer systems. Some of the stuff in there I knew the general theory of, but not the specifics of how to perform. As I thought about it, it occurred to me that Systems Administration is such a vast field. There is no way I can know all of this stuff. I made a list of the software and operating systems I currently manage. They include: - Windows Server 2003, Standard and Enterprise - Exchange 2003 - Windows XP - Windows Vista - Windows 2000 - Ubuntu Linux - OpenSuSE Linux - Mac OSX (10.3 and 10.4) - Solaris 8 - SQL 2005 - Various specialised software for the transport industry I have specific knowledge on some of this, broad knowledge on all of it, and always think "There's so much I *don't* know". It gets a bit down heartening sometimes. For one thing - I have no clue about SQL 2005 and I need to make it work with another bit of software. All complicated and nothing straightforward. Irritating doesn&

Traffic Monitoring using Ubuntu Linux, ntop, iftop and bridging

This is an update of an older post, as the utilities change, so has this concept of a cheap network spike - I use it to troubleshoot network issues, usually between a router and the network to understand what traffic is going where. The concept involves a transparent bridge between two network interface cards, and then looking at that traffic with a variety of tools to determine network traffic specifics. Most recently I used one to determine if a 4MB SDSL connection was saturated or not. It turned out the router was incorrectly configured and the connection had a maximum usage under 100Kb/s (!) At $1600 / month it's probably important to get this right - especially when the client was considering upgrading to a faster (and more expensive) link based on their DSL provider's advice. Hardware requirements: I'm using an old Dell Vostro desktop PC with a dual gigabit NIC in it - low profile and fits into the box nicely. Added a bit of extra RAM and a decent disk and that&