azure sqlmi high cpu spike cause by backups

Razzi29 336

The automated azure backups are causing a lot of performance and lock issues to our azure sql managed instance. We are at lost as to why it keeps happening every few hours and we have to manually kill the process id. Any has seeing this unwelcomed issue? Any queries or ideas you can offer to narrow it down? Thank you

Oury Ba-MSFT 19,801 Reputation points Microsoft Employee

2024-12-04T18:38:16.03+00:00
@Razzi29 Thank you for reaching out and sorry for the issue you are facing.

What type of automated backups have you scheduled for your Azure SQL Managed Instance. Understanding the backup schedule can help in diagnosing and resolving the performance and lock issues you're experiencing.

What types of automated backups are currently configured (e.g., Point-in-Time Restore, Long-Term Retention, Geo-Redundant Backups)?

What is the retention period for these backups?

Are there any custom backup schedules or policies in place?

Have there been any recent changes to the backup configuration or schedule?

This article teaches you how to monitor backup activity for Azure SQL Managed Instance by either querying the msdb database or by configuring extended event (XEvent) sessions. https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/backup-activity-monitor?view=azuresql

Fine tune back up storage consumption

Excess backup storage consumption depends on the workload and maximum size of the individual databases. Consider some of the following tuning techniques to reduce your backup storage consumption:

Reduce the database backup retention period to the minimum for your needs.

Avoid doing large write operations, like index rebuilds, more frequently than you need to.

For large data load operations, consider using clustered columnstore indexes and following related best practices. Also consider reducing the number of nonclustered indexes.

In the General-Purpose service tier, the provisioned data storage is less expensive than the price of the backup storage. If you have continually high excess backup storage costs, you might consider increasing data storage to save on the backup storage.

Use tempdb instead of permanent tables in your application logic for storing temporary results or transient data.

Use locally redundant backup storage whenever possible (for example, dev/test environments).

Share via

azure sqlmi high cpu spike cause by backups

Your answer