This message was deleted.
# microsoft-fslogixs
Slackbot
12/10/2019, 2:10 PMThis message was deleted.
l
Lucas Van den Broeck
12/10/2019, 3:04 PMNot using SOFS but normal CA-shares, there is a large IOPS penalty since they're effectively syncing the handles on the other fileserver in the cluster. That is also the main reason a lot of microsoft documents say to only use this for single file handles like quorum disks etc. And especially not for roaming profiles and redirected data loads of (small) file handles. (These are also recommended to have offline availability off for years). Since FSL only opens 1 handle per vdisk it should be a manageable penalty and the benefits 'should' outweigh the penalty on modern storage as far as I've seen.
k
Kasper Johansen
12/10/2019, 3:07 PMIf I understand the technologies correctly, it's either SOFS or CA, not both.
l
Lucas Van den Broeck
12/10/2019, 3:12 PMnot sure how it is these days (2019 and the like), but in 2012 R2 etc. you still needed to enable CA on SOFS
k
Kasper Johansen
12/10/2019, 3:30 PMWhat I have seen, in 2019, it shouldn't be necessary to enable CA with SOFS.
Kasper Johansen
12/10/2019, 3:30 PMI know @Leee Jeffries often has something clever to say/write about SOFS and CA
l
Leee Jeffries
12/10/2019, 4:44 PMSo SOFS is basically an active/active cluster. It's a cluster with storage spaces direct replication between nodes. This is recommended only for continuously available files (like VHDs), standard windows clustering (active/passive) has the ability to provide continuous availability on a share. As stated above though, the file handles are synced to passive node(s) so that when a storage node fails the handles are seamlessly ported and disconnects don't happen.
Leee Jeffries
12/10/2019, 4:45 PMThe only time I would use SOFS is when a storage provision cannot support the load / IOPS required for the load expected. SOFS would allow you to spread the load between distinctly different storage targets by balancing users across different nodes.
👍 1
Leee Jeffries
12/10/2019, 4:47 PMSOFS is also useful in Azure due to the limit of the number of disks that can attached to certain VM sizes in relation to the IOPS caps on certain disk types. This allows scaling of storage as well as options for costing.
Leee Jeffries
12/10/2019, 4:48 PMThanks for for looping me in @Kasper Johansen
👍 1
o
Owen Reynolds
12/10/2019, 4:50 PMThank you , lee. The client does have plans to utilize azure at some point. Thus the SOFS build.
l
Leee Jeffries
12/10/2019, 4:50 PMAbsolutely no worries. Just drop me a message if you need a hand at all.
🙂 1