Quota based on optimized storage
If 100 GB of protected versions occupies 9 GB in the repository, the plan uses 9 GB—not 100 GB.
- Quota basis
- Physical encrypted repository bytes
- Included overhead
- Packs, indexes, and metadata
- Dashboard
- Protected, used, and saved
One honest number for the storage SaveState actually holds
Customer-visible storage matches the encrypted bytes occupied by the Kopia repository. This includes every retained version and the repository structures that genuinely consume cloud storage.
The original source size remains visible as a separate statistic. That lets customers understand how much data their restore points represent without charging them for duplicated logical bytes that Kopia did not store twice.
Cleanup before a near-quota block
Expired or deleted snapshots can leave reclaimable blocks until full repository maintenance finishes. Near the plan limit, the client asks the service for storage-pressure information and runs cleanup before deciding that a new backup must be blocked.
If optimized storage is still full after maintenance, the backup stops with a clear action: remove a retained backup or move to a larger plan. A separate private safety buffer protects the storage service while cleanup is in progress.
Put this feature into a recovery plan
Install SaveState on Windows, protect a representative data set, and test the restore before it is urgent.
Choose a plan