CACTI upgrade (from 1.1.38 to 1.2.2 +)

[jhonnyx]

Hi Everyone,

I am running a 5 pollers deploymeny (1 main and 4 remote) running version 1.1.38 and at the moment is stable.

Now to keep up with the latest improvements I am thinking to upgrade to version 1.2.2 (or what will come next)

In the following page ( https://github.com/Cacti/documentation/ ... g-Cacti.md ) I can see a nice guide on how to run upgrades (that I regularly did up to 1.1.38 until now), but I would like to know if is a required or suggested step to upgrade also the database and in case what is the best approach?
I read also that remote pollers are updating themselves but I'd like to know if also there is required a database update

Also in case of a rollback, are the remote pollers going to synchronize with the main poller and downgrade as well? what about the remote poller's database ?

Besides all this I would like to see version by version if there is any change on the required and supported base software versions, like PHP and Apache, etc

Thanks a lot in advance (waiting for a backup function integrated in CACTI)

[netniV]

Database upgrades are just that upgrades. They never downgrade. If you want to rollback, backups are your best bet (just move your RRA's aside before restored then move them back to have the latest RRA's in place.

It's always worth turning off polling via cron or by disabling the pollers within cacti. In 1.3, we plan to implement a method of suspending the pollers during an upgrade but we aren't there yet.

All files will synchronise to the remote pollers (as long as the permissions are correct). Once each remote has the upgraded files, I think you have to visit each to perform the in place upgrade.

[jhonnyx]

Hi netniV

Apologies for resuming this topic after so long.

I have currently a smoothly working CACTI 1.1.38 deployment and I am a little afraid to upgrade it because that is in production but also I know that if I keep waiting it will be more and more risky to upgrade and keep up to date the platform.

Now it would be really nice or close to necessary for us that are running a medium sized implementation of CACTI (and doesn't just work on maintaining CACTI ) to have guidelines that are less general purpose and more integrated to a wiki or a guide.

I experienced myself how disruptive can be a CACTI upgrade (early on versions, right) but still I was lucky because it wasn't in production yet.

Having said that, I know you guys makes a great job and that's a big effort indeed to bring CACTI to the new millenium
Fact that I use it in production shows appreciation enough I hope, just I have a team monitoring depending on it and I'd like to not be in the odd situation of being told that we gotta move to another NMS that is more stable :/

Thanks again and keep up the good job!