<p dir="ltr">I've seen it done with DRBD and a dns failover. Two servers in back channel live sync with DRBD. Slave setup would fence and take over if master fell down and fall back once master resynced and returned. Did need to use soft mount and not hard.</p>
<div class="gmail_quote">On Oct 27, 2013 12:13 PM, "Leam Hall" <<a href="mailto:leamhall@gmail.com">leamhall@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I recall seeing a place use multiple NFS servers for the same mount point. That is, if NFS-1 is not available, then use NFS-2. However, I wasn't involved in the setup and am not sure if they were using Virtual IPs or if mount can actually have an "servera or serverb" option.<br>
<br>
What's the current best practice for setting up a shared filesystem with reliability, failover, and good replication? If distro matters, this is more towards Ubuntu.<br>
<br>
Thanks!<br>
<br>
Leam<br>
<br>
-- <br>
<a href="http://31challenge.net" target="_blank">http://31challenge.net</a><br>
<a href="http://31challenge.net/insight" target="_blank">http://31challenge.net/insight</a><br>
______________________________<u></u>_________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/<u></u>listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/<u></u>listinfo</a><br>
</blockquote></div>