Index › Vendors › AWS Elastic Disaster Recovery · September 2026 Edition

AWS · 1 category · Named, not ranked

AWS Elastic Disaster Recovery

9Judge labels

0First choices

2Negative labels

7 of 12Models named it

1Category

September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.

Standing

6 labels, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. AWS Elastic Disaster Recovery was named 6 times in Backup and DR, where Veeam led with 18%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small businessnot named

No model named it for this buyer.

Mid-market28 of 121

under the label threshold

Enterprise53 of 99

under the label threshold

In backup and dr · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named AWS Elastic Disaster Recovery for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Backup and disaster recovery	Cloud and infrastructure	0%	28 of 121	17%	6	under 10 labels · led by Veeam at 18%

Movement

This is the first edition on this tier, so no move can be computed for AWS Elastic Disaster Recovery yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated AWS Elastic Disaster Recovery across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Alternative	Mention	Negative	Labels
Claude Haiku 4.5	1	0	0	1
GPT-5.4 mini	1	0	0	1
Gemini 3.5 Flash	0	0	0	0
Perplexity Sonar	1	0	0	1
Grok 4.1 Fast	0	0	0	0
Mistral Small	0	0	0	0
DeepSeek V4 Flash	0	0	0	0
Llama 4 Maverick	0	0	0	0
Qwen 3.7 Flash	0	0	0	0
Kimi K2	0	1	0	1
GLM 4.7 FlashX	0	1	1	2
MiniMax M2.5	0	0	0	0

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct1 labelNone

Paraphrase0 labelsNone

Comparative5 labelsNone

Budget-constrained0 labelsNone

Scale-constrained0 labelsNone

Negative3 labelsNone

First choiceAlternativeMentionNegative9 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“strongest fit when AWS is your recovery target and continuous replication is the main requirement” Claude Haiku 4.5 · Backup and DR · comparative prompt · alternative

“Continuous replication and fast failover to AWS” Perplexity Sonar · Backup and DR · comparative prompt · alternative

“Best for: cloud workloads on AWS” GPT-5.4 mini · Backup and DR · comparative prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“Common offenders: - AWS Elastic Disaster Recovery (no file-, table-, or record-level restore)” GLM 4.7 FlashX · Backup and DR · negative prompt · soft negative

Named alongside

The products named in the same answers as AWS Elastic Disaster Recovery, over the 9 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and AWS Elastic Disaster Recovery was named but was not.

ProductSame answerTook the first choice insteadHead to head

Azure Site Recovery7 of 90Not in the top three

Commvault7 of 90Not in the top three

Veeam4 of 92Not in the top three

Zerto4 of 90Not in the top three

Veeam Data Platform3 of 92Not in the top three

AWS Backup3 of 90Not in the top three

Druva3 of 90Not in the top three

Acronis Advanced Disaster Recovery2 of 91Not in the top three

Arcserve UDP2 of 91Not in the top three

Acronis2 of 90Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named AWS Elastic Disaster Recovery. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 9 of the 9 answers that named AWS Elastic Disaster Recovery and are not a share of its labels.

Domains cited

eon.io7

expertinsights.com7

solutionsreview.com6

axcient.com4

technologymatch.com4

backblaze.com3

connectwise.com3

gartner.com3

peerspot.com3

tech-insider.org3

No domain is on file for AWS Elastic Disaster Recovery, so its own site is not marked.

Pages cited

eon.io/blog/best-cloud-disaster-recovery-solutions6

expertinsights.com/backup-and-recovery/top-disaster-recovery-dr-software-solutions5

axcient.com/blog/backup-and-disaster-recovery-solutions4

expertinsights.com/backup-and-recovery/the-top-business-continuity-and-disaster-recovery-s3

solutionsreview.com/backup-disaster-recovery/the-best-backup-and-disaster-recovery-compani3

solutionsreview.com/backup-disaster-recovery/whats-changed-2024-gartner-magic-quadrant-for3

tech-insider.org/nl/veeam-vs-rubrik-vs-cohesity-vs-commvault-20263

technologymatch.com/blog/rubrik-vs-cohesity-vs-veeam-which-cyber-reslience-tool-is-best-fo3

Pages are listed as the models cited them.

Names read as AWS Elastic Disaster Recovery

What the judge wrote, as written, with how often. The vendor table decides that these count as AWS Elastic Disaster Recovery; a claim can dispute any of them.

AWS Elastic Disaster Recovery (DRS) 1AWS backup / AWS Elastic Disaster Recovery 1

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when AWS Elastic Disaster Recovery's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as AWS Elastic Disaster Recovery, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at the vendor's own domain is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.