RPO RTO - ghdrako/doc_snipets GitHub Wiki

  • RPO(Recovery Point Objective) is a common term in business continuity. In the context of a database system, it describes the amount of data that may be lost following an unexpected outage before it is once again operational. It's important to understand this at an early stage because it will drive decisions such as node count, data synchronization methods, and backup technologies
  • RTO (Recovery Time Objective) this is the amount of time an outage of the database layer may last. Often, it is incorporated into a Service Level Agreement (SLA) contract presented to clients or assumed as a metric within the application stack. Like RPO, this is a contractual-level element that can determine the number of required nodes at steadily increasing expense as the amount of tolerable downtime decreases.
Uptime % Daily Downtime Weekly Downtime Monthly Downtime Yearly Downtime
99% 14m 24s 1h 40m 48s 7h 18m 18s 3d 15h 39m 30s
99.9% 1m 26s 10m 5s 43m 50s 8h 45m 57s
99.99% 8.6s 1m 1s 4m 23s 52m 36s
99.999% 0.9s 6s 26.3s 5m 16s