Setting up a failover cluster is a thing that admins must do. To build such cluster, you need to configure shared storage. And, there are a lot of ways to do that. Today, I’d like to discuss how to build a Windows Failover Cluster using a virtual SAN solution (StarWind Virtual SAN) as a shared storage provider.
Can SQL Server Failover Cluster Instance run on S2D twice as fast as SQL Server Basic Availability Groups on Storage Spaces? Part 1: Studying BAG performance
Some time ago, I published here comparison of SQL Server Failover Cluster Instances (FCI) and SQL Server Basic Availability (BAG) performance while having them run on top of StarWind Virtual SAN. Today, I measure SQL Server BAG performance on Storage Spaces. The next part sheds light on SQL Server FCI performance on S2D. Can I squeeze two times more TPM out of SQL Server FCI on S2D than SQL Server BAG can provide on Storage Spaces?
How to save disk space in Clustered File Servers on Windows Server 2016 using Data Deduplication feature
So we all know about the benefits you get with data deduplication technology. Long story short, it minimizes server application’s storage consumption by reducing the amount of redundant data stored on the disk. As the result, you should get more space for your VMs and applications. How does it work for a file server? Well, that’s what I’m gonna test here.
Subscribe to our posts
- How is NVMe-oF doing? Part 1: Linux NVMe-oF Initiator + Linux SPDK NVMe-oF Target
- Setting up a Windows Failover Cluster for a home lab
- Performance comparison: SQL Server Failover Cluster Instance on S2D vs. SQL Server Basic Availability Groups on Storage Spaces. The battle starts
- Can SQL Server Failover Cluster Instances run on S2D twice as fast as SQL Server Basic Availability Groups on Storage Spaces? Part 2: Studying FCI performance
- Can SQL Server Failover Cluster Instance run on S2D twice as fast as SQL Server Basic Availability Groups on Storage Spaces? Part 1: Studying BAG performance