What is the basic process behind high availability nfs over 2 servers? Let's say that I'm using heartbeat to fail over a floating IP between the 2. I then have a third party server that mounts an nfs share based off that IP. The idea being that I can manipulate files and then if a fail over occurs, the nfs will remain active and it will be temporarily unavailable as the nfs and IP is switched to the other server.
However, I'm wondering about the workflow. At the moment with manual fail over, I can have node1 as drbd primary and mount the drbd as nfs export with floating IP. Then if I want to fail over, I can unmount the drbd drive, set the server to secondary, then set node2 to primary, mount drbd nfs and then the new IP will come up on node2.
Is this the right idea? If I try and unmount the nfs/drbd mount gracefully, it can fail because nfs is still accessing it (aka if the third party server is accessing the share).
Is there a way to have a similar process with manual failover but quickly fail over?