non disruptive failover for cifs session

[grocanar]

Hi

I m wondering how i can manage to have non disrutive failover for cifs session. 

As far as i can see i should use continuous availability but i see it s not really good

for other things than 

Hyper-V over SMB and SQL over SMB.

Can i use it for general share like home share? 

[parisi · Accepted solution]

No, using continuously available share property is unsupported for workloads other than the ones mentioned.

SMB2/3 failover in general will be minimally disruptive by default due to durable handles and other features, so your end users likely won't notice failovers/givebacks in a majority of cases.

[GidonMarcus]

As @parisi  said - in SMB 2+ we usually don't see an impact. Just make sure the clients indeed use SMB 2+, as things like un-delegated CNAME aliases can get it to fallback to SMB1

CMD:

vserver cifs session show -vserver vserver_name -protocol-version SMB1

or PS:

Get-NcCifsSession -Controller $clustersSessions | ? {$_.ProtocolVersion -eq "smb1" -or $_.AuthMechanism -match "ntlm"} | select vserver,WindowsUser,Address,AuthMechanism,ProtocolVersion -Unique