Safe to move backup config file between different versions?

[torontob]

Hi Devs,

I would like to know what the general rule is about backup config files. Are there ANY risks to moving a backup config file from RC1 to a RELEASE for example or from a 2.0 to 2.3?

I am wondering what the general concept of backup config files are when upgrading hardware or pfSense release versions.

Thanks,

[jimp]

The primary rule is: Older configurations will always work on a newer pfSense

So a 2.0.x config will import OK to 2.1. Going from RC to RELEASE is also fine. So long as you're moving forward.

Going from new to old will NOT work in most cases. 2.1 to 2.0.x will not work.

[torontob]

Thanks for the input.

So, how are new features added? or is there a rule to just add new features and rename variables etc to make sure old configs are fine and if a new feature config is missing in the config file to be smart to move on?

Thanks

[jimp]

It could be that the format of a config section changed, something may be converted to/from an array, settings could move, variable names could change, etc, etc. Lots of different reasons. There is a configuration upgrade process that makes changes to the config as needed. It only happens when necessary.

The config format didn't change from 2.0 through 2.0.3, but it's already changed from 2.1 to 2.1.1.