[atYevP]

Yev from Backblaze here -> Cloud Storage services are better suited for that much data. I wrote a post recently where I went in to the differences between Sync, Backup, and Storage as it relates to the cloud -> https://www.backblaze.com/blog/sync-vs-backup-vs-storage/.

I'm not sure what happened in this user's case - but my guess is that something happened on their machine where our backup client decided that data on the machine didn't match with what is in the DC and restarted backing up the data so that we'd have a clean copy, resulting in 13TB of data getting re-scheduled for backup.

[mistermann]

For a backup service, you seem strangely unconcerned about what went on here.

[atYevP]

I wouldn't say that, it's just that I don't have a lot of data about this particular case to go on. In some cases if you overwrite our index files, you can get something that's known as a Safety Freeze. Again - I have no idea what happened with this customer, but I would venture to guess that since this occurred on their C: drive, something similar to what causes a Safety Freeze (https://help.backblaze.com/hc/en-us/articles/217666178-Safet... happened here, and they needed to re-upload the data (in most cases, previously uploaded data is still available for restore - but with 13TB of data to re-upload and not a lot of bandwidth, it would have taken them way longer than our 30-day history to do that).