Hi@madwarren,
there shouldn't be any issues restoring an FME Server backup from FME Cloud on your on-premise machine as long as the build of the FME Server you restore on is similar or higher.
Regarding instruction you only need to follow the documentation for theFME Server Backup & Restore.
Regarding the differences between the OS, the main thing to be aware of would be file paths.Linux is using forward slashes and windows backward slashes as separators in file paths.It is recommended to use the FME Server parameters when possible (e.g FME_SHAREDRESOURCE_DATA) instead hordcoded paths to avoid complications during migration.
I agree with@gisinnovationsb, there is a very high likelyhood of compatability issues.If you've used transformers, readers or writers that have been updated between FME 2016 and now those workspaces will not work on your FME Server.You can check this by opening the workspaces in FME 2016 Desktop and see if you get any warnings (or transformers go missing).
Best option would be to upgrade to FME Server 2018 too, then backup your FME Cloud and restore the backup in FME Server -or- create projects on FME Cloud and backup/restore those (as the full backup would also do the user management and security setup and you may want to set that up differently if it's running on-premises).
I doubt there will be much in the way of OS issues to be honest.The Windows version supports more formats than the Linux one actually, but to be on the safe side you can doublecheck in theFormats Matrix.
Hello@madwarren;
I believe that migrating from a higher build to a lower build would create problems, specifically when it comes to the workspaces.Is there a chance that you would be upgrading your FME Server to 2018?