How to increase web server uptime with DNS failover:
For illustration, let's start with some really bad hosting...
Find four free web hosts that are each 90% reliable
-- in other words they each are down on average one
day out of ten. Use a failover DNS system with monitoring
to switch servers if one fails. On average:
One server will be down one day out of ten
Two servers will be down one day out of a hundred
Three servers will be down one day out of a thousand
All four servers -- and thus your website -- will be
down at the same time one day out of ten thousand.
Two servers with 99% uptime will also be down at the same
time one day out of ten thousand. Three at 99% will be
down at the same time one day out of a million.
In addition, there will be a delay for some users before
the new server is switched in. One website measured this
as follows:
After 5 minutes, 3% of visitors see the new server.
After 10 minutes, 20% of visitors see the new server.
After 15 minutes, 37% of visitors see the new server.
After 20 minutes, 59% of visitors see the new server.
After 25 minutes, 69% of visitors see the new server.
After 30 minutes, 76% of visitors see the new server.
After 35 minutes, 80% of visitors see the new server.
After 45 minutes, 90% of visitors see the new server.
After 90 minutes, 95% of visitors see the new server.
After 18 hours, 99% of visitors see the new server.
With any number of servers at 90% uptime, this will
happen on average every ten days. With any number of
servers at 99% uptime, this will happen on average
every hundred days.
Needless to say, this works even better if you start
with high-uptime paid servers.
References: http://blog.pyromod.com/2007/09/viab...-failover.html http://www.webhostingtalk.com/showthread.php?t=524788 http://www.dnsmadeeasy.com/s0306/prod/dnsfosm.html http://www.georedundanthosting.com/p...t-hosting.aspx http://edgedirector.com/app/back.htm http://www.webstrikesolutions.com/Page_ID.aspx?IDTXT=36
--
Guy Macon <http://www.GuyMacon.co m/Guy Macon <http://www.GuyMacon.co m/>
Guy Macon <http://www.GuyMacon.co m/Guy Macon <http://www.GuyMacon.co m/>
Guy Macon <http://www.GuyMacon.co m/Guy Macon <http://www.GuyMacon.co m/>
Guy Macon <http://www.GuyMacon.co m/Guy Macon <http://www.GuyMacon.co m/> 8  2721 
Guy Macon <http://www.GuyMacon.co m/wrote:
>
How to increase web server uptime with DNS failover:
For illustration, let's start with some really bad hosting...
Find four free web hosts that are each 90% reliable
-- in other words they each are down on average one
day out of ten. Use a failover DNS system with monitoring
to switch servers if one fails. On average:
One server will be down one day out of ten
Two servers will be down one day out of a hundred
Three servers will be down one day out of a thousand
All four servers -- and thus your website -- will be
down at the same time one day out of ten thousand.
Two servers with 99% uptime will also be down at the same
time one day out of ten thousand. Three at 99% will be
down at the same time one day out of a million.
In addition, there will be a delay for some users before
the new server is switched in. One website measured this
as follows:
After 5 minutes, 3% of visitors see the new server.
After 10 minutes, 20% of visitors see the new server.
After 15 minutes, 37% of visitors see the new server.
After 20 minutes, 59% of visitors see the new server.
After 25 minutes, 69% of visitors see the new server.
After 30 minutes, 76% of visitors see the new server.
After 35 minutes, 80% of visitors see the new server.
After 45 minutes, 90% of visitors see the new server.
After 90 minutes, 95% of visitors see the new server.
After 18 hours, 99% of visitors see the new server.
With any number of servers at 90% uptime, this will
happen on average every ten days. With any number of
servers at 99% uptime, this will happen on average
every hundred days.
Needless to say, this works even better if you start
with high-uptime paid servers.
References:
http://blog.pyromod.com/2007/09/viab...-failover.html
http://www.webhostingtalk.com/showthread.php?t=524788
http://www.dnsmadeeasy.com/s0306/prod/dnsfosm.html
http://www.georedundanthosting.com/p...t-hosting.aspx
http://edgedirector.com/app/back.htm
http://www.webstrikesolutions.com/Page_ID.aspx?IDTXT=36
More References: http://www.simplefailover.com/outbox/dns-caching.pdf http://ausweb.scu.edu.au/aw03/papers...oth/paper.html http://support.easydns.com/Failoverfaq.php http://edgedirector.com/htm/note.htm
--
Guy Macon <http://www.GuyMacon.co m/Guy Macon <http://www.GuyMacon.co m/>
Guy Macon <http://www.GuyMacon.co m/Guy Macon <http://www.GuyMacon.co m/>
Guy Macon <http://www.GuyMacon.co m/Guy Macon <http://www.GuyMacon.co m/>
Guy Macon <http://www.GuyMacon.co m/Guy Macon <http://www.GuyMacon.co m/>
On Sun, 26 Oct 2008 17:11:35 +0000, Guy Macon wrote:
How to increase web server uptime with DNS failover:
Two servers with 99% uptime will also be down at the same time one day
out of ten thousand. Three at 99% will be down at the same time one day
out of a million.
....as long as they run different operating systems and different servers
and host different websites, and are on different internets and are
independent in every other conceivable way.
viza wrote:
>
Guy Macon <http://www.GuyMacon.co m/wrote:
>How to increase web server uptime with DNS failover:
>Two servers with 99% uptime will also be down at the same time one day
out of ten thousand. Three at 99% will be down at the same time one day
out of a million.
...as long as they run different operating systems
Nope. They can both be running on linux. If every linux system
goes down at the same time, having one of your copies on, say,
solarus won't help you: the entire internet will be down.
>and different servers
I already specified that. Did you bother to read the post you are
responding to?
>and host different websites,
Nope. two servers in different places won't go down at the
same time just because the are serving the same HTML.
>and are on different internets
Now you are just being silly.
>and are independent in every other conceivable way.
That's not how the math behind redundancy works. the two
redundant systems have to not share a single point of
failure. Being "independen t in every other conceivable
way." is not a requirement. My cellphone and my laser
printer both share the attribute of having copper
conductors and silicon microprocessors , (and thus are
not " independent in every conceivable way" but those
are not common points of failure. A copper wire may
fail, but all copper wires on earth are not going to
fail at the same time.
DNS failover can increase web server uptime. That is a
basig engineering calulation that has been tested many
times of many systems.
"Arguing with anonymous strangers on the Internet is a sucker's
game because they almost always turn out to be -- or to be
indistinguishab le from -- self-righteous sixteen-year-olds
possessing infinite amounts of free time."
-Neil Stephenson, _Cryptonomicon_
--
Guy Macon
<http://www.GuyMacon.co m/>
viza wrote:
On Sun, 26 Oct 2008 17:11:35 +0000, Guy Macon wrote:
>How to increase web server uptime with DNS failover:
>Two servers with 99% uptime will also be down at the same time one
day
out of ten thousand. Three at 99% will be down at the same time one
day out of a million.
...as long as they run different operating systems and different
servers and host different websites, and are on different internets
and are independent in every other conceivable way.
The OS they run is irrelevant. Different systems on different networks
is the only thing that really plays a role, not the web site, type of
web site, platform/OS, or anything else. None of that would help
ensure better uptime, and only the network used between the two would
matter.
Ideally, you want to host DNS on different networks so if a DNS server
fails, the requestor's system or network doesn't see it as nonexistent
(just non responsive). There's a difference between non responsive,
down and non existent and those responses could be cached.
Beyond DNS, is actual DNS round-robin balancing, so if one system or
service goes down (not the DNS server/service) the other will be used
(one is down, too slow, overloaded, etc., the other one is used), but
you'd want to just do more than a round-robin solution for failover
services, if you have the option to.
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
Guy Macon wrote:
viza wrote:
>Guy Macon <http://www.GuyMacon.co m/wrote:
>>How to increase web server uptime with DNS failover:
Two servers with 99% uptime will also be down at the same time one day
out of ten thousand. Three at 99% will be down at the same time one day
out of a million.
...as long as they run different operating systems
Nope. They can both be running on linux. If every linux system
goes down at the same time, having one of your copies on, say,
solarus won't help you: the entire internet will be down.
>and different servers
I already specified that. Did you bother to read the post you are
responding to?
>and host different websites,
Nope. two servers in different places won't go down at the
same time just because the are serving the same HTML.
>and are on different internets
Now you are just being silly.
>and are independent in every other conceivable way.
That's not how the math behind redundancy works. the two
redundant systems have to not share a single point of
failure. Being "independen t in every other conceivable
way." is not a requirement. My cellphone and my laser
printer both share the attribute of having copper
conductors and silicon microprocessors , (and thus are
not " independent in every conceivable way" but those
are not common points of failure. A copper wire may
fail, but all copper wires on earth are not going to
fail at the same time.
But he's right - both systems share the same internet. Completely
different than your cell phone and laser printer. This includes, among
other things, the DNS system, which isn't necessarily independent of
other parts of the internet.
They are a common point of failure.
DNS failover can increase web server uptime. That is a
basig engineering calulation that has been tested many
times of many systems.
"Arguing with anonymous strangers on the Internet is a sucker's
game because they almost always turn out to be -- or to be
indistinguishab le from -- self-righteous sixteen-year-olds
possessing infinite amounts of free time."
-Neil Stephenson, _Cryptonomicon_
--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp. js*******@attgl obal.net
=============== ===
Hi
On Mon, 27 Oct 2008 23:09:08 +0000, Guy Macon wrote:
viza wrote:
>>Guy Macon <http://www.GuyMacon.co m/wrote:
>>How to increase web server uptime with DNS failover:
>>Two servers with 99% uptime will also be down at the same time one day
out of ten thousand. Three at 99% will be down at the same time one
day out of a million.
...as long as they run different operating systems
>>and different servers
>>and host different websites,
Nope. two servers in different places won't go down at the same time
just because the are serving the same HTML.
Just as an example: consider a site that goes down because of a
vulnerability in some bloated php cms. If your two machines are running
the same cgi scripts then they are more likely to both go down.
Redundancy does increase uptime, but to claim to be able to calculate it
quantitatively without in depth analysis of the likelihood and
independence of every possible source of downtime is like picking numbers
out of a hat. In case you don't have a degree in statistic and several
years worth of logs for a few thousand servers then you are just making
numbers up out of nothing.
Your advice is worthwhile and may even be helpful to people, but your
numbers are just a fantasy.
viza wrote:
>
Guy Macon <http://www.GuyMacon.co m/wrote:
>viza wrote:
>>>Guy Macon <http://www.GuyMacon.co m/wrote:
How to increase web server uptime with DNS failover:
Two servers with 99% uptime will also be down at the same time one day
out of ten thousand. Three at 99% will be down at the same time one
day out of a million.
...as long as they run different operating systems
>>>and different servers
>>>and host different websites,
Nope. two servers in different places won't go down at the same time
just because the are serving the same HTML.
Just as an example: consider a site that goes down because of a
vulnerabilit y in some bloated php cms. If your two machines are running
the same cgi scripts then they are more likely to both go down.
Redundancy does increase uptime, but to claim to be able to calculate it
quantitative ly without in depth analysis of the likelihood and
independence of every possible source of downtime is like picking numbers
out of a hat. In case you don't have a degree in statistic and several
years worth of logs for a few thousand servers then you are just making
numbers up out of nothing.
Your advice is worthwhile and may even be helpful to people, but your
numbers are just a fantasy.
The title of this thread is "How to increase web server uptime with
DNS failover" and the text of the starting post compares multiple
servers with DNS failover with single servers. Your example of a
CGI script bringing down multiple servers would also bring down
a single server, and thus does not enter into a calculation for
increasing web server uptime with DNS failover. There are a great
number of things that are equally likely to bring down both the
single server and the multiple servers with DNS failover. The
sun going supernova, for example. If we were trying to predict
absolute reliability, we would have to account for all such
factors. If, as is the case here, we are calculating reliability
increase due to using multiple servers with DNS failover, all such
factors can be ignored.
--
Guy Macon
<http://www.GuyMacon.co m/>
Guy Macon wrote:
viza wrote:
>>Guy Macon wrote:
>>viza wrote:
Guy Macon wrote:
How to increase web server uptime with DNS failover:
Two servers with 99% uptime will also be down at the same time one
day out of ten thousand. Three at 99% will be down at the same time
one day out of a million.
...as long as they run different operating systems
and different servers
and host different websites,
Nope. two servers in different places won't go down at the same time
just because the are serving the same HTML.
Just as an example: consider a site that goes down because of a
vulnerabili ty in some bloated php cms. If your two machines are running
the same cgi scripts then they are more likely to both go down.
Redundancy does increase uptime, but to claim to be able to calculate it
quantitativel y without in depth analysis of the likelihood and
independenc e of every possible source of downtime is like picking
numbers out of a hat. In case you don't have a degree in statistic and
several years worth of logs for a few thousand servers then you are just
making numbers up out of nothing.
Your advice is worthwhile and may even be helpful to people, but your
numbers are just a fantasy.
Your example of a CGI script bringing down multiple servers would also
bring down a single server,and thus does not enter into a calculation
for increasing web server uptime with DNS failover.
If we were trying to predict absolute reliability, we would have to
account for all such factors. If, as is the case here, we are
calculating reliability increase due to using multiple servers with DNS
failover, all such factors can be ignored.
You are either contradicting yourself or demonstrating a basic ignorance
of statistics. Have you considered working for the government?
Your original statement was "Two servers with 99% uptime will also be
down at the same time one day out of ten thousand"
This assumes that all causes of downtime are completely independent,
which they are not.
You cannot just say that non-independent sources of downtime are
"irrelevant ", because they are included in the numbers that you have
already given.
Suppose you had said "two servers which independently go down for six
hours due to entirely internal hardware failure on average once a year,
and also at some unspecified interval for other reasons" then you could
calculate the uptime improvement by using redundant servers, but you
would then still have to add back onto that the downtime caused by non-
independent sources, and this would mask the majority of the miracle
effect that you are touting.
To reiterate, redundancy does increase uptime but your numbers are pure
fantasy.
viza This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Ben Allen |
last post by:
Is there a way (through a variable) to show the date of the last server
reboot i.e. when PHP last started running? As I am trying to show the
server uptime, which of course only works from the last reboot,
therefore my %ages are very low.
Cheers,
Ben
|
by: Chris Gatto |
last post by:
Hello,
My organization is currently considering the purchase of a new intranet
application server and we are looking for opinions from those who have been
down this road before. In brief the server must support the following:
- 600+ users using various ASP.Net based applications, only 2 currently but
growing over time as old legacy apps are converted;
- Some applications are mission critical, others not so much;
- DB back-end is a...
|
by: aj |
last post by:
I currently have 2 official DB2 Workgroup Edition
licenses for my 2 v8 production servers. I also have
tech support/software upgrade agreements in place
for both servers.
I am interested in building a separate backup/test DB2
server upon which I can experiment with impunity.
This backup server will not be in production in any way,
and the only person who will ever connect to it is me.
It will be up and online most if not all of the...
|
by: news.microsoft.com |
last post by:
Is there an elegant way to clear out the ADO connection pool used by the SQL
Server State Service following a cluster failover?
We are using a SQL Cluster to store both the ASP Session State database and
our application database.
When the SQL Server cluster is failed-over, any "pointers" to the live
connections stored in the connection pool are made invalid. When the
application tries to reference these "damaged" connections, it throws...
|
by: |
last post by:
My scenario is that I have two webservers/database servers that I'm trying
to make redundant in terms of filesystems, web services, and database
services:
+ filesystems are replicated using server 2003 R2
+ web services are made redundant using NLB
+ databases are mirrored via SQL Server 2005 database mirroring.
I have ASP.NET and ASP applications that consult the database. These
applications are being mirrored by virtue of the fact...
| | |
by: Mark D Powell |
last post by:
I have a production failover cluster running SQL Server 2000 at SP3
that I want to upgrade to SP4. I do not have a test failover cluster
to test with so I need the install on the primary server to work the
first time. Per the information I have I just install the patch on the
primary server and it will install both on the primary and on the
secondary.
However, I remember when I did the initial install and it failed. The
first problem...
|
by: Jay Balapa |
last post by:
Hello,
We have two Windows 2003 servers one running IIS and another for SQL Server.
We are at a stage where we need to load balance and provide a failover.
Can you show us a technical document which can help us do that?
Thanks.
-jay
|
by: streamkid |
last post by:
hello..
could anyone please help me build a uptime script for openbsd?
i tried phpsysinfo, it doesn't work (only uptime works, and that's
around 15k days :p)
i tried these:
<?php
$uptime_output = system("uptime", $uptime_output);
print $uptime_output;
?>
|
by: Vinod Sadanandan |
last post by:
Fast-Start Failover An Overview In Dataguard Environment
=============================================================================
This article describes the automatic fast start failover configuration and the conditions for trigerring a fast start failover in dataguard environment .
In Faststart failover dataguard configuration if the primary database becomes unavailable, the...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
| | |
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
| | |
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |
