Two recovery objectives

RTO specifies how long recovery may take. RPO specifies the point to which data must be recovered. State separate targets for order entry, execution history, statements and collateral records. The consequences of downtime and lost changes differ by component. NIST · Recovery Time Objective ↗ NIST · Recovery Point Objective ↗

A failover example

An order gateway accepts connections 12 minutes after a failure. The restored local log ends four minutes before the outage. The gateway meets a 15-minute RTO, but a one-minute RPO still requires recovery. Venue logs or drop copy may fill the gap after reconciliation.

What to verify

Record the failure time, service recovery time and last validated event for each source. Document how missing executions and duplicates were handled. Reconcile orders that were in flight before reopening the flow of requests.