How to Fix AWS RDS Manual Snapshot Stuck at 40% Before Switch to Preprod

Select Language:

If you’re working with an Amazon RDS MySQL instance in the ap-south-1a region and notice that your manual snapshot has been stuck at 40% for several hours, you’re not alone. This can be concerning, especially when the database and storage look idle and show no signs of performance issues.

First, understand that a snapshot being stuck at a certain percentage often points to underlying issues with the snapshot process, rather than the database itself. Since the database isn’t experiencing high CPU usage, active sessions, or disk queue delays, the problem is likely related to the snapshot service or temporary region-specific issues.

To address this, start by checking the status of your RDS snapshots through the AWS Management Console or AWS CLI. If the snapshot has been stuck for a prolonged period, consider the following steps:

Wait and Monitor – Sometimes, slow snapshot progress can resolve on its own. Keep an eye on the snapshot status over the next few hours.

ADVERTISEMENT
Cancel and Retry – If it remains stuck beyond a reasonable amount of time, you can attempt to delete the current snapshot and create a new one. Make sure you have recent backups before doing this.
Force Snapshot Completion – In some cases, restarting the RDS instance can help clear temporary states affecting snapshot processes, but this should be done cautiously, especially if the instance is in use.
Check AWS Service Health – Visit the AWS Service Health Dashboard to see if there are ongoing issues in the ap-south-1a region that could impact snapshot operations.
Contact AWS Support – If none of the above steps help, reaching out to AWS Support is your best bet. They can investigate backend logs and provide specific guidance or assistance.

In general, manual snapshot delays are often temporary, especially if the database is running smoothly. Planning for occasional snapshot retries and maintaining recent backups outside of snapshots can help minimize risks.

Always ensure you have multiple backup strategies in place, and avoid making snapshsots during peak loads or critical business hours to reduce the chance of such issues.