RDS Backup Retention
RDS instances are backed up automatically on a standard retention schedule. If
you need backups kept for longer or shorter, you can override the retention
period from the database Component's configuration in SVIEW.
Default retention period
If you have not set a custom value, automated backups are retained according to
the database's environment:
| Environment | Standard RDS (Postgres / MySQL / MariaDB / SQL Server) | Aurora (Postgres / MySQL) |
|---|---|---|
| Production | 10 days | 35 days |
| Staging / SIT | 4 days | 4 days |
| Sandbox | 7 days | 7 days |
| Dev | 1 day | 1 day |
| DR | Backups disabled | Backups disabled |
Aurora clusters use a longer production retention window than standard
(single-instance) RDS. Check which engine your database uses if you are unsure
which column applies.
Backups are disabled on DR instances by design. A DR instance is a copy of a
source database that is already being backed up, so a second automated backup
schedule would duplicate the data and the cost without adding recoverability.
Setting the retention period
Add a variables.backups_retention_period entry to the RDS Component's
configuration, giving the number of days to retain automated backups:
variables:
backups_retention_period: 21Click Save. The platform applies the new retention period to the instance.
The AWS maximum is 35 days. Any value above that is rejected, so do not set
one. A value of 0 disables automated backups entirely — do not use it on any
instance holding data you need to recover. If you need a copy retained beyond 35
days, raise a request: that requires manual or exported snapshots rather than the
automated backup window.
Related articles
- RDS Restore from Snapshot — restoring from an existing backup
Updated about 5 hours ago