You are here: Web User Interface > Using the Interface > Backup & Restore

Backup & Restore

Select Manage > Administration > Backup & Restore.

The Backup & Restore page provides tools for performing backup and restore operations on your FME Server configuration. You can use the Backup tool to backup a current instance of FME Server 2014 or later. You can use the Restore tool to restore backed up FME Server configurations to an instance of FME Server that is of the same or later version.

For more information about FME Server backup and restore, see Upgrading FME Server.

FME Cloud Users: The tools on the Backup & Restore page of the Web User Interface do not allow you to perform a full restore of an FME Server instance, including FME Server data and the PostGIS database. To perform a backup and restore operation of an FME Cloud instance, launch a new instance from a backup snapshot using the tools on the FME Cloud Dashboard and the FME Cloud Snapshots page. For more information, see Working with Backups in the FME Cloud documentation.

Which FME Server Components are Migrated?

When you perform a backup and restore operation, the following components of your FME Server are migrated:

  • Repositories and the items stored in them, including workspaces, custom transformers, custom formats, templates, and resources. Any designations by users of a repository item as a 'favorite' are also migrated.
  • FME Server Services.
  • Notification Service components, including topics, subscriptions, and publications.
  • Security configuration, including users, roles, object policies, role policies, and tokens.
  • Schedules.
  • Resources, which include the following:
    • Resources whose definitions and files are both stored with FME Server, and are configured for migration. By default, these are the Data and Engine folders. To determine if your resource folders are migratable, open the FME Server configuration file at <FMEServerDir>Server\fmeServerConfig.txt. Locate your resources under FME SERVER SETTINGS START > Shared Resource Management. Resources with a SHAREDRESOURCE_ISMIGRATABLE_* value of true are migrated.
    • Note: Resource folders containing large amounts of data require considerable time to back up, and result in large configuration files. We recommend defining large folders as non-migratable. Following backup and restore, manually migrate these folders to the new FME Server. Alternatively, host big data on a UNC path, then point the new FME Server to that path. For more information about configuring resource directories, see Resources.

    • Online resources whose definitions only are stored with FME Server, but whose files are stored outside FME Server. In the current version of FME Server, these resources are limited to any Amazon Web Service (AWS) S3 bucket connections that are defined. Only connection definitions are migrated (such as bucket names and authentication parameters). The files contained within S3 buckets are not stored on FME Server.
  • Database Connections.

Performing a Backup and Restore