Azure VM Guest processing

[helfire]

Hello All

Im new to Azure back up and busy testing it out with the free version. Everything seems to be running and backing up ok except when i turn on Guest processing for a windows 2019 DC. Its failing with cannot contact VSS agent. Now the manual says about port 443 being open. But not sure where to open it on the windows firewall or somewhere in azure setup ?

Any suggestions?

Running ver 3.0.0.666

Thanks

Chris

[Vitaliy S.]

Hi Chris,

Is this port open in the guest OS firewall? Should do the trick.

Thanks!

[helfire]

Tried turning of the firewall and still nothing. Windows docs says the Azure VM agent needs to be able to ping ports 80, 32526 and 443 for it to work; Now it can ping 80 and 32526 all ok just not 443. I know its not the windows firewall on the server as i can ping my VeeamPN on port 443.

[nikolaj]

Hi Chris,

Have you tried listing all the listening ports on the server? You could do this with the following command from within the server:

Code: Select all

netstat -an

Or, if you want to see how it looks from the outside, perhaps, try telneting* on port 443 to that machine.
If you receive a timeout, then it means that the port is most probably blocked by a firewall.

*Telnet has to be enabled on the machine itself.

[Vitaliy S.]

Chris,

Since you've checked the Guest OS for the firewall rules, then the other place would be the Azure network security group settings. As far as I know, by default port 443 is open there, but it is still worth checking.

Thanks!

[helfire]

Tried now with antivirus removed and firewall off and still the same. Have a support case opened. Wondering now if ive set it all up wrong. I have the back appliance in the same virtual network as the workers. And trying to back up a server in a different virtual network. Or does it all have to to be on the same virtual network/subnet ?

[Vitaliy S.]

The same subnet is not needed, so let's see what our support team finds out. Can you please post your case ID for tracking?

[Rouxls Kaard]

I had a similar issue, the VSS agent was failing to deploy during the application consistent backup. Tech support had me run these two powershell commands and it solved the issue:

Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

[eduzimrs]

Hi,

I tried those PS commands and still not working for me.
Anyone succeeded with this ?

Code: Select all

 '. Snapshot will not be application consistent. VM: /subscriptions/6b4e29a7-2413-4451-bffe-2ed532a5b045/resourcegroups/win2019_group/providers/microsoft.compute/virtualmachines/win2019
[16.03.2022 14:21:04]   35 (1) Warning: Failed to create an application-consistent snapshot for VM /subscriptions/6b4e29a7-2413-4451-bffe-2ed532a5b045/resourcegroups/win2019_group/providers/microsoft.compute/virtualmachines/win2019, failing over the crash-consistent snapshot creation. The Windows VSS agent has failed unexpectedly. Verify that outgoing traffic for this VM is not blocked on port 443. 
[16.03.2022 14:21:04]   35 (1) Error: Failed to freeze VM to make consistent snapshot, snapshot will not be application consistent (error : 'Cannot contact the Windows VSS agent via port 443. Proceeding with the crash-consistent snapshot', VM /subscriptions/6b4e29a7-2413-4451-bffe-2ed532a5b045/resourcegroups/win2019_group/providers/microsoft.compute/virtualmachines/win2019)

Thanks.

[nielsengelen]

@eduzimrs it looks like a firewall issue within the guest from the message. Please open a support case for assistance and let us know the case ID for future reference.