Warnings when doing Linux file level restore in Azure

Rob Nicholson 46

I often mount the file restore points for a Linux file level backup on a test virtual machine based on my network. The downloaded Python script works fine but recently, it's been giving this warning:

Your system doesn't have access to 'pod01-rec2.ukw.backup.windowsazure.com' on port 3260 (outbound). ILR Script won't be able to run successfully. Please add rules in the NSG to allow 'pod01-rec2.ukw.backup.windowsazure.com' on port 3260 (outbound), and also allow Public DNS resolution on port 53 (outbound). Please press 'N' to abort the operation. Press 'Y' if you still want to continue with running the script : y

If I say "Y", the script works fine. It mounts the backup volumes and I can access the backup.

But why has this warning started over the past few months? This Linux VM will have full outbound port access AFAIK and the same error occurs even if I disable firewall-cmd.

I assume that I because I can ping pod01-rec2.ukw.backup.windowsazure.com that public DNS resolution on port 53 is open. Not sure about port 3260. Could I try a telnet to it on that port?

When I run the same restore scripts on the actual Azure based VM, the warnings don't appear.

SadiqhAhmed-MSFT 41,716 Reputation points Microsoft Employee

2023-11-03T17:31:07.6+00:00
Hello @Rob Nicholson Thank you for reaching out to us on Microsoft Q&A platform and I apologize for the delayed response.

The warning message you are seeing indicates that your system is unable to access 'pod01-rec2.ukw.backup.windowsazure.com' on port 3260 (outbound), which is required for the ILR (Instant File Recovery) script to run successfully.

It's possible that the warning message started appearing over the past few months due to changes in your network configuration or security policies. It's also possible that the warning message is a false positive and the ILR script is actually able to access 'pod01-rec2.ukw.backup.windowsazure.com' on port 3260.

To troubleshoot the issue, you can try the following steps:

Check if your system has outbound access to 'pod01-rec2.ukw.backup.windowsazure.com' on port 3260: You can use the telnet command to check if your system can connect to 'pod01-rec2.ukw.backup.windowsazure.com' on port 3260. For example, you can run the following command:

telnet pod01-rec2.ukw.backup.windowsazure.com 3260

If the connection is successful, you should see a message indicating that the connection was established. If the connection fails, it's likely that there is a network or firewall issue that is preventing your system from accessing 'pod01-rec2.ukw.backup.windowsazure.com' on port 3260.

Check if there are any network or firewall issues: You can check if there are any network or firewall issues that are preventing your system from accessing 'pod01-rec2.ukw.backup.windowsazure.com' on port 3260. For example, you can check if there are any network ACLs or firewall rules that are blocking outbound traffic on port 3260.

If you are unable to resolve the issue, you can contact Microsoft Azure technical support for further assistance. They can help you troubleshoot the issue and provide guidance on how to resolve it.

Hope this helps. Feel free to post a reply if you have any questions or concerns.
Rob Nicholson 46 Reputation points

2023-11-03T19:16:24.0166667+00:00

Thanks for getting back to me. I can establish a telnet connection:

[root@localhost ~]# telnet pod01-rec2.ukw.backup.windowsazure.com 3260

Trying 51.140.211.105...

Connected to pod01-rec2.ukw.backup.windowsazure.com.

Escape character is '^]'.

As it works, I'm not too worried but it's a bit strange.
SadiqhAhmed-MSFT 41,716 Reputation points Microsoft Employee

2023-11-08T08:09:11.7133333+00:00

@Rob Nicholson Thats great to know it's working. But if you really want to know why there is warning triggered every time, we can investigate further. However, it requires you to contact Azure technical support by raising a support request.
Rob Nicholson 46 Reputation points

2023-11-13T17:38:09.19+00:00

This was a case of waiting... I didn't get around to contacting support but I've going through the very same process today, on the exact same system and no error. It was clearly a problem external to me that's been fixed.
SadiqhAhmed-MSFT 41,716 Reputation points Microsoft Employee

2023-11-13T20:13:16.37+00:00

@Rob Nicholson Thanks for the update. Glad to hear it is working.

Share via

Warnings when doing Linux file level restore in Azure