Veeam Backup & Replication Communication With Azure Proxy Fails With "The RPC server is unavailable"

KB ID: 4300
Product: Veeam Backup & Replication | 10 | 11
Published: 2022-04-19
Last Modified: 2022-04-19
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

When attempting to add an Azure Proxy to Veeam Backup & Replication or performing a Restore to Microsoft Azure using an Azure Proxy, the following errors may occur:

When attempting to add an Azure Proxy:

Failed to save Azure proxy. Error: The RPC server is unavailable.  Function name: [GetSvcVersion]. Target machine: [<IP Address>:6160].
Screenshot of failed to save errror
Restore job failed Error: The RPC server is unavailable.  RPC function call failed. Function name: [InvokerTestConnection]. Target machine: [<IP Address>:6162].
Proxy Failure
Note: This article is regarding the Azure Proxy VM, which is used to help speed up the restore process, not to be confused with the Azure Helper Appliance, which facilitates the restore Linux workloads to Microsoft Azure.

Cause

This error occurs when the Veeam Backup Server or Backup Repository server cannot communicate with the Azure Proxy appliance. By default, this communication happens over port 443. The port used for communication can be changed. For more information, see Specify Credentials and Transport Port.

Solution

In addition to checking local routers and firewalls to ensure outbound traffic to the Azure Proxy VM over port 443[1] is allowed, review the following Azure side configuration:

 

Check if the Azure Subnet that the Azure Proxy is using is associated with an Azure Firewall or a Network Security Group (NSG).

 

For subnet associated with NSG

Review the existing NSG rules, and if not configured, allow connections from the Veeam Backup server over port 443[1].

Alternatively, an NSG rule can be created with the highest priority (100) to allow connections over 443[1] using Azure CLI, PowerShell, or the Web Portal.

Reference: Azure Network Security Group

 

For subnet associated with Azure Firewall

By default, the Azure Firewall denies all traffic. Review the Azure Firewall configuration and ensure that a rule collection is configured to allow the traffic over port 443[1]. If it is a restore of Linux based computer, also allow port 22.

Reference: Azure Firewall Rules

[1]By default, communication happens over port 443. The port used for communication can be changed. For more information, see Specify Credentials and Transport Port.

More Information

As a workaround, for Azure Restores, you may elect not to use an Azure proxy VM. However, not using an Azure proxy VM may negatively impact restore performance.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.