Skip to main content
  • EN

Hi,

We upgraded our acceptance FME Server: versie 2017.1.1.2 - Build 17654 - win32 to versie 2019.0.0.1 win32 build 19246.

We are trying to restore the 2017 back on the 2019 server but it failed. There is little logging information that I see at an initial glance.

We tested the backup on the 2017 environment before we uninstalled and it was successful.

We did a 2015 to 2017 upgrade last time and the 2015 backup worked on the 2017 server.

Should we be able to restore the 2017 backup on the 2019 server?

I have opened a ticket with our vendor here but this usually takes awhile. Has anyone else successfully been able to restore a 2017 backup on a 2019 server?

Thanks,

Annette

 

How much later can the version be for the backup to restore successfully?

https://docs.safe.com/fme/2018.1/html/FME_Server_Documentation/Content/AdminGuide/Upgrading.htm

We are doing an upgrade on the same acceptance server.

 

 

Hi @annette2.

This is definitely something you want to report to www.safe.com/support

The backup and restore is made for these cases and should work.

Hi @annette2.

This is definitely something you want to report to www.safe.com/support

The backup and restore is made for these cases and should work.

Thanks Erik. I thought so too. I've logged a ticket with our vendor (your old colleagues). Bedankt en groeten vanuit Delft.

How much later can the version be for the backup to restore successfully?

https://docs.safe.com/fme/2018.1/html/FME_Server_Documentation/Content/AdminGuide/Upgrading.htm

We are doing an upgrade on the same acceptance server.

 

 

@richardatsafe We still are not having any luck with this. Our vendor is experiencing the same issue as us.

Is anyone else experiencing this issue too?

The backup works in Server 2018. We took a backup from 2018 and tried this in Server 2019 but his also failed.

 

We want to upgrade to 2019 as it supports our Portal for ArcGIS and 2018 doesn’t. But we have to retire our existing production server by the end of May.

 

Has there been any other cases of this issue?

 

Thanks,

 

Annette

Stedin, Rotterdam

@richardatsafe We still are not having any luck with this. Our vendor is experiencing the same issue as us.

Is anyone else experiencing this issue too?

The backup works in Server 2018. We took a backup from 2018 and tried this in Server 2019 but his also failed.

 

We want to upgrade to 2019 as it supports our Portal for ArcGIS and 2018 doesn’t. But we have to retire our existing production server by the end of May.

 

Has there been any other cases of this issue?

 

Thanks,

 

Annette

Stedin, Rotterdam

Can you try breaking it up into projects and export/restore those?

@richardatsafe We still are not having any luck with this. Our vendor is experiencing the same issue as us.

Is anyone else experiencing this issue too?

The backup works in Server 2018. We took a backup from 2018 and tried this in Server 2019 but his also failed.

 

We want to upgrade to 2019 as it supports our Portal for ArcGIS and 2018 doesn’t. But we have to retire our existing production server by the end of May.

 

Has there been any other cases of this issue?

 

Thanks,

 

Annette

Stedin, Rotterdam

I had the same problems when I did it to the 2019 RC. However it appears our IT guy was able to migrate them. I got around this by using what @redgeographics suggested of using projects.

@richardatsafe We still are not having any luck with this. Our vendor is experiencing the same issue as us.

Is anyone else experiencing this issue too?

The backup works in Server 2018. We took a backup from 2018 and tried this in Server 2019 but his also failed.

 

We want to upgrade to 2019 as it supports our Portal for ArcGIS and 2018 doesn’t. But we have to retire our existing production server by the end of May.

 

Has there been any other cases of this issue?

 

Thanks,

 

Annette

Stedin, Rotterdam

@redgeographics @runneals many thanks for the tips. Exporting to projects might be an option as a last resort - there are a lot of workspaces and multiple departments using the server to publish. We are using built in log-ins so I guess it would mean creating all the accounts and roles again too. Safe have been able to reproduce the issue and repair the backup. I'm waiting to hear if it is a long term fix i.e. will we be able to upgrade in the future after this fix.

@redgeographics @runneals many thanks for the tips. Exporting to projects might be an option as a last resort - there are a lot of workspaces and multiple departments using the server to publish. We are using built in log-ins so I guess it would mean creating all the accounts and roles again too. Safe have been able to reproduce the issue and repair the backup. I'm waiting to hear if it is a long term fix i.e. will we be able to upgrade in the future after this fix.

I've been in this situation myself a few times and it would be nice to get a bit more useful information in the error message so at least you'd know what caused the restore to fail.

I've been in this situation myself a few times and it would be nice to get a bit more useful information in the error message so at least you'd know what caused the restore to fail.

Never had any problem using the backup functionality myself but was wondering if the logs or system folder in the resources could contain more info about a failed backup?

Reply


Community Stats

29,983
Posts
113,913
Replies
37,613
Members
Terms & ConditionsCookie settings