Provider guide

Back Up a Mac to Backblaze B2

Backblaze B2 is a practical offsite destination when you want object storage priced separately from the backup app. Azivault writes encrypted repository objects to B2 through its S3-compatible API.

When this setup makes sense

Users who want independent offsite storage, predictable object storage billing, and a provider that is separate from their backup software.

What to enter in Azivault

In Azivault, choose Create New Plan, select the source folder, then go to Storage. Set Destination type to S3 compatible.

Bucket name: the bucket dedicated to the Azivault repository.
Region: Use the region assigned to the bucket. Keep the bucket region, endpoint, and credentials together in your recovery notes.
Custom endpoint: Use the S3 endpoint shown for your B2 bucket in the Backblaze console. Backblaze documents B2's S3-compatible API as using S3 syntax for tools already written for S3.
Use path-style requests: Azivault turns this on by default when a custom endpoint is present, unless you manually change the toggle.
Access key ID and secret access key: Create an application key with access limited to the backup bucket when possible, then enter the key ID and application key as the S3 access key and secret.
Session token: optional. Use it only if the provider issued one for the credentials.

Setup checklist

Create a private B2 bucket for the Azivault repository.
Copy the bucket name, region, S3 endpoint, key ID, and application key.
Use Test in Azivault before relying on the plan.
Keep Backblaze account recovery details outside the Mac being backed up.
Click Test in Azivault and wait for a healthy result before adding the plan.
Finish the schedule and recovery password steps, then add the plan.

What the storage test verifies

Azivault's S3 test is a real read/write check. It writes a small object under .azivault-health-check/, confirms the object exists, lists that prefix, reads the object back, and deletes it. If the test fails, review the bucket, region, endpoint URL, credentials, path-style setting, and network access.

Restore and disaster recovery

Existing backups remain restorable even if a subscription expires, but you still need the repository data, provider access, and the Azivault recovery password or synced Keychain key. For S3-compatible storage, plan how you would hydrate or copy the remote repository objects to a local folder, then import that repository folder into Azivault for restore browsing.

Backblaze B2 backup risks

Object lock support: B2 supports Object Lock for immutable retention, but it is a bucket and versioning decision you should make before the bucket becomes production backup storage. If you enable retention, test how your normal cleanup and emergency delete process behaves.
Lifecycle rules: B2 lifecycle rules can expire old file versions or hide/delete files after a configured age. Do not apply broad expiration rules to an Azivault repository unless you have confirmed the repository still restores across the full retention window you expect.
Egress costs: Backblaze advertises free egress up to a multiple of stored data, with overage rules after that. A full disaster restore can be much larger than a normal monthly test restore, so record the current pricing terms with your recovery plan.
Regional durability: A B2 bucket lives in the region you choose. Treat that region as the failure domain unless you have a second copy or replication plan outside it.
Access key scope: Use an application key limited to the backup bucket when possible. A broad master key can turn a stolen Mac or copied credential into account-wide storage access.
Restore gotchas: Keep the bucket name, region, S3 endpoint, key ID, application key, and Azivault recovery password together in offline notes. Without the original Mac, you will need those details before you can hydrate the repository for import.

Provider notes

Backblaze Personal Backup and Backblaze B2 are different products. Azivault uses B2 object storage, not the managed Personal Backup service.
Provider-side server encryption can be enabled, but Azivault already encrypts repository contents before upload.

Provider details can change. Check Backblaze B2 S3-compatible API docs before creating a production backup plan.

FAQs

Can Azivault back up to Backblaze B2?

Yes. Azivault can use Backblaze B2 as an S3-compatible backup destination with the bucket, region, endpoint, and access credentials described on this page.

Are files encrypted before they reach the provider?

Yes. Azivault encrypts repository contents locally before repository objects are written to folder or S3-compatible destinations.

What does Azivault's S3 test button check?

For S3-compatible destinations, Azivault writes a small health-check object, confirms it exists, lists the health-check prefix, reads it back, and deletes it.

How do I recover if the original Mac is gone?

Keep the provider account, storage credentials, and Azivault recovery password available. For remote S3-compatible repositories, hydrate or copy the repository objects to a local repository folder before importing it into Azivault.