Worker Issues - "The worker was stopped"

[gmoraes]

Hello,
I set up a free tier demo for Veeam for AWS at my company so we can see if it's the right product to migrate to but i keep having issues when trying to restore files from backup.

1st issue is that all my workers are being created as a t3.medium instance even after i set up the profile to use the aws default instances type (c5.large, xlarge, 2xlarge).
2nd issue is that the restore is failing after 30-45 minutes of restoring the file (files are very large. i tried a 1.7TB then when down to a 100GB file) with a message that says "The worker was stopped".
The job fails and the worker terminates by itself.

Is this a limit for the free tier of veeam for AWS? if it is, i may check with Veeam if we can get some trial of the full version so i can present to management.

Thank you!

[nielsengelen]

Hi Gustavo,

I am not aware of limitations on the free product regarding this issue. In which region are you trying to configure it? It could be that a specific instance size is not available in a region and therefor it would explain the first issue.

On the second issue, what type of restore are you performing at the moment? Instance, volume or file-level restore?

[gmoraes]

The region is eu-central-1.
I'm trying to do a file-level restore. It works for small files (i tried a couple of pictures/txt files) but it fails on the large 1.7TB bak and 100GB rar files

[nielsengelen]

There should not be an issue in that region as we often use it as well. The selected c5 sizes are also available there.

Could you please contact our support team (open a free case) and let us know the case ID so we can follow it?

[gmoraes]

Hello nielsengelen,
I'm trying to open a ticket but Veeam for AWS is not showing under the "free products" category. only under Marketplace.
Is it ok to open a ticket this way? it asks for my company's AWS ID and Support ID. All other options on the "free product" category does not ask for any personal account id.

Thanks!

[gmoraes]

Case #05596849
Worker Issues - "The worker was stopped"

[nielsengelen]

Thank you for the case. We'll follow it as well to hopefully find a quick solution.

[gmoraes]

Update:
instance size is resolved. support had me manually make changes to the config.ini file to add c5 instance types. Worker now being created as a C5.
Worker stopped issue: Still working on this. uploaded the log file this morning to find out why worker thinks it's idle (timing out) even when there is a restore job running.