VMware vCenter Site Recovery Manager has been introduced back in 2011. It is a VMware vCenter plug-in for disaster recovery site configuration and management. It also allows migrating to that site at the moment of need or during planned migrations. In other words, SRM ensures shortest services downtime if something goes wrong at your main site. Please, don’t count on that thing that much since there will be insignificant time losses anyway.
Sometimes, you badly need to provide your VMware VMs with more RAM or vCPUs without shutting them down. True, there’s a trick allowing you to do that – CPU Hot-Plug and Memory Hot-Add. In this article, I’ll discuss both these features and how to use them in different environments.
If you are new to VMware or just starting out in the tech, you may feel a bit confused about products naming. Well, at least I was. There are tons of products in the suite so many have a hard time grasping how all those things come together. For instance, it may be hard for a beginner to tell apart ESXi and vSphere. What should you do? Well, nothing special, you know. Google. Ask fellow admins. Look through forums. Read books. Well, my post is not here to bring you from the very beginning to finish.
A couple of days ago, I decided to re-distribute VM resource shares. I, basically, wanted several VMs to get some more resource without compromising their latency. For that purpose, I played around with Storage I/O Control parameters a bit. And, you know, I decided to look at things more globally. Actually, here’s how I decided to take a deeper dive into I/O filtering. In today’s article, I’m going to tell you about the VMware vSphere APIs for I/O Filtering (VAIO) framework providing the direct access to the to the VM I/O stream. I shed light on how to enable those filters, how they work, and why you need them.