Brian from Backblaze here. > If their building catches fire, you're SOL. We call this the "meteor hits our datacenter" scenario. With the Backblaze Online Ba

Brian from Backblaze here. > If their building catches fire, you're SOL. We call this the "meteor hits our datacenter" scenario. With the Backblaze Online Backup product, the hope is your laptop isn't hit by the same meteor so you still have a primary copy of the data. But I'm a HUGE believer in having two lower redundancy backups stored with completely different technology backed up by two separate companies that don't share a single line of code. In two separate locations. For example, make a local copy onto an external USB hard drive, and use Backblaze for a remote copy in case your house burns down. It would also be Ok to put one copy in Amazon S3 and a separate copy in Microsoft Azure, and try to use two separate pieces of software to do each of those backups. The main reason to use two different companies is in case a bug exists in the backup software. The same bug won't hit both backups at the same time.