This message was deleted.

erm no, not without Cloud Cache, FSLogix is Container Tech and does not handle an outage at all (that is what cloud-cache was specifically designed to handle). Each Container is directly mounted to the endpoints and written to in real time

so no good to reboot file store unless all users are off. Except when you use cloud cache

not unless you hate your users

thinking

Continuous availability (SMB feature) is also there for this. Nutanix Files, NetApp Files, ect all support Continous Availability on SMB That allows me to do maintenance (still do in change window) on file cluster situations with multiple servers, nodes, etc.

I thought CA and FSL didn't play nice together?

Thats typically around CC and CA

I once tested this for a customer (no Cloud-cache, just normal SMB). When the fileshare was available again in less than 1 minute, the users didn't have issues, when it took longer than 1 minute, it was a disaster! This was an isolated test with only a few VDIs active. I think it depends on the timeouts and reconnects you can specify in the FSLogix settings but didn't dig deeper into it. PS. This test was done > 3yrs ago, so don't know what newer versions today will do.

There is also a correlation to SMB handling there - I think it must depend on the type of outage - that goes way past where my brain can handle things - thats a @Leee Jeffriesspecial

A two node Windows file server cluster with CA enabled on the SMB share works great. Can reboot either node and not impact users/fslogix.

Yup, Love a bit of CA on Windows File cluster or anything else that supports it. Just do not turn on CA for a share that has lots of little files, like folder redirection. That will kill your file server.