How to set up and manage Backblaze B2 or Wasabi as a low-cost offsite cloud backup for your small business
Summary
This guide helps you troubleshoot and resolve: How to set up and manage Backblaze B2 or Wasabi as a low-cost offsite cloud backup for your small business. Follow the steps below to fix the issue.
Common Causes
Offsite backup is one of the most important safeguards you can put in place for your small business. Local drives fail, ransomware encrypts everything in reach, and natural events can damage your premises. Storing a copy of your critical data in a separate, geographically distant location protects you against all of these scenarios.
The good news is that cloud storage no longer has to be expensive. Services like Backblaze B2 and Wasabi offer S3-compatible object storage at a fraction of the cost of the big-name hyperscalers, making them ideal destinations for business backups. When paired with a capable backup client such as Duplicati (free, cross-platform) or Veeam (paid, Windows-based), you can build a robust, automated offsite backup solution for just a few dollars per month per terabyte.
This guide walks you through choosing a provider, creating the storage destination, configuring your backup software, verifying that your data is recoverable, and monitoring your backups over time.
Choosing a Cloud Storage Provider
Both Backblaze B2 and Wasabi are excellent choices, but they suit slightly different needs.
Backblaze B2
- Pricing: Around USD $6 per TB per month for storage, plus download and transaction fees.
- Best for: Smaller datasets, infrequent restores, customers who want a generous free tier (first 10 GB free).
- Region: Has an Australian endpoint (
s3.ap-southeast-002.backblazeb2.com) which reduces latency and egress costs for local customers.
Wasabi
- Pricing: Around USD $7 per TB per month with no egress fees and no transaction charges.
- Best for: Larger datasets, frequent restores, customers who want predictable monthly billing.
- Region: Has an Australian region (
ap-southeast-1) for data sovereignty and speed.
Both providers are S3-compatible, meaning almost any modern backup tool will work with either of them. If you are unsure which to choose, start with Backblaze B2's free tier to test your workflow before committing to a paid plan.
Wasabi's Sydney region uses the endpoint https://s3.ap-southeast-1.wasabisys.com. Ensure you use this specific regional endpoint rather than a generic S3 URL when configuring your backup client.
The 3-2-1 Backup Principle
Offsite cloud storage is only one part of a resilient backup strategy. We recommend following the 3-2-1 rule: keep at least three copies of your data, on two different media types, with one copy stored offsite. In practice, this means keeping your original data on your local devices, a second copy on a local external drive or NAS, and a third copy in Backblaze B2 or Wasabi. Cloud backups protect against fire, theft, and hardware failure, but they should complement—not replace—a local copy.
Creating Your Storage Bucket
Before configuring your backup software, you need to create a bucket in your chosen provider and generate access keys.
Backblaze B2
- Sign in to your Backblaze account and navigate to B2 Cloud Storage.
- Click Buckets in the left menu, then click Create a Bucket.
- Enter a unique bucket name (lowercase, no spaces).
- Set Files in Bucket to Private.
- Choose ap-southeast-002 as the region if you are based in Australia.
- Click Create Bucket.
- Go to Application Keys in the left menu and click Add a New Application Key.
- Give the key a name, restrict it to the bucket you just created, and set the required access (read and write).
- Click Create Key and copy both the keyID and applicationKey somewhere safe. You will not see the application key again.
Wasabi
- Sign in to the Wasabi console and select Buckets from the left menu.
- Click Create Bucket.
- Enter a bucket name and choose the ap-southeast-1 (Sydney) region.
- Click Create Bucket.
- Navigate to Access Keys in the left menu and click Create Access Key.
- Select Wasabi S3 User, assign read and write permissions, and click Create.
- Download or copy the Access Key and Secret Key. Store them securely.
Treat your access keys like passwords. Anyone with these keys can read, modify, or delete your backup data. Store them in a password manager and never share them over email or chat.
Configuring Duplicati as Your Backup Client
Duplicati is a free, open-source backup client that runs on Windows, macOS, and Linux. It supports Backblaze B2, Wasabi, and any other S3-compatible service. All data is encrypted before it leaves your computer using the passphrase you set during job creation.
Installation
- Download the Duplicati installer from the official website and run it.
- During installation, choose whether to install as a Windows service (recommended for servers) or as a user application (recommended for desktops).
- Once installed, open the Duplicati web interface (usually
http://localhost:8200) or the desktop client.
Creating a Backup Job
- Click Add backup on the home screen.
- Enter a meaningful Name for the job, such as
Daily-Business-Documents. - Set the Encryption passphrase. Use a long, unique passphrase and store it in your password manager. Without this passphrase, your backups cannot be restored.
- Under Destination, select S3 Compatible.
- Configure the destination settings:
- Server: Paste the S3 endpoint for your provider (for example,
https://s3.ap-southeast-002.backblazeb2.comorhttps://s3.ap-southeast-1.wasabisys.com). - Bucket name: The bucket you created earlier.
- AWS Access ID: Your access key.
- AWS Access Key: Your secret key.
- Server: Paste the S3 endpoint for your provider (for example,
- Click Test connection to confirm Duplicati can reach the bucket.
- Under Source Data, click + Add folder or + Add file and select what you want to back up.
- Configure the Schedule. For most businesses, a daily backup running outside business hours is appropriate.
- Review the options on the Options screen. Recommended settings:
- Retention: Keep at least 30 daily, 12 monthly, and 5 yearly versions.
- Upload volume size: 50 MB is a sensible default.
- Throttle bandwidth if you have a limited internet connection.
- Click Save.
Run your first backup manually after creating the job so you can verify it completes successfully. Subsequent backups will only transfer new or changed blocks, so they will be much faster.
Configuring Veeam as Your Backup Client
If you are running Windows Server or a virtualised environment, Veeam Backup & Replication Community Edition is a powerful option. The Community Edition is free for up to 10 workloads (virtual machines, physical servers, or workstations). This licence is intended for home lab and evaluation use; commercial use beyond the workload limit requires a paid Veeam licence. Review Veeam's current licensing terms before deploying in a production business environment.
Adding the Cloud Repository
- Open the Veeam console and click Backup Infrastructure in the lower-left corner.
- Right-click Backup Repositories and choose Add backup repository.
- Select Object storage, then S3 Compatible.
- On the Name screen, enter a descriptive name such as
Backblaze-Offsite. - On the Service provider screen, choose S3 Compatible (Other).
- Enter the following details:
- Service endpoint: The S3 endpoint URL for your provider (for example,
https://s3.ap-southeast-002.backblazeb2.comorhttps://s3.ap-southeast-1.wasabisys.com). - Region: The region you selected when creating the bucket.
- Access key and Secret key: The credentials you generated earlier.
- Service endpoint: The S3 endpoint URL for your provider (for example,
- Click Apply, then browse to and select your bucket.
- Choose a folder within the bucket if desired, then click Next.
- Review the summary on the final screen and click Finish to add the repository.
Creating a Backup Job
- In the Veeam console, click Home then Backup Jobs.
- Right-click Backup Jobs and select New Backup Job.
- Enter a name and description for the job.
- On the Virtual Machines or Computers step, add the servers or workloads you want to protect.
- On the Storage step, select the S3 repository you created earlier as the target.
- Configure the Guest Processing and Schedule options as required.
- Enable encryption for the job if you want data encrypted before it leaves your network.
- Review the summary and click Finish.
Verifying and Monitoring Your Backups
A backup is not trustworthy until you have proven you can restore from it. Schedule regular test restores and monitor job status to catch failures before you need to recover data.
Performing a Test Restore in Duplicati
- Open the Duplicati web interface or desktop client.
- Select your backup job from the home screen.
- Click Restore.
- Choose the backup version you want to restore from.
- Select the files or folders you want to recover.
- Choose a restore destination (a temporary folder is fine for testing).
- Click Restore and verify the recovered files open correctly.
Performing a Test Restore in Veeam
- Open the Veeam console and navigate to Home > Backups.
- Locate the backup job and the specific restore point you want to test.
- Right-click the backup and select Restore.
- Choose Entire VM restore, Guest files restore, or Volume-level restore depending on what you need to verify.
- Follow the wizard to select the restore destination.
- Complete the restore and confirm the data is intact.
Configuring Backup Failure Notifications
Do not wait for a disaster to discover that your backups have stopped running. Configure notifications so you are alerted immediately if a job fails.
Duplicati Notifications
- In Duplicati, go to Settings > Send notifications.
- Enable email notifications and enter your SMTP server details.
- Select the events you want to be notified about, including Backup failed and Backup completed with warnings.
- Enter the email address where alerts should be sent.
- Save the settings and send a test notification to confirm delivery.
Veeam Notifications
- In the Veeam console, go to Options > Email Settings.
- Enter your SMTP server, port, and sender email address.
- Configure authentication if your mail server requires it.
- In your backup job settings, enable Send notification emails and specify the recipient addresses.
- Choose to receive notifications on job failure, success, or both.
Monthly Verification Checklist
- Review backup job logs for failures or warnings from the past month.
- Confirm that backup jobs are running on schedule and completing within the expected window.
- Verify that retention settings are applying correctly and old versions are being purged as expected.
- Perform a test restore of at least one critical file or folder from each backup job.
- Check that notification emails are being delivered and reaching the correct recipients.
- Review cloud storage usage and billing to confirm costs remain within budget.
- Ensure access keys and encryption passphrases are still stored securely in your password manager.
Troubleshooting Common Issues
Authentication Failures
If your backup client cannot connect to the bucket, double-check that you are using the correct access key and secret key for the provider. Ensure the key has read and write permissions for the specific bucket. Remember that Backblaze uses a keyID and applicationKey, while Wasabi uses an Access Key and Secret Key.
Endpoint Mismatches
Connection errors often result from using the wrong regional endpoint. Backblaze B2 Australian customers should use https://s3.ap-southeast-002.backblazeb2.com, while Wasabi Sydney uses https://s3.ap-southeast-1.wasabisys.com. Do not mix endpoints between providers.
Throttling and Slow Uploads
If backups are taking too long or affecting business internet performance, enable bandwidth throttling in Duplicati or configure Veeam to limit concurrent tasks. Schedule backups outside business hours to minimise impact on staff.
Incomplete Uploads
Large files or unstable connections can cause uploads to fail partway through. Check your provider's console to see if objects were partially uploaded. Re-run the backup job; most clients will resume from where they left off rather than starting over.
If you continue to experience issues with your offsite backup configuration, Open a Ticket and our team will assist you.
Still Having Issues?
💻 Open a Ticket