How to set up automated offsite backups using Backblaze B2 or Wasabi for your Brisbane small business
Summary
This guide helps you troubleshoot and resolve: How to set up automated offsite backups using Backblaze B2 or Wasabi for your Brisbane small business. Follow the steps below to fix the issue.
Common Causes
Offsite backups ensure that your critical business data remains safe even if your local hardware fails, is stolen, or is compromised by ransomware. By using cloud object storage such as Backblaze B2 or Wasabi, Brisbane small businesses can implement a cost-effective "3-2-1" backup strategy without investing in expensive physical infrastructure.
Choosing Your Cloud Storage Provider
Both Backblaze B2 and Wasabi provide S3-compatible object storage. While Backblaze B2 is often preferred for its flexible pricing and ease of entry, Wasabi is known for having no egress fees, meaning you aren't charged when you download your data during a restore. However, Backblaze B2 charges for data egress, which can significantly increase costs during a full disaster recovery restore.
- Backblaze B2: Best for businesses wanting a simple setup and predictable monthly storage costs. Be mindful of egress fees when restoring large volumes of data.
- Wasabi: Best for organisations that frequently restore large volumes of data without incurring egress charges.
Provider Endpoint URLs
When configuring your backup software, you must enter the correct S3-compatible endpoint for your chosen region.
- Backblaze B2:
s3.us-west-004.backblazeb2.com(Example US West endpoint; check your B2 console for your specific region). - Wasabi:
s3.wasabisys.com(Use region-specific endpoints such ass3.ap-southeast-2.wasabisys.comfor Asia Pacific/Sydney to reduce latency for Brisbane businesses).
Quick Fix Steps
- Create an account with Backblaze B2 or Wasabi.
- Create a "Bucket" (a storage container) in your chosen provider's console.
- Generate an Application Key (Access Key and Secret Key) for authentication.
- Install backup software that supports S3-compatible storage (e.g., Veeam, Duplicati, or Cyberduck).
- Configure the software to point to your bucket using the Application Keys.
- Schedule automated daily or weekly backups.
Detailed Instructions
1. Setting up your Storage Bucket
- Log into your Backblaze B2 or Wasabi management console.
- Select the option to Create a Bucket.
- Give your bucket a unique name (e.g.,
brisbane-business-backups). - Set the bucket to Private to ensure your data is not publicly accessible.
- Save the bucket configuration.
2. Generating Application Keys
- Navigate to the Security or Keys section of your provider's dashboard.
- Click Add a Key or Create Application Key.
- Assign the key permissions to Read and Write for your specific bucket (Backblaze B2). For Wasabi, generate Access and Secret Keys at the account level.
- Copy the
Application Key IDandApplication Keyimmediately. You will not be able to view the secret key again after closing the window.
3. Enabling Object Lock for Ransomware Protection
Object Lock (or Object Immutability) prevents backup files from being deleted or modified for a set period, protecting your data against ransomware.
Backblaze B2
- Log into the Backblaze B2 web console.
- Navigate to Buckets and select your bucket.
- Click Bucket Settings.
- Toggle Object Lock to On.
- Select Compliance Mode for maximum protection (cannot be disabled once enabled) or Governance Mode for flexibility.
- Set the default retention period (e.g., 30 days).
- Click Save Changes.
Wasabi
- Log into the Wasabi console.
- Navigate to Buckets and select your bucket.
- Click the Object Lock tab.
- Click Enable Object Lock.
- Choose Compliance or Governance mode.
- Set the retention period in days.
- Click Apply.
4. Configuring your Backup Software
Specific menu paths and button names for common S3-compatible backup tools:
Veeam Backup & Replication
- Open Veeam and go to Backup Infrastructure.
- Right-click Backup Repositories and select Add Backup Repository.
- Choose Object Storage as the repository type.
- Select S3 Compatible from the vendor list.
- Enter the Endpoint URL (e.g.,
s3.ap-southeast-2.wasabisys.com). - Enter your Access Key and Secret Key.
- Select your bucket from the Bucket dropdown.
- Click Next and Finish to add the repository.
Duplicati
- Open Duplicati and select Add backup.
- Choose Configure a new backup.
- Set Destination type to S3-compatible storage.
- Enter the Endpoint URL for your provider.
- Enter your Access Key ID and Secret Access Key.
- Enter your Bucket name.
- Click Test Connection before saving.
Cyberduck
- Open Cyberduck and click Open Connection.
- Select Amazon S3 from the dropdown.
- Enter the Server (Endpoint URL).
- Enter your Access Key ID as the Username.
- Enter your Secret Access Key as the Password.
- Click Connect to browse your buckets.
5. Scheduling Automated Backups
- Navigate to the Schedule settings within your backup job.
- Select a frequency (Daily is recommended for most small businesses).
- Set a time outside of business hours to avoid impacting network performance.
- Enable Email Notifications so you are alerted if a backup fails.
- Save and run a manual test backup to verify the connection.
6. Encryption and Data Security
Ensure your data is protected both while moving to the cloud and while stored:
- Encryption in Transit: All connections to Backblaze B2 and Wasabi use TLS/SSL encryption. Ensure your backup software is configured to use HTTPS.
- Encryption at Rest: Enable server-side encryption (SSE-S3) in your provider console. For additional security, enable client-side encryption within your backup software so that data is encrypted before it leaves your Brisbane office.
7. Retention Policies and Lifecycle Rules
Define how long backups are kept to manage storage costs and meet compliance requirements:
- Daily backups: Retain for 30 days.
- Weekly backups: Retain for 12 weeks.
- Monthly backups: Retain for 12 months.
- Configure Lifecycle Rules in your provider console to automatically transition older backups to cheaper storage tiers or delete them after the retention period expires.
Brisbane and Australian Considerations
Small businesses in Brisbane should consider the following local factors:
- Data Residency: Choose a storage region located in Australia (e.g., Sydney) to keep data within the country and reduce latency.
- Compliance: Ensure your backup strategy aligns with the Australian Privacy Act 1988 and the Notifiable Data Breaches (NDB) scheme.
- Latency: Using an Asia Pacific/Sydney endpoint for Wasabi or the nearest Backblaze region improves upload speeds for Brisbane-based offices.
Testing Disaster Recovery and Documentation
A backup is only useful if you can restore from it. Follow these steps to verify recoverability:
- Monthly Restore Test: Restore a random selection of files to a test machine to verify integrity.
- Quarterly Disaster Recovery Test: Simulate a total hardware failure by restoring a full system image to different hardware.
- Document Procedures: Create a written recovery plan that includes step-by-step instructions, provider login details (stored securely), application key locations, and contact information for your MSP.
- Assign Responsibility: Designate a staff member responsible for monitoring backup alerts and performing restore tests.
Maintaining Your Backup Strategy
Setting up the backup is only the first step. To ensure your data is actually recoverable, follow these maintenance tips:
- Test Restores: Perform a test restore of a random file once a month to ensure the data is not corrupted.
- Monitor Alerts: Regularly check your backup logs for failure messages.
- Review Storage: Monitor your bucket size to ensure you are not exceeding your allocated budget.
- Billing Alerts: Set up billing alerts in your Backblaze B2 or Wasabi account to be notified when storage costs exceed a specific threshold. This is especially important for Backblaze B2 due to potential egress charges.
Troubleshooting Common Setup Failures
Authentication Errors
- Cause: Incorrect Access Key ID or Secret Access Key.
- Fix: Regenerate keys in the provider console and update them in your backup software. Ensure there are no trailing spaces when copying keys.
Bucket Not Found
- Cause: Bucket name typo or bucket created in a different region than the endpoint URL.
- Fix: Verify the bucket name matches exactly and ensure the endpoint URL corresponds to the region where the bucket was created.
Network Timeouts
- Cause: Firewall blocking outbound HTTPS traffic or incorrect endpoint URL.
- Fix: Ensure port 443 is open for outbound traffic. Verify you are using the correct regional endpoint (e.g.,
s3.ap-southeast-2.wasabisys.comfor Sydney).
Schedule Failures
- Cause: Backup software service not running or computer powered off during scheduled time.
- Fix: Ensure the backup service is set to start automatically and the machine is powered on during the backup window.
If you encounter issues during setup or need assistance selecting the right provider for your organisation, please Open a Ticket.
Still Having Issues?
💻 Open a Ticket