Feature Request: Retain volume type config on restore

[davehill]

I have an Outposts environment and it uses GP2 volumes.

When I restore instances using recent AMIs that have a default GP3 volume type - AL2023, RHEL 8 + and Win 2025 - Veeam is ignoring the GP2 I have configured, defaulting to GP3 and the restore fails.

Veeam is unusable on Outposts with certain AMIs.

I need Veeam to retain the volume configuration on restore or offer it as a configuration option during restore.

[nielsengelen]

Hi Dave,

When you perform the restore, there should be an option to change the AMI if the original one is incorrect (as explained in our user guide).

Keep in mind that Outposts support is experimental so certain features may not work properly due to the limitations of the configuration.

[davehill]

Hi Niel,

Amazon Linux 2023 uses GP3 by default and I configured my instance to override that behaviour to use GP2.

When I restore the instance using VBA it ignores my config and uses GP3, which fails the job.

If I use a new Amazon Linux 2023 AMI during restore it will also default to GP3 and break.

I need Veeam to retain the volume type I have configured.

[nielsengelen]

Hi Dave,

Let me check if we have a workaround for this and report back to you.

[davehill]

There is a workaround - I'm making custom AMIs from RHEL9 and AL2023 volume snapshots and hardcoding GP2

[davehill]

But if I'm restoring a batch of 50 instances in response to a disaster of some kind i don't want to mess around with this.