Fault Tolerance for Intranet

Posted on 2006-05-12
Last Modified: 2010-04-11
I think largely informational systems, such as a company’s intranet (often, but maybe not always), perhaps a system for documentation, testing or development application all do not necessarily need to be fault tolerant.  These types of applications can often sustain periods of downtime without adversely affecting a company’s productivity.  Am I wrong to assume and can you explain in more detail the pros and cons.
Question by:Bellpm2006
    1 Comment
    LVL 25

    Accepted Solution

    what you are talking about is actually a semi-measureable thing.  The pro to fault tolerance is if a piece of hardware fails, who cares because another one is taking up the slack. The con of not having fault tolerance is of course the needed resource is no longer available.  

    Now I'm not a CISSP, but I've started to read some of the literature for that certifcation and everything it says is determine the likelihood of the resource being down (and for approx. how long) and times that by the supposed cost of the resource being inaccessible for that time.  Now does the cost of making the resource fault tolerant exceed the cost of losing productivity.  If so, don't go with fault tolerance.

    Example,  If they determine they will lose $100,000/hour their site is down (just pulling figure out of my butt) and they figure the likelihood of their site going down due to server failure, link failure, etc. is around 3% which equates to about 11 days worth of down time during the year, that means a potential loss of revenue of over $26 million.  

    Figuring peoples productivity is obviously different.  If you determine there is a 3% likelihood of the resource being unavailable where people cannot do their jobs without the resource. and the total salary of those employees is around lets say $100,000/hour (obviously big company), then you can figure a potential loss of $26 million worth of loss productivity.

    Mostly you're pulling numbers from your butt, but that's how I figure it.  Your decision is mostly based on does the resource being down affect someone's job.  If someone can't do their job because the Intranet site is down, or even hinders the capability of them being able to perform their job, then I'd figure it into the potential cost.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Threat Intelligence Starter Resources

    Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

    By default, Carbonite Server Backup manages your encryption key for you using Advanced Encryption Standard (AES) 128-bit encryption. If you choose to manage your private encryption key, your backups will be encrypted using AES 256-bit encryption.
    Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
    Sending a Secure fax is easy with eFax Corporate ( First, Just open a new email message.  In the To field, type your recipient's fax number You can even send a secure international fax — just include t…
    This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now