SMB Connections move on connect Scale-Out File Server (SOFS) relies on DNS round robin for inbound connections sent to cluster nodes. When using Storage Spaces on Windows Server 2016 and older,...
Updated Sep 10, 2019
Version 5.0
Blog Post
I want to use Infrastructure SOFS but not Cluster Sets.
Is that impossible??
To elaborate my case:
Today I have:
A 2016 Hyper-converged S2D cluster
A set of 2016 Hyper-V hosts (not a cluster), which use a stand-alone 2016 file server as shared SMB storage.
I want to upgrade the S2D cluster as well as the stand-alone Hyper-V hosts to 2019 and retire the stand-alone file server.
And I want to create an Infrastructure SOFS role in the S2D cluster. It will be the new shared storage for all the virtual machines running on the stand-alone Hyper-V hosts.
The stand-alone Hyper-V hosts are not sufficiently alike to become a cluster and we do not need the failover capability of a cluster. But we do need the vm live migration capability of the shared storage.