Follow these instructions to upgrade MOVEit Transfer while migrating to a new server for advanced cases: when MOVEit is using a remote MS-SQL DB, and optionally a remote filestore. This topic will also explain how to migrate a Web Farm, which requires both a remote MS-SQL DB and remote file store.

Depending on the complexity of your environment, you may want to contact Progress to discuss a professional services engagement to help with your upgrade.

Prerequisites

Before you upgrade MOVEit Transfer :
  • Review and understand the changes and differences applied to the version of the product you are upgrading to. It is best practice to review the Release Notes for each your existing and target version. 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 downtime for you and your users during the upgrade process. Consider the impact of the outage and your operational schedule.

Upgrade MOVEit Transfer with migration for advanced cases including web farms

注: To migrate a MOVEit Transfer Web Farm, it is best practice to migrate to a single node and then add new nodes to the farm. The primary node manages the database-specific information.
  1. Setup a new server, ensuring that it meets the system requirements in the release notes for the new version of MOVEit Transfer.
  2. Right click on latest version of MOVEit Transfer Installer on the new server, and run as the Windows Server Administrator. Follow the standard installation instructions. When prompted for a database, choose Microsoft SQL. Enter the same database server name that your existing MOVEit server points to, but enter a place holder or "dummy" database name and a "dummy" database user. Later in the upgrade process, you will repoint MOVEit at the existing data, using the existing database user account. At the end of the install, there is no need to go through a full post-install configuration, such as adding orgs or users.
  3. On the existing server, use the MOVEit Configuration utility to stop all services. If you are upgrading a Web Farm, stop the services on all nodes.

  4. Backup the existing server’s MOVEit settings and configuration data using the DMZBackup utility. If you are migrating a Web Farm, you only need to do this on Node 1. Because you will be pointing your new server at an existing database and file store, there is no need to backup the database or files.

    For example, for MS SQL:

    C:\MOVEitTransfer\Scheduler>DMZBackup.exe --without-database --debug
Zipping backup files to 
C:\MOVEitTransfer\Scheduler\MOVEitDMZ_Backup_20240311.7z
    DMZBackup is normally located at c:\MOVEitTransfer\scheduler. This will create a compressed .7z ("7zip") file with an automatically generated name.
    • Copy the .7z file that was created from that command to the scheduler directory on the new server (normally c:\MOVEitTransfer\Scheduler).
    • As a precaution copy the web.config file from MOVEit Transfer’s root web directory (normally c:\MOVEitTransfer\wwwroot) to a temporary directory on the new server for safe-keeping. Do not copy to the web root directory on the new server. Do not use unless instructed by Progress Technical support.
  5. On the new server, restore the 7z backup file. The command to restore the settings and configuration data to the new server.
    For example:
    C:\MOVEitTransfer\Scheduler>DMZRestore.exe --debug MOVEitDMZ_Backup_20240311.7z

    --use the backup file created in Step 4. The DMZRestore utility is normally located at C:\MOVEitTransfer\scheduler.

  6. 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. (the older license file was restored during Step 5.)
    2. On the Paths tab, ensure that everything is correct for the new server. The File store entry should point to the remote file store. Re-point the database to your production data, which should be on the same database server, but with a different name. Use the database server name and username as they were configured on the existing server.
  7. On the new server, you need to upgrade the schema on the MOVEit database on the MS SQL server. Although your new MOVEit server is now pointing at the correct data, it still needs to be upgraded to use the latest database schema. To accomplish this, re-run the new installer and choose ‘repair.’
  8. After this is done, reboot. Your new server should now have the latest version of MOVEit Transfer running, with all the settings, data, and files from your existing version. At this point, we recommend that you run through the procedures outlined in the Post Upgrade section linked below and perform at least the quick test.
  9. If you are migrating a Web Farm, after you have run the basic tests outlined in the Post Upgrade topic on the first node you just upgraded, you can then proceed to install MOVEit onto new server nodes as necessary following the standard install instructions with an existing database as if you were deploying these nodes for the first time. There is no need to perform any sort of restore from the existing nodes. Those are no longer needed. As you add new servers to the Web Farm using the MOVEit-Transfer-AddToFarm.exe utility (located in the c:\Program Files\MOVEit\Utilities\ directory), they will automatically get all the settings and data of the first node that you migrated.

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.