Version 24.2.8980

• Upgrading from CData Sync 2021, 2022, and 2023
• Upgrading from CData Sync 2020
• Upgrading from CData Sync 2017, 2018, and 2019
• Upgrading Marketplace Instances

This section describes the simple process of upgrading from an earlier release of CData Sync. For information about performing a fresh installation of CData Sync, see Starting the Server.

Upgrading from CData Sync 2021, 2022, and 2023

This section explains how to upgrade from Sync 2021, Sync 2022, or Sync 2023.

Sync 2024 is provided through a setup.tar.gz file. Follow these steps to upgrade an existing installation of Sync 2021, 2022, or 2023 to Sync 2024:

1. Stop the server in either of the following ways:

   • To stop server as a service, submit this command:

     sudo systemctl stop sync

   • To stop the service in-process, submit this command:

     java -jar sync.jar --stop

2. Extract the contents of setup.tar.gz to /opt/sync/.

3. Start the server in either of the following ways:

   • To start the server as a service, submit this command:

     sudo systemctl start sync

   • To start the service in-process, submit this command:

     java -jar sync.jar

Notes:

• No matter how you choose to deploy Sync, the files and folders that are contained in ApplicationDirectory must be readable and writable by the user who runs the application. The service.sh script that is included with Sync uses cdatasync as this user.

• If the application was previously run as a different user and you want to restore the necessary permissions for a cdatasync user to run the application, submit a command that is similar to the following:

  sudo chown -R cdatasync:cdatasync /opt/sync

Upgrading from CData Sync 2020

This section explains how to upgrade from CData Sync 2020 to CData Sync 2024.

Sync 2024 is provided through a setup.tar.gz file. Follow these steps to upgrade an existing installation of Sync 2020 to Sync 2024:

1. Stop the server in either of the following ways:

   • To stop server as a service, submit this command:

     sudo systemctl stop sync

   • To stop the service in-process, submit this command:

     java -jar sync.jar --stop

2. Extract the contents of setup.tar.gz to /opt/sync/.

3. Submit the following upgrade command:

   sudo bash /opt/sync/upgrade.sh

   Optional: You can specify the -InstallDirectory parameter if your previous installation uses a nondefault path.

4. Start the server in either of the following ways:

   • To start the server as a service, submit this command:

     sudo systemctl start sync

   • To start the service in-process, submit this command:

     java -jar sync.jar

Notes:

• No matter how you choose to deploy Sync, the files and folders that are contained in ApplicationDirectory must be readable and writable by the user who runs the application. The service.sh script that is included in Sync uses cdatasync as this user.

• If the application was previously run as a different user and you want to restore the necessary permissions for a cdatasync user to run the application, submit a command that is similar to the following:

  sudo chown -R cdatasync:cdatasync /opt/sync

Upgrading from CData Sync 2017, 2018, and 2019

The installer for CData Sync 2024 attempts to detect existing previous installations of Sync and to import previous settings. These imported settings include the following:

• All jobs

• All connections

• Any external connectors

• All Sync settings

Upgrading Marketplace Instances

When you use marketplace instances of Sync, CData publishes updated instances following new product enhancements and product releases. You can migrate your Sync configuration easily from the old instance to the new by following the steps listed earlier in Migration Tab.