Replication and the recovery objectives

A fictional organization agrees that its profile-data recovery objective permits at most fifteen minutes of lost committed changes and that usable service should return within two hours for a defined user group. A storage design replicates changes to another location, and the proposal describes this as a complete backup solution. During a test, an accidental deletion propagates to both copies. An older protected snapshot remains available, but its latest verified consistent point is forty minutes before the deletion. The recovery team restores it in seventy minutes, then spends another thirty minutes validating identity, profile access and the users' applications. The manager wants to mark the test as a complete success because the restore command finished in less than two hours. The architect must assess both objectives and recommend the specific remaining work.