Regarding the account used for deploying worker instances when using Additional Restore Mode

[Asahi]

Hi,

In the current version of Vb4AWS, it appears that when “Additional restore mode” is selected, worker instances cannot be launched in the VPC of the production AWS account where the target EC2 instance resides.
https://helpcenter.veeam.com/docs/vbaws ... l-location

Is this a restriction on the AWS side?
Or is it a Veeam restriction?

Kind Regards,
Asahi

[nielsengelen]

Hi Asahi,

You can configure production network settings under the configuration section of the appliance. If you specify the same VPC as the EC2 instance, I believe it should work. Can you verify the configuration and let me know if these are different which would explain the issue you see?

[Asahi]

Hi,

When I looked into it, I found that it was clearly stated in the Veeam documentation as well.
※That was based on the assumption of cross-account functionality.

[This option applies only if you choose not to deploy worker instances in the production account]
https://helpcenter.veeam.com/docs/vbaws ... tml?ver=10

Kind Regards,
Asahi,
Climb Inc.

[nielsengelen]

Hi Asahi,

There is a second part on the user guide. You can deploy a worker in production for restores from Snapshot, Replica or Manual Snapshots.

If you are trying to perform the restore from the backup, then this is not possible as it's a limitation we have due to AWS and the architecture as of today.