- Print
- DarkLight
Create and Manage Cloud Replication Rules
- Print
- DarkLight
The Backblaze Cloud Replication feature provides for replicating one or many objects to one or multiple buckets within or between regions. This feature can help to serve multiple use cases, like ensuring data set copies are geographically distributed to support disaster recovery objectives, reducing concentration risk, serving compliance needs, or helping to move data closer to end users for faster access irrespective of edge infrastructure.
You must have a separate account for each data region. For example, if your source region is US West and you want to replicate data to US East, you need accounts for both regions.
For more information about Cloud Replication, click here.
To create a Cloud Replication rule using the Native API, click here.
The following video guide walks you through configuring a Backblaze Cloud Replication rule using the Backblaze web UI.
Create a Cloud Replication Rule
- Sign in to your Backblaze account.
- In the left navigation menu under B2 Cloud Storage, click Cloud Replication.
- Click Replicate Your Data.
- Enter or select the following details:
- Enter a name for your rule.
- Select the source bucket that contains the data that you want to replicate.
- Select the destination region in which your data will be replicated.
- Select the destination bucket that will contain the data that you are replicating. Optionally, click Create New Bucket if you do not already have a destination bucket.
- If you already have a destination account, click Sign in to authenticate an existing Backblaze B2 destination account.
- Enter the email address that is associated with the destination account.
- Click Next.
- Enter the password that is associated with the destination account.
- Click Sign in.
- If you do not already have an existing destination account, click Create a new Backblaze B2 destination account.
- Enter an email address that does not already exist as a Backblaze customer.
- Enter and confirm a password.
- Enter a bucket name.
- Optionally, select Enable Encryption or Enable Object Lock.
- Click Next.
- Enter your billing information.
- Click Create.
- Click Next.
- Click Create Replication.
After you create the Cloud Replication rule, you can view it on the Cloud Replication page under B2 Cloud Storage.
Check the Status of a Replication Rule
After you set a Cloud Replication rule, you can check the status of the replication. You can do this only on the source account and only on a file-by-file basis.
Currently, you can apply only two rules for the same bucket. If you create a third rule on the same bucket, the rule fails when you attempt to create the bucket.
The file status that is returned also manages these multiple rule scenarios.
- Sign in to your Backblaze account.
- In the left navigation menu under B2 Cloud Storage, click Buckets.
- Click Upload/Download for the source bucket that includes your Cloud Replication rule.
- Click the information icon for a file that is included in the replicated bucket.
One of the following Cloud Replication statuses is displayed after you create and run a replication rule:
- Completed
This status indicates that the file was successfully replicated to the destination bucket. For multiple rules, this means both rules completed successfully. - Pending
This status indicates that this file is in the process of being replicated or is waiting to be replicated. For multiple rules, this means at least one rule is in process. - Failed
This status indicates that the file encountered an error that cannot be resolved. Files with this status are not attempted again. The only way to attempt it again is to create a new replication rule. For multiple rules, this status means at least one rule failed. You must check the destination bucket to understand which rule failed. - Replica
For files that are the result of a replication, the replication status returns “replica.” Replica files cannot be used for more replication rules.
Failed Statuses
A failed state is a non-recoverable state of the file. This state is not expected to be resolved, and this file will not be re-evaluated in its current state.
The following causes are possible:
- Permissions
Ensure that the permissions that you created for the replication rule are still present. The source bucket must have read access for the authentication key and write access for the destination authentication key. The keys are created when the Backblaze web UI completes successfully. If you remove or change the properties of how these are set up, it may cause failures. - Object Lock and Encryption
If you enabled Object Lock on the source bucket, you must also enable Object Lock on the destination bucket. Similarly, SSE-C encryption, managed by the client, is not supported. These may also return failed states. - Part Files
Cloud Replication for large files is done only after the large files are finalized (following a call to b2_finish_large_file). After all of the parts of the file are uploaded, all of the part files are queued for replication. Until the final b2_finish_large_file is run, the part files are ignored by the replication process.
If you believe that your file is a valid file and you want to retry it, the best way is to upload the file again, creating a new version. This triggers the file to be re-evaluated.
For assistance with Cloud Replication, contact the Support team.