Issue with Workers after upgrading from version 6 to 7.0

[enoch]

Hi,

Hope someone can help.

After upgrading fra over VBR the Azure Veeam Appliance from version 6 -> 7.0, we have issues with "Workers" when backing up in our West Europe Region. Our North Europe Region works fine with the "Workers"

I can see in the Worker Instance in GUI that workers is getting created for "West Europe" region. In Web GUI the workers shows as "Creating" but nothing happens! In Azure Portal I can see the machines getting created and they shows as "Running".

We have few backup jobs on "North Europe" region and those Workers works is created fine and working!

We have tried to stop the Workers and remove them. This will again let Veeam create new workers, but still as "Creating"

I'll start a case with Veeam, but maybe someone have a fix or what we can look at?

[nielsengelen]

Hi Peter,

Please work with support on this topic as we have a similar case that we are investigating and working on. Can you share the ID once opened with us?

[enoch]

Great,

This ID number on the case is: 07345314

[enoch]

I also see this issue in the general.log file:

Error: Unable to deploy a worker, the worker VNet not found. Provisioning of VM extension VBA-a121db56-85b7-4326-b3b1-4ebdd2af7680-CustomScript has timed out. Extension provisioning has taken too long to complete. The extension last reported "Plugin enabled".

The VNet exists so currently don't know what the issue is. It seems someone on the Worker provisioning fails and thereby cannot communicate with the Veeam for Azure appliance.

[nielsengelen]

Hi Peter,

Thanks for the case ID. We'll try to come up with a solution as soon as possible. For now, best is to work with support as it's unsure if this requires a fix from our side or something else while we analyze logs etc.

[enoch]

Thanks for reply, i'll contact the support again for "next action"

[enoch]

Hi Peter,

Thanks for the case ID. We'll try to come up with a solution as soon as possible. For now, best is to work with support as it's unsure if this requires a fix from our side or something else while we analyze logs etc.

If it's possible for you, please let the support take action in the case. We cannot off-backup customers backups and it is beginning to be critical.

[nielsengelen]

Hi Peter,

Sorry for the delay but it looks like in your last communication, it looks resolved. If not please let me know so we can escalate it if needed.

[enoch]

Yes, "somehow" it works today

What fixed or changed, I don't know

[Tobias.K]

I got a hot fix from the support to upgrade from v6 -> v7. We had some issues with snapshots not being able to get created.
After upgrade, we then experienced the same issue with workers being stuck on "Creating".

Support has been contacted - I will update whenever I receive feedback, in case someone else experiences these particular issues.

[Heyko]

Hi,

I have a simmilar issue. "Error: Unable to deploy a worker, the worker VNet not found.". Is there a solution for this error?

[aedens]

We seem to be running into a similar issue as well. At first issues with upgrading from 6 to 7 after we upgraded the B&R server to 12.2.
Received a fix (Azure plugin) from support after which we were able to upgrade the VBA.

Now backup jobs don't run (snapshots do) as the workers hang on 'Creating'... (VM's and related resources (nic, 2x disk) are being created in Azure with the expected vnet/subnet, and are running)
I don't see any errors about the workers in the general.log for the job though; last message regarding the workers is 'Worker VBA-e78338ea-a45f-4435-93a0-f080d1dc6571: setting up the network' and the silence...

Already working with support as a followup on the upgrade-issue; case 07412714

[david.domask]

Hi Arnoud, welcome to the forums.

Glad to hear the fix worked -- please continue with Support on the follow up issue, it's not clear if it's related to the current issue so let's allow Support time to review the new information.

Thanks!