- Newest
- Most votes
- Most comments
Hello.
If you use AWS Backup for backup, I think you can take a backup once every hour.
https://docs.aws.amazon.com/aws-backup/latest/devguide/creating-a-backup-plan.html
Also, the backup at that time will be an incremental backup because a snapshot of RDS will be taken.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithAutomatedBackups.html
The first snapshot of a DB instance contains the data for the full database. Subsequent snapshots of the same database are incremental, which means that only the data that has changed after your most recent snapshot is saved.
Hi,
If you need to maintain a very stringent SLA on your RDS database in terms of recoverability, I would suggest to implement Point-In-Time-Recovery (PITR) for a continuous backup strategy: it goes down to a resolution of 1s
See https://docs.aws.amazon.com/aws-backup/latest/devguide/point-in-time-recovery.html
With continuous backups, you can restore your AWS Backup-supported resource by rewinding
it back to a specific time that you choose, within 1 second of precision (going back a maximum
of 35 days). Continuous backup works by first creating a full backup of your resource, and then
constantly backing up your resource’s transaction logs. PITR restore works by accessing your full
backup and replaying the transaction log to the time that you tell AWS Backup to recover.
Best,
Didier
Relevant content
- asked 7 months ago
- asked a year ago
- asked 9 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago