Quick question about switching versions x86 -> x64
-
I just noticed that when I upgraded from 2.1 to 2.2, it put me onto the x86 version.
(Which explains why I had to reset my RRD data)Backing up my config, reinstalling (the x64 version) and restoring the config should get me up and running without any issues other than RRD data again, correct?
-
Yes. The config.xml file is transferable between architectures. The only thing to look out for is if you have been running snapshots at any time you may have specified a different update server which is architecture specific. That is almost always the cause of unexpected switch from 64 to 32bit or vice-versa.
Are you running packages?Steve
-
I went from official release to official release.
I do have packages, but nothing that would've affected this.
(arping, cron, file manager, notes, openvpn export)It's no matter though, I have downtime scheduled for Friday night. I'll swap versions then and make sure it's checking the right place.
-
You probably want to add those packages into your fresh install before you restore the config file for the smoothest transition.
Steve
-
I think I had read that the recommended upgrade when restoring from XML was to not install any packages and use an XML restore file that has no package details. Get the basic firewall up & running and then manually re-add your packages. That's how I'm planning to do mine either this Friday or next. Get a basic 2.2 running with our rules & general config. Later, I will add the handful of packages. I can't see it taking more than 15-30 mins to install & configure them all, and I don't have to worry about conf file incompatibilities between package versions.
-
You probably want to add those packages into your fresh install before you restore the config file for the smoothest transition.
Steve
I was actually planning on editing the XML to remove all reference to any packages and just have the firewall config and reinstall all the packages fresh after.
-
Good call. Be aware that you can easily make a mistake hand editing the file though. ;)
Trying to restore a complete config file that references packages onto an install that doesn't can have interesting results. I've tried that and it resolved itself OK but there were worrying looking errors. Whilst you can choose to restore individual areas on the config file there's no option to restore everything except packages. So you can restore each area individually but that's not a good idea if the config file version doesn't match the install. You can load the packages you had before. You can edit out the packages section. You can make a backup of the config file without the packages section but that requires some forethought!
Steve
-
I was actually planning on editing the XML to remove all reference to any packages
GAH! Don't do that! Just go to Diagnostics - Backup/Restore and check the Do not backup package information box.
-
Good call. Be aware that you can easily make a mistake hand editing the file though. ;)
Trying to restore a complete config file that references packages onto an install that doesn't can have interesting results. I've tried that and it resolved itself OK but there were worrying looking errors. Whilst you can choose to restore individual areas on the config file there's no option to restore everything except packages. So you can restore each area individually but that's not a good idea if the config file version doesn't match the install. You can load the packages you had before. You can edit out the packages section. You can make a backup of the config file without the packages section but that requires some forethought!
Steve
Actually I didn't notice the checkbox for backing up without package information.
That will work perfectly.Plus I can do two, one with and one without and see if there's anything specific I'd want to save.
