Forum Discussion
Solved
60MB Azure SQL database restore taking over 50 minutes?
I kicked off a restore of an Azure SQL Database via the Azure Portal. Its only 60MB in size and is LRS so expected it to be pretty quick. 50+ minutes later it is still "Restoring..." wondered is ...
- In defence of Azure just a bit, the on-prem (private cloud) while more under our control and not shared with thousands of other customers, can have the same issue. Any type of restore would have to take in consideration the weekend full backups.
The solution mentioned above with an Azure VM running SQL is expensive as you said, so your concern would be a good one to raise with your Microsoft account executive and customer success account manager. Both likely would want to know that you provisioned a VM to resolve a concern related to an unmet Azure SQL RTO (Recovery Time Objective) and/or RPO (Recovery Point Objective).
thanks. It completed in the end after about 4 hours.
I had the same issue, small backup/database and took forever. Never figured it out, just went to Azure VM running SQL. Expensive solution. Did you ever get it working quicker?
CJMorganT11020 it seems to be very random. Sometimes it is quick like in a few minutes. Other times it can take a few hours.
I'm starting to think maybe it is stuck in a queue or something.
It is frustrating as we cannot rely on it as now we can't reliably estimate how long a restore takes.
- Having the same issue long back, a support request was opened with Microsoft Azure SQL support and the reply on that request is that the Azure SQL backup/restore infrastructure is working the restore requests into a queue and if the restore happens to be during a heavy workload of full backups, the restore make take much longer than expected. While supporting on-prem SQL, the same was also noticed and a question raised with the on-prem backup support team. The answer was similar, while full backups are running a restore request can take longer.
ms_dba
yes I think you have got this right.Unfortunately it is another barrier for cloud deployments as when we have to describe how long an environment might take to restore we cannot say and the range can be in excess of many hours more. This then does not inspire business continuity confidence.
Or at least this is a consideration specifically for Azure SQL deployments.