Backblaze B2¶
Mount a Backblaze B2 bucket as a Windows drive via B2's S3-compatible API.
Before you begin¶
You need an Application Key: the keyID is the access key and the applicationKey is the secret.
Where to get the keys — on the Application Keys page of the Backblaze console: click Add a New Application Key, choose the bucket scope, and copy the applicationKey — it is shown only once.
The key must be S3-API capable — the account master key, and keys created before B2's S3 API launch, do not work with the S3 endpoint; create a new application key instead — see Backblaze: S3-compatible app keys.
Help from Backblaze
Connect¶
- Click Add in the toolbar.
- Choose Enterprise → Backblaze B2.
- Enter the keyID as Access Key ID and the applicationKey as Secret Access Key, then click the Refresh button next to the bucket field.
- Select the bucket and click Connect.
Manual bucket entry
If your key is not allowed to list buckets, tick the checkbox to the left of the bucket field and type the bucket name directly.
Settings¶
| Setting | Description | Default |
|---|---|---|
| Access Key ID / Secret Access Key | B2 application key's keyID / applicationKey | — |
| Bucket | The bucket to mount (list or manual entry) | — |
| Read-only | Blocks writes to the mounted drive | off |
Behavior & limits¶
- The drive talks to
s3.<region>.backblazeb2.com; the region is part of the bucket's endpoint shown in the B2 console. - S3 semantics: renaming a large folder tree copies and deletes every object under the prefix.
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
| Authentication fails | Master key or pre-S3 key used | Create a new application key in the console |
| Bucket list empty | Key is restricted to one bucket | Type the bucket name manually |