Table of Contents
1. Objectives
2. Stakeholders
3. RTO/RPO Targets
4. Hurricane Trigger Points
5. Communication Plan
6. Pre-Hurricane Preparations
7. Activation of Failover
8. Monitoring and Maintenance
9. Activation of Failback
10. Post-Event Analysis
11. Updates and Revisions
1. Objectives
- To ensure uninterrupted data center operations during a hurricane.
- To provide a systematic approach to failover and failback.
2. Stakeholders
- Data Center Engineers
- Management
- IT Support
- External Vendors
- Clients
3. RTO/RPO Targets
Recovery Time Objective (RTO)
The maximum acceptable time to restore operations after a disaster event.
Our RTO goal is 4 hours to restore critical systems during a hurricane failover scenario.
Recovery Point Objective (RPO)
The maximum acceptable data loss in the event of disruption.
Our RPO goal is 1 hour – we can accept up to 1 hour of potential data loss.
Aligning Procedures with RTO/RPO
- Data synchronization between sites should occur at least every 1 hour to meet RPO.
- The failover process itself should take no longer than 3 hours to complete to stay within RTO.
- Follow-up data sync after failover completes to capture final changes.
- Failback process should also adhere to the 4-hour RTO.
- Have procedures for partial failover of critical systems first to meet RTO.
- Test failover/back quarterly to confirm we meet RTO/RPO goals.
- Compare actual recovery times during tests to the targets and adjust procedures accordingly.
4. Hurricane Trigger Points
Failover Triggers:
- Hurricane Watch: When a Hurricane Watch is issued for the area, begin pre-hurricane preparations. They are issued 48 hours in advance.
- Hurricane Warning: When a Hurricane Warning is issued for the area, initiate failover procedures. They are issued 36 hours in advance.
5. Communication Plan
- SMS alerts
- Emergency hotline
- Video conferencing
6. Pre-Hurricane Preparations
When: Triggered by a Hurricane Watch 48 hours
Who: Data Center Engineers, Management
- Verify that the backup data center is fully operational and capable of meeting RTO/RPO targets.
- Ensure synchronization of all data at least every 1 hour.
- Check hardware health and pre-allocate resources for quick failover to meet RTO.
7. Activation of Failover
When: Triggered by a Hurricane Warning 36 hours
Who: Data Center Engineers, Management
1. Inform engineers via the emergency hotline and SMS.
2. Ensure failover can be completed within 3 hours to meet RTO.
3. Perform the failover process.
4. Confirm the success of failover within RTO.
5. Inform all stakeholders that the failover was successful.
8. Monitoring and Maintenance
When: Throughout the hurricane event
Who: Data Center Engineers (at the backup site), IT Support
- Monitor performance and fix any issues immediately.
- Keep stakeholders updated on the situation.
9. Activation of Failback
When: 48-72 hours after the hurricane has passed and local conditions are confirmed stable
Who: Data Center Engineers, Management
1. Assess the condition of the primary data center.
2. Ensure failback can be completed within 4 hours to meet RTO.
3. Perform the failback process.
4. Confirm the success of failback within RTO.
5. Inform all stakeholders that failback was successful.
10. Post-Event Analysis
- Evaluate the performance and effectiveness of the BCP.
- Update the BCP based on the experience and data collected.
11. Updates and Revisions
- Regularly review the BCP at least once a year to account for new risks, technologies, and operational changes.
This integrated plan provides a framework to adapt to your specific needs. Make sure to involve all stakeholders in both planning and regular updates. Also, periodic simulation exercises help prepare everyone for real-world scenarios.