Full Daily Snapshots combined with Transaction Logs, backup to S3.
Allows for Point in Time restore, up to the second. (date/time picker)
Retention Period: 1 to 35 days.
Define Preferred Backup Window.
2 options
Manual / User Initiated.
Persist even if RDS instance is deleted.
Copy Snapshots to different regions.
snapshot
snapshot
snapshot
transaction logs
mm/dd/yyyy hh:mm:ss
RDS Backups
Backups are RDBMS agnostic;
ex: NO .bak, .sql, .csv, .json, .xml, <else db dump format>
Exporting to data level backups, requires additional DB engine specific tools;
ex: mysql_dump, PHPMyAdmin, SQL Server Managenet Studio, etc
Recover ONLY to point (date/time) in RDS instance retention period history.
continued...
Warning: You may experience DB I/O latency during snapshots. Schedule accordingly
RDS RESTORE & Scale
* Important to note, that one method of scaling / upsizing RDS DB instance size, is to restore a snapshot, and choose a more powerful DB engine tier aka instance class.
* Restoring an RDS backup results in a NEW instance endpoint / DNS connection string.
Multi-AZ Deployments
Replicate within the same region between Availability Zones.
Automatic synchronous replication & failover - single connection string.
High Availability, Disaster Recovery, Redundancy
us-east-1a
us-east-1b
Region
(primary)
(secondary)
proddb.asdf123.us-east-1.rds.amazonaws.com
endpoint:
AZ1
AZ2
Read Replicas
Scaling & Performance
Read Only. Improve Performance. Not for DR.
Replicate within the same region between Availability Zones.