Behavior of Services for NFS on a 2008 failover cluster
i have question expected behavior of services nfs in 2008 r2 failover cluster.
i running 2-node file/print server cluster fibre (hba) connection san back-end.
services nfs installed , running successfully. windows , linux clients connecting using ad lookup (identity unix installed on dcs gids/uids populated).
when move cluster services nodea nodeb, see cluster disk , cluster resource come online without problem. also, file share nfs comes online without incident.
however, observing when try access nfs share windows client, can see share name when click on windows explorer, receive error device not ready.
during last test, found take nfs share offline , bring online resolve this. also, found statement "best practices running server nfs in server cluster":
to ensure proper operation of server nfs in server cluster, when stopping server cluster, first stop server nfs, stop server cluster.
so...does mean recommended manually stop server nfs before fail server cluster on node??
i have question expected behavior of services nfs in 2008 r2 failover cluster.
i running 2-node file/print server cluster fibre (hba) connection san back-end.
services nfs installed , running successfully. windows , linux clients connecting using ad lookup (identity unix installed on dcs gids/uids populated).
when move cluster services nodea nodeb, see cluster disk , cluster resource come online without problem. also, file share nfs comes online without incident.
however, observing when try access nfs share windows client, can see share name when click on windows explorer, receive error device not ready.
during last test, found take nfs share offline , bring online resolve this. also, found statement "best practices running server nfs in server cluster":
to ensure proper operation of server nfs in server cluster, when stopping server cluster, first stop server nfs, stop server cluster.
so...does mean recommended manually stop server nfs before fail server cluster on node??
we have nfs guest vm cluster moving hyper-v node node w/o issues it's kind of misconfiguration.
-nismo
Windows Server > File Services and Storage
Comments
Post a Comment