Issue: FLR to Original Location failing for AzureVMs which are part of a failover cluster. VBAzure fails to create FLR Session
Error: Invalid resource type Microsoft.Network/loadBalancers/backendAddressPools expected Microsoft.Network/loadBalancers (Parameter 'id')
FLR works on these VMs as expected when attempting without restore to original location option
FLR with Original Location works on other VMs (standalone, not part of any Windows Failover cluster) in the same resource group
Support case 08096852 opened more than two weeks ago, issue still not resolved. Please help
We cannot resolve support related issues via the forums. Please continue working with support to find the solution as potentially a fix is required to resolve this issue.
Usually when I post about an issue in the forum, I was always requested to provide support case number. That's why I mentioned the support case# in the post.
I'm not trying to resolve support related issues, just trying to get insight into the FLR issue with VBAzure.. if any other customers face same issue, is there any known workaround for this, if any Azure experts here know what this error means, etc.
It's a specific Azure issue which seems that during the restore process, something goes wrong and we need to understand if this is related to changes at Microsoft's side or a potential bug in VB for Azure.
Support has provided a private fix, which resolved the issue.
As per the support, the root cause of the issue is, during File-Level Recovery with RTO enabled, the network export resolves the source VM's load balancer from its NIC backend-pool association. It queried Azure using the backend address pool id instead of the parent load balancer id, which the Azure API rejects with Invalid resource type Microsoft.Network/loadBalancers/backendAddressPools expected Microsoft.Network/loadBalancers
The fix was to make VBAz look up load balancer by its own resource id (the parent of the backend pool reference).
