Designing for Failure

You will be flooded, You will have a fire, You will lose everything. At the end of the day your backups need to hold the line between you and great loss.

We don’t design or implement a system that doesn’t assume the failure of any part within it. Failure is not only possible, it’s probable and so how do we embrace that truth changes the process we implement. Therefore we start each client a review to understand their current process and identify what gaps exist in their current protection.

Scope of Protection

Good backups begin with an understanding of what type of risks an organization can handle and what expectations you have from your backup. So we like to ask:

  • How long can you be offline?
  • How many staff will be impacted?
  • What Systems services are critical and which ones can be rebuilt?
  • What Data is critical and what can be rebuilt?

Planned Path

We take this time to understand the clients needs for uptime and scope of protection so we can put in place the correct plan. Which includes 

  • When was the last time the backups being taken were restored?
  • Is process documentation upto date?
  • What is most important to you, data, uptime, return to service?
  • In what order?
  • What do we do if any link this process fails?
  • Finally we need to know how we’re going to detect failure in this process and send out correct alerts.

Once we can satisfactorily answer these question and document a plan we move into action, monitoring and backing up your system, testing the media and reviewing and signing off with you. This process is repeated at least once a year, in many causes more often depending on the client need.

We want you to trust in our backup plan. We know failure will happen and we want you to bounce back and shake it off like nothing happened. 

Trusted backups are just one part of our 4 part wholeistc support approach.

No services found