Recovery Time Objective, or RTO, is a key metric informing an MSP’s business continuity and disaster recovery (BCDR) solution choice and deployment decisions. Knowing how much downtime will cost an organization is critical for understanding what kind of investment in BDR makes sense for your clients’ businesses. A solid RTO number allows an MSP to weigh their clients’ economic tolerance for how much data loss and downtime they can afford to suffer and compare it against the investment they’ll choose to make in backup and disaster recovery systems.
Another important consideration is the shorter RTO an MSP can deliver using Axcient’s patented Local Cache feature in their Direct-to-Cloud (D2C) deployments. Local Cache enables x360Recover D2C to deliver fast RTO for our partners; it is an “expediter” and allows you to virtualize via an on-premise Hyper-V deployment.
Enter Your Recovery Data:
Important Best Practices
- While cloud virtualization in the Axcient cloud takes just a few minutes, failing over to the cloud also requires failing back and downloading the data (subject to above speeds).
- A physical shipment of data from the cloud is an available paid service, but can take hours or days to copy the data to the physical disk, encrypt it, and ship via next flight out.
- If your estimated RTO above is more than 2 hours, use a Local Cache or local appliance to ensure fast recovery if your customer loses a server.
- The Recovery Center software is optimized for recovery from Local Cache or an appliance only. Use FTPS for fast data recovery from the cloud.
- Recovering from a Local Cache requires a local machine with at least 300 MB of RAM per TB of data stored in the local cache (max 10 TB per cache).