Methodology
Every number names its boundary.
The planner is a destination-neutral sizing and recovery baseline. It keeps quantities, transfer rates, and objectives separate from a provider’s implementation details.
Capacity
Current data + retained changed data
Minimum destination capacity equals current protected decimal TB plus monthly changed GB × retained days ÷ 30. It excludes deduplication, compression, metadata, application consistency, and destination-specific version behavior.
Transfer
Decimal data ÷ effective MB/s
The model converts Mbps to MB/s, applies the chosen efficiency percentage, and uses 1,000,000 MB per decimal TB. It is a planning duration, not measured throughput.
Objectives
RPO and RTO remain independent
The copy interval is compared with RPO, while the priority restore transfer duration is compared with RTO. Neither comparison validates applications or credentials.
Verification
A restore test closes the loop
The next check is a representative restore using the selected destination, retention behavior, independent access, and application-level validation.
Editorial record
Maintained by Make Your Own Tools to turn “Protect and restore data” into a defined capacity, copy topology, recovery window, and restore-test baseline. The references below provide the technical context for this planning path. Its calculation rules and planning assumptions are documented in the methodology, and affected calculations pass regression checks before the review date advances.
- Last reviewed
- Evidence set
- 3 primary references
- Calculation coverage
- 5 affected rules checked
- Planning scope
- Home backup capacity, transfer-window, recovery-objective, and restore-testing planning.
- Next check
- Destination-specific backup behavior, encryption or credential management, legal retention requirements, application-consistent backups, or recovery execution.