> For the complete documentation index, see [llms.txt](https://moverdocs.files.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moverdocs.files.com/connections/object-storage/s3-compatible-storage/backblaze-b2.md).

# Backblaze B2

## Connections

Create a new connection and choose <code class="expression">page.vars.VENDOR\_NAME</code> as its type.

Provide a *Connection Label* so you can identify the connection in a list. This is especially useful when you have more than one connection of the same type.

### Bucket Details

Enter the name of the bucket to use for the connection.

Enter the endpoint for your Backblaze bucket. It will have a format like `https://s3.<region>.backblazeb2.com`.

### Credentials

Mover uses an access key and secret key to authenticate S3 requests. In Backblaze B2, these values are named *Key ID* and *Application Key*.

You can use the Backblaze web console to create Application Keys (or App Keys) for this connection. We recommend generating separate keys for each bucket, rather than one key for all buckets. You can also grant read/write access or limit it to read-only; Mover needs read/write access to copy files to the bucket.

## <code class="expression">page.vars.VENDOR\_NAME</code> is Case Sensitive

Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.

Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.