This topic describes how to upgrade MOVEit Transfer while migrating to a new server when MOVEit is using a local MySQL database and a local file store.

Prerequisites

Before you upgrade MOVEit Transfer :

  • Review and understand the changes and differences applied to the version of the product you are upgrading to.

    Before you proceed, it is best practice to review these documents:

    • Release Notes for your existing version of MOVEit Transfer.

    • Release Notes for your target (new) version of MOVEit Transfer.

      Remarque : Release Notes for all supported versions are available here: MOVEit Transfer
  • Review the Plan your upgrade topic in this guide.

  • Download the MOVEit Transfer installer package and activation code. See the following link for how to download the license file.

  • You should be confident in your backup strategy and that you can restore your current environment with a recent set of data in a timely fashion.
  • There will be application downtime for you and your users during the upgrade process. Consider the impact of the outage and your operational schedule.

To upgrade with migration to a new server deployment

  1. Set up the new server machine. For best results, you should install to a clean Windows Server machine. Consult the system requirements in the MOVEit Transfer Release Notes to ensure that the Windows Server version you are running is supported by MOVEit.
  2. Right click and run the new MOVEit Transfer installer as Windows Server Administrator on the new server machine. Create a new/fresh MySQL database instance in this process.

  3. Perform a basic test of MOVEit to make sure it is working as expected.

  4. On the existing server, use the MOVEit Transfer Config Utility to stop all services except

    for MySQL. Then use Windows Services to set the startup type for these services to ‘disabled.’

  5. Backup your existing MOVEit Transfer system using the DMZBackup utility. This will backup your MySQL database and several other configuration items. Although this utility can be used to also backup the file store, we recommend copying those files manually.
    1. Backup the database. Run the following backup command as an elevated user to copy your MySQL database and other MOVEit information without the file store:

      DMZBackup --with-files --debug

      DMZBackup is normally located at c:\MOVEitTransfer\scheduler.

    2. Copy the .7z file. Copy the .7z file that was created to the scheduler directory on the new server machine.

    3. Copy the MOVEit Transfer file store. Copy the contents of the existing file store folder to the new server machine. The file store is normally located at c:\MOVEitTransfer\Files.
      Important : Ensure you copy the contents of the existing Files folder into the Files folder on the new server machine. This prevents overwrite of permissions set by the new MOVEit Transfer installer. The new MOVEit Transfer instance expects these folder permissions to access the files in the folder it created.

    4. Save the site configuration (web.config). Save a copy of the existing web.config file to a temporary directory on the new server (it is created in C:\MOVEitTransfer\wwwroot). Do not use unless instructed by Progress Technical support.

  6. On the new server, restore the 7z backup file. Run the following command as an elevated user to restore the database and configuration data to the new server: dmzrestore --debug <backup-file-name> (replace with actual name of the backup file).
  7. Modify any MOVEit settings on the new server if necessary. Use the MOVEit Transfer Config Utility to check and potentially change a few items.
    1. If you used a license file when you installed MOVEit on the new server for the first time, you will need to use the license tab and reload the new license file.
    2. On the Paths tab, ensure that everything is correct for the new server. The filestore should point to the local filestore, and the database should be pointed at the local version of MySQL.
  8. Run a repair install to update the database schema. Although your MOVEit database has been moved to the new server, it still needs to be upgraded to use the latest database schema. Re-run the new installer and choose ‘repair.’ Run the MOVEit Transfer Installer in Repair mode.
    • When prompted, choose the Repair option.
    • If prompted to reapply database updates, select Yes.
    Important : As the installer runs and performs an upgrade on a large installation, it might take a longer than expected time to complete, and the status bar might not move for a few or many minutes. If this happens, please wait for the installer complete.
  9. If you are using a production TLS/SSL certificate, make sure to rebind it in the new server’s IIS configuration.
  10. After this is done, reboot. At this point, your new server should have the latest version of MOVEit Transfer, with all the settings, data, and files from your older version. Proceed to the Post upgrade section for information on testing and promoting the server to production.

Post upgrade

After the upgrade procedure is complete, post-upgrade/migrate you should perform post-upgrade tasks to verify that all data was imported and to test the system to ensure that all functionality is working as expected.

What to do if something goes wrong

When an issue arises in a migration, upgrade, or other install processes, consulting the install logs is a good way to begin the troubleshooting process. You may find enough information in the logs to resolve your issue. If you need assistance from our technical support team, they will ask for your install logs.

For information about how to locate install log files, see Locate MOVEit install logs.