Mark Gritter (markgritter) wrote,
Mark Gritter

Terminological Confusion (Work Stuff)

The acronym "RPO" stands for "recovery point objective". When this is given a definition it's something like "how old is my backup copy in the worst case". I.e., if your data center catches on fire but you're replicating to a remote site, how much data has been lost?

Unfortunately, idiomatically it seems to be used more in terms of "how often are snapshots taken". But these two quantities aren't the same thing. It might take ten minutes to replicate all your hourly snapshots. Is an RPO of 60 minutes being met? Technically no, because the last replicated data could be 70 minutes old.

So if we provide an option that says "replicate this set of VMs, with a 60 minute RPO" should we just take hourly snapshots? Would it be more or less confusing to take snapshots slightly more often in order to get them replicated within the 60-minute window?
Tags: distributed systems, storage, work
  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.