Skip to main content

VMware Converter: How I saved my production environment from embaressment!



This is true story , by the way:

We had a couple of old servers responsible for login details for over 50,000 users!!! And it all runs on a NT4 sp5 OS. The hardware is also pretty old. REALLY OLD!!!

My Network Admin had been complaining about it for a long time. They have saved the day in the past by rebooting the machines (with fingers crossed , hoping that the hardware wouldn't die out on them!).

Anyways I approached them and...Hang on lets catoonify all that happened. No special kernel tales here, sorry. Plain execution!!!










So we:
  • Converted the Machines
  • Ported them to the ESX Lab
  • and we plan to keep it running on our "new & shiny" hardware as redundant copy of production
Motto Moral of the story is:

All mission critical systems are not prominent and maybe hidden in your organization. Don't get that impression that a system you need to virtualize is large and huge. So start virtualization with a mission to get a grip on your processes!

Comments

  1. How did you convert physical nt4 sp5 without upgrading to sp6a ?

    ReplyDelete

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!