High reliability web server - cluster, redundancy, etc Post: 302302261

Sponsored Content

Special Forums UNIX and Linux Applications High Performance Computing High reliability web server - cluster, redundancy, etc Post 302302261 by kipperjp on Monday 30th of March 2009 01:38:16 PM

03-30-2009

Registered User

Keep in mind that clustering does not mean high availability. CLustering is sharing resources with multiple machines. What you need to look into is syncing and failover mechanisms so that 2 web servers at different locations are mirrored copies so that if one goes down, dns is routed to the other server.

I am kind of down this route myself and learning as I go. Be nice to utilize an HA consultant as trial and error can be costly.

kipperjp

View Public Profile for kipperjp

Find all posts by kipperjp

3 More Discussions You Might Find Interesting

1. Solaris

High Availability zone on Sun Cluster

HI Experts, Could some one help me in configuring high availability zone on Sun Cluster Reg: Sudhan

2. Red Hat

Red Hat High Availability (HA) Cluster

How can we implement a service in HA, which in not available in HA. like sldap or customize application. Requirement Details. NODE1 service slapd is running.(Require) NODE2 service slapd is running.(Require) on both the node replication is happening. Now here requirement is need...

3. Red Hat

Web server cluster at some point ?

What's the best way clusters for Storage at some point? (The way that data is the same in all parts) To set up a Web server cluster is the logical way?! Cluster database and Storage and then by keepalived + HA cluster will be communicated? Or, there a better solution? (For about 4 points) Thank...

LEARN ABOUT DEBIAN

dump_sockdfr

DUMP_SOCKDFR(8) 					      System Manager's Manual						   DUMP_SOCKDFR(8)

NAME

       dump_sockdfr -  Display contents of frozen route file for SOCKS server

SYNOPSIS

       dump_sockdfr [infile]

DESCRIPTION

       dump_sockdfr reads in a frozen route file for the SOCKS server and produces a listing of its contents on the standard output.

       The argument is optional; if omitted, /etc/sockd.fr is assumed.

       The frozen route file is produced by make_sockdfr and is essentially the memory image of the parsed route file. Using the frozen route file
       can reduce the start-up delay of the SOCKS server program since it no longer has to parse the file contents.

       When the SOCKS server starts, it always looks for the frozen route file /etc/sockd.fr first. If that file is not found, it  then  tries	to
       use  the  plain-text  route file /etc/sockd.route. If you use frozen route file, you must remember to run make_sockdfr every time after you
       modify the plain-text file or the SOCKS server will continue to use the frozen version of a previous route file.

FILES

       /etc/sockd.fr, /etc/sockd.route

SEE ALSO

       make_sockdfr(8), sockd.fr(5), sockd.route(5)

AUTHOR

       Ying-Da Lee, yingda@esd.sgi.com or yingda@best.com

								    May 6, 1996 						   DUMP_SOCKDFR(8)