Backups, Restores and Snapshots
- For all the AWS RDS engines except Amazon Aurora the database backup is scheduled every day. you can schedule the back up in your own window as per your convinience.
- You can also monitor the backups to make sure they are completing succesfully.
- The backps includes the entire database, transaction logs and change logs. By default backups are retained for every 35 days (If you want to retain backups for a longer period of time, you need to raise a support ticket to aws).
- Multiple copies of the backup are kept in each AZ where you have instance deployed
- When you restore the database for the backup, you create a new exact copy of the database or clone of the database. Restoring is pretty simple, you need to choose where to restore (your db instance) and when (time) to restore.
- While restoring a database, you define all the instance configurations just like when creating a new instance
- We can also manually trigger a backup which is referred as snapshot.
- When you take the snapshot, there will be temporary I/O suspension that can last from few seconds to few minutes.
- The snapshots are create in S3 and you can also use these snapshots to restore the database
- In the case of Aurora, you don’t have to backup manually since everything is automatically backed up continously to the s3 bucket.
- This allows you to restore the database at any point in the time.
- Aurora backups are also retained for 35 days & to increase we have to raise a support ticket
- Activity: Create a mysql instance with 2 days backup
- Insert some tables and records in your database
- Navigate to Automated backups
- Create a Snapshot
Parameter Groups
- Database parameters specify how the database is configured.
- A DB Parameter group acts as a container for engine configuration values that are applied to one or more DB instances.
- AWS has a default DB Parameter Group which contains database engine defaults
Option Groups
- Refer Here for the official documentation
