Azure SQL backup discovery

kumar kaushal 176

As i know the part of discovery phase is to install AzureBackupWindowsWorkload extension. If we get a timeout during discover DB phase What steps i can take to find the Root cause ?

3 answers

Andreas Baumgarten 111.8K Reputation points MVP

2020-12-21T22:33:45.86+00:00

Maybe this is helpful:
https://learn.microsoft.com/en-us/azure/backup/backup-sql-server-database-azure-vms#establish-network-connectivity

You have to make sure the connectivity between VM with SQL Server, Azure Backup, Azure Storage and Azure AD is working properly.

The required extension will be installed automatically by Azure Backup after the discovery is done:

Azure Backup installs the AzureBackupWindowsWorkload extension on the VM. No agent is installed on a SQL database.

https://learn.microsoft.com/en-us/azure/backup/backup-sql-server-database-azure-vms#discover-sql-server-databases (see 8.)

----------

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten
Please sign in to rate this answer.
kumar kaushal 176 Reputation points

2020-12-22T07:12:44.393+00:00

I would like to understand the workflow as to how an extension gets installed . Like when we select discovery tab under sql backup on azure VM , is that we send a call to azure VM agent within the Vm and that VM agent gets that package from internet and puts at the root of C drive under s:\packages folder , then installs it . Why i am asking this is because : if we don't have an internet connectivity to pull the package then we can timeout right and this can be also be one of the reason . Am i correct ? Any thoughts on this ?

Andreas Baumgarten 111.8K Reputation points MVP

2020-12-22T08:13:13.897+00:00

The VM needs at least "some connectivity" to the internet: Azure Backup, Azure Storage and Azure AD
Without any internet connectivity it wouldn't work and this can be the reason for the issue.

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten

kumar kaushal 176 Reputation points

2020-12-22T11:19:11.25+00:00

Thank you for your inputs . In the Procmon from my working environment i do see that the VM basically establishes a UDP connection . Ip's truncated and the WindowsAzureGuestAgent.exe calls the createfile function
10:43:16.5725694 AM svchost.exe 3408 UDP Send myVM72:xyzasd -> x.y.z.d:ssdp SUCCESS Length: 137, seqnum: 0, connid: 0
10:43:16.5726305 AM svchost.exe 3408 UDP Receive x.y.z.d:ssdp -> myVM72:xyzasd SUCCESS Length: 137, seqnum: 0, connid: 0
10:43:16.5770614 AM svchost.exe 2432 TCP Receive line truncated SUCCESS Length: 43, seqnum: 0, connid: 0
10:43:16.8357811 AM WindowsAzureGuestAgent.exe 3580 CreateFile C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\1.0.18053.0\DotNetZip-dgaigzp1.tmp SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened

kumar kaushal 176 Reputation points

2020-12-22T20:22:40.703+00:00

Still working on this . Will get back once i get the issue resolved
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
kumar kaushal 176 Reputation points

2020-12-25T21:06:23.187+00:00

I found that actually we are timing out because we fail to enable the Plugin AzureBackupWindowsWorkload with WLenable.cmd script and we exited with exit code 52. That is a clear call out in wappagent log in the windows azure \logs folder .

I am not sure as to why are we failing to enable the plugin because installation succeeds.

Any clues any body as to why we would failing to enable the plugin ?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
kumar kaushal 176 Reputation points

2021-02-02T11:41:00.427+00:00

Ok this issue is resolved . After uninstalling the 3rd party components like AV . We were able to see the actual failure . And it was because of .net framework 4.5.2 not installed on the machine . and sql backup basically requires that . Once we installed the .net framework we were able to install the Plugin/extension .

Bingo
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure SQL backup discovery

3 answers

Your answer