I'm currently in the process of restoring a 10TB RDS SQL Server instance, and it's been taking over 20 hours with no sign of completion. Typically, this whole process should wrap up in under an hour. I've reached out to support, but they're not very quick to respond. They mentioned that the database is stuck in a recovery state and is spending all its time in phase 2. Since I'm not a DBA, I'd appreciate it if someone could help explain what's going on with the database being in this state. Thanks!
2 Answers
Have you checked the AWS documentation for SQL Server restores? Sometimes, databases can get stuck in recovery if there's a lot of transaction log activity or if the restore process encounters issues. Running a diagnostic on the logs might give you more insight as to why it's taking so long.
It sounds like your restore process might be running into some resource limitations. If you're using a smaller RDS instance, it could be throttled by disk throughput or network speeds, which might drastically slow down the recovery. Consider switching to a larger instance during the restore process to see if that helps.
Exactly, resource bottlenecks can really impact restoration times. I've seen similar issues when using lower-tier instances for large databases.
Good point! Checking transaction logs can reveal pending transactions that might be hampering the restore.