The FME Server docs do a good job of telling you how to uninstall and reinstall Server, whatever configuration you choose. However, if you want to migrate from last year's FME Server to the latest release, you have to backup and uninstall everything first. This might work fine for an Express install. But if you have a distributed install of FME Server, the server backup only contains the workspaces, repositories, services and supporting files from your last install. Your previous architecture's configuration isn't stored anywhere. How would you recommend backing up your previous distributed configuration settings (network locations, ports, service account names, etc) to make it easier to install the new release so you have the same configuration as before?
How do you upgrade and migrate a distributed install of FME Server?
+20- Safer
- 3719 replies
Best answer by rylanatsafe
As far as the "typical" backup procedure or best practice goes, I think that a great starting point would be the Migration and Upgrade Chapter from the FME Server Admin Course that was presented at the 2017 FME UC!
I would also strongly recommend users to document their FME Server installation and configuration processes in a separate document. I have seen a few that are really well done – complete with screenshots!
Even if you use the (now discontinued - or is it?) MS Paint to sketch out your FME Server Architecture, I think it would prove very useful during a full upgrade procedure – or if you ever have to pass on the task to another colleague.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+14- Safer
- 671 replies
- Best Answer
As far as the "typical" backup procedure or best practice goes, I think that a great starting point would be the Migration and Upgrade Chapter from the FME Server Admin Course that was presented at the 2017 FME UC!
I would also strongly recommend users to document their FME Server installation and configuration processes in a separate document. I have seen a few that are really well done – complete with screenshots!
Even if you use the (now discontinued - or is it?) MS Paint to sketch out your FME Server Architecture, I think it would prove very useful during a full upgrade procedure – or if you ever have to pass on the task to another colleague.
+16- Supporter
- 81 replies
As far as the "typical" backup procedure or best practice goes, I think that a great starting point would be the Migration and Upgrade Chapter from the FME Server Admin Course that was presented at the 2017 FME UC!
I would also strongly recommend users to document their FME Server installation and configuration processes in a separate document. I have seen a few that are really well done – complete with screenshots!
Even if you use the (now discontinued - or is it?) MS Paint to sketch out your FME Server Architecture, I think it would prove very useful during a full upgrade procedure – or if you ever have to pass on the task to another colleague.
Hi @Ryan Cragg ,
Is there an updated version of this documentation for the latest version of FME Server? We are in a similar situation where we have a 2022.1 distributed FME Server that we need to upgrade due to the recent security vulnerability, and the standard upgrade documentation is not comprehensive, while the link above is old.
Thanks,
Marc
+5- Safer
- 89 replies
Hi @mgg_beca ,
These documents might be of help. I have tried to find current documentation equivalent to what is in the linked 2017 course chapter.
+16- Supporter
- 81 replies
Hi @mgg_beca ,
These documents might be of help. I have tried to find current documentation equivalent to what is in the linked 2017 course chapter.
Hi @Merline George ,
Those resources are useful, but none of them explicitly address the upgrade path for a distributed server deployment, where you have:
- 1 X VM with Web Applications/FME Core
- 1 X VM with FME Engines
- 1 X SQL Server with system DB
- 1 X File Share with System Resource Folders
My interpretation is that we should use the uninstall/reinstall approach on the Web/Core VM, and the FME Engine Upgrade approach on the FME Engine VM.
Questions:
- Can you please confirm this is appropriate, and if there are any additional considerations we should be aware of, and if there is a recommended order of operations for this upgrade?
- Besides restoring the backed up configuration, do we need to run any of the post-install scripts that we had to run after the initial installation?
- For the engine upgrade, the recommendation is to name the new folder fmeengineupgrade, which I'm not a fan of. Is it ok to name the previous FME Engine folder something like <FMEServerDir>\\Server\\fmeengine_2022.1 and install the new version into the <FMEServerDir>\\Server\\fme folder?
Cheers,
Marc
+5- Safer
- 89 replies
Hello @mgg_beca ,
After consulting with my team, I recommend you go through the process/document for Distributing Components (2-Tier)
for upgrading your distributed setup [in place upgrade].
- You can start by taking a backup of your old install
- Uninstall FME Server
- Follow the install document above to completely install the new version.
Please note that you will have to rebuild the DB with the scripts provided in the new server installer package. Please do not reuse the DB scripts from an older install as the schema might undergo changes between versions.
- Follow this document to add FME Engines on a Separate Machine
- After the installation, you can restore your setup.
Please note that any post-install configurations are not stored in the backup. For example- the HTTPS config will need to be redone.
+16- Supporter
- 81 replies
Hello @mgg_beca ,
After consulting with my team, I recommend you go through the process/document for Distributing Components (2-Tier)
for upgrading your distributed setup [in place upgrade].
- You can start by taking a backup of your old install
- Uninstall FME Server
- Follow the install document above to completely install the new version.
Please note that you will have to rebuild the DB with the scripts provided in the new server installer package. Please do not reuse the DB scripts from an older install as the schema might undergo changes between versions.
- Follow this document to add FME Engines on a Separate Machine
- After the installation, you can restore your setup.
Please note that any post-install configurations are not stored in the backup. For example- the HTTPS config will need to be redone.
Thanks for the advice. This process is in dire need of streamlining. Having to reconfigure half the installation after an upgrade is pretty frustrating.
+11- Contributor
- 25 replies
Hello @mgg_beca ,
After consulting with my team, I recommend you go through the process/document for Distributing Components (2-Tier)
for upgrading your distributed setup [in place upgrade].
- You can start by taking a backup of your old install
- Uninstall FME Server
- Follow the install document above to completely install the new version.
Please note that you will have to rebuild the DB with the scripts provided in the new server installer package. Please do not reuse the DB scripts from an older install as the schema might undergo changes between versions.
- Follow this document to add FME Engines on a Separate Machine
- After the installation, you can restore your setup.
Please note that any post-install configurations are not stored in the backup. For example- the HTTPS config will need to be redone.
Have there been any updates/changes to the process since this post?
+60- Celebrity
- 3704 replies
Hello @mgg_beca ,
After consulting with my team, I recommend you go through the process/document for Distributing Components (2-Tier)
for upgrading your distributed setup [in place upgrade].
- You can start by taking a backup of your old install
- Uninstall FME Server
- Follow the install document above to completely install the new version.
Please note that you will have to rebuild the DB with the scripts provided in the new server installer package. Please do not reuse the DB scripts from an older install as the schema might undergo changes between versions.
- Follow this document to add FME Engines on a Separate Machine
- After the installation, you can restore your setup.
Please note that any post-install configurations are not stored in the backup. For example- the HTTPS config will need to be redone.
Have there been any updates/changes to the process since this post?
The biggest change that was added fairly recently (and should be reflected in the current documentation) is that the backup is encrypted. So that means you need to download the encryption key from the original install and keep it safe, then do the backup, check that the backup actually downloaded (ask me how I know...), uninstall the old version, install the new version, update that encryption key with the one you’ve saved and then restore the backup.
Lose the encryption key and you can’t restore the backup.