Disaster Recovery & Business Continuity
Fibernet has the ideal disaster recovery setup for your data infrastructure: host in Utah or California and failover to either facility.
- Private network backbone between Fibernet’s Silicon Valley and Utah data center facilities.
- Host near your customers in California, failover to disaster-safe Utah.
- Utah’s low power costs make disaster recovery colocation affordable.
- Variety of disaster recovery solutions to fit your recovery time and recovery point objectives.
- Office space available for disaster recovery business continuity.
- Utah is the lowest disaster risk state in the US and also has great connectivity and accessibility.
Disaster Recovery Solutions
Disaster recovery solutions vary from business to business and according to RTO and RPO objectives. Contact us and we can help build an affordable disaster recovery solution that meets your business continuity plan for your data infrastructure.
RTO / RPO and Cost
While there are a lot of backup and failover options it’s important to understand how the cost increases as you reduce the recovery time and point objectives.
High Downtime and Lowest Cost
The lowest-cost disaster recovery solution would be where you simply backup your data to a removable drive or remote archival data volume. But your downtime would be significant should you have to recover your business purely from that data.
Moderate Downtime and Moderate Cost
Moderate-cost disaster recovery solutions that might require a day or two of recovery time to get your business back to a satisfactory recovery point objective include bare metal backup, virtual machine backup, and SAN snapshots. Cost increases significantly as you make the recovery point window smaller.
Low Downtime and Moderate to High Cost
Having a virtual equivalent of your physical infrastructure is one way to have a warm failover site. Data is periodically updated on the warm failover site which also has its CPU and RAM allocations reduced until the need to scale up in case of a failover situation. Another solution is to have the data from the hardware site continuously update the virtual failover site, which has RAM and CPU resources set to the live site equivalent. The latter solution offers a lower RTO/RPO whereas the former solution is its cost-sensitive version that has an increased recovery time and point objective.
Little to No Downtime and High Cost
Mirrored hot sites are ideal for failover, especially set up in a load-balanced situation where you know it works because it’s always serving content in a round-robin traffic distribution. Data would flow from the primary site continuously and update the mirrored locations. Large organizations have data center footprints set up all around the world with this hot-mirrored site architecture.