Testing a DR scenario where we only have our backups in wasabi.
I created a VM in Azure, connected the S3 bucket backup repositories, imported backups and get all my VM's listed,
I started the restore process for a windows VM to azure, after the disk is created in azure I receive the following error
It's difficult to say what's triggering the error without examination of debug logs, please contact our support team to take a closer look at the issue and don't forget to share a support case ID with us.
If anyone is interested, issue was vm size was not available in eastus, once I selected another vm size it worked.
Can Veeam check which vm sizes are available before offering the size?
Could you please elaborate a bit more, for instance which size did you select to make it work? By default, the smallest VM size is selected automatically to support the number of disks for the restored machine.
Backup server only shows VM Sizes that are available in the selected region.
Backup server receives a list of available regions and caches it.
The issue experienced might happen due to:
* Cache being outdated. In general it should not happen, as the cache gets updated regularly. However, sometimes the cache might store information that has become outdated since the its last update
* The selected VM Size is temporarily unavailable caused by intermittent cloud problems