This message was deleted.
# microsoft-fslogix
s
This message was deleted.
j
CA shares
j
CA stand for?
l
continuous availability, scale out cluster without scale out πŸ˜‰
so just a file cluster with CA option enabled on those shares
j
yep that
n
I can unfortunately confirm that if the shares go down, Outlook crashed hard...
j
Nick was this with CA file cluster? What are the lessons learned?
n
This was with a single file server using a DFS front-end. πŸ™‚
That issue allowed me to force the server team into doing what I asked for the first time around, a file cluster with CA. We'll be migrating in January.
j
Thanks Nick for the clarification!!! What Server OS are you using?
n
Server 2016. I don't think we actually have any 2019 stuff yet. We're healthcare, and are a little slow to adopt.
d
When the sh*t hits the fan it’s good to have smaller failure domains, so distribution to multiple shares hosted on different servers might be something to consider at your scale.
a
Does Microsoft SOFS require vSAN licensing when configuring on vSphere? From what it looks like you have to configure vSAN WSFC when configuring Microsoft SOFS on vSphere or I may be reading this all wrong.
k
@Austin Madison vSAN is not a prereq. As far as I see it, based on the WSFC whitepaper from VMware, you have to configure WSFC with Raw Device Mapped storage, to have a VMware supported solution, when the file cluster resources reside on different VMware hosts. You can configure a WSFC using VMware shared disk, and that is supported as long as the file cluster resources are on the same VMware host. Putting the file cluster resources on different hosts also works, but is not supported by VMware. VMware has an excellent whitepaper on how to configure MSCS and WSFC here: https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-67-setup-mscs.pdf
a
Thanks @Kasper Johansen for clarifying. Really appreciate it!
πŸ‘ 1