Disaster Recovery as a Service
Continuous replication to a secondary site with configurable RTO/RPO targets, so you can fail over and keep running instead of waiting on a restore.
Failover, not just restore
Restores lost or damaged data from a point-in-time copy. It is well suited to recovering a file, a table, or a whole server image, though the workload remains down for the duration of the restore.
Continuously or near-continuously replicates your environment to a secondary site, so when your primary environment goes down, you fail over and keep running with minimal interruption.
Most customers run both: Backup as a Service for granular, routine recovery, and Disaster Recovery as a Service for the scenario in which an entire environment, or an entire site, goes down.
Built around your recovery targets
Your environment replicates to a secondary site on a near-continuous basis rather than through a nightly job.
Set a recovery time objective that matches how fast each workload actually needs to come back.
Tune your recovery point objective to control exactly how much data you can afford to lose.
Fail over into a metro on the other side of the country, so the event that takes out your primary site cannot reach your replica.
The two numbers that define your DR plan
Every DR plan comes down to how fast you need to be back, and how much data you can afford to lose getting there.
How long your applications can be down before failover completes and service is restored. A shorter RTO means faster failover. Parallax offers configurable RTO targets tuned to the criticality of each workload.
How much data, measured in time, you can afford to lose if a failure occurs right now. A shorter RPO means more frequent replication and less data at risk. RPO is also configurable to match each workload.
Why teams plan for failover
Meet DR requirements that show up in audits and regulatory frameworks across finance, healthcare, and other regulated industries.
Keep the applications that cannot go down, including order processing, customer-facing platforms, and core business systems, running through an outage.
Protect against a full site outage caused by power, network, or physical disaster by failing over to a geographically separate location.
Fail over to a known-clean replica instead of racing to rebuild infected infrastructure from scratch.
Pick a failover metro that is genuinely far away
Every metro in our footprint can act as a DR target, which means you can put real distance, and a different power grid, weather system, and carrier mix, between your primary site and your replica.
Central and inland, away from both coasts. The default pairing for customers whose primary sits on either seaboard.
Central and inland like Dallas, but on a separate grid and weather exposure, which makes the two a clean in-country pair.
Dense carrier choice in the upper Midwest, useful when recovery traffic needs to re-route quickly toward the Northeast.
Southeast coverage on a separate grid and carrier mix from the Northeast corridor.
East Coast target with the densest carrier choice in the country for re-routing traffic after a failover.
West Coast target for customers who need to keep recovery close to Pacific users.
Second West Coast option, on a different metro grid from San Jose when you need separation without leaving the coast.
Your primary does not have to be with us. Replicate from your own data center, a colocation footprint, or another cloud provider into any of our metros. We will help you choose the target that gives you the geographic separation your recovery plan, or your auditor, actually requires.