I'm not a sysadmin—I work mainly with IoT and automation—but our company recently lost several virtual machines after multiple hard drives failed. The surviving backups were months old, so we also lost recent Docker containers, databases, scripts, and SCADA projects.
While investigating, I noticed that the virtual machines appeared to be using VMware Workstation. I had assumed production environments would normally use a server-focused hypervisor such as ESXi, KVM/QEMU, Hyper-V, or Proxmox. Is running VMware Workstation—or even VirtualBox—on a production server common in small or legacy environments? Could using a type 2 hypervisor contribute to instability, or are the much bigger problems here the lack of storage redundancy, monitoring, and current backups?
5 Answers
No, VMware Workstation is not a normal choice for production server virtualization. It’s primarily intended for desktop development, testing, labs, and occasionally specialized operational technology setups where an old application has to be preserved on a newer host. Production workloads should generally run on a platform designed for servers, such as ESXi, Hyper-V, KVM, or another dedicated hypervisor.
VMware Workstation is commonly used on developer or engineering PCs to build and test images before moving them to a server virtualization platform. It also appears in industrial and automation environments when legacy Windows machines or vendor-supplied VM images need to keep running. Those are exceptions and workarounds, not evidence that it is a suitable general-purpose server platform.
This kind of arrangement does show up in SCADA and other industrial systems because old Windows versions, vendor software, and specialized hardware can be difficult to replace. In that case the system should be isolated, documented, monitored, and backed up carefully. Treating a desktop host with individual disks as the company’s only infrastructure is the dangerous part, regardless of whether the hypervisor is type 1 or type 2.
The hypervisor choice probably wasn’t the main reason everything was lost. Workstation can be reasonably stable, but it doesn’t compensate for poor infrastructure design. The serious issues are the failed drives without adequate redundancy, backups that were months out of date, and apparently no alerting when backups stopped working. RAID, monitoring, tested restores, and at least one separate or off-site backup copy should be priorities.
Be cautious about identifying the product solely from a VM’s MAC address. VMware uses different address ranges in different products and configurations, but MAC addresses can be manually assigned, changed, or affected by how the virtual networking is configured. Confirm the hypervisor directly from the host and its management tools before drawing conclusions.
Even if the host is definitely running Workstation, the storage and recovery design still need to be investigated separately. Moving the VMs to a server hypervisor may improve management and availability, but it won’t replace a proper backup and disaster-recovery plan.
Small businesses do sometimes end up with setups like this, especially when an engineer or developer gradually takes on infrastructure work. That makes it possible, but not a sound standard.