Availability and durability
Topics
Instance monitoring and repair
Aurora continuously monitors the health of your databases. In the rare event of a failure, Aurora automatically restarts your database and associated processes. Unlike other databases, Aurora does not require crash recovery replay of database redo logs, which greatly reduces restart times. Aurora also isolates the database buffer cache from database processes, which allows the cache to survive a database restart without brownouts.
Multi-AZ failover
On instance failure, Aurora uses RDS Multi-AZ
Amazon Aurora Global Database
Aurora Global Database
Fault-tolerant and self-healing storage
Aurora makes your data durable across 3 AZs, and its storage is fault-tolerant transparently handling the loss of up to two copies of data without affecting database write availability and up to three copies without affecting read availability. Aurora storage is also self-healing, and data blocks and disks are continuously scanned for errors and replaced automatically.
Automatic, continuous, incremental backups and point-in-time restore
Aurora backups are automatic, incremental, and continuous and have no impact on database performance. The
backup capability of Aurora enables point-in-time recovery for your instance, and you can restore your database
to any second during your retention period, up to the last 5 minutes. Your automatic backup retention period
can be configured up to 35 days. Automated backups are stored in Amazon S3
Database snapshots
You can create user-initiated backups of your Aurora instance at any time, and snapshots are stored in Amazon S3 and retained until you explicitly delete them. Aurora uses automated incremental snapshots to reduce the time and storage required. You can create a new instance from a DB snapshot whenever you desire.