--- title: "What it Takes to Recover a 100 TB Postgres Database in AWS RDS" url: https://daily.dev/posts/what-it-takes-to-recover-a-100-tb-postgres-database-in-aws-rds-v3k21len0 source_url: https://neon.com/blog/recover-large-postgres-databases type: article source: "Neon" published: 2026-07-09T06:57:28.377Z updated: 2026-07-09T06:58:36.358Z tags: ["postgresql", "aws-rds"] reading_time: 8 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # What it Takes to Recover a 100 TB Postgres Database in AWS RDS **[Neon](https://daily.dev/sources/neontech)** · 8 min read · 0 upvotes · 0 comments ## Summary A deep dive into the challenges of recovering a 100 TB PostgreSQL database on AWS RDS, covering two primary failure modes: logical errors (requiring PITR) and infrastructure/AZ failures (requiring HA). AWS RDS snapshot-based PITR is slow at scale—restoring a 100 TB snapshot can take hours—while Multi-AZ standbys don't solve PITR and can suffer replication lag at large sizes, plus double costs. Neon's storage-compute separation and log-structured storage engine are presented as an alternative, enabling instant PITR via database branching at any historical timestamp and built-in multi-AZ HA without dedicated standby instances. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#postgresql](https://daily.dev/tags/postgresql), [#aws-rds](https://daily.dev/tags/aws-rds) [View this post on daily.dev](https://daily.dev/posts/what-it-takes-to-recover-a-100-tb-postgres-database-in-aws-rds-v3k21len0)