Want to unleash the full potential of your Hyper-V environment? Uncover straightforward tips to optimize performance, covering Windows Server adjustments and efficient VM strategies.

Explore storage protocols with our performance benchmarking series! In Part 1, we configured NFS, and now, Part 2 dives deep into iSCSI configuration. Which protocol is your best fit for virtual infrastructure?

In the world of virtualization infrastructure, NFS and iSCSI are the contenders. NFS brings simplicity and scalability to the table, while iSCSI boasts performance and reliability. Which one suits your mission-critical applications? Let’s find out!

Every admin knows that maintaining all the local area networks within an IT environment manually is a major headache. Fortunately, there are multiple ways to remedy that by automating a number of functionalities, one of which is command-line shells.

The previous comparison of file and block VM storage focused specifically on the SMB, NFS, iSCSI, and NVMe-oF protocols. Now, it’s time to compare these storage types in the context of Microsoft’s Hyper-V environment!

Dive into the world of VM storage in Windows Server Hyper-V! Discover the differences between file and block storage protocols, and their impact on VM performance. From SMB3 and iSCSI to NVMe-oF, learn which protocol suits your needs best.

Managing an IT environment is impossible without a reliable backup and recovery plan that must include a robust storage option.

Software and feature licensing is often complex, requiring in-depth expertise to be licensed correctly and efficiently. Microsoft ecosystem is no exception.

While some OS-s built on Linux kernel support NVMe-oF, Windows just does not. No worries, there are some ways to bring this protocol to a Windows environment! In this article, I investigate whether presenting an NVMe drive over RDMA with Linux SPDK NVMe-oF Target + Chelsio NVMe-oF Initiator provides you the perfomance that vendors of flash list in their datasheets.

Virtualization of your work servers is a necessary action, but the problem is when you do that, you basically put all your eggs in one basket. Let’s imagine that your Hyper-V host with several VMs on it requires rebooting. Well, in that case, you won’t be able to boot a specific VM until the host OS is restarted, and all VMs are booted. And there’s no guarantee they will be available after that! Now, that surely doesn’t sound too good. However, luckily there are ways to make this process less painful and more efficient.

While configuring Hyper-V host, you’ll have to be able to boot your VMs in a specific order. I gotta admit, even though it took me a while to figure out how to customize this process, I have some results for you.
Mind, even if your server OS isn’t prone to failure, it’ll still be wise to configure Hyper-V automatic start action for VMs. One way or another, someday, you’ll have to reboot your server. So, when such a reboot occurs, it would’ve been nice if you didn’t have to boot ever separate VM manually, don’t you think so?