I'm sorry to say but this is a terrible article. It's all marketing fluff... I'd like to see some implementation specifics outside of "we did this so you should too" marketing bs.

@oksana I doubt you will find the audience you are looking for at reddit, but good luck.

That blog post is wrong, it says that DRBD must be active/passive. But it has offered active/active for some time. https://docs.linbit.com/doc/users-guide-83/s-dual-primary-mode/

@r3dpand4 said in Microsoft Removes Storage Spaces Direct from Windows Server 2016: @tim_g said in Microsoft Removes Storage Spaces Direct from Windows Server 2016: @scottalanmiller said in Microsoft Removes Storage Spaces Direct from Windows Server 2016: @darek-hamann said in Microsoft Removes Storage Spaces Direct from Windows Server 2016: The implementation of an Azure Stack would be something to get our heads around for the time being. Hopefully it is better than the actual Azure system! It is Azure, same thing, but you have a physical node on-prem. You pay for the hardware, and you get Azure a little cheaper, but it's fully managed by them. It's really only for remote places with bad bandwidth imho. Think like, needing cloud from an 18-wheeler in a remote location. This sounds like a crappy version of the AWS Snowball Completely different. This is like making your portion of the AWS cloud in-house, including the entire AWS stack. Again, not too useful unless you are trying to bring the cloud to a remote location to avoid excessive latency or to somewhere the internet doesn't exist... like linking it to a satellite connection during a disaster or something. There are other real uses, but that would be for bigger enterprises... for most SMBs, Azure Stack would never be a consideration.

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

@r3dpand4 said in Compuverde: vNAS or Hyperconverged: @fateknollogee I mean that's depending on your deployment, it's included with 2016 Datacenter.... So is Storage Replica and whole bunch of things you aren't going to use if you aren't within hyperconverged setup. VMware with a separate SKU for VSAN got a better idea. ImHO.