Upgrade appliance without internet access - what needs to be backed up

[angrysysadmin]

I have a Zabbix appliance running on my Hyper-V server. I need to upgrade it to the latest version. Unfortunately the default "easiest" way to do this is to run "dnf update zabbix* but that requires appliance to have internet access. My appliance is on a secure network which does not have any internet access. Due to company rules I cannot give Zabbix access to internet.

So I am thinking the only other way to upgrade would be to:

1. Make a full backup of existing database
2. Download new VHDX appliance
3. Replace the VHDX on the HyperV server with the new one
4. restore the backup

Is this sufficient to preserve ALL existing settings, connections, history, etc etc or are there any other local files in the appliance I need to backup and restore as well?

Or maybe is there an easier way to upgrade?

[cyber]

You do not mention any version numbers... With minor version upgrades it might be easy, but with major upgrades you might need to keep old DB and let appliance run upgrade tasks...

[tim.mooney]

I have a Zabbix appliance running on my Hyper-V server. I need to upgrade it to the latest version. Unfortunately the default "easiest" way to do this is to run "dnf update zabbix* but that requires appliance to have internet access. My appliance is on a secure network which does not have any internet access. Due to company rules I cannot give Zabbix access to internet.

An rpm software repository as used by dnf or yum is nothing more than a web server, copies of the rpms, and some metadata. Could you mirror the official Zabbix repo to an internal web server that your appliance does have access to? If you have "reposync" that's a powerful tool for doing that, but you can accomplish what you need using something as simple as wget or curl, plus the "createrepo" tool to rebuild the repo metadata based upon what packages are present.

Once you have the repo mirrored, you just modify the repo definition(s) on the appliance to point to your local server, rather than the upstream Zabbix vendor repo.

Fully or partially mirroing a software repository isn't hard once you understand how basic a repo is, and it's a good tool to have in your toolbox.