Upgrading an Instance

The procedure for upgrading an FME Flow Hosted instance to a newer version of FME Flow depends on two factors:

  • The versions of FME Flow with which you are working.
  • Whether you can accept a change in URL of the upgraded instance, or you want to keep the same URL as the original instance.

Upgrading Between Versions of FME Flow Earlier Than 2024.0

Upgrading with a Change in the Instance URL

  • No downtime
  • Copies instance settings
  1. From the FME Flow Hosted instance you want to upgrade, clone a new instance.

    2. When the clone is ready, there should be two instances running: The original instance you are migrating from and the new instance you are migrating to.

  2. Backup FME Flow

    3. Connect to the original instance and perform a backup in the FME Flow Web User Interface. You can backup to a Resources folder or download the backup file. If you have a large amount of data on the instance, we recommend backing up to an Amazon S3 bucket, which you can create as a Resources connection. Since FME Flow Hosted resides on AWS, FME Flow Hosted instances have a very fast connection to S3.

  3. Backup the PostGIS Database

    4. If you are using the PostGIS database on the FME Flow Hosted instance to store data, you must migrate this to a new instance. Use PostgreSQL tools, either pg_dump (a command-line tool) or pgAdmin a GUI tool).

    Note   For information about connecting to external databases, see How to Connect FME Flow Hosted to an External Database in the FME Community.
  4. Restore FME Flow and the PostGIS Database

    5. Restoring FME Flow is the reverse of backing up. Connect to the new FME Flow Hosted instance and perform a restore in the FME Flow Web User Interface. You may need to mount your Amazon S3 resource connection first if you backed up to an Amazon S3 bucket.

    To restore the PostGIS database, use the pg_restore command, or pgAdmin.

  5. Terminate the Original Instance

    6. Once you have checked that the migration completed successfully, you can terminate the original FME Flow Hosted instance.

  6. Reassign the Plan to the New Instance

    7. If the original FME Flow Hosted instance was assigned to a plan, reassign the plan to the new instance. If the new instance is not the same type (for example, the original instance was a Standard and the new instance is a Professional), contact Safe Software support about upgrading your plan.

Upgrading and Keeping the Same Instance URL

  • 20+ minutes downtime
  • Does not copy instance settings
  1. Backup FME Flow

    2. Connect to the original instance and perform a backup in the FME Flow Web User Interface. You can backup to a Resources folder or download the backup file. If you have a large amount of data on the instance, we recommend backing up to an Amazon S3 bucket, which you can create as a Resources connection. Since FME Flow Hosted resides on AWS, FME Flow Hosted instances have a very fast connection to S3.

  2. Backup PostGIS Database

    3. If you are using the PostGIS database on the FME Flow Hosted instance to store data, you must migrate this to a new instance. Use PostgreSQL tools, either pg_dump (a command-line tool) or pgAdmin a GUI tool).

    Note  For information about connecting to external databases, see How to Connect FME Flow Hosted to an External Database in the FME Community.
  3. Snapshot Existing FME Flow Hosted Instance

    4. Take a snapshot of the original FME Flow Hosted instance. If there is an issue after terminating the original instance, you can rollback to it.

  4. Terminate Original FME Flow Hosted instance

    5. Once the snapshot is complete, you can terminate the original FME Flow Hosted instance.

  5. Launch New FME Flow Hosted Instance

    6. Launch a new instance with the required build.

  6. Restore FME Flow and PostGIS

    7. Restoring FME Flow is the reverse of backing up. Connect to the new FME Flow Hosted instance and perform a restore in the FME Flow Web User Interface. You may need to mount your Amazon S3 resource connection first if you backed up to an Amazon S3 bucket.

    To restore the PostGIS database, use the pg_restore command, or pgAdmin.

  7. Reassign the Plan to the New Instance

    8. If the original FME Flow Hosted instance was assigned to a plan, reassign the plan to the new instance. If the new instance is not the same type (for example, the original instance was a Standard and the new instance is a Professional), contact Safe Software support about upgrading your plan.

You should now have the latest build of FME Flow running, and it should have the same URL as your original instance. If satisfied, you can remove the snapshot you took of the original instance.

Upgrading From FME Flow Earlier Than 2024.0 to FME Flow 2024.0 or Later

Upgrading an Instance with a Change in the Instance URL

  • No downtime
  • Copies instance settings

  1. From the FME Flow Hosted instance you want to upgrade, clone a new instance.

    Note   You must create a clone to an FME Flow build number that is the same as or higher than the current FME Flow build number.
  2. Backup FME Flow

    3. Connect to the original instance and perform a backup in the FME Flow Web User Interface. You can backup to a Resources folder or download the backup file. If you have a large amount of data on the instance, we recommend backing up to an Amazon S3 bucket, which you can create as a Resources connection. Since FME Flow Hosted resides on AWS, FME Flow Hosted instances have a very fast connection to S3.

  3. Backup PostGIS Database

    4. If you are using the PostGIS database on the FME Flow Hosted instance to store data, you must migrate this to a new instance. Use PostgreSQL tools, either pg_dump (a command-line tool) or pgAdmin a GUI tool).

    Note  For information about connecting to external databases, see How to Connect FME Flow Hosted to an External Database in the FME Community.
  4. Restore FME Flow and PostGIS

    5. Restoring FME Flow is the reverse of backing up. Connect to the new FME Flow Hosted instance and perform a restore in the FME Flow Web User Interface. You may need to mount your Amazon S3 resource connection first if you backed up to an Amazon S3 bucket.

    To restore the PostGIS database, use the pg_restore command, or pgAdmin.

  5. Terminate the original FME Flow Hosted instance.
  6. Reassign the Plan to the New Instance

    7. If the original FME Flow Hosted instance was assigned to a plan, reassign the plan to the new instance. If the new instance is not the same type (for example, the original instance was a Standard and the new instance is a Professional), contact Safe Software support about upgrading your plan.

