Ad Widget

**Markku** · 12-12-2022, 19:31

First of all you need to read and understand all the upgrade notes between 4.2.x and 6.0.12: https://www.zabbix.com/documentation...l/installation (and from that on)

What I would do is roughly this (I'll just plain and simple assume that the operating systems and the database is some old version anyway):

Install new database server and import the current database there
Install new Zabbix server and start it against the new database server
Install the new frontend(s) and other additional stuff on new server(s)
Shutdown the old processes, change the old server IP addresses and change the new server IP addresses.

Zabbix server process will automatically upgrade the database from 4.2 to 6.0 when started (see zabbix_server.log for any errors). Do note that you will still need to check your zabbix_server.conf to be correctly set up with Zabbix 6.0.x. Maybe there are some other required or optional changes that you need to execute manually in the database, the upgrade notes will tell you that.

Markku

**cyber** · 13-12-2022, 09:40

I'm not sure you will benefit from doing that upgrade to 4.4.10 in between and then going to 6... And all those agent, get, sender versions are kind of irrelevant in all this process. Markku pretty much said it all, what you need to do..

**alexw-z** · 13-12-2022, 10:05

Thanks for the replies guys. I've read the release notes already, and the software version numbers are just for completeness really, I'm not so worried about agent & tool versions.

The old server is indeed an older version of Ubuntu (14 or 16 from Memory), and the new platform will be Alma 8 (hence the kinda convoluted 2 step upgrade process to get around some dependency issues). The new box will be stand alone initially, with a second HA node added at a later date.

My understanding was that it would be best to upgrade to 6.0 from the latest version of 4.4, and that the versions should match.

Is it safe to port a 4.2.x database into a new box running 4.4.10? I would have thought that would have the potential to cause problems.

**cyber** · 13-12-2022, 10:20

since v2 of zabbix there is possibility to directly upgrade from whatever version to latest. That's why I said, you don't really benefit from doing double upgrades... It should not really matter if you go to 6.0 from 4.2 or 4.4. I don't know how big your DB is, but you can export all your tables as csv and import to new DB version (whatever Mariadb version you may choose there), and recreate old version DB schema.... So you would have new platform with old DB content. Your new server will do all the necessary conversions, when you run it first time. You may need to run some additional conversion patches (primary key adding and some double precision mods on tables) later, but those are in release notes (also read the inbetween versions (5.x) release notes..

).

**alexw-z** · 13-12-2022, 10:51

Just checked back on my notes (I'm resuming this project after being blocked for a few months), I'm blocked from upgrading directly to 6.0 on the current box as version of Ubuntu is EOL and doesn't have the necessary versions of PHP and/or MySQL/Maria.

I'm aware technically I could do a distro upgrade but I've never done them (I'm a CentOS guy), and read varying reports about them - especially given the original boxes were built by my predecessor and some of his configs are a bit... idiosyncratic. Another primary goal is to move the service away from Ubuntu as a platform and onto a box I've designed and built myself. That's the reason for the two step process, so I can get to a sensible version to incorporate a platform jump.

I've actually done a dry run of a sandboxed copy of the prod box (like I said it's just stand alone so the solution was simpler), and got that up to 6.0 with just a couple of minor tweaks needed, but as I said I'm in this weird situation where the pre-prod instance is more complex than the prod one (I was initially led to believe that the pre-prod instance was a not in service POC thing, hence why I've ended up evaluating pre-prod after doing a dry run on prod, I appreciate some of this approach sounds a little bit backwards

), so I'm just trying to iron out whether there's a preferred upgrade order where multiple nodes are a factor. Otherwise I'm fairly comfortable with my plan.

**cyber** · 13-12-2022, 12:03

yep, thats true, your old platform will not support latest versios. But as you plan to change it anyway..

All you need is DB contents basically..

Set up parallel instance, copy over DB contents and run it..

I recently did the same to go from 4.4 to 6..

multiple corosync/pacemaker proxy clusters, HA frontends and DB-s..

yada-yada... the main task was to transfer database and run it on new platform. I needed to go from RH7 to 8, but even going from ubuntu to RH /Centos or something else would have been pretty much the same... Get parallel (and up to date) platform going and insert data. I would do dist upgrades only on some desktop host..

better to start clean on servers.

But if you really want to do that 4.4 there... just introduce new repos to those hosts (http://repo.zabbix.com/zabbix/4.4/ub...abbix-release/ and something according to your version of buntu). Then stop everything and make sure it will not start automatically. Then upgrade everything. Going from 4.2 to 4.4 should be pretty painless. Then start up DB, after that server, check server logs, that it does all needed tasks and stays running. After that start up frontend(s). Then you can already go back and restore automatic startups, where needed etc.

**alexw-z** · 14-12-2022, 14:05

Brilliant - thanks for the replies/confirmation

Ad Widget

Best Order To Upgrade Zabbix Cluster?

Best Order To Upgrade Zabbix Cluster?

Comment

Comment

Comment

Comment

Comment

Comment

Comment