Upgrade to v5 (from v3) failing with 502 Bad Gateway

[fmagic]

After we attempted to upgrade to v5, our system reported the "502 Bad Gateway" message on the login screen. We restored the system from a snapshot, and have it running again with v3, but we would like to get it upgraded. I am wondering if there (1) is a way to step up to v4 without going all the way to v5, or (2) if there is a way to back up the configuration (externally) from our current appliance so we can restore it to a new appliance? When the appliance was in the failed state, we can still access SSH. On the restored appliance, I did step through the upgrades one batch at a time, and the failure only occurred after applying the major updates: Veeam Backup for Microsoft Azure (5.0.0.579) and File level recovery for Veeam backup (6.0.0.682). I was able to apply all DotNetCore updates, and all Ubuntu updates, but it is after applying the major updates that the appliance goes into the 502 bad gateway state.

We are running the community (free) edition of Veeam Backup for Azure v3, so we cannot open a ticket with support.

Server version: 3.0.1.34
Worker version: 3.0.1.34
FLR service version: 4.0.0.360

[nielsengelen]

Even with the free edition you can open a case, it will be handled on available resources and best effort.

If you get 502, it means the webservice didn't start properly (or something else went wrong).

If you log in via SSH, you can most likely manually download and install v4. I do not have a v3 lab anymore but can you try the following:

Code: Select all

wget http://repository.veeam.com/vbazure/2/public/pool/main/v/veeamazurebackup/veeamazurebackup_4.0.0.714_amd64.deb
sudo dpkg -i veeamazurebackup_4.0.0.714_amd64.deb

[fmagic]

I have opened case 06017420. At this point, I have recovered the original appliance using a snapshot backup, since that is all that was available with v3, so I can attempt the upgrade again.

I did attempt the v4 upgrade with those instructions, but the DotNet software is now too new for the v4 upgrade to run, so I'm stuck with that recovery, too! If I could recover the configuration from the v3 appliance and apply it to a new v5 appliance, that would be my preference at this point so I can have a clean installation. This original appliance was deployed as v1, and upgraded to v2, then v3, so it's had a lot of upgrades over time. I'm not sure how we missed v4 since I check for updates monthly. We had paid support available until about a month ago, but we had to let that lapse.

admin@veeamaz:~$ sudo dpkg -i veeamazurebackup_4.0.0.714_amd64.deb
(Reading database ... 118879 files and directories currently installed.)
Preparing to unpack veeamazurebackup_4.0.0.714_amd64.deb ...
Unpacking veeamazurebackup (4.0.0.714) over (3.0.1.34) ...

dpkg: dependency problems prevent configuration of veeamazurebackup:
veeamazurebackup depends on dotnet-runtime-6.0; however:
Package dotnet-runtime-6.0 is not installed.
veeamazurebackup depends on aspnetcore-runtime-6.0; however:
Package aspnetcore-runtime-6.0 is not installed.
veeamazurebackup depends on veeamflr-netdep (>= 5.0.0.426); however:
Version of veeamflr-netdep on system is 4.0.0.360.

dpkg: error processing package veeamazurebackup (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
veeamazurebackup

[nielsengelen]

Hi Mike,

It doesn't look like it states that dotnet is too new but missing some packages.

Could you try the following maybe (again no lab so just using top of my head logic).

Code: Select all

sudo apt-get install veeamazurebackup=4.0.0.714

[fmagic]

That command suggested I run "apt --fix-broken install" to add the missing components, so I ran:

Code: Select all

sudo apt --fix-broken install

As soon as that was done, the GUI came alive with version 4, so I can now at least get in there and make a configuration backup to the Azure repository.

Since this was a clone, I had to go to Configuration\Administration\Accounts and edit the Azure account to reauthorize the application, and that worked.

I was able to make a configuration backup successfully to the Azure repository.

I plan to wait a day so this new appliance can get a snapshot, and then I'll either attempt to (1) upgrade the v4 appliance to v5, or (2) restore the configuration backup to a new v5 appliance.

[nielsengelen]

Hi Mike,

Glad that worked. Yes, please run v4 for a few days first. You can also use the Configuration Backup to create an extra backup on a repository.

This way, you could deploy a fresh v5 and import everything from v4 in case the upgrade would fail.