Backup SQL Managed instance while stopped

Question

Backup SQL Managed instance while stopped

Mark Pearson 40

I am currently looking into Azure SQL Managed Instances, but I'm stumped on the following issue with backups:

While the instance is in a stopped state, it's not possible to take backups. For example, let's say that you have long-term backups configured, with yearly backups in place. If you stop the instance during the defined yearly backup period, the backup is skipped. We recommend that you keep the instance up and running during the yearly backup period.

The issue I have, is that I can only specify the retention policies, not anything specific with backup timings. Also I cannot find anywhere that shows me the specific time that the backups are due to run.

So, how do I ensure that the Instance is not in a stopped state at the time of the backups, If I cannot specify or view the time these backups are due to run?

Sai Raghunadh M 4,640 Reputation points Microsoft External Staff Moderator

2025-05-23T12:01:19.64+00:00

Hi @ Mark Pearson

Thanks for reaching out with your question about Azure SQL Managed Instance backups—it's a great one and definitely something that can cause confusion.

You're absolutely right: Azure doesn't currently allow us to set or view the exact time when long-term retention (LTR) backups are taken. These backups—like weekly, monthly, or yearly ones—are managed automatically by the Azure platform. The system schedules them dynamically based on overall resource usage, so there's no way to set a fixed time or get advance notice.

Because of this, if your managed instance is stopped during the expected backup window (even unknowingly), that backup can be missed, and Azure won’t go back and take it once the instance is restarted. This can be especially important for critical yearly or monthly backups that you might need for compliance or long-term storage.

Here are a few strategies to ensure your instance remains running during backup periods:

Since long-term backups follow a predefined schedule, Microsoft recommends keeping the instance running during the yearly backup period.

While you can't see the exact backup timing, you can check backup history in the Azure portal to get an idea of when backups typically occur

Set clear internal reminders or automation to keep the instance running during the timeframes when backups are likely to occur—usually once per week for full backups, which feed into the LTR retention schedule.

If you need more control, consider using manual backups to Azure Blob Storage, which allows you to schedule backups at specific times

Please go through these Documentations that might help you:

https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/doc-changes-updates-known-issues?view=azuresql#known-issues

https://techcommunity.microsoft.com/blog/azuresqlblog/troubleshooting-potential-backuprestore-issues-on-azure-sql-managed-instance/633556

Hope this helps. Do let us know if you any further queries.
Mark Pearson 40 Reputation points

2025-05-23T13:00:03.18+00:00
I find this answer pretty frustrating.

I'm honestly astounded that my only 2 options are:

Have the machine running for long periods incuring costs in the hope that I have it up at the right time period to both allow any and all backups (Weekly, monthly and yearly) to begin and fully finish

Manually create my own backups and store them on Azure storage, causing the process of backup and restoring to become a long winded manual process where I also have to keep track of what backups I have and when they can be deleted.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-05-23T21:23:21.1733333+00:00

Maybe I (and Microsoft) are overly simple-minded, but the way I see it the start/stop functionality is mainly for dev/test which are not in use constantly. For these LTR backups are not of much interest. For production instances they are of course of interest, but I expect these to up be all the time - even for a system that is mainly used during office hours.

So I am a little curious about your use case. How come you want both LTR backups and start/stop?

Accepted answer

0 additional answers

Your answer

Mark Pearson 40 Reputation points

2025-05-23T13:00:03.18+00:00

I find this answer pretty frustrating.

I'm honestly astounded that my only 2 options are:

Have the machine running for long periods incuring costs in the hope that I have it up at the right time period to both allow any and all backups (Weekly, monthly and yearly) to begin and fully finish

Manually create my own backups and store them on Azure storage, causing the process of backup and restoring to become a long winded manual process where I also have to keep track of what backups I have and when they can be deleted.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-05-23T21:23:21.1733333+00:00

Maybe I (and Microsoft) are overly simple-minded, but the way I see it the start/stop functionality is mainly for dev/test which are not in use constantly. For these LTR backups are not of much interest. For production instances they are of course of interest, but I expect these to up be all the time - even for a system that is mainly used during office hours.

So I am a little curious about your use case. How come you want both LTR backups and start/stop?

Answer 1

PratikLad 1,825 Microsoft External Staff Moderator

Hi Mark Pearson,

how do I ensure that the Instance is not in a stopped state at the time of the backups, If I cannot specify or view the time these backups are due to run?

As per documnet Automatic full backups are initiated once a week based on a schedule determined by Microsoft

While you can’t view the exact schedule, you can monitor whether an LTR backup has been created:

Use Azure CLI, PowerShell, or the Azure Portal to query the existing LTR backups:


az sql midb ltr-backup list --location [--database] [--database-state] [--latest] [--managed-instance] [--resource-group]

This lets you verify whether a yearly/monthly/weekly backup has been created, so you know you’re in good shape before stopping the instance.

As per your situation currently Safest workaround is as you suggested to take your own backups manually and store them in Azure Storage. This means you’re in full control you decide exactly when backups happen, and you keep track of them yourself.

PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-05-27T11:01:21.0833333+00:00

Hi Mark Pearson, We haven’t heard from you on the last response and wanted to follow up to check if your issue has been resolved.

If you have found a solution, we would appreciate it if you could share it with the community, as it may be helpful to others. Otherwise, please provide more details, and we will do our best to assist you further.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-05-28T09:53:12.36+00:00

Hi Mark Pearson, We haven’t heard from you on the last response and wanted to follow up to check if your issue has been resolved.

If you have found a solution, we would appreciate it if you could share it with the community, as it may be helpful to others. Otherwise, please provide more details, and we will do our best to assist you further.

Share via

Backup SQL Managed instance while stopped

0 additional answers

Your answer