The reason why Backblaze and Crashplan have various restrictions is due to being all-you-can-eat. At some point, they have to create an arbitrary cap. So, the

The reason why Backblaze and Crashplan have various restrictions is due to being all-you-can-eat. At some point, they have to create an arbitrary cap. So, the snapshot is a curious feature, but seems to be implemented poorly. It doesn't seem to be snapshot system, but an archive system. A snapshot is usually a point in time represented by a series of changes. By being a series of change, it would deduplicate redundant files between snapshots. It appears that this is a full archive backup, which is fine but have some limitations: * Need to upload the whole archive every time. * No deduplication. * Need to have double the space to restore (download then unzip). * No partial restores. * No encryption of personal files. If you have any technical willingness, consider restic. It is a command line utility that has the ability to backup to many backends, including B2. Being a CLI, it can be scripted. Files can be arbitrarily backed up and restored. It has encryption that the servers can never see. I also hear Duplicati is similar, but have never used it. If you want an easy way to just make archives locally and store it on B2 for cheap, consider a cloud mounter, like Mountain Duck. You can treat B2 as a drive and upload/download files as needed. Note: B2 is a _very_ simple store, so simple that it doesn't support renaming files (must download, rename, and upload). But, it is fast and inexpensive.