1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

How to Deal with Single Points of Failure: Hardware

Written by SPK Blog Post
Published on April 9, 2013

Continuing our series on why economizing in the wrong areas can leave your business at risk, it is time to start considering single points of failure. A single point of failure is a part of your IT and development system, be it human, software, hardware or administration, that if it fails, for whatever reason, leaves the rest of your system crippled, which in turn damages your business. Before you continue reading how to deal with hardware failure, it might be a good idea to have an IT assessment performed on your infrastructure.

Single-Point-of-FailureIn terms of hardware, there are lots of different pieces of equipment which can become a single point of failure. The most obvious is “the server.” Whether an email server, a file server, a source code repository or a license server, any shared server is a single point of failure.

If the server goes down employees stand up in their cubicles or at their desk like meerkats bobbing up and down to see what has happened. Where is their work? When was the last time they saved it? When will the system be back? Soon people start drifting to the coffee machines or head out for an early lunch. Business has been shutdown.

When an individual’s hardware fails, it’s inconvenient, but in general work can continue. When a shared resource fails, however, everyone is affected. Servers aren’t the only single point of failure. The underlying network including the various switches and routers is key to keeping your business running. Plus there is your Internet connection, if that was lost, what would be the effect? Then there are items like network attach storage and hardware in the development lab.

The best strategy to deal with hardware failure is two-pronged:
  1. As much hardware redundancy as can be afforded should be used. This includes servers with dual power supplies, RAID hard disk system, clusters, failover servers etc.
  2. Provide an effective response to the failure.

When the hardware fails, it’s the response to that failure which will decide the fate of your company. Who will fix it? What if the key member of the IT support staff is sick? Where will the spare parts come from? Is the IT support staff on 24×7 call? Who understands the system and how it all fits together?

Relying on an ad-hoc, hope-it-works kind of strategy will eventually kill your company, you might be lucky, things will run smoothly for years, but then suddenly at the least expected moment disaster could strike.

Using a professional IT outsourcing company to handle your IT infrastructure brings with it guarantees, expertise and safety. The best can help with everything from machine room planning to daily maintenance, from disaster planning to contingency plans, from failover configurations to disaster responses.

When the product in which you have invested large sums of money can’t launch because of hardware failure, your business and your reputation are at stake.

Next Steps:

Latest White Papers

The Next Chapter of Jira Service Management

The Next Chapter of Jira Service Management

The service industry is only becoming more competitive as the years pass, making efficient delivery vital to success. Development and Operations teams need to work together to deliver aid and Jira Service Management can help achieve this. Explore the future of Jira...

Related Resources

Exploring Modern Software Deployment Strategies

Exploring Modern Software Deployment Strategies

Deploying software can feel like a gamble due to all the strategies and solutions on the market, but it doesn’t have to be. Discovering which software deployment strategy works best for your organization is a great place to start. This strategy, combined with a modern...

Automatically Visualizing Dependencies in Codebeamer

Automatically Visualizing Dependencies in Codebeamer

If you work in the software and systems engineering space, you likely understand that managing dependencies across multiple components and requirements is critical for project success. Unfortunately, specifications can be difficult to track, and dependencies hard to...