You can’t predict disasters. If you could, they would be less… disastrous. Since planning is the best prevention, we view disaster recovery plans as a sort of insurance policy. Some clients also use IT disaster recovery servers for production applications or for maintenance purposes.
Here’s what disaster recovery means to us
Resilient Systems — So there’s no single point of collapse, no weak links. We architect systems that withstand single component failures.
High Availability — In the event of a hardware or software failure, an IT service can provide automated failover.
Disaster Recovery — The service can be restored in the event of catastrophe.
Business Continuity — So the show goes on without a hitch.
Our design criteria utilizes disaster recovery servers and storage as development, test, sandbox, and in some cases, production resources. We use software based remote data replication products such as Quest Shareplex, Oracle, Veritas Volume Replicator, and GoldenGate. We use array based remote data replication products such as SRDF, MirrorView, Continuous Access, and others.
We have a plan
We could spend a week installing a clever system of alarms, traps and pulleys, or hire men in black suits to stand guard over your machines. Instead, we’d like to spend a week with you, creating an IT Disaster Recovery strategy. Here’s a picture of our process:
- Examine what depends upon the IT Service Environment
- Inventory and classify the IT application portfolio including Service Level Objectives
- Discuss the difference between Business Continuity planning and IT Disaster Recovery
- Define “disaster”
- Once disaster is declared, what are the communication and management practices?
- How is IT change management and system administration impacted by business critical service continuity?
- Steps to document the infrastructure and business practices.
- Develop technical requirements for security, application compatibility model, and resource requirements.
- Review and assess current system back-up and recovery plans.