What immutable cloud storage would you consider for 250 TB of backups?

November 18, 2026 5 answers
Asked by 9k~copperstencil_371

We're comparing Veeam and Veritas NetBackup and need immutable, S3-compatible storage for roughly 250 TB. The budget is around $20,000 a year, and we care about egress costs, restore speed and reliability.

Wasabi, Backblaze, AWS Glacier tiers and vendor-managed storage are on the list. What would you evaluate, and what should we watch for?

Answers

_g51!torkeli.8

I'd get quotes for Wasabi and Backblaze first. Both came up as immutable storage destinations alongside established backup products, and they let you compare storage separately from the backup software decision.

Ask each provider to price the actual retention pattern, not just 250 TB sitting still. Minimum storage duration charges can matter with Wasabi if backups are deleted or replaced early. Check egress terms and any limits in the current contract too, rather than assuming every restore is free.

_n83~drimvexa.7:

Also check whether a direct connection has a separate cost and what it does for restore throughput. It shouldn't be assumed necessary just to avoid egress charges.

Reply to this answer
_x93!fendelo.4

I'd put restore time ahead of a zero-egress requirement. If this copy is mainly for disaster recovery, an occasional egress bill might be a lot less painful than finding out the recovery takes too long.

Run a restore test with a representative amount of data, then use the measured throughput to estimate a larger recovery. Include the time to make the data available, not just the transfer rate. A storage quote on its own won't tell you whether the design meets your recovery deadline.

Reply to this answer
q.537+claspwhistle

Be careful with Glacier comparisons. Glacier is a storage tier, not backup software, so compare the full workflow and make sure the chosen backup product supports the tier and retrieval method you need. A cheaper archive tier may not suit a restore that has to start quickly.

If you're already heavily invested in AWS, AWS Backup is another architecture to evaluate, with a separate backup account and centrally managed policies. That's a different approach from simply pointing a backup product at an S3-compatible target.

Reply to this answer
_r27~torvani.6

Don't rule out a local backup copy plus an immutable cloud copy. A local NAS or appliance could help with routine restores, while the cloud copy gives you a separate recovery destination. Check the immutability and failure boundaries of each copy rather than treating replication by itself as the protection.

Reply to this answer
c.391!plimaro

If you're still choosing the backup platform, compare a managed service as well as standalone object storage. Druva, Commvault Cloud and Rubrik are options to investigate, but their packages aren't necessarily like-for-like with an S3 storage quote.

Get the total price for your workloads, retention and restore needs, and confirm exactly where immutability applies. Otherwise the $20,000 target is hard to compare across proposals.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions