Comments on Highly Available NFS Server Using DRBD And Heartbeat On Debian 5.0 (Lenny)

"A common system administration error is to delete the links with the thought that this will "disable" the service, i.e., that this will prevent the service from being started. However, if all links have been deleted then the next time the package is upgraded, the package's postinst script will run update-rc.d again and this will reinstall links at their factory default locations. The correct way to disable services is to configure the service as stopped in all runlevels in which it is started by default. In the System V init system this means renaming the service's symbolic links from S to K." "EXAMPLES Example of disabling a service: update-rc.d -f foobar remove update-rc.d foobar stop 20 2 3 4 5 . "

Instead of using 192.168.1.5 as virtual IP ("192.168.1.5/24 would be my virtual floating IP addres") you used 192.168.1.100 as virtual IP in your howto.

I followed all your instructions and noticed a "Resource stopped" after giving the command invoke-rc.d heartbeat start. I am using 2 Systems with DRBD and nfs-server. We want to set up a service IP. Most the time nfs-kernel-server starts, but the nfs-common not. This is the reason for missing all exports. Do you have any idea? Thanks for any idea or help. phil

Well explained. I have found another good site for a DRBD NFS Pacemaker / Heartbeat tutorial on this site here: http://docs.homelinux.org

Thanks for Your articel

I walked through this explanation and had a working failover clustered NFS server first pass. Thanks for your help!

sorry i have a small questen . i dont understand the ip configure the cliend have 192.168.1.4 the virtuel ip is 192.168.1.5 and in the config of /etc/ha.d/haresources - (on server01 and server02): is the ip 192.168.1.100 questen 1 how install i the cliend or is 192.168.1.5 the cliend and what is then 192.168.1.100 can anybody help ?