60e to 60f changing the configuration version file and upgrading from 7.0.11 to 7.2.6

[Tabish]

Hi Support,

When migrating from 60e to 60f, do we need to change the conf ver file during backup push.
#conf_file_ver=170387064977772676.

Also firmware of our new fw 60f is on version 7.2.6 and old  60e is on 7.0.11.

Can we directly upgrade 7.0.11 to 7.2.6 and take backup and push it to 60f?

Because as per upgrade path it is showing h 7.0.11>7.0.12 >7.0.13 then all the way to 7.2.6f. It is very time consuming 10 firmware version are their between the two.

[AEK]

Hi Tabish

Restoring a configuration from one FGT model to another different FGT, or from one FOS version to a different FOS version is not supported, and will not work in most cases.

The solution is to use FortiConverter or to adapt the configuration by hand (requires some knowledge).

[dingjerry_FTNT]

Hi @Tabish ,

I haven't compared the FGT 60E and 60F hardware specifications.  If they have the hardware specifications, such as, the same number and same name of the interfaces,  the same disks, and so on, yes, you can replace the configuration file header directly to use it on FGT 60F.

And please do not upgrade to 7.2.6 directly, because it is not officially supported and we don't know what will happen to the configurations in this way.

[Tabish]

Hi @dingjerry_FTNT @AEK,

Yesterday we did migration from 60E to 60F and pushed backup to new one without any issue.

I only made fortilink port as regular port and rename them as per old backup and everything work successfully.

[sw2090]

it will work if bothg FGT share at least the same interfaces or if the new one has interfaces the old one hadn't. I would not recommend using different FOS versions. Either upgrade the old one to the same FOS the new one runs or vice versa.

[Tabish]

Yes I made sure both have same firmware before pushing.