If you are thinking about using VMware, you should read this article first. Unless the software you plan to use is specifically optimized for more processors, the system will slow itself down.
Whether you're a seasoned IT veteran or just starting out in tech, there's a lot to know about VMware. Especially if you're working a full-time job, it's easy to feel overloaded and overwhelmed.
Mistakes are also part of the game, no matter how prepared you think you are. However, if you avoid these three major traps that many novices fall into, you'll be on a better track towards success.
1. More Doesn't Mean Better
This is one of the more common mistakes that you might make when transitioning into VMware, because you're applying logic based on previously held assumptions that doesn't work the same way with VMware technology. Many VMware Junior admins like yourself are assigned to pump out more performance to meet quarterly goals.
In order to achieve the performance goal, you might think that you simply need to add more power to your systems, whether that translates to video cards, memory, or Central Processing Units (CPUs) for server systems. You might think the same rule applies when addressing power limitations on a virtual server. However, after adding more Virtual CPUs (vCPUs) to your system, you're actually seeing performance drop significantly. How can this be the case?
Instead, what you should be doing is scaling out what you do have over more Remote Desktop Services (RDS) servers and also create virtual CPUs and memory. By adding more vCPUs, what you're actually doing is preventing the virtual machines from using the vCPU correctly. By assigning more cores (via more processors) to the virtual machine, the VMware scheduler has to wait until those cores are "free", thereby pausing these cores and slowing down your overall performance.
Unless the software is specifically optimized for more processors, the system will slow itself down. You should instead start by assigning one vCPU to the machine, then slowly increase until there is a performance hit, at which point you should scale back.
2. Relying on Snapshots for Testing
Sometimes when you're trying to avoid making simple mistakes, you can often just end up making different mistakes altogether. Let's say you need to implement a new patch for the version that you have. You're no doubt thinking of a way to test the patch without messing up your virtual machine.
Perhaps in your mind, the quickest way to do that is with the VMware snapshot feature. This allows you to essentially create a picture (or snapshot) of a moment in time from your virtual machine. That way, if something breaks while implementing the patch or new version, you can go back to that moment in time and unfreeze it, as though the problem never happened.
The problem is that these snapshots are not true backups of your system. While taking a snapshot can be used effectively in certain instances, complications can arise when this becomes the go-to procedure for testing. Because the virtual machine will be running slower on the snapshot, the updates will take longer to process. Plus, after it's done processing, merging the files in order to delete the snapshot will often end up taking hours to complete. This is not an efficient process.
Instead, make a full clone of your virtual machine to act as a backup before you start running updates. If there happens to be an issue during the process, you can simply destroy the machine, rename the clone, and restart it. If the update is successful, you can simply delete the clone without waiting hours to complete the merge. It's safer for your system, and faster as well.
3. Installing ESXi on the Local Disk
Just as it may seem obvious to add more physical CPUs to increase the performance, you may think that the local disk is the best place for installing your first Enterprise Class (ESXi) whitebox. Though it may seem like a more secure location than a flash drive, it actually takes up a fair amount of space on the disk that you should reserve instead for the virtual machine datastores.
There are a number of different reasons why a flash drive works better for the ESXi install. First, it does save space. Since the flash drive is only used to boot up the ESXi OS before it switches over to the memory resident, there's no need to waste the space on the local disk. Second, having it on a flash drive makes it easier to backup or replace if something were to happen, rather than wiping the local disk and starting from scratch. Make sure to use a high quality flash drive, however, and follow the correct steps when booting from the drive.
The Next Step: The Experts Exchange Community
The life of a VMware novice isn't easy, but there is help out there. Experts Exchange is backed by the oldest and strongest technology community in the world. As a VMware professional, you will be required to work with many technologies beyond VMware, from operating systems to storage area networks. One of those professionals, Andy Hancock, is one of the top 25 vExperts in the world, and has many tutorials for novices. Check out the rest of his highly rated content through the community.
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging
Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…