Backup of RDS may fail with the error “can not take snapshot, db is in stopped state" error

Backup of RDS may fail with the below error:

"(database: >DB name>) can not take snapshot, db is in stopped state"

This is due to an AWS limitation.

AWS automatically backs up a stopped RDS, so there is no need for manual backups: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_StopInstance.html?shortFooter=true

"Amazon RDS automatically backs up a stopped DB instance. "

If you would try to take a snapshot of a DB in stopped state manually in EC2, it would fail:

“Cannot create a snapshot because the database instance <instance name> is not currently in the available state. (Service: AmazonRDS; Status Code: 400; Error Code: InvalidDBInstanceState; “

In order to overcome this error, please run backups on DBs which are in the running state

Related Articles
RDS backups may fail with "CPM Server identified this backup as orphaned: marking as failed"
The problem may happen if 2 policies are using the same schedule/target RDS, And therefore are trying to backup the same RDS databases at the same time. The following errors may be logged in the Backup Log: Info - Backup is agentless, managed by CPM ...
"SnapshotQuotaExceeded" error when trying to backup RDS
Customer may receive the following error when trying to backup RDS: ERROR: get_object(connection.py:1202) 400 Bad Request ERROR: get_object(connection.py:1203) <ErrorResponse xmlns="http://rds.amazonaws.com/doc/2013-05-15/"> <Error> ...
RDS Backup or DR fails with Reason: cannot create more than 100 manual snapshots
Issue: Backup or DR may fail with the following errors: ERROR: run_snapshots(.\agent.py:880) (database: "dbname") snapshot failed to start. Reason: cannot create more than 100 manual snapshots ERROR: backup_function_internal(.\agent.py:1204) policy: ...
CPM may mark a successful RDS snapshot as failed
CPM may mark a successful RDS snapshot as failed. In the backup log you may see the following error: Error - snapshot of database <DBname> failed. There may also be a "rate exceeded" error in the CPM server logs: ERROR: get_list(connection.py:1180) ...
Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error
RDS DR backup of encrypted snapshots between different regions may fail with the following error in the Backup log: Error - RDS DR, copy snapshot failed (to DR account) due to an AWS limitation regarding default encryption key (source US East (Ohio), ...

Backup of RDS may fail with the error can not take snapshot db is in stopped state error

Backup of RDS may fail with the error “can not take snapshot, db is in stopped state" error

Related Articles

RDS backups may fail with "CPM Server identified this backup as orphaned: marking as failed"

"SnapshotQuotaExceeded" error when trying to backup RDS

RDS Backup or DR fails with Reason: cannot create more than 100 manual snapshots

CPM may mark a successful RDS snapshot as failed

Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error