We’re often asked why Backblaze didn’t implement S3-compatible APIs for our B2 Cloud Storage. Here are the reasons why we believe our approach has advantages over Amazon’s APIs and enables us to offer our cloud services at lower cost than our competitors.
It’s been a few months since our last “What’s New In B2” blog post, so we wanted to highlight the latest B2 developments, which include new application keys, our Java SDK, and B2 compute partnerships with Packet and ServerCentral.
All cloud storage vendors talk about data durability, but don’t tell you how they calculate what they claim. Until now. In this post, we detail the inputs and calculations for Backblaze B2’s 11 nines of durability.
If you’re ready to get started with B2 Cloud Storage, this post has tips and resources that will quickly get you up and running with B2.
Keeping a copy of your data in the public cloud is a great idea and enables you to comply with the 3-2-1 backup rule. By going beyond that and adopting a multi-cloud strategy, it is possible to save money and enhance redundancy and security by having data in more than one public cloud service.
Network-Attached-Storage (NAS) devices are great for local backups and archives of data. With the latest releases of software from QNAP, you can now sync the data on your QNAP NAS to and from Backblaze B2 Cloud Storage.
Some organizations and users have advanced needs for cloud backup and archiving. By combining general purpose object cloud storage, such as Backblaze B2, with off-the-shelf and custom integrations, a wide range of solutions can be created.
If you’re using GithHub, you want to make sure that your hard work is safe. What happens if a repository or gist is lost? Here’s a quick solution to keep a copy of your code secure in the cloud.