Learn about Recovery Point Objective, including how to measure it, and leverage it in dashboards and visualizations with Metabase.
Recovery point objective (or RPO) is a metric that determines the maximum amount of data that can be lost after recovering from a complete system failure before the data exceeds what a company can handle as acceptable. The RPO tells you the maximum age required for backup files to meet the requirement set by the RPO incase a serious problem occurs. RPOs are measured in time and are important points of information to determine how often is appropriate for backing up files and determining an acceptable amount of loss that can be incurred. It’s inevitable to lose some data during a catastrophic failure, so it’s important to assess what can be lost and what can’t. Higher-priority RPOs will require backups more often, and so on.
Get Started
You’ll need to determine your RPO on a case by case basis. RPOs will be determined in time, anywhere from 0 to 48 hours depending on priority, resources, cost, and need. A shorter RPO dictates a higher priority, for example if you had medical records or financial transactions being logged, that would be a higher priority than personal information because personal information is updated less frequently by users. RPOs are based completely on data importance and the needs of your company, so it’s up to you how often you want to back up your files.
Get everyone on the same page by collecting your most important metrics into a single view.
Take your data wherever it needs to go by embedding it in your internal wikis, websites, and content.
Empower your team to measure their own progress and explore new paths to achieve their goals.
That's right, no sales calls necessary—just sign up, and get running in under 5 minutes.
We connect to the most popular production databases and data warehouses.
Invite your team and start building dashboards—no SQL required.
