Object storage is supposed to be the affordable option. The marketing says so: pennies per gigabyte, infinite scalability, set and forget. So why does your monthly bill keep creeping up in ways you can’t quite explain?
If you’re backing up to S3-compatible storage with Veeam, you’re not imagining things. The gap between what you expected to pay and what you’re actually paying is real—and it’s almost never about how much data you’re storing.
The Problem Nobody Warned You About
Here’s the uncomfortable truth: $/TB is the smallest part of most object storage bills.
What actually moves the needle? API requests. Every time Veeam writes a block, reads metadata, checks immutability status, or cleans up expired backups, that’s an API call. And Veeam doesn’t store your backups as single files—it breaks them into blocks and metadata objects. More objects means more API operations. More API operations means more cost.
Then there’s egress. Every time you restore data from cloud object storage back to your on-premises environment, you’re paying to retrieve your own data. Run a few test restores or recover a large VM, and suddenly you understand why “data transfer out” is its own line item.
And if you’ve enabled immutability for ransomware protection (as you should), there’s an additional layer of API activity that varies significantly depending on your Veeam version and configuration.
What We’ve Learned
We’ve put together a technical guide that cuts through the noise and focuses on what actually works. It’s called Reducing Object Storage Spend for Veeam Backup & Replication, and it’s built around a simple premise: you can’t optimise what you don’t understand.
The guide covers where costs actually come from (spoiler: it’s not just capacity), the specific ways Veeam interacts with object storage that drive variable charges, a prioritised optimisation playbook that starts with the highest-impact changes, and critical mistakes to avoid—like applying bucket lifecycle policies to Veeam-managed storage.
The Key Takeaways
If you take nothing else away, remember these points.
Design for local restores first. Keep your common restore window on fast local storage. The performance tier exists for a reason—use it for operational recoveries where speed matters and egress costs add up.
Match retention to storage tier rules. Archive tiers look cheap until you realise they have minimum storage durations and early deletion fees. If your retention policy is shorter than the minimum duration, you’re paying archive prices without getting archive economics.
Don’t let your cloud provider manage Veeam’s objects. Provider-side lifecycle rules and automatic tiering on Veeam buckets can break your backups. Veeam needs to be the sole manager of those objects.
Measure continuously. Storage growth, request volume, restore traffic. Costs only become predictable when usage is observable.
When Optimisation Isn’t Enough
Sometimes the problem isn’t your configuration—it’s the pricing model itself. If API calls and egress dominate your spend, you’re fighting a battle that never ends. Every efficiency gain gets eaten by the next workload change or restore test.
That’s why we built InfiniStor: S3-compatible object storage with a flat $/TB price, no API request fees, and no egress charges. For organisations tired of unpredictable bills, it’s worth running a side-by-side cost model against your current provider.
Get the Full Guide
The complete technical guide is available now. It includes an implementation checklist for your first 30 days and the following 60-90 days, a breakdown of common cost levers and their trade-offs, and references to Veeam’s official documentation and best practices.
Whether you’re troubleshooting an unexpected bill or planning a new backup architecture, it’ll give you a framework for making decisions you can defend.
Download: Reducing Object Storage Spend for Veeam Backup & Replication