Forum Discussion
Abnormal CPU Usage on Azure VMs with SQL
Hello,
For a week, we have noticed abnormal CPU usage on Azure VMs that have SQL Server installed.
We observe a link with the Azure SQL backup in the VMs. The CPU load saturates when a backup job is triggered!
The backup process iaaSWLPluginSvc consumes a lot of resources, but especially the LSASS process which saturates the CPU.
The domain controller is affected by this problem; on it, the LSASS process also saturates the CPU and does not go down! even when the job is finished!
Is anyone else experiencing this problem?
If so, have you found a solution?
We have opened a Microsoft ticket but no response at the moment!
Solution in Original Post : https://learn.microsoft.com/en-us/answers/questions/1605321/is-anyone-else-having-problems-with-high-cpu-consu
MS has provided us the following Workaround (seems to work for us by now):
- go to C:\Program Files\Azure Workload Backup\bin\plugins\SQL and open PluginManifest.json
- Change the value of AllowCommunicationThroughNamedPipes from true to false
- Open TaskManager and Stop AzureWLBackupPluginSvc and AzureWLBackupInquirySvc. Restart AzureWLBackupCoordinatorSvc.
3 Replies
Solution in Original Post : https://learn.microsoft.com/en-us/answers/questions/1605321/is-anyone-else-having-problems-with-high-cpu-consu
MS has provided us the following Workaround (seems to work for us by now):
- go to C:\Program Files\Azure Workload Backup\bin\plugins\SQL and open PluginManifest.json
- Change the value of AllowCommunicationThroughNamedPipes from true to false
- Open TaskManager and Stop AzureWLBackupPluginSvc and AzureWLBackupInquirySvc. Restart AzureWLBackupCoordinatorSvc.
No changes !
There is also a discussion on Learn: https://learn.microsoft.com/en-us/answers/questions/1605321/is-anyone-else-having-problems-with-high-cpu-consu
Another user experiencing the same problem received a response from Microsoft:
Right now, it seems to be an authentication issue between the extension and the SQL server. Our ticket was escalated to the product group, and we're now awaiting their answer.
