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!
Labels:

Comments

  1. AnonymousWed Sep 05, 02:30:00 PM GMT+2

    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
Post a Comment
Read more

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...
Post a Comment
Read more