<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RPO on Catalogic Software</title><link>https://www.catalogicsoftware.com/blog/tags/rpo/</link><description>Recent content in RPO on Catalogic Software</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.catalogicsoftware.com/blog/tags/rpo/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering RTO and RPO: Metrics Every Backup Administrator Needs To Know</title><link>https://www.catalogicsoftware.com/blog/understanding-rto-and-rpo/</link><pubDate>Fri, 20 Sep 2024 00:00:00 +0000</pubDate><guid>https://www.catalogicsoftware.com/blog/understanding-rto-and-rpo/</guid><description>&lt;p&gt;Two numbers govern most of what a backup administrator does. The first is how long the business can be down after a failure, and the second is how much data it can afford to lose. Those are the Recovery Time Objective (RTO) and the Recovery Point Objective (RPO), and they sit at the centre of any &lt;a href="https://csrc.nist.gov/pubs/other/2020/04/24/protecting-data-from-ransomware-and-other-data-los/final"&gt;disaster recovery plan&lt;/a&gt; worth the name. They get confused with each other constantly, because both are expressed in units of time and both get tighter as the system gets more important. They measure different things.&lt;/p&gt;</description></item></channel></rss>