What would you look at instead of Veeam for S3 backups?

November 8, 2026 5 answers
Asked by q3+Knapsack

We’re considering moving away from Veeam after prolonged support problems and recurring failures with S3 backup jobs, including locked files and checkpoint errors. We need reliable backups for a hybrid on-premises and disaster recovery setup, with immutable storage. Which alternatives are worth evaluating, and what should we test before switching?

Answers

bitsy

Rubrik is one option to put on the shortlist, especially if you want a more integrated backup and recovery platform. Still, check the full cost of expansion and refreshes, not just the initial quote. Make the vendor demonstrate your actual S3 workflow and restore scenarios before treating it as a fit.

Reply to this answer
F6!Mullion

Commvault is worth evaluating if the S3 side is a major part of the requirement. It can be deployed on-premises or in the cloud, and its capabilities may suit larger environments. I’d compare operational complexity and licensing alongside throughput, recovery time, and object-lock behavior.

Reply to this answer
47+Flotilla

HYCU may be a good candidate if your infrastructure lines up with what it supports, particularly in a Nutanix-heavy setup. Don’t assume it will cover every hypervisor or workload you have. Ask for a compatibility check and a proof of concept that includes recovery, not just successful backup runs.

d4~Clapboard:

VMware support is a key question for us. I’d want that confirmed for our exact versions and configuration before spending time on a trial.

Reply to this answer
evie

I wouldn’t make the decision from one bad support experience alone, but months of unresolved failures are a fair reason to assess other products. If you haven’t already, ask your account team for a concrete escalation and resolution plan while you run a parallel evaluation. Keep the current backup path until restore tests show the replacement is ready.

q3+Knapsack:

That makes sense. We’ll keep the existing setup in place until a candidate has passed restore and failure-recovery tests.

Reply to this answer
9M!Calabash

First pin down whether the failures are tied to AWS S3 or an S3-compatible provider, and document the storage settings involved, including immutability and retention. Then test each contender for interrupted jobs, locked objects, retry behavior, checkpoint cleanup, and restores. A product that works well with one object-storage service may not behave the same with another.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions