Each virtual machine (VM) is a collection of resources provided by the infrastructure layer, usually organized in a pool of resources and assigned dynamically (or in some case statically) to each VM. VMs “see” a subset of physical resources in a form of virtual hardware components defined usually by the certain minimum elements. Adding hardware components can be useful in some cases, or they can be necessary for performing some basic operations, like, for example, installing the guest OS where a video driver, a keyboard and a mouse device are needed to use the remote console. That is why you should be aware of which hardware resources can be hot-add and which hot-remove.

Building a virtualized environment with VMware Workstation is a bit different from the scenario discussed before. Today, I use VMware Workstation 15 Pro – a virtualization platform that supports hypervisor virtualization and allows administrating small VMware infrastructures. Yes, Workstation is a vCenter-like platform, but it has rather limited functionality. Anyway, it allows building a vSphere lab for free! This being said, the solution is good for this article.

While writing my previous article, I remembered the days when I was only building my first lab. It was a bit tough, you know, as vSphere yet was a black box for me. Those thoughts brought me to the idea of writing this article. The article in which I share my know-how of building a minimalistic lab using… only a PC, switch, and laptop. I’ve divided this topic into 2 parts as I am unsure whether you guys like long-reads. In this part, I discuss how to build an ESXi environment using PC and ESXi 6.7 U1. The next article addresses creating a lab using PC and VMware Workstation 15 Pro. I hope that both of them will be really handy for you!

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. It’s rather a long process, and you need to pay your dues sometimes. Honestly, I got some knowledge only through fixing things that I had messed up. This post covers some questions that popped out in my head when I was only starting. And, my case is not unique. So, let’s start with VMware!

Microsoft has recently released Windows Server 2019 Insider Preview Build which is the latest release of Windows Server vNext LTSC (Long-term servicing channel). This update contains Desktop Experience and Server Core in eighteen server languages. Also, it includes an English Windows Server Semi-Annual Channel release. And, that’s not all: the build includes the first Microsoft Hyper-V Server preview. In today’s post, we will talk about what to expect from this build, its known issues, and terms of use.

What is RDMA and why do we like it.

What was a privilege of enterprises just a few years ago, now becomes a common thing for companies of all sizes – I’m talking about cloud. The number of cloud storage providers grows, delivering various solutions that fit the needs of different organizations in terms of features and prices. Moreover, the competition in the cloud market is getting tougher, making cloud storage providers cut their prices just to stay afloat. Therefore, cloud becomes a really great alternative to purchasing more physical storage or compute resources to maintain data and applications. However, despite there is a wide range of cloud offerings, we still struggle with choosing a cloud provider that offers us storage we need without charging us a steep price in the end of the billing period. So today, we’ll have a closer look at some public cloud providers to decide on the cheapest storage.

Companies often store critical client mailbox data on an Exchange server database. The Exchange database is a warehouse of critical mailbox information such as contacts, notes, calendar items and emails of thousands of users. One of the most serious issues companies can face is the corruption of the Microsoft Exchange 2013 database file leading to unavailability of important data for the client. The Microsoft Exchange 2013 database can become vulnerable to crashes due to unavoidable hardware issues, software malfunctions, system freezes, server or boot failures, accidental shutdowns or any unforeseen circumstances. Since the last thing a company wants is to endanger business goals such as data availability during disasters, the first step is to make efforts to recover the damaged file.

So, we all know about Microsoft’s Storage Spaces Direct (S2D to put it simple) by now. It’s the feature introduced in Microsoft Server 2016 (Datacenter Edition) that pools together server’s storage allowing to build…that’s right: highly available and easily scalable software-defined storage systems. In this article, I’m gonna talk about not as much about its fault-tolerance characteristics themselves, but some hands-on experience, namely: how to replace a failed disk.

Plenty of articles have been released about Storage Spaces and everything around this topic. However, I would like to absorb all actual information and lead you through the journey of configuring Storage Spaces on a Standalone host. The main goal of the article is to show a Multi-Resilient Volume configuration process. In order to use Storage Spaces, we need to have faster (NVMe, SSD) and slower (HDD) devices. So, we have a set of NVMe devices along with SAS HDD or SATA HDD, and we should create performance and capacity tier respectively.