The hyper-v.io blog was acquired by StarWind Software, Inc. on March 1st, 2023.
We are currently reviewing the content of the blog, but please note that any opinions expressed before the effective date of the acquisition are solely those of the original owner(s). We will not provide any comments or opinions on the previous content. You are welcome to post comments on the original posts, but we are not obligated to respond to your inquiries.
StarWind has set hyperconvergence performance record. Let’s get behind the scenes
Hyperconvergence has dramatically transformed data center landscape over the past few years. New technologies are being developed, good old ones are being improved… We live in exciting times! And as data centers are becoming more reliable and powerful, it is important to get more out of the hardware in use: nobody likes to leave money on the table! Intel, Mellanox and StarWind have teamed up to develop a Hyper-V highly available cluster where you’ll get awesome performance without compromising ease of manageability of the environment. This article discusses the measurements in brief, showcasing the recent results.
How is NVMe-oF Doing? Part 4: “Who’s the fastest hand in the West”?
It is the fourth part of my NVMe-oF Initiators’ performance study. Before, I tested NVMe-oF initiators developed by Linux, Chelsio (LINK) and StarWind (LINK). Here, the battle ends: which NVMe-oF initiator delivers the highest performance and which one Windows admins should use?
I’m leaving the blog to my friend Dmitriy. Bohmer’s farewell post
I have to stop blogging because my wife gives birth soon, so I want to spend more time with my family rather than at my office or lab. Maybe, I’ll start writing again someday, who knows.
Configuring Time Synchronization for all Computers in a Windows domain
Microsoft operating systems and server applications are becoming increasingly dependent on proper time synchronization. A skewed system clock can affect your ability to log on, can cause problems with mail flow in Exchange, and be the source of a great many difficult-to-locate problems. To compound matters, the default method of handling time synchronization within a Windows network isn’t exactly reliable or even predictable. If a Hyper-V host’s clock becomes out of sync, it usually affects all of its virtual machines, sometimes catastrophically. Fortunately, it doesn’t take much work to get everything in sync.
Pick a Computer to Server as the Authoritative Internal Time Source
The first thing you want to do is decide what machine you want to serve as the authority of time within your domain. In most cases, I choose the domain controller that holds the PDC emulator role. According to Microsoft’s documentation, that’s supposed to be the highest authority on the matter anyway, although it doesn’t seem to work out that way in practice. The machine that you choose will be regularly consulting Internet sources, so if you’re in a high-security facility, you might consider delegating this role to a different computer. You could have multiple machines serving as authoritative time sources, but more than one per site generally is unnecessary. You could also have one machine pull external time and have your PDC emulator use that as its source while still serving as the authoritative server for the rest of the computers in your domain.
Hard to imagine anything worse than data center outage, right? The business has to move smoothly, and data has to be available 24/7. Well, luckily, there are ways to make it happen. Check out the Azure Site Recovery service and find out what you can do with it!