Skip to main content
Solved

Backup and Restore to FME Server 2018 & moving drives

  • April 16, 2018
  • 3 replies
  • 37 views
ciarab
Contributor
Forum|alt.badge.img+9

Has anyone ever / Is it possible to do an upgrade from 2017 to 2018 Server but move drives and restore your config in the process.

For example 2017 is installed on the C Drive- company policies is to only allow 50gb on the C Drive and no permissions for me as an admin to write on the C Drive. So I can't delete old files make changes etc without bringing in I.T which is very frustrating.

Only solution is that we move FME Server to a new drive where we can have as much space as required. So my question is, if I take a backup of 2017 where everything is configured on the CDrive and I install 2018 Server and restore to the EDrive for example will everything work as expected? Or am I expecting too much :)

Best answer by jlutherthomas

Hi @ciarab

 

If you do a new install and point that to install in the E drive, FME will put all the new config files in there that you'll need then when you do the restore your workspaces etc should come back.

 

You may need to do some reconfigs if needed, eg SSL, AD...

 

That's better than using the same drive.

 

 

So you'd run the back up on the 2017 machine through the web ui then just do the import on 2018, it should be fine even if you're moving drives, as when you installed you told FME 2018 you told it to use the E drive.

 

I'd check the back up file before you install 2018 just to check it's valid. You could also make projects for any important work as a back up.
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.

3 replies

I
Forum|alt.badge.img
  • inovacaogis
  • 10 replies
  • April 16, 2018
There may be some inconsistencies because your workspaces were made in FME 2017, perhaps by uploading in 2018 the workspaces do not work correctly.

 

 

J
Forum|alt.badge.img+2
  • jlutherthomas
  • 364 replies
  • Best Answer
  • April 16, 2018

Hi @ciarab

 

If you do a new install and point that to install in the E drive, FME will put all the new config files in there that you'll need then when you do the restore your workspaces etc should come back.

 

You may need to do some reconfigs if needed, eg SSL, AD...

 

That's better than using the same drive.

 

 

So you'd run the back up on the 2017 machine through the web ui then just do the import on 2018, it should be fine even if you're moving drives, as when you installed you told FME 2018 you told it to use the E drive.

 

I'd check the back up file before you install 2018 just to check it's valid. You could also make projects for any important work as a back up.
ciarab
Contributor
Forum|alt.badge.img+9
  • ciarabContributor
  • Author
  • Contributor
  • 167 replies
  • April 16, 2018

Thanks @jlutherthomas that sounds promising! It would be great to get everything that's configured so far back up and running on a new drive but I'm willing to have to redo some work if required.

We have a preproduction Server too so I will run through the process in the test environment first. Hopefully it will be mostly smooth

Community Stats

32,087
Posts
121,852
Replies
39,729
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.