Fresh/New installation using old config.xml backup from 2.3.4 ? How to?
-
The instructions say yes, 2 sticks.
I would believe the installer may be programmed to use config.xml if it exists.
I'll let you know tomorrow as I need to do this also.Doug
-
;)
https://doc.pfsense.org/index.php/Automatically_Restore_During_Install
Doug
I've found this method to be extremely unreliable. Your safest best is to save a copy of your config and then do a fresh install. Once you are able to make it to the dashboard restore your saved config file.
-
It's pretty simple with 2.4:
Start the installation.
Choose the option to recover an existing config.
Select the partition of your old pfSense installation.
It will then mount it and read the config.
After that continue installing the normal way and you'll be done.If that fails, setup your LAN interface in the console and restore a backup of your config via the WebUI.
-
;)
https://doc.pfsense.org/index.php/Automatically_Restore_During_Install
Doug
I've found this method to be extremely unreliable. Your safest best is to save a copy of your config and then do a fresh install. Once you are able to make it to the dashboard restore your saved config file.
Do i have to clear the config.cache after restoring the config.xml ?
-
Ok. i did it. No problems at all! :-)
i did a fresh install over IPMI. After installation process was finished i restored the config.xml and did a restart.
no problems at all.thx4all
-
So is it really better to recover the file during the installation or just restore it in the dashboard when pfsense is already reinstalled?
-
I have just had to restore a 2.3.4 config onto a fresh 2.4 system (upgrade to 2.4 via GUI failed, long story, file system got corrupted somehow).
Doing a fresh install of 2.4, then restoring the 2.3.4 config backup worked perfectly. All packages were installed automatically and everything seems fine. Entire system back up and running very quickly.
Restore was done via gui diagnostics menu after the system was up and running with default config btw.
For ref, this was done on a PCEngine APU1D4 via a serial cable.
-
I have just had to restore a 2.3.4 config onto a fresh 2.4 system (upgrade to 2.4 via GUI failed, long story, file system got corrupted somehow).
Doing a fresh install of 2.4, then restoring the 2.3.4 config backup worked perfectly. All packages were installed automatically and everything seems fine. Entire system back up and running very quickly.
Restore was done via gui diagnostics menu after the system was up and running with default config btw.
For ref, this was done on a PCEngine APU1D4 via a serial cable.
I see. Did you reinstall it in UEFI mode?
-
I have just had to restore a 2.3.4 config onto a fresh 2.4 system (upgrade to 2.4 via GUI failed, long story, file system got corrupted somehow).
Doing a fresh install of 2.4, then restoring the 2.3.4 config backup worked perfectly. All packages were installed automatically and everything seems fine. Entire system back up and running very quickly.
Restore was done via gui diagnostics menu after the system was up and running with default config btw.
For ref, this was done on a PCEngine APU1D4 via a serial cable.
I see. Did you reinstall it in UEFI mode?
No, standard bios I’m afraid. The APU uses the open source coreboot firmware which I believe is comparable to legacy bios.
-
I have just had to restore a 2.3.4 config onto a fresh 2.4 system (upgrade to 2.4 via GUI failed, long story, file system got corrupted somehow).
Doing a fresh install of 2.4, then restoring the 2.3.4 config backup worked perfectly. All packages were installed automatically and everything seems fine. Entire system back up and running very quickly.
Restore was done via gui diagnostics menu after the system was up and running with default config btw.
For ref, this was done on a PCEngine APU1D4 via a serial cable.
I see. Did you reinstall it in UEFI mode?
No, standard bios I’m afraid. The APU uses the open source coreboot firmware which I believe is comparable to legacy bios.
I see. So we're not UEFI-compatible, bummer :(
