Skip to main content
Question

Backup all FME Server workspace versions

g_karssenberg
Contributor
Forum|alt.badge.img

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?

5 replies

g_karssenberg
Contributor
Forum|alt.badge.img
  • g_karssenbergContributor
  • Author
  • Contributor
  • 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+17
  • erik_janContributor
  • Contributor
  • 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
  • g_karssenbergContributor
  • Author
  • Contributor
  • April 15, 2020
erik_jan wrote:

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+10
  • thijsknapenContributor
  • Contributor
  • April 15, 2020
g_karssenberg wrote:

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
  • g_karssenbergContributor
  • Author
  • Contributor
  • April 16, 2020
thijsknapen wrote:

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.

Reply


Helpful Members This Week

Community Stats

30,907
Posts
117,105
Replies
38,708
Members

Latest FME

Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.