Estimate the network traffic and retained storage created by redundant data replication. Enter the source data changed each day, the number of remote copies, compression savings, transfer overhead, and retention period. The calculator separates daily wire traffic from logical retained copies so network egress and storage capacity can be planned with the right basis.
The main result is total replication wire traffic over the retention-length period. Retained storage excludes protocol overhead because headers and retries are normally not stored as payload.
The model assumes daily change volume and savings stay constant. Full reseeds, snapshot metadata, minimum object sizes, and cross-region provider rules can add cost or capacity.
For 500 GB/day, two remote copies, 30% savings, 8% overhead, and 30 days, daily wire traffic is 756 GB. Period replication traffic is 22,680 GB, while retained compressed payload is 21,000 GB.
Usually no. Enter only copies transferred to redundant destinations, then plan source storage separately.
Transfer headers and retries consume network volume but are generally not retained as logical payload.
It models the entered daily changed-data volume. Full backups should be entered as their own scenario.
This simplified calculator uses one rate. Calculate destinations separately when their savings differ.
Enter their measured or expected percentage in protocol and retry overhead; it increases wire traffic but not retained payload.
| Variable | Meaning | Unit |
|---|---|---|
| D | Daily changed source data | GB/day |
| C | Remote copy count | copies |
| s | Compression/dedup savings | % |
| o | Protocol and retry overhead | % |