Skip to main content
Question

Backup all FME Server workspace versions

  • April 8, 2020
  • 5 replies
  • 90 views

g_karssenberg
Contributor
Forum|alt.badge.img+7

We have FME Server running (2019.0.1 - 19253 - win64 - patch 1) with version control enabled without remote Git repository. I am planning an upgrade and I am looking for a way to handle and keep the workspace versions in the repositories.

The preferred way would be to have all versions restored on the new FME Server version. Unfortunately this is not possible with the default backup mechanism. If restoring all versions is not possible or very difficult, another option would be to at least backup all the workspace versions to be able to use these in the future if needed. Of course it is not preferable that we have to download all these version manually.

I looked at the REST API, but there appear to be no calls to download all versions. Other option might be to access the FME Server database on the machine to get the files, but I did not look into that yet.

Does anyone know of a way to accomplish a solution for this problem?

This post is closed to further activity.
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.

5 replies

g_karssenberg
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • 32 replies
  • April 10, 2020

I used a combination of the following (unofficial) calls to the FME Server REST API to download all workspaces that where published using commits:

https://[host]/fmerest/v3/versioncontrol/local/commits?repository=[repository name]

https://[host]/fmerest/v3/versioncontrol/local/commits/[workspace sha value]?accept=contents

This solves the backup issue, but I am still looking for a possibility to restore all workspaces (including commits) on the new FME Server installation. Anyone?


erik_jan
Contributor
Forum|alt.badge.img+22
  • Contributor
  • 2179 replies
  • April 10, 2020

I don't know if there is a solution (I could not find one), but it is definitely worth posting this as an idea for future development.

I believe if versioning is enabled, exporting all versions should be an option.

I will vote for the idea when you post it.


g_karssenberg
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • 32 replies
  • April 15, 2020

I don't know if there is a solution (I could not find one), but it is definitely worth posting this as an idea for future development.

I believe if versioning is enabled, exporting all versions should be an option.

I will vote for the idea when you post it.

Added two ideas:

https://knowledge.safe.com/idea/111943/ability-to-download-all-workspace-versions-from-fm.html?

https://knowledge.safe.com/idea/111944/backup-and-restore-all-workspace-versions-to-fme-s.html?


thijsknapen
Contributor
Forum|alt.badge.img+11
  • Contributor
  • 155 replies
  • April 15, 2020

I used a combination of the following (unofficial) calls to the FME Server REST API to download all workspaces that where published using commits:

https://[host]/fmerest/v3/versioncontrol/local/commits?repository=[repository name]

https://[host]/fmerest/v3/versioncontrol/local/commits/[workspace sha value]?accept=contents

This solves the backup issue, but I am still looking for a possibility to restore all workspaces (including commits) on the new FME Server installation. Anyone?

May I ask how you found out about this unofficial functionality of the FME Server REST API?


g_karssenberg
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • 32 replies
  • April 16, 2020

May I ask how you found out about this unofficial functionality of the FME Server REST API?

I used the Chrome DevTools (F12) to monitor network traffic and calls while using e.g. the History and Download Workspace buttons in FME Server.