SaaS Ranking
Menu

SaaS transparency ranking · Security and compliance

Backup and recovery software

41 vendors · updated 2026-10-17 · 6 without enough data for a score

Backup, replication and disaster recovery products, ranked by what they publish about how they handle your data.

Public transparency score, not a product or security rating. Transparency means: published on the vendor's own site, readable without a login, found by us at the addresses we checked.

=exactly at the median of every category we measure

  • Backup and recovery17
  • All categories17
Median transparency score, out of 100. Backup and recovery sits at the median across every category we measure.
  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D2 6%
  5. E10 29%
  6. F23 66%
35 vendors with a score; 6 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.
All filters
Show only vendors where we found

Transparency band

6 without enough data for a band

41 vendors

Sort by

Not in the ranking

We could not measure this product with our method, so it is listed here instead of being scored. This says something about our method, not about the vendor.

Before the demo

Backup software: a restore trial checklist

Restore a business task, then verify the result independently.

Map the records the business needs back

List the applications, record types, attachments, identities and relationships needed for the trial. Ask which of them the quoted connector covers and which require a separate process. Make the boundary explicit for deleted accounts, shared workspaces and configuration data. Include one deliberately excluded item so the reviewer can recognise an incomplete recovery. For a service your team operates, record the storage destination and who patches the backup software. For a managed service, name the supplier and service scope. Retain the dated coverage statement alongside what your trial actually restored.

Choose a recovery point deliberately

Create the first version of the sample, run the configured protection process and record its completion. Change one record, remove another and capture the next run. Choose which earlier point the exercise should recover and why. Record both the timestamp represented by that point and the time the job finished. Ask how missed runs, connector failures and retention settings affect the available history. A successful recent job does not answer whether the older state you need is still available. Use a failed trial connection to inspect how the operator notices and investigates missing coverage.

Measure recovery and business validation separately

Restore into the agreed isolated destination, with an operator who has the intended permissions. Record the request time, job completion time and the time the independent reviewer can complete the business task. Read the restored content, follow the relationships and check the permissions from a non-administrator account. Ask how a larger dataset or service-side limit could change the result, and keep the small trial’s scope visible. AWS Backup documents restore-job execution and optional validation as separate steps; that distinction is useful when designing this exercise for any product, without implying identical capabilities.

Full trial checklist and CSV worksheet

A trial you can repeat

Use an isolated trial environment and invented records to define a small recovery exercise. Select a file, a related record and a permission that must survive. Write down what another colleague should be able to do after the restore. Use the same dataset and success criteria for each product. A completed backup job and a usable recovery answer different questions; record both without treating one as proof of the other.

AWS documents restore testing with job timing, an optional validation step and resource cleanup. The cross-product coverage, operator and purchasing exercises here are editorial tasks. A small successful trial does not establish a production recovery guarantee. AWS Backup: restore testing. Source reviewed 2026-10-03. The trial questions are editorial guidance, not additional measured criteria.

Narrow it down

Each of these lists the Backup and recovery vendors that meet one condition, with the source for each, and appears only where at least 8 of them meet it.

This category, criterion by criterion

How this market does on each criterion, with its own share and how it compares with the rest.

Every result links its source on the vendor page. A grey segment means we could not measure it, not that it is missing. See how we score.