Bug in error checking when restoring to cloud

[crshovrd]

Hey there, I had an open ticket: 02343129

I was running into a strange issue when restoring a full VM from Object Storage to Azure.

Error: "Restore job failed Error: Failed to process request: (BadRequest). The value of parameter disk.name is invalid."

Reviewing the logs in the case, this was the error found:

Code: Select all

[15.09.2021 07:51:16] <26> Error        Failed to perform http request
[15.09.2021 07:51:16] <26> Error        The remote server returned an error: (400) Bad Request. (System.Net.WebException)
[15.09.2021 07:51:16] <26> Error           at System.Net.HttpWebRequest.GetResponse()
[15.09.2021 07:51:16] <26> Error           at Veeam.Backup.AzureAPI.CAzureRMAPI.DoWebRequest(String requestType, String url, CAzureRequestOptions options, Boolean addApiVersion, String requestBody)
[15.09.2021 07:51:16] <26> Error           at Veeam.Backup.AzureAPI.CAzureRMAPI.DoRequest(String requestType, String url, CAzureRequestOptions options, String requestBody)
[15.09.2021 07:51:16] <26> Info         Error response: {
[15.09.2021 07:51:16] <26> Info           "error": {
[15.09.2021 07:51:16] <26> Info             "code": "InvalidParameter",
[15.09.2021 07:51:16] <26> Info             "message": "The value of parameter disk.name is invalid.",
[15.09.2021 07:51:16] <26> Info             "target": "disk.name"
[15.09.2021 07:51:16] <26> Info           }
[15.09.2021 07:51:16] <26> Info         }
[15.09.2021 07:51:16] <26> Error        Failed to proces disk 'Ide0-1\GPData.VHDX'
[15.09.2021 07:51:16] <26> Error        Failed to process request: (BadRequest) 
[15.09.2021 07:51:16] <26> Error         The value of parameter disk.name is invalid. (Veeam.Backup.AzureAPI.CAzureWebException)
[15.09.2021 07:51:16] <26> Error           at Veeam.Backup.AzureAPI.CAzureRMAPI.DoRequest(String requestType, String url, CAzureRequestOptions options, String requestBody)
[15.09.2021 07:51:16] <26> Error           at Veeam.Backup.AzureAPI.CAzureRMAPI.DoRequest(String requestMethod, String url, CAzureRequestOptions options, String requestBody, Int32 retryCount)
[15.09.2021 07:51:16] <26> Error           at Veeam.Backup.AzureAPI.CAzureManagedDisksRmInvoker.Create(String resourceGroup, CAzureRmManagedDiskInfo diskInfo)
[15.09.2021 07:51:16] <26> Error           at Veeam.Backup.Core.CAzureManagedDiskInfrastructure.CreateManagedDisk(String name, String location, String resourceGroupName, CAzureManagedDiskSpec spec)
[15.09.2021 07:51:16] <26> Error           at Veeam.Backup.Core.CAzureManagedDiskProvider.CreateDisk(IDiskInfo diskInfo, Int64 capacity)
[15.09.2021 07:51:16] <26> Error           at Veeam.Backup.Core.CAzureDiskRestorer.RestoreDisk(IDiskInfo disk, IStopSessionSync sessionSync)

The tech was able to point me to this API URL being called:

Code: Select all

https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}?api-version=2019-07-01

I took a look to the Azure RM compute API and found this documentation:

Code: Select all

https://docs.microsoft.com/en-us/rest/api/compute/disks/create-or-update

The diskName parameter mentions an 80 character limit. Sure enough, the string that was being put together by B&R was more than 80 characters. I reduced the name of the server during the wizard and I was able to get the server to restore.

After all of this, the fix would be to implement error checking against Microsoft's documentation for the particular field.

I also hope this helps someone else running into the same issue.

[HannesK]

Hello,
first: thanks for posting the solution.

second: can you please check the ticket number again? It should be starting with 05... I will check then how we can fix that issue.

Best regards,
Hannes

[crshovrd]

Thanks Hannes!

Here is the full ticket: 05025720, lol. Not sure where I got that other number from. I will edit my original post.

[HannesK]

ok thanks - we will have a look at it after the 11a release

[HannesK]

Hello,
confirmed as a bug #338083. We plan to fix it, but I cannot give a timeline yet.

Best regards,
Hannes

[crshovrd]

Thanks HannesK!

Good to know I'm not crazy and glad I could help (I think)

[HannesK]

well, the bug was created (internally, not related to any support case) a week before you opened the case.

anyway, thanks for posting the workaround. that might still help customers until it's fixed