we're at the moment stuck trying to create an Azure Proxy. We went through the official documentation multiple times, but we don't see how we can try things any different. We're running the latest Build from Veeam B&R v10 on a W2012R2 Server. There are two errors occurring in the proxy deployment:
1. Error while creating Update Network Interface
On our multiple tries to deploy the proxy, this error only occurred in some of them. On the Azure Activity Log, one the following errors shows up:
Code: Select all
# Azure Monitor | Activity Log #
Microsoft.Network/networkInterfaces/(...) is not in Succeeded state. Resource is in Updating state and the last operation that updated/is updating the resource is PutPublicIpAddressOperation
Microsoft.Network/networkInterfaces/(...) is not in Succeeded state. Resource is in Updating state and the last operation that updated/is updating the resource is PutNetworkSecurityGroupOperation
2. Error while creating Virtual Machine
The following error always comes up, and ultimately kills the proxy deployment procedure:
Code: Select all
# Veeam B&R Console #
Provisioning state is 'failed': PlatformImageNotFound (System.Exception)
# Azure Monitor | Activity Log #
'MicrosoftWindowsServer:WindowsServer:2012-R2-Datacenter:latest' is not available. Verify that all fields in the storage profile are correct.
# the used azure account for the proxy deployment is the Onwer of the respective Azure subscription
# all of our resources, including the storage account for the proxy VM, are located on West Europe, so there's no Region mismatch between resources
# we ran ___ az vm image list -l 'West Europe' ___ on the Cloud Shell and the W2012R2 Datacenter is listed as available
# AzureRM 5.1.1 is installed on the VBR Server
# the Azure network and subnet resources to be used were provisioned beforehand
# we can manually deploy an Azure VM instance with the W2012R2 Datacenter SKU without any problem whatsoever
We also tried:
# recreate the azure storage account used by the proxy (to no avail)
# add our azure compute account through both "Use the existing account" and "Create a new account" methods. The veeam special application is successfully registered with the later method
We already have an opened ticket with the Azure support, but the assigned support engineer is not familiar with veeam, so we're still grinding through... Veeam case: #04437673
Has anyone faced similar issues in the past?
Regards