Have questions about SingleHop?
I'm here to help.
Call us toll free at 866.349.0689
Solutions for Disaster Recovery
Disaster recovery is an exercise in risk mitigation and managing economics. A disaster can be something as simple as an extended power outage in your building. Our engineers can work with you to design a disaster recovery solution that meets your economic needs as well as your business needs. It can be as simple as offsite data and server images that can be restored to the cloud in one of our globally distributed data centers and can be as complete as redundant, globally load balanced real-time operations. We will design the right solution for your business.
Do you know which solution is right for you?CHAT WITH AN EXPERT
More Solutions By Need
Stop natural and physical disasters from taking down your infrastructure by using our globally available platform.Learn More
What is Involved
The basic components of a disaster recovery solution include a secondary site that is typically geographically dispersed from the primary site, available compute resources, secondary data storage, a replication mechanism/process, and a disaster declaration process.
- Recovery point objective (RPO): RPO is the amount of time that elapses between replication of data. If the primary site goes down, this typically represents the maximum potential data lost. For instance, an RPO of 1 hour would result in a maximum of 1 hour of data loss.
- Recovery time objective (RTO): RTO is the amount of time that elapses between a disaster declaration and the time that the secondary site is up and accessible.
- Hot and warm disaster recovery sites: A hot site involves a fully functional replica of the primary site. A warm site involves a fully functional replica of the primary site with reduced compute resources. The replica is online and available. All data is present and compute resources are available and patched to the same level as the primary site. Compute resources for the warm site do not need to be 1:1 in terms of scale, but must be online and available. This is the fastest form of disaster recovery. It involves RPOs between zero and 15 minutes and RTOs between zero and 60 minutes. Note: In many businesses, a warm site is completely acceptable, as this is for disaster purposes only and should not be a long-term solution. The warm option helps with economics.
- Cold disaster recovery site: A cold site involves replicating the data and server images at periodic intervals to the secondary site. There is the expectation that some effort will be required to bring the secondary environment online. RPOs are typically in the 1 to 24 hour range and RTOs are in the 8 to 72 hour range, depending on the level of complexity and replication. This is typically the most economical solution and can be a very good first step in executing on a disaster recovery plan. Because we have available compute resources in each facility, this option is selected by many of our customers.
Disaster Planning and Declaration Process
Every company should have a disaster plan. This involves documentation of key processes and resources. A good plan also has a documented and rehearsed communications plan and key resource hierarchy. Our engineers can provide guidance on best practices to follow to implement a disaster plan that is right for your business.
Disaster Recovery Process
Let our infrastructure engineers custom design, deploy, and manage your business infrastructure. This unique service blends our proprietary automation platform with premium managed services to offer a uniquely flexible, yet fully managed hosting experience.
We start by determining what solution you need for your infrastructure. You will then work with our engineers to design your custom-built solution. Once your solution is ready for deployment, we’ll help you migrate all your data and deploy your solution. We’ll support you 24/7/365 with testing and refining your environment every step of the way.
1. Requirements Analysis
- Infrastructure assessment
- Define business case
- Define requirements and success criteria
2. Solution Design
- Architect solution design
- Collaborative review
- Budget and recommendations
3. Migrate and Deploy
- Build infrastructure
- Set up support process
- Migrate solution
- Go live
4. Production Support
- 24/7/365 support
- Troubleshoot and escalate
- Ongoing collaboration
5. Review and Refine
- Periodic review
- Report card