16.6 Backups and snapshots
In short: RDS backups are storage-volume copies of the whole instance (every database on it), not a mysqldump of one schema.
RDS backups are storage-volume copies of the whole instance (every database on it), not a mysqldump of one schema.
Automated backups. With a retention period of at least one day, RDS takes a daily snapshot and keeps transaction logs. Point-in-time restore can rebuild the data to any second inside that window. Retention 0 turns automated backups off, and then point-in-time restore is not available.
Manual snapshot. On the database, open Actions, then Take snapshot (the menu may vary). Give it a name. A manual snapshot stays until you delete it. The retention window does not remove it.
Restore always creates a new instance. A snapshot restore and a point-in-time restore both leave the original appdb untouched. You get a new instance, a new identifier and a new endpoint. Point the application at that new endpoint, or switch back once you trust the copy.
What the snapshot contains. It contains the data on the volume at that moment. It does not contain your parameter-group or option-group settings. On restore, RDS attaches the default groups unless you pick your custom ones in the restore dialog. You also choose the VPC security group again. A change such as max_connections lives in the parameter group, not inside the snapshot. Select that group when you restore, or the new instance comes up with default settings and your old data.