Recovery Time Objective (RTO) is a key metric informing an MSP’s BCDR solution choice and deployment decisions.
Knowing how much downtime will cost an organization is critical for understanding what kind of investment in BCDR makes sense for your client’s business.
Important Best Practices
- 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 shorter RTO an MSP can deliver using Axcient’s patented Local Cache feature in their x360Recover 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.
- The Recovery Center software is optimized for recovery from a 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).
- 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 the calculated 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 the next flight out.
- Learn more about RTO and get step-by-step instructions on getting the most out of this calculator by visiting our RTO Calculator Knowledgebase page.
