Impact of Enabling AWS Backup PITR on RDS Native Automated Backups

Hi,

When you enable continuous backups for an Amazon RDS instance in AWS Backup,

• AWS Backup will intelligently schedule your backup windows to coordinate with the Amazon RDS maintenance window, to prevent conflicts. Manual configuration of the RDS automated backup window is then unavailable.
• RDS will still take daily snapshots regardless of the backup plan frequency in AWS Backup.
• After applying a continuous backup rule, you can't create or modify the continuous backup settings directly in RDS - all changes must be done through the AWS Backup console or CLI.
• To transition continuous backup control back to RDS, you need to delete the RDS backup plans and recovery points in AWS Backup.
• The key is that AWS Backup's continuous backups work alongside RDS's automated backups, with AWS Backup managing the continuous backup schedule and settings.
• You can perform PITR restores using either the AWS Backup console/CLI or the Amazon RDS console/CLI.
• When doing a PITR restore through AWS Backup, the console will display a "Restore time" section where you can specify the point in time to restore to.
• When changing the PITR retention period, AWS Backup will immediately apply that change, even if there are other pending RDS configuration updates waiting for the next maintenance window.

Please refer to the following documents and blog post for additional details, https://docs.aws.amazon.com/aws-backup/latest/devguide/point-in-time-recovery.html

https://aws.amazon.com/blogs/database/demystifying-aws-backup-for-amazon-rds-for-oracle/