Veeam Backup & Replication — S3-Compatible Object Storage Repository

Enterprise-grade Windows backup platform. Veeam Backup & Replication v12 and later supports S3-compatible object storage as a backup target, either as the capacity tier of a Scale-out Backup Repository (SOBR) or as a direct backup repository.

1. Prerequisites

• Veeam Backup & Replication v12 or later (v12 introduced direct-to-object storage backup; earlier versions require SOBR with a performance tier).
• A user account with Veeam administrator rights.
• Network connectivity from the Veeam server to storage.hummingtribe.com on port 443.
• Your HummingTribe S3 credentials and bucket name.

2. Get your S3 credentials

Log in to your HummingTribe dashboard → S3 Storage tab. Copy your Access Key ID and reveal your Secret Access Key (shown once — save it now). Note your bucket name.

3. Add cloud credentials to Veeam

In the Veeam Backup & Replication console, open the main menu (top-left) → Credentials Manager → Cloud Credentials → Add → S3 Compatible.

Enter:

• Access key: your Access Key ID
• Secret key: your Secret Access Key
• Description: HummingTribe S3

Click OK. The credentials are stored encrypted in the Veeam configuration database.

4. Add the object storage repository

Go to Backup Infrastructure (bottom-left navigation) → Backup Repositories → Add Repository → Object storage → S3 Compatible.

Name: HummingTribe S3 (or any label you prefer). Click Next.

Service point: https://storage.hummingtribe.comRegion: eu-central-1 (or leave the default if the field accepts it — HummingTribe ignores the region but Veeam requires a non-empty value) Credentials: select the credentials added in step 3

Click Next. Veeam contacts the endpoint and lists available buckets.

5. Select bucket and folder

Bucket: pick your HummingTribe bucket from the dropdown. Folder: click Browse → New Folder → name it (e.g. veeam-backups) → OK. A dedicated folder keeps Veeam data separate from anything else in the bucket.

Limit object storage consumption to: tick this and set a value below your plan's storage quota to avoid overage — for example, set it to 450 GB on a 500 GB plan.

Make recent backups immutable for: if your workflow requires ransomware protection, tick this and set a retention period (e.g. 7 days). HummingTribe S3 supports object lock — immutability is enforced at the storage layer.

Click Next → Apply → Finish.

6. Use the repository

Veeam v12 supports two ways to use object storage:

Option A — Direct backup target. Assign the HummingTribe repository directly as the target of a backup job. Go to Home → Backup Job → Virtual machine (or the relevant type) → on the Storage step, pick HummingTribe S3 as the backup repository. Fast to set up, suitable when you don't need a local performance tier.

Option B — Scale-out Backup Repository (SOBR) capacity tier. Recommended for production VM workloads where fast restores matter. Veeam keeps recent backups on a local performance tier (fast disk) and offloads older backups to HummingTribe S3.

To configure SOBR: Backup Infrastructure → Scale-out Repositories → Add Scale-out Repository:

1. Name: e.g. SOBR-Offsite
2. Performance Tier: add your existing local Veeam repository
3. Placement Policy: Data locality (default) — keeps related backup files together
4. Capacity Tier: tick Extend scale-out backup repository capacity with object storage → select HummingTribe S3
   • Copy backups to object storage as soon as they are created — sends every backup to HummingTribe immediately for offsite protection.
   • Move backups to object storage as they age out of the operational restore window → set the operational window (e.g. 14 days).

Click Apply → Finish. Existing and future backup jobs can now target the SOBR.

7. Run a backup and verify

From Home → Jobs, right-click the job targeting your SOBR or HummingTribe repository → Start.

Monitor progress in the History tab. The first backup uploads the full dataset — subsequent runs are incremental and only transfer changed blocks.

Once the job completes, verify the backup chain: right-click the job → Properties → Advanced → Maintenance → run a Health Check. Veeam reads the backup files from HummingTribe and validates integrity.

8. Restore from the repository

From the main console, go to Home → Backups → Object Storage (or Disk (imported) depending on tier). Find the machine or file you want to restore.

Right-click → Restore → pick the restore type:

• Entire VM — full VM restore to the original or a new location
• Guest Files (Windows) — file-level restore from within the backup
• Application Items — application-aware restore (Exchange, SQL, AD, etc.)

Veeam streams the required blocks from HummingTribe, reassembles them, and performs the restore. For large restores, consider staging via the performance tier by running a Migrate to performance tier operation first if you are using SOBR.

Manage your bucket and credentials from your HummingTribe dashboard.