Problem Statement
Automated RDS backup tasks in Druva CloudRanger fail with the following error message:
Cannot create a snapshot because the database instance [instance-id] is not currently in the available state. Retrying in 600 seconds.
Root Cause
This error occurs because the target Amazon RDS instance is not in an Available state at the time CloudRanger attempts to initiate the snapshot.
Common scenarios include:
The instance is currently Stopped.
The instance is in a state transition (e.g., Starting, Stopping, or Modifying).
The instance is undergoing a maintenance window or an automated AWS backup process that restricts snapshot creation.
This is frequently observed in environments where RDS instances are scheduled to shut down outside of business hours to optimize costs.
Verification
To confirm if the instance state is preventing backups, perform these steps in the AWS Management Console:
Navigate to the RDS Dashboard and select Databases.
Locate the affected instance and check the Status column.
Attempt to perform a Manual Snapshot:
Select the instance.
Click Actions > Take snapshot.
If the instance is not ready, AWS will return a native error such as:
Database is in an invalid state.
Resolution
To ensure successful backups, the RDS instance must be fully operational before the CloudRanger backup window begins.
1. Align Operational Schedules
Ensure that the RDS instance's "Start" schedule is configured to complete before the CloudRanger backup task triggers.
2. Implement a Buffer Period
AWS instances may take several minutes to move from a Starting to an Available state. It is recommended to schedule the backup at least 15–30 minutes after the instance is scheduled to start to account for initialization and health checks.
3. Review Maintenance Windows
Check the AWS RDS console to ensure that automated AWS maintenance windows do not overlap with your CloudRanger backup schedule, as certain maintenance activities can temporarily lock the instance state.