As in my previous post I failed miserably buiding an S2D cluster. Fortunately, it was just a small matter of reading this whitepaper properly which states only local storage can be used. We all know iSCSI storage is not locally attached so it makes perfect sense it doesn’t work. But at least I tested it and verified…
OK, so knowing that S2D works with DAS storage only it is time to test and verify if it’s difficult to build an S2D cluster.
To build the cluster, I’m going to build one using this guide. I use 2 FS1 Azure VMs and attach one P10 disk to each node.
So I follow the steps to build the cluster.
Thir fist step is to enable S2D which works fine.
NOTE: as in my previous post, the CacheMode parameter is not there. While this is still in the guide it may be a bit confusing to read it.
The next step is creating a Storage Pool for S2D.
Hmm, that’s odd. Appearantly 2 disks is insufficient. So, let’s add two more, one at each node resulting in having four disks.
OK, so I can continue building a S2D cluster disk of 250 GB
The final step is creating a share according to the guide.
Hmmm, this fails too…
Well I was able to create the share using the Failover Clustering Console by configuring it as a SOFS and provide a ‘Quick’ file share.
So yeah, it’s relatively easy to build an S2D cluster but some steps in the overview need to be reviewed again. It contains mistakes…