How do I back up to Amazon S3, Wasabi, Backblaze B2 or another S3-compatible store?
Add an Amazon S3 destination with a bucket, region, access key ID and secret access key. For MinIO or any other S3-compatible store also fill in Custom endpoint URL. Wasabi and Backblaze B2 have their own provider cards.
What you need
A bucket, its region, and an access key that can list, read, write and delete objects in it (retention cleanup deletes objects). Create the bucket with Object Lock and Object Versioning off.
Amazon S3 and other S3-compatible storage
- Open Destinations and choose + Add destination, then Amazon S3.
- Fill in:
- Display name (required).
- Bucket name and Region (for example
us-east-1). - Access key ID and Secret access key.
- Custom endpoint URL: leave blank for AWS. For MinIO or any other S3-compatible store, enter its endpoint, for example
https://s3.example.com. - Path prefix (optional): a folder inside the bucket, for example
backups.
- Choose Add destination, then Test on its card.
Wasabi
Choose Wasabi and fill in the bucket, region, access key ID and secret access key. The endpoint is set from the region.
Backblaze B2
Choose Backblaze B2 and fill in the bucket, Region (for example us-west-004), Application key ID and Application key. Endpoint URL is derived from the region if you leave it blank (for example https://s3.us-west-004.backblazeb2.com).
Google Cloud Storage through the S3 type
You can use this card with a Google HMAC key and the endpoint https://storage.googleapis.com. See Google Cloud Storage.
The path prefix is used exactly as typed
On S3 the prefix is used verbatim. bw/ and bw are different keys: with the prefix bw/ an object is stored at bw//objects/..., and with bw at bw/objects/.... Disaster Recovery bundles are stored inside the prefix, at <prefix>/dr/<server-id>/. Use the same prefix when you read the store with bw-extract.
Limits to know
- BackupWall has no settings for Object Lock, versioning, storage class or server-side encryption. On an Object Lock bucket, deletes fail. On a versioned bucket, deleted objects stay as old versions and keep costing money. Do not use Object Lock or versioning, or add a lifecycle rule that removes old versions.
- Retention removes points and a later cleanup frees space. A pack file is rewritten only when it is at least 6 hours old and less than 70% in use, so used space comes back slowly. See Schedules and retention.
- Backups are stored as packs of about 32 MB. A bucket far from the server is slower per request, so BackupWall groups objects into packs and keeps many requests in flight to compensate.
- Amazon S3, Wasabi and Backblaze B2 have had no real runs by PortWall yet. They use the same S3 code that was tested on one third-party S3-compatible bucket and on Google Cloud Storage through the S3 interface.