Open table of contents
Conclusion
Derive retention from recovery windows and deletion constraints before storage configuration.
Context
Delayed detection can make recent backups insufficient for returning to a clean state. Derive retention from recovery points and detection delay.
Design and verification scope
Assess the following responsibilities and boundaries when designing and verifying a configuration.
- Detection delay
- Recovery points
- Retention
- Legal hold
- Storage cost
- Deletion
Decision rationale
Use the relationship between Detection delay and Deletion to compare the responsibilities of the selected approach and alternatives. Separate retained constraints from what the new boundary can change.
Trade-offs
Compare the implementation, maintenance and review work introduced by Recovery points with the control it provides. Include failure paths, operator effort and conditions in which the approach should not be adopted.
Limitations
Record detection assumptions, recovery points, legal review and costs, including restrictions on shortening Compliance retention.
Related case context
These cases provide attributed design context. They do not establish that the proposed experiments or configurations were delivered in those engagements.