Upgrade from 2.4.5 to 2.6
-
I've been upgrading our installs from 2.4.x to 2.6.0. The process has been to upgrade from 2.4.5 to 2.5.2 and then to 2.6.0 but that option isn't there anymore with the introduction of 2.7.0. I can only see 2.6.0 and 2.7.0 as options. Can I upgrade directly from 2.4.5 to 2.6.0? (New installs will be 2.7.0 but we want to hold off on upgrading existing installs pas 2.6.0 until we can verify everything will work properly.)
-
@Stewart said in Upgrade from 2.4.5 to 2.6:
Can I upgrade directly from 2.4.5 to 2.6.0?
I was reading in the forum anywhere that it is the best option to
go from 2.4.x to 2.5.x and then over to the version 2.6.By the way I would install a fresh 2.6 version and then based
on the ZFS (files system) and then it would be "better" to
go over to the version 2.7 as I see it.fresh 2.6 (zfs) > 2.7 (zfs) would be my way as today.
-
@Dobby_ I agree that skipping major versions isn't a great idea, but I can't exactly drive out to each location and replace the units. Since I no longer have the option to jump from 2.4.x to 2.5.x to 2.6.0, I'm trying to figure out what the right procedure would be from here.
-
@Stewart set System/Update to Previous Stable which is 2.6 until the next version comes out.
Also see my sig re packages. -
@SteveITS So, is it OK to go straight from 2.4.5 to 2.6.0?
-
@Stewart I have skipped versions before and been OK. I would follow the upgrade guide, namely to uninstall packages, upgrade, and reinstall packages. I don't recall what version PHP was in 2.4.5 but 2.6 to 2.7 jumps both OS and PHP versions. You can download the 2.6 image as a backup method (reinstall and restore) by going to pfsense.org/download, leave Architecture blank, and submit the form to see a few recent versions.
I was in another thread this week, and it sounds like Netgate's goal moving forward is to have the choices be "stay on whatever version you're on" and "upgrade to the latest". That would apply on 2.7 though.
-
@Stewart said in Upgrade from 2.4.5 to 2.6:
@SteveITS So, is it OK to go straight from 2.4.5 to 2.6.0?
I went from 2.4.5 to 2.6.0, but I did a clean install of 2.6.0 and restored the 2.4.5 config.xml file and it worked great. I don't know if the direct upgrade process works that smoothly. Ideally you'd test the process on-site and if it fails, be able to to a clean install of 2.6.0 and restore a fresh backup config, and if that works, ideally it'll work at your other sites.
