NFS service on cluster with shadow copies enabled


we have windows 2012 r2 file server in cluster. there no cluster shared volume (because user file server resource manager , nfs, not supported csv)
"file server general use"

we install role "server nfs".  since created first nfs share resource in cluster, new resource automatically created in file cluster role : network file system

we enabled shadow copies volume shares (nfs , smb share). use default schedule settings shadow copies, twice day.

after ~1 month, failover role on node, , noticed resource network file system take long time come online. long goes in failed state... other resources working well. if wait long enough, resource become in online state eventually... 15 minutes. 

in windows event logs, in servicesfornfs-server logs, can see operational log filled operation "created volume", "destroyed volume", "discovered volume" etc... , these operations take long time during failover of cluster. when finished, resource become online.

i tried deactivate shadow copies on volume. , failover of nfs working fast !!! nfs resource online @ same time of others resources.

so obvioulsy nfs not work shadow copies! (on cluster)

does else figured issue out ? or has idea cause of issue??
need have shadow copies on volume !

thanks !

hi serge84,

thanks post.

do have messages in system event log associated shared storage? i’m sorry seems work fine in test.

you check thread discussed before. , might discuss in our cluster forum for more idea.

https://social.technet.microsoft.com/forums/windowsserver/en-us/2cd8a6e7-0fcb-4e6c-9672-bdfa19de00de/server-2012-nfs-10-minutes-to-resume-after-failover?forum=winserverclustering

best regards,

mary


please remember mark replies answers if , unmark them if provide no help. if have feedback technet subscriber support, contact tnmff@microsoft.com.




Windows Server  >  File Services and Storage



Comments

Popular posts from this blog

Group Policy Event ID 1058 Error Code 1326 (The user name or password is incorrect)

Suspicious event log Event ID: 4905

DCOM received error "2147746132" from...