Backblaze B2 Cloud Replication
Automatically copy data from one location to another for redundancy, compliance, and fast local access.
Automatically copy data from one location to another for redundancy, compliance, and fast local access.
Creates 2x backups for disaster recovery, compliance.
Proximity places data closer to teams for more local access.
Works automatically per rules you set via API or Web UI.
Replicating your Backblaze data is easy and free—no service or egress fees—just the standard Backblaze B2 storage rates.
Backblaze does not charge service or egress fees for replication. Standard Backblaze B2 Cloud Storage rates apply to replicated data storage.
No. Backblaze data storage costs do not differ from one region to another, and you do not incur any service or egress fees. Standard Backblaze B2 storage rates apply to replicated data storage. In practical terms, this means if you use Cloud Replication to store your 1PB of data in two regions, you will incur cost for a total 2PB of storage.
Getting started with Cloud Replication is quick and easy. First, ensure you have a Backblaze B2 account in each region where you would like to store replicated data. Then, sign in to the Backblaze B2 account you wish to replicate data from and click on Cloud Replication in the left-hand navigation of your account. Create a replication rule and click confirm. Your data will start replicating automatically.
Detailed instructions on creating a replication rule are available in our technical documentation. To learn about setting up a Cloud Replication rule using the Backblaze web console, click here. Or to create a Cloud Replication rule using the Native API, click here.
Replication times will vary based on the number of files you replicate. Initial replication of a large dataset usually takes longer than any subsequent replications. For subsequently uploaded files, replication begins when you upload a new file to a replication-enabled bucket. For existing files, replication occurs each day at midnight UTC. If the replication fails with a non-fatal error, the replication automatically retries after midnight UTC the following day.
