Veeam backup to S3-compatible object storage
Since version 12, Veeam Backup & Replication can write backups directly to S3-compatible object storage, with no local staging tier required. This guide walks through adding an S3 bucket as a backup repository in Veeam, enabling immutability with Object Lock as ransomware protection and getting block size and task limits right from the start. The examples use Hexabyte object storage as the endpoint, but the steps apply to any S3-compatible storage.
Prerequisites
- Veeam Backup & Replication 12 or later (direct-to-object backup to object storage arrived in v12).
- An S3-compatible object storage account: endpoint URL, access key and secret key.
- A bucket created with versioning and Object Lock enabled, if you want immutability. With most S3-compatible storage (including Ceph-based platforms), Object Lock must be set when the bucket is created and cannot be enabled afterwards.
- HTTPS access (port 443) from the backup server to the endpoint.
Create the bucket and S3 credentials
Create the bucket and API keys in your provider’s control panel. In Hexabyte Cloud, go to Object Storage and click Create new access key; the new access key is shown together with its secret key, so save both. The endpoint is s3.hexabyte.se.
Bucket names are globally unique, must be DNS-compliant and cannot contain dots, so a name someone else already took cannot be chosen. Pick something of your own, for example my-veeam-backups.
The commands below assume the AWS CLI is installed and your keys are configured, either via aws configure or the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.
If you plan to use immutability, the bucket must be created with Object Lock. If your panel has no option for it, create the bucket with the AWS CLI against the endpoint:
aws s3api create-bucket \
--bucket my-veeam-backups \
--object-lock-enabled-for-bucket \
--endpoint-url https://s3.hexabyte.se
Then confirm Object Lock is active:
aws s3api get-object-lock-configuration \
--bucket my-veeam-backups \
--endpoint-url https://s3.hexabyte.se
The response should contain "ObjectLockEnabled": "Enabled".
Add the repository in Veeam
- Open Backup Infrastructure, right-click Backup Repositories and choose Add Backup Repository.
- Select Object Storage, then S3 Compatible.
- Name the repository, for example
hexabyte-s3. - On the Account page: enter the endpoint URL (for Hexabyte
https://s3.hexabyte.se) in the Service point field, fill in Region, and add your access key and secret key as credentials. - On the Bucket page: select your bucket and create a folder for Veeam to write to.
- Finish the wizard. Veeam verifies the connection before saving the repository.
Enable immutability with Object Lock
On the Bucket page of the wizard, tick Make recent backups immutable for N days and set the lock period. 14 or 30 days is a common choice, depending on your policy. The option is only selectable if the bucket was created with Object Lock and versioning; Hexabyte object storage supports both.
Veeam writes the locked objects in compliance mode: for the duration of the lock they cannot be deleted or overwritten, not even by a compromised administrator account. This is the main reason to put Veeam backups in object storage. An attacker who reaches the backup server can encrypt repositories on local disk, but cannot touch locked objects in the bucket. Plan for the effective lock to run up to ten days longer than the configured period, because Veeam extends protection for active block generations.
Point your backup jobs at the repository
In v12, a backup job can target the object storage repository directly: select it in the job’s repository step just like a regular disk repository. The alternative is using it as the capacity tier of a Scale-Out Backup Repository (SOBR), keeping fast restores on local disk with long-term copies in object storage.
For smaller environments, direct-to-object is usually the right call: fewer moving parts, and the backup is off-site from the first write. SOBR earns its complexity when fast restores from local disk are a hard requirement.
Block size and task limits
Two settings have the biggest impact on throughput and API request volume:
Block size is controlled by Storage optimization in the job settings (Advanced, then the Storage tab). The 1 MB default works for most environments. Larger blocks (4 MB) mean fewer API calls and higher throughput for servers with large volumes, at the cost of bigger increments when small changes occur. With Hexabyte, all API requests are included in the price, so the choice is purely about throughput and increment size, not per-request cost. The change only takes effect after a new active full backup, so pick a block size before the first job run.
Task limits cap how many parallel tasks write to the repository at once. The checkbox is called Limit concurrent tasks to N and lives on the Name step when you add the repository; afterwards you reach it through the repository’s properties. Start conservatively, with 4 for example, and raise it step by step if the backup window needs shortening and your uplink has headroom.
Troubleshooting
- “Failed to establish connection” when adding the repository: check the endpoint URL and that the backup server reaches it over port 443:
curl -I https://s3.hexabyte.se. Also check the system clock; S3 signatures fail on large clock skew. - The immutability option is greyed out or errors: the bucket was created without Object Lock. Create a new bucket with Object Lock enabled and repoint the repository; it cannot be enabled on an existing bucket.
- Access denied: the keys lack permissions on the bucket, or the bucket name is wrong. Verify with
aws s3 ls s3://my-veeam-backups --endpoint-url https://s3.hexabyte.se. - Slow backups: raise task limits gradually and review the block size. The bottleneck is often the uplink from the backup server.
- The backup chain turns corrupt: lifecycle rules on the bucket or manual deletions have removed objects. Veeam handles retention and deletion itself; never add your own lifecycle rules or delete objects manually.
S3 storage in Sweden for your Veeam backups
Hexabyte object storage is S3-compatible, supports Object Lock and works with tools like Veeam. All data is stored on our own server infrastructure in Umeå, Sweden, entirely within the EU, encrypted at rest and spread redundantly across a distributed Ceph cluster. That makes it a solid target for immutable off-site backups of servers running on-premises or with other providers. You pay only for the storage you use; all traffic and API requests are included at no extra charge.