Veeam
Veeam Backup & Replication supports any S3-compatible object storage as a Capacity Tier for the Scale-Out Backup Repository (SOBR). Filebase fits this role with no egress charges, which makes restores from cold backups cheap.
Add Filebase as a backup repository
- In the Veeam console, open Backup Infrastructure → Backup Repositories → Add Repository.
- Choose Object storage.
- Choose S3 Compatible.
- Fill in:
| Field | Value |
|---|---|
| Service point | https://s3.filebase.io |
| Region | auto |
| Access key | Your Filebase access key |
| Secret key | Your Filebase secret key |
| Bucket | Your Filebase bucket |
| Folder | (an optional prefix within the bucket) |
- Configure throughput limits if your environment requires them.
- Complete the wizard.
Use as Capacity Tier in a SOBR
- Backup Infrastructure → Scale-Out Repositories → Add new SOBR.
- Add your existing local performance tier as the Performance Tier.
- Add the Filebase repository as the Capacity Tier.
- Choose policy:
- Move — older backups migrate from local to Filebase.
- Copy — backups are written to Filebase as well as kept locally.
Immutability
If you want immutable backups (Veeam's defense against ransomware-tampering of backup chains), enable object lock on the bucket and set the immutability period in Veeam. Object lock support on Filebase is on the roadmap; for now, immutability is a roadmap feature you should plan for if it's a requirement.