This tutorial explains how to set up a highly available NFS server that can be used as storage solution (NAS – networked attached storage) for a cluster of web server instances that are being load balanced by a load balancer , for example ELB . If you have a web server cluster with two or more instances that serve the same web site contents, then these instances must access the same amount of data so that each one serves the same data, no matter if the load balancer directs the user to instance 1 or instance n. This can be achieved with an NFS share on an NFS server that all web server instances (the NFS clients) can access.<\/p>\n
Install the package nfs-utils in the NFS server instance<\/p>\n
[shell]# yum install nfs-utils[\/shell]<\/p>\n
The NFS setup also needs the portmap daemon<\/p>\n
[shell]# yum install portmap[\/shell]<\/p>\n
Every file system being exported to remote ec2 instance via NFS, as well as the access level for those file systems, are listed in the \/etc\/exports file. When the nfs service starts, the exportfs command launches and reads this file, passes control to rpc.mountd (if NFSv2 or NFSv3) for the actual mounting process, then to rpc.nfsd where the file systems are then available to remote instances.<\/p>\n
Lets say you want to export the directory \/opt\/nfstest of the nfs server to two remote instances having private ip’s 192.168.1.9 and 192.168.1.10<\/p>\n
[shell]# vi \/etc\/exports[\/shell]<\/p>\n
Add<\/strong><\/p>\n [shell] and save the file<\/p>\n Now we use the exportfs command. It is used to maintain the current table of exported file systems for NFS. This list is kept in a separate file named \/var\/lib\/nfs\/xtab<\/strong> which is read by mountd <\/strong>when a remote instance requests access to mount a directory. [shell]#exportfs -a[\/shell]<\/p>\n Getting the services started<\/strong><\/p>\n Starting the Portmapper<\/strong> [shell]# \/etc\/init.d\/portmap start[\/shell]<\/p>\n it is worth making sure that it is running before you begin working with NFS<\/p>\n [shell]# ps aux | grep portmap[\/shell]<\/p>\n Now start the NFS daemon<\/strong><\/p>\n [shell]# \/etc\/init.d\/nfs start[\/shell]<\/p>\n Verifying that NFS is running<\/strong><\/p>\n [shell]# rpcinfo -p [\/shell]<\/p>\n you will get something like this.<\/p>\n program vers proto port Please note that portmap listens on port 111 and nfs on port 2049.<\/p>\n If you later decide to add more NFS exports to the \/etc\/exports file, you will need to either restart NFS daemon or run command exportfs:<\/p>\n [shell]#exportfs -ar[\/shell]<\/p>\n Mount remote file system on client<\/p>\n First we need to create a mount point:<\/p>\n [shell]# mkdir \/opt\/localmount [\/shell]<\/p>\n If you are sure that the NFS client and mount point are ready, you can run the mount command to mount exported NFS remote file system:<\/p>\n [shell]# mount -t nfs 192.168.1.3:\/opt\/nfstest \/opt\/localmount[\/shell]<\/p>\n Here 192.168.1.3 is the ip of the NFS server, -t is used to specify the file system.<\/p>\n Restart the portmap daemon in the client<\/p>\n [shell]# \/etc\/init.d\/portmap restart[\/shell]<\/p>\n done !<\/p>\n Now you can verify your NFS mounts with the showmount command which shows the exports from the NFS server.<\/p>\n [shell]# showmount -e 192.168.1.3[\/shell]<\/p>\n which will show output like<\/p>\n [shell] This tutorial explains how to set up a highly available NFS server that can be used as storage solution (NAS – networked attached storage) for a cluster of web server instances that are being load balanced by a load balancer , for example ELB . If you have a web server cluster with two or […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[3],"tags":[28,612,454,44,609,220,232,610,608,250,611,179,204,613,615,614],"class_list":["post-287","post","type-post","status-publish","format-standard","hentry","category-cloud-computing","tag-aws-ec2-cloud-computing-nfs","tag-exported-file-systems","tag-file-systems","tag-load-balancing","tag-network-file-system","tag-network-file-systems","tag-network-management","tag-network-attached-storage","tag-routing","tag-server","tag-storage-solution","tag-udp","tag-web-server","tag-web-server-cluster","tag-web-server-instances","tag-web-site-contents"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
\n\/opt\/nfstest 192.168.1.9\/255.255.255.0(rw, no_root_squash, async)
\n\/opt\/nfstest 192.168.1.10\/255.255.255.0(rw, no_root_squash, async)
\n[\/shell]<\/p>\n
\nNormally this xtab file is initialized with the list of all file systems named in \/etc\/exports by invoking exportfs -a.<\/p>\n
\nNFS depends on the portmapper daemon, either called portmap or rpc.portmap. It will need to be started first.<\/p>\n
\n100000 2 tcp 111 portmapper
\n100000 2 udp 111 portmapper
\n100011 1 udp 749 rquotad
\n100005 2 tcp 766 mountd
\n100005 3 udp 769 mountd
\n100005 3 tcp 771 mountd
\n100003 2 udp 2049 nfs
\n100003 3 udp 2049 nfs
\n300019 1 tcp 830 amd
\n300019 1 udp 831 amd
\n100024 1 udp 944 status
\n100024 1 tcp 946 status
\n100021 1 udp 1042 nlockmgr
\n100021 3 udp 1042 nlockmgr
\n100021 4 udp 1042 nlockmgr<\/p>\n
\n\/opt\/nfstest 192.168.1.9\/255.255.255.0,192.168.1.10\/255.255.255.0
\n[\/shell]<\/p>\n","protected":false},"excerpt":{"rendered":"