background banner image

Disaster Recovery & Business Continuity

70% of companies that suffer a major IT disaster, without a valid recovery plan in place, fail within the next year. Of those that do survive, only 10% make a full recovery.

DR implementation and configuration depends on two important factors – recovery time objectives and recovery point objectives. RTO indicates how quickly you can restore data – usually minutes or hours, and in some cases days. Some operations and data types may tolerate very little time to recover, while others can survive longer delays. RPO indicates how much data loss you can tolerate, and that determines how often you replicate data – every hour, three times per day, etc. Many organisations define different RTOs and RPOs across the enterprise – uniformity is not important as long as you can easily and affordably match data types to protection levels.

Business continuity (BC) differs from data protection and disaster recovery because it describes not only a level of protection that speeds recovery, but also a strategy that makes recovery speed less important. With BC, it’s not about how long it takes to get back in operation – it’s about staying in operation regardless of the failure, outage, attack, or corruption. For example, if you have a duplicate data centre at another location with data copies, you can quickly bring operations online at the new location.

There are a number of disaster types including software failure, hardware failure and complete site failure that can affect an organisation's overall potential to operate. Software failure will have an impact on an individual application and cause a disruption to the service.

We can help you to design and implement process, technology, logistic and facility solutions that meet the needs of your business at a realistic cost.