Start with the business task
Recovery Point Objective describes the acceptable loss of recent data measured back from an interruption. Recovery Time Objective describes the target time to restore a required service. They are goals, not promises made true by entering numbers into a backup application.
A shop's ability to take payments, retrieve records and issue invoices may have different tolerances. Define targets for the workflow, including its dependencies, rather than applying one attractive number to every computer.
Establish a realistic baseline
- Ask the process owner what happens if the service is unavailable for an hour, a day or longer. Identify any existing manual workaround and its practical capacity.
- Ask how much recent work could be recreated from other records. A daily backup may leave a substantial gap even if every scheduled job succeeds.
- Compare the proposed targets with actual backup frequency, retention, restore access and measured recovery performance. Include internet speed and the availability of required hardware.
- Agree on targets that the existing arrangement can support, or document the gap and the owner's decision. This exercise does not require purchasing a new service to begin measuring reality.
Verify with a bounded restore
Restore a harmless representative file to a separate location and record how long the full workflow took. Include finding the right backup, obtaining authorised access and checking the recovered data. Download speed alone is not the whole recovery time.
For a complete application, file recovery may not establish service recovery. Databases, licences, identity services and configuration can add dependencies that need a separate approved test.
Avoid false precision
A target of fifteen minutes has little meaning if nobody measured a restore or identified who can initiate it after hours. Also distinguish a successful backup timestamp from the last consistent recoverable application state. Record uncertainty rather than presenting every job as equivalent evidence.
Maintain the decision record
Document the owner, agreed targets, measured results and unresolved limitations. Review when the data volume, staff workflow or backup method changes. The objective is to make recovery tradeoffs visible and testable, so the business knows what its current free or existing tools can realistically deliver during an interruption.
Official references
Consult the current vendor documentation if your version or screen differs.
Documentation-based draft. Commands have not all been executed against the named products in a lab. Validate configuration examples against your installed version before changing a working system.