Recovery Brief

Method

How to read this evidence

We show what the saved pages say, who said it, when it was read and which conditions apply.

Scope

The candidate covers US companies with roughly 100 to 999 employees evaluating backup and disaster recovery for servers, virtual machines and SaaS data. The current detailed evidence covers 10 of 16 named Stage 0 vendors: Veeam Software, Rubrik, Cohesity, Commvault, Druva, HYCU, Acronis, NAKIVO, Unitrends, Zmanda.

Evidence roles

Vendor claims describe what a vendor says. They are not independent tests of performance or security. Project feedback is an attributed report from one user or thread. Editorial guidance explains a buyer action. These roles are not interchangeable.

Coverage and unknowns

The aggregate contains 34 manually reviewed rows (34 vendor claims, including four explicitly scoped workload/edition mappings). 6 named Stage 0 vendors (Dell PowerProtect, Veritas NetBackup, Zerto, Datto, Axcient, Eon) have no admitted claim in this evidence set. No independent recovery benchmark or repeated freshness measure is available. Unknown does not mean a feature is absent.

Project feedback review counted 64 candidate records: 7 posts and 57 explicit-identity comments. Of these, 30 could be partially informed by at least one matched source statement, and 0 were fully answered by the reviewed evidence. This search-selected sample is not representative of all buyers.

Source dates

Vendor pages in this comparison were read on 13 November 2026. A source's own update date is shown only when the saved evidence records one. A page read date does not mean its claims were independently verified or remain unchanged.

Claim changes

Displayed claims are bound to exact saved source and reviewed-record hashes in the site dependency manifest. If a source changes or fails review, every linked page must be checked before the claim returns.

Sources for these plan and workflow details

These are vendor descriptions and policies, read on 2026-11-14. They do not establish measured product performance.

Druva · Archive restores

Druva gives an Archive restore allowance of 1% of archived source-plus-change data per day. Extra restores cost 1 credit per TB; unused allowance rolls forward.

Enterprise Workloads Archive only; not a dollar fee or a promise about recovery speed.

Open Druva documentation ↗

Read date and saved passage

Read 2026-11-14T03:48:07.139652+00:00 · L306–308 · vendor_statement

Saved excerpt SHA-256: d2c2d27e79a041a73b62076104746aa32a1f7e29c8dc569e77130c3dfb2438f2

Druva · Credit exhaustion

Druva says backups stop at 110% of purchased credits until more credits are bought.

Enterprise Workloads; existing-data retention and restore rights need the contract and workload terms.

Open Druva documentation ↗

Read date and saved passage

Read 2026-11-14T03:48:07.139652+00:00 · L255–256 · vendor_statement

Saved excerpt SHA-256: d2c2d27e79a041a73b62076104746aa32a1f7e29c8dc569e77130c3dfb2438f2

Veeam Software · Locked storage can outlast retention

For EC2/RDS image backups in Veeam’s AWS plug-in, the first block generation adds 25 days to retention. Existing block locks cannot be shortened.

Veeam Backup & Replication 13 guide, build 13.1.2.57; this is not a rule for every Veeam repository.

Open Veeam Software documentation ↗

Read date and saved passage

Read 2026-11-14T03:48:07.139652+00:00 · L9695–9714 · vendor_statement

Saved excerpt SHA-256: 7d0858080640b0ab2c7ec4b84e010a45f93d0a5bbdbd99cd46baf4e689391206

Veeam Software · Changing retention can add requests

Veeam warns that frequent retention changes create new block generations and can increase storage-service requests and cost.

AWS plug-in image-level backups with immutable target repositories.

Open Veeam Software documentation ↗

Read date and saved passage

Read 2026-11-14T03:48:07.139652+00:00 · L9711–9714 · vendor_statement

Saved excerpt SHA-256: 7d0858080640b0ab2c7ec4b84e010a45f93d0a5bbdbd99cd46baf4e689391206

Veeam Software · Encryption keys are part of the restore path

Encrypted EC2/RDS operations need the appliance’s IAM role to reach the required AWS KMS keys.

Permissions depend on the operation and source/target keys; document applies to build 13.1.2.57.

Open Veeam Software documentation ↗

Read date and saved passage

Read 2026-11-14T03:48:07.139652+00:00 · L9697–9723 · vendor_statement

Saved excerpt SHA-256: 15c74b107bff4ff9373c0ffbe6ef2378b103243f3803aa3947e9c7fe363f0973