This is timely. THanks

Good read and it explains very clearly what split-brain is, and how to prevent it in simple enough terms. I've had to explain many times myself what split-brain is and ways to prevent it. I just get starred at. . .

@oksana said in How many IOPS your NVMe can do? All of them!: There’s a common opinion that the performance in general and IOPS-intensive performance like NVMf [NVMe over Fabrics] is usually lower in virtualized environments due to the hypervisor overhead. Check out this article to prove or knock down this belief! Great, now I'm impatient to see the results!

@oksana said in Accelerating your IT environment to new speeds with StarWind iSER: @travisdh1 Yes, PFC for switch and RDMA support for Ethernet So, yes, it does require a few things, but things that should be available already. Great!

@travisdh1 I'm surprised too, but I guess. I think they're probably counting things like rogue USB devices left lying around and such as part of the malicious group.

@r3dpand4 said in Configuring Multi-Resilient Volume with Storage Spaces: Should be noted that any server running 1709 cannot be added to S2D pools as it stands currently since it's not considered production ready.... Correct. S2D is gone from non-GA WS2016. https://docs.microsoft.com/en-us/windows-server/get-started/server-1709-relnotes Storage Spaces Direct Storage Spaces Direct is not included in Windows Server, version 1709. If you call Enable-ClusterStorageSpacesDirect or its alias Enable-ClusterS2D, on a server running Windows Server, version 1709, you will receive an error with the message "The requested operation is not supported". It is also not supported to introduce servers running Windows Server, version 1709 into a Windows Server 2016 Storage Spaces Direct deployment.

good article thanks and handy script

Is that different than hardware defined storage? It has all those issues, too.

Also, in the followup post on the blog they actually do another interesting lab that requires this first bit.

@darek-hamann said in Configuring Windows Server 2016 Core. Part 2: Hyper-V role installation: @dashrender This is actually a great article! It simplifies the procedure of installing a Hyper-V role from a GUI free Windows 2016 Core setup. That's nice, but again - WHY. This is not the way you should NORMALLY install Hyper-V because now you have a license tied to the hardware. I get that there are reasons, but I'm asking what they are.

That's a very good post that covers information people don't often think about after deploying vCenter. Additionally, it's something helpful when studying for the VCP-DCV. Thanks for sharing!