Shaw Systems Disaster Recovery and Business Continuity Plan
- Backups – We have scheduled backup of all our systems.
- Redundant Storage – All of our applications run on redundant storage.
- Redundant Server Hardware – All of our servers are redundant and if we lost a physical server we could run the logical servers on backup hardware.
- Clusters – We also have high availability clusters that allow multiple servers to work as one. We could lose one and the system would still operate.
- Multisite Redundancy – We have 2 offices with replicated setups to allow us to run applications out of either or both office.
Once critical applications have been reviewed, at what point do each of the applications need to operate in order to ensure business operations remain stable? And what time frame is required for full recovery of services and applications?
Depending on the application we can absorb an uptime of 99% without any issues. That being said we aim for a 99.99% uptime and consistently meet that goal. Our Recovery Point Objective is 1 to 2 hours maximum, depending on the application, it could be as low as a few minutes.
What kind of testing do we have in place to test our strategy plan in the event of a disaster?
We require annual testing but usually test 2 to 4 times a year including maintenance of failovers and other events. This testing involves complete fail over of systems and using them as the production system. We also monitor and test our backups, hardware, and network connections regularly.