Upgrading an Instance and Keeping the Same Instance URL

  • 7-10 minutes downtime
  • Copies instance settings

  1. From the FME Flow Hosted instance you want to upgrade, clone a new instance.

    Note   You must create a clone to an FME Flow build number that is the same as or higher than the current FME Flow build number.
  2. Backup FME Flow

    3. Connect to the original instance and perform a backup in the FME Flow Web User Interface. You can backup to a Resources folder or download the backup file. If you have a large amount of data on the instance, we recommend backing up to an Amazon S3 bucket, which you can create as a Resources connection. Since FME Flow Hosted resides on AWS, FME Flow Hosted instances have a very fast connection to S3.

  3. Backup PostGIS Database

    4. If you are using the PostGIS database on the FME Flow Hosted instance to store data, you must migrate this to a new instance. Use PostgreSQL tools, either pg_dump (a command-line tool) or pgAdmin a GUI tool).

    Note  For information about connecting to external databases, see How to Connect FME Flow Hosted to an External Database in the FME Community.
  4. Restore FME Flow and PostGIS

    5. Restoring FME Flow is the reverse of backing up. Connect to the new FME Flow Hosted instance and perform a restore in the FME Flow Web User Interface. You may need to mount your Amazon S3 resource connection first if you backed up to an Amazon S3 bucket.

    To restore the PostGIS database, use the pg_restore command, or pgAdmin.

  5. Terminate the original FME Flow Hosted instance.
  6. Change the URL of the new instance to that of the old instance.
  7. Reassign the Plan to the New Instance

    8. If the original FME Flow Hosted instance was assigned to a plan, reassign the plan to the new instance. If the new instance is not the same type (for example, the original instance was a Standard and the new instance is a Professional), contact Safe Software support about upgrading your plan.

Upgrading Between Versions of FME Flow 2024.0 or Later

Upgrading with a Change in the Instance URL

  • No downtime
  • Copies instance settings

  1. From the FME Flow Hosted instance you want to upgrade, clone a new instance.

    Note   You must create a clone to an FME Flow build number that is the same as or higher than the current FME Flow build number.
  2. Backup FME Flow

    3. Connect to the original instance and perform a backup in the FME Flow Web User Interface. You can backup to a Resources folder or download the backup file. If you have a large amount of data on the instance, we recommend backing up to an Amazon S3 bucket, which you can create as a Resources connection. Since FME Flow Hosted resides on AWS, FME Flow Hosted instances have a very fast connection to S3.

  3. Backup PostGIS Database

    4. If you are using the PostGIS database on the FME Flow Hosted instance to store data, you must migrate this to a new instance. Use PostgreSQL tools, either pg_dump (a command-line tool) or pgAdmin a GUI tool).

    Note  For information about connecting to external databases, see How to Connect FME Flow Hosted to an External Database in the FME Community.
  4. Restore FME Flow and PostGIS

    5. Restoring FME Flow is the reverse of backing up. Connect to the new FME Flow Hosted instance and perform a restore in the FME Flow Web User Interface. You may need to mount your Amazon S3 resource connection first if you backed up to an Amazon S3 bucket.

    To restore the PostGIS database, use the pg_restore command, or pgAdmin.

  5. Terminate the original FME Flow Hosted instance.
  6. Reassign the Plan to the New Instance

    7. If the original FME Flow Hosted instance was assigned to a plan, reassign the plan to the new instance. If the new instance is not the same type (for example, the original instance was a Standard and the new instance is a Professional), contact Safe Software support about upgrading your plan.

Upgrading and Keeping the Same Instance URL

  • 3-5 minutes downtime
  • Copies instance settings

  1. From the FME Flow Hosted instance you want to upgrade, clone a new instance.

    Note   You must create a clone to an FME Flow build number that is the same as or higher than the current FME Flow build number.
  2. Backup FME Flow

    3. Connect to the original instance and perform a backup in the FME Flow Web User Interface. You can backup to a Resources folder or download the backup file. If you have a large amount of data on the instance, we recommend backing up to an Amazon S3 bucket, which you can create as a Resources connection. Since FME Flow Hosted resides on AWS, FME Flow Hosted instances have a very fast connection to S3.

  3. Backup PostGIS Database

    4. If you are using the PostGIS database on the FME Flow Hosted instance to store data, you must migrate this to a new instance. Use PostgreSQL tools, either pg_dump (a command-line tool) or pgAdmin a GUI tool).

    Note  For information about connecting to external databases, see How to Connect FME Flow Hosted to an External Database in the FME Community.
  4. Restore FME Flow and PostGIS

    5. Restoring FME Flow is the reverse of backing up. Connect to the new FME Flow Hosted instance and perform a restore in the FME Flow Web User Interface. You may need to mount your Amazon S3 resource connection first if you backed up to an Amazon S3 bucket.

    To restore the PostGIS database, use the pg_restore command, or pgAdmin.

  5. Verify that the new instance is working correctly, then change the URL of the old instance temporarily. Doing so frees up the URL so that it can be assigned to the new instance.
  6. Assign the original URL to the new instance.
  7. When the URL is successfully assigned to the new instance, terminate the original FME Flow Hosted instance.
  8. Reassign the Plan to the New Instance

    9. If the original FME Flow Hosted instance was assigned to a plan, reassign the plan to the new instance. If the new instance is not the same type (for example, the original instance was a Standard and the new instance is a Professional), contact Safe Software support about upgrading your plan.