Comments on Setting Up A Highly Available NFS Server
Setting Up A Highly Available NFS Server In this tutorial I will describe how to set up a highly available NFS server that can be used as storage solution for other high-availability services like, for example, a cluster of web servers that are being loadbalanced. If you have a web server cluster with two or more nodes that serve the same web site(s), than these nodes must access the same pool of data so that every node serves the same data, no matter if the loadbalancer directs the user to node 1 or node n. This can be achieved with an NFS share on an NFS server that all web server nodes (the NFS clients) can access.
8 Comment(s)
Comments
Another similar setup http://www.planetmy.com/blog/setup-a-linux-highly-availability-nfs-servers/
The text says:
Also, make sure /dev/sda7 as well as /dev/sda8 are identical in size
But the illustration indicates:
/dev/sda7 -- 150 MB unmounted
/dev/sda8 -- 26 GB unmounted
So which is it?
Thanks
Means same size on BOTH server in cluster.
And here: http://docs.homelinux.org another well explained tutorial about DRBD and NFS on Debian.
This is somewhat of the set-up that I have been looking for, however when joining this “Highly Available NFS Server or a Balanced MySQL Cluster” with a “Loadbalanced High-Availability Web Server Apache Cluster”, my concerns are the IP's...
The tutorial for both “Loadbalanced High-Availability MySQL Cluster and Loadbalanced High-Availability Web Server Apache Cluster” utilize the same IP addresses…
Within this tutorial it’s mentioned “Virtual IP address that represents the NFS cluster to the outside and also a NFS client IP address...”
I am looking to join two of the clusters to make a highly available stable web hosting cluster with utilizing either NFS or MySQL for the back-end…
Which IP’s should be used for each node?
But how do i "Virtual Ip" over the 2 servers?
I've having an interesting issue. server1 and server2 properly work with server2 mounting drbd0 properly in /data. Performing ls /data shows the correct mountpoint as the drbd0 folder on server2 if i stop the heartbeat of server1.
I was having nfs issues on the client whenever i would test the heartbeat of server1. During testing, I have found that if i stop the heartbeat of server1 and then manually mount the nfs at the Virtual IP address, it will mount the original /data folder of server2 (not the drbd0 /data folder).
"Virtual IP address: I use 192.168.0.174 as the virtual IP address that represents the NFS cluster to the outside."
What is this VIP mapped to? A load balancer or the primary NFS server?