Disaster Recovery

— Do you have a plan, Mr. Fix?

— Do I have a plan?


Does your company have a plan for a disaster recovery of its IT systems? That's the question every CTO should be asking themselves. Failure to plan for contingencies can result in loss of important data even as a result of a minor technical issue or human error. The consequences are well known: the company loses money and often also loses face.

A famous US movie studio lost the results of months of work by the entire staff of the company when an employee accidentally wiped the server. The kicker was that the server's backup function hadn't been working for more than a month. Experts estimate that businesses around the world lose about USD 1.7 trillion a year for good due to irrevocable loss of valuable data that were never backed up for some reason or another.

A disaster recovery plan is how you can guarantee that a failure in your IT system will be nothing more but a minor inconvenience and won't result in catastrophic data loss, impacting your company's performance and undermining the profitability of its operations. In addition, a good DRP will also reduce the time of recovery and the risks of a repeat occurrence of the same situation.

A disaster recovery plan must be developed in a comprehensive and careful manner, and its viability directly depends on the competencies and experience of the people that develop and execute it. You need to plan for hundreds of contingencies and take into account thousands of details and specific features of your corporate information and communication systems. What makes the task even more challenging is the fact that every organization has a unique ICT system.

In the years that STEP LOGIC has been developing DRPs for its clients, we've developed a carefully crafted procedure for it. Every stage specifies the steps that must be taken and that means that certain algorithms must be put in place. And following these algorithms ensures we can develop a failsafe DRP for any organization.

Stage 1

At this stage, we identify the IT processes and resources that are critical to the functioning of the organization. For each resource, its importance is determined, so is the degree to which it is interconnected with the other resources, and then various options for backing it up are considered.

Stage 2

At the second stage, we decide on which tools we're going to use to protect the client's IT resources. These may be organizational solutions or technology solutions, such as mirroring, clustering, backup, and replication. The result of this stage is a concept that describes the behavior of every system after a failure and the procedures for the IT department to follow when responding to a failure.

Stage 3

Then, it comes time to deploy and test the solutions, and during this stage we work on specific elements of the plan in detail and prove the plan's overall viability. 

As a result, the customer ends up with a comprehensive and fully tested disaster recovery plan for their IT systems to prevent a negative impact of such unpleasant but very common occurrences as media failure, network equipment problems, software, hardware or human error, power outage, etc. 

— So do you have a plan, Mr. Fix?