Veeam 10 Restore to Amazon EC2

[thedon]

Hi. We use Veeam 10. Our infrastructure is VMware 6.7 and 7.0. All machines are virtual.

When we run local recoveries from are local Veeam server to Vmware, everything works perfectly. We have an Amazon as our DR site with some VMs already running there. But we started testing the Restore to Amazon EC2 and the very first restore worked. But weeks later when we needed it for an exercise of DR recovery testing, we started getting these specific errors. I have seen the same mentioned without a resolve in some posts here. So I am adding specific questions for anyone that is doing this.

We get these errors.

Server1

Code: Select all

3/24/2021 8:21:55 PM Error    Importing VM Error: Failed to import machine to Amazon EC2: FirstBootFailure: This import request failed because the instance failed to boot and establish network connectivity.

Server2

Code: Select all

3/24/2021 8:41:05 PM Error    Importing VM Error: Failed to import machine to Amazon EC2: The request must contain the parameter size or snapshotId

The machines we are trying to restore at AWS are normally VMware VMs.
They have Fixed IPs, VMware tools installed, normally backed up while powered on and have Antivirus installed.

Do anybody running these types of restores have any issues and do you do anything specific to make sure your VMs are EC2 compatible?

[Gostev]

Hello! Please include a support case ID for this issue, as requested when you click New Topic. Thanks!

[veremin]

The second issue has been caused by Amazon changing some API that we're relying on. Currently, we are working on a hotfix for the issue, I will keep you updated about its status. Thanks!

[veremin]

Update: last week the R&D team was busy working on the cumulative patch, so the hotfix development has been put on hold. This week they are getting back to it, so it should be ready in the next few days. Thanks!

[veremin]

The hotfix for 10.0.1.4854 was provided yesterday. If that's the version you're currently running and you still didn't get the hotfix, kindly, refer to the case number 04694722 to receive it. Thanks!