Skip to main content
Question

Questions about in place upgrade of FME Server 2022 to Flow 2024

  • February 14, 2025
  • 2 replies
  • 84 views

emo10001
Contributor
Forum|alt.badge.img+2

We are currently running FME Server 2022.2. on prem (not cloud hosted).  We had been planning on upgrading to the latest, but now even more so with the privilege escalation issue, and there apparently not being a fix for our version….except to upgrade.

Looking over the “in place upgrade” portion of the documentation, it seems we can simply backup the configuration files (we’re not using version control yet), do an uninstall of 2022.2, do a fresh install of the latest 2024, and then restore the configuration backup.

Are there any known issues with doing this from 2022 to 2024?  I know the product was rebranded in 2023, but the differences I could see between 2022 and 2023 seemed mostly cosmetic for the rebrand.  However, I know 2024 seems to be different.

I just really want to dot all my i’s and cross all my t’s, and keep any down time to a minimum.  And know if there are any “gotchas” that can be avoided.

Thank you.

2 replies

crutledge
Enthusiast
Forum|alt.badge.img+31
  • Enthusiast
  • March 6, 2025
emo10001 wrote:

We are currently running FME Server 2022.2. on prem (not cloud hosted).  We had been planning on upgrading to the latest, but now even more so with the privilege escalation issue, and there apparently not being a fix for our version….except to upgrade.

Looking over the “in place upgrade” portion of the documentation, it seems we can simply backup the configuration files (we’re not using version control yet), do an uninstall of 2022.2, do a fresh install of the latest 2024, and then restore the configuration backup.

Are there any known issues with doing this from 2022 to 2024?  I know the product was rebranded in 2023, but the differences I could see between 2022 and 2023 seemed mostly cosmetic for the rebrand.  However, I know 2024 seems to be different.

I just really want to dot all my i’s and cross all my t’s, and keep any down time to a minimum.  And know if there are any “gotchas” that can be avoided.

Thank you.

Hi There, Just wondering if you had any success on the in place upgrade? I am planning for a 2024 to 2025 move this year and wondered if you could share experience? If you haven’t moved maybe we could collaborate if you are going from 2022 to 2025. Let me know. Interested in your experience.
Best,
Clifford.


j.botterill
Influencer
Forum|alt.badge.img+36
  • Influencer
  • March 7, 2025

Hi there,

A good starting point is https://support.safe.com/hc/en-us/articles/34243509378061-Known-Issues-in-FME. There is always issues with new functionality being constantly introduced. I always recommend upgrading to the last build… e.g. 2024.2.3 for its stability as it has the most fixes applied.

I assume you only have an express installation, not a distributed deployment?

FME 2023 introduced flow encryption, so when you restore the 2022 back in the 2024 version, be sure to download the key, you’ll need it for future backup/restore operations.

 

An in-place upgrade requires a larger outage window compared to a side-by-side upgrade as the environment needs to be taken down during the uninstallation, deployment & configuration steps required. A side-by-side upgrade can minimise the outage window required, but then will require additional configuration changes to any load balancers, firewall rules and other infrastructure as the connectivity routes between FME Flow and other components will change.  

In place upgrade involves the following steps:

  1. Back Up Configuration.

Warning  If System Encryption is Standard (default) on the FME Flow that is backed up, it must also be Standard on the FME Flow that is restored, and use the same custom encryption key. Before proceeding, ensure your custom encryption key is downloaded and safely saved.

 

  • Backup configuration files from C:\Program Files\FMEServer or FMEFlow
    • fme[*].conf 
    • Any certs within ./lib/security/cacerts 
    • Tomcat configuration files from <FMEServerDir>\Utilities\tomcat\conf 
    • Tomcat keystore 
  1. Verify the integrity of the backup by restoring the configuration to the existing FME Flow. A successful restore indicates the backup is valid.
  2. Uninstall FME Flow.
  3. Install the newer version.
  4. Restore Configuration.

Upgrading Process using a Second machine… side by side:

To remove the need for an outage window, you can backup FME on MACHINE1. Restore the version on MACHINE2. You will have to manage the migration of the license and applying a new SSL certificate on machine 2. Also the FME Flow Web URL may need a different DNS entry depending on the magic your IT can perform.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings